By joesciallo on Feb 28, 2007
- Directory Scalability at Telcoms
- Communication Express: Authentications Between Components
- Communications Express Deployments in 6.3
My email server was down from around 6pm last night until noon today (sendmail, not Messaging Server), and once back up, I decided to do some cleanup on my--ahem!--out of control inbox. (Afterall, a smaller inbox WILL help in times of system recovery.)
In the process of my cleanup, I came across an email thread that I thought I'd post, to see if the Comms Community cares to discuss. The topic: What information pertaining to Comms could we (Sun) provide more in-depth training/knowledge coverage on? Here are the responses. Granted, I'm only one tech writer on Comms, but the more feedback I can gather on issues such as this, the better off I can come to my SMEs and try and argue for what the customer needs. (Note: I believe this was initially a "training" request, but from where I sit, waiting for training courses to come out (no offense to our training coordinators and developers) takes too long to address the info/knowledge gaps.)
Just for grins, I took a look at what some of us have been discussing about general Comms topics we "think" we should be working on in terms of Comms training/knowledge enhancement:
Now, for more data points. I did an internal survey of our field/engagement forces a few months back, with the same question, and got these responses:
In an ideal world, we'd be working on all these topics, but unfortunately, we have to prioritize them and assign what resources we have accordingly. The good news is, some of these topics have already been addressed, or are in the process of getting addressed by documentation. Now that I have this list assembled and am looking at it in its entirety, I see that another post is in order to recap where we're at, and where we hope to go. Stay tuned for details.
And as always, drop a line if you have any suggestions on what docs/information you'd like to see us work on.
I like it when I can say, here's some new information for you. As I mentioned yesterday, we were close to getting out a cool article (and it's actually the script that is cool) for generating an automatic email to your Calendar Server users, containing that day's appointments and tasks. Have at it:
Thanks to Mike d. for contributing this info.
As I wrote about in this previous blog entry, I've been working in conjunction with one of our Calendar Server gurus to document how to provide your Calendar Server users with a daily summary of their Calendar Server events and tasks, emailed to their inbox or mobile device each weekday morning. I've got the article on our internal staging site, and it should be pushed out this week to BigAdmin.
While were at it, for more fun with Calendar Server, see this post by a new Sun employee (formerly with SeeBeyond) and his positive experiences with Thunderbird and the Lightning extension that is part of the Sunbird Mozilla project, to access his Calendar Server data from w/i Thunderbird.
I'm not a Mac user (yet)--actually, I'm thinking about making my next computer purchase a Mac, but that's another story--but for those of you who are, and are using our Sun Java System Calendar Server product, there's good news: You can use JSCalendarSync to synchronize data between Calendar Server and Mac OS X’s iCal.
JSCalendarSync uses the native synchronization framework provided by Mac OS X 10.4. Note that JSCalendarSync development is in progress, it is not to be considered as a finished product. Mac users can also benefit from Lightning, the Mozilla Thunderbird extension, created by Sun's StarOffice developers. Indeed, several Sun teams are using Thunderbird+Lightning to collaborate.
With the proliferation of browsers and versions of specific browsers, it's only natural that we get the question, and quite often, which browsers does Communications Express support? As always, start with the Release Notes to find out. For the current version, that is, Communications Express 6 2005Q4, the "supported" browsers are Netscape 7.2, IE 6.0 SP2 or later 6.x version, and Mozilla 1.4.
Though this is the "officially supported" browser list, we are always working to certify the most commonly used browsers over time.
Norwegian Governmental Services To Be Powered by Sun Solutions, Including Messaging Server and Calendar Server
The Norwegian government announced a deal with Sun to use the Solaris 10 Operating System, and Sun servers and software, including Messaging Server, Calendar Server, and Portal Server, to enable citizens to have secure, browser-based public access to government services through a secure and personalized portal interface. The complete end-to-end Sun solution allows the government to drive innovation and provide an online platform for citizens to vote, pay taxes, obtain social security benefits, register and manage automobiles, communicate with public officials and conduct other civic initiatives and services.
So you want every sent email from every employee to carry a company disclaimer message. Whether because of increased awareness of confidentially, legality, or fashion, appending disclaimer messages to out-going mail is here with us.
But before asking how to do this with the Sun Java System Messaging Server MTA, step back and ask if you really need to do this. Start by reading the following:
Here's perhaps the money quote:
"In the end, I think, although I am vastly ignorant of the law here, that adding disclaimers only makes you more vulnerable. This is because without disclaimers reasonable conventions and existing law apply. But once you add the disclaimer you had better get it exactly right and on exactly the right messages, and you sacrifice reasonable convention."
Okay, let's say that in spite of this advice, you want to proceed full steam ahead anyways and get every outgoing message from the MTA to bear this disclaimer stamp. Our experts advise the following:
For more information, see the following:
Some Troubleshooting Advice
If you configure the MTA as described above, and run into problems where the disclaimer is not appearing, you should begin by looking at your conversions file, and get a master_debug conversion channel debug log file. (The tcp_local_slave.log-\* file, and the mappings file, are just about getting the message to the conversion channel. The appending of the disclaimer would be done by the conversion channel, so you need to see what the conversion channel itself is doing.)
As we get closer to releasing Messaging Server 6.3 (part of Communications Suite 5), I thought I'd provide a bit more detail on some of the major feature enhancements. This entry focuses on Message Archiving, also known as AXS-One Archiving.
What Is Message Archiving?
A message archiving system saves all or some specified subset of incoming and outgoing messages on a system separate from Messaging Server. Sent, received, deleted, and moved messages can all be saved and retrieved in an archive system. Archived messages cannot be modified or removed by email users so the integrity of incoming and outgoing is maintained.
How Is the Archiving Support Provided?
In 6.3, Messaging Server supports archiving through the AXS-One archive system.
How Is Message Archiving Useful?
There are two ways to look at archiving, compliance and operational. Compliance archiving is used when you have a legal obligation to maintain strict retrievable email record keeping. Selected email (selected by user(s), domain, channel, incoming, outgoing and so on) coming into the MTAis copied to the archive system before being delivered to the message store or the internet. Archiving can be set to occur either before or after spam and virus filtering. Operational archiving is used for mail management purposes, for example to reduce storage usage on the Messaging Server message store by moving less used (older) messages to an archiving system which uses lower cost storage (that is, an alternative for data backup). Note that compliance and operational archiving are not exclusive. That is, you can set up your system so that it does both compliance and operational archiving.
Where Can You Get More Information?
The Messaging Server 6.3 Administration Guide will have overview information on message archiving. The Message Archiving Using the AXS-One System technical note will contain detailed deployment instructions. As usual, you'll be able to get these docs through the docs.sun.com web site, or better yet, through the Communications Suite Hub Library tab.
Note: If you have access to the Beta, you can read the AXS-One technical note now at (sorry for those who don't, it's password protected):
I'm sure most of you are following this:
The Energy Policy Act of 2005 mandates that US DST will start on the second Sunday in March and end on the first Sunday in November. In 2007, the start and stop dates will be March 11 and November 4, respectively. These dates are different from previous DST start and stop dates. In 2006, the dates were the first Sunday in April (April 2, 2006) and the last Sunday in October (October 29, 2006).
In case you want to know how this affects the Communications Suite products, here's the link:
Never a dull moment here in Comms Suite docs. That is, there is never any downtime, I'm always getting new requests for information deliverables. So, here's a quick update on what's in the pipeline:
As usual, I hope the Comms Suite community finds this kind of information useful and pertinent, and if you have any suggestions or doc needs, please feel free to leave a comment or drop me a line.
We in documentation hear what customers want: more examples. Communications Suite examples, especially for deployment, are unfortunately far and few between. Good news is that I'm updating the single-host deployment example for the upcoming Communications Suite 5 release.
And more good news: the document itself is shrinking by a number of pages. Does this mean that the Comms Suite stack (along with the Java ES components it requires) is getting easier to install? Well, maybe. Some changes in the Communications Suite 5 release that are reflected in this doc include:
I should have this document ready at release time, unlike in the past, where we had some lag time between getting the release bits installed to be able to test the doc and get it out.
BTW, if you are looking for current Communications Suite (aka Communications Services) examples, check them out here:
Okay, over the weekend the docs.sun.com site underwent some changes. If you're having problems finding the Communications Suite (Messaging Server, Calendar Server, Instant Messaging) doc collections, you are not alone. They have been relocated. Here are your choices to get the docs in this new taxonomy:
- Click the Sun Java Enterprise System link on the docs.sun.com front page.
- Click the Collaboration and Communication link.
- Click the appropriate product collection.
- Messaging Server: http://docs.sun.com/app/docs/prod/mess.svr#hic
- Calendar Server: http://docs.sun.com/app/docs/prod/cal.svr#hic
- Instant Messaging: http://docs.sun.com/app/docs/prod/im#hic
Interesting predictions for 2007 on mobile email and backup/restore from Synchronica CEO Carsten Brinkschulte:
The next figure shows a correct deployment of an anti-spam/virus filter solution.
The Messaging Server MTA performs certain functions well, including:
The anti-spam/virus filter is good at determining if an email is spam or has a virus, but is generally not nearly as good at doing the things expected of a good MTA. Thus, do not depend on an anti-spam/virus filter to do those things. Your deployment is more "correct" when the anti-spam/virus filter is well integrated with the MTA, which is the case with Messaging Server. Messaging Server spam filter plug-in support provides all the potential reasons to reject a message early and applies all reasons at the same time.
A robust MTA, such as Messaging Server's, contains security features (SSL/TLS, traffic partitioning by IP address, early address rejection to reduce denial-of-service attacks, connection throttling by IP address/domain, and so on), which are defeated when an anti-spam/virus filter is deployed in front. Furthermore, anti-spam/virus filters that communicate by using the SMTP protocol often do not follow the robustness requirements of SMTP and thus lose email when they shouldn't. A correct deployment should have the anti-spam/virus filter working in conjunction with a robust MTA.
Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.