>We were thinking the same way but after second thougts we gave it up >for many reasons. > >Mainly reasons was > >1. uptime. ( if mysql dies imgate stops moving mail) >2. corrupted table ( see above) > >depending on the volume of domains this can drag down the performance >on server.
I know a high-volume site that uses multiple MXs of equal priority running postgrey/SQL and address_verify into a shared SQL server that holds the greylist and address_verify tables. yes, it's a single point of failure, but there hasn't been any apparent problem in slowdown vs local .map db's. The advantage of a single greylist and address_verify db's is that a legit MTA, once past greylist and SAV/RAV steps, can arrive at any MX and be accepted. With separate db's on each MX, the legit traffic has to get past the greylist and address_verify steps on each MX. Len
