search for: joallesi

We're running into an issue where sendmail is only receiving one e-mail, but after a client accesses the message via IMAP and moves it to another IMAP folder, the message duplicates but each message has different X-UID headers. Has anyone ever seen this type of anomaly before? Is it a bad IMAP client, or a known bug? Running 1.0.7 Thanks!

We're stuck on RHEL 4.x, so we're currently working on a plan to live in harmony with .99 for another year or so. With that said, the plan is below. Let me know if you have any other recommendations. [ ]Convert to high-performance mode vice high-security to reduce overall resource usage. [ ]Implement iptables throttling for new connections to prevent denials of service. [ ]Covert from

All, [version: dovecot-0.99.11-4.EL4.src.rpm] We recently experienced an issue that prevented all new IMAP logins from occurring. Although it appears that it was due to running out of available system file descriptors, I'm still not sure what the true root cause was as I can't replicate the same error in our test environment. The system file descriptor max was set at (per `cat

This morning dovecot stopped allowing pop3 logins. In the logs I found the messages below Is there a config value for the max open files ? Dec 7 10:00:22 frigga dovecot: execv(/usr/local/libexec/dovecot/pop3) failed: Too many open files Dec 7 10:01:14 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga

All, Is anyone using iptables (recent module), or any other alternatives, to throttle the number of new imap or pop connections per minute? We have some applications that like to login every second to pull mail using imap, so we'd like to protect the entire dovecot server from these applications. We've already made the change over to high-perf mode, but we still need some type of denial

I have referred to the wiki and the RFC, but I still can't find the exact answer I'm looking for. From what I know, Dovecot uses the IMAP standard of 32 bit integers to uniquely identify messages. After a message is deleted from the mbox, can this UID ever be reissued to a new message or is that UID retired? What about after the 2 billion limit is reached? Thanks!

Any known issues with these locking strategies? (RHEL 4.x default) Dovecot: mbox_locks = fcntl Procmail Locking strategies: dotlocking, fcntl() We're considering moving to all dotlocking after a recommendation from RedHat, even though we're not using NFS at all. Thanks!