On Tue, Mar 11, 2008 at 10:38 PM, Jay Soffian <jaysoffian@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
