Hi! I am using spamassassin 3.2.5 on debian linux squeeze to filter emails
for my personal domain.
I'm sorry if this has been answered before, but i've looked at the SA
manpages as well as googled this but found very little information about
this feature.
I was wondering how to enable the
Hi,
In the last few days some spam messages have been able to elude the filters I
use. Upon checking the headers, it seems to be following the same pattern.
Left only a few headers to exemplify:
-
Received: from localhost (localhost [127.0.0.1]) by mx.company.com (Postfix)
with ESMTP id
Michael,
can we use the askdns.pm for SA 3.3 or do we have some missing dependencies?
(I noticed some rules in latest couple of saupdates:
20_dnsbl_tests.cf:askdns DKIMDOMAIN_IN_DWL
_DKIMDOMAIN_._vouch.dwl.spamhaus.org TXT /^([a-z]+
)*(transaction|list|all)( [a-z]+)*$/
On 2010/12/07 9:20 AM, Florescu, Dan Alexandru wrote:
My question is: shouldn't there be a rule to verify that the mail specified at To: header
actually corresponds to the one at Received: [...] for?
No, take this list for example. RCPT TO: will be your address, while
To: is
On 12/7/10 8:20 AM, Florescu, Dan Alexandru
alexandru.flore...@rompetrol.com wrote:
Hi,
In the last few days some spam messages have been able to elude the filters I
use. Upon checking the headers, it seems to be following the same pattern.
I just earned $31 in a few hours at home on
On Tue, 7 Dec 2010, Florescu, Dan Alexandru wrote:
Received: from localhost (localhost [127.0.0.1]) by mx.company.com (Postfix) with
ESMTP id 8BCA320EC86 for mym...@company.com;
To: somefakem...@somedomain.com
My question is: shouldn't there be a rule to verify that the mail
specified at To:
-Original Message-
From: Michael Scheidell
Sent: Saturday, November 06, 2010 2:59 PM
To: users@spamassassin.apache.org
Subject: Re: Spamhaus Whitelist
found out that below is a violation of the specs, and is NOT recommended
to be used.
I would assume that the specs detail tighter
Thank you for the answers.
@Jason Bertoch - I'll try to upgrade, although it will be a difficult task
(many corporate mails).
@Daniel McDonald - Nice rules, I'm going to integrate it too and see what
happens. Funny keywords :D - thanks.
@John Hardin - Your suggestion led me to a very good link:
On tir 07 dec 2010 15:11:41 CET, Peter Alex. wrote
Any help would be appreciated :)
upgrade to 3.3.1
but checking faked headers, hmm
--
xpoint http://www.unicom.com/pw/reply-to-harmful.html
Hello,
We are running DirectAdmin on CentOS 5.x 64bit, and I just installed
Spamassassin yesterday. It seems to be enabled and working for all
users virtual accounts, but not for our primary domain account. On a
side note, these are all accounts that were imported into DA from cPanel
from
On Tue, 2010-12-07 at 13:46 -0800, Kevin C. Connell wrote:
We are running DirectAdmin on CentOS 5.x 64bit, and I just installed
Spamassassin yesterday. It seems to be enabled and working for all
users virtual accounts, but not for our primary domain account. On a
side note, these are all
Karsten,
Given your comments, I agree, this does appear to be a DA or email issue on the
server.
Thank you!
-Kevin C.
Cell:(503) 936-4938
-- Sent from my Palm Pre
On Dec 7, 2010 2:44 PM, Karsten Bräckelmann lt;guent...@rudersport.degt;
wrote:
On Tue, 2010-12-07 at 13:46 -0800, Kevin C.
Sorry bubbie, send me a challenge and you go into the evil list, which
tends to be a permanent /dev/null redirect. This is iron clad on a
mailing list. Direct I may or may not consign. C/R is plain evil as I
have encountered it in the past. On mailing lists it's beyond evil as
it generates
13 matches
Mail list logo
