similar to: dovecot ldap failed to recover

One of our dovecot-servers (v2.0.14) got a bit too busy last evening: Sep 13 20:39:18 popimap1 dovecot: master: Warning: service(pop3-login): process_limit reached, client connections are being dropped then logged a few: Sep 13 20:39:20 popimap1 dovecot: pop3(XXXXXXXXX at YYYYY.YY): Warning: I/O leak: 0x3829233d20 (10) Sep 13 20:39:20 popimap1 dovecot: pop3(XXXXXXXXX at YYYYY.YY): Warning:

I finally upgraded to v1.2.16 on my backend servers, with ldap instead of previously mysql, and put a couple of dovecot v2.0.8 directors in front of them (used haproxy previously). It seemed to work OK initially, but after a few hours we got bit by "Connection queue full" problems on the directors. So I now set default_process_limit=512 and also: service anvil {

I've had 18 instances of this error the last 24 hours: Sep 8 08:56:00 popimap1 dovecot:: lmtp(10529, first.last at example.om): mGdAOtdlaE4hKQAAg/aw4w: msgid=<B8FA3D5B230184409450D51D522678404E5052 at ASP-EX02.ASP.lan>: save failed to INBOX: BUG: Unknown internal error 17 on lmtp-server A, and one on lmtp-server B. On server A it was a message with 55 recepients, where 17 failed

I''m trying to time a function within Firefoxwith a pid$target probe [2]. e.g dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 13954 -s menu- construct.d -s sigcont.d elapsed: 12.7942481ms cpu : 7.7911194ms count : 40 times I''m also measuring Firefox startup time by running it arguments like this: ... file:///Users/joelr/work/mozilla/startup/startup.html#`python

Hi, For the past day, I have been researching about making dovecot to support mailfront (http://untroubled.org/mailfront/) imapfront-auth natively and able to use mailfront imapfront-auth with dovecot imap v1.2.16 without starting any dovecot related services and no /etc/dovecot.conf file is required. More information about this can be read at:

Hi, I am reinstalling my server and i have encoutered a strange problem, both dovecot 2.0.13 and 1.2.16 are reporting me a problem with fd_send Invalid argument on imap login. I am running dragonfly bsd 2.10.1., compiled dovecot from pkgsrc. Can someone help me out or at least point me in some direction, i am a bit lost... :( Aug 15 10:01:00 master: Info: Dovecot v2.0.13 starting up Aug 15

Ok, so I think I have a complete explanation for the difference between the *BSD behaviour and the Linux/Solaris behaviour. Well, almost complete :) Pull out your trusty copies of "The Design and Implementation of the 4.4BSD Operating System" as well as "Unix Internals: The New Frontiers". Specifically, pages 111-112 and 344 of the former and page 108 of the latter. It comes

What are the major differences between Versions 1.x and 2.0? I am beginning to set up a new mail server for a small group of users (~20 accounts). Options are the "0.99" version pre- packaged with RHEL-4, or building v1.2.16 or v2.0.7. Just wondering what the list recommends for a new installation. Thanks, - Don

It's long over due, but now I finally plan on upgrading from v1.0.15 to v1.2.16 on our servers. Would appreciate any comments! We have 7 servers, all running of the same GPFS filesystem. Both maildirs and indexes are stored here. We use dovecot for POP/IMAP and deliver. Currently we're using mysql as authentication source, but want to move to using ldap instead. Can we upgrade one server

We have quite a few frontend mail gateways that deliver incoming email trough our dovecot director (lmtp proxy) to the backend lmtp servers, and are seeing this logged on the frontend mail gateways: Sep 5 10:51:56 mailgw1 postfix/lmtp[23443]: 0E2F41C01A: to=<me at example.com>, relay=loadbalancers.example.com[192.168.42.15]:24, delay=61, delays=0.02/0.3/31/30, dsn=4.4.0, status=deferred

We upgraded our two dovecot directors from v2.0.14 to dovecot-ee 2.1.10.3 this week, and after that mail seems to be flowing a lot slower than before. The backend mailstores are untouched, on v2.0.14 still. After the upgrade we've been hitting process_limit for lmtp a lot, and we're struggeling with large queues in the incoming mailservers that are using LMTP virtual transport towards our

(dovecot v1.2.16) I've notice the log notices about increasing /proc/sys/fs/inotify/max_user_instances on my servers, and started wondering if inotify works for network/cluster filesystems.. I found this: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=311194 which says that there's no mechanism for one node to tell another node that a directory changed for GPFS.. And I

http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz.sig The important changes since v1.2.16: - Fixed potential crashes and other problems when parsing header names that contained NUL characters. - IMAP: Fixed a memory leak with ESEARCH command handling - Quota warnings could have been executed at incorrect

http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz.sig The important changes since v1.2.16: - Fixed potential crashes and other problems when parsing header names that contained NUL characters. - IMAP: Fixed a memory leak with ESEARCH command handling - Quota warnings could have been executed at incorrect

Hello kind people, Any help on this would be appreciated. Dovecot v1.2.16. Freshly installed today. Comes up with this during service startup (CentOS 5.5 -> "service dovecot start" <ENTER> : --------------------------- Restarting DovecotFatal: ssl_listen: Can't resolve address required: Name or service not known --------------------------- Here's "dovecot

Hello , Went to /etc/dovecot/dovecot.conf, hunted down "ssl_listen =" which I had set it up to "ssl_listen = required" and commented it out. Tried "service dovecot start" and it started. The USD2,000,000 question being : what does this do (I know , I know, I cannot remember, I documented all this for v1.2.14) and will I need it in the future ? THank you people,

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

Suppose I have a USDT probe in Firefox and that I''m trying to catch the startup with a probe like this: proc:::exec-success /execname == "firefox-bin"/ { start = timestamp; } and stop tracing when Firefox hits this USDT probe: mozilla:::main-entry { exit(0); } How do I put the running firefox-bin into "trace mode" so that my USDT probe fires? Thanks, Joel

https://bugzilla.mindrot.org/show_bug.cgi?id=2619 Bug ID: 2619 Summary: infinite loop, 100% cpu use in ssh if ^Z is pressed at password prompt Product: Portable OpenSSH Version: 7.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: