Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How not to migrate an email domain

simianlogic.com

Post reply on HN
Print view View original

21–30 of 30 posts

Re: How not to migrate an email domain

#21

Post by kureikain »

We gotta give Mailgun some empathy here. It's tough to run an email service and keep reputation of it. If some bad actor got in, they can send large spam email and dilute the reputation.

Of course, this is just a mistake and after explaining Mailgun shouldn't charge $1358 for clean service. But as a customer, you should take some responsibility when doing something wrong as well. For example, if the account is old, and this is the first time this happen, and once we explain the mistake, Mailgun should waive that fee.

On AWS SES if the bounce rate >10%, your account is temporarily suspended.

If the exact samething happen with any mail provider, where a large of emails volume are bounced. They would need to pause/restrict your account in some way.

I would suggest look into AWS SES and started to write code to handle bounce email yourself to get a sense of it.

Re: How not to migrate an email domain

#22

Post by dddw »

> I don't know yet whether Postmark will be any better, but I like the product so far and they seem to be a lot more customer-focused. Fingers crossed!

Postmark is definitely better in my experience with multiple customers. They actually check the delivery to different big mailproviders like gmail.

The support I had there was also quick and helpful.

It is definitely pricier, but should spare a couple of headaches if email is vital to your business.

Re: How not to migrate an email domain

#25

Post by SimianLogic »

TedDoesntTalk wrote: post #23

> I stopped the ToS email with around 70k more users to send I don’t want emails about changing to your ToS

Cool, email support@intromaker.com from your account email and I'll delete you. (Which is the same offer I made to everyone else in lieu of an unsubscribe button.)

I did weigh whether to send a notice or not, and for me it came down to emotion more than economics. My thinking:

It'll end up costing a few hundred dollars to send it out. A lot of users have probably forgotten what IntroCave is or don't need it any more, and hopefully they'll request account deletion (hundreds of people did). I expected to generate approximately $0 in sales from the email, but if I can save even a handful of users from typing in the old domain, getting redirected to the new domain, wondering WTF, and bouncing -- that seemed worth it.

Re: How not to migrate an email domain

#27

Post by oriki »

Aachen wrote: post #26

Noob here (with his own mail server so I'm not familiar with these kinds of issues). What's the problem with a bounce? You pay for the delivery attempt anyway I assume, why do they care?

Mostly to do with making sure their service isn't being used for spam, to protect reputation. Bad reputation can mean blacklisting which is a bad time when your service is centralized on emails.

Re: How not to migrate an email domain

#28

Post by stavros »

jabroni_salad wrote: post #5
cmeacham98 wrote: post #3

Earlier quoted context omitted.

Surprised this isn't at least account wide or maybe even global for all users? Are there really email services that bounce (not send to spam, but bounce) email based on domain? (Assuming you have SPF and DKIM and reverse DNS and whatever else configured correctly, which I assume you must to be able to use Mailjet?)

Yes, your domain can end up on a blacklist such as SORBS or Spamhaus and then you will have deliverability issues across the board. I have also heard from many companies and individuals with personal domains that have difficulty with Gmail and the verizon/aol/yahoo postmaster. They will just bounce you out of the blue. DMARC and friends only help with authenticity. There's plenty of fraudsters sending authentic spam…

This is all true, but I don't understand why email providers will bounce personal domains. If you run DMARC and your domain is years old, what's the issue? I imagine that reduces the risk of spam by a lot.

Re: How not to migrate an email domain

#29

Post by [deleted] »

kureikain wrote: post #21

We gotta give Mailgun some empathy here. It's tough to run an email service and keep reputation of it. If some bad actor got in, they can send large spam email and dilute the reputation. Of course, this is just a mistake and after explaining Mailgun shouldn't charge $1358 for clean service. But as a customer, you should take some responsibility when doing something wrong as well. For example, if the account is old, a…

[deleted]

Re: How not to migrate an email domain

#30

Post by Aachen »

oriki wrote: post #27
Aachen wrote: post #26

Noob here (with his own mail server so I'm not familiar with these kinds of issues). What's the problem with a bounce? You pay for the delivery attempt anyway I assume, why do they care?

Mostly to do with making sure their service isn't being used for spam, to protect reputation. Bad reputation can mean blacklisting which is a bad time when your service is centralized on emails.

Sure, but how would allowing bounces lead to being used for spam? If it bounces, that means the mail was not delivered. Why are these errors bad for a reputation? It doesn't even matter whether the mail was spam or not, since it wasn't delivered anyway. That's what I don't get, of course I know they're trying to keep their reputation good.
Post reply on HN