>
> This is definitely not the sender's problem. The problem is the
> software that is adding the NOLUG information.
>
<snip>
>
> The sender (Curtis) is sending a valid email. This email, by itself,
> will be displayed by Gmail properly. The email is entirely base64
> encoded and the header of the email indicates this. Gmail understands
> that and doesn't have a problem.
>
My question is, what's this nonsense about encoding plain text? How (un)common
is that? Can the poker (basher, whatever) change the encoding on his device?
> Along the way, though, the NOLUG mailing list software adds 3 un-encoded
> lines (the bit that says “Nolug mailing list”) at the end. It leaves
> the message otherwise un-altered.
>
Have you tried decoding it to see what plaintext pops out?
<snip>
>
> But the real bug is in the mailing list software.
>
Um...
-- Joey Kelly Minister of the Gospel and Linux Consultant http://joeykelly.net
___________________
Nolug mailing list
nolug@nolug.org
This archive was generated by hypermail 2.2.0 : 08/06/09 EDT