similar to: NFS and performances

Does anyone got any example about how to implement delay_until = timestamp ? I am not sure where i can setup it. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20230307/28560a87/attachment.htm>

Hello - I know I am not the only one that will be trying, or has tried this before. Here are my questions! NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with relevant patches (utime, etc) Backend - netapp filer End users - various clients all running IMAP It looks like 1.0.beta8 is definately the way to go. I have a few questions with regards to setup. Is it now

Hi, Does anyone have experience with bending the NFS recommendations to get better performance? The question is has anyone, with Maildir and the INDEX= on NFS (i.e. dovecot.index and dovecot.index.cache, set mail_nfs_index to no. If so, was it better to turn maildir_copy_preserve_filename to on or did it help to turn if off. The other question is did you play with turning off atime updates

Hi Timo, Hello list, I've played around with dovecot-1.1.1 on AIX to get quotas (especially NFS quotas) to work. I've found that dovecot doesn't implement handling of 'mntctl' and so it is unable to determine filesystem mountpoints on AIX correctly. Your'll find more information about 'mntctl' here:

Hello, We are having performance problems trying to migrate our pop/imap servers to a new version. Our old servers are 4 debian lenny with 5GB of RAM running of XenServer VMs with kernel 2.6.32-4-amd64 and dovecot 1.1.16. New servers are 4 ubuntu 12.04 with dovecot 2.1.5 running on vmware vm with 6 cores and 16GB of RAM and kernel 3.2.0-24-generic. On both server we are using nfs 3 with

We recently moved all our users from the Washington IMAP server to Dovecot. There has been a substantial improvement in performance, but some users are reporting duplicate messages, and we see 'Stale NFS file handle' errors in the syslog. Does anyone know what would cause this ? The errors relate to the index file, eg. Nov 29 00:49:47 imap-e.ucl.ac.uk dovecot: [ID 107833 mail.error]

On Fri, 23 Mar 2018 09:53:00 -0700 Shaun Johnson <shaun at linuxmagic.com> wrote: > Greetings Dovecot List, > > I have a bit of an edge case I am trying to resolve. I am currently > using dovecot on Ubuntu 14.04 - Ubuntu package version: > > 1:2.2.9-1ubuntu2.3 > > I have attached the output of doveconf -n to this email - but to > describe the configuration

Greetings dovecot mailing list. I have implemented a relatively big dovecot setup (250k users) and overall I am very pleased with dovecot functionality and performance. Setup description: * dovecot 1.0.x * FreeBSD 6.3 * Postfix (using dovecot deliver as LDA). * OpenLdap backend * Storage is NFS (Clariion EMC NFSd for Maildir, and FreeBSD NFSd for Indexes). * Locking is fcntl using

Hi, About a week ago I upgraded our reasonably heavily loaded mail servers from a pretty recent courier version to dovecot-1.1rc10. IMAP performance on dovecot is amazing, however POP3 performance is worse than courier :-( I have uploaded some munin graphs taken today to http://linweb.atlas.pipex.net/dovecot/; the dovecot server is handling about 2000 pop logins/sec and 300 imap sessions (but

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

Hi, I'll try to keep short. My primary question is what, in people's experience, are the best configuration settings for to avoid potential NFS cache locking issues in an interesting heterogeneous environment? We appear to have a workaround for some locking issues we have seen, which is turning off IDLE. Upgrading our version of dovecot from 1.1.4 is likely to address some core

I configured dovecot on a Fedora Core 2 system - the version that comes with FC2. I was using it with a RHEL 3 NFS server. Dovecot would again and again get stuck trying to grab an fcntl lock, even though I specified that it should only use dotlocks in dovecot.conf. Sometimes it would segfault (leaving things locked?). Often there would be two dovecot imapd processes for the same user.

On 2019-09-26 03:44, Asai via dovecot wrote: > Greetings, > > We're in the process of upgrading our Dovecot server to new hardware > and new expanded storage. We planned on using an NFS share for the > mail storage, as we're running Postfix / Dovecot on a VM and wanted to > separate out the mail storage from the VM for backup reasons. > > I read as much as I

I've been working on setting up a Dovecot server with a maildir mailboxes stored over NFS. Initially, everything was working great, and then I started seeing this error as previously discussed on the list in my maillog: (mail_index_expunge): assertion failed: (!t->view->external) Timo, in another thread, suggested to remove line 247 in mail-index-transaction.c in the test52

For the record, ever since the last patches for NFS got committed, we don't see locking issues over NFS in general across all our platforms, but it also depends on how you configure your NFS server. You might find that this is not a dovecot issue, but an NFS issue. You might want to post more about your NFS setup(s) and then someone on the list might better assist you. -- Michael -- On

Hi all. My clients have got problem accessing dovecot by "Windows live mail (Windows 7)" client. The problem is that users can't delete two or more folders one-by-one. There is no errors deleting first folder (new dir /storage/vol1/mail/domain/user/Maildir/..DOVECOT-TRASHED appeared and wasn't deleted). If I try to delete second one, error occurs (user, domain, IP address

Hello, since updating two of our backup mailservers from dovecot 1.1.16 to 1.2.4 i get the following errors from dovecot-deliver when receiving (smtp) mail. Oct 16 00:10:42 mail3 dovecot: deliver(user): write_full(/home/r/user/.temp.backupmail.22774.d17050a07b2108e8) failed: Stale NFS file handle Oct 16 00:10:42 mail3 dovecot: deliver(user): copy: i_stream_read() failed: Stale NFS file handle Oct

Hi, I've discovered some interesting behaviour when running Dovecot on a GlusterFS volume (3.10) that is mounted via NFS 4.1 (ganesha NFS). First of all, using the usual settings for NFS storage seemed like an obvious choice for my setup (Dovecot 2.2.33.2, CentOS 7.4): mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always maildir_copy_with_hardlinks = yes

Dovecot 1.0RC15 running on Fedora Core 5 kernel 2.6.18-1.2257.fc5smp. A SLES10 server (kernel 2.6.16.21-0.8-smp) has the home directories on an ext3 partition mounted with options (rw,acl,user_xattr,usrquota) which is then exposed as an NFS mount with server side options (rw,no_root_squash,no_acl,async). The home directories include Maildirs to which postfix delivers. The Fedora Core 5

> I built an email system using a proxy / director pair (IMAP, POP3, LMTP) > and a backend pair. > > To have an HA system, I would like to understand if it is better to use > an NFS export or replication to save emails and index files > > NFS is provided by a NAS (in HA), while for replication I would use the > local backend disks > > Which of the two systems is