So far, I've set squirrelmail to $imap_auth_mech = 'login'; and now it seems users can logon no matter how their password is stored in the database... so hopefully I'm good to go.
________________________________________ From: Myers, Jon W Sent: Sunday, May 12, 2013 12:56 AM To: [email protected] Subject: RE: [qmailtoaster] courier to dovecot conversion Thanks for the re-assurance, Jeremy... Did the convert, and it works.. sort of.. It seems my old accounts cannot authenticate, but newer accounts can. Pure guess is that its not liking the old style passwords in the database (both types are in there... ones beginning with $1$ and ones that are just 13 characters long). changing the user's password, they can login.. So now I dont know what to do about all the other users.. go back to courier, or what... ________________________________________ From: Jeremy Utley [[email protected]] Sent: Sunday, May 12, 2013 12:41 AM To: [email protected] Subject: Re: [qmailtoaster] courier to dovecot conversion On 5/11/2013 11:28 PM, Myers, Jon W wrote: > So I'm getting ready to do this conversion, read through > http://wiki.qmailtoaster.com/index.php/Replacing_Courier_IMAP_with_Dovecot_IMAP > a few times... but I noticed something... it says to stop qmail and courier: > First we need to stop Courier IMAP: > # cd /var/qmail/supervise > # touch imap4/down imap4/log/down > # touch imap4-ssl/down imap4-ssl/log/down > # service qmail stop > > do all the changes, then start everything back up: > # service qmail start > # chkconfig dovecot on > # service dovecot start > > won't "service qmail start" also restart courier? Where am I telling it NOT > to run courier? just by creating those "down" files? Thats what I'm > thinking, but just wanted to make sure before doing the conversion, and didnt > want courier to pop in there and play with the maildirs after the convert... Correct....courier is run from daemontools, not the normal sysvinit scripts, so creating those "down" files signals daemontools that these services are not to run. Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
