Re: [tdf-discuss] Problematic digest mail answering - Buggy mailclient?
Friedrich Strohmaier wrote on 2011-05-16 23.45:
As I read in this thread and in others, answering listmails received in
digests cause problems for some mail clients. As I found out Thunderbird
is affected and gmail seems as well. I suspect it may be caused by the
base64 encoded content of that mails.
ah, thanks a lot - now I got it.
I don't have any digest subscriptions. From what I recall with
Thunderbird 3.x, you should see all mails as attachments. If you open up
that attachment, you should be able to reply to it. However, cannot test
it right now.
Might also be an error in encoding introduced either by mlmmj or by
pymime. For mlmmj, I plan (soon :-) to update to a newer version that
might bring cure. For pymime, you could try
changing mlmmj-pymime to mlmmj for the test list
do a postfix reload
try the digesting again
don't forget to go back from mlmmj to mlmmj-pymime and restart Postfix
That way you can at least discover if the erorr is in pymime or not.
Florian Effenberger <email@example.com>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy