Brian asked:
Did anyone get this message?
I didn't. ;->
(Thanks, Brian. How are you enjoying Mailman3?)
On Wed, Mar 02, 2022 at 09:12:29PM -0800, Rick Moen wrote:
Brian asked:
Did anyone get this message?
I didn't. ;->
(Thanks, Brian. How are you enjoying Mailman3?)
Mailman 3 seems to have taken more effort than Mailman 2.
Granted, I configured Mailman 3 for Exim. I stumbled on the lmtp configuration portion. I didn't realize that for lmtp, that exim acts as a client to connect to Mailamn that is listening on the port. Fortunately, the guys on the Debian-exim list clarified that. Second, I missed a configuration setting that indicated Exim in mailman3.cfg. The mailman docs for Debian pretty much just point you to the Exim docs. Most other packages auto configure things. Third, I had an issue with getting Hyperkitty to archive. For some reason, I didn't get an API key configured.
I still need to configure reverse dns on the server and probably do some dmarc or dkim configuration. Plus, I would like to configure the list so that it says lists.saclug.org, or something like that. But hey, we are back with "a list".
Brian
Quoting Brian E. Lavender (brian@brie.com):
Mailman 3 seems to have taken more effort than Mailman 2.
Well done. I'm not surprised to hear that it was a bit of a bear.
I still need to configure reverse dns on the server and probably do some dmarc or dkim configuration.
You definitely need rDNS. Many SMTP sites de-facto penalise sending hosts that lack rDNS -- and some even penalise ones with generic-seeming rDNS -- despite that not being an RFC mandate.
You're probably aware of this, but there are RFC mandates for:
o must accept mail to abuse@ o must accept mail to postmaster@ o must accept mail from the null sender
On DKIM/DMARC, you might already be aware of my view of those standards from the Firm Formerly Known as Yahoo:
:r! dig -t txt _dmarc.linuxmafia.com +short "DMARC: tragically misdesigned since 2012. Check our SPF RR, instead."
-
Brian E. Lavender -
Rick Moen