Hi,
I searched the list and found this rule to catch URL with single space
(www.ledrx .com). Please help me in modifying this rule to catch URL with
double space (www.superveils . com).
body URL_WITH_SPACE m/\bhttp:\/\/[a-z0-9\-.]+[!*%, -]+\.?com\b/
Thanks.
-Original message-
From:
On Thu, 08 Mar 2007 03:24:20 +, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,
I searched the list and found this rule to catch URL with single space
(www.ledrx .com). Please help me in modifying this rule to catch URL with
double space (www.superveils . com).
body URL_WITH_SPACE
The following was the signature of an advance fee fraud attempt:
Yours Respectfully,
Capt Aziz Hassan
NOTE; I AM NOT AN ISLAMIC EXTREMIST, I AM MODEST.
I breathe a sigh of relief. Fancy an extremist spammer; what a horrible
thought! :-)
-R
On Thu, 8 Mar 2007, [EMAIL PROTECTED] wrote:
I searched the list and found this rule to catch URL with single space
(www.ledrx .com). Please help me in modifying this rule to catch URL
with double space (www.superveils . com).
body URL_WITH_SPACE m/\bhttp:\/\/[a-z0-9\-.]+[!*%, -]+\.?com\b/
Luis,
OK, but the point is that I run SA trough AMaViS, so procmail recipes
aren't the answer. Thanks a lot, I suppose I should create some type of
whitelist in AMaViS to avoid SA.
As this mailing list use VERP sender envelope addresses,
you need to use regexp-based lookup table in
Jim Knuth writes:
Heute (08.03.2007/03:10 Uhr) schrieb Don O'Neil,
Thanks that did it... :-) sa-update works great now.
How often are rulesets updated? Should I set sa-update to run on cron daily?
This is indefinite. And no, not needed. Spare your ressources an
make it manually. ;)
On Thu, 8 Mar 2007, Jeremy Fairbrass wrote:
I just tested those three rules below, and none of them work with
www.superveils . com (ie. having a space both before and after that
dot).
Strange, it matches rule 3 with egrep:
echo 'www.superveils . com' | egrep 'www[\ ]+?\.([a-z0-9\-\ ]?)+\.[\
Strange indeed - not for me - I'm using The Regex Coach from
http://weitz.de/regex-coach/ which so far always does a perfect job of
testing regex. Maybe it's wrong on this case - who knows! :)
BTW I'm not sure it's necessary to escape the space character within the
[square brackets] - I think
BTW I'm not sure it's necessary to escape the space character within the
[square brackets] - I think it's acceptable to just have [ ] without the \
inside. Although it doesn't do any harm having it in there either...
No need to escape the space. Even better to include both space and tab
pls unsubcribe me from this group
On Tuesday 06 March 2007 23:53, Mark Martinec wrote:
Btw, the following warnings (in v320) seem excessive, a null return path
(aka envelope sender) is normal and constitute few percent of all mail:
message: envelope_sender_header '' is not an FQDN - ignoring
at
Nick Leverton writes:
On Tuesday 06 March 2007 23:53, Mark Martinec wrote:
Btw, the following warnings (in v320) seem excessive, a null return path
(aka envelope sender) is normal and constitute few percent of all mail:
message: envelope_sender_header '' is not an FQDN - ignoring
Hi Guys,
Can anyone provide me a process how to integrate the spamassassin with postfix.
I tried many times. But I cannot identify why I always get the following logs.
Mar 10 05:38:26 gateway postfix/qmgr[13424]: 01A8217FBD: to=[EMAIL
PROTECTED], relay=none, delay=25610, delays=25610/0.01/0/0,
I recently (~26 Feb 2007) submitted two RBL blocks to SORBS
(85.93.37.128-85.93.37.191 and 86.212.217.0-86.212.217.255). My emails
created 2 tickets on rt.sorbs.net, but the tickets remain new, even
though the autoreply said they should be handled in 24-48 hours. The
tickets did get moved from
usha chowdary wrote:
pls unsubcribe me from this group
From the headers:
list-unsubscribe: mailto:[EMAIL PROTECTED]
Banyan He wrote:
Hi Guys,
Can anyone provide me a process how to integrate the spamassassin with
postfix. I tried many times. But I cannot identify why I always get
the following logs.
Mar 10 05:38:26 gateway postfix/qmgr[13424]: 01A8217FBD:
to=[EMAIL PROTECTED] mailto:[EMAIL PROTECTED],
On Thu, 8 Mar 2007, Banyan He wrote:
Hi Guys,
Can anyone provide me a process how to integrate the spamassassin with postfix.
I tried many times. But I cannot identify why I always get the following logs.
Mar 10 05:38:26 gateway postfix/qmgr[13424]: 01A8217FBD: to=[EMAIL
PROTECTED],
From the too little, too late department:
The US Securities and Exchange commission has suspended trading
of 35 penny stocks that were linked to stock spam.
http://news.yahoo.com/s/nm/20070308/wr_nm/spam_sec_dc_3
the SEC is investigating the companies themselves as well as outsiders
I am having some serious probles with SpamAssassin. For example check out my
logs:
Mar 8 14:42:32 penguin spamd[15553]: spamd: connection from localhost
[127.0.0.1] at port 52601
Mar 8 14:42:32 penguin spamd[15553]: spamd: setuid to root succeeded
Mar 8 14:42:32 penguin spamd[15553]: spamd:
On Thu, Mar 08, 2007 at 11:44:31AM -0800, Andrew Rosolino wrote:
Mar 8 14:42:32 penguin spamd[15553]: spamd: setuid to root succeeded
Mar 8 14:42:32 penguin spamd[15553]: spamd: still running as root: user not
specified with -u, not found, or set to root, falling back to nobody at
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall. It's underpowered and is no
longer able to keep up with the I/O demands of our two MXes. During
the day, uptime on the machine plateaus at about 5-7, and iowait
percentage rides at about
Chris St. Pierre schrieb:
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall. It's underpowered and is no
longer able to keep up with the I/O demands of our two MXes. During
the day, uptime on the machine plateaus at about 5-7, and iowait
-Messaggio originale-
Da: Chris St. Pierre [mailto:[EMAIL PROTECTED]
Inviato: giovedì 8 marzo 2007 23.33
A: users@spamassassin.apache.org
Oggetto: Make Bayes more efficient?
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall.
At 14:33 08-03-2007, Chris St. Pierre wrote:
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall. It's underpowered and is no
What engine are you using for MySQL? InnoDB is better for
Bayes. Did you look into MySQL optimization?
At 14:33 08-03-2007, Chris St. Pierre wrote:
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall. It's underpowered and is no
What engine are you using for MySQL? InnoDB is better for Bayes. Did you
look into MySQL optimization?
Why does a directory need execute permissions?
Theo Van Dinter-2 wrote:
On Thu, Mar 08, 2007 at 11:44:31AM -0800, Andrew Rosolino wrote:
Mar 8 14:42:32 penguin spamd[15553]: spamd: setuid to root succeeded
Mar 8 14:42:32 penguin spamd[15553]: spamd: still running as root: user
not
Thanks guys everything is good now =D!
Phil Barnett wrote:
On Thursday 08 March 2007 19:46, Andrew Rosolino wrote:
Why does a directory need execute permissions?
Because you can't use it and you can't move into it unless it does.
--
Balmer is basically saying: We know there's a
On Thu, Mar 08, 2007 at 04:46:30PM -0800, Andrew Rosolino wrote:
Why does a directory need execute permissions?
For directories, the x bit makes it traversable. That means if
/foo/ has permissions drw-rw-rw-, then you can read (and write) the
directory but you can't get to any of any of the
Andrew Rosolino wrote:
Here is the permissions for the folder:
drw-rw-rw-2 root nobody 4096 Mar 8 14:35 spamassassin/
Directories should have RWX permessions, not RW.
In Directories, X takes on a different meaning, and refers to the
ability to list files in the directory..
On Thu, 8 Mar 2007, Matt Kettler wrote:
Directories should have RWX permessions, not RW.
In Directories, X takes on a different meaning, and refers to the
ability to list files in the directory.. Without that, apps can only
open files they already know the exact name of.
No the 'r' bit is
Chris St. Pierre schrieb:
We're sharing our Bayesian database (MySQL) between two MX nodes and
the database server has hit a wall. It's underpowered and is no
longer able to keep up with the I/O demands of our two MXes. During
the day, uptime on the machine plateaus at about 5-7, and iowait
31 matches
Mail list logo
