Here you are:
Aug 23 11:35:43 server1 sendmail[31790]: k7IDbxwo003338:
to=<janephaley (at mark) aol.com>, delay=4+20:57:43, xdelay=00:00:02,
mailer=esmtp, pri=82200330, relay=mailin-04.mx.aol.com., dsn=4.0.0,
stat=Deferred: Bad file descriptor
Aug 23 11:35:51 server1 sendmail[9507]: k7LL8OF6001554:
to=<Madhatterchurch (at mark) aol.com>, ctladdr=<harry (at mark) fast-mail.net> (857/100),
delay=1+13:27:27, xdelay=00:00:00, mailer=esmtp, pri=26763998,
relay=mailin-03.mx.aol.com., dsn=4.0.0, stat=Deferred: Bad file
descriptor
Aug 23 11:35:54 server1 sendmail[9507]: k7LKIpp4029238:
to=<madhatterchurch (at mark) aol.com>, ctladdr=<harry (at mark) fast-mail.net> (857/100),
delay=1+14:17:03, xdelay=00:00:00, mailer=esmtp, pri=27212374,
relay=mailin-04.mx.aol.com., dsn=4.0.0, stat=Deferred: Bad file
descriptor
Aug 23 11:36:08 server1 sendmail[31790]: k7IDBguD031715:
to=<GSLBLUNDELL (at mark) aol.com>, delay=4+21:24:26, xdelay=00:00:05,
mailer=esmtp, pri=82570216, relay=mailin-04.mx.aol.com., dsn=4.0.0,
stat=Deferred: Bad file descriptor
Aug 23 11:36:17 server1 sendmail[31790]: k7ICbFOf026842:
to=<eastlifemagazine (at mark) aol.com>, ctladdr=<jane.withers (at mark) fast-mail.net>
(735/100), delay=4+21:59:02, xdelay=00:00:09, mailer=esmtp,
pri=82863835, relay=mailin-04.mx.aol.com., dsn=4.0.0, stat=Deferred: Bad
file descriptor
The mail server that was talking to AOL was server1.mainline.co.uk
This is set up for my users to relay mail - used to work fine until last
week.
It now seems to pick up the user's IP and do a reverse on that as well
as the actual server that is connecting to AOL
Thanks
Colin
> -----Original Message-----
> From: Oscar Zovo [mailto:zovo (at mark) nexus.ao]
> Sent: 23 August 2006 11:06
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:06528] Re: Mail relaying probs with AOL
>
> Do you have some maillogs (from your BQ box) with rejections
> from AOL?
> That would help. The delivery report doesn't show what mail
> server was talking to AOL.
>
> Maybe you may have some smart relay setup to the other server?
>
> regards,
> zovo.
>
> Colin Jack wrote:
> > Has anybody any ideas on this? My users are starting to get
> irate but
> > I can't see why the AOL servers are doing this. It only
> seems to be my
> > BQ box that is having problems relaying to AOL - and only
> to AOL. Is
> > it something in the way the BQ/C box structures the headers
> or something?
> >
> > Thanks
> >
> > Colin
> >
> >
> >> -----Original Message-----
> >> From: Colin Jack [mailto:colin (at mark) mainline.co.uk]
> >> Sent: 22 August 2006 09:13
> >> To: coba-e (at mark) bluequartz.org
> >> Subject: [coba-e:06509] Re: Mail relaying probs with AOL
> >>
> >> Hi Michael,
> >>
> >> You are not understanding the problem (or I am not explaining
> >> clearly)
> >>
> >> exchange.mainline.co.uk (84.45.131.144) has nothing to do
> with this,
> >> that is my office about 200kms from where my servers are
> colocoed ;)
> >>
> >> The server in question is server1.mainline.co.uk
> >> (212.21.100.75) and I'm happy that checks out okay.
> >>
> >> The problem is that stupid AOL are picking up the original
> connection
> >> to my mail server ... in other words the user has a
> dynamic IP of say
> >> 84.45.67.234 and connects to my server to relay mail. The
> AOL server
> >> tries to do a reverse lookup on the original IP
> >> (84.45.67.234) which of course fails.That is the problem.
> >>
> >> Regards
> >>
> >> Colin
> >>
> >>
> >>> -----Original Message-----
> >>> From: Michael Stauber [mailto:bq (at mark) solarspeed.net]
> >>> Sent: 21 August 2006 23:29
> >>> To: coba-e (at mark) bluequartz.org
> >>> Subject: [coba-e:06496] Re: Mail relaying probs with AOL
> >>>
> >>> Hi Colin,
> >>>
> >>>
> >>>> Our side is fine ... its only AOL that we are having
> >>>>
> >>> problems with ...
> >>>
> >>>> the rest of the civilised world like us ;)
> >>>>
> >>>> The problems is that AOL seems to be parsing all the
> >>>>
> >>> headers .... and
> >>>
> >>>> rejecting it because it finds the initial dynamic IP in
> >>>>
> >> the header.
> >>
> >>>> Test my server if you want ... 212.21.100.75
> >>>>
> >>> (server1.mainline.co.uk)
> >>>
> >>> According to ...
> >>>
> >>> http://www.dnsreport.com/tools/dnsreport.ch?domain=mainline.co.uk
> >>>
> >>> ... you indeed have reverse DNS records. Also everything
> >>>
> >> else checks
> >>
> >>> out just fine.
> >>>
> >>> What I find a bit irritating is this report ...
> >>>
> >>> exchange.mainline.co.uk claims to be host mainline.co.uk
> [but that
> >>> host is at
> >>> 212.21.100.75 (may be cached), not 84.45.131.144].
> >>>
> >>> ... but I guess I know what you're doing there. That
> >>>
> >> shouldn't be the
> >>
> >>> source of the problem either.
> >>>
> >>> According to the AOL error message you posted initially ...
> >>>
> >>> <<< 421-: (DNS:NR)
> >>> http://postmaster.info.aol.com/errors/421dnsnr.html
> >>> <<< 421 SERVICE NOT AVAILABLE
> >>> ... while talking to mailin-01.mx.aol.com.:
> >>>
> >>> ... the only other explanation I could come up with is that
> >>>
> >> AOL wasn't
> >>
> >>> able to resolve your R-DNS, although you have a valid one.
> >>>
> >> So whatever
> >>
> >>> the problem
> >>> is/was: I'd say it's pretty likely that it may not be your end at
> >>> fault there.
> >>>
> >>> --
> >>>
> >>> With best regards,
> >>>
> >>> Michael Stauber
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
>
>
>