Scott,
Will adding 64.94.110.0/24 to the ipfile block these?
BLACKLISTIP ipfile D:\IMail\Declude\ipfile.txt x 20
Sheldon
Sheldon Koehler, Owner/Partnerhttp://www.tenforward.com
Ten Forward Communications 360-457-9023
Nationwide access, neighborhood support!
Whenever you
Will adding 64.94.110.0/24 to the ipfile block these?
BLACKLISTIP ipfile D:\IMail\Declude\ipfile.txt x 20
No. The problem is that the E-mail isn't *coming* from 64.94.110.11, the
problem is that a response to the E-mail would be sent to 64.94.110.11.
On Sep 17, 2003, at 12:17 PM, Sheldon Koehler wrote:
Scott,
Will adding 64.94.110.0/24 to the ipfile block these?
BLACKLISTIP ipfile D:\IMail\Declude\ipfile.txt x 20
Bill posted this in response to my posting about being able to use
this...
Below is the right hand side test you can use
False positives will come from users that misspell their domain name in
their mail client. I have had that happen. There are also lots of
forms being used on Web sites that take the user's input and construct a
message using their address as the From in order to facilitate replies,
and I can
On Sep 17, 2003, at 2:59 PM, Matthew Bramble wrote:
False positives will come from users that misspell their domain name
in their mail client. I have had that happen. There are also lots of
forms being used on Web sites that take the user's input and construct
a message using their address
Since the address is bad, the bounce won't ever get to the sender. It's
pretty unfortunate.
I just had a client call the other week when I upgraded to a newer
version of Declude which I think started catching the misspelling in
MAILFROM where as it didn't before (if I recall the problem
Just so people are aware, Network Solutions just hours ago made the dumb
move of making all unregistered domains point to their web site. As a
result, very little E-mail will fail the MAILFROM test in Declude JunkMail
(only E-mail from addresses on recently expired domains, and domains not
Seems like the easiest solution is to block all email from domains that
resolve to 64.94.110.x The question is, how do we do this? (I'm still
learning... sorry if this is a stupid question.)
NS is going to make a lot of enemies doing this.
Just so people are aware, Network Solutions just
Any more than they already have?? Its not a stupid move at all (if you
NetSol). The make all of their money on the ignorance of newbies that
just don't know any better. Once people realize what lyin', cheatin',
stealin' scum they are...you get the idea.
Do all of the unregistered domains
Good call Keith. I don't know what the proper address would be, but
the following article says that it can be blocked:
http://biz.yahoo.com/ap/030915/internet_typos_1.html
If you were correct, you would probably have to do this in your DNS
server. Maybe set up reverse DNS for that block.
Ignore my earlier reverse DNS thoughts, that doesn't make any sense :)
I certainly have my moments.
I think the article is also wrong by saying that DNS could be used to
defeat this. I'm betting that providers like AOL are just simply
configuring that block of addresses to point to their own
For now I've added:
REVDNS 10 ENDSWITH sitefinder-idn.verisign.com
to at least be able to add some weight to e-mail messages that use bogus
domain names and resolve RDNS for 64.94.110.11 to
sitefinder-idn.verisign.com.
Bill
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
Oops, never mind, that's not going to work. Hmmm, back to the drawing board
on this one...
Bill
- Original Message -
From: Bill Landry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 15, 2003 7:18 PM
Subject: Re: [Declude.JunkMail] A slight increase in spam not getting
I think a better filter might be:
BODY 100 CONTAINS verisign
HEADERS 100 CONTAINS verisign
HELO 100 CONTAINS verisign
MAILFROM 100 CONTAINS verisign
REMOTEIP 100 CONTAINS verisign
REVDNS 100 CONTAINS verisign
ALLRECIPS 100 CONTAINS verisign
SUBJECT 100
Yep, that should certainly cover all of the
bases! ;-)
Actually, what we need is a hostname lookup
filter:
HOSTNAME-ADDR
25 IS 64.94.110.11
If the hostname resolves to 64.94.110.11, then add
lots of weight to the message.
Bill
- Original Message -
From:
Matthew Bramble
Another good test for this would be a mail domain
"A" recordlookup filter:
MAILDOMAIN
25 IS 64.94.110.11
That, combined with the hostname "A" record lookup
filter below, would take care of this stupid VeriSpam issue.
Bill
- Original Message -
From:
Bill
Landry
To:
16 matches
Mail list logo
