#2806 - Emails: Spam considerations
-
By PDStig
- Added
- 2 views
| Identifier | #2806 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | Emails: Spam considerations |
| Status | Closed (rejected) |
| Handling member | Chris Graham |
| Addon | core_notifications |
| Description | I feel we need to re-evaluate how emails are formatted and sent out in Composr. In several instances, spam servers for email domains will block emails from Composr due to it thinking or feeling like the message is spam. Common reasons are the email having URLs/links, photos, and/or attachments in it.
The easy solution would be disable HTML emails in Composr and force text-only emails. But if we have the option of HTML emails, I feel we need to do something to ensure they are sent as ham and not spam. I'm not sure myself how it can be done though. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Set up SPF on the domain and you are much less likely to get spam-blocked.
You can also disable the inline image feature in the configuration if needed, but the tradeoff there is you need to click a show images button.
A lot of spam filters also focus on domain reputation. Having no reputation is like having a bad reputation sometimes... meaning your emails could still get potentially blocked just because they don't know you can be trusted.
What does it say?
- Added text mail template, for forcing word-consistency with the mail template (SpamAssassin)
- Documented additional SPF settings
- Documented about fixing bad return-path addresses
- Documented configuring HELO
- Removed mail.add_x_header in default PHP setting overrides and documented (it triggers a high SpamAssassin score)
Getting rid of HTML emails / links / attachments really shouldn't be needed. They'd have a tiny impact on spam score and a big impact on UX, and extra complexity in our emailing layer.