Scott,
I'll go to try your tool. Looking at the filter file I can see a lot of
interesting declude like filter commands that looks very very interesting.
Maybe people at declude could give a look to this filter files...
In addition I want to add:
Maybe you can add the following replacements for
We use it. For us the main benefit is to keep
spammers from forging our customers' domains. SPF tells us when the mail
server sending the email from one of our customer's domains is not ours.
Works very nicely, and also is used as anotherbit ofevidence to
other email admins (since they
My weighting system is
subject tag at 100, hold at 200, delete at 300.
- Original Message -
From: Markus Gufler [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 26, 2005 2:13 AM
Subject: RE: [Declude.JunkMail] Alternative drug spellings
Scott,
I'll go to try your
How does SPF tell you that a rouge server is
forging mail from one of your customers, if you server isn't receiving the
forged mail? I noticed the majority of other email admins arn't even Running
spf..
for example:
nremc.com
then, there are the 1,000,000,000,000 hosts that
don't even
That would require the receiving mail server to
check SPF. Many don't, but we find it useful.
Darin.
- Original Message -
From: William Stillwell
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 26, 2005 10:29 AM
Subject: Re: [Declude.JunkMail] DNS SPF Record
How does SPF
If he defines SPF records for his customers' domains where
he lists the authorized mail servers - then any mail that he receives supposedly
from his customer will be flagged/deleted if it does NOT originate from one of
the authorized mail servers.
there are the
1,000,000,000,000 hosts
Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail Standard.
Using the WHITELIST IP 66.155.125 in global.cfg (separated by spaces, not
tabs). Syntax seems identical to the one listed in the manual. However,
Junkmail is still running all tests on mail from this IP
I messed that up, it should be 66.155.125.0/24
Matt
Chris Anton wrote:
Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail Standard. Using the "WHITELIST IP 66.155.125" in global.cfg (separated by spaces, not tabs). Syntax seems identical to the one listed in
Chris,
That's not a valid entry, you only have three of the dotted quads and
the Global.cfg requires either a full IP or a CIDR range. For the class
C you would want to use 66.155.125/24.
Matt
Chris Anton wrote:
Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail
Matt,
Thanks, that fixed it right away.
-Chris
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
The way I understand it is that the server
receiving the email does an SPF query to your DNS server to see if you have an
SPF record defining that only mail from this domain should come from this mx or
ip4 address.
This doesnt work very well if the
receiving server doesnt do an SPF
I posted a new version with the 3 new obfuscations.
- Original Message -
From: Markus Gufler [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 26, 2005 2:13 AM
Subject: RE: [Declude.JunkMail] Alternative drug spellings
Scott,
I'll go to try your tool. Looking at
12 matches
Mail list logo
