[exim] NDN, Mailer-Daemon, DSN - EXIM

Top Page
Delete this message
Reply to this message
Author: Nazarevych Ol
Date:  
To: exim-users@exim.org
Subject: [exim] NDN, Mailer-Daemon, DSN - EXIM
Hello, we have an issue with Non-Delivery Notification NDN in Exim 4.90_1
There are 2 mail servers Exim and one as Email Spam Filtering - Cisco Ironport (ESA)

The Primary Mail server:
primary_hostname = main1.company.com, qualify_domain = company.com

The Internal server for mass mailing:
primary_hostname = corp17.company.com and the qualify_domain = company.com

As MX server for domain company.com acts Cisco ESA so the all correspondence goes thru for a spam filtration.
SPF, DKIM, and DMARK records configured correctly and everything works as well expect NDN Notification

For SPF used rule for example:
v=spf1 a mx ip4:1.1.1.1 ip4:2.2.2.2 ip4:3.3.3.3 -all


But when someone try to sending an email through Internal server corp17.company.com to non existing email address for example wwwwii@???
the corp17.company.com forms a NDN mail to user from company.com domain and trying to sent it through MX server - Cisco ESA. As there were SPF
configured for domain company.com Cisco ESA check field and report that

Received-SPF: None (esa.company.com: no sender authenticity information available from domain of
postmaster@???) identity=helo; client-ip=1.1.1.1; receiver=esa.company.com;
envelope-from=""; x-sender="postmaster@???"; x-conformance=spf_only


Off course there is no SPF records for domain: corp17.company.com - its only primary_hostname of the server.

Why "Internal server" use primary_hostname instead qualify_domain ?
I'll trying to set dsn_from = Mail Delivery System <Mailer-Daemon@$qualify_domain> but receive the same message above.