

There's obviously something going on here - even CI's forums aren't beautifying the code!Īs I said, this is a very minor and esoteric bug.
X-Cloudmark-Analysis: v=1.0 c=1 a=f3KF1xABGwYA:10 a=zWdrAmO6HrYA:10 a=zlDW84ILT6cUjMvqIccA:9 a=HUOryjtR0cDrQyMghjxW2Gg72BkA:4 a=o9PM8HGNfBskj5mkJ4gA:9 a=D5SBOb9QXtBOQyXRaLgHPocyF2UA:4 The Outlook mail API supports the following actions on messages with MIME content: Send messages. Subject: =?utf-8?Q?Test_with_broken_attach?=Ĭontent-Type: multipart/alternative boundary="B_ALT_4a007a9d451eb"

Your email application may not support this format.Ĭontent-Type: multipart/alternative boundary="B_ALT_4a007a09caa96"Ĭontent-Transfer-Encoding: quoted-printableĪnd now, with the attachment removed for brevity - but the effect is the same if the path is valid. This is a multi-part message in MIME format. X-Cloudmark-Analysis: v=1.0 c=1 a=f3KF1xABGwYA:10 a=zWdrAmO6HrYA:10 a=zlDW84ILT6cUjMvqIccA:9 a=HUOryjtR0cDrQyMghjxW2Gg72BkA:4 Quote:Subject: =?utf-8?Q?Test_with_broken_attach?=Ĭontent-Type: multipart/mixed boundary="B_ATC_4a007a09cae72" OK, so here is a message with an attachment (where the attachment path is invalid and the programmer didn't spot the error.
