Nigel Kukard wrote: >>>> Will it be added to v2? >>>> >>>> >>>> >>>> >>> Could you describe the feature you're after in v2 including your use for it. >>> >>> Regards >>> Nigel >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.policyd.org/mailman/listinfo/users >>> >>> >>> >> whitelistdnsname as featured in policyd v1, the dns name or dns >> namespace of the client sending me mail. Snipped from the policyd 1.8 >> config file: >> " >> # ...this type of >> # whitelisting gives far greater power when it comes to >> # whitelisting ISPs or big companies which you know do not >> # house spammers." >> >> We have used v1 for a couple of years and we have a built up a list of >> whitelistdnsname's along the way. In other words, as long v2 doesn't >> provide the same feature we can't we can't switch to it, which is a >> pity since v2 looks very good and has a lot of new nice features. >> >> > I don't think you've read over the Policyd v2 documentation. > > To get the same functionality, add a policy and use the following as > describe in the documentation: > <SNIP> > whatever.example.com > This will match the reverse dns of the IP where the client is connecting > from. > - You can use * as a wildcard match against anything except the ., for > example hello.*.example.com . You can use * as much as you like. > - Specifying example.com will only match example.com > - Specifying .example.com will match anything.example.com and > fu.bar.example.com > > As a technical note, * is expanded into [a-z0-9\-_\.] and if . doesn't > prefix the specification it gets ^. All reverse dns specifications are > matched with end of line $ at the end. > </SNIP> > > Once you have a policy, add an ACL and just PERMIT the mail... you will > now bypass everything. Alternatively create more specific policies to do > what you need. > > Regards > Nigel > >
Hi. Sorry. I obviously didn't read that part, but I have used the popup boxes over the question marks, and the part about reverse dns is not listed as a valid entry there. At least on my installation. Anyway, when I make a policy with a policy group of domains as source, my internal domains as destination, I get this in my cbpolicyd.log: [2009/05/31-22:12:27 - 82459] [POLICIES] WARNING: [ID:10/Name:whitelistdnsname]=>(group:whitelist_dns_names): - Source '.google.com' is not a valid specification Regards, Arvinn _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
