[exim-dev] [Bug 2843] New: wishlist for method to correctly …

Top Pagina
Delete this message
Reply to this message
Auteur: admin
Datum:  
Aan: exim-dev
Onderwerp: [exim-dev] [Bug 2843] New: wishlist for method to correctly create valid headers like SomeHeader:${format_header: .....}
https://bugs.exim.org/show_bug.cgi?id=2843

            Bug ID: 2843
           Summary: wishlist for method to correctly create valid headers
                    like SomeHeader:${format_header: .....}
           Product: Exim
           Version: 4.95
          Hardware: All
                OS: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: String expansion
          Assignee: unallocated@???
          Reporter: arekm@???
                CC: exim-dev@???


This is feature request about adding feature (string expansion) for creating
proper headers based on other data. That will handle correctly folding, new
lines, length etc.

Use case, probably there are other, too:

There is bounce_message_file feature in exim. It allows generating own bounce
messages. Unfortunately this file needs to be perfect since exim doesn't do any
validation or normalization of data there.

So that file contains:

Subject: Mail delivery failed${if eq{$sender_address}{$bounce_recipient}{:
returning message to sender}}

now we want to add original subject inside this one

Subject: Mail delivery failed${if eq{$sender_address}{$bounce_recipient}{:
returning message to sender}}: $h_subject:

That won't get correct results since original subject can be long, can be
folded etc.

So some:

Subject:${format_header:Mail delivery failed${if
eq{$sender_address}{$bounce_recipient}{: returning message to sender}}:
$h_subject:
}

would be nice.


ps. right now using

Subject: Mail delivery failed${if eq{$sender_address}{$bounce_recipient}{:
returning message to sender}}: ${sg{$h_subject:}{^(.\{50\})..*\\s\$}{\$1
[...]}}

so truncating (since it's hard to do folding here correctly with what exim
currently offers) which is not optimal but (I hope) correct and safe enough.

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