> > When going through my maillogs, I noticed various 546 > Routing loops. > > Upon a closer look, it appears that several bulk-mail domains have > > DNS-(A/MX)-records that point to 127.0.0.1, which can cause the > > beforemetioned routing loop. > > > > Is this a fault from my part (error in my courier > configuration)? If > > not, is there any way I can refuse mail from domains that > resolve to > > 127.0.0.1 without breaking anything? Doesn't pointing to reserved, > > private, etc. IPs in (public) DNS-records violate an RFC? > > I'm not aware of anything that technically prohibits such an > MX record. > > But they can be easily stopped. You must enable > BOFHCHECKDNS, and put "badmx 127.0.0.1" in the bofh file. > The man pages give more information.
Thanks! Can I use whildcard in that expression, e.g. badmx 127.0.0.* And what about those domains that have mx's point to 0.0.0.0? Are they legal too??? Kind Regards, Sander Holthaus ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
