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

SpamAssassin scoring phpList emails with TO_NO_BRKTS_HTML_IMG #919

Open
markmixx opened this issue Jan 7, 2023 · 1 comment
Open

SpamAssassin scoring phpList emails with TO_NO_BRKTS_HTML_IMG #919

markmixx opened this issue Jan 7, 2023 · 1 comment

Comments

@markmixx
Copy link

markmixx commented Jan 7, 2023

The default SpamAssassin rules are adding a relatively high score to phpList emails because of the combination of the To: header not being surrounded by angle brackets, the default HTML message format, and the default single tracking image that is setup on campaigns. This is a fresh phpList install with nothing changed except adding a test campaign.

SpamAssassin reports from two different servers:

  1. * 2.0 TO_NO_BRKTS_HTML_IMG To: lacks brackets and HTML and one image
  2. TO_NO_BRKTS_HTML_IMG 1.999 To: lacks brackets and HTML and one image

This was mentioned on the forums but in that post the score was negative. On two different SpamAssassin receiving servers I have access to it is actually a positive score which can end up classifying phpList mails as spam.

Currently the To header is being set like this:

To: [email protected]

I believe the fix for this would be to change the To header to be enclosed in brackets, either one of these:

To: <[email protected]>
To: [email protected] <[email protected]>

This is with phpList configured to use an SMTP server and not PHP's mail(). Thanks.

@michield
Copy link
Member

michield commented Jan 8, 2023

Those errors seem more about an image having incorrect HTML tags than the To field. It may be that some images are not closing with />

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