Re: [exim] Behaviour change in 4.83?

Top Page

Reply to this message
Author: Viktor Dukhovni
Date:  
To: exim-users
Subject: Re: [exim] Behaviour change in 4.83?
On Wed, Jul 30, 2014 at 05:26:22PM +0300, Lena@??? wrote:

> Something even more strange in my testing (FreeBSD, Exim 4.83 from ports):
>
> acl_check_mime:
>   warn logwrite = mime_content_type=$mime_content_type
>        logwrite = mime_filename=$mime_filename
>        decode = default
>        logwrite = mime_decoded_filename=$mime_decoded_filename

>
> Test message as received:
>
> ===========================================================================
> Message-ID: <20140730140329.GE786@???>
> Mime-Version: 1.0
> Content-Type: multipart/mixed; boundary="/2994txjAzEdQwm5"
> Content-Disposition: inline
> User-Agent: Mutt/1.4.2.3i
>
>
> --/2994txjAzEdQwm5
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
>
>
> --/2994txjAzEdQwm5
> Content-Type: application/zip
> Content-Disposition: attachment; filename="price.zip"
> Content-Transfer-Encoding: base64
>
> UEsDBBQAAgAIALKujDAkU6NQQBQAAABaAAAJAAAAcHJpY2UueGxz7VwJjCXXVb1VXb1vv/dl
> ===========================================================================


Does anything change if you add the final closing boundary string,
or was it there all along?

===========================================================================
Message-ID: <20140730140329.GE786@???>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="/2994txjAzEdQwm5"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i


--/2994txjAzEdQwm5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



--/2994txjAzEdQwm5
Content-Type: application/zip
Content-Disposition: attachment; filename="price.zip"
Content-Transfer-Encoding: base64

UEsDBBQAAgAIALKujDAkU6NQQBQAAABaAAAJAAAAcHJpY2UueGxz7VwJjCXXVb1VXb1vv/dl

--/2994txjAzEdQwm5--
===========================================================================

-- 
    Viktor.