smtp – Page 6 – KutuKupret

ConvertMboxToMailbox

Jul 162008

Converting from UNIX mbox/mailbox to Maildir – postfix, procmail, Squirrelmail, uw-imap and cyrus-imap

This guide discusses transforming a system from the traditional mbox/mailbox format to the more advanced Maildir format.

I assume you are using the postfix mailer – if not, you will probably want to change over to postfix first or some of this material may not be relevant.

Make a backup

Before commencing, backup your entire system.

Stop the mailer

You do not want any mail coming in while doing the conversion. You should also stop any programs that automatically generate mail locally.

# /etc/init.d/postfix stop

Get the necessary tools

If you are running Debian, this command will get everything you need:

# apt-get install mb2md

Convert each users mail

For each user on your system:

 # su daniel
 $ cd ~
 $ mb2md -m
 $ mb2md -s mail
 $ exit
 # mv /var/spool/mail/daniel /var/spool/mail/daniel.preMaildir
 # mv ~daniel/mail ~daniel/mail.preMaildir

NOTE: The second mb2md command is only needed if the user has a directory ~/mail where they store mbox/mailbox format mail folders.

Later on, you will want to delete the .preMaildir versions to recover disk space. Before you do so, make sure everything is working fine.

QMT Failover replication Setup

linux No Responses »

Jul 082008

source: http://wiki.qmailtoaster.com/index.php/QMT_Failover_replication_Setup

QMT Failover replication Setup

Craig Smith – 26th October 2006 – craig@doc-net.com

Thanks to Jake for taking the time to review this for me before posting. It always helps to have a sounding board and Jake was kind enough to be that board for me.

This page gives you a procedure to configure a backup qmt server that will be available for failover in the event of primary server failure. The backup server will only ever be 10 minute out from the primary.(depending on cronjob timing)

Please note initial replication (the first run) will take some time, so schedule this for off peak hours. Once the first run has finished and unison has a db of what it is working with subsequent runs are pretty quick. So enable the cron job settings at a time that you can manage the traffic for initial replication.

Also this setup is based on 2 servers where the port used is internal and not visible publically. If you cannot do this on a private network, then read up on using ssh for replication as this is not a secure transport and should not be used on open networks.

This was setup and tested on Fedora core 5 on both servers, and it works without any hiccups.

The details are pretty much cut and paste.

Page 6 of 6 Newer Entries 1 2 … 4 5 6