Milter-greylist

Hi,

	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.

	IMO, this means that milter-greylist does not tell the peers about
tuples that are already present in the autowhite list and that are
autowhitelisted for more time when a new mail with same IP, from and to is
received.  I think that this can introduce an unneeded delay if the primary
MX is unreachable: since peers do not know about the additional
autowhitelisting, the entry can expire on secondary MX while it still exists
on the primary MX.

	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?

	Cheers

		R\ufffdmy