2017-06-23 00:42:47 UTC
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
This posting was sent by OmniMix 2.4.6 (exit dizum =>
***@m2n.mixmin.net) including the headers
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
***@dizum.com and ***@m2n.mixmin.net 'normalize' comma
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug