I get lots of email concerning all kinds of aspects of our Communications Suite products. As a writer, part of my job is to sift and dig through this constant heaping of information, and ultimately help determine what to do with it.
Here's a quick grab bag of facts that seemed perhaps obvious and then again, perhaps not. If we had a Frequently Asked Questions document, this is where I would locate such information. (Note: I am investigating a means to do this on a Sun external site, such that the FAQ would be editable by anyone. Stay tuned for details.)
PDA Access to Communications Express?
You need Sun Java System Communications Sync
, which syncs PalmOS and Windows Mobile 5.0 PDAs to Sun calendar and contacts.
Communications Express Without Access Manager?
It's a current requirement, when running Communications Express 6 2005Q4 to have to use Schema 2 and
Access Manager. The Access Manager requirement is evidentally removed in the upcoming release (Communications Suite 5, Communications Express 6.3). The Communications Express 6.3 Administration Guide will have the details.
Will a New Messaging Server 6.x MTA Function with a 5.2 Message Store?
It depends on your setup. You cannot mix Messaging Store 5.2 store executables with 6.x MTA executables. However, you may deploy a 6.x MTA running on one host
delivering mail to a 5.2 Message Store running on another host. In such a deployment,
you'll also need a 5.2 MTA on the store machine because LMTP isn't
supported in Messaging Server 5.2, but such a setup will function.
ACLs Missing from Messaging Server 5.2 imsbackup?
The imsbackup utility in Messaging Server 5.2 does not back up the ACLs. This is a known issue. Unfortunately, this could impact maibox migrations. As a workaround, you can get the ACL list from the old store with the following command:
mboxutil -l -p pattern -x
then set it with readership -s after the migration.
Adding New Spelling Dictionaries to Communications Express?
The dictionaries in Communications Express are from ispell, which can be downloaded here:
See the Communications Express Customization Guide for details on installing the new dictionaries.
Calendar Server: Linux or x86 Front-end with a Solaris SPARC Back-end?
Beginning with Calendar Server 6.3, mixing different architectures for front-end and back-end machines is now supported. The hardware platforms no longer must be the same on each end. The big-endian vs.small-endian incompatibility no longer applies and you can now use both an x86 platform machine and a SPARC platform machine in the same Calendar Server deployment containing front-end and back-end machines. You can also mix Linux and Solaris x86 systems for front-end and back-end machines.