In article <57e49a8d.1030...@sgeinc.com> you write:
> From a quick look, it looks like base64 encoding. Invented back in the
>dialup/uucp days when transport was not always 8bit clean so things were
>encoded to make sure only transportable characters were used.
Well, actually, we uucp users used something called uuencode, and base64
was invented for Internet MIME messages in the 1990s.
But if you can forward the message to your mail program, it can probably
decode the base64 and you can see what it is. Your hint about the
different character set is spot on, that's likely why it's base64 encoded.
>On 9/22/2016 9:58 PM, Matt Morgan wrote:
>> I have a message in a moderation queue. It's from a member (everyone is
>> moderated on this list) so I think it's not spam or other junk. But when I
>> click to review it, it's not legible. This is all I see in the message
>> I feel like I've seen other messages that look encoded/illegible in
>> moderation, though I don't have other examples right now. What can cause
>> For what it's worth, the sender is a speaker of a language that uses a
>> different character set, so if that's possible cause, that might be the
>> reason here.
Mailman-Users mailing list Mailman-Users@python.org
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/