BAD HEADER SECTION, MIME error: part did not end with expected boundary; error: unexpected end of parts before epilogue

[par]

All email notification from this forum are missing the ending MIME marker which results in the message from Amavis in the title(and the SPAM folder in my case). Is this another thing broken by Amazon SES or something that can be fixed by a simple config change somewhere?

 

Edit: It seems Amazon SES is aware of the need to include the ending marker. From an example in their docs - https://docs.aws.amazon.com/ses/latest/dg/event-publishing-send-email.html

 

Quote

X-SES-MESSAGE-TAGS: tagName1=tagValue1, tagName2=tagValue2
X-SES-CONFIGURATION-SET: myConfigurationSet
From: sender@example.com
To: recipient@example.com
Subject: Subject
Content-Type: multipart/alternative;
    boundary="----=_boundary"

------=_boundary
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

body
------=_boundary
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

body
------=_boundary--    

The last line is always missing ;(

Edited May 23, 2021 at 07:24 PM by par

[Shmuel Gerber]

Testing this for myself.

[Shmuel Gerber]

One more time.

[Shmuel Gerber]

2 hours ago, par said:

All email notification from this forum are missing the ending MIME marker which results in the message from Amavis in the title(and the SPAM folder in my case). Is this another thing broken by Amazon SES or something that can be fixed by a simple config change somewhere?

 

Edit: It seems Amazon SES is aware of the need to include the ending marker. From an example in their docs - https://docs.aws.amazon.com/ses/latest/dg/event-publishing-send-email.html

 

The last line is always missing ;(

Thank you for the report; I've put in a request to technical support for Invision Community Services.

In the meantime, you may be able to bypass the problem on your end by doing something like what is shown on this page:

https://www.danami.com/clients/knowledgebase/112/How-can-I-disable-Amavis-bad-header-tests.html?language=english

[par]

Thank you for verifying. I will keep an eye on my SPAM folder while this is being investigated.

[Shmuel Gerber]

One more time.

[Shmuel Gerber]

On 5/23/2021 at 11:12 PM, par said:

Thank you for verifying. I will keep an eye on my SPAM folder while this is being investigated.

Invision has made a change so that the closing boundary marker should be included in emails. @par please reply here with whether this has solved the problem for you.

[par]

@Shmuel Gerber

Haven't gotten anything. Please trigger something. I hope I am not shadow banned

[par]

Yeah, it works. The only issue at this point is unnecessary base64 encoding:

 

From: =?UTF-8?B?VGhlIE9mZmljaWFsIFJPTlIgUSAmIEEgRm9ydW1z?= <noreply@invisioncloudcommunity.com>
Subject: =?UTF-8?B?U2Vjb25kcy4=?=

 

Edited June 30, 2021 at 05:15 AM by par

[Shmuel Gerber]

On 6/30/2021 at 1:04 AM, par said:

Yeah, it works. The only issue at this point is unnecessary base64 encoding:

 

From: =?UTF-8?B?VGhlIE9mZmljaWFsIFJPTlIgUSAmIEEgRm9ydW1z?= <noreply@invisioncloudcommunity.com>
Subject: =?UTF-8?B?U2Vjb25kcy4=?=

 

Is this actually an issue that is causing any problems?

[par]

On 7/3/2021 at 7:25 PM, Shmuel Gerber said:

Is this actually an issue that is causing any problems?

Not really, it is just unnecessary.