similar to: Question about migration from tpop3d mbox -> Dovecot maildir

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 :).

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

Hi, Here is an updated patch which allows to use tpop3d compatible UIDL in dovecot (it's against 1.0rc1): http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/dovecot-tpop3d-uidl.patch?rev=1.2 which is based on: http://dovecot.org/pipermail/dovecot/2006-March/012080.html Please consider merging it. -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl

hi all, I am hoping to convert a 350K user qpopper installation using mbox to dovecot and maildir (pop3 only). many of the users "leave mail on server", and qpopper's UIDL format isn't (yet) supported by dovecot. since the UIDLs have been written by qpoppper to the existing mbox files (and will be preserved when the mboxes are converted to maildir) it would be possible to do

hi all, this is needed to make the pop3_reuse_xuidl option work in 1.0alpha4. I am using maildir and I noticed that for each message which doesn't have an indexed X-UIDL header, the entire message is read from disk. as this is reading only headers, it is probably reasonable to stop reading at the end of the headers. it would also be neat if dovecot could be configured to only try reading

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're upgrading a cluster of servers from v1.0.15 to v1.1.x or v1.2.x. It appears that the UIDL generation mechanism has changed, and thus we'll be getting POP3 dups with users that leave mail on server (which is a nasty practice, I know). From checking the sources, and performing a number of controlled tests in various scenarios, here is the outcome: upgrade from 1.0.15 to

hi All, I have a srange problem. Before dovecot there was a courier imap and it worked just fine. The client(s) are the same then before, so I think, this is an server side problem. I have a user with Outlook and he uses pop3 and leaves messages on server. Sometimes the messages get downloaded again, when he starts the outlook. Not all, but 7-9 hours back. uidl format is like it's

Hi, we are in migration progress from Communigate Pro 5.0.x to Dovecot 2.0.15 with mdbox. We still migrated about 25.000 IMAP accounts from CGP to Dovecot. Also there were still added about 2000 new POP3 Accounts on Dovecot. Now we must migrate about 10.000 POP3 accounts from CGP to Dovecot. At the beginning of our migration we didn't set the "pop3_reuse_xuidl" configuration

Hello, I've taken a different (better) approach to getting tpop3d-compatible UIDLs: the first attached patch (...md5_modifier.diff) adds a variable expansion modifier (%M) to return the md5sum of the expanded variable in hex. With the patch, you can get tpop3d-compatible UIDLs by setting pop3_uidl_format to %Mf. While testing interactions with other modifiers (e.g. %MUf to get the md5sum in

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

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, I've attached a patch that adds an additional expando to pop3_uidl_format. The additional expando (%M) expands to the md5sum of the filename (which is already available via %f.) This UIDL style is compatible with tpop3d when using Maildir. The patch is against dovecot 1.0 beta3, and I'd love to see it be merged into the official tree. Comments welcome. -- Ben Winslow

Hello! I am trying to migrate from Teapop to Dovecot. I'm using Dovecot 1.1.14. I need to make use of the X-UIDL header so clients don't download messages they've already received. I have the X-UIDL head in the message. I have pop3_reuse_xuidl(pop3): yes My problem is the X-UIDL in the message is being ignored and Dovecot is still generating it's own. The INBOX is an mbx

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

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, I'm migrating accounts from one server with dovecot mbox and pam nss-ldap authentication to a new server with dovecot maildir and mysql auth (no posix accounts). My problem is the pop3 uidl format on the two servers are different, even though I'm using pop3_uidl_format = %08Xu%08Xv in both configs, I'm always re-downloading left messages on my test runs. Is there a way I could

I've got a weird split setup where POP3 is currently handled by Courier (courier-imap-3.0.2 distribution), and IMAP is currently handled by the RHEL 5 version of Dovecot (1.0.7) I'm trying to figure out a way to convert the POP3 UIDLs (in cases where the courierpop3dsizelist is newer than dovecot-uidlist, at least) to something that Dovecot will read, or to configure Dovecot's pop3 to

Hello everyone, in february I posted the mail below[1]. I can now reproduce the problem. When filling up a mailbox with postfix' smtp-source with dozens of identical mails, then it is never possible for me to fetch one single mail out of the mailbox. The process of fetching mail via POP3 always fails. It makes no difference which mail client I use. I have tested KMail, Outlook and

Hi there, I ran into an issue yesterday (dovecot 2.0) whereby when we dsync messages from a local machine (sdbox) to a remote (Maildir) which have different pop3_uidl_formats configured, the uidl format is not preserved. There doesn't seem to be any way to force this in the code, although I suspect that Maildir sources with saved pop3 uidls would pass them correctly. Attached is a rough patch