nanog mailing list archives
[NANOG] Re: Mailing list message headers
From: Joel Esler via NANOG <nanog () lists nanog org>
Date: Mon, 10 Mar 2025 07:14:41 -0400
I do not run the list, but I have extensive experience with mailman.. inline: — Sent from my 📱iPhone
On Mar 8, 2025, at 09:26, nanog--- via NANOG <nanog () lists nanog org> wrote: Something was up with the headers on this message delivering multiple copies to NANOG. Possibly Thunderbird inserted an extra CC to the list. /This/ message only has To: nanog () lists nanog org and should be delivered once. If so, nothing is wrong the list and it was my fault for not checking the CC header. I'm also seeing most but not all list messages with To: NANOG From: NANOG. To see who actually sent the message I have to check the message source as it's saved in X-MailFrom. Is this the new expected behaviour after the server upgrade?
This is expected based on configuration. If the list admins want the traffic to stay on the list, as a primary, which I recommend, then yes. It should send this way. The other way to configure mailman is to make the “to” the actual sender. The problem with that is, everyone on the list has to reply all. Otherwise, all responses go back to just the sender on reply. _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog () lists nanog org/message/5UY33VG3BSNNS6D5Z25TIOTK3IM3GGQG/
Current thread:
- [NANOG]Proposal for HENETIX: A Global IXP with High-Discounted Peering and Transit Services Volkan SALiH (Mar 02)
- [NANOG]Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Volkan SALiH (Mar 02)
- [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Tom Beecher (Mar 02)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Josh Luthman via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Christopher Hawker via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Josh Luthman via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Christopher Hawker via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Josh Luthman via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures nanog--- via NANOG (Mar 08)
- [NANOG] Mailing list message headers nanog--- via NANOG (Mar 08)
- [NANOG] Re: Mailing list message headers Joel Esler via NANOG (Mar 10)
- [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Tom Beecher (Mar 02)
- [NANOG]Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Volkan SALiH (Mar 02)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Volkan SALiH via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Tom Beecher via NANOG (Mar 03)
- Message not available
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Volkan SALiH via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Dave Hart via NANOG (Mar 05)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures TJ Trout via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Josh Luthman via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Re: Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures TJ Trout via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Randy Bush via NANOG (Mar 03)
- [NANOG] Re: [NANOG]Request to Reinstate Feeless BGP Sessions with Enhanced Security Measures Deepak Jain via NANOG (Mar 03)
