4 ms·
Ask HN: Amazon SES or alternatives for forwarding bulk email
Hi,
Have a situation where we are receiving email (could be anywhere from 500k - 1mln daily) and need to forward them to a third party parsing service. We would be forwarding these emails only to a single third party email address. We're currently using O365 and they only allow 10k outgoing messages per account per day. We would be setting up a subdomain specifically for this.
Does anyone have any experience with a similar situation? Any advice on a solution would be greatly appreciated. Asked about SES because the link below appears to be my use case but I'm not familiar with AWS services so including.
https://aws.amazon.com/blogs/messaging-and-targeting/forward-incoming-email-to-an-external-destination/
- QuinnyPig 6y agoFor that kind of volume and the fact that it's basically "set it and forget it" to a single recipient, I'd be tempted to slap a Postfix server into an auto-scaling group, configure the rules internally, validate with your AWS rep that you're not going to smack face-first into their port 25 limits, and call it a day. I hate running mailservers, but this is such a simple use case that I'd have a hard time dealing with the complexity of a new vendor relationship for such a direct use case.
- pythonthrowaway 6y agoThanks for the response. I agree completely that it's a simple use case but a good portion of our IT infrastructure is outsourced and we don't have anyone internally that could manage a mail server.
- yuppie_scum 6y agoAWS is pretty likely to consider that abuse, in my experience. If you can VPN or send on an alternate host to the third party, though..