From: Josh E. <jo...@en...> - 2004-12-14 18:16:02
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lionel Bouton wrote: | For one isolated user it takes a long time for auto-whitelist to kick in | (especially SQLgrey's domain-based one) because the greylister can't | learn from trafic to other users. You'll have a much better | auto-whitelist usage in an ISP environment. I actually have a number of live/active users on my test server, but I see your point. Of course, everyone gets different email, so I'm wondering how large the difference really is. | I think you can already use postfix to selectively use greylisting, see | the postfix online documentation, especially the chapter where it is | configured to greylist only specific source domains. Do you mean greylist for specific users or specific incoming email domains? This is what I was considering, a per-user opt-in approach. I just have to look into how to get Postfix to look up the policies to use. I can insert it before or after alias expansion with my setup (Postfix is so flexible :)), but I guess that's beside the point. | Then an ISP can launch sqlgrey in "optin" or "optout" mode and add to | its web interfaces some configuration pages that will allow its users to | subscribe to the service by adding/removing entries in the correct | sqlgrey tables. This is what I'll probably do, make a web interface, but I was thinking about using an SQL lookup in Postfix to get the policies (not sure if that is possible) and/or putting it in amavisd-new or something so you can have "trickle-down" organization-based policies. If this isn't possible, adding it to sqlgrey may be the only option, but I think it "belongs" in Postfix, personally. Anyway thanks for the response! Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBvyvwV/+PyAj2L+IRAt0HAJwIBPbZdok+fWfsp1Vkk7UqVbehXgCdHYaZ 4RuBdrSSxR9IC8P2lZmD02Y= =uaJ2 -----END PGP SIGNATURE----- |