similar to: Solution: NFS & Dovecot!

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

Hi, yesterday I updated my second server from Debian Squeeze to Debian Wheezy. Since todaay I get the followinig errors in my logs: Error-Log: ... Jun 26 09:08:28 mailstore dovecot: imap(user at domain.net pid:28898 session:<iuMX3Lf8fACXLrFC>): Fatal: master: service(imap): child 28898 killed with signal 11 (core dumped) ... Mail-log ... Jun 26 09:08:28 mailstore dovecot: imap-login: ID

Try as I may, I cannot get Dovecot to allow anything but blank passwords listed in a custom file I made for the purpose. It will not recognise anybody in passwd. Only using POP3 on an internal network so little danger of incursions. Once I created a password file with user names and no password, one user could login (from Outlook 2003) but another could not. Telnet test also fails to

Hello, With the same basic configs as in my previous messages, I tried with the maildir format instead of the mbox format. That is, in both cases ("virtual" uids/gids vs a single "real" uid/gid), doveconf -n shows: mail_location = maildir:~/maildir instead of: mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox Here too, with "virtual" uids/gids, connections thru

Hi, we recently upgraded dovecot from 1.0.5 to 1.1.3+latest patches. After the upgrade I saw some errors in the logs and I'm not sure whether they're a cause for concern. Our setup is 2 servers running openSUSE 11.0 and a NetApp Filer as storage backend. Following is the config: protocols: imap imaps pop3 pop3s login_dir: /var/run/dovecot/login login_executable(default):

Hey guys, After many trials and tribulations I have now got some fairly stable NFS clients serving dovecot-lda and pop3/imap. Over a 9 hour postal/rabid stress test only saw 5 errors for the 4 servers. Wondering if anyone can shed a bit more light on what they mean exactly. I have tried to find "Resource temporarily unavailable" and "No locks available" in the src to get

HI I don't know if this is a dovecot issue or a client one. But as Dovecot is the most recent change, I'll start here. I have a server that's been running Courier for about 6 years and in all that time I think I've only ever had 1 issues where an entire mail box was repopped by a webmail client. However, since moving to a new server and dovecot 4 weeks ago, I've now had the

Hello list, I am currently testing a setup for a PoC wit this configuration. - 1 x Frontend dovecot for proxying IMAP/POP3/LMTP/ManageSieve/Submission - 2 x Backend dovecot with local mail storage The frontend does the user authentification and communicate with the backends using a master password The fronted accepts PLAIN and LOGIN auth mechanisms and talk with backends using PLAIN auth

Hello My provider allows to activate/deactivate a forwarding rule by sending a SIP MESSAGE. This is done outside a call. That is, while there is no ongoing call, a SIP client just sends the following message: MESSAGE sip:543951354657 at callfwd.sip.providerx.com SIP/2.0 Call-ID: b9ba106e-613a-46b9-8a4d-0efb4dc0a0f2 CSeq: 1 MESSAGE To: <sip:543951354657 at

Hi, yesterday I upgraded to version 2.2.13 under Debian Squeeze. Since today morning sometimes my logfile shows the folling error: .. Jun 24 10:14:16 mailstore dovecot: imap(user at domain.net pid:23434 session:<jf6yi5D8TADD/vzh>): Fatal: master: service(imap): child 23434 killed with signal 11 (core dumped) ... The kernel error log shows: ... Jun 24 10:14:16 mailstore kernel:

Hello, My first time on this list, just switched from courier imap/pop3 system to dovecot. Imap part is great, pop3 seems to suffer, been fighting it for a week. Anyway, the reason for this post is that I have seen these pop up in my logs, and on one of my mailheads there were some 50 lines of this dovecot: 2008-10-26 09:33:54 Error: auth(default): BUG: Authentication client gave a PID 15661 of

These changes apparently broke something: > 2006-04-24 09:17 Timo Sirainen <timo.sirainen at movial.fi> > > * src/lib-index/mail-index-transaction.c: Fixed crash while > updating keywords (broken by recent changes). > > 2006-04-20 14:10 Timo Sirainen <tss at iki.fi> > > * src/lib-index/mail-index-transaction.c: If we sorted appended > messages, we

Hi, I just installed dovecot 1.0 beta 7 and I have these errors: May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=::ffff:xx.xx.xx.6, lip=::ffff:xx.xx.xx.1 May 5 09:21:27 mail dovecot: POP3(user2): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user3>, method=PLAIN,

Hi I'm trying to build a cluster of two servers with dsync replication (based on http://wiki2.dovecot.org/Replication). My test setup works fine for very simple tests, I can log in to both servers, copy a message to one of the servers and it successfully apperars in the other account. But, if I try to copy a large amount of messages at once to one of the accounts, my maillogs get flodded with

http://dovecot.org/rc/ I should have released 0.99.14 already, but I've been way too busy lately. Among other things I started working half-time at Movial (www.movial.fi). I had forgotten 8 hour work days at office could take so much time :) Anyway.. There has been a few changes since RC1 so I'll still make RC2 before the final. Changes since RC1: - passwd-file userdb wasn't working

Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend

Hi, I've upgraded a mailstore from Debian Jessie (aka oldstable) with Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1 today. It worked pretty well, except that we're seeing error messages very similar to this old thread https://dovecot.org/pipermail/dovecot/2015-July/101396.html It appears to be happening when a mail with multiple recipients on this message store is

All, On our main file server, all our home directorys are automount points. So /home isn't a real filesystem area, it points to a bunch of different home areas based on the auto.direct table. Example: /home/user1 mounts from --> /export/home1/user1 /home/user2 mounts from --> /export/home2/user2 /home/user3 mounts from --> /export/home2/user3 /home/user4 mounts from -->

Hello, Dovecot log is showing too many POP3 RETR entries which are identical lines. I also suspect that it is causing high pop traffic eating most of the network bandwidth. Here are some of the lines out of 11009 in a day. Such pattern is observed only for few users. dovecot version is 2.1.17. ============== Mar 20 00:00:07 pi3 dovecot: pop3(user at example.com): Disconnected: Logged out

hello guys, i am using dovecot v1.0.rc15-1~bpo1 from backports.org on a debian sarge machine as pop3 pop3s imap and imaps server. since some days it seems the pop-server will stop randomly. noone is able get mails, but imap is still working. the logfile says: dovecot: 2007-03-19 16:44:19 Info: auth(default): password(user1 at domain.de,212.100.55.y): Requested HMAC-MD5 scheme, but we have only