similar to: UIDL conversion courier -> dovecot

Hello, I need to migrate from courier-imap to dovecot. I'm trying to use courier-dovecot-migrate.pl to migrate the users' maildirs but I'm getting these messages: --- # courier-dovecot-migrate.pl --to-dovecot --recursive mydomain.com Testing conversion to Dovecot format Finding maildirs under mydomain.com mydomain.com/contact/./Maildir: No imap/pop3 uidlist files

Hi, I found a problem in the courier conversion script (courier-dovecot-migrate.pl). In some cases, it does not correctly preserve the order of POP3 UIDLs. Consider the following case, when courierpop3dsizelist contains: /2 9000 1327481629 AAA1:2,S 10000 21:1327481629 AAA2:2,S 10000 22:1327481629 AAA3:2,S 10000 23:1327481629 AAA4:2,S 10000 24:1327481629 AAA5:2,S 10000 25:1327481629 BBB11:2,S

Hi, guys. I've read the information in the Wiki about making dovecot's UID's match Courier's UID's in the POP3 server, so that a UIDL command on either server will return the same UID's for the same group of messages. However, what I've read doesn't match what I'm seeing in Courier. Courier appears to keep the UID numbers for messages that it uses for the POP3

I've tested this only with a test user. http://dovecot.org/tools/courier-dovecot-migrate.pl http://wiki.dovecot.org/Migration/Courier # Migrate Courier IMAP (any version) and Courier POP3 (v0.43+) to Dovecot v1.0 # by Timo Sirainen. This is public domain. # Usage: [--quiet] [--convert] [--overwrite] [--recursive] [<conversion path>] # --quiet: Print only errors # --convert: Do

hi list, I've just registered to the list, so please be tolerant ;) I'm currently in the process of planning the migration from courier to dovecot as POP/IMAP-Server. I'm migration from Courier 0.58 (Debian-Etch-packages) to Dovecot 1.1.13 (Debian Lenny Backport). The conversion of the Mailbox from Courier to Dovecot will be done with "courier-dovecot-migrate.pl"-script[1],

HI All, We have the latest Dovecot 1.1.6 running and I need to migrate some POP3 users over from Courier to Dovecot and would need to convert the courierpop3dsizelist to maintain the UIDs. I just need to confirm that the script (http://www.dovecot.org/tools/courier-dovecot-migrate.pl) only works for Dovecot v1.0 and not for v1.1? As the dovecout-uidlist file that is created (by the script) is not

hi all I have a problem with the conversion of files containing UIDL Courier to dovecot uidl , dovecot version is 1.2.15 , format in dovecot is pop3_uidl_format = %08Xu%08Xv i try any other from available list without success courierpop3dsizelist format /2 920 1290084761 1296206202.H818256P31717.domain.tld,S=57135:2,S 57679 87:1290084761 1296239411.H289216P22896.domain.tld,S=1660:2,S 1694

Hi, Courier to dovecot migration script https://dovecot.org/tools/courier-dovecot-migrate.pl referenced at the https://wiki.dovecot.org/Migration/Courier page has a couple of problems. One of them is that the script could not process courierpop3dsizelist generated by courier-5. File format has been changed a bit to mark UTF-8 messages with an additional attribute. Is it safe to ignore such flag

hi, I'm getting quite a few of these in the logs of our new dovecot mail server: Aug 20 09:50:03 mail2 dovecot: POP3(vwc406): Couldn't init INBOX: BUG: Unknown internal error Aug 20 09:50:03 mail2 dovecot: POP3(vwc406): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 we migrated from courier and other mailboxes work. any idea what the cause might be or how I can fix it?

Howdy, I've been having a bear of a time tracking this down. I'm currently using rsync to back a bunch of servers up to a ZFS pool on a server. I recently noticed my deltas between ZFS snapshots seemed a bit large, so I started looking more closely at what was being backed up. Looking at some Maildirs, I found that messages (files) that had been deleted on the server were not being

Hello, For months I have the following configuration in run. Postfix with Mysql and Postfixadmin, Courier Imap + Pop I get a new server and, therefore, would like to change on Dovecot. The installation has also clapped without problems and the configuration has run so far also without defects. If I liked to call away the emails, I always get the announcement Internal Login failure.

Last night we migrated from Courier-IMAP to Dovecot 1.2RC5 and all seems to work fairly well, but I seem to have lost all my mailboxes apart from INBOX. The maildirs are all on the HD in the correct place (/usr/local/virtual/bordo.com.au/jlbrown): mail:jlbrown root# ls -l total 21400 drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .4D drwxrwxr-x 14 _vmail _postfix 476 Jun

Dear R-Core, after switching to 2.3.0, all my trusted do.call constructs that worked in 2.2 and earlier fail. I noted that changes were introduced to do.call, but I could not find out how these relate to my problem. The following example works in 2.2 and earlier, but fails because rownames are partially NA. I can correct this by manually adding row names, but it's a bit of work to check this

Hi there, I've just been experimenting with the latest courier-dovecot-migrate.pl script and I notice that it favours keeping pop3 UIDL ordering rather than IMAP UID preservation. There is this comment (line 312): # POP3 clients may want to get POP3 UIDLs in the same order always. # Preserve the order even if it causes IMAP UIDs to change. Does anyone have details as to which

Hi Migration page [1] on wiki says "Courier version 3 (younger versions) Here everything has changed: Courier's UID data are now stored in courierpop3dsizelistand in a completely new format. But it's still possible to convert it to the format dovecot needs (link to perlscript and further configuration details will follow later). " but there's nothing more. I

Hi all, I have a bunch of mail servers running postfix (external smtp), qmail (LDA) and courier IMAP/POP. Frequently, Ext3 filesystem goes into read-only mode forcing recovery using fsck. Below are the errors we have seen so far on these systems and those systems config. The ext3 errors are common in many cases. 1. Red Hat Enterprise Linux Server release 5.2 (Tikanga) 2.6.18-92.1.10.el5

How can be sure of the current POP3 UIDL? Below my current config (to be migrated to 2.0.x ASAP). Thanks, P. # dovecot -n # 1.0.2: /etc/dovecot.conf log_path: /var/log/mail/dovecot.log info_log_path: /var/log/mail/dovecot.info.log protocols: pop3 pop3s imap imaps listen: * login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap):

I finally got my aging FC2 box retired and moved all email to my new CentOS 5 box. My site is all-IMAP, no POP3. I have one user who downloads all email to Thunderbird on his laptop so that he can work offline while away from a network connection (eg. on an airplane). I forgot to change the pop3_uidl_format setting as described here: <http://wiki.dovecot.org/Upgrading/1.0> So he was

Hi I run a small mail server with Dovecot and postfix. Several of the accounts are popped by an external email provide I use, mostly out habit and also for a bit of redundancy. I have no details on that external server except that it uses exim. Lately, it's been repopping mail from accounts (mail is left on the server so I can use IMAP) at fairly frequent, but undetermined, intervals. Before

Hi all, attached is a patch against 0.99.10.4 that fixes the STAT, LIST and UIDL POP3 command output in the case that they're issued after one or more messages have been deleted. Examples of incorrect behavior (bad spots marked with '***') C: STAT S: +OK 2 806 C: LIST S: +OK 2 messages: S: 1 403 S: 2 403 S: . C: UIDL S: +OK S: 1 1076749908.12