------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=428
------- Comment #8 from graeme@??? 2007-06-20 12:11 -------
On Wed, 2007-06-20 at 12:06 +0100, ph10@??? wrote:
> ------- Comment #7 from ph10@??? 2007-06-20 12:06 -------
> There seem to be some anomalies, both in the patch and in the original code.
> The original includes /per_xxx in the key, but only if it is explicitly given.
> So the default is lacking it. Also, although per_cmd and per_rcpt are supposed
> to be synonymous, they are used as specified in the config, so could create two
> different keys. A bug in the new code makes it not quite compatible with the
> old: you insert "/ strict /" for example in the key, but the old code, since it
> uses what's given by the user, might have "/strict /" or even "/strict/". I
> propose to clean all this up and generate standardised keys. It will mean that
> old behaviour might be forgotten on an Exim upgrade, but I don't think this is
> a huge problem.
Thanks for looking, Phil.
Please note Bug #496 - spaces in the key cause exim_tidydb not to
process the ratelimit DB properly.
I don't believe that "forgetting" the ratelimit DB on an upgrade will
matter greatly, either *unless* people start to use it for greylisting
in which case the docs will have to caveat/note the changes greatly.
Graeme
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
