Spamassassin headers. What you can do with Spamassassin headers and how.

How might a provider pull together better, easier ways to explain,
instruct a. using less of what might be perceived as jargon and b.
using less what might be perceived as arcane references, how might a
provider more easily explain, more easily instruct end users with these
questions?... end users with areas of expertise not directly applicable
to...

1.
What can you do with the spamassassin headers?... spamassassin headers
have appeared in the headers at the top of messages in emacs rmail.

2.
And how do you do the things you can do with the spamassassin
headers?...

Around the web the instructive material about spamassassin didn't
appear to meet the needs of end users, given the usual explanations
deferring the matter to another department, the provider, the isp,
someone else not me and so on.

Or what example or examples are there by way of individual spamassassin
hints, tips, pointers, features?...

Unrelated, but here's an example of providing hints, tips, points,
features
http://www.apple.com/pro/tips/

In comp.os.linux.networking (E-Mail Removed):
> How might a provider pull together better, easier ways to explain,
> instruct a. using less of what might be perceived as jargon and b.
> using less what might be perceived as arcane references, how might a
> provider more easily explain, more easily instruct end users with these
> questions?... end users with areas of expertise not directly applicable
> to...

What kind of end-users? Can we presume the only have POP3/IMAP or
alike access to their account?

> 1.
> What can you do with the spamassassin headers?... spamassassin headers
> have appeared in the headers at the top of messages in emacs rmail.

Which headers do you mean? There are quite a few SA can add.

> 2.
> And how do you do the things you can do with the spamassassin
> headers?...

Presuming you use SA to rewrite the subject, like this:

Subject: ****SPAM(29.2)**** Get all the me ds you need in one place! quirt

> Around the web the instructive material about spamassassin didn't
> appear to meet the needs of end users, given the usual explanations
> deferring the matter to another department, the provider, the isp,
> someone else not me and so on.

You seem to be as confused as those end-users. Anyway, why not
concentrate on rewriting "Subject:", gather information which
MUA (Mail User Agent) are used and setup a small how-to including
some screen-shots/etc on how to add some folder in the MUA and
then setup a filter moving the SA flagged mails into this folder.
For the top 10 MUA used or so.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 443: Zombie processes detected, machine is haunted.