Re: [PATCH 07/10] builtin-archive: mark unused prefix "unused_prefix"
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Mar 11, 2008, 16:21 UTC
- Message-ID
- <fcaeb9bf0803110921g754dfa54w517cad490476e59e@mail.gmail.com>
- In-Reply-To
- <76718490803110838p1cdc30a8vb9792d81ddf62a0d@mail.gmail.com>
On Tue, Mar 11, 2008 at 10:38 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
> I hate to make this request, but Gmail seems unable to decode messages > which are "Content-Disposition: inline" + "Content-Transfer-Encoding: > base64". The message body shows up completely blank in the Gmail web > interface. (I wonder if it is due to the footer that Majordomo appends?)
Funny that meesage was created by gmail.
> I've reported this is a bug to Gmail, but since I imagine I'm not the > only one using Gmail to read this list, and since so far your messages > seem to be the only ones sent this way, can I ask that you configure > your MUA to not send messages this way, if possible?
If I does not misunderstand it, non-ascii characters make gmail encode messages base64. I'll be careful next time removing all non-ascii (or switch back to mutt).
> Much appreciated, > > j. >
-- Duy