On 6/9/2010 10:11 AM, Proniewski Patrick wrote:
Hello,
I used to have a old SMTP server, with after-queue content filtering. My new setup involve a before-queue
content filter (amavisd). Unfortunately, Amavisd is a little bit strict about the smtp session: it
bounces email sent using "MAIL FROM: address" instead of "MAIL FROM:<address>".
It's ok for my all my clients but one. It's an appliance, so I cannot change
anything about its way to handle SMTP protocol.
Here is a debug session:
smtp/smtpd[86566]: connect from extron.domain.tld[192.168.42.241]
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 127.0.0.1
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 192.168.0.0/16
smtp/smtpd[86566]:> extron.domain.tld[192.168.42.241]: 220 smtp.domain.tld
ESMTP
smtp/smtpd[86566]:< extron.domain.tld[192.168.42.241]: HELO extron.domain.tld
smtp/smtpd[86566]:> extron.domain.tld[192.168.42.241]: 250 smtp.domain.tld
smtp/smtpd[86566]:< extron.domain.tld[192.168.42.241]: MAIL FROM:
applia...@domain.tld
smtp/smtpd[86566]:> extron.domain.tld[192.168.42.241]: 250 2.1.0 Ok
smtp/smtpd[86566]:< extron.domain.tld[192.168.42.241]: RCPT TO:
techserv...@domain.tld
smtp/smtpd[86566]: check_namadr_access: name extron.domain.tld addr
192.168.42.241
smtp/smtpd[86566]: check_addr_access: 192.168.42.241
smtp/smtpd[86566]: permit_mynetworks: extron.domain.tld 192.168.42.241
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 127.0.0.1
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 192.168.0.0/16
smtp/smtpd[86566]:> 127.0.0.1:10024: XFORWARD NAME=extron.domain.tld
ADDR=192.168.42.241 PORT=2488 HELO=extron.domain.tld PROTO=SMTP SOURCE=LOCAL
smtp/smtpd[86566]:> extron.domain.tld[192.168.42.241]: 501 5.5.2 Syntax: MAIL
FROM:<address>
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 127.0.0.1
smtp/smtpd[86566]: match_hostaddr: 192.168.42.241 ~? 192.168.0.0/16
smtp/smtpd[86566]: lost connection after RCPT from
extron.domain.tld[192.168.42.241]
smtp/smtpd[86566]: disconnect from extron.domain.tld[192.168.42.241]
I've read the Postfix documentation, especially this part:
The content filter should accept the same MAIL FROM and RCPT TO command syntax
as the before-filter Postfix SMTP server, and should forward the commands
without modification to the after-filter SMTP server. If the content filter or
after-filter SMTP server does not support all the ESMTP features that the
before-filter Postfix SMTP server supports, then the missing features must be
turned off in the before-filter Postfix SMTP server with the
smtpd_discard_ehlo_keywords parameter.
I know the problem is on Amavisd's side. But I'm sure others have been
confronted to this issue. Any idea other than patching amavisd?
thanks,
Patrick PRONIEWSKI
For problems with amavisd-new, better to ask on the
amavis-users list.
I don't think this is configurable in amavisd-new, in which
case the easiest solution is to redirect the problem client to
an unfiltered postfix listener.
Either have the client connect to a different IP:port, or use
firewall redirect rules.
-- Noel Jones
