> >> > >> 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 > > No. > > > what about those domains that have mx's point to 0.0.0.0? Are they > > legal too??? > > Technically they're legal, but practically they're broken. >
Would it be possible or would you consider making a bofh-option to refuse such addresses? RFC3330 states that certain addresses should not appear on the public internet. While it is technically legal and of course allowed in private networks, blocking should also be possible (with the exception if the DNS-server is located within the same pivate address-range perhaps). On 127.0.0.0/8 it states: "no addresses within this block should ever appear on any network anywhere" which is a pretty valid reason to block MX-servers/DNS-records which contain such an address. 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 [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
