On 2015-08-28 19:55, Robert Schetterer wrote: > Am 28.08.2015 um 19:46 schrieb Per olof Ljungmark: >> On 2015-08-28 18:07, Viktor Dukhovni wrote: >>> On Fri, Aug 28, 2015 at 05:59:08PM +0200, Per olof Ljungmark wrote: >>> >>>> Yes, that helped with Thunderbird but not from Horde/IMP where it still >>>> bounces the same way. >>>> >>>> The difference seems to be that IMP sends a >>>> "Content-Transfer-Encoding: quoted-printable" >>>> >>>> and TB >>>> "Content-Transfer-Encoding: 8bit" >>>> >>>> Could this be the cause? >>> >>> Yes, if IMP sends data claimed to be quoted-printable, but contaning >>> unencoded non-ASCII characters. >>> >>> You'll need to capture a sample message and find the violation. >> >> Looking at the sent messages I cannot find anything violating >> quoted-printable, "It's" is "It=C2=B4s" for instance. >> >> IMP uses >> "Content-Transfer-Encoding: quoted-printable" >> and that seems to be true. >> >> and TB uses >> "Content-Transfer-Encoding: 8bit" >> which also seems true and is dealt with according to Wietse's reply. >> >> What I do not understand is that in the bounce from the remote Exchange >> mail relay, our IMP message is presented as 8bit. >> >> Sent: >> >> --=_rJ0N-qFsVHye8YMhx4uKOaC >> Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes >> Content-Description: Endast text-meddelande >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> Bounce: >> >> --=_rJ0N-qFsVHye8YMhx4uKOaC >> Content-Type: text/plain; >> format=flowed; >> charset="utf-8"; >> delsp=Yes >> Content-Description: Endast text-meddelande >> Content-Disposition: inline >> Content-Transfer-Encoding: 8bit >> >> As my knowledge sort of ends here I will ask our sysadmin Monday to look >> over what is coming out of IMP, but I seriously doubt that it is >> anything wrong with it. >> >> Thanks! >> > > old imp version ? > > https://bugs.horde.org/ticket/13851
horde-imp-6.2.10 Not ancient, is it?
