4 ms·
4. Email delivery period. Using AWS Simple Email Service, you're actually sharing an email server IP address with other accounts. At times those accounts can
by camhart 6y ago
4. Email delivery period. Using AWS Simple Email Service, you're actually sharing an email server IP address with other accounts. At times those accounts can get the IP address added to spam lists. All the sudden your emails stop getting received on some clients.*
* Solution to this is to pay $$ / month to get a dedicated IP address, then never let it get added to a spam list.
- starbugs 6y agoWe ended up purchasing a dedicated IP from Mailgun. This solves the spam/latency problem mostly, but brings about new problems.
- albertgoeswoof 6y agoWhat other problems do you face with a dedicated IP?
- starbugs 6y agoYou have more management work for your team. If something's wrong with it, it's mostly your problem. I initially thought it was a "problem solved" thing by paying the money. Ended up causing us regular work (not much, but still).
- petercooper 6y agoNot MailGun, but we have 3 dedicated IPs with SendGrid and one problem is that there are spamlists and ISPs that block or mark down IP blocks owned by SendGrid so you get no real advantage from the dedicated IP. I wish you could "bring your own IP" to these services.
- jethro_tell 6y agoHeh, it would get tagged as a sendgrid ip after a few transactions.
- albertgoeswoof 6y agoDedicated IPs aren’t great because they’re completely untrusted. Better to sign up with a smaller email provider than mailgun/ses
- RulerOf 6y agoSES warms up dedicated IPs for several weeks by using them for regular SES traffic during the warmup phase: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/dedicated-ip-warming.html https://docs.aws.amazon.com/ses/latest/DeveloperGuide/dedica...
- sethammons 6y agoI work with Twilio SendGrid. What do you mean? IPs are the de facto way that reputation is tracked and a dedicated IP’s trust is based on your sending habits. How would a smaller provider be better? The only thing that I can think is similar IP ranges can also influence delivery, so you may want a dedicated range for transactional email. I don’t see smaller providers as able to do that.
- albertgoeswoof 6y agoA new dedicated IP is unknown and some providers will automatically treat it as untrusted and give it a lower score. A smaller email provider can give you a shared IP that has other users and is therefore already whitelisted. Provided the email provider has good anti-spam approaches (e.g. enforced DKIM verification), you should have better luck with that shared IP over a dedicated one if you only send a few thousand emails a month.
- sethammons 6y agoah, I see what you are saying. Better shared pool management by the larger senders would help, but a smaller sender should be able to more aggressively protect their shared IPs; I agree in principle. This is extra important for infrequent sending. I still contend that a dedicated IP is superior for deliverability reputation as long as you are sending enough email. For a brand new (to you) dedicated IP, it will need to be warmed up (gradually increase the amount of traffic it sends). There are automated and manual processes to accomplish that, including "pre-warmed" dedicated IPs that were previously in a "good enough" shared pool.
- iggldiggl 6y ago> 4. Email delivery period. Using AWS Simple Email Service, you're actually sharing an email server IP address with other accounts. They also randomly rotate through their mail servers on each retry attempt, so a simple Greylisting implementation based on matching the full IP address can delay your emails for not just one retry interval, but several (until by chance Amazon happens to reuse the IP of the original delivery attempt).