On Sat, 21 May 2005 03:14:47 -0700 p dont think wrote: > Gerald V. Livingston II wrote:
> > 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 Won't work. It's why Jared wrote his. SA only reads SQL per-user prefs if it is being run in spamd/spamc daemon/client mode. Amavisd-new doesn't use the spamc/spamd pair, it loads Mail::SpamAssassin as a module into its own daemon mode. I'd rather use the SA per-user prefs because they offer more options than Amavis does (like letting our english-only customers block foreign character sets or changing whether to encapsulate spam or turn dcc/razor on/off). But then I'd have to also set up a different delivery method wrapped around maildrop or procmail delivering into virtual mailboxes adding another layer of complexity that I don't want. > > 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. I googled it and found three or four different possible causes. Then I decided I'm not really all that worried about it because using MySQL works and is what I was planning to do all along, I just hadn't gotten to it at that point. > > 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. See the last sentence of my original message. ISP customers are a 'reactive' group and on average know very little about computers and the internet. If we make a change in our system that requires them to make a single change in a single part of their setup we would suffer about a 30% loss of our customer base. They can't understand how to change a single setting so they cancel their account with us and move to another ISP where they get to go through a set of step-by-step instructions to set up everything in a linear fashion without having to find a specific configuration item. No, I'm not exagerating. We are a dial-up ISP and we lost about 30% of our userbase 2 years ago when we dropped one of our POP providers because we were having constant radius issues with their numbers. 30% of our customers went to other providers rather than follow a simple set of instructions to locate and change the phone number in their dial-up-networking properties --- and most of those were customers who had been complaining about repeated failed connections (due to the upstream radius issues) so the change we made would have solved their problems. The current mail server is set up so it ONLY allows authentication using the "username+password" method for our primary domain. Any subdomains on the mail server have to use the [EMAIL PROTECTED]" method. I have to make sure both methods work for authenticating to the POP3 daemon and for SMTP authentication for outgoing mail. > > 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. I wasn't sure how much info SQM gets from the Authentication deamon when a login occurs. The Authd only actually authenticates from the database using the full "[EMAIL PROTECTED]" --- but if there is no "domain.tld" part it adds a default domaon before querying the database. I didn't know if it reported back to PhP simply "the connection you requested is OK" or "the connection for '[EMAIL PROTECTED]' is OK". > http://www.squirrelmail.org/plugin_view.php?id=47 I hadn't looked at that one yet because I'm currently only putting a single domain on this server. It's in "virtual hosting" format only to avoid needing /etc/passwd entries for every user. I'll grab it now to see what I can do with it. thanks, 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
