similar to: mdbox and pop3 locking

If pop3_lock_session = yes, how does Dovecot LDA handle the situation when the pop3 mbox is locked? Does it requeue mail for later delivery immediately (EX_TEMPFAIL), or wait until mbox_lock_timeout? Thanks, Ken A. Pacific.Net

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

Hello dovecot-users, I have a question/suggestion regarding the submission_host feature of the lda (either via dovecot-lda binary or lmtp) in combination with sieve. When trying to deliver message to a mailbox and this message has a sieve redirect action applied to it, dovecot is using the configured smtp server to forward the message just fine. Unfortunately, if the server configured for

I have a problem I can't seem to fix. I have dovecot configured to do POP3 with plain text authentication using a MySQL database. I am using Dovecot 1.0.7 with fcntl locking. My problem has been when an iPhone/iPod checks email. The iPhone/iPod doesn't disconnect with a TCP FIN packet and it leaves the mailbox in a locked state and prevents the user's desktop from checking

I'm preparing a migration of several mailboxes to another machine. The different useraccounts are distributed to different backend machines by means of a dovecot LMTP/IMAP/POP proxy. Proxying is working really well (now that the kernel does as it should). But how can I "lock" a user during migration? The plan is: ============ * lock the user * kick the user (doveadm kick) *

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:

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

This doesn't seem to affect clients, but I'm seeing an occasional pop3 error in the log over the last week. Any ideas what is causing this? Thanks, Ken > Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Connection > closed top=0/0, retr=0/0, del=0/4582, size=246709805 > Jul 4 15:04:03 mail dovecot: POP3(user)x.x.x.x: Panic: file > pop3-client.c: line 585

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e

I'm new to Dovecot, using 1.1.8 and I just wanted to verify that what I am observing is the intended behavior. I'm using Maildir++ quota. When a message is delivered to a mailbox that cannot accept the message because it would place them over the quota limit, deliver states to the MTA that the messsage was delivered successfully (example using postfix): Jan 17 12:05:31 msa

Hi, I have a couple questions about migrating from 1.x to 2.x I'm needing to support larger mailbox sizes and mdbox seems like the right format to use to get larger size boxes and maintain, or possibly even increase speed. Is that correct? Am I correct that the best way to accomplish this migration is to copy the mboxes over to the new server and then use dsync to convert them to mdbox?

Hi, while testing out dovecot 1.1, I found that when you set quota_full_tempfail = yes in dovecot.conf and use the deliver -e command line flag, no deferral reason is printed, thus breaking my fancy quota_exceeded_message. This appears to be because of the if() block in lines 1003-1009 in src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug, and not intended behavior).

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

Hello, I need an advice about POP3 and NFS with Dovecot 1.0 (as 1.1 is still tagged beta) . I currently have all messages and indexes under a NFS partition . I thus turned cache off using actimeo=0 . Of course, my current architecture does not allow me to keep the same user on the same dovecot server. Now, I have some NFS issues with high percentages of getattr() . If I understood well, the

Fixes, mostly: * The login and master usernames were reversed when using master_user_separator (now the order is UW-IMAP compatible). * Killing dovecot master process now kills all IMAP and POP3 processes also. + -a parameter to dovecot prints now all settings that Dovecot uses. -n prints all settings that are different from defaults. + Added pop3_lock_session setting + %M modifier

Fixes, mostly: * The login and master usernames were reversed when using master_user_separator (now the order is UW-IMAP compatible). * Killing dovecot master process now kills all IMAP and POP3 processes also. + -a parameter to dovecot prints now all settings that Dovecot uses. -n prints all settings that are different from defaults. + Added pop3_lock_session setting + %M modifier

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the

I am using dovecot in mbox format. I'm going to set to leave the 30-day mail to the server with the mail client. The other day, some of email was received duplicate When receive mail. Mail does not arrive between Nov 4 11:09:03 and Nov 4 11:13:25. There should be the 259 (274-15) messages at the time of Nov 4 11:09:03 on the server from the log. But there were the 280 messages at the time of

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl