In linux.gentoo.user, you wrote:
> --Sig_/TRElrs3oa099GBUkPVLmB/I
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
>
> On Mon, 28 Mar 2011 14:11:55 -0400, Elaine C. Sharpe wrote:
>
>> Apparently not everyone who uses kmail has the problem.
>> Maybe it's the people who use html mail?
>> Neil Bothwick's posts often have the "=3D=3D20", but usually just one or
>> two. Some posts are positively riddled with them, to the point of=20
>> being terribly difficult to parse.
>> Everytime I look at the headers of such a post it says kmail, but=20
>> not every kmail user has the problem.=20
>
> That's intriguing, considering it's been many years since I used
> KMail.
>
> The =3D20 is usually caused by a quoted-printable message, meaning either
> your newsreader cannot handle quoted-printable or the mail-to-news
> gateway is screwing it up.
>
>
> --=20
> Neil Bothwick
>
> WinErr 01C: Uncertainty error - Uncertainty may be inadequate.
>
> --Sig_/TRElrs3oa099GBUkPVLmB/I
> Content-Type: application/pgp-signature; name=signature.asc
> Content-Disposition: attachment; filename=signature.asc
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAk2RCc4ACgkQum4al0N1GQMW0gCfUWbfcTsR0qud/emp2jPLKp+w
> vTYAmgMURy8e9zJU1XSI0ZRv6Lhi7m/P
> =84Zr
> -----END PGP SIGNATURE-----
>
> --Sig_/TRElrs3oa099GBUkPVLmB/I--

I see you're using claws, sorry -- guess I misremembered.
You can see an "=20" though in the quote, there at your
sig delimiter? It appears to replace the trailing space,
so that your sig is not delimited and shows in the quote.
 
Anyway, apologies to the kmail users.
Probably the mail2news is the culprit, as I've used slrn for usenet
for years and have it working extremely well on every other group.
Later I'll try setting up mutt for nntp just for this one group, as
it can pipe through lynx. Maybe that'll be easier to read.

-- 
...she kept arranging and rearranging the rabbit and kind of waving to it. 
I decided, "this is the person I want to sit next to".


Reply via email to