Does the Spamdomains tests use the mailfrom or the From: address to compare
to the revdns.
I'm betting it is the mailfrom address.
Thanks
Stu
---
[This E-mail was scanned for viruses by Declude EVA www.declude.com]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe,
Sent: Friday, January 06, 2006 10:50 AM
Subject: [Declude.JunkMail] Spamdomains test
Does the Spamdomains tests use the mailfrom or the From: address to
compare
to the revdns.
I'm betting it is the mailfrom address.
Thanks
Stu
---
[This E-mail was scanned for viruses by Declude EVA
Thanks Bill. I checked the archives and found one from Nov.28,2003 ... just
got it setup.
thanks again,
Larry Craddock
- Original Message -
From: Bill Landry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 28, 2004 12:34 AM
Subject: Re: [Declude.JunkMail] Spamdomains test
I think I need a little more detail on the spamdomains test. Here's the
entire explanation from the manual:
[This test will catch E-mail that is not coming from a mailserver that it
should be coming from. This test will only work if you set up a file listing
domains that you wish to be
But I'm sure I've seen discussion someplace with reference to lines
containing more than just a domain name in the spamdomains.txt file ... or
is that all that's needed besides enabling the test?
That's a new feature, that allows you to have an alias (for lack of a
better word) that can be
So a line example.com would require that any E-mail address from
@example.com must have a reverse DNS entry containing example.com.
However, if legitimate @example.com E-mail can also be sent from
@example.net, then you could have a line example.com example.net.
Scott, any thoughts
Using the dnsbl type of test and a custom zone, you could extend this
through DNS. For instance:
MPBL-SPAMDOMAINS dnsbl %REVDNS%.%RHSBL%.spamdomains.example.com
127.0.0.2 4 0
In your custom zone, you could construct records like so:
*.aol.com.aol.comA
127.0.0.1
TXT ( "Good
Using the dnsbl type of test and a custom zone, you could extend this
through DNS. For instance:
MPBL-SPAMDOMAINS dnsbl%REVDNS%.%RHSBL%.spamdomains.example.com
127.0.0.240
Interesting idea, Matt. Still way too much management compared to
SPF-compatible
I've been planing on trying this for about a week now, and I'm still
not convinced that it will work. From my standpoint though, this
represents a good way to remove a tad bit more processing and maintain
a system to be shared on multiple servers without having to update text
files.
This idea
Thanks everyone. Now that I understand how to use
the test, does anyone have a spamdomains.txt file that includes the entries for
the domains most commonly used that they could share?
Larry Craddock
- Original Message -
From: Larry Craddock [EMAIL PROTECTED]
Thanks everyone. Now that I understand how to use the test, does anyone
have a spamdomains.txt file that includes the entries for the domains
most commonly used that they could share?
Check the archives, Larry. I have posted
Scott, I am noticing SpamDomains test is not working consistently. Lots of
messages are being properly flagged, but many that should be flagged but are
not. I can provide samples, if you would like.
Thanks for looking into this.
Bill
---
[This E-mail was scanned for viruses by Declude Virus
Scott, I am noticing SpamDomains test is not working consistently. Lots of
messages are being properly flagged, but many that should be flagged but are
not. I can provide samples, if you would like.
Yes, samples would be very helpful. Also, what version are you running?
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
Scott, I am noticing SpamDomains test is not working consistently. Lots
of
messages are being properly flagged, but many that should be flagged but
are
not. I can provide samples, if you would like.
Yes, samples would be
14 matches
Mail list logo
