On Tuesday 29 July 2003 14:35, John McKinney wrote: > On Tue, 29 Jul 2003, MKlinke wrote: > Mike, > > > On Tuesday 29 July 2003 13:03, Michael Schwendt wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > While I appreciate your sentiment, it seems to be doing some good > > by letting these go to the list. It would seem at this point that > > the list server has some issues and the discussion is generating > > private email as well as public that can help to determine the > > problem. If the list admin feel this is no longer beneficial to > > have it in the public forum and has enough info to tackle the > > problem I'll be happy to let it die. > > > > Regards, Mike Klinke > > If you check your domain at dnsreport.com it shows that the reverse > lookup for 67.153.21.10 is not working. This would cause the problem > you are describing. Does your upstream provider handle reverse > lookups? > > Hope this helps. > John McKinney
Heh, my ISP periodically has reverse lookup issues but that won't create the problem we are having. There are too many of us that had exactly the same thing happen at the same time with regard to the list email and in each case that I have access to, the list e-mail server was trying to send mail to the A-record identified boxen rather than the MX record identified boxen. The simple fact that I am receiving mail from the list after the postfix was restarted, and as you pointed out, still won't reverse resolve, should indicate that the reverse lookup won't impact this problem. Thanks for looking! Mike Klinke -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
