4 ms·

I think you have it backwards though. if you use a big player like AWS or Azure or GCP, you can be pretty sure your mail will get to inbox and not in the spam f

I think you have it backwards though. if you use a big player like AWS or Azure or GCP, you can be pretty sure your mail will get to inbox and not in the spam folder, not the other way around I think. DIY is a little harder

danpalmer 6y ago
I think the previous comment was potentially more correct. Typically for low volume sending it doesn't matter. For high-volume sending you need to get the IPs, domains, and security controls set up correctly to reduce how much you're seen as spam. AWS SES will allow you to configure this all, but you need to know how. Something like SendGrid (not a small player) will be more expensive, but will provide usability features on top and guide you through that setup of that solid foundation a little more. Ultimately the reputation comes down to the organisation authoring the email (not the email service provider), as they are the ones doing well or badly on the quality of the email they send.
elif 6y ago
Not true. Inbox placement requires vigilance and monitoring of every user on your IP. AWS is so mixed that is an intractable problem.
- john-shaffer 6y ago
  You can "bring your own IP" or lease a dedicated IP address for $25/month. I'm not sure how effective it is, but the option is there.
  - deleted 6y ago
    [deleted]
  - macNchz 6y ago
    If you're sending a lot of email every day, having dedicated IPs is an important piece of owning your sender reputation. A shared IP is only as good as the email service provider's ability to prevent people from sending spam on their platform. In a system full of black boxes that can have sudden and hard to fix impacts on your business if you rely a lot on email, eliminating one black box (the behavior of other customers on your shared IP) can be a huge risk reduction.
    - pbhjpbhj 6y ago
      In the past our domain was blocked by one of the top free email providers - we sent about 1 email per day at the time - because we sent email from an IP owned by a hosting provider who also owned another IP that in the past had sent spam. That was the reason given. Whitelisting and adding as a contact didn't allow us to even receive emails from ourselves, to our own email address (over a decade old at the time) with that provider. Our _domain_ has never had spam sent from it, never appeared in a blacklist, and the IP address itself was clean. So yes, own the IP [and do all the regular SPF, DKIM and such], but be aware that is possibly nowhere near enough.

danpalmer 6y ago

I think the previous comment was potentially more correct. Typically for low volume sending it doesn't matter. For high-volume sending you need to get the IPs, domains, and security controls set up correctly to reduce how much you're seen as spam. AWS SES will allow you to configure this all, but you need to know how. Something like SendGrid (not a small player) will be more expensive, but will provide usability features on top and guide you through that setup of that solid foundation a little more. Ultimately the reputation comes down to the organisation authoring the email (not the email service provider), as they are the ones doing well or badly on the quality of the email they send.

elif 6y ago

Not true. Inbox placement requires vigilance and monitoring of every user on your IP. AWS is so mixed that is an intractable problem.

john-shaffer 6y ago
You can "bring your own IP" or lease a dedicated IP address for $25/month. I'm not sure how effective it is, but the option is there.
- deleted 6y ago
  [deleted]
- macNchz 6y ago
  If you're sending a lot of email every day, having dedicated IPs is an important piece of owning your sender reputation. A shared IP is only as good as the email service provider's ability to prevent people from sending spam on their platform. In a system full of black boxes that can have sudden and hard to fix impacts on your business if you rely a lot on email, eliminating one black box (the behavior of other customers on your shared IP) can be a huge risk reduction.
  - pbhjpbhj 6y ago
    In the past our domain was blocked by one of the top free email providers - we sent about 1 email per day at the time - because we sent email from an IP owned by a hosting provider who also owned another IP that in the past had sent spam. That was the reason given. Whitelisting and adding as a contact didn't allow us to even receive emails from ourselves, to our own email address (over a decade old at the time) with that provider. Our _domain_ has never had spam sent from it, never appeared in a blacklist, and the IP address itself was clean. So yes, own the IP [and do all the regular SPF, DKIM and such], but be aware that is possibly nowhere near enough.