On 30/07/14 15:48, [email protected] wrote:
Does anything change if you add the final closing boundary string,
or was it there all along?
It was there:
===========================================================================
MCRTo1BAFAAAAFoAAAkAAAAAAAAAAAAgAAAAAAAAAHByaWNlLnhsc1BLBQYAAAAAAQABADcA
AABnFAAAAAA=
--/2994txjAzEdQwm5--
===========================================================================
I've had a look now. My test email _does_ have the attachments checked:
Content-Type: multipart/mixed; boundary=20cf305e24f5a9d46304ff6b08ac
<snip>
--20cf305e24f5a9d46304ff6b08ac
Content-Type: text/plain; charset=UTF-8
<snip>
--20cf305e24f5a9d46304ff6b08ac
Content-Type: image/x-icon; name="test.ico"
Content-Disposition: attachment; filename="test.ico"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_hy8tq4p90
<snip>
--20cf305e24f5a9d46304ff6b08ac
Content-Type: application/zip; name="test.zip"
Content-Disposition: attachment; filename="test.zip"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_hy8tq4qi1
<snip>
--20cf305e24f5a9d46304ff6b08ac--
Another email does _not_
Content-Type: multipart/mixed;
boundary="------------305540313793879511083040"
This is a multi-part message in MIME format.
--------------305540313793879511083040
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<snip>
--------------305540313793879511083040
Content-Type: application/octet-stream;
name="663511-30.07.2014.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="663511-30.07.2014.zip"
<snip>
--------------305540313793879511083040--
I'm afraid I don't know what the correct/acceptable format is but ask
for more if I've snipped too much. I also don't know if this is a
change in 4.83 as I only increased my logging when I noticed some junk
not being handled properly after upgrading.
George.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
