similar to: [PATCH proposal] make dsync preserve pop3_uidl_format

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

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

Hi all, Lets say I have a maildir which doesn't contain any dovecot files but has some emails lying around in it. If I add a message to this mailbox using deliver, dovecot creates the uidlist file with a single entry (the message that was just delivered). When I then log in to the mailbox, all the other messages are added into the uidlist file in the normal order (directory list order I

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'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 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, we're running dovecot 1.1.2 (centos5 32-bit rpm from atrpms) havn't had any real issues with it, but today it looks like an index has become badly corrupted. We're seeing this in the logs every time we log in to a particular account: 2008-09-10T11:56:07+01:00 mail8 dovecot: Panic: IMAP(xxx): Trying to allocate 2273345672 bytes 2008-09-10T11:56:07+01:00 mail8 dovecot: IMAP(xxx):

Hi all, We need to set our filestore to read-only for quite a while, and I want to mitigate the effects for our clients. First issue; dovecot. If we just change the nfs mounts to read-only, dovecot complains: 2009-02-19T14:03:19+00:00 mail2 dovecot: pop3-login: Login: user=<test2 at markandruth.co.uk>, method=PLAIN, rip=10.15.10.95, lip=10.15.10.102:11002 2009-02-19T14:03:19+00:00 mail2

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

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

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there

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

On 25.09.19 12:29, Sami Ketola via dovecot wrote: > > >> On 25 Sep 2019, at 4.52, Plutocrat via dovecot <dovecot at dovecot.org> wrote: >> >> On 24/09/2019 10:14 PM, @lbutlr via dovecot wrote: >>> Did the target machine already have the user setup? I think dsync wants to sync mailboxes between configured and working servers with users already defined.

Timo, There is a problem with the dsync POP3 migration plugin when syncing a large INBOX. What happens is dsync establishes a connection to the POP3 server at the beginning of the sync, but then it sits there idle until it's used to sync the UIDLs. On a very large inbox with many thousands of messages it will be idle for longer than a POP3 server's idle timeout setting. When the UIDL

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. #

Hi, today I've finished migration from uw-imap daemons to shiny and fast dovecot. With thanks of dovecot my mail server load average drops by factor of ten even with ancient unix mailboxes. ;-) So, the only thing I've discovered is what POP3 uidls are different than ones used in the uw-imap. Luckily, the difference are only in the format string used in uidl response. So, I've

Hi, About a week ago I upgraded our reasonably heavily loaded mail servers from a pretty recent courier version to dovecot-1.1rc10. IMAP performance on dovecot is amazing, however POP3 performance is worse than courier :-( I have uploaded some munin graphs taken today to http://linweb.atlas.pipex.net/dovecot/; the dovecot server is handling about 2000 pop logins/sec and 300 imap sessions (but

Dear All, I'm having an intermittent problem, with dovecot slowing to a crawl. Restarting dovecot fixes the problem. Looking at the maillog, I see loads of these errors.... dovecot: pipe() failed: Too many open files dovecot: Temporary failure in creating login processes, slowing down for now dovecot: Created login processes successfully, unstalling looking at the processes, I can see

My existing pop3/imap environment is courier imap + vpopmail + qmail with MySQL backend. I'm looking at migrating this to Dovecot. Currently I have multiple instances of Courier bound to different loopback IPs (the IPs correspond with the virtual IPs on a server load balancer). When a user authenticates they don't have to specify a domain - if they don't, Courier will use a

Scenario: Using Dovecot 0.99.10.9 as pop3 server. With delete on retrival off. clients: outlook* Problem: Everytihng work perfectly, except that outlooks keeps re-downloading SOME mail over and over. Though it already got them. No obvious pattern which, but only a small percentage. First of I looked at dovecots UIDLs. Initialy I thought it's broken (see my previous thread) Sorry for even