similar to: dovecot mbox to dovecot maildir migration

Hello, I am in the process of migrating a hosting setup from UW-IMAP to Dovecot. The protocols available to mail clients are IMAP and POP3 both before and after migration. I also wanted to change the mail storage format from MBOX to Maildir. However, at this point I hit a major snag with Dovecot and POP3 UIDL (unique identification listing for POP3 mailboxes). Several of the customers connecting

TESTED AND RUNNING, MIGRATING from MBOX to MAILDIR, PRESERVE UID and OUTLOOK sees the email as downloaded. I hope this helps a lot of people out there. Feel free to post this somewhere else too. By: Horn Wijaya (hwijaya at nodens.biz) 8th May 2008 I have been searching for weeks for a foolproof method to migrate all my users mbox to maildir/dovecot without having the pain of downloading

Dear Tim Schafer, Take a look at my sample dovecot-ldap.conf hosts = localhost dn = cn=root,dc=ceylonlinux,dc=com dnpass = secret ldap_version = 3 base = dc=ceylonlinux,dc=com deref = never scope = subtree user_attrs = mail,homeDirectory=mailMessageStore,uidNumber=1003,gidNumber=1003 user_filter = (&(objectClass=user)(mail=%u)) pass_attrs = mail=user,userPassword=password pass_filter =

Thank you for the reply of my previous post (http://www.dovecot.org/list/dovecot/2007-March/020716.html) now it works, but I have another question about migrating pop3 account (with leave mail on server) to maildir. On this post -> http://www.dovecot.org/list/dovecot/2006-February/011464.html you explain how to create dovecot-uidlist preserving UIDVALIDITY. Is there someone that have

I am moving from and old FC2 system to a new RHEL5 system and am having trouble getting the UIDLs to move over right, mainly the UID. I copy over the mailbox, and see the x-uid in the message is what it was on the old server, but when I telnet in to check pop, it rewrites x-uid in the message to something new, causing old messages to get downloaded again, which is not what we want I have tried

Hi, This small mail to share my observation about a recent move of mailboxes between two servers and ask about explanation and/or improvement about UIDL in dovecot. SV1 : Dovecot 0.99.14 / Red Hat Fedore Core 4 SV2 : Dovecot 1.07 / CentOS 5.2 Mailboxes in /var/spool/mail on the twoo servers. Test will be done with outlook express with option "leave message on server" checked. Goal is

Hello, I have used mb2md for an individual user like this: su ~username cd ~ ./mb2md -m This converted /var/spool/mail/username mbox to /home/users/username/Maildir just as I expected. To convert 100s of users the same way would be a chore (su as each user for permissions, etc.). Is there a way to batch process all /var/spool/mail/$USER to /home/users/$USER/Maildir with the correct

Is there some way that message uids can be preserved when converting uw-pop3 mbox mail to dovecot maildir format? We've tried perfect_maildir, mb2md and the convert-tool that comes with dovecot but so far have been unable to preserve the message uids, which for example go from 44333a8500000003 before the conversion to 4434621500000003 afterwards. The quantity of mailboxes involved means

I was hoping some one might be able to offer me some advice on a little problem I have. I am looking to A. move from mbox to maildir B. looking to move from tpop to dovecot to bring both pop and imap under the same program. anyways the problem I am having is this tpop3d mbox uses MD5 sum of the mailbox headers in hex which is option %m in the uidl section but the problem is when dovecot

Hi We have been running a dovecot server for some time.. users connect with pop. Now this server is going to be substituted with a new one.. before we used mbox, but now we will move to maildir! I have done some testing transfering the mail with the mb2md script, the conversion works correctly, but users gets duplicates since they selected "keep mail on server" I have googled for the

Hello All! I am new to this list so I hope I'm not in the wrong list with my question. First, I have to say that dovecot is (in my opinion) one of the best POP3/IMAP servers arround. I especialy like its' simplicity (configuration) and powerfullness (speed, auth mechs). In my production environment I would like to cange from tpop3d to dovecot, but I have only one little problem :).

I recently set up an OpenBSD - Dovecot mail server for a client. Naturally (according to Murphy's Law) they want to use Outlook 2003, pop3s, and leave messages on the server. And just as naturally, the UIDLs don't seem to be working, and when they download mail, they get EVERY email stored on the server, not just the new ones. Other than switching them over to IMAP, I found the

> On 26 Jan 2016, at 15:56, Marc Schiffbauer <m at sys4.de> wrote: > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >> >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve

Package: dovecot-imapd Version: 0.99.14-1 Severity: important Hi, I think I've identified a bug in Dovecot 0.99.14 as packaged and distributed by Debian Sarge. I believe the bug lies in the original Dovecot source, not with any modifications made by Debian. Specifically, this bug deals with Dovecot's handling of message unique identifiers (UIDs) for IMAP clients when using the mbox

I am testing migration from Qpopper 4.0.5 and have come across a problem. Dovecot dies while processing UIDL command when accessing malformed Qpopper's mbox which has duplicated "From " separator. Qpopper occasionally makes such header while rewriting mbox. In the attached file, unnecessary "From " at line 3. ---------------- * Dovecot 1.0.0 on Debian 4.0(x86) * ext3

Hi, Considering the scenario, where you have some old account with a different POP3 UIDL format and you migrate them to dovecot. So these old UIDLs would be saved to dovecot-uidlist. At some later time you want to introduce a virtual POP3 INBOX like described on: http://wiki.dovecot.org/Plugins/Virtual So you decide to make the new UIDL format "%f" - to make them unique across

From the Dovecot 1.0.1 sample dovecot.conf file: # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu ... # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #

Yes, again! :) I googled this issue but found no solution. Then, simple question - on this moment, it is possible without losing UIDLs or not?

Hello list, im am trying to migrate customer mails via dsync from an old dovecot 1.1 setup to an new installed dovecot 2.2.25 setup with mdbox. Upgrading the old dovecot 1.1 to 2.2 with Maildir isnt an problem and the replication to the new setup works well too. The only problem now is, that the POP3 UIDL are completely wrong on the target setup. Im using for Maildir pop3_uidl_format = %f With

We have an older mail server using qpopper and the mbox format which we need to update to dovecot and maildir format. I have read through the docs on migrating from mbox to maildir, as well as a few nuggets on how to migrate from qpopper to dovecot, and I was wondering if I could get some suggestions on best practices for this specific migration. Would the built in dovecot conversion plugin be a