|
From: Michel B. <mi...@bo...> - 2005-06-07 15:44:53
|
Le Mardi 07 Juin 2005 17:26, Lionel Bouton a =E9crit : > > SQLgrey could clean connect entries when moving entries from "from_awl" > to "domain_awl". I think this is good, and wouldn't be a performance penalty as movements = to=20 domain_awl are quite rare... > There could be cases where the sender won't retry the=20 > connect entries, but if the src made it to domain_awl, the chances are > rather slim of this happening. And anyway it wouldn't matter if the connect entry has been deleted, and = is=20 not retried... > >2nd case sample > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > >(VERP-style, I saw something like this for real...) [...] > This one is less obvious. The only way would be to delete entries in > "connect" each time a message is allowed to pass (maybe not only for > AWLs but also for whitelists: if you update them you get the same > beahviour). For whitelists, it's less of a problem (IMHO) if entries remain in connec= t or=20 AWLs for a while before being purged by the cleanup task. I think deleting from connect each time a message is allowed to pass woul= d be=20 too much of a performance penalty. But I suggest instead that each time an address is moved from connect to=20 from_awl, connect should be purged not with : $self->delete_mail_ip_from_connect($sender_name, $sender_domain, $cltid); But by first calculating a "sender_truncated" that would be the sender_na= me=20 truncated to only its alphanumeric beginning /^[a-zA-Z0-9]+/ and using an= SQL=20 "like" to delete everything that begins with this (for same domain and IP= of=20 course). There would be a very little risk to delete a "corresponding" longer addr= ess=20 from the same IP and domain waiting in connect, but I think this would be= =20 very rare, and would only result in the delayed message being delayed a=20 little longer, but I'm sure it will happen once in years ;-) It would surely be much more efficient on the performance standpoint than= =20 trying to delete from connect each and everytime we accept a message... Cheers. --=20 Michel Bouissou <mi...@bo...> OpenPGP ID 0xDDE8AC6E |