MigrationGuide

Generally, there are two ways in which you can migrate emails over to MailArchiva:

1) Import emails directly from the MailArchiva GUI (EE)

2) Import emails using command-line based utilities in the MailArchiva_Utilities package (EE & OSE)

Importing emails from MS Exchange is not a perfect science, so if for any reason one particular method does not work for you, please switch over to another method.

For command line utility imports, you'll need to download the mailarchiva_utilities package available from http://www.mailarchiva.com/downloads.php. This package contains a variety of utilities that may prove useful in your migration efforts.

Email Migration From Microsoft Exchange 2000/2003

1) Follow the instructions in the Admin Guide and run the direct Exchange import from the MailArchiva GUI (EE)

2) Configure the Exchange M-Drive and run the Ex2MailArchiva utility as described in ExchangeMigration (OSE && EE)

Email Migration From Microsoft Exchange 2007

1) Follow the instructions in the Admin Guide and run the direct Exchange import from the MailArchiva GUI (EE)

2) Export emails to PST and then run the import (OSE & EE)

a) Export your Exchange information store to one or more PST files

See: http://www.ditii.com/2007/04/13/how-to-export-and-import-mailboxes-to-pst-files-in-exchange-2007-sp1/

b) Step 2. Run the PST2MailArchiva utility (available in the mailarchiva_utilities package)

Note: MailArchiva Exchange 2007 does not support the M-Drive at this time.

Email Migration From Outlook PST Files

a) Run the PST2MailArchiva utility (available in the mailarchiva_utilities package) (OSE & EE)

Email Migration From EML or MSG Files

1) Use the message import function in the MailArchiva GUI (EE)

2) Use Ex2MailArchiva utility in the MailArchiva utilities package (EE & OSE)

The Ex2MailArchiva utility has the capability to sweep up millions of EML or MSG files from the file system. Please refer to the README file in the mailarchiva_utilities package.

Email Migration From Maildir

1) Use the message import function in the MailArchiva GUI (EE)

2) Since Maildir stores emails in standard RFC2822 format, you can simply use the Ex2MailArchiva utility as described above. (OSE & EE)

Email Migration From MBOX Format

1) Use the message import function in the MailArchiva GUI (EE)

2) Use the Ex2MailArchiva utility. Note: There is a switch in Ex2MailArchiva that causes the utility to migrate emails from MBOX format.

Email Migration From IMAP/POP Servers

The IMAP/POP client within MailArchiva is used for the active archiving of the journal account. It is not recommended to use it for purposes of migrating your old emails to MailArchiva.

The MailArchiva mail archiving solution embeds a lightweight SMTP server and thus can integrate with a wide variety of mail servers. In the Listeners section of the Configuration screen, you can change the listening port from 8091 to 25 (the standard SMTP server port).

To suck emails from POP or IMAP servers, use the well known Linux fetchmail utility. This utility fetches mail from remote mailservers and forwards it to your local (client) machine’s delivery system (i.e. MailArchiva). The fetchmail utility can be run in a daemon mode to repeatedly poll one or more systems at a specified interval.

The fetchmail program can gather mail from servers supporting any of the common mail-retrieval protocols: POP2 (legacy, to be removed from future release), POP3, IMAP2bis, IMAP4, and IMAP4rev1. It can also use the ESMTP ETRN extension and ODMR.

Examples of working fetchmail:

This will fetch all emails from the INBOX folder of an IMAP server. Make sure to change USERNAME and MAIL.SER.VER. Also, verify MailArchiva is listening on 8091 fetchmail -a -k -v -u "USERNAME" -S localhost/8091 -p imap MAIL.SER.VER

This will fetch all emails from the INBOX\old-messages folder fetchmail -a -k -v -r "INBOX.old-messages" -u "USERNAME" -S localhost/8091 -p imap MAIL.SER.VER

To achieve this on Windows, you can use the handy Postie utility available at http://www.infradig.com/.

{insert postie commandline parameters below}

-- TWikiGuest - 20 Jul 2008