Opened 16 years ago

Closed 14 years ago

Last modified 15 years ago

#239 closed enhancement (wontfix)

Per-domain bayesian database

Reported by: maia@… Owned by: rjl
Priority: low Milestone:
Component: amavisd-maia Version: 1.0.0 RC6
Severity: normal Keywords:


I'd like to make a request for a per-domain bayesian database. While a global database does keep the overall size to a mimimum, it doesn't work very well in our environment as a service provider.

Change History (2)

comment:1 Changed 15 years ago by dmorton

  • Milestone set to 1.1.0

This *may* be possible as early as 1.1, but I'm not sure...

comment:2 Changed 14 years ago by dmorton

  • Milestone 1.1.0 deleted
  • patch set to 0
  • Priority changed from normal to low
  • Resolution set to wontfix
  • Status changed from new to closed

Looking at the API for spamassassin, I don't think it is possible. The

username used by SA is established when SA is initialized, which is a very expensive operation. We obviously don't want to (possibly) re-initialize SA on every message... that might mean 4-5 seconds per message!

There is also a signal_user_changed() call, but the docs indicate that it closes the current set of databases and opens up the new ones. It may be talking specifically of filesystem based .spamassassin/ db's, but at any rate the api doesn't seem to have any support for per-user calls.

What needs to happen is a rewrite of much of SA to accept a user parameter to many of the functions. Unless that happens, I just don't see any way to incorporate this into Maia.

Closing as wontfix for now; if circumstances change and SA *can* handle this, we can reopen the ticket.

Note: See TracTickets for help on using tickets.