Hi, On Fri, May 10, 2019 at 02:44:05PM +0000, Gert Doering wrote: > this mail was intentionally sent without a message-id
So - if you send mail to the openvpn-devel list, and your MTA either
omits the "message-id:" header or mangles it in funky ways, Sourceforge
will add a new message-id (required by RFC822 and successors) *but*
seems to do this at a point in the processing where their MTA sees
multiple individual mails (one per receipient?) and the message-id:
seen at the receiving end is no longer unique.
This particular mail ended up with at least these message IDs...
<[email protected]>
<[email protected]>
<[email protected]>
(so it's clear that it wasn't done by "something close to the receipient",
but somewhere in the sourceforge mailing list system)
Long story cut short: I'll check patches for such message-IDs in future,
and ask for re-sending from a less broken sending MTA.
(I'm not going to discuss this with SF - it would be way easier to just
migrate the list away than find someone there who would understand and
fix that)
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
