similar to: POP UIDL

HI I don't know if this is a dovecot issue or a client one. But as Dovecot is the most recent change, I'll start here. I have a server that's been running Courier for about 6 years and in all that time I think I've only ever had 1 issues where an entire mail box was repopped by a webmail client. However, since moving to a new server and dovecot 4 weeks ago, I've now had the

there is an error line 348 Clusterer.popUp( poppedUpCluster ) Clusterer.rePop = function ( clusterer ){ if ( clusterer.poppedUpCluster != null ) Clusterer.popUp( poppedUpCluster ); }; should be Clusterer.rePop = function ( clusterer ){ if ( clusterer.poppedUpCluster != null ) Clusterer.popUp( clusterer.poppedUpCluster ); }; -------------- next part -------------- An HTML

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

Hello, I'm in the process of migrating accounts between two dovecot servers. An old server running ancient 1.0.15 and a new server running 1.2.15. Account migration is going to be gradual and so i would like to use imapsync to move messages and subscriptions from one server to the other. The only problem so far is with POP users. After doing an account migration with imapsync, and

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

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

Hi all, I'm migrating a Postfix + Dovecot 1.0 server with mboxes to Qmail + Dovecot 1.4 with Maildirs and encounter the following the problem. Using perfect-maildir.pl from: http://perfectmaildir.home-dn.net/ i can relatively succesfully convert the mbox to a Maildir. The problem, however is that clients with "leave mail on server" set to on retrieve all email a 2nd time. I

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

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. Yes, of course. And the directory structure was pretty much identical between the two. Which was how I was able to write and run the rsync script. I think at this point, I'm past

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

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.

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

Hi, we're trying to migrate from UW imap 2001a-10, which doesn't seem to use the UIDL format documented in the wiki. It seems to use a 16 character long MD5 hash of something. I've tried configuring Dovecot to do the same but the value comes out differently. The main thing that I can see is getting in the way is that the UIDL format is not documented sufficiently. There is no

Hello, I have a serious problem with dovecot and mbox format. dovecot returns the same UIDL for new messages and as result some MUAs don't retrieve new mail. UIDs returned by UIDL command look like 000000*1c*49006cec And there is a moment when dovecot stops incrementing marked digits. In other words when new message arrive to mbox, UIDL command returns used UID. I'll show with example:

Greetings, is anybody aware of an extension to POP3 that supports UIDL ranges? It would be very useful for keep-messages-on-server setups (yes, I know, IMAP4 domain) to be able to do UIDL 21-42 to obtain just these 22 UIDs (this would always have to be a multi-line reply, just like UIDL without argument). If such a thing does not exist yet, perhaps a keyword such as "[X]UIDLRANGES" in

Hi ! POP3-RFC (1939) speaks about UIDL command: The unique-id of a message is an arbitrary server-determined string, consisting of one to 70 characters in the range 0x21 to 0x7E, which uniquely identifies a message within a maildrop and which persists across sessions. When I issue an UIDL command (dovecot 0.99.10.9) I get replies like 1 1093990148.1 2 1093990148.2 3 1093990148.3 ... . You see

Hello! I have two Dcs Samba 4 version 4.4.0, the DC 2 received rsync to DC 1, ok this SYSVOL, but necessary execute "samba-tool ntacl sysvol reset", for correct ids, but now is a one error this process: samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File

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

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