[DUAS] Email formatting issue for emails sent via $U Alerting Rules and/or Uproc Email Notifications
Article ID: 204093
Updated On:
Products
Issue/Introduction
Sometimes the E-mail sent via $U are not accepted by the SMTP server due to RFC violation :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We read the headers and noticed this: “X-Amavis-Alert: BAD HEADER SECTION, MIME error: error: part did not end with expected boundary” which seems to indicate the that email does not respect the RFC.
This error message seems to indicate that the boundary is either incorrect or not present at all.
Here is an example of how it should work:
· The content type is defined in the header, so you can know how to interpret the email:
Content-Type: multipart/alternative; boundary="----=_NexPart_000"
· The message is “multipart”. To know what needs to be displayed (ex : text or html part), each part of the message present in the body is defined by the boundary ------=_NexPart_000
------=_NexPart_000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
<base 64>
------=_NexPart_000
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
<html>
Note: Your email will show the the text/html part if you've selected html display and text/plain if you've selcted text display.
· At the end of the message, it must be indicated that the body is finished, the boundary is specified again followed by two dashes at the end:
------=_NexPart_000--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment
Release : 6.10
Component : DOLLAR UNIVERSE
Cause
Depending on the SMTP server, the BOUNDARY_ENCODING setting must be adapted : instead of "Q", the value "quoted-printable" must be set.
Related doc :
https://docs.automic.com/documentation/webhelp/english/ALL/components/DU_AS/latest/%20%20Dollar%20Universe%20Guides/help.htm#UVCHelp/nodesettingssmtp.htm
Resolution
Feedback
