Re: [exim] mime_filename and &# encoding

Top Page
Delete this message
Reply to this message
Author: Lena
Date:  
To: exim-users
Subject: Re: [exim] mime_filename and &# encoding
> From: Jamie <jamie@???>

> deny message = Blacklisted file extension detected
>    condition = ${if match \
>                     {${lc:$mime_filename}} \
>                     {\N(\.exe|\.pif|\.bat|\.scr|\.lnk|\.com|\.zip)$\N} \
>                  {1}{0}}

>
> It has hugely reduced the amount of spam, but they have suddenly worked
> around it by sending documents with an attachment name of "& # 1057 ;
> opy_of_document_SER176.zip" (without spaces)


How the full header of the MIME part looks undecoded? Use the
"view source" function of your MUA, like perhaps Ctrl-U in Thunderbird,
e in Mutt, Ctrl-F3 in Outlook Express. Base64-encoded filenames
like this example should be decoded correctly:

------=_NextPart_000_0460_01CB8725.B9B27090
Content-Type: application/msword;
        name="=?windows-1251?B?6u8g/evl6vLw7uT7LmRvYw==?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
        filename="=?windows-1251?B?6u8g/evl6vLw7uT7LmRvYw==?="