Our mail server is flooded by such spams. Is this a new variant of spam?
Does any one have cracked a rule to catch this?
-Original Message-
From: braye64 [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 14, 2007 1:49 AM
To: [EMAIL PROTECTED]
Subject: IR1E1
Hillo2 41b
-Original
On 12-Apr-2007, at 02:22, Martin.Hepworth wrote:
1.3 NA_DOLLARS BODY: Talks about a million North American
dollars
Well, that's more than double the default score.
0.6 J_CHICKENPOX_48BODY: {4}Letter - punctuation - {8}Letter
OK, I thought Chickenpox was deprecated
Mário Gamito wrote:
Hi,
now, take one of the messages and run spamassassin -t on it and show
these tests (at the end of the report).
Strange, it has only 4.1 points, but is marked as SPAM!
not now, but it was marked as spam when it was delivered. maybe
dcc/razor (or spamcops?)
Hello,
I was not lucky to get information about how to whitelist IP Range
should it be something like
whitelist_from 172.16.
or
whitelist_from 172.16.0.0-172.16.255.255
or
whitelist_from 172.16.0.0/16
thank you
On Sat, April 14, 2007 10:31, Wael Shahin wrote:
whitelist_from 172.16.0.0/16
trusted_networks 172.16.0.0/16
whitelist_from is for email not for ip :-)
--
This message was sent using 100% recycled spam mails.
Opps,
looks like i totally messed up
thaks Benny
- Original Message -
From: Benny Pedersen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 14, 2007 1:17 PM
Subject: Re: whitelist_from ip_range
On Sat, April 14, 2007 10:31, Wael Shahin wrote:
whitelist_from
Jake Vickers wrote:
[ ${TMPDIR} ] || TMPDIR=${SA_DIR}/RulesDuJour; # Where we store old
rulesets. If you delete
I'm not talking about editing the script. I am talking about the config
file. Do you have /etc/mail/rulesdujour/config ?
Yes, I know that.
When I originally posted, I had
On 4/13/07, Gene Heskett [EMAIL PROTECTED] wrote:
Now, I *think* I have that X-Originating-Ip: 193.93.97.195 in my .procmailrc,
but it didn't fire. Odd...
Is that rule before or after the point at which you run the message
through spamassassin?
If after, it probably ddin't fire because
On Saturday 14 April 2007, Bart Schaefer wrote:
On 4/13/07, Gene Heskett [EMAIL PROTECTED] wrote:
Now, I *think* I have that X-Originating-Ip: 193.93.97.195 in my
.procmailrc, but it didn't fire. Odd...
Is that rule before or after the point at which you run the message
through spamassassin?
Using 3,1.8.
When feeding sa-learn with messages from stdin, I get this:
archive-iterator: invalid (undef) format in target list, 2
at /opt/csw/share/perl/csw/Mail/SpamAssassin/ArchiveIterator.pm line
724, STDIN line 1.
Is there a patch for this?
Thanks,
Alex
--
Apache SpamAssassin 3.2.0-rc2 is now available! This is a *PRERELEASE*,
not the full release of 3.2.0.
Downloads are available from:
http://people.apache.org/~jm/devel/
Downloading
---
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-rc2.tar.bz2
Hey,
I've just read 127.* is now always trusted in the new release of
SpamAssassin.
However, i have some mailinglists which are being handled with SmartList
(which runs on top of procmail). So, when a spammail hits this list, it
gets marked as spam (hopefully), but then it will be processed
Kshatriya wrote:
Hey,
I've just read 127.* is now always trusted in the new release of
SpamAssassin.
However, i have some mailinglists which are being handled with SmartList
(which runs on top of procmail). So, when a spammail hits this list, it
gets marked as spam (hopefully), but then it
13 matches
Mail list logo
