Kevin A. McGrail |
Re: Request for wiki access |
Tue, 01 Jan, 01:14 |
Fabio Sangiovanni |
URIDNSBL: how to query certain lists only? |
Fri, 04 Jan, 10:48 |
Alexandre Boyer |
Re: URIDNSBL: how to query certain lists only? |
Fri, 04 Jan, 13:22 |
Kris Deugau |
Re: URIDNSBL: how to query certain lists only? |
Fri, 04 Jan, 14:38 |
Daniel McDonald |
Re: URIDNSBL: how to query certain lists only? |
Fri, 04 Jan, 15:52 |
Kris Deugau |
Re: URIDNSBL: how to query certain lists only? |
Fri, 04 Jan, 17:12 |
Jeremy Morton |
Is the SpamAssassin wiki dead? |
Sun, 06 Jan, 12:49 |
Jeremy McSpadden |
Re: Is the SpamAssassin wiki dead? |
Sun, 06 Jan, 14:25 |
Fabio Sangiovanni |
Re: URIDNSBL: how to query certain lists only? |
Mon, 07 Jan, 09:18 |
s.@yacc.co.uk |
Does anyone recognise this? |
Mon, 07 Jan, 17:04 |
Ned Slider |
FPs on AXB_XMAILER_MIMEOLE_OL_B054A |
Mon, 07 Jan, 17:29 |
Rob McEwen |
ANNOUNCEMENT: update to ivmURI regarding surge in rarely-blacklisted domains spammers use from legit site that are "compromised" |
Mon, 07 Jan, 18:15 |
dar...@chaosreigns.com |
Re: ANNOUNCEMENT: update to ivmURI regarding surge in rarely-blacklisted domains spammers use from legit site that are "compromised" |
Mon, 07 Jan, 18:53 |
Alexandre Boyer |
Re: URIDNSBL: how to query certain lists only? |
Mon, 07 Jan, 19:02 |
Rob McEwen |
Re: ANNOUNCEMENT: update to ivmURI regarding surge in rarely-blacklisted domains spammers use from legit site that are "compromised" |
Mon, 07 Jan, 19:19 |
Kevin A. McGrail |
Re: HELO_DYNAMIC_IPADDR2 & HELO_DYNAMIC_SPLIT_IP hitting ham |
Mon, 07 Jan, 19:40 |
Kevin A. McGrail |
Re: the sa-rules tarball http://spamassassin.apache.org/ is ancient |
Mon, 07 Jan, 19:42 |
Kevin A. McGrail |
Re: Understanding KAM_MXURI |
Mon, 07 Jan, 22:14 |
Jeremy Morton |
Re: Is the SpamAssassin wiki dead? |
Mon, 07 Jan, 22:41 |
dar...@chaosreigns.com |
Re: Is the SpamAssassin wiki dead? |
Mon, 07 Jan, 22:49 |
Kris Deugau |
Re: FPs on AXB_XMAILER_MIMEOLE_OL_B054A |
Tue, 08 Jan, 16:27 |
Kevin A. McGrail |
Re: FPs on AXB_XMAILER_MIMEOLE_OL_B054A |
Tue, 08 Jan, 16:31 |
Ned Slider |
Re: FPs on AXB_XMAILER_MIMEOLE_OL_B054A |
Tue, 08 Jan, 19:20 |
Ned Slider |
Re: FPs on AXB_XMAILER_MIMEOLE_OL_B054A |
Tue, 08 Jan, 20:08 |
Jeremy Morton |
Added me to wiki contributors? |
Tue, 08 Jan, 22:25 |
Jeremy Morton |
Problem with SpamAssassin wiki formatting |
Wed, 09 Jan, 00:07 |
Ben Johnson |
Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 09 Jan, 22:14 |
Marius Gavrilescu |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 09 Jan, 22:29 |
RW |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 09 Jan, 22:36 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 00:03 |
wolfgang |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 00:36 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 01:58 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 02:13 |
Ned Slider |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 04:51 |
Tom Hendrikx |
spamc exit code for exceeding max size |
Thu, 10 Jan, 11:41 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 13:49 |
Tom Hendrikx |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 14:59 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 15:03 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 16:26 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 16:43 |
RW |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 16:49 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 16:51 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 17:18 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 17:48 |
RW |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 18:06 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 18:51 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 18:55 |
Tom Hendrikx |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 20:13 |
Tom Hendrikx |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 20:16 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Thu, 10 Jan, 21:12 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 21:43 |
Tom Hendrikx |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 22:16 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 22:33 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 23:17 |
Tom Hendrikx |
Re: spamc exit code for exceeding max size |
Thu, 10 Jan, 23:20 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 00:18 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 00:49 |
jdow |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 01:46 |
RW |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Fri, 11 Jan, 11:29 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 12:52 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 17:34 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 17:37 |
John Hardin |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 18:10 |
John Hardin |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 18:25 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 18:45 |
Tom Hendrikx |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 19:25 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Fri, 11 Jan, 20:25 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Fri, 11 Jan, 21:27 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 21:35 |
Martin Gregorie |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 22:30 |
Kevin A. McGrail |
Re: spamc exit code for exceeding max size |
Fri, 11 Jan, 22:44 |
jdow |
Re: spamc exit code for exceeding max size |
Sat, 12 Jan, 00:37 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Mon, 14 Jan, 18:24 |
RW |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Mon, 14 Jan, 19:49 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Mon, 14 Jan, 20:59 |
jdow |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Mon, 14 Jan, 23:36 |
jdow |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Mon, 14 Jan, 23:41 |
Noel |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 00:48 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 01:16 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 15:27 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 16:26 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 18:55 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 20:39 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 20:47 |
Bowie Bailey |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 21:05 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 21:27 |
Bowie Bailey |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 21:39 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 21:50 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 22:22 |
jdow |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 23:33 |
jdow |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Tue, 15 Jan, 23:38 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 01:23 |
jdow |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 04:45 |
Tom Hendrikx |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 07:02 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 15:49 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 15:58 |
John Hardin |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 16:00 |
Bowie Bailey |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 16:04 |
Noel |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 17:05 |
Ben Johnson |
Re: Calling spamassassin directly yields very different results than calling spamassassin via amavis-new |
Wed, 16 Jan, 18:18 |