[exim-dev] [Bug 384] 0x000b: terminated by signal 11

http://www.exim.org/bugzilla/show_bug.cgi?id=384





------- Additional Comments From floris@??? 2006-10-04 23:36 -------
I take it you followed these steps as well (last post)?
http://www.directadmin.com/forum/showthread.php?s=&threadid=14533&perpage=20&pagenumber=2

If nothing works, perhaps you can use my hack to at least crank the troublesome
mails out with a delay.

#!/usr/local/bin/php
<?php
  if (!file_exists("/tmp/mail_flush.lock")) {
    echo "Passed lock test\n";

    shell_exec("touch /tmp/mail_flush.lock");

    $files = explode("\n", trim(shell_exec("ls /var/spool/exim/msglog")));

    foreach($files as $file) {
      if (!empty($file)) {
        echo "Processing $file... ";
        shell_exec("exim -M $file");

        if (file_exists("/var/spool/exim/msglog/$file")) {
          echo "NOT delivered\n";
          shell_exec("mv /var/spool/exim/msglog/$file /root/oldspoolmails");
        } else {
          echo "delivered\n";
        }
      }
    }

    shell_exec("rm -f /tmp/mail_flush.lock");
  }
?>

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.