Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What is it that keeps Mailgun being passed from company to company like a hot potato?

Feel like I've had "oh here we go, incredible journey that needs me to reconfigure everything" a few times now

e: in fairness to Mailgun the most recent one I was thinking of (Pathwire) was a branding thing not a purchase



Yeah, the first thing that I thought when I opened the blog post and saw "Mailgun by Pathwire" was "wait, I thought this was Mailgun by Rackspace".

Apparently I'm way behind on the Mailgun ownership saga.


Well, it seems the actual deal is that Sinch is acquiring Pathwire. Mailgun is their biggest brand, but they also own Mailjet and Email on Acid.


I woild say different expectations from each acquisition, less profit and more overhead.


Trying to squeeze profits out of what should be a non profit (like Let's Encrypt, Quad 9, etc).


I’m afraid how much sensitive information transits through email services. Notably, all credentials to access accounts, and possible viruses. Maybe, after the buyer takes ownership, they realize the immense liability it is, and decide to get rid of it.


> all credentials to access accounts

What?


Proof of ownership of an email address is often used to prove ownership of an account on a third-party site.

Common examples are "forget password" workflows and Spotify/Slack's magic login link workflows.

If you own the transactional mail service through which all these flow, you are now responsible for the security of a large chunk of the Internet.


The same is true for services that offer "Login with Google" etc.

It's actually really bad that I can sign up with many services using a traditional email and password combo and the "Login with..." options work straight away. They really should be opt-in for security.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: