Thanks Daryl.
That error is now no more.
Cheers,
AK.
-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Monday, 18 June 2007 12:59 PM
To: Anthony Kamau
Cc: SpamAssassin Mailing List
Subject: Re: Problems with Received: header checks and ALL_TRUSTED
rule..
Anthony Kamau wrote:
I've checked my logs and noticed the following entry whenever I restart
the spamassassin service:
config: dup unknown type msa_networks, Mail::SpamAssassin::NetSet
Is this something I should be worried about?
As long as you don't have any users calling "clear_msa_networks
ECTED]
Sent: Wednesday, 13 June 2007 5:12 PM
To: Daryl C. W. O'Shea
Cc: SpamAssassin Mailing List
Subject: RE: Problems with Received: header checks and ALL_TRUSTED
rule...
Thanks a ton Daryl.
I've patched my SA 3.1.7 per [1] and it is working as expected.
Cheers,
AK.
C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Thursday, 14 June 2007 11:53 AM
To: Anthony Kamau
Cc: SpamAssassin Mailing List
Subject: Re: Problems with Received: header checks and ALL_TRUSTED
rule...
In any case, spamming people with backscatter in the form of NDRs from
your system is comp
eers,
AK.
-Original Message-
From: Kris Deugau [mailto:[EMAIL PROTECTED]
Sent: Friday, 15 June 2007 12:56 AM
To: users@spamassassin.apache.org
Subject: Re: Problems with Received: header checks and ALL_TRUSTED
rule...
Anthony Kamau wrote:
>
> Any chance you know of a quick and dirty
Anthony Kamau wrote:
Any chance you know of a quick and dirty method to implement sendmail AD
authentication? I did search during build of the sendmail box, but did
not find conclusive instructions to do so - possibly because I was under
immense pressure to get a spam identifier installed.
C
Anthony Kamau wrote:
3/ if exchange is configured to send a copy of received email to an
external account OR the message is destined for a non-existent mailbox,
exchange will initiate a connection with sendmail either for forwarding
mail or for NDR
4/ since the exchange box is now trusted via m
installed.
Cheers,
AK.
-Original Message-
From: Robert - eLists [mailto:[EMAIL PROTECTED]
Sent: Thursday, 14 June 2007 10:47 AM
To: users@spamassassin.apache.org
Subject: RE: Problems with Received: header checks and ALL_TRUSTED
rule...
AK,
The MTA should not accept email for non exis
>
> I've just discovered something rather interesting after I enabled the
> msa_networks feature in local.cf. What's happening is this:
>
> 1/ spam arrives at the sendmail box from someone who has used a
> non-existent email address in our domain
>
> 2/ spamassassin clearly marks this as spam,
Hey Daryl, et al,
I've just discovered something rather interesting after I enabled the
msa_networks feature in local.cf. What's happening is this:
1/ spam arrives at the sendmail box from someone who has used a
non-existent email address in our domain
2/ spamassassin clearly marks this as spam
blems with Received: header checks and ALL_TRUSTED
rule...
That's only available with 3.2, though, so you'll either need to patch
SA [1] or do something else [2].
Daryl
[1] http://people.apache.org/~dos/sa-patches/msa_networks.3.1
[2] http://wiki.apache.org/spamassassin/DynablockIssues
Anthony Kamau wrote:
Thanks Daryl.
I've done a little bit of reading on msa_netowrks and it appears I need
to upgrade to SA 3.2.x to get this added benefit - correct?
Yeah, I missed that you were using 3.1.7 in my first reply. If you
can't upgrade I think that the 3.1 patch for msa_networks
hony Kamau
Cc: SpamAssassin Mailing List
Subject: Re: Problems with Received: header checks and ALL_TRUSTED
rule...
Anthony Kamau wrote:
> How then can I tell spamassassin to fire the ALL_TRUSTED rule if the
> connecting host is on the trusted list and ignore further Received:
> header c
Daryl C. W. O'Shea wrote:
Anthony Kamau wrote:
How then can I tell spamassassin to fire the ALL_TRUSTED rule if the
connecting host is on the trusted list and ignore further Received:
header checks? I have read Mail::SpamAssassin::Conf help file but
cannot find the solution yet. I thought the
Anthony Kamau wrote:
How then can I tell spamassassin to fire the ALL_TRUSTED rule if the
connecting host is on the trusted list and ignore further Received:
header checks? I have read Mail::SpamAssassin::Conf help file but
cannot find the solution yet. I thought the whitelist_allows_relays
wo
All,
I have several remote users in a country well known to inject spam mail.
These users are connected via dialup links to our backend Exchange
Server and they are able to send email. The Exchange Server relays all
email to the front end mail server running Red Hat Enterprise Linux AS 4
and Spam
16 matches
Mail list logo
