similar to: Solaris NFS woes

Folks - Some time ago as I migrated to dovecot 1.0, I ran into all sorts of problems with file locks, and I tried various solutions. Apparently, in the process, I got a bit careless and removed all my dovecot-uidlist files. They're gone. My understanding, however, is that they should come back, but this doesn't happen. I've been forced to run with index=MEMORY in 1.0 for

> > Shot in the dark here: > > What are you using for the sharenfs value on the ZFS filesystem? Something like rw=.mydomain.lan ? They are IP blocks or hosts specified as FQDNs, eg., pptank/home/tcrane sharenfs rw=@192.168.101/24,rw=serverX.xx.rhul.ac.uk:serverY.xx.rhul.ac.uk > > I''ve had issues where a ZFS server loses connectivity to the primary DNS server and

Hi Benjamin: I think that the following link will give you an idea for what you need to know: http://www.cisco.com/warp/customer/620/roadmap_b.shtml This is for the naming: http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not you worry you will not loose anything with the new

Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 <https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180606/996cfe38/attachment.html>

Does anyone have any idea what can cause nmbd to begin gobbling CPU? We are running Samba 2.2.4 on HP-UX 10.20, having upgraded from Samba 2.0.10 about a month ago. Our clients are a mixture of NT 4.0 and Win2K. Today, we have begun to see widespread client drive disconnections, and nmbd is averaging 60%+ CPU usage with peaks up to 100%. We have heard reports of network problems at our site

Hi everyone, some days ago I had trouble with my NFS-Server (high delays) which caused dovecot lmtp to deliver the same message several times (up to 10x). I recognized some old/unused .nfsXXXX files in the maildirs which seemed to be index files. I deleted them and everything was fine again. However, there are still 2-3 mailboxen where mails (old and new ones) are delivered multiple times. All

On Fri, 19 Apr 2019 11:58:23 +0200 Martin Krämer <mk.maddin at gmail.com> wrote: > Hi Rowland, > > thanks for your reply. > > > I personally would have used 'cache directory =' , see 'man > > smb.conf' for the difference. > From description based on man smb.conf I would absolutely agree. > I have tried and set the "cache directory"

I use Dovecot's deliver as the LDA for Postfix in a virtual user setting. My maillog reads: Oct 22 00:17:51 mail dovecot: auth(default): master in: USER 1 mark.ruys at in2sports.net service=deliver Oct 22 00:17:51 mail dovecot: auth-worker(default): sql(mark.ruys at in2sports.net): SELECT maildir AS home, 5000 AS uid, 5000 AS gid, CONCAT('dirsize:storage=', round(quota/1000))

Hi all, Please excuse me if this question is not appropriate for this forum: Lets assume that samba server crashed or was shut down abnormally, while users where holding open files in the server. In this case, I've noticed that locking.tdb is not being cleaned when samba is restarting. I was wondering why shouldn't it be cleaned. Thanks, Nir

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? -

Thanks for mySql For Squat vs Solr, Solr does not reach Squat by very far in terms of results : If I setup Solr, and search (via the search in Roundbube or Evolution) for a keyword or part of the keyword, the results are complete non sense. The diference between "search in full body" and "search in fields" does not even work. Solr with Dovecot seems very early beta

Hi How to solve this ? So many similar segfaults Thank you On 2018-11-30 06:11, Joan Moreau wrote: > ANother (very very long) example : > > # gdb /usr/libexec/dovecot/indexer-worker core.indexer-worker.0.3a33f56105e043de802a7dfcee265a07.21017.1543533424000000 > GNU gdb (GDB) 8.2 > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or

finally managed to locate the dump here the output: # gdb /usr/libexec/dovecot/auth /var/lib/systemd/coredump/core.auth.0.3a33f56105e043de802a7dfcee265a07.28130.1543516118000000 GNU gdb (GDB) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it.

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence for making things working correctly over nfs. But I run into locking issues if I run over nfs. procmail is doing the delivery over nfs. uw-imap was ruining over nfs. dovecot is fine if its on the nfs server (i.e. it has local access to the disk, no nfs) I run into lock deadlocks if I run dovecot over nfs Users

We've just cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first

> On December 4, 2018 at 8:18 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > We don't consider it as "very early beta". We consider it production ready. It is bit more work to set up though. FWIW, Squat has been deprecated since 2.0, so none of this should come as a surprise. https://wiki.dovecot.org/Plugins/FTS > Aki > > > On 04 December

I have to make dotlock work because this openwebmail thing only supports one of dotlock or flock, but procmail delivery does dotlock and fcntl. procmail correctly creates a dotlock file in /var/spool/mail/username.lock when delivering, I can watch this with `while :; do ls -la | grep lock; done`. It works fine when lock_method=fcntl, but no dotlock file shows up in /var/spool/mail.

A mail user reported that he filled up his INBOX (despite reminders he was approaching his filesystem quota), and furthermore, he could not fix the situation because he couldn't expunge message he marked for deletion. The dovecot logs revealed the cause dovecot: imap(user): Error: open(/var/mail/user.lock) failed: Disc quota exceeded This created an impasse where a user cannot free