#1 Parsing mime encoded From headers impossible

2.1.3
closed
opendkim (10)
5
2010-09-02
2010-09-02
Florian Sager
No

Hi,

I see log messages like
opendkim[6372]: A19F380132: can't parse From: header value `=?UTF-8?B?IldhbHRlciIgP...VuaWNhdGlvbi5jb20+?='

Is there any reason not to mime_decode these header fields before processing them?

Best regards,
Flo

Discussion

    • assigned_to: nobody --> cm-msk
     
  • A From: header field containing only that is not legal. See RFC2047 section 5.
    The <user@host> portion can't be encoded.

     
    • status: open --> pending
     
  • Florian Sager
    Florian Sager
    2010-09-02

    • status: pending --> closed
     
  • Florian Sager
    Florian Sager
    2010-09-02

    Thanks for this information, for those that may look for details:

    RFC2047, section 5:
    + An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'

    RFC822:
    addr-spec = local-part "@" domain ; global address