On 9/15/2007, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: >> Please point out the language that says I MUST ACCEPT one with a >> null sender...
> It doesn't really exist in any standards track rfc - it is just the > way the protocol has been interpreted over the years. > > Now that is changing with the backscatter problem, and various > products now refuse null senders unless they are genuine bounces of > previously sent messages - Ironport device, the latest Mdaemon MTA > etc. Ok, so a follow-up... What types of legitimate messages use null sender? Is it only DSN type messages? Someone else (Marrco?) said that Return receipts & vacation messages(?) do this (I don't think a proper vacation autoresponder does - I'll have to look at one of ours)? What about things like meeting requests/confirmations/changes? I certainly wouldn't want to block those, or legitimate DSN messages. -- Best regards, Charles ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
