Milter-greylist

> 
> I am testing the mxsync function and it is stable, but I have some 
> discrepancies in the databases.
> 
> If a host that is currently in the database, either greylisted or 
> auto-whitelisted, and is deemed ok for auto-whitelisting AND 
> the host is 
> NOT the same as before BUT in the same D-class network (I use 
> subnetmatch /24) the following happens:
> 
> server_1 updates its database correctly, but does not update the IP, 
> since it matches the subnetmatch. server_2, which we are syncing to, 
> writes a new entry with the current IP and does NOT remove 
> the old entry 
> which matches the subnetmatch. Please note that server_2 does 
> no actual 
> work, it only recieves mxsync-data.
> 

Hello,

The patch I submitted near a week ago is addressing exactly that problem.
On our site I am using it in production since than and the redundancy of the autowhitelisted entries from the same class D has been reduced from 76% to 0%.

Bests,
Attila