I've been using sympl for some time (started when it was called symbiosis), and I've always been happy with it. Russell On Thu, 2020-05-21 at 09:50 +0100, Anahata via users wrote:

I've been running a postfix mail server on my VPS for years, and use roundcube alongside it. The biggest issue with the big email providers seems to be ensuring the DNS is set up properly and setting up such things as SPF and DKIM. The workaround.org takes you through all this from the simplest principles On Wed, 27 Oct 2021 at 10:31, Ashley Norris <ashley(a)norris.org.au> wrote:

Hi Ashley, On Wed, Oct 27, 2021 at 08:19:13PM +1100, Ashley Norris wrote: If you're sending important transactional email like invoices and order receipts, or marketing mail, then I don't think those guides are exaggerating and it might be wise to use an email service provider. However, I/we do not use one and so I cannot give any recommendations. I would like to give an anti-recommendation of SendGrid, who in 2019 were acquired by Twilio. Since that time the amount of outright phishing mail and blatant spam that no one ever signed up for has exploded in volume and they don't seem to have any desire to stop taking money from those senders. However, despite my anti-recommendation SendGrid are used by some massive companies so their deliverability is likely to be high. I can only criticise them on a moral level, unfortunately. They are "too big to block" (like Google and MS). As regards sending mail from BitFolk infrastructure, I don't believe there is any particular problem compared to well-managed address space anywhere else. We work hard to deal with compromises swiftly and that keeps our entire netblocks from being singled out for blocking. These days, not having a bad reputation is sometimes not enough. Even having no reputation is sometimes an impediment to deliverability, and you can only get reputation by sending very large quantities of email, which is why I would tend to recommend an email service provider for email that really matters. If you're serious about sending/receiving email I'd recommend joining the "mailop" mailing lsit: https://www.mailop.org/ Linked on that page is "Best Practice for Servers" and that article goes through some of what you'll need to do to maximise your deliverability. You'll see it's quite a technical burden. Even more so if you have untrusted folk sending through you. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

On 2020-05-21 19:28+0300, G. Miliotis via users wrote: 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. Yes, but then you have another entity scanning the outbound mail building a profile of the recipient </tinfoil>. 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). Ed

On 2020-05-21 20:12+0100, Chris wrote: Maybe in the near-ish future if I replace this qmail setup with postfix. I wanted to workout how postfix did maps for a backup MX in a way that I'm happy with and doesn't stray too far from the comfort zone I'm in with qmail. Setting up one node seemed simple enough, but the backup MX had me a bit stumped. Don't worry, not asking for help, just making a public commitment to do something about it :) Ed