problem with AOL

hi,

(sorry for my poor english)

with the new configuration of my network, I have a problem sending
messages to the aol.com domain.

the architecture of the network is the following one:


----------- ----------- ------
192.168.2.x--------192.168.0.x---router-----internet
----------- ----------- --fw--

the mail server is in the 192.168.0.x network.

the problem: trying to send messages to any address of aol.com, I get
error messages of the type:

The original message was received at Tue, 13 Sep 2005 22:19:44 +0200
> from [192.168.2.179]
>
> ----- The following addresses had permanent fatal errors -----
>
> (reason: 221 SERVICE CLOSING CHANNEL)
>
> ----- Transcript of session follows -----
> ... while talking to mailin-04.mx.aol.com.:
> > > > DATA
> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html
> <<< 421 SERVICE NOT AVAILABLE
> ... while talking to mailin-03.mx.aol.com.:
> > > > DATA
> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html
> <<< 421 SERVICE NOT AVAILABLE

Nothing similar with any other e-mail address, receiving and sending.

I know that aol mail servers need the reverse dns service
(http://postmaster.aol.com/guidelines/standards.html)

is it possible that my problem is related to this ? what should I do ?

thanks in advance to all!


va

Re: problem with AOL

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-9488-1127904661-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Va writes:

>> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html
>> <<< 421 SERVICE NOT AVAILABLE
>> ... while talking to mailin-03.mx.aol.com.:
>> > > > DATA
>> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html
>> <<< 421 SERVICE NOT AVAILABLE
>
> Nothing similar with any other e-mail address, receiving and sending.
>
> I know that aol mail servers need the reverse dns service
> (http://postmaster.aol.com/guidelines/standards.html)

That's exactly what the URL in their error message says.

> is it possible that my problem is related to this ?

Of course it is. That's exactly what the URL, above, says.

> what should I do ?

Fix your reverse DNS.



--=_mimegpg-commodore.email-scan.com-9488-1127904661-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQBDOnWVx9p3GYHlUOIRAlINAJ4lFeXUwmjKWFVv232G0U6P0UTOIgCd HLzr
cLiepkGTs7J9BYB0JuCB0zg=
=5QGT
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-9488-1127904661-0001--

Re: problem with AOL

Va wrote in
news:pan.2005.09.28.08.40.23.475868@bastaspam.libero.it:

>...
> the mail server is in the 192.168.0.x network.

That doesn't matter, what matters is the public IP address the
internet sees when you connect through your router.

>...
>> ----- Transcript of session follows -----
>> ... while talking to mailin-04.mx.aol.com.:
>> > > > DATA
>> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html <<< 421
>> SERVICE NOT AVAILABLE ... while talking to mailin-03.mx.aol.com.:
>> > > > DATA
>> <<< 421-: (DNS:NR) http://postmaster.info.aol.com/errors/421dnsnr.html

Did you read this web page?

>> <<< 421 SERVICE NOT AVAILABLE
>...
> I know that aol mail servers need the reverse dns service
> (http://postmaster.aol.com/guidelines/standards.html)
>
> is it possible that my problem is related to this?

Yes, that's exactly what the web page above tells you.

> what should I do ?

Get your ISP to set up a valid PTR record for your public IP address.
If you don't have a static IP address, they should have set up
generic PTR names for all their dynamic IP address space, but
apparently they haven't done that.

If you can't get your ISP to set up proper reverse DNS, you need a
better ISP.

- Fred