BakasIT
asked on
Plesk Upgrade 8.1 to 8.6 Clients cant log into email
I just upgraded Plesk from version 8.1 to 8.6
clients cant login into horde email (psa-horde)
I can see clients details in Plesk.
Was able to add a new email [test] user to one domain
I can see the passord with PowerTools.
I can see this has been done with the commandline tool:
/usr/local/psa/admin/sbin/
| test@testdomain.com.au | | password123 |
==> /var/log/mail.info <==
Oct 24 14:37:27 srv1 imapd: IMAP connect from @ [127.0.0.1]checkmailpasswd
can any please help ?
clients are ringing up they cant access email
clients cant login into horde email (psa-horde)
I can see clients details in Plesk.
Was able to add a new email [test] user to one domain
I can see the passord with PowerTools.
I can see this has been done with the commandline tool:
/usr/local/psa/admin/sbin/
| test@testdomain.com.au | | password123 |
==> /var/log/mail.info <==
Oct 24 14:37:27 srv1 imapd: IMAP connect from @ [127.0.0.1]checkmailpasswd
can any please help ?
clients are ringing up they cant access email
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wasnt the answer - but as so kindly offered something I think deserves the points
ASKER
Thanks IT4SOHO
The problem was a mixmatch between 8.1 and 8.6 components.
Not all the components where upgraded - in particular psa-hordemail
Plesk8.6 now uses a poppasswd.DB rather than the popasswd shadow file
but without the newer psa-hordemail the horde-web-frontend to mail still used the old popasswd shadow file.
- I got around the problem by recreating the popasswd shadow file by hand so the username,password pairs could be found (and the directory from which to retrieve mail for this user)
*This at least gave some breathing space*
The correct approach was to upgrade every package in horde to build 8.6.
Now it all works as expected.
But as you so kindly answered Ill donate the points to you anyway.
Cheers
Sean
The problem was a mixmatch between 8.1 and 8.6 components.
Not all the components where upgraded - in particular psa-hordemail
Plesk8.6 now uses a poppasswd.DB rather than the popasswd shadow file
but without the newer psa-hordemail the horde-web-frontend to mail still used the old popasswd shadow file.
- I got around the problem by recreating the popasswd shadow file by hand so the username,password pairs could be found (and the directory from which to retrieve mail for this user)
*This at least gave some breathing space*
The correct approach was to upgrade every package in horde to build 8.6.
Now it all works as expected.
But as you so kindly answered Ill donate the points to you anyway.
Cheers
Sean
ASKER
The problem was a mixmatch between 8.1 and 8.6 components.
Not all the components where upgraded - in particular psa-hordemail
Plesk8.6 now uses a poppasswd.DB rather than the popasswd shadow file
but without the newer psa-hordemail the horde-web-frontend to mail still used the old popasswd shadow file.
- I got around the problem by recreating the popasswd shadow file by hand so the username,password pairs could be found (and the directory from which to retrieve mail for this user)
*This at least gave some breathing space*
The correct approach was to upgrade every package in horde to build 8.6.
Now it all works as expected.
But as you so kindly answered Ill donate the points to you anyway.
Cheers
Sean