Sounds like they need a new admin... It's likely they are using NAT through a firewall, as someone else pointed out.
If it's an isolated case, and you don't feel like either fixing his DNS issues, or teaching him how to correctly configure DNS, I would just whitelist their IP and be done with it. That is, if you trust their mail, which, I would be hesitant of a "Windows" admin that can't configure DNS *AND* has an Exchange server under their control. Michael J. Colvin NorCal Internet Services www.norcalisp.com > -----Original Message----- > From: [email protected] [mailto:spamdyke-users- > [email protected]] On Behalf Of Faris Raouf > Sent: Friday, February 12, 2010 6:45 AM > To: 'spamdyke users' > Subject: [spamdyke-users] Exchange server Webmail for Outlook and A > records > > I had a very interesting conversation with a sysadmin who is in charge of > mail server whose emails our Spamdyke servers are rejecting because their > PTR has no corresponding A record (reject-unresolvable-rdns in > spamdyke.conf). > > The sending server runs MS Exchange 2007, and apparently when they add an > A > record for their PTR, their webmail (whether accessed externally or > internally) stops working. > > Does anybody have any experience of Exchange 2007? Does this make any > sense? > It doesn't to me. But I don't know enough about how Exchange works and how > its webmail thing works either to make any real comment. My only guess is > that it has something to do with the exchange server using a local private > IP for the webmail server internally, and when this is effectively changed > to a public IP it all falls down? I don't know why they can't just change > the external DNS and leave the internal stuff alone, unless the Exchange > server actually runs the external DNS too? Argh. It makes my head hurt > just > thinking about it. > > Obviously we can whitelist them - problem solved - but not everybody will > do > that for them and they are going to face some serious problems before long > as more and more ISPs and mail servers come to reject on an unresolvable > RDNS. > > And if it is a generic problem with Exchange then that's going to be a > bigger problem for us and others. > > Faris. > > > > > > > > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
