On Mon, Jan 07, 2002 at 11:59:19PM -0500, Charlie Brady <[EMAIL PROTECTED]> wrote:
>
> On Tue, 8 Jan 2002, Darrell May wrote:
>
> > solution. Block all emails coming in on the external interface addressed
> > directly to the postmaster. Don't know if this might 'break' something.
>
> Like RFC822 compliance, perhaps?
Yep. Talking directly to the SMTP port on a remote system and sending
mail to "Postmaster" is sometimes the only way to notify them of problems.
It's pretty sad (but sadly common) when "Postmaster" itself bounces :-(
http://www.ietf.org/rfc/rfc0822.txt?number=822
6.3. RESERVED ADDRESS
It often is necessary to send mail to a site, without know-
ing any of its valid addresses. For example, there may be mail
system dysfunctions, or a user may wish to find out a person's
correct address, at that site.
This standard specifies a single, reserved mailbox address
(local-part) which is to be valid at each site. Mail sent to
that address is to be routed to a person responsible for the
site's mail system or to a person with responsibility for general
site operation. The name of the reserved local-part address is:
Postmaster
so that "Postmaster@domain" is required to be valid.
Note: This reserved local-part must be matched without sensi-
tivity to alphabetic case, so that "POSTMASTER", "postmas-
ter", and even "poStmASteR" is to be accepted.
Gordon
--
Gordon Rowell [EMAIL PROTECTED]
VP Engineering
Network Server Solutions Group http://www.e-smith.com
Mitel Networks Corporation http://www.mitel.com
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
