similar to: migrating from maildir to mdbox, preserving pop3 UIDL

A warning to those considering to upgrade to Debian 10 (buster): we have seen occasional NFS hangs with dovecot when using the stock debian buster kernel (4.19.67-2+deb10u1). When we downgrade to the debian stretch kernel (4.9.189-3+deb9u1), the issue does not occur. Note that we *only* downgraded the kernel, the rest of the OS is still debian buster. Dovecot 2.3.8. A little more info: we have a

I tried setting the "destuser" setting on the LMTP director as follows, to preserve the original envelope rcpt: protocol lmtp { auth_socket_path = director-userdb passdb { driver = ... override_fields = destuser=%{orig_user} } } The passdb driver would return the appropriate "user" for each alias. Suppose, for example, user1 has emails user1 at domain.tld,

I wanted to forward information from the director to the backend dovecot (original login name), so I had the userdb on the director return a forward_ologin variable. However, when I tried to use that variable in the "password_key" query on the backend dovecot, ${forward_ologin} was expanded to UNSUPPORTED_VARIABLE_forward_ologin. After testing a bit and looking around in the source a

There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout: Jun

Hi, We're synching mailboxes, changing format from maildir to mdbox, using doveadm backup/doveadm sync. When still running 2.2.36, 'doveadm backup' also synched the sieve scripts, without issues. After the upgrade to 2.3.5.1, the sieve sync stopped working. We're using the pre-built 2.3 packages from https://repo.dovecot.org/ce-2.3-latest/debian/stretch In fact, when I now

Occasionally, all of our directors get stuck in an endless loop. Likely triggered by some network event, but I haven't been able to isolate exactly what triggers it, and am unable to reproduce at the moment. When this happens, it makes the dovecot/director process on all directors unresponsive, making login impossible. Restarting dovecot "fixes" it. Here's the info collected

TESTED AND RUNNING, MIGRATING from MBOX to MAILDIR, PRESERVE UID and OUTLOOK sees the email as downloaded. I hope this helps a lot of people out there. Feel free to post this somewhere else too. By: Horn Wijaya (hwijaya at nodens.biz) 8th May 2008 I have been searching for weeks for a foolproof method to migrate all my users mbox to maildir/dovecot without having the pain of downloading

(I'm not subscribed to the list, please Cc me on replies). We have configured sshd to listen on port 80 for some of our users who are behind sufficiently paranoid firewalls. However, others are now confused since they're expecting a web server on port 80. So, I created a small patch (just as proof-of-concept so far), that determines the type of client connecting. A web client will start

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 all, Does anyone have a good migration document for Migration from Maildir (old server 2.1.x) to mdbox onto another new server with SIS preserving POP3 UIDLS. Preserving UIDLs is of paramount importance so that clients don't download mails again into outlook. Regards/DP --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: > > On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> Hi, >> >> We're synching mailboxes, changing format from maildir to mdbox, using doveadm backup/doveadm sync. >> >> When

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:

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

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

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