From: Peter Volkov <pva@gentoo.org>
To: mlmmj@mlmmj.org
Subject: MIME encodings when dealing with adding the footer
Date: Thu, 13 Dec 2007 10:07:35 +0000 [thread overview]
Message-ID: <1197540455.6128.23.camel@camobap> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hello, list.
There is a problem in the current version of mlmmj in handling footer
which in combination of gmail effectively makes impossible usage of this
feature. In short if you have mail mime encoded (which happens very
often this days) footer like this:
[footer]
--
gentoo-doc-ru@gentoo.org mailing list
[/footer]
will be displayed in evolution as
�│ИМ╒▀╛z╨Н│ИМ╒┼+┌f╒√)Ю√+-
But the worst thing is that our Russian users reported that it
completely impossible to read such messages in gmail. See bug
bugs.gentoo.org/173159 for additional details. And quoting Robin Johnson
for the mentioned bug:
============================================================
The best fix would be, if the body has a non-plaintext type, add the
footer in another MIME block, rather than trying to add it to the
existing block.
============================================================
This is still the issue with net-mail/mlmmj-1.2.14, but I do not see any
flag in ChangeLog that this is fixed in 1.2.15. So the question is are
there any plans to fix this issue?
Thank you very much for your time,
--
Peter.
[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-12-13 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 10:07 Peter Volkov [this message]
2007-12-13 10:31 ` MIME encodings when dealing with adding the footer Morten K. Poulsen
2007-12-13 11:18 ` Peter Volkov
2007-12-13 11:49 ` Morten K. Poulsen
2007-12-13 12:02 ` Robin H. Johnson
2007-12-13 13:00 ` Morten K. Poulsen
2007-12-13 13:09 ` Jakob Hirsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1197540455.6128.23.camel@camobap \
--to=pva@gentoo.org \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.