On 22.08.2013 17:05, Paul J Stevens wrote:
On 08/22/2013 04:39 PM, Chedomir Nikolikj wrote:
Hello,
This morning we updated dbmail to the latest version 3.1.3 from git. We
noticed that dbmail-imapd daemon is failing. We managed to get 128 debug
log of one of the failings.
I don't see any 'failures' in the logs. Apart from the logs you sent,
how does this manifest itself on the client-side?
Well the service is not running, so imap connection's cannot be
established, if that's the question
Aug 22 14:50:28 dbmail-pdc dbmail-imapd[25138]: [0x7f563e411840]
Debug:[imap] imap_handle_exit(+413): [0x7f5603875c40] state [4]
command_status [0] [logout] returned with status [2]
Aug 22 14:50:28 dbmail-pdc dbmail-imapd[25138]: [0x7f563e411840]
Debug:[clientbase] client_error_cb(+122): [0x7f55dd006000] 225 Broken
pipe[32], 0x7f55dd006000
That is kind of surprising. I've never seen SIGPIPE errors before on a
socket, especially since dbmail is setup to ignore SIGPIPE.
How are you running dbmail? Are you perhaps running it from (x)inetd, or
behind a proxy?
We are running dbmail as a daemon, starting it as regular service from
/etc/init.d/dbmail-imapd
Also we use a custom authldap.c so we can authenticate with custom
attribute for ldap password authentication. Maybe that has something to
do with this issue ?
BR,
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
