Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Matthias A. <mat...@gm...>]

Am 20.11.2017 um 16:46 schrieb Ralph Corderoy:
> Hi Matthias,
>
>>> I used fetchmail 6.3.26-6
> ...
>>>     About to rewrite To: group-addr: ;, ra...@ex......
>>>     ...rewritten version is To: group-addr: ;@ruis.pair.com, ra...@ex....
>> Please file a proper report.
>> <http://www.fetchmail.info/fetchmail-FAQ.html#G3>
> No, sorry, you haven't made clear what's lacking and I've already spent
> too much time trying to find out how to report a bug;  that shouldn't be
> buried in the FAQ.
>
> It seems very likely from looking at fetchmail-6.3.26.tar.xz's
> rfc822.c's reply_hack() that this section kicks in erroneously.
>
> 	/*
> 	 * Not expanding on last non-WS == ';' deals with groupnames,
> 	 * an obscure misfeature described in sections
> 	 * 6.1, 6.2.6, and A.1.5 of the RFC822 standard.
> 	 */
> 	else if ((*from == ',' || HEADER_END(from))
> 		 && has_bare_name_part
> 		 && !has_host_part
> 		 && last_nws != ';')
> 	{
>     ...
> 	    *from++ = '@';
> 	    memcpy(from, host, hostlen);
> 	    from = p + hostlen + 1;
> 	    has_host_part = TRUE;
> 	}
>
> If there's useful data I can provide, let me know as fetchmail is
> currently corrupting modern, valid, emails that are in the wild;  not
> some exotic test case.
>
I need the configuration (including usernames but without passwords)
since that influences how rewriting happens and what code paths are run,
and the -vv verbose trace.
Please disregard the other message where I am asking for the message, I
have been able to extract the "offender" from the archive.