[Bug 251102] New: amavisd-new 2.4.3 converts 7 bit encoded messages to 8 bit
https://bugzilla.novell.com/show_bug.cgi?id=251102 Summary: amavisd-new 2.4.3 converts 7 bit encoded messages to 8 bit Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: joe_morris@ntm.org QAContact: qa@suse.de A 7 bit encoded email sent through Postfix with amavisd-new setup to virus and spam scan converts the message encoding to 8 bit, which when relayed to a server not announcing 8bitmime support through an Exchange server, which does support 8bitmime, but does not convert to 7 bit for servers not announcing support for 8bitmime, gets bounced. Though the Exchange policy is wrong (it should convert and not bounce), the message should not have been converted to an 8 bit message in the first place. This was tested by sending a message to a christian.net address (which does not announce 8bitmime support) through Postfix, amavisd-new, Postfix, Exchange, christian.net, and it gets bounced. Postfix set to discard the Exchange 8bitmime, message goes through. Virus scanning turned off via Yast, remove the 8bitmime discard directive, message goes through. I updated to amavisd-new 2.4.5 (rebuilt the src rpm tweaked for the version change), and it works correctly. With the 2.4.5 version, 7 bit mail goes through Postfix, amavisd-new, Postfix, relayed to Exchange (without discarding 8bitmime), delivered to christian.net. I realize this bug would not affect many, since Postfix works correctly and would convert the 'converted' 8 bit message to a 7 bit message for a server not announcing 8bitmime support, so Postfix corrects the bug. It only shows up if, Postfix relays through a server announcing 8bitmime suppport (and therefore does not correct the error from amavisd-new 2.4.3), and the email is being relayed through a server that does not convert the now 8 bit message to 7 bit for a server that does not announce 8bitmime support (like aol.com). Version 2.4.5 appears to fix this bug. I believe it is a bug, as the virus and spam scanning should not change the message encoding to something less compatible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=251102 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |varkoly@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=251102 varkoly@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from varkoly@novell.com 2007-03-08 07:20 MST ------- Updated to 2.4.5. The new packages you can find ftp://ftp.suse.com/pub/people/varkoly/amavisd-new/2.4.5 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com