Spam handling?

RT Users
1

I have MimeDefang/SpamAssassin scanning for spam on our internet
gateway but it tags rather than rejecting the identified messages.
Has anyone come up with a reasonable way to handle spam on the
way into RT? Can it be filtered into a different queue based on
the X-Spam-Score: header added by MimeDefang or would it be better
to intercept before it goes into RT at all, perhaps dumping into a
mailbox that someone scans occasionally.

Les Mikesell
les@futuresource.com

2

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

Content-Type: text/plain; charset=us-ascii

In message CJELIEBEFNCJAOMOOMNNOEFOCKAA.les@futuresource.com, “Les Mikesell”
writes:

I have MimeDefang/SpamAssassin scanning for spam on our internet
gateway but it tags rather than rejecting the identified messages.
Has anyone come up with a reasonable way to handle spam on the
way into RT? Can it be filtered into a different queue based on
the X-Spam-Score: header added by MimeDefang or would it be better
to intercept before it goes into RT at all, perhaps dumping into a
mailbox that someone scans occasionally.

We just run the email through procmail before sending it to RT. Procmail
dumps the emails that tag high enough as spam.

Ted Cabeen http://www.pobox.com/~secabeen ted@impulse.net
Check Website or Keyserver for PGP/GPG Key BA0349D2 secabeen@pobox.com
“I have taken all knowledge to be my province.” -F. Bacon secabeen@cabeen.org
“Human kind cannot bear very much reality.”-T.S.Eliot cabeen@netcom.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+VsFboayJfLoDSdIRAiXPAKC/jw/iYWBBckVpIG4rSKb0xUIVSQCfUwSM
1vKErHIiZIajgsXNCrL+KtU=
=YAdU
-----END PGP SIGNATURE-----

3

I have MimeDefang/SpamAssassin scanning for spam on our internet
gateway but it tags rather than rejecting the identified messages.

That’s exactly what we do too, and we trap the tagged messages with
procmail into an extra mailbox. The Mail which is not caught
goes on to rt’s real mail-address.

Stucki

Christoph von Stuckrad * * |nickname |stucki@math.fu-berlin.de
Freie Universitaet Berlin |/_*|‘stucki’ |Tel(days):+49 30 838-75 459|
Fachbereich Mathematik, EDV|\ |if online|Tel(else):+49 30 77 39 6600|
Arnimallee 2-6/14195 Berlin * |on IRCnet|Fax(alle):+49 30 838-75454/

4

Les Mikesell wrote:

Has anyone come up with a reasonable way to handle spam on the
way into RT? Can it be filtered into a different queue based on

How I did it:

http://lists.fsck.com/pipermail/rt-users/2002-June/008829.html
�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

5

Les Mikesell wrote:

Has anyone come up with a reasonable way to handle spam on the
way into RT? Can it be filtered into a different queue based on

How I did it:

http://lists.fsck.com/pipermail/rt-users/2002-June/008829.html

And I used Phils style, with addition of one recipe at the top

:0:

  • ^X-Spam-Status: Yes
    |/dev/null

I used this because by the time the mail get’s to RT, it’s already
passed thro spamassin and is tagged. In my setup, mail that is tagged
as spam is quarantined and a notification is sent to the original
recipient about it. I also trash these notifications via another recipe.

Might not be perfect, but works for me.

    cheers
   - wash

Odhiambo Washington, wash@wananchi.com . WANANCHI ONLINE LTD (Nairobi, KE) |
http://ns2.wananchi.com/~wash/ . 1ere Etage, Loita Hse, Loita St., |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
“Oh My God! They killed init! You Bastards!”
–from a /. post

6
  • Odhiambo Washington [2003-02-22 02:13]:

:0:

  • ^X-Spam-Status: Yes
    |/dev/null
    ^

Does this actually work? You’re piping this through /dev/null here (the
leading |), instead of putting it into /dev/null.

(Also, you don’t need to lock /dev/null – use :0 instead of :0:).

(darren)

History doesn’t always repeat itself. Sometimes it just yells ‘can’t
you remember anything I told you?’ and lets fly with a club.
– John W. Campbell Jr.