Couple of things I found when we had a HDSL line.  AOL and others are
blocking based on the IP address.  If you have a cable internet connection,
even with IP space delegated, they will bounce the mail.  Best way to solve
this is to call AOL, be prepared to wait to talk to someone, and tell them
what's up and give them the mail server addresses.  They can whitelist your
servers which is what they did for us until we got a T1.

Unfortunately, with the massive amount of viruses and spam that come from
cable IP blocks, they are increasing being blocked on a wholesale basis
without regard to whether or not they are business blocks.

Rich

----- Original Message ----- 
From: "Jim Matuska" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 05, 2004 9:52 AM
Subject: Re: [Declude.Virus] OT Problems with emails to aol.com and
earthlink.net addresses


> Those are private internal addresses for users and as private addresses
> cannot have reverse entries.  Are you saying that because we use private
IP
> space (as it should be done to preserve IP address space) all our emails
> will be blocked by AOL and earthlink?  The email server itself has a
> registered IP address and reverse entry.
>
> Jim Matuska Jr.
> Computer Tech II
> CCNA
> Nez Perce Tribe
> Information Systems
> [EMAIL PROTECTED]
> ----- Original Message ----- 
> From: "Ncl Admin" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 05, 2004 9:42 AM
> Subject: Re: [Declude.Virus] OT Problems with emails to aol.com and
> earthlink.net addresses
>
>
> > No it isn't.
> >
> > Reverse DNS for 172.16.2.103
> > Generated by www.DNSstuff.com
> > Country: [Private IP]
> >
> > Preparation:
> > The  reverse DNS entry for an IP is found by reversing the IP, adding it
> to
> > "in-addr.arpa", and looking up the PTR record.
> > So, the reverse DNS entry for 172.16.2.103 is found by looking up the
PTR
> > record for
> >  103.2.16.172.in-addr.arpa.
> > All DNS requests start by asking the root servers, and they let us know
> > what to do next.
> > See How Reverse DNS Lookups Work for more information.
> >
> > How I am searching:
> > Asking i.root-servers.net for 103.2.16.172.in-addr.arpa PTR record:
> >        i.root-servers.net says to go to henna.arin.net. (zone:
> > 172.in-addr.arpa.)
> > Asking henna.arin.net. for 103.2.16.172.in-addr.arpa PTR record:
> >        henna.arin.net says to go to BLACKHOLE-2.IANA.ORG. (zone:
> > 16.172.in-addr.arpa.)
> > Asking BLACKHOLE-2.IANA.ORG. for 103.2.16.172.in-addr.arpa PTR record:
> > Reports that no PTR records exist.
> >
> > Answer:
> > No PTR records exist for 172.16.2.103. [Neg TTL=604800 seconds]
> >
> > Details:
> > BLACKHOLE-2.IANA.ORG. (an authoritative nameserver for
> > 16.172.in-addr.arpa., which is in charge of the reverse DNS for
> 172.16.2.103)
> > says that there are no PTR records for 172.16.2.103.
> >
> > To get reverse DNS set up for 172.16.2.103, you need to speak to your
> > Internet provider.  You could also
> > check with [EMAIL PROTECTED], who is in charge of the
> > 16.172.in-addr.arpa. zone.
> >
> > Note that all Internet accessible hosts are expected to have a reverse
DNS
> > entry (per RFC1912 2.1),
> >
> >
> >
> > At 09:33 AM 5/5/2004 -0700, you wrote:
> > >We have our own DNS servers and are providing reverse entries.  Our
> primary
> > >email server is enterprise.nezperce.org Is there anything in that which
> AOL
> > >would block?
> > >
> > >Jim Matuska Jr.
> > >Computer Tech II
> > >CCNA
> > >Nez Perce Tribe
> > >Information Systems
> > >[EMAIL PROTECTED]
> > >----- Original Message ----- 
> > >From: "Stan Buck" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Sent: Wednesday, May 05, 2004 9:12 AM
> > >Subject: Re: [Declude.Virus] OT Problems with emails to aol.com and
> > >earthlink.net addresses
> > >
> > >
> > >> AOL recently instituted a new policy of not accepting mail from
servers
> > >with
> > >> dynamic IPs.  As part of that, they do a reverse DNS and look for
> "dsl",
> > >> "adsl","dyn", etc and block your mail if one of them shows up.  We
had
> > >"dsl"
> > >> in ours, given to us by our ISP, and even though it's a business DSL
> line
> > >> with a fixed IP, they wouldn't take our mail (just piled up in the
> queue
> > >and
> > >> generated the message you see).  We had to contact our ISP and change
> our
> > >> name.
> > >>
> > >>
> > >>
> > >> ----- Original Message ----- 
> > >> From: "Jim Matuska" <[EMAIL PROTECTED]>
> > >> To: <[EMAIL PROTECTED]>
> > >> Sent: Wednesday, May 05, 2004 12:03 PM
> > >> Subject: [Declude.Virus] OT Problems with emails to aol.com and
> > >> earthlink.net addresses
> > >>
> > >>
> > >> This is a little off topic but maybe someone else on this list has
seen
> > >> this.  Recently every time anyone tries to send an email to an aol
> account
> > >> they get a message like the following:
> > >>
> > >> Delivery failed 20 attempts: [EMAIL PROTECTED]
> > >>
> > >> and for earthlink:
> > >>
> > >> Unknown user: [EMAIL PROTECTED]
> > >>
> > >> Additional RCPT TO generated following response:
> > >> 550 relaying to <[EMAIL PROTECTED]> prohibited by administrator
> > >>
> > >> this seems to be happening whenever anyone responds to an AOL or
> Earthlink
> > >> Account, the earthlink one is really weird to me since if a user is
> > >unknown
> > >> why would you get a relaying prohibited message, especially since
this
> > >> happens when our mailserver connects to earthlink's, I didn't think
> that
> > >> would create a relay problem.
> > >>
> > >> We are running the Declude 1.79 and Imail 8.10 (With HF1, and HF2).
> Could
> > >> this be related to the version of Imail we are running or is there
just
> a
> > >> problem with aol and earthlink servers?  Any thoughts?
> > >>
> > >> Jim Matuska Jr.
> > >> Computer Tech II
> > >> CCNA
> > >> Nez Perce Tribe
> > >> Information Systems
> > >> [EMAIL PROTECTED]
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> ---
> > >> [This E-mail was scanned for viruses by Declude Virus
> > >(http://www.declude.com)]
> > >>
> > >> ---
> > >> This E-mail came from the Declude.Virus mailing list.  To
> > >> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> > >> type "unsubscribe Declude.Virus".    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.Virus mailing list.  To
> > >unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> > >type "unsubscribe Declude.Virus".    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.Virus mailing list.  To
> > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> > type "unsubscribe Declude.Virus".    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.Virus mailing list.  To
> unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
> type "unsubscribe Declude.Virus".    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.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

Reply via email to