Displaying 2 results from an estimated 2 matches for "imapdir2".
Did you mean:
imapdir
2012 Mar 15
1
director lmtp -> smtp problem
...tor nodes run sendmail, which deliver mail "locally" using LMTP
to the director, which then feeds to SMTP on the real servers (also
sendmail.) Why sendmail? Because procmail is used for mail filtering
and as the delivery agent.
Here's the problem, on the director:
Mar 14 20:40:08 imapdir2 dovecot: lmtp(10692): Connect from local
Mar 14 20:40:38 imapdir2 dovecot: lmtp(10692): Panic: file
lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed:
(proxy->data_input
->eof)
Mar 14 20:40:38 imapdir2 dovecot: lmtp(10692): Error: Raw backtrace:
/usr/lib/dovecot/libdoveco...
2011 Oct 04
1
trouble setting up director, "invalid argument" for connect() call
...ps disabled)
Oct 3 16:11:34 imapdir1 dovecot: director: Error:
connect(132.198.100.150:9090) failed: Invalid argument
Oct 3 16:11:41 imapdir1 last message repeated 3 times
Both nodes report this error. The director on each node is listening on
port 9090 just fine:
> [root at imapdir1 ~]# nc imapdir2 9090
> VERSION director 1 0
> ME 127.0.0.1 9090
> [root at imapdir2 ~]# nc imapdir1 9090
> VERSION director 1 0
> ME 127.0.0.1 9090
"doveadm director ring status" always reports failure of the peer:
> [root at imapdir1...