On Wed, 2014-09-24 at 18:33 -0400, Sam Varshavchik wrote: > With a caveat. "Most specific" here means "octet boundary". I should clarify > that in the man page. > > makesmtpaccess uses Net::CIDR to expand out CIDR to even octet boundaries. > So, an entry for 192.168.0.0/22 is going to get replicated as four entries: > 192.168.0.*, 192.168.1.*, 192.168.2.* and 192.168.3.*.
So under what circumstances would this differ from the range definition as definded by the CIDR notation? -- Lindsay Haisley | "UNIX is user-friendly, it just FMP Computer Services | chooses its friends." 512-259-1190 | -- Andreas Bogk http://www.fmp.com | ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
