Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML MIMEMultipart issue #229

Open
dokime7 opened this issue Sep 2, 2022 · 2 comments
Open

HTML MIMEMultipart issue #229

dokime7 opened this issue Sep 2, 2022 · 2 comments

Comments

@dokime7
Copy link

dokime7 commented Sep 2, 2022

Hi again,

Sorry but I'm trying to increase at maximum the email deliverability :)

I can see on the code than the MIMEMultipart scafolding is well implemented but there is an issue for one case.
The case is when html is provided and no attachment.
In this line we are adding an 'alternative' part into a 'mixed' part but this 'mixed' part is not needed (only when attachments).
So Rspamd add the CTYPE_MIXED_BOGUS flag and decrease deliverability.

@theruziev
Copy link
Owner

Sorry but I didn't find any spec for changing mimetype from alternative to mixed.

Can you describe more information about it.

@dokime7
Copy link
Author

dokime7 commented Oct 4, 2022

No, it's no changing alternative to mixed, but removing mixed part in case of there is no attachment.
It is not clear on the spec but there is an example with Content-Type: multipart/alternative at the root of email headers.

There is an exemple of scafolding here where attachments are present, but when not, it seems that the mixed part is not needed, so we start directly with alternative part.

We can also read here that the mixed part is used only when attachments on Exchange Server.

Anyway, the purpose of this proposition is to inscrease deliverability by avoiding Rspamd bad score.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants