similar to: UIDL question

Good afternoon, I am considering to upgrade from Dovecot 1.1.18 to 1.2.x and was reading your Wiki regarding any changes and found: "If you were using e.g. mail_location = maildir:/var/mail/%h, just change it to mail_location = maildir:%h and add /var/mail/ prefix to home dirs." I am currently using: "mail_location = maildir:~/Maildir" in combination with vpopmail. Does

Good morning, Still not having luck to get the LDA to work, using Qmail + Vpopmail and read the wiki. I'm using: auth default { mechanisms = plain passdb vpopmail { } userdb vpopmail { } user = vpopmail count = 1 ssl_require_client_cert = no } Which work well for authenticating users, however when using the following in a .qmail file: |/var/qmail/bin/preline -f

Hi, today we have a problem our mail server about user accounts. (something about prefetch) anyway i corrected, but some clients re-download emails again. how can i stop this .I've read about some forums about UIDVALIDITY ? is it posibble prevent clients redownload emails with pop3 ? thanks in advance. -- Sel?uk YAZAR

Hi all, I'm trying to get Relay-Ctrl to work (as explained on http://wiki.dovecot.org/HowTo/PopBSMTPAndDovecot), however when i add: mail_executable: /usr/local/bin/envdir /etc/relay-ctrl /usr/local/bin/relay-ctrl-chdir /usr/local/bin/dovecot-settcpremoteip /usr/local/bin/relay-ctrl-allow /usr/local/libexec/dovecot/imap to /usr/local/etc/dovecot.conf I get the following error message

Good morning, I have a question. Currently we are using Dovecot to handle our pop3, pop3s, imap and imaps connections. Our virtual domain management backend is vpopmail. Which works beautifully. Our current setup requires users to login with their email address and password (user at domain). We are now looking at migrating another server to our environment where users are logging in with their

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 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 everyone Been spending the whole day on the wiki and in the list archives on using dovecot for POP3 mail. I'd like to present my findings and ask for some feedback. Our current software setup: * Courier-IMAP running POP3/IMAP * Postfix MTA * MySQL backend for user and login info As for the system layout, it looks like this: * NFS server which is the same server that houses single

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

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

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

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

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

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

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

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

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 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 '^]'.