I just saw the mail from Joost Cassee who already found out that the
"foreground_mode no" setting triggers the bug. Sorry for double-posting.
This message was sent using IMP, the Internet Messaging Program.
--
To UNSUBSCRIBE, e
I noticed that the PID of a just started imapproxyd is different from the PID
written to /var/run/imapproxy.pid. Grep uses the PID in this file and doesn't
find the process.
The initscript uses the --background option of start-stop-daemon, perhaps
there is some interference with the "foreground
Hi maintainer
It is not possible to uninstall imapproxy.
[ache] 4 ROOT:~# sh /etc/init.d/imapproxy start
Starting IMAP proxy: grep: /proc/6756/cmdline: No such file or directory
Failed to start imapproxy. Check logs for details.
[ache] 4 ROOT:~# dpkg -r imapproxy
(Reading database ... 64543 fil
3 matches
Mail list logo
