On 2020-05-21 19:28+0300, G. Miliotis via users wrote:
I use a dedicated mail server where all the effort for
deliverability, etc. goes . I have set up my web servers to send through it.
This has the benefit that you can centralize your outgoing spam filtering
(you do have that, yes?) and keep incoming mail flowing if the site is down.
I don't scan outbound mail. I don't intentionally let other people
control the content of outbound mail. I suppose I don't care about it
enough to have a dedicated instance.
You could I suppose say that a docker container is a dedicated instance,
depending how much you want to stretch it, or remove points of failure.
You may want to locate it in another continent to be really safe against
failures in London, but then you have more points for the webbys to hop.
So then you're back to putting a local queue on the webby that waits for
it's next hop to reanimate.
You can also use dedicated (paid) mail sending
services and send via SMTP
(you can configure your python or PHP for this - never trust CMS outgoing
Yes, but then you have another entity scanning the outbound mail
building a profile of the recipient </tinfoil>.
Also, for incoming mail through site contact forms you
can set up dedicated
mail accounts. This means your form mail never leaves your network to get
you blacklisted. You can do this trick without a dedicated mail server,
Yeah, I suppose. You could use those a docker container or an IP
namespace for a mail server if you really want to do that sort of thing.
Depends how much email the webby emits to which degree you want to
abstract the setup. For me, the past ten years (and more) have been just
fine with it all in one VM (except a MX that's elsewhere, almost a
duplicate of this setup but far slower on 1/8th the RAM).