Joe Morris (NTM) wrote:
Sandy Drobic wrote:
Joe Morris (NTM) wrote:
Since the message was 7 bit to start with, and telling Postfix to discard the 8bitmime ehlo response allows it to work, which is the problem? Should Postfix convert the message to 8bit? Is that the proper response to the 8bitmime ehlo response? Is the problem Exchanges non conversion to 7bit when the destination server does not support 8bitmime? IOW, they could configure Exchange to not advertise 8bitmime
Postfix does not convert any 7bitmime to 8bitmime, it merely converts 8bitmime to 7bitmime, if the destination server does not support 8bitmime.
But didn't the message have to be converted to 8 bit to be rejected by those domains we had trouble sending to , and whose servers do not advertise 8bitmime? I guess I was assuming they had to be since they were bounced. And they now work with 8bitmime keyword discarded. So am I wrong that, since the client says the message was 7 bit (Thunderbird), i.e.
Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
The only way to be sure is to inspect the message after they went through a hop and compare them with the originally sent message. Use the "hold" action to capture the mail and have a look at it with "postcat -q queue-id". That way you can compare the mail before and after it went through Amavisd-new. I am not an expert on mime encapsulation but AFAIK every mime entity can have a different encoding. If you are using AlterMIME to add Footers to outgoing mails or something similar, that could also introduce 8bitmime.
and it now goes through with only the change to what Postfix sees in the response codes from Exchange, that they had to be being converted to 8 bit somewhere. I do also run amavisd-new with virus and spam checking, so all the messages do also go through there. If Postfix doesn't convert 7 bit to 8 bit, how do they now work? I checked amavisd-new, and it also advertises 8bitmime. If it started off as a 7 bit encoded message, and it went through Postfix 2x and amavisd-new once, and discarding 8bitmime AFAIU should make Postfix convert the message to 7 bit, where could it have become an 8 bit message?
Any hop on the way could have done it. But better take a look at the exact message content after each hop (yes, Amavisd-new also counts as hop).
Though there was a bug recently in a perl module that amavisd-new uses (Net::Cmd 2.2.7), which caused ALL mail to be converted to UTF8 regardless of the encoding of the headers. It caused a lot of screams here in Germany because the problem immediately became apparent with the German "Umlaute" äüö etc.
I checked and I don't have that module installed. pin doesn't even list that module. But that got me to wondering if amavisd-new could be converting it. I had totally forgot about that one.
Easy to forget. I had an eye on Amavisd-new because I needed to implement DSN, so I kept in mind that Amavisd-new also acts as an smtp server. Net::Cmd is part of libnet 1.20. I was bitten by that bug when I updated my Perl installation through the cpan shell. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org