3 ms·
> This stack was created out of frustration due to the fact that to this day there's no easy way to have a full email server without the overhead of installing
by alfiedotwtf 6y ago
> This stack was created out of frustration due to the fact that to this day there's no easy way to have a full email server without the overhead of installing and configuring all servers needed to handle incoming and outgoing messages.
Looking at diagram, I'm not sure Postfix + Cyrus is more complicated than what you've got here.
Congrats though, I'm sure this will help a lot of people wanting to manage mail themselves. Just not sure how you're going to get mail accepted by others from constantly changing (and possibly blacklisted) Amazon IPs without using trusted smart hosts.
- goodpoint 6y agoYou spotted the issue: maintaining a mailer requires constant monitoring of blocklists and contacting the list owners to be unblocked. It required a fixed ipaddr and takes months to gain trust. Using random AWS IP addresses is a lost cause.
- xenophonf 6y ago> Just not sure how you're going to get mail accepted by others from constantly changing (and possibly blacklisted) Amazon IPs without using trusted smart hosts. Are you thinking about EC2 public IP addresses here? That service uses a different IP range than SES, which you can verify by comparing https://ip-ranges.amazonaws.com/ip-ranges.json https://ip-ranges.amazonaws.com/ip-ranges.json to `dig amazonses.com TXT`. In my experience, we haven't had any issues with SES emails getting blocked, but you must set up DMARC properly and respond to bounces quickly.