I've been thinking about a new rule, either for Bayes or for more
normal processing, and I'd like the group's opinion. It has to do with
URLs in the message.
My original thought came to me when running SpamCop on a bunch of
messages. Taking a peek at the SC output I see that they whois the host
g that if I'm using spamc/d, I need to invoke
"| spamc -u $LOGNAME" from /etc/procmailrc?
TIA,
Brad Koehn
[EMAIL PROTECTED]
___
Don't miss the 2002 Sprint PCS Application Developer's Conferenc
Hey all,
I'm trying to use both SpamBouncer and SpamAssassin on my system, and
I'm having troubles.
My /etc/procmailrc file looks like this:
[Misc setup code snipped]
DROPPRIVS=yes
FILTER=yes
INCLUDERC=/usr/local/spambnc/sb.rc
#
# SpamAssassin
#
:0fw
| /us
Hey all,
While trying to upgrade to SA-2.41 via CPAN, I get the following error:
t/spamd_maxchildren.ok 27/33# Failed test 28 in
t/spamd_maxchildren.t at line 44
# t/spamd_maxchildren.t line 44 is: ok (spamcrun ("< data/spam/001",
\&patterns_run_cb));
I've verified that I have the la
I've noticed that my Received: headers seem to have disappeared, at
least in messages that are marked as spam. For example, my subscription
to this list came in with the following Received headers:
Received: from mail.koehn.com ([unix socket])
by mail.koehn.com (Cyrus v2.1.15) with LMTP;
Oh boy am I dumb!
Never mind, the Received headers are correct, it's the attached spam
message that shows the full chain of headers back to the originating
server. That whole Received... with Spamassassin thing through me for a
loop.
My bad, sorry for the waste of bandwidth.
Brad
Brad
Any spammer worth his salt runs his message through SA and other
popular anti-spam tools as best he can. Most of SA is relatively static
and slow to respond to changes in message content. The problem comes in
a few areas like checks against Received headers (since the spammer may
be using tho
t
should be good enough to authenticate.
Good luck!
Brad Koehn
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from
These kinds of things make me nervous: automatically downloading code
from another site over insecure protocols and running it locally,
possibly as root.
If we're going to distribute code, we really need some kind of signing
mechanism like PGP, otherwise the bad guys will just start hacking the
I've been getting a bunch of messages either squeaking by SA 2.61 or
nearly so (bigevil is nice), and added some rules to make them less
likely (I couldn't come up with a better name than glop, sorry):
describeglop_15 15 or more alphas in sequence
bodyglop_15 /[a-zA-Z]{15}/
s
10 matches
Mail list logo
