> Sander Holthaus wrote: > > Would it be possible or would you consider making a bofh-option to > > refuse such addresses? > > Why don't you do what Sam already suggested on 2005-01-19?
I did. And it is working, but it is not a permanent and foolproof sollution. The problem is: Sam Varshavchik wrote: > Sander Holthaus wrote: > > Thanks! Can I use whildcard in that expression, e.g. badmx 127.0.0.* > > And > > No. Meaning to create a foolproof sollution, I would get a huge bofh-file (unmaintainable and will probably seriously slow down Courier). Second, I think that there are valid reasons to create a bofh-entry to disable certain addresses as MX's. If RFC 3330 states on 127.0.0.0/8 "no addresses within this block should ever appear on any network anywhere" and spammers are starting to abuse the fact that no-one blocks this address range in public DNS-records, why not make an easy way (bofh-option or wildcard expressions in badmx) to block these? The same can be said on other private address-spaces. If I know that I reach any network using private address-spaces, why should I allow someone to send mail whose MX-server is in such an address space? This can only be abused or point to configuration errors. 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
