Suppression of encoding bad header function in postfix

7 msg	Postfix 2.2.5 on latest Solaris 9 x86
5 msg	Postfix Relay, and Pop-before-smtp
12 msg	Newb Question
13 msg	Best defense against this?
1 msg	undelivered mail problem - SOLVED
4 msg	Legal local-part
3 msg	virtual_alias_domains with mysql: 'User unknown...
6 msg	Submission port (587): howto to use differente ...
5 msg	When does smtpd_reject_unlisted_recipient kick in?
4 msg	Postfix 'falling back' on sasldb? I don't want ...
3 msg	Nested access maps (I think ;))

Suppression of encoding bad header function in ...
\ Johny Mail list (21 Sep 2007)
. \ Victor Duchovni (21 Sep 2007)
. \ (Wietse Venema) (21 Sep 2007)

4 msg	RE: Catchall ??
3 msg	problem with .forward files + forwarding loops
5 msg	Postfix Strange Behaviours
7 msg	Content filter question, based upon auth'ed or not
28 msg	Mail stuck in active queue for loooong time
11 msg	How to stop a user from changing the 'From:' he...
10 msg	[Semi-OT] blocked port 465, anywhere?
7 msg	chroot problems on Nexenta (OpenSolaris)

Subject:	Suppression of encoding bad header function in postfix
Group:	Postfix-users
From:	Johny Mail list
Date:	21 Sep 2007

Hi list,
I have noticed between my debian update (3.1 to 4.0) that a function
had been deleted in the postfix , i think.
I explain:
Before with my Debian 3.1 with postfix 2.1.5 when i sent an email my
subject and other header was encoded if i put some incorrect
characters like " ° é è à ...".
Now with my Debian 4.0 with postfix 2.3.8 when i try to send this kind
of email, amavis lock it or spamassassin give a hard score to this
mail because, for example, the subject is not encoded.

I think it's a postfix problem because i have try with php mail()
function and with mail command from the shell and it's the same.

The configuration between postfix 2.1.5 and postfix 2.3.8 is the same.

Do you have any ideas? Because this make a lot of problems to my customers...

Thanks