On Wed, 2008-04-02 at 16:27, mouss wrote: > Joseph Brennan wrote: > > > > > > --On Wednesday, April 2, 2008 2:45 -0700 Loren Wilton > > <[EMAIL PROTECTED]> wrote: > > > >> Received: from k2smtpout06-01.prod.mesa1.secureserver.net > >> ([64.202.189.102]) > >> by mx-pigeons.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP id > >> 1jGWCE6yu3Nl34g0 > >> for <[EMAIL PROTECTED]>; Wed, 2 Apr 2008 02:39:00 -0400 (EDT) > >> Received: (qmail 12925 invoked from network); 2 Apr 2008 06:39:00 -0000 > >> Received: from unknown (HELO Pousada.com.br.secureserver.net) > >> (72.167.52.118) > >> by k2smtpout06-01.prod.mesa1.secureserver.net (64.202.189.102) with > >> ESMTP; 02 Apr 2008 06:39:00 -0000 > > > > > > Let me play dumb, because I don't understand the problem here. > > > > It looks to me like dynamic 72.167.52.118 submitted mail to its smtp > > server 64.202.189.102. Why is that bad? > > > > > > My understanding is that his server _is_ 72.167.52.118. his From > indicates pousada.com.br: > $ host -t mx pousada.com.br > pousada.com.br mail is handled by 10 mail.pousada.com.br. > $ host mail.pousada.com.br > mail.pousada.com.br has address 72.167.52.118 > > so he has a generic rDNS: > $ host 72.167.52.118 > 118.52.167.72.in-addr.arpa domain name pointer > ip-72-167-52-118.ip.secureserver.net > > and this will cause delivery problems nowadays. > > In addition, his server helos with Pousada.com.br.secureserver.net which > does not resolve. > > and > $ telnet 72.167.52.118 25 > ... > 220 Pousada.com.br.secureserver.net ESMTP > > so the hostname in the banner seems to be another one: > $ host Pousada.com.br.secureserver.net > Host Pousada.com.br.secureserver.net not found: 3(NXDOMAIN) > I use secureserver.net to host my domain name and I also run my own MTA. I don't suffer from this problem, so if he rearranges his setup so it is similar to mine the chances are the problem will go away.
As I said, Secureserver.net is my domain host. Apart from having the definitive DNS records it does just two things for me: - it forwards e-mail to my ISP's mail server - it forwards web requests to my website host. I run Postfix as my MTA. Its configured to forward all outgoing mail to my ISP's mail server with a 'relay_host' directive. Other MTAs will probably have equivalent rules available. This way my sending IP doesn't appear in dynamic/residential blacklists. He could try a similar setup fairly easily. My guess is that he's using the same system as me to receive mail but is failing to direct outgoing mail through his ISP's MTA. Martin
