Remy Card <Remy.Card@...> wrote: > I think that I have found a problem in the MX synchronisation code. > It seems to me that a tuple that is autowhitelisted for more time is not sent > to the peers. As I understand the code, milter-greylist tells the peers > about tuples that are removed from the pending list and added to the > autowhite list, i.e. mails that have been delayed and that are autowhitelisted > for the first time. Yes, this has been a known minor bug for a while. > I do not have a patch for this problem (the version of milter-greylist > that I use is quite different from the standard one and a patch against it > would be unusable by anybody but me) but I think that the problem could be > solved by adding a call to peer_delete() in autowhite_add() when an entry > is found in the autowhite list and its life time is prolongated, i.e. when > an entry is autowhitelisted for more time. The code could be similar to > the one in pending_check() when the greylist delay is over, I think. > > Comments, anyone? Sounds good. Someone test that fix? -- Emmanuel Dreyfus Il y a 10 sortes de personnes dans le monde: ceux qui comprennent le binaire et ceux qui ne le comprennent pas. manu@...
Message
Re: [milter-greylist] MX synchronisation bug?
2004-12-06 by manu@netbsd.org
Attachments
- No local attachments were found for this message.