Gerald V. Livingston II wrote:
I'm working with Jared Watkins who's written the AmavisNewSQL plugin for
setting Amavisd-New + SpamAssassin per-user preferences.

Well, actually, Jared is doing all the work, I just keep find new and unique
ways to break things. ;-)

Since Squirrelmail uses the IMAP server to authenticate logins (good idea
since it's connecting to the IMAP server) it allows username/password pairs
to be in any form that the IMAP server accepts.

This appears to be creating a problem for Squirrelmail user prefs info in
certain cases. We (Sysmatrix.net) are moving from a really bad Windows based
mail server to a combination of:

PostFix
Amavisd-New
SpamAssassin
ClamAV
Courier IMAPd
Courier POP3d
Courier AuthDaemon
SquirrelMail
MySQL feeding info to ALL of it

FYI, this plugin also works very well in that kind of system:

http://www.squirrelmail.org/plugin_view.php?id=167

I first had SQM set up using file based user prefs in $data_dir while I was
getting all the other pieces to work together. When it came time to get the
per-user SA settings working I discovered that SQM would error out with a
"Cannot open /user.pref.tmp" error. Not the fact that "/" is NOT my
$data_dir. I still have no idea why that was happening.

Cruise the mailing list archives and you will probably find a solution. I've seen this one on the lists before, and it wasn't that hard to track down IIRC.

So, after a suggestion from Jared I did what I had been planning to do
anyway. I went on and set up a squirrelmail database for user prefs and
address books. That solved the problem but brough another to light.

Courier IMAP is set up to allow login for our primary domain users as either
"username+password" or "[EMAIL PROTECTED]".

Why? This just makes things harder on you in the end IMO. The only place where users have to enter their username more than once is in webmail unless you have something else going on. If you use the vlogin plugin, it will automatically map "username" logins to "[EMAIL PROTECTED]" for you so you can tighten up Courier.

While working with
Jared to try to make sure the Amavis per-user entries were always save as
"[EMAIL PROTECTED]" we discovered that SQM *DOESN'T* follow this behavior.

If a user comes to the SQM page and logs in as "blooglefarf" -- SQM creates
user-pref entries in the squirrelmail database for "blooglefarf". If they
make changes to settings from the options pages they are saved just fine.

If that users comes back later and logs in as "[EMAIL PROTECTED]" SQM
does *NOT* read their old prefs entries. It creates a NEW user in the
database called "[EMAIL PROTECTED]" -- with all the default settings.

Of course. How is SM supposed to know that's the same user? You should be using vlogin.

http://www.squirrelmail.org/plugin_view.php?id=47

I've looked in the docs but I'm a bit addle headed from mail server tweaking
right now.
Would there be a way to get SQM, at the login page, to *either* add a default
domain to any login submitted without one OR to strip the domain off of any
user entry that DOES have one prior to passing he username info in for
further processing? I want usernames to consistently have one form or the
other so only one .pref file is created, and read, for each user but I cannot
turn off the ability to log in either way in the Courier AuthDaemon because
that would entail trying to explain to thousands of clueless users how to
change the login settings in all of their various remote email clients.

Thanks all,

Gerald


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
--
squirrelmail-users mailing list
Posting Guidelines: 
http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: [email protected]
List Archives: 
http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to