similar to: dovecot-auth: Too many open files

We use Dovecot on a cluster (10'000 domains, 30'000 account) without any problem with pop/imap. We use Dovecot 1.0 RC10 Now we use virtual transport from postfix for mail delivery. We need the Dovecot LDA for sieve support. We test this solution on some domains with success. But if we change the configuration of all our domains, we have a lots of bounce with this error in postfix

it's verry slow i saw in the archives something about strace and will include it below please help: my dovecot is crawling when downloading through pop here is my last trace file contents :18:04.657706 poll([{fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=15, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=13, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=17,

Hello Timo and others.. 14:09 mail:~# dovecot --version 1.0.rc31 Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : inotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with

Hi, I installed Dovecot on FreeBSD 4-STABLE machine and have a problem. MTA is postfix delivering to ~/Maildir, runs perfectly. Dovecot is configured to use plaintext auth, config file is at the end of this mail. When trying to get mail via IMAP, I'm getting the following errors: /var/log/dovecot.log > Aug 24 12:00:35 Info: Dovecot starting up > Aug 24 12:00:51 Info: Login: goshik

Hi, My laptop runs a local IMAP server so that I'm immune from breaking my mail client, and when playing around with powertop I discovered that Dovecot (in particular imap-login) wakes up every 1000ms and then every 50ms even when no clients are connected. A bit of stracing shows this: gettimeofday({1180875699, 667917}, NULL) = 0 <0.000010> poll([{fd=7,

Hi all, I have a dovecot installation which very suddenly decided to slow to a crawl yesterday after being totally fine for months. IMAP is fine, but POP3 is very painful to use, and frequently times out. here's my config: # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot_errors info_log_path: /var/log/dovecot_informational ssl_ca_file: /etc/postfix/ssl/cacert.pem ssl_cert_file:

Hi all, I'm pulling my hair out on this problem and wanted to throw it out there to see if anyone else had run across it. I recently restarted my server. There were some network config issues that caused the interfaces not to come back up, but my colo company got those resolved. However, after restart, my IMAPS server has stopped responding to outside requests. I can successfully access

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, in order to stress my Dovecot test installation a bit, I compiled imaptest10.c. Now and then I see: Logi List Stat Sele Fetc Fet2 Copy Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 33% 50% 100% 100% 100% 100% 30% 5% 5% 0 0 0 0 0 0 0 0 0 0 0 0 1/

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

I'm using dovecot 1.0.alpha4 on a freebsd 5.3 i386 system. Dovecot is configured to use mysql authentication and I'm running mysql 5.0.15 . Everything works fine, but after a period of inactivity (20-30 minutes ) when I connect and try to authenticate it just hangs. I noticed that the dovecot-auth worker process is not running anymore... from looking at the source code I understand that

Hi all, When setting auth mechanisms: plain login cram-md5 and only having pam passdb and passwd userdb. dovecot nevers starts and crashes reporting: Feb 29 10:19:41 pitux-clust-op1 dovecot: Dovecot v1.0.10 starting up Feb 29 10:19:41 pitux-clust-op1 dovecot: auth(default): CRAM-MD5 mechanism can't be supported with given passdbs Feb 29 10:19:41 pitux-clust-op1 dovecot: Auth process died

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded,

Hello everybody! We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem). A typical node: # cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) # uname -r 3.10.0-693.11.6.el7.x86_64 # rpm -qa |grep libvirt libvirt-daemon-driver-qemu-3.7.0-1.el7.centos.x86_64 libvirt-daemon-driver-storage-disk-3.7.0-1.el7.centos.x86_64 libvirt-3.7.0-1.el7.centos.x86_64

Hi there, I'm using the latest Thunderbird & Dovecot. I'm trying to setup either pop3s or imaps. The plain versions of the protocols both work fine for me, even with the TLS option selected in Thunderbird. But when I try to use the ssl versions, my client does not negotiate - it just time's out. I have as much logging enabled as possible and the only thing that shows up

Hello, I'm running an Debian etch box with unstable and ever since the last upgrade to dovecot, I've seen odd things. At times, I would see emails would go missing from the Inbox or other folders, and I couldn't move emails that were moved from the Inbox to another folder back into the Inbox. These have seen gone away since I removed all dovecot.* files and .index* files from my

Hi! Occasionally of late, I've seen a few cases where libvirtd cpu usage shoots up to 100% and stays there indefinitely. This seems to happen when a QEMU VM is starting up, although on one occasion I *think* I saw it happen after a QEMU VM was p2p-migrated. Doing strace -f -p <libvirtd pid> reveals a flood of poll() functions calls like these: [pid 1690] poll([{fd=3,

I'm trying to get dovecot running on my VPS and the main imap process is receiving a SIGKILL from what I presume to be the Linux Kernel and/or OpenVZ. This happens after I login and my client(s) just sit their idling. The mailbox is empty. I'm not running out of memory. stracing the process doesn't show anything interesting... ... gettimeofday({1233024777, 844804}, {420, 0}) = 0

On Wednesday, 26 February 2020 15:08:24 CET Daniel P. Berrangé wrote: > On Wed, Feb 26, 2020 at 02:39:04PM +0100, Pino Toscano wrote: > > select() has a maximum value for the FDs it can monitor, and since > > the libguestfs library can be used in other applications, this limit > > may be hit by users in case lots of FDs are opened. > > > > As solution, switch to

select() has a maximum value for the FDs it can monitor, and since the libguestfs library can be used in other applications, this limit may be hit by users in case lots of FDs are opened. As solution, switch to poll(): it has a slightly better interface to check what changed and for which FD, and it does not have a limit in the value of the FDs monitored. poll() is supported on the platforms we