Greetings from Switzerland,

I got a serious problem with Unicode and Amavis. I'm trying to solve a certain 
problem for about a week, but the problem seems to have been there since the 
first mailserver setup last year. All mail bodies seem to get encoded to utf-8, 
even if explicit not allowed to do so. iso-8859-1 bodies get (double?)encoded 
to utf8, unicode bodies get reencoded, both senarios result in an odd display 
of umlaute (ä ö ü). I never saw this problem myself because I use Apple Mail 
which Base64 encodes everything, but my father, who uses thunderbird, just 
recently started to use my mailserver.

The mail system setup consists of postfix as smtp, amavis with clamav and 
spamassassin for antispam/antivirus and the last part courier-imap. If I 
disable amavis I've got no wrong encodings, so it must be something with amavis 
itself or its modules. Following that though I disabled all plugins (no 
antivirus and no antispam modules) but it still encodes iso mails to utf.

Then I checked for right LANG settings, which arn't set so defaulting to 
"Posix", setting the locale for amavis explicity doesn't work either (to C or 
en_US), it's been understood by amavis but it hadn't any effect on the problem. 
Then I set the $unicode_aware settings explicit to undef. I did the reverse to, 
enforcing UTF8, no change at all (I think it didn't get worse and certainly not 
better).

Since I'm using amavisd-new on debian sarge from a backport package, the 
version was a little older than the newest one (2.3.3). So I manually updated 
the Version to the newest available (2.4.2) which worked but I still had that 
Unicode bug.

So I started tracing ($LOG_LEVEL=3) which actually just told me that everything 
worked but sometimes my clamav's db file can't be used properly after some 
time, not very usefull for my unicode problem but at least I found one more 
problem. :) (I may need more output for logging)

I hope someone can help me finding the bug and eliminating it, that would be 
great. Links to similar problems and solving techiques would be nice too. 
(Although everything should already reside on my browsers cache).

Here is a link where you can find the evidence I collected, meaning one email 
with and without using amavis.
http://www.temporal.ch/tmp/

bye
Alexander Schäfer

PS: Just got another error trying to send an email to here, how to solve it? 
Adding postmaster to the mailserverdomain as well as the maildomain didn't help.
X-Postfix; host mail.sourceforge.net[66.35.250.206] said:
550-Postmaster verification failed while checking <mbalex (at) temporal {dot} 
ch>
550-(result of earlier verification reused). 550-Several RFCs state that
you are required to have a postmaster 550-mailbox for each mail domain.
This host does not accept mail 550-from domains whose servers reject the
postmaster address. 550 Sender verify failed (in reply to RCPT TO command)

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to