David Laube's Blog » Email

Cpanel – incorrect email disk space used

admin — Fri, 20 Aug 2010 15:28:02 +0000

Control Panel -> Email -> Add/Remove/Manage Accounts -> Show Disk Space Used

When there are inconsistencies with Cpanel’s email disk space usage, you should verify the actual disk space being utilized by:

(1)

du -sh /home/username/mail/userdomain.com/user/
tail -1 /home/username/mail/domain.com/user/maildirsize

(2) Compare the utilized disk space reported by the first du command with the bytes shown in the user’s maildirsize file. If the totals reported are different delete or rename the maildirsize file (/home/username/mail/domain.com/user/maildirsize). Next, logout and then back in again within the user’s control panel and go to Control Panel -> Email -> Add/Remove/Manage Accounts -> Show Disk Space Used

Increasing log retention in qmail’s qmail-smtpd

admin — Thu, 22 Apr 2010 18:07:01 +0000

The default qmail toaster install wont give you much in terms of log data past a 20-30 minutes on a production mail server. It quickly becomes advantageous to increase the duration of log data. You will want to set the “s” and “n” options in multilog to accomplish this.

Open up your /service/qmail-smtpd/log/run file and change;

#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/smtpd

to this…

#!/bin/sh
#The "s16777215" option sets the size of the log file and the "n80" denotes the number of log file to keep on hand.
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s16777215 n80 /var/log/qmail/smtpd

Then you will need to restart multilog via supervise with the following command:
svc -h /service/qmail-send/log

[Dovecot] – Inotify instance limit for user exceeded, disabling?

admin — Fri, 26 Feb 2010 01:54:29 +0000

Today I noticed a bunch of errors in the dovecot log stating “[Dovecot] – Inotify instance limit for user exceeded, disabling”. Apparently Inotify is used to notify
the client immediately after new message has been received. This typically happens after the IMAP client uses the IDLE command.

The solution:

[root@SERVER ~]# cat /proc/sys/fs/inotify/max_user_instances
128
[root@SERVER ~]# echo "256" > /proc/sys/fs/inotify/max_user_instances
[root@SERVER ~]#

Dovecot shouldn’t need to be restarted, but you can choose to do so…. or can you?

.qmail-default files with nonexistent catchall

admin — Wed, 10 Feb 2010 15:46:40 +0000

On servers where a catchall has been setup using the qmailadmin web interface, it is possible for postmasters to delete an email account that was setup as a catchall account (in this case; johnsmith@example.com). When this occurs, the .qmail-default file is not updated. Assuming said catchall was already designated prior to removal, mail is accepted for any-random-user@example.com and messages are deferred when delivery to /home/vpopmail/domains/P/earthwire.com/johnsmith is attempted. This can cause the qmail queue to grow over time when you have many users with this scenario.

A problem /home/vpopmail/domains/P/example.com/.qmail-default file:

| /home/vpopmail/bin/vdelivermail '' /home/vpopmail/domains/P/earthwire.com/johnsmith

What a nonexistent qmail user directory deferral looks like;

/var/log/qmail/current:
@400000004b72cd931e35f0ac delivery 5362496: deferral: client_connect:_connect_failed:_2/user_does_not_exist,_but_will_deliver_to_/home/vpopmail/domains/P/example.com/johnsmith//can_not_open_new_email_file_errno=2_file=/home/vpopmail/domains/P/example.com/johnsmith/Maildir/tmp/1265814921.29239.qmailserver.maildomain.com,S=3149/system_error/

A quick solution(s):

Edit the /home/vpopmail/domains/P/example.com/.qmail-default so the user account path points to postmaster or another user that exists.

Qmailadmin feedback

admin — Mon, 01 Feb 2010 15:05:14 +0000

Thanks. It’s working now.

You have my sympathy for having to support the qmailadmin web
interface. I assume I have yours for having to use it…

-Random Client

Exim problem

admin — Wed, 27 Jan 2010 18:48:56 +0000

While attempting to send outgoing mail through our exim relays, our Qmail mailbox was saying:

@400000004b60848425285634 delivery 12799: deferral: Connected_to_216.120.xxx.xxx_but_connection_died._Possible_duplicate!_(#4.4.2)/

On the relay : 2010-01-27 13:25:31 1NaCa3-0000zJ-AT demime acl condition: error while creating mbox spool file 2010-01-27 13:25:34 1NaCa3-0000zJ-AT H=smtp-2.******.net [216.120.xxx.xxx] F= temporarily rejected after DATA

This was resolved by clearing out the 30,000+ directories in /var/spool/exim/scan on the exim relay server left over from clamd scanning.

/etc/rc.d/init.d/exim stop; cd /var/spool/exim/scan;  find ./ -type d -exec rm -rf {} \; /etc/rc.d/init.d/exim