Hi, >>>That would break backward compatibility. We could have an option that >>>change the comparison to an exact match, though. Do you want to >>>contribute it? That's rather simple. >> >>I think I can do that. > > > I suggest the exactmatch option. Hmm, I'd suggest to have this be the default. IMHO, the old behaviour seems counterintuitve to me. The only problem I can see with this is maybe with subdomains. Say, I want to allow all subdomains of xxx.yyy like aaa.xxx.yyy and bbb.xxx.yyy. Or, on an email addresses, say to allow aaa+bbb@... through if aaa@... is allowed. This should however be reduced to those special cases, not to any substring match that's in there. IMHO, it's perfectly OK to change the behaviour to only allow real subdomains of some "domain xxx.yyy" through, but deny anything that just happens to end with the same bytes, more or less by accident. Similar for email addresses. Noone in his right mind would rely on the old behaviour. Yes, there are reasons to drop backward-compatibility. Actually, IMHO, it should be dropped quite a bit more often... Ciao, Wolfgang -- ws@... Wolfgang Solfrank, TooLs GmbH
Message
Re: [milter-greylist] Re: "domain" configuration option
2005-02-11 by Wolfgang Solfrank
Attachments
- No local attachments were found for this message.