spf

Potential issues using member's “from” address and the “sender” header

时光怂恿深爱的人放手 提交于 2019-11-27 17:37:27
A major component of our application sends email to members on behalf of other members. Currently we set the "From" address to our system address and use a "Reply-to" header with the member's address. The issue is that replies from some email clients (and auto-replies/bounces) don't respect the "Reply-to" header so get sent to our system address, effectively sending them to a black hole. We're considering setting the "From" address to our member's address, and the "Sender" address to our system address. It appears this way would pass SPF and Sender-ID checks. Are there any reasons not to

Too many DNS lookups in an SPF record

二次信任 提交于 2019-11-27 09:36:56
问题 My website needs to send out emails with Google Apps, SendGrid and MailChimp services. Google Apps is used to receive and read incoming email to my domain. I need to set the SPF record for my domain. The following is syntactically correct (not sure about A and MX tokens): "v=spf1 a mx include: _spf.google.com include: servers.mcsv.net include: sendgrid.net ~all" But if I test it with http://www.kitterman.com/getspf2.py I get PermError SPF Permanent Error: Too many DNS lookups Similar problem

Potential issues using member's “from” address and the “sender” header

好久不见. 提交于 2019-11-26 19:10:03
问题 A major component of our application sends email to members on behalf of other members. Currently we set the "From" address to our system address and use a "Reply-to" header with the member's address. The issue is that replies from some email clients (and auto-replies/bounces) don't respect the "Reply-to" header so get sent to our system address, effectively sending them to a black hole. We're considering setting the "From" address to our member's address, and the "Sender" address to our