Bugzilla email routing change

[mark]

Hi all,

I've moved Bugzilla's outgoing email to Mailgun (http://mailgun.net/). This should improve reliability of the emails because it now does SPF and DKIM on the outgoing messages. This should also reduce the headache of me trying to manage email in an EC2 environment, which is kind of a pain.

This should be no-op to most of you, but if you stop getting bugmail or something weird happens, please let me know and I can investigate.

Comments

[foxfirefey]

Sexy!

[denise]

Hm. Looking at the things they offer, the "campaigns" thing seems like it could be very interesting from an analytics standpoint. How hard would it be to pipe the sending of site communication through them too? (Things like password reset emails, community membership requests, and official post notifications, not general comment emails.)

If nothing else, offloading official post notifications to them might keep there from being the usual hour-long mail delay after a news post gets posted...

Possibly this is not possible, or not cost-effective, or just a stupid idea, but it would be really fascinating to have those analytics so we could work on improving the messaging in our emails.

[mark]

Oh, super duper easy. I'm using them at Bump to send our marketing stuff, which is how I got to know them. Their service is really awesome. I am not sure how much email we send on a regular basis, but using Mailgun would certainly increase our deliverability metric.

[denise]

I'll think about how we could best utilize something like that. Send me the login information for our account when you get a chance so I can look at their available metrics?

If nothing else, offloading the news post notifications could seriously help fix a seriously annoying problem.

[mark]

The password is in the file /root/.mailgun on sb-admin01.

Edit: They don't do sub-accounts. Also, please don't change anything, of course. :)

[denise]

I promise! I know better than to start mucking about with things ;)

Thank you! (And I'm really off to bed now. Pinky swear.)

[mark]

Also, it looks like we send ~4 million emails per month. This would put us in Mailgun's first-class tier which is a graduated tier. At this volume, it would cost nearly $1,000/month to have them send all of our emails. To use the "Campaign" feature, the cost goes up by 50%. We might be able to talk to them about a discount given that we're an open source project, etc.

I don't know that spending that much money on email is worth it when we already have a somewhat functional solution. The thing with the news post emails can be addressed by just having a send_email_batch worker so that they run separately from the normal email workers. That would be pretty easy to build.

Anyway, there ya go. Some data!

[denise]

Aw, darn. Yeah, that's definitely not cost-effective -- alas and woe.

I'm pretty sure we do already batch the news post notifs separately from the regular comment notifs (send-email-mass vs send-email) -- I think it just gets overwhelmed. Ah well, there's always bug 4369; that will help a bit when we get it implemented.

(Now I'm wondering how useful it might be to build some kind of "campaign" tracking or email response metrics into our system. DON'T MIND ME I'M DREAMING OF MORE STATS TO ANALYZE)

[fu]

We are not running send-email-mass on anything at the moment!

[exor674]

Isn't the delay caused by OMG HOW MANY NOTIFICATIONS getting stuck into ESN, not the mail sender itself?

[pauamma]

Does that mean I might get my Bugzilla whine emails again? I kinda miss them.