?ip=66.136.203.220>]
1.5 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see
<http://www.spamcop.net/bl.shtml?66.136.203.220>]
Any help would be appreciated.
Thanks,
Brad Hazledine <[
Thanks Seth, that did the trick.
Brad
On 15 Jan 2004, Seth wrote:
> If you run the attached email through SpamAssassin, it should flag as a
> HABEAS_VIOLATOR.
>
> Seth
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference
I was catching them with all of the other rules, I was just unsure as to
whether or not it was even checking the violator list. The sample that
Seth sent me came back positive so I know it is working.
Brad
On Thu, 15 Jan 2004, Christopher X. Candreva wrote:
>
> Rather that takeing out the Habea
Are you using the --mbox flag with sa-learn?
Brad
On Fri, 16 Jan 2004, Marcus Frischherz wrote:
> Hi!
>
> I use SA 2.61, exim 4.24 and WU imapd, I use IMAP4 and keep my mails on the
> server. The folders seem to be in the mbx format. When I run sa-learn on one of
> them it, sa-learn is busy f
On Wed, 21 Jan 2004, Spyros Tsiolis wrote:
> Hello list !
Hello.
>
> I am kinda new here chaps, so please bare with me.
>
> A simple question (which I didn't pose on the xmail forum in case I
> get flamed/cursed) :-)
>
> >From what it seems, one must let spamassassin know of what to filter
> as
Has anyone written a rule that catches mail supposedly sent by yourself to
yourself?
Example here...
Received: from WIN-SYEZX91ADBP ([61.50.222.200])
by fargo.caledoncard.com (8.12.10/8.12.10) with SMTP id
i0L6pDT5006761
for <[EMAIL PROTECTED]>; Wed, 21 Jan 2004 01:51:14
-0500
Me
I had the same problem and found out why.
The log has to be the current year only. The code inserts the current year
and my log went back to July. After I moved everything out prior to Jan
1st it worked fine.
Brad
On Thu, 22 Jan 2004, Vermyndax wrote:
> Hi Bob... Tried this and still got the s
That will teach me to RTFM.
Thanks.
Brad
On Wed, 21 Jan 2004, Matt Kettler wrote:
> Why not change your domain whitelist to a whitelist_from_rcvd command,
> instead of whitelist_from.
>
> You'll avoid the forgery problem outright.
---
The
>
> > Could someone help me cobble together a rule quickly to counteract the
> > attachments it's using. Something to catch test.zip, readme.zip and
> > body.zip (the most common ones it appears to be using at the moment).
>
If you go to John Hardin's site
http://www.impsec.org/email-tools/local
rophy pion extempore
throat cake sketch abundant coordinate
Brad Hazledine <[EMAIL PROTECTED]>
Caledon Card Services
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.
Excellent!!
Thanks for the help.
Brad
On Tue, 6 Jan 2004, Kenneth Porter wrote:
> I'm using this set of rules posted to the list last month. Drop this in
> /etc/mail/spamassassin as rnd_uc_char.cf.
---
This SF.net email is sponsored by: IB
How about giving the test a negative score? i.e. -20.0
Brad
On Thu, 8 Jan 2004, John Fleming wrote:
>
> I want to specify a text string in the Subject header such that if it
> exists, the msg will NOT be considered spam, no matter what else might be
> wrong with it.
-
I use the procmail sanitizer ...
http://www.impsec.org/email-tools/procmail-security.html
Been using it for years and it traps all of the garbage that people try to
send. Wonderful tool.
Brad
On Fri, 9 Jan 2004, Jeff Lasman wrote:
> We're being hit by MS security update emails. I know they'r
score HABEAS_SWE 0.0 in your local.cf
Brad
On Mon, 12 Jan 2004, SAtalk Mail User wrote:
> Hello All,
>
> I have been getting alot of HABEAS based spam and I have been reporting
> the spam to [EMAIL PROTECTED] But in the mean time I would like to
> figure out a way to either turn off the HABEAS
Hi,
You want http://kepler.acns.bethel.edu/~bjn/spamassassin/rnd_uc_char.cf
Works great!
Brad
On Wed, 14 Jan 2004, Hein Zelle wrote:
> Hello,
>
> (new to this list, so please notify me if this has already been
> discussed or should be posted elsewhere. I've checked the mailing list
> archive
15 matches
Mail list logo