Bug 1506 - SAproxy should allow separate per-user files
Summary: SAproxy should allow separate per-user files
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: obsolete (show other bugs)
Version: unspecified
Hardware: Other other
: P5 normal
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-20 06:32 UTC by Daniel Quinlan
Modified: 2004-07-27 15:09 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Quinlan 2003-02-20 06:32:14 UTC 
Option 1: per-account (DBs and user_prefs)
Option 2: per-computer (DBs and user_prefs)

Per-account might be the best way, but not all authentication methods
allow it.  Maybe we need to add user information to the proposed PROXY
extension to POP3.

Per-person configuration data (including manual whitelists) would
require a lot more work (maybe a web interface would be the way to go)
than per-account or per-computer auto-whitelists.
Comment 1 Daniel Quinlan 2004-07-27 23:09:02 UTC 
We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation
therefore we are unfortunately unable to continue supporting it as part of the
SpamAssassin project.