Re: Invalid address and bounce from Exchange

From: Eray Aslan (no email)
Date: Thu Feb 01 2007 - 04:56:30 EST

  • Next message: Eray Aslan: "Re: Invalid address and bounce from Exchange"

    Eray Aslan wrote:
    > Postfix acts as a relay for our internal exchange server. The following
    > message generates a bounce from exchange. Shouldn't
    > reject_non_fqdn_sender catch these addresses?
    >
    > mail ~ # zgrep 503242E4DC /var/log/mail.log.1.gz
    > Jan 29 16:50:46 mail postfix/smtpd[30273]: 503242E4DC:
    > client=unknown[201.76.232.39]
    > Jan 29 16:50:47 mail postfix/cleanup[30290]: 503242E4DC:
    > message-id=<1d9701c743b4$034438c1$27e84cc9 at kawanna>
    > Jan 29 16:50:50 mail postfix/qmgr[7027]: 503242E4DC: from=<@cathye.com>,
    > size=7570, nrcpt=1 (queue active)
    > Jan 29 16:50:58 mail postfix/smtp[30291]: 503242E4DC:
    > to=<>, relay=127.0.0.1[127.0.0.1]:10024, delay=13,
    > delays=5.1/0/0.01/7.6, dsn=2.6.0, status=sent (250 2.6.0 Ok,
    > id=29009-20, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as
    > E85E09148D)
    > Jan 29 16:50:58 mail postfix/qmgr[7027]: 503242E4DC: removed

    As far as I can tell, RFCs allow empty local part as quoted null string.
     Even if it is technically correct, should we allow empty local parts in
    email address in the form of @example.com? Certainly, it not
    deliverable. Or is Exchange at fault here and I should solve this by a
    regexp in check_sender_access?

    -- 
    Eray
    

  • Next message: Eray Aslan: "Re: Invalid address and bounce from Exchange"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD