[exim-dev] [Bug 2804] New: Header lines are not unfolded cor…

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: admin
Ημερομηνία:  
Προς: exim-dev
Καινούρια Θέματα: [exim-dev] [Bug 2804] $header_<name> cannot distinguish multiple headers from multiline headers, [exim-dev] [Bug 2804] $header_<name> cannot distinguish multiple headers from multiline headers
Αντικείμενο: [exim-dev] [Bug 2804] New: Header lines are not unfolded correctly
https://bugs.exim.org/show_bug.cgi?id=2804

            Bug ID: 2804
           Summary: Header lines are not unfolded correctly
           Product: Exim
           Version: 4.94
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: String expansion
          Assignee: unallocated@???
          Reporter: bugzilla.exim.simon@???
                CC: exim-dev@???


According to RFC2822, additional newlines should be removed when unfolding
header lines.

Exim is not doing this which means that comparing $h_Subject: (which is
supposed to be what the MUA displays) in a filter is unnecessarily difficult.

$ git log -1
commit 6b69b71028f15c7ba3157bac955103b764326f60 (HEAD -> master, tag:
exim-4.95-RC2, origin/master, origin/HEAD)

$ cat filter
# Exim filter
if $h_Subject: begin "test1 test2" then
        seen
        finish
endif


$ cat test.email
Subject: test1
test2 test3

$ src/build-Linux-x86_64/exim -C /dev/null -bf filter < test.email
Testing Exim filter file "filter"
Filtering did not set up a significant delivery.
Normal delivery will occur.

$ cat test.email2
Subject: test1 test2 test3

$ src/build-Linux-x86_64/exim -C /dev/null -bf filter < test.email2
Testing Exim filter file "filter"
Seen finish
Filtering set up at least one significant delivery or other action.
No other deliveries will occur.


Both of these test emails should behave the same.

Extra logging shows that $h_Subject: has an embedded "\n" in this scenario.

--
You are receiving this mail because:
You are on the CC list for the bug.