Dave Goodrich wrote:
Ken Jones wrote:
"Charles J. Boening" <[EMAIL PROTECTED]> said
I also think spamc options should be stored in the same place.
Currently the spamc options can be set on the configure line.
We thought that would be a good place since the spamc options
are site wide. I thin
---
> From: Ken Jones [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 03, 2005 7:19 AM
> To: vchkpw@inter7.com
> Subject: [vchkpw] spamassassin development was spamassassin
> configuration
>
> > "Charles J. Boening" <[EMAIL PROTECTED]> said So let me see
Ken Jones wrote:
"Charles J. Boening" <[EMAIL PROTECTED]> said
I also think spamc options should
be stored in the same place.
Currently the spamc options can be set on the configure line.
We thought that would be a good place since the spamc options
are site wide. I think all the user prefere
>> This would handle both
>> the problem of if the user wants their mail scanned and the disposition
>> of the scanned mail.
> Yep.
If using SQL settings for Spamassassin, the user could also whitelist all
senders to avoid spam processing.
>> I also think spamc options should
>> be stored in the
> "Charles J. Boening" <[EMAIL PROTECTED]> said
> So let me see if I can summarize where this might be going. A lot has
> been talked about on this topic.
>
> Use the pw_uid/pw_gid to check and see if a user wants their mail
> filtered. I'd also suggest setting another bit for delivery. So we'd
