Work on mail.haskell.org beginning, please report any problems

Hello Haskellers, Beginning today, I am upgrading our Postfix installation on mail.haskell.org, and introducing some new options to reduce the amount of spam that hits our mailman server. If you experience delivery problems, or any bounced mail, please send a copy of the full bounce message to my address: jwiegley@gmail.com. I'll be making more changes gradually over the next few days, and watching the mail logs, but it's possible that mail accepted before will suddenly start getting rejected, depending on how well-behaved your sending mail server is. Activities planned for this Christmas break are: - [x] Upgrade Postfix to 2.11 - [X] Enable postscreen for pre-queue RBL filtering - [ ] DKIM sign messages sent from mailman - [ ] Implement DMARC policy (i.e., reject incoming messages improperly DKIM signed, or failing SPF check) - [ ] Prevent mail being spoofed from haskell.org addresses - [ ] Tighten sender and recipient restrictions - [ ] Re-assess inbound and outbound rate limits - [ ] Use SpamAssassin for post-queue filtering - [ ] If helpful, enable deep protocol pre-filtering - [ ] Document all the above, so others can help with e-mail admin Thank you, John Wiegley Haskell.org, infrastructure team

On Dec 22, 2016, at 11:55 AM, John Wiegley
wrote: - [x] Upgrade Postfix to 2.11
If available as a package for your O/S, might as well use 3.1
- [X] Enable postscreen for pre-queue RBL filtering
This makes it possible to combine multiple lower-weight RBLs, that individually are not sufficient to reject mail, but you should still use the SpamHaus zen RBL in smtpd(8).
- [ ] DKIM sign messages sent from mailman
Fair enough.
- [ ] Implement DMARC policy (i.e., reject incoming messages improperly DKIM signed, or failing SPF check)
DO NOT DO THIS! DMARC is an abomination, abused by Yahoo and others to shift costs onto others. The right thing to do with DMARC is to avoid modifying the message headers (no subject tags) and body (no footers). This way relayed posts pass DKIM checks. [ See e.g. perma-thread playing out on ietf@ietf.org at the moment. ] We can ask list subscribers to add the [Haskell-cafe] tag to the first message in each new thread, so that the list can avoid the need to modify the message in transit (beyond adding List- headers, a Sender- header and setting an appropriate envelope sender).
- [ ] Use SpamAssassin for post-queue filtering - [ ] If helpful, enable deep protocol pre-filtering
Deep protocol tests in "postscreen" have proved difficult to use, too many large providers don't retry messages from a stable IP address, and whitelisting their ever-changing address blocks is challenging. -- Viktor.

Am 22.12.2016 um 17:55 schrieb John Wiegley:
- [ ] Implement DMARC policy (i.e., reject incoming messages improperly DKIM signed, or failing SPF check)
I would be unable to send mail, because my mail installation is a bit old and would not pass either check (probably). This would be the first mailing list to have this problem for me.
participants (3)
-
Joachim Durchholz
-
John Wiegley
-
Viktor Dukhovni