After removing the Content Preview header, I sent another email to the mailing list. Instead of bouncing back with the previous 8-bit header error, this time it disappeared into a black hole. It neither posted to the list nor produced an error message.
This is the entry from my Exim log: 2022-09-17 13:34:47 1oZeWP-005k6N-2w => debian-...@lists.debian.org R=dnslookup T=remote_smtp H=bendel.debian.org [82.195.75.100] X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no DN="C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CN=bendel.debian.org,EMAIL=hostmas...@bendel.debian.org" K C="250 2.0.0 Ok: 9210 bytes queued as D970620700” 2022-09-17 13:34:47 1oZeWP-005k6N-2w Completed Time zone is -0700. Because of the previous problem with SpamAssassin headers I thought I might test removing all of them to see if this was the problem. I did that by adding the following lines to the main Exim config. # Remove the SpamAssassin headers from outgoing email. REMOTE_SMTP_TRANSPORTS_HEADERS_REMOVE = X-Spam-Action : X-Spam-Score : X-Spam- Bar : X-Spam-Report After doing this, I was able to post to the list. This is the email that went through: https://lists.debian.org/debian-kde/2022/09/msg00011.html[1] Removing the headers from outbound mail isn’t a problem for me because SpamAssassin is still being run and it is only important for me that the headers are added to inbound mail and are in the logs for outbound mail. But that might or might not be an acceptable solution for all email servers. It isn’t clear to me if blocking all emails with SpamAssassin headers is an intentional configuration on the list servers, but if it is I would imagine the behavior should probably be modified to produce a bounce email with an error message to make it easier for people to understand why emails are not getting through. -- Soren Stoutner 623-262-6169 so...@stoutner.com -------- [1] https://lists.debian.org/debian-kde/2022/09/msg00011.html
signature.asc
Description: This is a digitally signed message part.
