similar to: dovecot-example.conf error with POP3 UIDL format?

Hi, I see this in the 1.0-beta7 dovecot-example.conf file: # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # # Note that Outlook 2003 seems

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, 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

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

I am migrating from UW's POP3 server (mbox), to Dovecote (mbox -> maildir). Anyway, I am concerned about the Logging details offered by Dovecot, as I manage several details from the logging information provided by UW's Syslog information. Here's a sample of the UW information: Oct 7 22:08:39 ns6 ipop3d[15432]: pop3 service init from 66.207.133.233 Oct 7 22:08:39 ns6

Hi, I'm trying to migrate from maildir to mdbox while preserving the pop3 UIDL (and the imap UID). The problem is, for maildir we use (for compatiblity with qpopper): pop3_uidl_format = %f Problem is, as soon as I convert that to mdbox, then whenever a client issues the UIDL command via a POP connection, the connection is closed and this error is displayed in the log: Error: UIDL: File

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

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

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

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

I have been setting up a new mail server and copied our client's old mail to it. The old server has Courier (under Plesk), we're using Dovecot on the new server. Most accounts seem to work fine (under IMAP or POP3), but for a few we're getting the following in the /var/log/mail.err. Error: Message ordering changed unexpectedly (msg #1: storage seq 140 -> 1) Fatal: Can't

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 28 March 2019 16:37 Kevin A. McGrail via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

I have installed rc22 and tried it with my mbox-based mail - fine. Then I converted that mbox to Maildir to see if new feature (saving state without QUIT) works - first run - I get time out. Second run - I get rest of the Maildir scanned and get into mailbox. Fine. but.... # telnet enders2 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'.

With a INBOX mbox created by UW IMAP the messages in INBOX mbox contains the X-UIDL field When I use Dovecot POP3 with pop3_uidl_format = %08Xv%08Xu on the first run, X-UID is inserted, but all messages are downloaded again. What am I missing, I don't want the clients to download the read messages again. Thanks Bertrand Leboeuf leboeuf at emt.inrs.ca

Hi, I just migrated a server running qmail+vpopmail+maildir to sendmail+dovecot+maildir+vpopmail The migrating is working great thanks to the help from the list and the wiki. I'm now running the infamous problem about duplicating emails, because of pop3 UIDL mismatch. My question is: anyone knows that the pop3_uidl_format string for a vpopmail server? I'm using vpopmail auth and

On 3/28/2019 7:42 AM, Aki Tuomi via dovecot wrote: > olution: > Operators should update to the latest Patch Release. The only workaround > is to disable FTS and pop3-uidl plugin. Hi Aki, thanks for the CVE.? For quick mitigation, can you confirm how to disable these plugins and what they provide?? We'd like to assess if we are using them while we rollout the fix. Regards, KAM

On 3/28/2019 10:40 AM, Aki Tuomi wrote: > > check for fts in mail_plugins. pop3-uidl is used by pop3_migration > plugin. Sorry if I'm dense but can you be more specific?? Are you talking about checking conf files or binary files?? For example, does the existence of /usr/local/lib/dovecot/lib20_fts_plugin.so imply an exploitable situation?? Are their settings in a conf file that

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, 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