| Summary: | set Message-ID domain to ipfire.org | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Peter Müller <peter.mueller> |
| Component: | Mail & Mailing Lists | Assignee: | Peter Müller <peter.mueller> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Müller <peter.mueller> |
| Severity: | Minor Usability | ||
| Priority: | - Unknown - | ||
| Version: | unspecified | ||
| Hardware: | all | ||
| OS: | All | ||
| See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=11813 | ||
| Bug Depends on: | |||
| Bug Blocks: | 11634 | ||
|
Description
Peter Müller
2018-10-14 06:05:27 UTC
I am not really a fan of rewriting IDs, because rewriting an ID just feels wrong. I also do not see the Message-Id needing to be conforming to any guidelines. That's not in the original RFC. However, because I do not have a better solution, just go ahead and have this rewritten on the individual VMs. Be aware that those servers might need to send email from another domain than just ipfire.org. Changed for *.i.ipfire.org (header_checks on mail01.ipfire.org). Other domains are not affected. However, stumbling across FORGED_SENDER and R_SPF_NA symbols in rspamd output for monitoring mails, I am not sure if this solves the entire problem. Rewriting Message-IDs is not requried for staying SPF compliant. After some debugging, it turned out that mails from monitoring01.i.ipfire.org were sent with the envelope sender <icinga@monitoring01.i.ipfire.org>, causing both MX and SPF failures and thus adding some points to the spam score. We _must_ make sure MIME and envelope sender are equal to each other and point to @ipfire.org (or any other domain with at least a valid MX record). I reverted all changes made because of this ticket. |