https://bugs.exim.org/show_bug.cgi?id=2143
Bjoern Jacke <bjoern@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
CC| |bjoern@???
--- Comment #7 from Bjoern Jacke <bjoern@???> ---
I also ran into this problem. This is highly unexpected and the problem doesn't
pops up most of the time because a comma ADN a non-ascii character, that
triggers RFC2047-encoded header line is relatively rare.
I understand that this is intended - but I'm reopening this bug because I
really think that such a case, where a raw header MUST be used (but isn't)
should actuall be checked at startup and at least a warning/hint should be
issued in the log file. This is a configuration trap which is just too well
hidden.
--
You are receiving this mail because:
You are on the CC list for the bug.
