On 10/11/2017 01:23 AM, Dlugasny via Mailman-Users wrote: > > The problem is that we are sending an E-mail which looks as follow: > > From: [email protected] > Return-Path: [email protected] > To: @gmail.com > > The problem is that DKIM check on the gmail server server (and all others) > returning error: > [[email protected]](mailto:[email protected]) > does not designate xx.xx.xx.xx as permitted sender
This is not DKIM. it is SPF. external-company.com publishes an SPF record that doesn't allow myserver.com as a sender. Start at <https://en.wikipedia.org/wiki/Sender_Policy_Framework> to learn more about SPF. There are two solutions to this. The Return-Path: [email protected] header indicates that [email protected] is the envelope sender of the message and SPF is based on the domain of the envelope sender. solution 1). external-company.com can augment its published SPF record to designate your myserver.com server as a permitted sender. solution 2). Your mail relaying process can rewrite the envelope sender to your domain, e.g., [email protected] or some other appropriate @myserver.com address. This will break mailman's automated bounce processing for mail from [email protected] that is relayed by you, but if you can verify the deliverability of that mail before relaying it and if it's not deliverable, reject it before rewriting the envelope sender, that won't be an issue. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
