Skip to main content

Upgrading dbmail

Last week, I upgraded my production imap server from dbmail 2.0.9 to the latest stable 2.2.1. I need to upgrade because there are features I need to use. They are:

1. server-side sorting (fixed after 2.1.7)
2. sieve server-side filter (using dbmail-timsieved daemon)

The upgrade was a risky one. It was a leapfrog from 2.0.x to 2.2.1 by skipping 2.1.x. Many changes since 2.0. Since I did not have a test server so it was important to backup all emails. After too much thought, I decided to give it a go.

Stopping the mail server
These stops all necessary mail-related services. You may not want to stop httpd services to make announcement to users on the website. You have to stop services in order to migrate your system smoothly without bothering emails coming in and out and slow down the whole process.

service postfix stop
service dbmail-imapd stop
service dbmail-lmtpd stop


Backing up all emails
It is important to backup all emails before upgrading process. At least you can revert to previous dbmail if something go wrong.

mysql -u dbmail -p dbmail > dbmail-2.0.9.sql

Source
Download the source from dbmail.org and untar it.

tar xzvf dbmail-2.2.1.tar.gz
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-mysql --with-sieve

Note: If you want to use sieve filter (--with-sieve), you have to download libsieve at http://libsieve.sourceforge.net/. Compile it and install.

make
make install

Migrate the database
Use the provided script in sql dir to migrate dbmail tables to make it suitable for 2.2.x

mysql -u dbmail -p dbmail <>

Fix the header

/usr/sbin/dbmail-util -by

If you do not run this command, you will get unknown (for sender) and (no subject) (for subject) for all mails in mail header. Please make sure it is the latest binary you're running by issuing dbmail-util -V.

Please watch any error coming out of the upgrade process. If any, you should consult dbmail mailing list.

That's all there is to it. Restart all the process (or you may want to restart your server). Make sure all the related services start during startup with chkconfig.

dbmail-timsieved init-script
This is a script I make for dbmail-timsieved by modifying dbmail-imapd script. Clever huh? :P


#!/bin/bash
#
# Startup script for the DBMail TimSieve Server
#
# chkconfig: - 81 19
# description: DBMail is a mail server with a database backend. Unlike \
# WUimapd it does not run through inetd.
# processname: dbmail-timsieved
# pidfile: /var/run/dbmail-timsieved.pid
# config: /etc/dbmail.conf

# Source function library.
. /etc/rc.d/init.d/functions

if [ -f /etc/sysconfig/dbmail ]; then
. /etc/sysconfig/dbmail
fi

# Path to the dbmail script.
dbmail=/usr/sbin/dbmail-timsieved
prog=dbmail-timsieved
RETVAL=0

start() {
pid=`pidof $prog`
if [ -n "$pid" ]
then
echo "dbmail timsieved daemon is already running, PID $pid"
else
echo -n $"Starting $prog: "
daemon $dbmail
RETVAL=$?
echo
[ $RETVAL = 0 ] && touch /var/lock/subsys/$prog
return $RETVAL
fi
}
stop() {
echo -n $"Stopping $prog: "
killproc $dbmail
RETVAL=$?
echo
[ $RETVAL = 0 ] && rm -f /var/lock/subsys/$prog /var/run/$prog.pid
}
reload() {
echo -n $"Reloading $prog: "
killproc $dbmail -HUP
RETVAL=$?
echo
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status $dbmail
RETVAL=$?
;;
restart)
stop
start
;;
condrestart)
if [ -f /var/run/$prog.pid ] ; then
stop
start
fi
;;
reload)
reload
;;
*)
echo $"Usage: $prog {start|stop|restart|condrestart|reload|status}"
exit 1
esac

exit $RETVAL

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy

postfix - mailbox size limit and message size limit

postfix is my MTA of choice. I use it for my mailserver because its simplicity , security and sendmail-compatible (the widely used smtp in the world but not as secure). It is also extensible by plugging other servers for various purposes (antispam, antivirus,database etc).

I had one problem with file attachment larger than 10MB. Users couldn't send it although I have setup squirrelmail (SM) to be able to attach files summed up more than 20MB and I had modified php settings as per here. The problem was not in SM setting. It was postfix. By default, attachment size that can be sent by postfix is 10MB ~ 10240000 byte. How did I know it? I looked in log file (for my system it is in /var/log/mail/errors. For other system, the file to look is /var/log/maillog). The line looked like this:

Feb 26 16:30:53 webmail postfix/sendmail[30775]: fatal: me@mymailserver.org(74): Message file too big


Solution
Open /etc/postfix/main.cf with a text editor of choice and find message_size_limit directive an…