Sandy Drobic wrote:
Jim Flanagan wrote:
Ulf Rasch wrote:
Jim Flanagan wrote: <snip>
: 24.238.237.18 failed after I sent the message. Remote host said: 550 Error: improper use of 8-bit data in message body ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That should be the reason. Have a look at the settings of your MUA (email client).
Ulf
Hi Ulf,
I don't understand what you mean here. I did notice that part you quoted, but I don't know what it means. What bearing would my email client have on a message being bounced by apparently my server? These are not messages I've sent.
That would be typical for a Postfix/Cyrus setup where Cyrus would reject the mail when it is not correctly encoded, let's say, a subjectline with extended characters. Postfix has restrictions that will reject such mails.
strict_8bitmime strict_8bitmime_body
Check your mail log /var/log/mail for the error message and check the output of "postconf -n" for these settings.
Sandy Thanks everyone for the pointers. Yes, the test message did not bounce, but two of the original OP messages did. The same thing happened on some of the spamassassin list mails as well with the same error message.
postconf -n returns... strict_8bitmime = yes strict_rfc821_envelopes = no No mention of strict_8bitmime_body listed. I believe this is standard Suse postfix setup, I did not change this setting. I am using Cyrus IMAP, does this have any bearing on this matter? Will changing strict_8bitmime = no in /etc/postfix/main.cf (and postfix reload) likely fix this problem? Any repercussions with Cyrus? Also, if you have time, what is the purpose of making this setting to yes? I take it that it prevents malformed email of some sort. But what is the drawback to not having this check set to strict? What are the known sloppy email clients (er, Outlook Express??!!). Many thanks, Jim Flanagan