> Disabling NUL Sender for us stops a lot more junk than it does
> actual bounces, because it seems that most delivery failures are
> identified during the attempt, not after the fact by some return
> message...
You cannot block <> in today's SMTP world if you have any regard for
your customers or clients, so you just need to get over it.
> (there are exceptions for a few systems that will accept virtually
> anything and then call back later...gateways maybe? AOL?).
ANY MX-only server will not be able to reject based on mailbox server
criteria such as mailbox quotas. Exchange versions prior to 2000
cannot reject at the envelope for unknown users. For that matter,
IMail mailbox servers--even when also MXs--do not reject at the
envelope for certain domain- and user-specific criteria. MXs that do
not have access to domain userbases, due either to the size of the
userbase or other reasons, are another factor.
> Personally, I feel that if a system fully accepted a message, then
> wants to generate a new message back later, it should identify
> itself as [EMAIL PROTECTED] or some such thing.
Submit your RFC and we'll see what we can do. :)
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]
SpamAssassin plugs into Declude!
http://www.mailmage.com/download/software/freeutils/SPAMC32/Release/
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
