[exim-dev] [Bug 385] New: Cannot add Content-Transfer-Encodi…

トップ ページ
このメッセージを削除
このメッセージに返信
著者: World Wide Web Owner
日付:  
To: exim-dev
題目: [exim-dev] [Bug 385] New: Cannot add Content-Transfer-Encoding header with extra_headers statement
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: ph10@???
        ReportedBy: mh+exim-bugzilla@???
         QAContact: exim-dev@???



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.