[exim-dev] [Bug 2805] New: valid message-id with [] on right…

Top Pagina
Delete this message
Reply to this message
Auteur: admin
Datum:  
Aan: exim-dev
Nieuwe Onderwerpen: [exim-dev] [Bug 2805] 4.95 ALPN callback returns protocol prefixed with length, [exim-dev] [Bug 2805] 4.95 ALPN callback returns protocol prefixed with length, [exim-dev] [Bug 2805] 4.95 ALPN callback returns protocol prefixed with length, [exim-dev] [Bug 2805] 4.95 ALPN callback returns protocol prefixed with length
Onderwerp: [exim-dev] [Bug 2805] New: valid message-id with [] on right side considered invalid
https://bugs.exim.org/show_bug.cgi?id=2805

            Bug ID: 2805
           Summary: valid message-id with [] on right side considered
                    invalid
           Product: Exim
           Version: N/A
          Hardware: x86
                OS: All
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Unfiled
          Assignee: unallocated@???
          Reporter: arekm@???
                CC: exim-dev@???


exim 4.92.4 doesn't consider 1234@[bar.] to be valid message-id

$ echo -e 'From: root\nMessage-ID: 1234@[bar.]\n\nhi\n' | exim -v root 2>&1 |
grep "<="
<= arekm@??? U=arekm P=local S=359

it isn't logged here as id=XYZ (while for example using "1234@bar" is logged
fine)

while https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.4 allows such
message-id

msg-id = [CFWS] “<” id-left “@” id-right “>” [CFWS]
id-right = dot-atom-text / no-fold-literal / obs-id-right
no-fold-literal = “[” *dtext “]”

dtext = %d33-90 / ; Printable US-ASCII
%d94-126 / ; characters not including
obs-dtext ; “[”, “]”, or “”



ps.
That also means that there is some kind of message-id validation in exim which
is interesting since there is request to add such validation (in a different
area) https://bugs.exim.org/show_bug.cgi?id=330

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