Could you please stop those full quotes and reduce the quoted context to
the relevant parts?
On 01-04-30 Felipe Alvarez Harnecker wrote:
> Bulent Murtezaoglu writes:
> > >>>>> "ELBnet" == Tech Support <support@elbnet.com> writes:
> > ELBnet> Try using: headers_check_syntax = true headers_checks_fail
> > ELBnet> = true
> > ELBnet> which checks to be sure the From To BCC etc. are correctly
> > ELBnet> formatted and rejects them if not.
> > Which would do you no good for two reasons:
> > 1- The original poster wants to block the null sender in the envelope
> > from.
> > 2- The null sender is a legitimate envelope from.
> > Based on my e-mail interaction with the original poster (sender ?)
> > I think what is being missed here is RFC 1123 which says
> > 5.2.9 Command Syntax: RFC-821 Section 4.1.2
> > The syntax shown in RFC-821 for the MAIL FROM: command omits
> > the case of an empty path: "MAIL FROM: <>" (see RFC-821 Page
> > 15). An empty reverse path MUST be supported.
> > and again in summary table 5.4, it says RECEIVER-SMTP _MUST_ send
> > error notification messages using the null return path.
> > If you block the null sender some nasty things happen. For example
> > your customer sends off an important price quote to an important
> > customer using the wrong e-mail address, the mail gets queued
> > in some relay and eventually gets bounced (with null envelope sender),
> > but since you refuse such messages your customer never finds out.
[...]
> Ok. I'm the original poster and what i want is:
> Mails with a NULL sender with an invalid recipient get bounced to the
> email address of any Header that happen to exists.
> And if the recipient doesn't exists and
> there is no way to bounce then reject.
What you are suggesting here is a violent of the RfC. Bounces will
always be send by a Mail-Server with MAIL FROM: <>. Rejecting or
Bouncing this mail is a violation of the RfC, since the host should
accept them and the postmaster should check those bounces then. So if
you really want to create this setup, please refrain from connecting
this mail-server to the internet and let customers use it, until it's
properly configured according to the RfCs. Never reject or bounce any
mail with MAIL FROM: <> in any way. This mail should always be accepted
by a/your mailserver and the admin/postmaster should check them. If you
really want to violate RfCs and connect a broken mail-server to the
internet, then you should figure this one out on your own. But don't
start wondering why in the future postmaster and users will get annoyed.
Christian
--
Debian Developer (http://www.debian.org)
1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853
Attachment:
pgpUGggxXLQSf.pgp
Description: PGP signature