Hi,
I wrote:
I've triggered it myself at pair.com. An empty group address isn't
sufficient; it needs to be followed by another address. Still
perfectly valid under RFC 2822.
Tx'd: To: group-name: ;, ralph(_at_)example(_dot_)com
Rx'd: To: group-name: ;, ""@ruis.pair.com, ralph(_at_)example(_dot_)com
I'll tell them.
Before I did that, I went to gather more evidence and it wasn't pair.com
at fault. I've tracked it down to fetchmail 6.3.26-6 and I've emailed
fetchmail-users(_at_)lists(_dot_)sourceforge(_dot_)net, though it hasn't
appeared at
their archive yet.
https://sourceforge.net/p/fetchmail/mailman/fetchmail-users/?viewmonth=201711
Manually inspecting the remote mailbox showed no corruption, fetchmail's
verbose output showed
About to rewrite To: group-addr: ;, ralph(_at_)example(_dot_)com...
...rewritten version is To: group-addr: ;@ruis.pair.com,
ralph(_at_)example(_dot_)com.
Others also seeing corruption might want to do similar to narrow down
the culprit in their case. If you need to point others at Ken's
original, it can be seen with
$ curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
> sed -n '/Sat Nov 18 19:42:55 2017/,/^To:/p' |
> sed -n '$p'
To: nmh-announce: ;, nmh-workers(_at_)nongnu(_dot_)org
$
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers