http://www.exim.org/bugzilla/show_bug.cgi?id=385
Summary: Cannot add Content-Transfer-Encoding header with
extra_headers statement
Product: Exim
Version: 4.62
Platform: All
OS/Version: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Filters
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [email protected]
Hi,
In a personal filter, I have a mail statement with an extra_headers option
allowing the use of German Umlauts:
extra_headers "Mime-Version: 1.0\nContent-Type: text/plain;
charset=iso-8859-1\nContent-Transfer-Encoding: 8bit"
This is rejected with the error message:
Filter error: \n not followed by space or valid header name in "Mime-Version:
1.0\nContent-Type: text/plain; charset=iso-8859-1\nContent-Transfer-Encoding:
8bit" in mail command
When I change Content-Transfer-Encoding to Content-TransferEncoding, omitting
the second dash, debugging shows that these headers would indeed be added.
This looks to me like exim doesn't consider a Header name with two dashes
valid. Am I doing something wrong?
Greetings
Marc
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details
at http://www.exim.org/ ##
