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

[12.0] mail_tracking: SpamAssassin flag 'RAND_MKTG_HEADER' #701

Closed
JorgeQuinteros opened this issue Apr 20, 2021 · 3 comments · Fixed by #741
Closed

[12.0] mail_tracking: SpamAssassin flag 'RAND_MKTG_HEADER' #701

JorgeQuinteros opened this issue Apr 20, 2021 · 3 comments · Fixed by #741
Assignees

Comments

@JorgeQuinteros
Copy link
Contributor

Hello,
Recently some invoice emails that I have been sending through Odoo were not reaching the recipients.They were always to the same customers, and if you sent with the same email account but from Thunderbird for example, it would arrive perfectly.

I have tested with mail-tester to check mail reputation and due to a recent update of SpamAssasin, the headers for Odoo mail tracking detects them as SPAM and drops almost 3 points. This increases the probability of getting into the inboxes of some customers.
imagen

imagen

It appears that if SpamAssasin finds several headers that start with "X-..." and have keywords like "Tracking" it lowers the email's score and may cause problems for certain recipients.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7888

If I uninstall the mail_tracking module my score is 10/10.

Has anyone else experienced this?
or any ideas on how to fix this, mail_tracking is a very powerful tool and I would hate to lose it.
Thanks,

@pedrobaeza
Copy link
Member

Fixed for v13 in #741

@eLBati
Copy link
Member

eLBati commented Jun 27, 2022

Porting to 12.0 with #926

@eLBati
Copy link
Member

eLBati commented Jun 27, 2022

Porting to 10.0 with #927

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

Successfully merging a pull request may close this issue.

4 participants