Spam filtering

RT Users
1

anyone have info on a spam filtering setup for rt? the faq mentions
that using spamassisin is a good idea but stops too short of being useful.
tony

2

anyone have info on a spam filtering setup for rt? the faq mentions
that using spamassisin is a good idea but stops too short of being
useful.

putting procmail in front of rt is pretty common.

seph

3

I’m interested too. Is there a LinuxDoc type HowTo on setting up RT with spam filtering? I’ve never done it in general, so a recipe would be really helpful.

4

In article 3F65C51E.6040900@cwlab.com, tony zoeteman wrote:

anyone have info on a spam filtering setup for rt? the faq mentions
that using spamassisin is a good idea but stops too short of being useful.

I would imagine the setup would much like it is for setting up a spam
filter to guard a regular address. In this case, you might do something
different with the “SPAM” mail, such as forward it a human for review,
or just set the threshold very high. For messages that score very highly
as spam, you could delete them directly.

In general, I would procede with installing a spam prevention tool as if
you were using with it with a regular e-mail account. I use SpamAssassin
for my personal mail and am extremely happy with it. Before that I used
TMDA which I found more cumbersome while still letting some spam
through, when spammers respond to the confirmation message.

Mark

. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
mark@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .

5

I use the following tool to do my spam filtering in front of RT.
It uses Mail::Audit and Mail::Spamassassin. It can, in fact, be run in
front of any program that receives mail through a pipe in your
/etc/aliases file. You’ll need to make sure it can write to its temp
directories and your spamassassin setup is as you like it.

Rob Spier wrote this tool for perl.org and I adapted it for RT3.
I’m eternally grateful. It’s made my life suck much less.

in /etc/aliases, I’ve got this:
rt-3.0-bugs: “|/opt/bestpractical.com-rt3/bin/mailaudit /opt/fsck.com-rt3/bin/rt-m
ailgate --queue ‘rt3’ --action ‘correspond’ --url http://rt3.fsck.com/”

mailaudit is this:

#!/usr/bin/perl

$Id: bugsfilter,v 1.31 2002/07/31 04:06:22 rt Exp rt $

use strict;

– CONFIGURATION –

my $HOME = “/opt/rt3/mail/”;
$ENV{‘HOME’} = $HOME;
my $maildir = “$HOME/Mail/”;

use Mail::Audit qw(KillDups);
use Mail::SpamAssassin;
$Mail::Audit::KillDups::dupfile = “$HOME/.msgid-cache”;

my @defaults = qw(your-rt-owner);

– CODE –

my $mail = Mail::Audit->new( loglevel => 4,
log => “$HOME/triggerfilt.log”,
noexit => 1,
nomime => 1) ;
exit if $mail->killdups;

my $spamtest = Mail::SpamAssassin->new();
my $status = $spamtest->check($mail);

if ($status->is_spam()) {
# eval from simon, who calls it a naughty hack, to work around
# brokenness in M::A and Mime
eval { $status->rewrite_mail(); };
$mail->accept(“$maildir/spam”);
# default() unless ($status->get_hits() > 15);
exit();
}
rt( $mail);
exit;

sub default {
$mail->resend($_) for @defaults;
exit;
}

sub rt {
my ($mail) = @_;
my $cmd = join(" “, @ARGV);
do {
$mail->reject(“Unable to determine recipient”);
$mail->accept(”$maildir/badrt");
} unless $cmd;

$mail->pipe( "$cmd");
if ($? >> 8 == 0 ) { 
$mail->accept("$HOME/Mail/rt");
} elsif ($? >> 8 == 75)  {
exit (75); # TEMPFAIL  
}
else {
$mail->accept("$maildir/rt-failed");
}

}

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

6

tony zoeteman wrote:

anyone have info on a spam filtering setup for rt? the faq mentions
that using spamassisin is a good idea but stops too short of being useful.

http://www.google.com/search?q=spamassassin+howto+site%3Afsck.com

it’s for RT2, but works with RT3 with a minimum of work…
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

7

In article 3F65C51E.6040900@cwlab.com, tony zoeteman wrote:

anyone have info on a spam filtering setup for rt? the faq mentions
that using spamassisin is a good idea but stops too short of being useful.

I would imagine the setup would much like it is for setting up a spam
filter to guard a regular address. In this case, you might do something
different with the “SPAM” mail, such as forward it a human for review,
or just set the threshold very high. For messages that score very highly
as spam, you could delete them directly.

In general, I would procede with installing a spam prevention tool as if
you were using with it with a regular e-mail account. I use SpamAssassin
for my personal mail and am extremely happy with it. Before that I used
TMDA which I found more cumbersome while still letting some spam
through, when spammers respond to the confirmation message.

Mark

–
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
mark@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

4 Aug 2003 19:49

I posted my setup to rule out spam. There’s a lot in the archive about
fighting spam.

/rhb

8

I use the following tool to do my spam filtering in front of RT.
It uses Mail::Audit and Mail::Spamassassin. It can, in fact, be run in
front of any program that receives mail through a pipe in your
/etc/aliases file. You’ll need to make sure it can write to its temp
directories and your spamassassin setup is as you like it.

Rob Spier wrote this tool for perl.org and I adapted it for RT3.
I’m eternally grateful. It’s made my life suck much less.

in /etc/aliases, I’ve got this:
rt-3.0-bugs: “|/opt/bestpractical.com-rt3/bin/mailaudit /opt/fsck.com-rt3/bin/rt-m
ailgate --queue ‘rt3’ --action ‘correspond’ --url http://rt3.fsck.com/”

mailaudit is this:

#!/usr/bin/perl

$Id: bugsfilter,v 1.31 2002/07/31 04:06:22 rt Exp rt $

use strict;

– CONFIGURATION –

my $HOME = “/opt/rt3/mail/”;

I am guessing you meant /opt/rt3 as $HOME

$ENV{‘HOME’} = $HOME;
my $maildir = “$HOME/Mail/”;

use Mail::Audit qw(KillDups);
use Mail::SpamAssassin;
$Mail::Audit::KillDups::dupfile = “$HOME/.msgid-cache”;

my @defaults = qw(your-rt-owner);

What would be the default value of rt-owner ?

[…]

I will give this a shot

Thanks a lot
Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

9

I use the following tool to do my spam filtering in front of RT.
It uses Mail::Audit and Mail::Spamassassin. It can, in fact, be run in
front of any program that receives mail through a pipe in your
/etc/aliases file. You’ll need to make sure it can write to its temp
directories and your spamassassin setup is as you like it.

Rob Spier wrote this tool for perl.org and I adapted it for RT3.
I’m eternally grateful. It’s made my life suck much less.

in /etc/aliases, I’ve got this:
rt-3.0-bugs: “|/opt/bestpractical.com-rt3/bin/mailaudit /opt/fsck.com-rt3/bin/rt-m
ailgate --queue ‘rt3’ --action ‘correspond’ --url http://rt3.fsck.com/”

mailaudit is this:

#!/usr/bin/perl

$Id: bugsfilter,v 1.31 2002/07/31 04:06:22 rt Exp rt $

use strict;

– CONFIGURATION –

my $HOME = “/opt/rt3/mail/”;

I am guessing you meant /opt/rt3 as $HOME

$ENV{‘HOME’} = $HOME;
my $maildir = “$HOME/Mail/”;

use Mail::Audit qw(KillDups);
use Mail::SpamAssassin;
$Mail::Audit::KillDups::dupfile = “$HOME/.msgid-cache”;

my @defaults = qw(your-rt-owner);

What would be the default value of rt-owner ?

I am ready to test it. Except I am not sure what would the default value of
rt-owner. I am runnign RT-3-0-5

Please help

[…]

I will give this a shot

Thanks a lot

Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

10

Hi All

I know Jesse is extremely busy. However anyone else used this setup and have
answer to the following question ? I installed the modules required for this to
run. Now I am stuck here. What would be the default value of rt owner in this
next line ?

my @defaults = qw(your-rt-owner); [excerpted from the following code…]

ThanksOn Sun, 21 Sep 2003, Asif Iqbal wrote:

On Wed, 17 Sep 2003, Asif Iqbal wrote:

On Mon, 15 Sep 2003, Jesse Vincent wrote:

I use the following tool to do my spam filtering in front of RT.
It uses Mail::Audit and Mail::Spamassassin. It can, in fact, be run in
front of any program that receives mail through a pipe in your
/etc/aliases file. You’ll need to make sure it can write to its temp
directories and your spamassassin setup is as you like it.

Rob Spier wrote this tool for perl.org and I adapted it for RT3.
I’m eternally grateful. It’s made my life suck much less.

in /etc/aliases, I’ve got this:
rt-3.0-bugs: “|/opt/bestpractical.com-rt3/bin/mailaudit /opt/fsck.com-rt3/bin/rt-m
ailgate --queue ‘rt3’ --action ‘correspond’ --url http://rt3.fsck.com/”

mailaudit is this:

#!/usr/bin/perl

$Id: bugsfilter,v 1.31 2002/07/31 04:06:22 rt Exp rt $

use strict;

– CONFIGURATION –

my $HOME = “/opt/rt3/mail/”;

I am guessing you meant /opt/rt3 as $HOME

$ENV{‘HOME’} = $HOME;
my $maildir = “$HOME/Mail/”;

use Mail::Audit qw(KillDups);
use Mail::SpamAssassin;
$Mail::Audit::KillDups::dupfile = “$HOME/.msgid-cache”;

my @defaults = qw(your-rt-owner);

What would be the default value of rt-owner ?

I am ready to test it. Except I am not sure what would the default value of
rt-owner. I am runnign RT-3-0-5

Please help

[…]

I will give this a shot

Thanks a lot

Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

11

Hi All

I know Jesse is extremely busy. However anyone else used this setup and have
answer to the following question ? I installed the modules required for this to
run. Now I am stuck here. What would be the default value of rt owner in this
next line ?

my @defaults = qw(your-rt-owner); [excerpted from the following code…]

It’s an email address.

12

Hi All

I know Jesse is extremely busy. However anyone else used this setup and have
answer to the following question ? I installed the modules required for this to
run. Now I am stuck here. What would be the default value of rt owner in this
next line ?

my @defaults = qw(your-rt-owner); [excerpted from the following code…]

It’s an email address.

I used root as the rt-owner and in my /etc/aliases I put

support: |“/opt/rt3/bin/mailaudit /opt/rt3/bin/rt-mailgate --queue support
–action correspond --url http://webrt.arl.qwestip.net”

I noticed it created a file triggerfilt.log with 0 bytes in the /opt/rt3 ($HOME)
directory. But it is not creating any ticket anymore and no autoreply either

Jesse, I know you are busy. So I am hoping someone else in the mailing list may
be able to help me in the mean time. I am currently using just procmail to
filter

Thanks

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

13

Jesse’s script didn’t work out of the box on my system, and I needed
slightly different behavior, so I hacked it up a bit. Others working
on a redhat system or those who have similar installation problems
might find it useful. I put it up for download in case anybody else
can use it:

http://zettabyte.net/downloads/rt/rt-mailaudit

Feedback welcome, of course.

-Bill

smime.p7s (2.31 KB)

14

I am running amavis-new with spamassassin and have SA tag the spam
mails with SPAM. Ususally I use procmail to deliver these mails
into a separate caughtspam folder, but procmail doesn’t deliver rt
mails. Is there anyway I can keep things with a subject marked
SPAM from creating a ticket?

Anne

15

I am running amavis-new with spamassassin and have SA tag the spam
mails with SPAM. Ususally I use procmail to deliver these mails
into a separate caughtspam folder, but procmail doesn’t deliver rt
mails. Is there anyway I can keep things with a subject marked
SPAM from creating a ticket?

There’s some old stuff that Phil Homewood worked on at

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

that should hopefully give you a pointer in the right direction.

Niall