Re: [Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-15 Thread Mark Sapiro
On 11/15/2013 06:11 AM, Roel Wagenaar wrote: > > I have adde your lines right after "import re", and almost instantly get the > "We hit a bug" message in the web interface. > > I have attached an extract from mailmans error log, hope the list will allow > it. > The error message is: > > admin(30

Re: [Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-15 Thread Roel Wagenaar
Mark Sapiro wrote: > I am guessing that you are talking about plain text message bodies with > character set UTF-8, and your list is adding a msg_header or msg_footer, > although there could be other cases as well. > > This issue is due to the Python email package. In order to add a > msg_header

Re: [Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-14 Thread Mark Sapiro
On 11/13/2013 11:52 PM, Roel Wagenaar wrote: > > My /etc/procmailrc is decoding Content-Transfer-Encoding: base64 headers as > standard rule forall incoming mail. > > Funny thing happens when filtered mailis beiing resend by Maiman, it encode > the base64 part again, is there an option to prevent

[Mailman-Users] Content-Transfer-Encoding: not workng as expected.

2013-11-13 Thread Roel Wagenaar
L.S. Mailman version 2.1.15-1 Debian Wheezy My /etc/procmailrc is decoding Content-Transfer-Encoding: base64 headers as standard rule forall incoming mail. Funny thing happens when filtered mailis beiing resend by Maiman, it encode the base64 part again, is there an option to prevent this? I don