Hi all!
Disclaimer:
I'm not an B4x user so please apologize if the following post is not a bug or unrelated to B4x.
The case:
The amavisd content filter on my systems banned a multipart email with a boundary "asdasdwdwqd__HV_qwdqwdddwq".
The error message given by amavisd was:
"BAD HEADER SECTION, MIME error: error: part did not end with expected boundary; ; error: unexpected end of parts before epilogue"
Attached on this post there is an extract of the mail message with only relevant content.
Looking at the message I verified that amavisd was right, the last MIME multipart boundary expected from the standard (https://tools.ietf.org/html/rfc2046) was missing.
The boundary "asdasdwdwqd__HV_qwdqwdddwq" look like a bunch of chars typed by a developer's two finger so I thought the mail was generated by a framework.
Searching the boundary string to google I've found only B4x related results so I supposed this is that framework.
Please, fix the Email sending component to conform MIME standard or ignore this message if not related to it.
Regards,
Daniele
Disclaimer:
I'm not an B4x user so please apologize if the following post is not a bug or unrelated to B4x.
The case:
The amavisd content filter on my systems banned a multipart email with a boundary "asdasdwdwqd__HV_qwdqwdddwq".
The error message given by amavisd was:
"BAD HEADER SECTION, MIME error: error: part did not end with expected boundary; ; error: unexpected end of parts before epilogue"
Attached on this post there is an extract of the mail message with only relevant content.
Looking at the message I verified that amavisd was right, the last MIME multipart boundary expected from the standard (https://tools.ietf.org/html/rfc2046) was missing.
The boundary "asdasdwdwqd__HV_qwdqwdddwq" look like a bunch of chars typed by a developer's two finger so I thought the mail was generated by a framework.
Searching the boundary string to google I've found only B4x related results so I supposed this is that framework.
Please, fix the Email sending component to conform MIME standard or ignore this message if not related to it.
Regards,
Daniele
