Re: [exim] raw mime_filename

Top Page
Delete this message
Reply to this message
Author: Mikhail Golub
Date:  
To: exim-users
Subject: Re: [exim] raw mime_filename

I have email message:
Content-Description: Elinta Charge CityCharge WiFi configuration.pdf
Content-Disposition: attachment;
    filename="Elinta Charge CityCharge WiFi configuration.pdf"; size=548769;


In exim config (acl_smtp_mime):
     logwrite = TEST: mime_filename="$mime_filename"\
         ${if and { \
             {def:mime_content_description} \
             {!match{$mime_content_description}{(?i)^=\?utf-8}} \
             {match{$mime_content_description}{^=\?}} \
         } \
         {, mime_content_description="$mime_content_description", \
         ${rfc2047d:$mime_content_description}}}




I got this:
TEST: mime_filename="Elinta Charge CityCharge WiFi configuration.pdf",
mime_content_description="elintachargecitychargewificonfiguration.pdf",
elintachargecitychargewificonfiguration.pdf

Why mime_content_description not does not match header
"Content-Description" in letter?

In documentation:
"$mime_content_description
     This variable contains the normalized content of the 
Content-Description: header. It can contain a human-readable description 
of the parts content. Some implementations repeat the filename for 
attachments here, but they are usually only used for display purposes."


What is meant by "normalized content"?


On 13.10.2022 22:55, Jeremy Harris via Exim-users wrote:
> On 13/10/2022 20:41, Mikhail Golub via Exim-users wrote:
>> Content-Disposition: attachment;
>>      filename="=?windows-1251?B?wevg7eog7/Du7+7n6Pazvy5kb2N4?="; size=48777;
>
> Here:           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>>      creation-date="Wed, 25 Aug 2021 08:33:00 GMT";
>>      modification-date="Thu, 13 Oct 2022 07:06:59 GMT"
>