Ok, so now I'll admit that there is something fishy going on with postfix delivering to A records instead of MX records. I'll keep looking and let folks know when I find something.
In the mean time, if anyone else notices postifix delivering to their domain A record instead of the proper MX, please let me know offline so I can get some kind of correlation. Regards, Matthew Galgoci On Tue, 29 Jul 2003, MKlinke wrote: > On Tuesday 29 July 2003 12:46, Matthew Galgoci wrote: > > > It's been at least that long since 67.153.21.10 mail server has > > > been the axsi.com mail server, probably closer to 5 months when it > > > was made primary according to the MX record. The 64.81.113.223 MX > > > record was added at the end of June, the 30th, and 67.153.21.10 was > > > demoted to secondary mail server on that day. Even if your DNS > > > cache wasn't updated to the new primary, 64.81.113.223, I can't > > > begin to guess how your server ever resolved 67.153.21.8 as > > > axsi.com's mail server. I guess we'll just have to chalk it up to > > > one of those inexplicable glitches unless your seeing this with > > > some of the other posters who have also lost list mail > > > > > > Regards, Mike Klinke > > > > I have seen postfix cache before, but not like this :( > > Well, offline, another subscriber just sent me a note that he saw > > "starting on the morning of the 23th they started trying to deliver to > the a-record host for my list signup, rather than the mx-record host. > late yesterday this appears to have been all they were trying to hit." > > and this appears to be what happened to me too, since a host lookup to > axsi.com will show 67.153.21.8 which is the A-record for axsi.com but > it is not the MX record! > > Regards, Mike Klinke > > > -- Matthew Galgoci "Dirty deeds, done dirt cheap" System Administrator Red Hat, Inc 919.754.3700 x44155 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
