On Wed, Sep 13, 2006 at 03:42:12PM +0100, Dermot Paikkos wrote: > Does that mean the only way to whitelist senders is manually via the > local.cf as I have disabled user_prefers? If so, what would be the
If you want something specifically always whitelisted, yes, it needs a whitelist_* config somewhere. If user prefs are disabled, it would need to be in a site-wide config file, though not necessarily local.cf (*.cf is fine). > best method allow mortal users (via http) to whitelist senders. I had > been using `$f->add_address_to_whitelist ($addr)` but that seems to > specifically add them to the whitelist DB. There's no SA function that will force a whitelist/create a config file for you. If you have a web interface already, I'd add some code to allow users to paste in the headers of a message they want whitelisted. From there, you can parse out the information (using SA function if you like) to create a whitelist entry (try to do whitelist_from_rcvd, and only failback to whitelist_from if necessary since it's easily forged). I'd probably save that info in a DB or something, and then periodically update a cf file and restart spamd. Even better, if someone wants a sender whitelisted, do it in whatever you have calling SA if possible. -- Randomly Generated Tagline: "Windows and MacOS are products, contrived by engineers in the service of specific companies. Unix, by contrast, is not so much a product as it is a painstakingly compiled oral history of the hacker subculture." - N. Stephenson
pgpqE404cnS7J.pgp
Description: PGP signature
