HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=27)
-   -   Can't add new mailboxes (http://www.howtoforge.com/forums/showthread.php?t=59905)

hfr 10th December 2012 11:00

Can't add new mailboxes
 
Hello,

ISPConfig-Version 3.0.4.6
Linux: CentOS release 5.8 (Final) 32-Bit (setup According to "perfect server guide centos 5")

It is not possible to add new mailboxes anymore via ispconfig. Since I don't add mailboxes very often I am not sure when it stopped working, but 1-2 month ago it still worked.

In ispconfig gui everything seems ok (mailbox is added successfully), but when trying to login to roundcube or catching mails via imap the following error msgs are written to /var/log/maillog:

Code:

Dec 10 10:39:32 server imapd: Connection, ip=[::ffff:127.0.0.1]
Dec 10 10:39:32 server imapd: LOGIN, user=bb@domain.de, ip=[::ffff:127.0.0.1], port=[59956], protocol=IMAP
Dec 10 10:39:32 server imapd: Error reading ACLs for INBOX.sieve: No such file or directory

This only happens with new mailboxes, all existing mailboxes work.

Any ideas what can cause this?

Regards
Hans

hfr 12th December 2012 08:57

Tried with pop3, also does not work with another error message in maillog:

Quote:

Dec 12 08:53:18 server pop3d: LOGIN, user=bb@domain.de, ip=[::ffff:212.x.x.x], port=[35804]
Dec 12 08:53:18 server pop3d: scancur opendir("cur"): No such file or directory
Sending mail via smtp works.

Any Ideas?!

hfr 12th December 2012 09:41

OK, it seems ispconfig does not generate valid mailboxes in filesystem anymore. After adding a mailbox in ispconfig, /var/vmail/domain.de/bb looks like:

Quote:

-rw-rw---- 1 vmail vmail 5 12. Dez 09:30 ispconfig_mailsize
drwx------ 9 vmail vmail 4096 12. Dez 09:30 Maildir
One of the old mailboxes (which still work) looks like:

Quote:

drwxr-xr-x 2 vmail vmail 4096 12. Dez 09:10 courierimaphieracl
drwx------ 2 vmail vmail 4096 22. Jun 12:21 courierimapkeywords
-rw-r--r-- 1 vmail vmail 53 22. Jun 12:21 courierimapsubscribed
-rw-r--r-- 1 vmail vmail 15 3. Dez 11:59 courierimapuiddb
-rw-r--r-- 1 vmail vmail 139 3. Dez 11:35 courierpop3dsizelist
drwx------ 2 vmail vmail 4096 3. Dez 11:59 cur
drwx------ 5 vmail vmail 4096 22. Jun 12:21 Maildir
drwx------ 2 vmail vmail 4096 3. Dez 11:35 new
drwx------ 2 vmail vmail 4096 12. Dez 08:59 tmp
So the second error message (opendir cur) makes sense.

I then tried to create the mailboxes with maildirmake and it worked. The mailbox created with maildirmake looks like:

Quote:

drwx------ 2 vmail vmail 4096 12. Dez 09:31 cur
drwx------ 2 vmail vmail 4096 12. Dez 09:31 new
drwx------ 2 vmail vmail 4096 12. Dez 09:31 tmp
The mailbox seems to work fine (imap + pop3, smtp worked before).

How can I find out what goes wrong when ispconfig tries to create the mailbox?

till 12th December 2012 09:56

Please see sticky post of this forum for debug instructions:

http://www.howtoforge.com/forums/showthread.php?t=58408

hfr 12th December 2012 11:14

Thanks. Output:

Quote:

[root@server ispconfig]# /usr/local/ispconfig/server/server.sh
PHP Deprecated: Directive 'register_long_arrays' is deprecated in PHP 5.3 and greater in Unknown on line 0
12.12.2012-10:07 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
12.12.2012-10:07 - DEBUG - Found 1 changes, starting update process.
12.12.2012-10:07 - DEBUG - Calling function 'user_insert' from plugin 'mail_plugin' raised by event 'mail_user_insert'.
12.12.2012-10:07 - DEBUG - Created Maildir /var/vmail/domain.de/asd4 with subfolder:
12.12.2012-10:07 - DEBUG - Set ownership on /var/vmail/domain.de/asd4
12.12.2012-10:07 - DEBUG - Created Maildir: su -c 'maildirmake -q 0S /var/vmail/domain/asd4' vmail
12.12.2012-10:07 - DEBUG - Created Maildir /var/vmail/domain.de/asd4 with subfolder: Sent
12.12.2012-10:07 - DEBUG - Created Maildir /var/vmail/domain.de/asd4 with subfolder: Drafts
12.12.2012-10:07 - DEBUG - Created Maildir /var/vmail/domain.de/asd4 with subfolder: Trash
12.12.2012-10:07 - DEBUG - Created Maildir /var/vmail/domain.de/asd4 with subfolder: Junk
12.12.2012-10:07 - DEBUG - Calling function 'update' from plugin 'maildeliver_plugin' raised by event 'mail_user_insert'.
12.12.2012-10:07 - DEBUG - Mailfilter config has been changed
sh: dovecot: command not found
12.12.2012-10:07 - DEBUG - Calling function 'update' from plugin 'maildrop_plugin' raised by event 'mail_user_insert'.
12.12.2012-10:07 - DEBUG - Mailfilter config has been changed
12.12.2012-10:07 - DEBUG - Processed datalog_id 678
12.12.2012-10:07 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
sh: dovecot: command not found

I use courierd not dovecot. In ispconfig -> System -> Serverconfig -> Server -> Mail the attribute POP3/IMAP Daemon was set to dovecot (don't know why but i am sure i did not change this). I set it to courier now but error stays the same.

till 12th December 2012 12:22

Quote:

I set it to courier now but error stays the same.
You have to delete the mailbox and then create it again after you changed the settings as the maildir layout from dovecot and courier is different.

hfr 12th December 2012 12:24

Quote:

Originally Posted by till (Post 289528)
You have to delete the mailbox and then create it again after you changed the settings as the maildir layout from dovecot and courier is different.

That is exactly what I tried (create completely new mailbox). But it still says sh: dovecot: command not found in ispconfig log.

till 12th December 2012 12:27

Dovecot must have been installed on your server at the time when the last ispconfg update was installed as your server is configured for dovecot at the moment.

Check with:

which dovecot

that really no dovecot binary is installed anymore now, then download ispconfig tar.gz agaian, run the update.php script and choose to reconfigure services so that your server gets configured for courier again. You should see in the installer output that it configures courier then and not dovecot.

hfr 12th December 2012 12:34

I found some evidence of a previous/old dovecot installation.

Quote:

[root@server ispconfig]# which dovecot
/usr/bin/which: no dovecot in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/courier-imap/sbin:/usr/lib/courier-imap/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
[root@server ispconfig]# locate dovecot
/etc/dovecot-sql.conf
/etc/dovecot.conf.rpmsave
/etc/dovecot.conf~
/etc/pki/dovecot
/etc/pki/dovecot/certs
/etc/pki/dovecot/private
/etc/pki/dovecot/certs/dovecot.pem
/etc/pki/dovecot/private/dovecot.pem
/usr/lib/python2.4/site-packages/sos/plugins/dovecot.py
/usr/lib/python2.4/site-packages/sos/plugins/dovecot.pyc
/usr/lib/python2.4/site-packages/sos/plugins/dovecot.pyo

[root@server ispconfig]# rpm -q dovecot
Das Paket dovecot ist nicht installiert
How does ispconfig determines, which mta is actually used?

till 12th December 2012 13:14

Quote:

How does ispconfig determines, which mta is actually used?
With the command:

which dovecot

So the dovecot package must have been installed at the time you installed ispconfig or updated it the last time as this configuration can only be changed by the installer 7 updater. To fix it, follow the steps I explained above.


All times are GMT +2. The time now is 12:54.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.