Michelle Konzack writes:
Hello,I use "mutt" and since some month I get errors like Can not allocate memory. malloc() failed OK, after an strace on "mutt" we have encountered the error in "courier-imap" but now I like to know from "courier" experts/developers HOW to debug it. It is a production intranet server with über 180 users and we have currently no fallback availlable because I relocate my enterprise to Germany. We need URGENTLY help, because in some days we need to put <mail.tdwave.net> online for our customers...
There's an explicit setting in the imapd configuration file, IMAP_ULIMITD, that sets the maximum RAM footprint that an imapd server process is allowed to grow. You probably have a large folder that causes your imapd server process to exceed it's memory quota. You can try increasing it, to see if it makes any difference.
It's always better to cap the growth of an individual imap process, so the damage from a mailbombed account is limited to that account only, rather than having an imapd process consume all available ram trying to swallow a massive hairball, and thus impact everyone.
But if you insist on debugging it, you can always run imapd from the shell: imapd [path to maildir], using the uid and gid that owns the maildir, under a debugger. However, your imapd binary should, of course, be compiled with debug symbols, and compiler optimizations turned off. Otherwise, as with any other application, you'll have a hard time hacking at it.
pgpa7Nnv2COYo.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
