#2806 - Emails: Spam considerations
0 guests and 0 members have recently viewed this.
The top 3 point earners from 14th Dec 2025 to 21st Dec 2025.
| PDStig |
|
|
|---|---|---|
| Gabri |
|
|
| sholzy |
|
|
There are no events at this time
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.