With Exchange 2003 SP2 coming out soon, Sender ID will become more important.  How do you set up the DNS record for the domains in your organization?  You can easily do this with the SPF Record Wizard.
http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx

Should a company start doing this now?  Yes.  Even though the Exchange's Sender ID functionality is not available for much of the public, companies are already implementing this and other technologies that use SPF records.

The homepage of Sybari (http://www.sybari.com) has a new logo on it.

Microsoft has completed the acquisition of Sybari! This is good news for our customers.  The press release (http://www.microsoft.com/presspass/press/2005/jun05/06-21SybariCompletePR.mspx) says the following:

"Microsoft will offer Sybari products for the Microsoft Windows platform, including Antigen for Microsoft Exchange, Antigen for Microsoft SharePoint^® Portal Server and Windows SharePoint Services, Antigen for Instant Messaging, Antigen for SMTP Gateways, Sybari Enterprise Manager, Advanced Spam Manager, Advanced Spam Defense and Antigen for Domino on Windows NT^®.

Microsoft will continue to offer high-quality customer support for the complete range of Sybari products offered before the acquisition."

Sybari also is on the Microsoft site at http://www.microsoft.com/windowsserversystem/solutions/security/sybari.mspx but most of the links point back to the Sybari site.

Now if I could just get my hands on a copy internally...

First let's explain the difference. A really good article on Journaling is included below as well as the definition of the two:

Journaling with Exchange Server 2003

"Journaling is the ability to record all communications in an organization. E-mail communications are one of many different communication mechanisms that you may be required to journal. Therefore, journaling in Exchange has been developed to enable the messaging administrator to feed messaging data into a larger journaling solution, while using minimum overhead.

It is important to understand the difference between journaling and archiving. Journaling is the ability to record all communications; alternatively, archiving refers to reducing the strain of storing data by backing it up, removing it from its native environment, and storing it elsewhere. That said, you may use Exchange journaling as a tool in your e-mail retention or archival strategy."

For journaling, customers are using the journaling that is built into Exchange 2003. Some send all of this to third party solutions either on site or elsewhere for storage and they use other means to search and retrieve that data when it is needed.

For ideas as to what our partners can provide please as far as the archiving portion of this check out the following article:

Supporting Regulatory Compliance with Exchange Server 2003

Our partners in this space are IXOS, KVS, LEGATO Software, and ZANTAZ.

Ok, this gets asked a lot because some companies have the policy of not allow their employees to archive mail to a .pst and the message from the Exchange server says:
"You may not be able to send or receive new mail until you reduce your mailbox size. To make more space available, delete any items that you are no longer using or move them to your personal folder file (.pst). Items in all of your mailbox folders including the Deleted Items and Sent Items folders count against your size limit. You must empty the Deleted Items folder after deleting items or the space will not be freed."

So, the old way of doing this was hiring MCS to come in and modify a couple of .dlls so that the text said something different.  But if those .dlls got updated in a service pack, you had to do it all over again.  Plus, if you called into Microsoft Support and said that you got the error: "Your mailbox is too large.  Clean it up."  The response would be: "????  I've never heard of that error. That isn't in our code..."

Then we released a fix that would allow you to turn off all mailbox size limit messages.  How to disable mailbox size limit warning messages on an Exchange 2000 Server computer.  This was included in Exchange 2003 SP1 and also could be found in the Exchange 2000 Post SP3 roll-up.  But this was an on or off thing.  Administrators sometimes want the message to be sent.  They just want it to say something else. 

Then Jason Nelson announced the release of the Exchange Quota Message Service.  This is a separate service that can run on your exchange servers and send out custom messages.  Its source code is available under the Microsoft Shared Source License.  It isn't supported by PSS\CSS.  It currently has been updated to allow for easier installation than before. 

Wouldn't it be nice if this or something similar was included in the product? 

The http://www.microsoft.com/exchange site now includes more official information about Exchange 2003 SP2.  Some of the improvements:

• Updated OAB to speed up downloads.
• Updated Exchange Intelligent Messaging Filter to include blocking phishing schemes.
• Sender ID - finally.