3 ms·
I do two things: 1. Send mail via a static IP (that I pay extra for) 2. Send all mail through a reputable 'smarthost' (mine is provided by my ISP as part of t
by Jaruzel 7y ago
I do two things:
1. Send mail via a static IP (that I pay extra for)
2. Send all mail through a reputable 'smarthost' (mine is provided by my ISP as part of the 'business' package).
This fixes all sending mail problems. For extra fairy-dust, I added SPF records to my mail server IP.
The BIG problem is Spam. Unless you pay for an intermediary spam filtering service, you will NEVER be on top of it. After self-hosting my own mail system for decades, I am now seriously planning a migration to Office 365.
- huhtenberg 7y ago> The BIG problem is Spam. YMMV, but a combination of graylisting, RBL and "sender address valiation" tends to drop inbound spam rate to nearly zero.
- Jaruzel 7y agoI'm currently hosting a spamassassin instance, and route incoming mail via that, however a lot still gets through :(
- wpietri 7y agoI'm using SA as well; it's fine for me. My big trick is to route a bunch of stuff right into the spam training system. E.g., when a tagged address I've given out is compromised, that goes right to training. The same goes for spam to random names: also right to SA spam training. My theory here is that statistically, by the time a spammer tries to send one to an active address, they're likely to have already fed things into the trainer, often multiple times.