Neal's Admin.Notes.

Adding IMAP4 to Exchange 2003 Cluster

This is a simple task, just remember a few things.

The IMAP4 and POP Virtual Servers are not installed as a default resource in Exchange 2003 Cluster. Because of this, you need to change the IMAP Service from "Disabled" to "Manual" on the Services Menu ( under Computer Management -> Services ) of each node.If you do not change the service's properties and tried adding the resource , your Exchange Group will fail...and fail miserably. Anyways..from this point you can go ahead and add you IMAP Viirtual Server, with its dependancies. I use a geographically dispersed cluster, and my dependancies were only the System Manager and the Drives. Enable the resource when you're all done and you can IMAP ! The same process applies to POP service, if you want to add that to you cluster resource that it.

How to Avoid "Read Receipts" for Mail-Enabled Groups

Sometime you don't want that Exchange sends "read receipts" to message originator. This is espesially necessary when the e-mail has been sent to a distribution list. You can disable this by following the instructions: - Start "Activ Directory Users and Computers" - Find the distribustion list you want to configure - Choose properties - On the Exchange Advanced tab of a mail-enabled group's properties, you have the following three options for delivery reports: - Send delivery reports to group owner - Send delivery reports to message originator - Do not send delivery reports If you select Do not send delivery reports, you also disable the sending of read receipts.

SenderBase.org

The number of end user systems on the major networks that are running some sort of malware mail transfer agent is astounding in some ways. SenderBase does a pretty nice job of wrapping the available information and making it easily available.

Non Delivery Reports

Each NDR provides a 3-digit status notification code that defines the failure in detail. Each of these three digits provides information about the failure itself and can be translated as follows:

2.x.x > successful transfer
4.x.x > persistent failure
5.x.x > permanent failure

The following list describes second and third digit:

x.1.0 > other address status
x.1.1 > bad destination mailbox address
x.1.2 > bad destination system address
x.1.3 > bad destination mailbox address syntax
x.1.4 > destination mailbox address ambiguous
x.1.5 > destination mailbox address valid
x.1.6 > mailbox has moved
x.1.7 > bad sender’s address syntax
x.1.8 > bad sender’s system address
x.2.0 > other or undefined mailbox status
x.2.1 > mailbox disabled, not accepting messages
x.2.2 > mailbox full
x.2.3 > message length exceeds administrative limit
x.2.4 > mailing list expansion problem
x.3.0 > other or undefined mail system status
x.3.1 > mail system full
x.3.2 > system not accepting network messages
x.3.3 > system not capable of selected features
x.3.4 > message too big for system
x.4.0 > other or undefined network or routing status
x.4.1 > no answer from host
x.4.2 > bad connection
x.4.3 > routing server failure
x.4.4 > unable to route
x.4.5 > network congestion
x.4.6 > routing loop detected
x.4.7 > delivery time expired
x.5.0 > other or undefined protocol status
x.5.1 > invalid command
x.5.2 > syntax error
x.5.3 > too many recipients
x.5.4 > invalid command arguments
x.5.5 > wrong protocol version
x.6.0 > other or undefined media error
x.6.1 > media not supported
x.6.2 > conversion required and prohibited
x.6.3 > conversion required but not supported
x.6.4 > conversion with loss performed
x.6.5 > conversion failed
x.7.0 > other or undefined protocol status
x.7.1 > delivery not authorized, message refused
x.7.2 > mailing list expansion prohibited
x.7.3 > security conversion required but not possible
x.7.4 > security feature not supported
x.7.5 > cryptographic failure
x.7.6 > cryptographic algorithm not supported
x.7.7 > message integrity failure