On Mon, Dec 06, 2004 at 02:22:19AM +0100, manu@... wrote: > Remy Card <Remy.Card@...> wrote: > > 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. Ok. I did not know about this since I am quite new to this list. > > 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. > > Sounds good. Someone test that fix? Note that this could be a bit more complex than what I wrote. After re-reading the code and thinking of it again, I believe that a fictive pending record should be allocated and initialized to be used as a parameter to peer_delete(). The fictive record should not be added to the pending list. R\ufffdmy
Message
Re: [milter-greylist] MX synchronisation bug?
2004-12-06 by Remy Card
Attachments
- No local attachments were found for this message.