similar to: UIDL format

Migrated a 1.0.2 server to 2.0.16 (same old box). IMAP seems working Ok. POP3 give problems with some clients (Outlook 2010 and Thunderbird reported). Seems authentication problem Below my doveconf -n (debug enbled, but no answer found to the problems) Any hints? Thanks, P. # doveconf -n # 2.0.16: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with:

Current box: CentOS 4.x (32 bit), dovecot 1.02, mbox format New box (supposed): CentOS 6.x (32/64 bit ? ), dovecot 2.04, mbox format The server have about 3.000 active users (unix users); /var/mail is about 100 GB; /home/Users about 150 GB I read the docs and searched on the net, but still request hints for planning the migration. 32/64 bit? Tricks to avoid users get all messages ...?

Hi All, Our test users re-download the mail they've left on the server when they switch from Qpopper to Dovecot. Qpopper includes the X-UIDL header - X-UIDL: X8V"!E)<"!58?"!"9C"! - on read messages. Any suggestions are appreciated. I've included my dovecot configuration. Thank you, Tristan --- Tristan Tristan Goguen CEO, ILAP? T: 416-250-5600 ext. 205 F:

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

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

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:

I'm sure I'm missing something obvious :-( Dovecot version 1.1.6, pam authentication via ldap (openldap). basicly, we use: passdb pam userdb passwd which work fine, except for Outlook/OL Express users that are asked for their password whenever they "send/receive"... We've had also "passdb shadow" that somehow "fixed" this but allowed also users with

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

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

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

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is

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

I noticed a problem with handling UIDL msgnumber in test46. If you do "UIDL 1" on a POP3 connection it returns the UID of the message followed by a dot and an error message. I made 2 changes: I added the following line to line 527 of src/pop3/commands.c ctx->message = message; I changed line 559 from: if (list_uids_iter(client, ctx)) to: if (!list_uids_iter(client, ctx))