Bulletproof email infrastructure setup guide
iafonov.github.com
Bulletproof email infrastructure setup guide
1–10 of 34 posts
Re: Bulletproof email infrastructure setup guide
#2Another option for bounce handling is to setup a client/server architecture. Continuing with the rails example: since directly spawning a rake task from a postfix hook will slaughter your machine if you get any decent amount of emails due to loading the whole rails stack each time, what I have chosen to do is this:
Postfix pipes the bounced email through command line to a simple client that shoves the body over a socket to a server process which has my full stack running. It then shoves the email into a resque queue to be handled by my normal job queue.
There are many ways to skin this beast, however if you need/want realtime response to emails, maybe to facilitate reply to notifications email to add a comment, and you get any decent volume of traffic, you want your postfix hook to be as fast as possible.
Re: Bulletproof email infrastructure setup guide
#3Another option for bounce handling is to setup a client/server architecture. Continuing with the rails example: since directly spawning a rake task from a postfix hook will slaughter your machine if you get any decent amount of emails due to loading the whole rails stack each time, what I have chosen to do is this: Postfix pipes the bounced email through command line to a simple client that shoves the body over a soc…
I think this would be the next step for me. For now our performance isn't a big issue and bounces are processed in background cron job once per several minutes. For now volumes of bounces are not so high as you have, so we are just fine with spawning application. Thanks for commenting.
Re: Bulletproof email infrastructure setup guide
#4Recently there's also DMARC, which allows a domain owner to specify their support of SPF and DKIM, and how to handle email that doesn't pass authentication.
Another benefit is feedback reports from major email providers on messages that have passed or failed authentication.
Re: Bulletproof email infrastructure setup guide
#5Recently there's also DMARC, which allows a domain owner to specify their support of SPF and DKIM, and how to handle email that doesn't pass authentication. Another benefit is feedback reports from major email providers on messages that have passed or failed authentication. http://dmarc.org/ http://en.wikipedia.org/wiki/DMARC
Thanks, I have never heard about this thing. I think I would add it to the article.
Re: Bulletproof email infrastructure setup guide
#6How likely are servers to reject your emails simply because the PTR records don't match? I'm using my ISP's SMTP server as a smarthost and I've configured the SPF record to match their server, but making them add a PTR record is out of the question, unfortunately.
(This is just for personal mail, that's why I'm avoiding paying for a proper setup)
Re: Bulletproof email infrastructure setup guide
#7Igor, thank you, excellent guide/walk-through.
Re: Bulletproof email infrastructure setup guide
#8How likely are servers to reject your emails simply because the PTR records don't match? I'm using my ISP's SMTP server as a smarthost and I've configured the SPF record to match their server, but making them add a PTR record is out of the question, unfortunately. (This is just for personal mail, that's why I'm avoiding paying for a proper setup)
I've had a few servers reject our office mail for it when we changed IP and forgot to update the PTR
Re: Bulletproof email infrastructure setup guide
#9How likely are servers to reject your emails simply because the PTR records don't match? I'm using my ISP's SMTP server as a smarthost and I've configured the SPF record to match their server, but making them add a PTR record is out of the question, unfortunately. (This is just for personal mail, that's why I'm avoiding paying for a proper setup)
As coob mentioned it could be rejected by some providers. Overall I think that situation when your emails are rejected by some providers is the worst possible. It is even worse than when all providers reject your email. For me the easiest way to track down such things is reading mta logs.
Re: Bulletproof email infrastructure setup guide
#10If I'm using a service such as Mailgun or Sendgrid, what parts of the article apply to me?