|
<astonishment>What, Matt, you get anal about your
work!?</astonishment>
Don't worry, I
won't make you the butt of any jokes.
Andrew
8)
Oops,
sorry. I'm not sure about netscape.com, but E-mail from that domain has
been quite rare in the past since they don't have hardly any employees, and
even if you had their primary reverse DNS entries, it's quite possible that
they send out as netscape.com from third-parties just like symantec.com does
(which is quite boneheaded for an AV/Anti-Spam provider). This is what
I'm using for netscape.com:
@netscape.com
.aol.
This might be a good example of a domain though that
really needs benefit of two columns, i.e.:
netscape.com
.aol.
I have no idea what they are doing for
their new ISP service as far as E-mail goes, but I would expect for them to
channel everything through aol.com just as they have with netscape.net.
I don't see why they would seek to establish a new network exclusively for
this new service.
FYI, I never found a reason for the following
entry:
aol.com netscape.net
Omitting it
hasn't caused any problems that I am aware of. I did of course though
use Bill's original list as the starting point for mine and for the most part
it remains intact except that I got anal about the @ thing
:)
Matt
Colbeck, Andrew wrote:
Well, Matt, that's a great example for Netscape.net, but Jeff was asking
about Netscape.com
So I guess to round out the conversation, here's the two entries in
spamdomains that everybody seems to have, to cover Netscape.net:
aol.com netscape.net
netscape.net aol.com
I'm pretty sure that we have Bill Landry to thank for the seminal work on
sd.txt from which everyone has benefitted (hey, credit where credit is due!)
Andrew 8)
-----Original Message-----
From: Matt [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 19, 2004 11:52 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] SPAMDOMAINS - Netscape.com
Andrew and Jeff,
Unfortunately Netscape.net is actually handled by aol.com when it is
outgoing (which is what matters in this case). I sometimes search my
known good E-mail for outgoing servers, or Google for it by looking for
header code along with the address and keeping in mind that a lot of
that stuff is forged especially in newsgroups. Here are the headers
from a test of my own account:
Received: from imo-d01.mx.aol.com [205.188.157.33] by mx1.mailpure.com with
ESMTP
(SMTPD32-8.05) id AE31AB9B0140; Mon, 19 Apr 2004 14:45:05 -0400
Received: from [EMAIL PROTECTED]
by imo-d01.mx.aol.com (mail_out_v37_r1.2.) id j.1b5.a579353 (16239)
for <[EMAIL PROTECTED]>; Mon, 19 Apr 2004 14:45:00 -0400 (EDT)
Received: from netscape.net (mow-d23.webmail.aol.com [205.188.139.164]) by
air-in03.mx.aol.com (v98.19) with ESMTP id MAILININ33-3f6f40841e2c327; Mon,
19 Apr 2004 14:45:00 -0500
Date: Mon, 19 Apr 2004 14:45:00 -0400
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: test
MIME-Version: 1.0
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: Atlas Mailer 2.0
X-AOL-IP: 24.195.119.188
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MailPure: ================================================================
X-MailPure: RFC-NOABUSE: Failed, listed in abuse.rfc-ignorant.org (weight
1).
X-MailPure: RFC-NOPOSTMASTER: Failed, listed in postmaster.rfc-ignorant.org
(weight 1).
X-MailPure: ================================================================
X-MailPure: Spam Score: 2
X-MailPure: Scan Time: 14:45:12 on 04/19/2004
X-MailPure: Spool File: D1e31ab9b01404b3e.SMD
X-MailPure: Server Name: imo-d01.mx.aol.com
X-MailPure: SMTP Sender: [EMAIL PROTECTED]
X-MailPure: Received From: imo-d01.mx.aol.com [205.188.157.33]
X-MailPure: Country Chain: UNITED STATES->destination
X-MailPure: ================================================================
X-MailPure: Spam and virus blocking services provided by MailPure.com
X-MailPure: ================================================================
Colbeck, Andrew wrote:
Jeff, the main problem with figuring out spamdomains entries is that you
really have to receive valid mail from the domain to really know.
If they have an SPF record, that's the easiest way to research them, but
you
can also try the website at http://www.SenderBase.org to see what they've
noticed. They've noticed one more host: dust.netscape.com
The problem with checking the MX record is that it is only for recording
inbound mail to Netscape.com, it doesn't necessarily say anything about
outbound mail from them, which is what you're after.
I suspect that your suggestion will work fine, as I think that they keep
their corporate domain for netscape.com separate from the customer business
as netscape.net ...
Andrew 8)
-----Original Message-----
From: Jeff Maze - Hostmaster [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 19, 2004 11:07 AM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] SPAMDOMAINS - Netscape.com
Hello,
I got a message that was "from" [EMAIL PROTECTED] but came from
RoadRunners networks. There isn't a netscape entry in my SPAMDOMAINS.TXT
file. I was just wondering what I would enter to make it so.
I did a NSLOOKUP on netscape.com and the MX record points to
mail.nescape.everyone.net. So the entry I would enter would be:
netscape.com netscape.everyone.net
Is this correct? Just want to make sure if there are more later. I
want to understand this so I don't keep asking. Thanks.. -Jeff
---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]
---
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.
---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]
---
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.
--
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================
|
