ispCP - Board - Support
POP/IMAP not working after update RC5 -> 1.0.2 - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: POP/IMAP not working after update RC5 -> 1.0.2 (/thread-8573.html)

Pages: 1 2

RE: POP/IMAP not working after update RC5 -> 1.0.2 - fm4 - 12-11-2009 05:40 PM

(12-10-2009 07:05 AM)Jillian Wrote:  check /etc/courier/userdb and compare uid to /etc/ispcp/ispcp.conf line MTA_MAILBOX_UID =
Example:
/etc/courier/userdb: email@domain.tld uid=1001|gid...
/etc/ispcp/ispcp.conf: MTA_MAILBOX_UID = 1001
If they match, check vmail uid/gid with command: id vmail and check if they match to config.

/etc/courier/userdb and /etc/ispcp/ispcp.conf both say 1004 while "id vmail" gives back 1000.
So I just change manually uid in userdb and ispcp.conf to fix my problem?

RE: POP/IMAP not working after update RC5 -> 1.0.2 - kilburn - 12-11-2009 05:47 PM

(12-11-2009 05:40 PM)fm4 Wrote:  /etc/courier/userdb and /etc/ispcp/ispcp.conf both say 1004 while "id vmail" gives back 1000.
So I just change manually uid in userdb and ispcp.conf to fix my problem?

Yes, and don't forget to execute "makeuserdb" after modifyin the "/etc/courier/userdb" file! Smile

RE: POP/IMAP not working after update RC5 -> 1.0.2 - fm4 - 12-11-2009 06:56 PM

problem solved - thank you all for your help!! Smile

RE: POP/IMAP not working after update RC5 -> 1.0.2 - Jillian - 12-12-2009 02:52 AM

Remember to fix /etc/ispsp/courier/working/userdb too. Otherwise you could get errors when you modify your mailboxes.

RE: POP/IMAP not working after update RC5 -> 1.0.2 - Nuxwin - 12-13-2009 02:48 AM

Hello everybody ;

First, this problem is not related to directory permissions. So, if you have changed the permissions restore it before.

To fix your problem, for the version before 1.0.3, you should check the real uid of vmail user in your /etc/passwd file as this:

Code:
ispcp:~# getent passwd |grep vmail
vmail:x:1000:8:vmail-user:/home/vmail:/bin/false

Here the real uid is 1000, so, you must replace the uid value of vmail user in your /etc/ispcp/ispcp.conf file with the real uid of vmail user.

Example for Debian Lenny, replace
Code:
MTA_MAILBOX_MIN_UID = 1004

MTA_MAILBOX_UID = 1004

by

Code:
MTA_MAILBOX_MIN_UID = 1000

MTA_MAILBOX_UID = 1000

Where 1000 is the uid obtained with the last command.

After that, you must rebuild your /etc/courier/userdb file as this :

First, change the status of all mail account in your ispCP database :
Code:
mysql -u USER -p
use ISPCP_DATABASE_NAME
UPDATE `mail_users` SET  `status` = 'change' WHERE status = 'ok'
Note : Replace USER and ISPCP_DATABASE_NAME by your own values

And after, run the ispcp engine manager manually :

Code:
# /etc/init.d/ispcp_daemon stop
# cd /var/www/ispcp/engine
# perl ispcp-rqst-mngr

And to finish, restart the ispCP daemon:
Code:
# /etc/init.d/ispcp_daemon start

EDIT: Oh sorry kilburn, the problem was already solved with your fix. Ok that work fine too, but normally, the user should avoid changing the userdb file manually .