Re: Scoring on basee64 encoded message body

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Jan Tatarik <jan.tatarik@gmail.com> writes:

> I finally realized the content of the messages is base64 encoded, so
> matching on the raw body cannot work.
>
> The attached patch fixes the problem for me, but I have no idea
> whether it's a generally acceptable solution. I'm only using the body
> match in a low-traffic group, so speed is not an issue for me.

[...]

> +            (when (string= (gnus-fetch-field "content-transfer-encoding") "base64")
> +              (article-de-base64-unreadable t))

This isn't a general enough solution here.  QP-encoded messages also
want decoding.

But the more general issue is -- should scoring on bodies be done on the
decoded messages or the encoded messages?  I think it would make more
sense to do it on decoded messages, and since these are body matches,
speed don't really matter that much, because body matches are s-l-o-w
anyway.

Scoring on headers are done on the decoded headers, right?  So it would
be more consistent to decode the bodies, too.  Wouldn't it?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/