Wietse Venema wrote:
Daniel L. Miller:
[ Charset ISO-8859-1 unsupported, converting... ]
Wietse Venema wrote:
Daniel L. Miller:
Mar 4 23:21:33 mailserver postfix/smtpd[20964]: warning: proxy
inet:192.168.0.10:225 rejected "DATA": "250 2.1.5 Ok"
Your proxy replies with "250 2.1.5 Ok" to the "DATA" command.
250 Is an incorrect reply. It should be "354" for success,
5xx or 4xx for failure.
And because 250 is not a valid DATA reply, Postfix does not go into
the DATA phase.
Postfix then forwards the "250 2.1.5 Ok" to your SMTP client.
When you talk directly to Postfix, this is why you see "250 2.1.5
Ok" in response to DATA. This is clearly bogus, and I'll fix Postfix
so it will send some appropriate reply instead. But I won't be
posting patches for that.
Wow. Last thing I expected was to hear I found a bug in Postfix 2.5.
THIS IS NOT A POSTFIX BUG. POSTFIX IS ONLY THE MESSENGER.
Okay, okay!! I take it back! I misunderstood! It's not Postfix bug!
The proxy filter replies with SMTP reply code 2.1.5 to the SMTP
DATA command. That is the problem.
My fix only makes sure that this bogus reply from the proxy filter
would not confuse naive SMTP client software, so that it will stop
sending message-id etc. headers after it receives a 2.1.5 reply.
You can log the conversation between SMTP client, Postfix and the
proxy filter by adding one -v option on the smtpd command line in
master.cf, or by using debug_peer_list and debug_peer_level in
main.cf.
Wietse
I tried the -v option (wow - lot of stuff goes on behind the scenes,
doesn't it?!). What I still don't understand (I'm dense, I know, but
please bear with me) is why there is a difference between connecting
through Postfix to ASSP (and back to Postfix) and connecting to ASSP
directly (and back to Postfix).
Somehow, someway, there is a difference between telnet - or my mail
client (Thunderbird) - connecting directly to ASSP, vs. connecting to
Postfix and the Postfix smtp process connects to ASSP. Just to be 100%
sure we're communicating, I'll try a picture:
Client ---> 192.168.0.10:225 (ASSP) ---> 192.168.0.11:325 (Postfix
smtpd) ---> internet
vs
Client ---> 192.168.0.11:25 (Postfix smtpd with proxy parameter) --->
192.168.0.10:225 (ASSP) ---> 192.168.0.11:325 (Postfix smtpd) ---> internet
Since I'm not adjusting the ASSP settings between connections - I don't
see where this is an ASSP configuration problem. Is there anything
about one of the _filter parameters that would change the
communication? Do I need to change something in a transport?
--
Daniel
