Yes. It is redhat 5 >who wrote that client and why? It is a legacy application written years ago by dev team. I will try upgrade postfix either on RHEL6 to leverage command_filter as suggested by Mr. Venema. The last option would be to get someone to modify the client app code.
Thanks, Steve -----Original essage----- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of li...@rhsoft.net Sent: Tuesday, December 23, 2014 5:42 PM To: postfix-users@postfix.org Subject: Re: 5.5.4 Unsupported option: <supp...@mycompany.com> Am 24.12.2014 um 02:32 schrieb steve zeng: > I put the following debug and command_filter in main.cf: > > smtpd_command_filter = pcre:/etc/postfix/command_filter notify_classes > = resource, software, protocol, policy > > /etc/postfix/command_filter: > /^(MAIL\s+FROM:).+(<.+>)/ $1$2 > > In postmaster email, I got: > > Out: 220 qa.mycompany.com ESMTP Postfix > In: HELO app01.mycompany.com > Out: 250 postfix.mycompany.com > In: MAIL FROM: Customer Support <do.not.re...@mycompany.com> > Out: 555 5.5.4 Unsupported option: Customer > > It looks like the command filter did not kick in. when looked at its > document, it appears available from postfix > 2.7 and above. I am currently 2.3.3 and cannot upgrade it for company > policy smells like RHEL5 > http://www.postfix.org/postconf.5.html#smtpd_command_filter > > Is there a postfix config to simply disable the syntax check on MAIL > FROM field? The Exim version we had before does not check it who wrote that client and why? MAIL FROM != From-Header