Wednesday Jul 29, 2009

Tuning Brightmail AntiSpam

This Blueprints article could be of use to the Messaging Server population. Synopsis:

This article provides background information on Symantec Brightmail AntiSpam (SBAS) software and CoolThreads technology-powered servers, the configurations used for performance measurements, the challenges presented by benchmarking anti-spam software, and the actual steps used to tune the hardware/software combination to achieve the reported performance levels.

Wednesday Nov 05, 2008

Messaging Server: Installing Multiple Instances

With the continued move towards using Solaris Zones for creating a Messaging Server installation of multiple instances, another approach to this situation might be getting lost in the mix. New in the Communications Suite installer (available with Messaging Server 6.3p1 and 7.0) is an "altroot" power user feature that enables you to install multiple instances of Messaging Server on the same host.

For more information, see the following document:

Performing Multiple Installations with an Alternate Root

A few caveats with this approach:

  • This feature gets limited operational testing, so we recommend field testing before deployment in your environment.
  • You have to configure the different instances to use different interfaces (for all the components) to prevent conflicts.
  • There are a few Messaging Server features that just won't work (for example, SNMP), and others that might require hand-editing to work (for example, SMF startup).
  • You need to understand the implications of altroot patching as well (it creates a SVR4 package/patch datastore separate from the main OS datastore for that information).

Hat tip CN

Wednesday Aug 27, 2008

Tutorial: Using the Portal Server Addressbook Provider for Comms Express

Not sure how in demand this is for the Comms Community, but just in case, Rajesh posted a nice how-to last month, detailing how to hook up the Portal Server Addressbook provider with Communications Express. Here's the link:

Wednesday Jul 30, 2008

Deep Email Thought of the Day

Some people are addicted. They might even live in a city near you.

Thursday Jul 17, 2008

Messaging Server: Taking the Bite out of Phishers

Great ideas from the Comms Community on how to deal with phishers.

Friday Jun 27, 2008

Messaging Server: Tripping Down Memory Lane

Ah, the good ol' days. (BTW, gas price was under $1.50/gallon back then, at least in CA.)

Hat tip Doug G.

Monday Jun 23, 2008

Email: The True Story Can Now Be Told... hates the living. (Rumor has it that the slides are on the way.)

Hat tip Jesse

Friday May 09, 2008

Messaging Server: Managing Tiered Storage Requirements

We've recently completed an article, posted on the Comms Wiki, titled "Messaging Server and Tiered Storage Overview." Here's a synopsis:

This document describes the operation of Sun Java System Messaging Server message store, its performance characteristics, and how to plan for and allocate store partitions. Additionally, this document describes next generation best practices to meet the storage needs of both ISPs and enterprises.

Part of what this article says is here you are now:

And here is where we think you ought to end up:

This article also contains a very nice summaries of the Comms logical two-tiered architecture as well as how Messaging Server works:

Thursday Apr 24, 2008

Modern Email Usage

And the survey is in: Spam in a landslide!

Thursday Apr 17, 2008

Messaging Server: Best Practices for userPassword Attribute

There was a question posed the other day about what, if any, character limitations there are for the userPassword attribute in our schema. The questioner pointed out that for the uid attribute, a number of characters are disallowed, including:

$ ~ = # \* + % ! @ , { } ( ) / < \\> ; : " ” [ ] & ?

Apparently, there are no such restrictions on the userPassword attribute. One of our Messaging experts reports to have seen most, if not all, of the disallowed characters for the uid attribute used in the userPassword attribute.

However, this does not necessarily mean that it is a good idea to consider all of these characters for use in the userPassword attribute.

In general, best practice would be to disallow characters that can be confused by a Unix shell or web page to be a seperator, wildcard, grouping symbol, or other meta character. For example, think about what could happen to a migration script or LDIF output that had userPassword: !/bin/sh;rm -r /\*. Instead of just reading the password characters, imagine the damage this could cause if a typo or bad code spawned the command.

The takeway: Just because something is "allowed" doesn't make it a good practice.

Note: uid, which is a synonym for userID (defined in RFC 1274), is used by Messaging Server not only for logging in, but also in hashed form, to specify part of the file path where user messages are stored. Thus, Messaging Server needs additional restrictions on the uid so that the file path constructed using the uid is good and safe. Furthermore, to avoid ambiguity with IMAP ACL syntax, the Message Store also enforces a restriction that the leading character of the uid cannot be a hyphen (-).

Hat tip KH and DL.

Friday Mar 07, 2008

Reminder: Messaging Server & Sun Cluster Software Support

An oldie but a goodie: In Case You Missed it, Messaging Server 6.3 Now Supported on Sun Cluster 3.2.

Note also that only Messaging Server 6.3 supports Sun Cluster 3.2 software. Previous versions of Messaging Server do not support Sun Cluster 3.2 software.

BTW, if you're looking for what's supported for the Communications Suite 5 version of Messaging Server (and Calendar Server), here's the scoop.

Thursday Feb 28, 2008

How to Reach More Users?

If you are a Telco, you better become a destination site, says Sun Microsystems Chairman Scott McNealy.

Friday Feb 22, 2008

Mozilla Messaging Aims to Fix 'Broken' Email with Thunderbird 3.0

Mozilla Foundation to evolve Thunderbird.

Thursday Jan 17, 2008

Messaging Server: New MTA Technical Note

What started as a blog discussion here has resulted in the following technical note, published to BigAdmin:

Preferred Practices for Deploying Sun Java System MTA


Typically, a Sun Java System Messaging Server deployment consists of front-end and back-end services. The front-end services enable users access to the system, while the back-end services store and provide access to data. In the past, we've heard disputes about how to deploy the MTA on the front end: either as an entrance gateway to the system, or “behind” an anti-spam/anti-virus service that also provides an MTA functionality. This article describes the recommended way to deploy your MTA with respect to anti-spam/anti-virus services.

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.


« July 2016