Very Computer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

I got spamassassin working using the canned instructions on
http://www.mandrakeforum.com/article.php?lang=en&sid=2140

It works very nicely, but I don't know how to set up a KMail filter rule to
run spamassassin on all in coming messages. The filters I have managed to
set up use <To>:whatevername rules. So, spam messages which have bad To:
fields don't get filtered out.

Am I missing something obvious? (And, if so, what?)

Any help appreciated

Cheers

        Jens
- --

    Analogue filtering / 5GHz RLAN / Mdk Linux / odds and ends
http://www.imaginet.fr/~jensting/             +44 1223 211 585
"He's very fussy about his drums, they loom large in his legend" Hard Days
Night
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE88HKzimJs3AlyPBIRAg9MAKDrAUncKBWGY9g+TqbJBqGhAWkdvwCg4s5C
oDlyry3oXm+EuhMcMpFn+Hc=
=AGUo
-----END PGP SIGNATURE-----

I'm going to ask a related question, as well as guess at a possible answer.

Possible answer: does "filter action"--> "execute command" or "pipe though"
do anything for you?. (I can't answer as I don't use spamassassin)

Related question: How can I use the "To" "doesn't contain" line to use all
of my local possibilities

first filter.  I want to say something like

(insert other possibilities)--> send to trash" but putting this as seperate
rules even in the same filter using "any or all" doesn't do this.  Even if
I uncheck "stop filtering here" of course.

all the best,
Robert_L
--
Debian 3.0
KDE-3.0.1
XFree-4.1

Quote:> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Hi

> I got spamassassin working using the canned instructions on
> http://www.mandrakeforum.com/article.php?lang=en&sid=2140

> It works very nicely, but I don't know how to set up a KMail filter rule
> to run spamassassin on all in coming messages. The filters I have managed
> to set up use <To>:whatevername rules. So, spam messages which have bad
> To: fields don't get filtered out.

> Am I missing something obvious? (And, if so, what?)

> Any help appreciated

> Cheers

>         Jens

From http://spamassassin.org/dist/README,
<quote>
If you use KMail:

  - http://kmail.kde.org/download.html mentions:

    The filter setup is the work of five minutes (if that!) if you have a
    working spamassassin set up.

    The filter in question is "<any header><matches regexp> ."

    The action is "<pipe through> spamassassin -P"

    Then, in the advanced options, uncheck the "If this filter matches,
    stop processing here" box. If you keep this filter at the top, it will
    analyze any incoming mail, decide whether it's spam or not, and flag
    it accordingly.

    [Then add] a second filter behind it, which searches for the added
    spam-flags and diverts them into a specific spam folder. [...]

</quote>

There's also a FAQ on the spamassasin.org site. Check it out.

HTH,
Tim

<snip>

Just use a filter that must match any incoming message, e.g. any
message must have a domain name in the <From> field, so

must contain an alpha numerical character, so use
'<any header>  does match reg. expr. [a-zA-Z\d]'.

Then use Filter Actions->execute command  to run the app on all
incoming messages. If you want further filtering, uncheck 'If
this filter matches.....' and make it the first filter.

HTH,
Ransom

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[..]

Quote:>> Am I missing something obvious? (And, if so, what?)

[..]

Quote:> From http://spamassassin.org/dist/README,
> <quote>
> If you use KMail:

I guess I was missing something obvious - RTFM.

Thanks a bunch for the posts with the answers.

Regards

        Jens
- --

    Analogue filtering / 5GHz RLAN / Mdk Linux / odds and ends
http://www.imaginet.fr/~jensting/             +44 1223 211 585
     "If t'were you, t'would be twerrific!"       'Men in Tights'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE88bEqimJs3AlyPBIRAtz3AKCCZAOQlDKI5bJEqHscAQPEXezRqQCg8eY9
OR0OrXEdI1KPoZGhEiCf/vM=
=dOqU
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[..]

Quote:

> I'm going to ask a related question, as well as guess at a possible
> answer.

> Possible answer: does "filter action"--> "execute command" or "pipe
> though" do anything for you?. (I can't answer as I don't use spamassassin)

Yes, "pipe through" works fine. Spamassassin has a pipe mode which I
verified from the command line, and the same thing happens to messages in
KMail piped through using filter action "pipe through".

Regards

        Jens

- --

    Analogue filtering / 5GHz RLAN / Mdk Linux / odds and ends
http://www.imaginet.fr/~jensting/             +44 1223 211 585
     "If t'were you, t'would be twerrific!"       'Men in Tights'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE88bDYimJs3AlyPBIRAiN8AKCLWGhS2OZoJYqIpV61OjENuvbFAQCfVKAF
Epd8YqVz9vDkAS7Brm5XAHw=
=qZHn
-----END PGP SIGNATURE-----

I guess I know what you are trying to accomplish. I do that and it works
for me. Obviously you should put this rule at the END of the list. This is
the last rule you want to have after you pass thru all your previous
filters...

(X) Match ALL of the following

Get the picture? Work in pairs...always one for the To field and another
for the Cc...

Try it out.

Jos

Thanks Jos.  It seems obvious now.  For some reason I thought selecting
"ALL" would do something different- and when I tested it it failed for a
different reason.  This seems to work.  I'll give it a try.

all the best,
Robert_L
--
Debian 3.0
KDE-3.0.1
XFree-4.1