<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 10: Support for multiple users/accounts</title><link href="https://sourceforge.net/p/spamato/dev/10/" rel="alternate"/><link href="https://sourceforge.net/p/spamato/dev/10/feed.atom" rel="self"/><id>https://sourceforge.net/p/spamato/dev/10/</id><updated>2006-06-14T10:02:57Z</updated><subtitle>Recent changes to 10: Support for multiple users/accounts</subtitle><entry><title>Support for multiple users/accounts</title><link href="https://sourceforge.net/p/spamato/dev/10/" rel="alternate"/><published>2006-06-14T10:02:57Z</published><updated>2006-06-14T10:02:57Z</updated><author><name>Keno Albrecht</name><uri>https://sourceforge.net/u/kemil/</uri></author><id>https://sourceforge.net44939d66d51aafff28d3bc1155a2a61cd8e31411</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, Spamato is restricted to a single user. All&lt;br /&gt;
messages are handled as if they have been sent to a&lt;br /&gt;
single user or account. Even the Spamatoxy, that allows&lt;br /&gt;
access even from several users, "shares" one instance&lt;br /&gt;
of Spamato. This is only sub-optimal as users (and&lt;br /&gt;
event different accounts of one user) might differ&lt;br /&gt;
significantly from each other.&lt;/p&gt;
&lt;p&gt;To allow different users to use a single Spamato&lt;br /&gt;
instance, we have to enable the plugin system to&lt;br /&gt;
support multiple users. All plugins must access their&lt;br /&gt;
data from a new "user-aware session object".&lt;br /&gt;
Additionally, plugins must take into account this new&lt;br /&gt;
behavior---they, cannot store global variables or state&lt;br /&gt;
information outside the session object.&lt;/p&gt;
&lt;p&gt;Here are some additional ideas just to log them for&lt;br /&gt;
future consideration:&lt;/p&gt;
&lt;p&gt;Multi-user/account support should be optional. For&lt;br /&gt;
easier handling, a user should also be able to choose&lt;br /&gt;
the old way. That is, for instance, if accounts aren't&lt;br /&gt;
that different, the user might want to have a single&lt;br /&gt;
session or rather to share knowledge among account&lt;br /&gt;
session as before. This would also ease administration&lt;br /&gt;
if we want to run a Spamatoxy for several users with&lt;br /&gt;
the same settings.&lt;/p&gt;
&lt;p&gt;There will be several problems to be solved: For&lt;br /&gt;
instance: How to configure such a system? Using the&lt;br /&gt;
web_config with several users, we might have to add a&lt;br /&gt;
'login' since users shouldn't be able to change other&lt;br /&gt;
users' settings. How to distinguish between multiple&lt;br /&gt;
users and multiple accounts for a single user? How to&lt;br /&gt;
share sessions/data between users/accounts? And how to&lt;br /&gt;
configure all this?&lt;/p&gt;
&lt;p&gt;To allow all this, it would also be necessary to update&lt;br /&gt;
the add-ons. A user with multiple accounts using&lt;br /&gt;
Thunderbird or Outlook should be able to modify its&lt;br /&gt;
settings for different accounts. But it shouldn't be&lt;br /&gt;
more difficult than with one account.&lt;/p&gt;
&lt;p&gt;We can probably have a special implementation for&lt;br /&gt;
multiple users and multiple accounts for a single user.&lt;br /&gt;
We might also want to have different implementations&lt;br /&gt;
for the Spamatoxy (which might be used by several&lt;br /&gt;
users) and the other add-ons (S4O, S4T, S4M). We might&lt;br /&gt;
even end up with an integration version for mail servers.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>