OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: 250-8BITMIME question

From: Bill Landry (billinetmsg.com)
Date: Thu Sep 20 2007 - 10:27:45 CDT


Mark Martinec wrote:
>>> amavisd unix - - n - 5 smtp
>>> -o disable_mime_output_conversion=yes
>>> ...
>> After adding "smtpd_discard_ehlo_keywords = ('8BITMIME');" to
>> amavisd-new, I realized that I needed to change the last line above to
>> "disable_mime_output_conversion=no" and that seems to have resolved the
>> signing issue I was having with 8bit mail sent from SquirrelMail.
>
> Right. This option was never suggested for a signing path
> in amavisd-new documentation, quite the opposite.

When I set up the DK and DKIM milters, I followed the advise shown in the
Postfix MILTER_README, which states:

"Content filters may break domain key etc. signatures. If you use an SMTP-based
content filter, then you should add a line to master.cf with "-
o disable_mime_output_conversion=yes" (note: no spaces around the "="), as
described in the advanced content filter example."

But since "amavisd is 8bit clean", as I now see stated on your DKIM page, the
amavisd-new suggestion is to NOT disable "disable_mime_output_conversion".

>> However, in doing this, is there anything else I should be concerned
>> about possibly breaking?
>
> Nothing comes to mind, but there are numerous ways mailers and
> mailing list managers can break a signature, so - time will tell...

Thanks, I'll report back if I find any issues...

Bill