From: Wietse Venema (no email)
Date: Sun Oct 14 2001 - 18:23:24 EDT
Greg A. Woods:
> The message was sent with the "sendmail -t" command-line interface.
> Here are the original recipient headers I created:
>
> To: . ,
> ,
>
> Here's how Postfix re-wrote them (note the dropped space!):
>
> To: .,
> ,
> Cc:
>
> As a human I would have inserted a comma, and NEVER drop the space!
> I guess the problem is what assumption to make when one finds there are
> some valid commas already....
Yep. Postfix parses right to left. It's kind of hard to parse named
groups left-to-right.
> (not unsurprisingly even the latest Smail makes a very similar parsing
> error, though oddly it seems to also strip the last "@host" from what it
> sends in the RCPT TO: -- I'll have to try to fix that.... :-)
>
> It then proceeded to hand off the resulting concatenated mess un-quoted
> in the SMTP connection.
That is the result of a choice between two evils.
Early Postfixen quoted the localpart as "a at b"@c. If Postfix was
the primary MX then it would bounce the mail because "a at b" is not
a local iser.
The problem was when Postfix was a backup MX and Sendmail the
primary. It was found that the Sendmail boxen would strip the
quotes, causing nasty open relay problems.
That is why Postfix no longer quotes a at b@c, so that its address
rewriting machinery can recognize the @ inside the localpart. This
is necessary because Postfix address rewriting is token based, not
regexp-based.
> Finally even more surprisingly postfix complains when it gets a 5xx
> reply to the resulting errant RCPT TO:
Postfix always send postmaster notice if it gets a 50x reply,
because that is indicative of a protocol or syntax error.
Wietse
-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users
|
|
|