Executive summary:
- There is a BOM in the X-Ham-Report header field.
- There is reason to believe that it, and not just any non-ASCII,
triggered this rejection.
- Disabling the X-Ham-Report field (and possibly an X-Spam-Report
field) seems to be the best option.
Christian via Mailman-Users w
For cPanel, this looks relevant, assuming you have root privileges:
https://forums.cpanel.net/threads/how-to-remove-x-ham-report-from-message-header.636153/post-2597865
It shouldn't be overwritten on a Mailman update, whereas I think hacking
Cleanse.py would be.
On Fri, Feb 4, 2022 at 4:17 AM St
On 2/4/22 11:01, Russell Clemings wrote:
For cPanel, this looks relevant, assuming you have root privileges:
https://forums.cpanel.net/threads/how-to-remove-x-ham-report-from-message-header.636153/post-2597865
That's for exim. For Postfix, there's
/^X-Ham-Report:/ IGNORE
in /etc/postfix/hea
