Email passwords dont work

[paranoidcookie]

Following an upgrade to ispcp 1.0.7 none of the passwords for email accounts work.
I can go in and create a new one , or reset an existing account ok. Is there a method to regenerate the passwords (they all appear to still be in the table mail_users)?

[lomex]

I have the same problem.

[motokochan]

Passwords are hashed, I believe. This means they cannot be recovered. You can set new passwords using the control panel.

Also, it might be a bug with certain portions of the mail system stack. Check each service (IMAP, POP3, SMTP) manually to make sure that the passwords are not working globally.

[paranoidcookie]

Yes I understand that the passwords are encrypted what I dont understand is why this patr of the upgrade failed.

I checked on my post upgrade backup and the key files are the same, so I didn't forget to backup the keys.

[motokochan]

It's just mail passwords, right? If you can still login to the control panel interface then your key files are fine.

Did you try manually connecting to each service to see if the passwords are indeed failing on everything? That will make troubleshooting a lot easier. If you're not sure what to do just search the web for the service name and "telnet", For example, for IMAP, search "imap telnet". You'll find instructions on how to connect to manually and see what the services themselves have to say.

[paranoidcookie]

The only problem areas were imap/pop and smtp. FTP accounts were ok as were the htaccess for stats.
Comparing the /etc/courier/usersdb pre / post upgrade, the password hashes were different. This seems to indicat [at least to me] post upgrade ispcp was using a different cipher, any thoughts?

I have had mixed reports on access to Ispcp, some clients claim their passwords didn't work (but who knows if they just forgot their password or now). The admin ispcp is what I used and this was fine for me so I don't really know what has happened.

I have just bitten the bullet and asked clients to reset their passwords or contact me to reset them on their behalf.

[motokochan]

The Courier UsersDB format is very specific. It might have been rebuilt, or it could have just been re-generated and new salt used to build the hashes (they are never stored plaintext in that file). It is rather difficult at this level to determine the cause of the issue, unfortunately. A Courier expert might be able to divine more, but I am not one, alas.

[shigwegi]

Hi,

i got the same problem, but i can log in via webmail.