<HTML dir=ltr><HEAD><TITLE>RE: murder configuration issue final stretch</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText75582 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Andrew, </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Made the change on the backend server. Now is complains that remote server is unavailable and the corresponding log on the backend is saying "badlogin: 10.80.72.205 PLAIN SASL(-13): authentication failure: Password verification failed". At least they are talking now. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I tried it with _mechs: PLAIN but when I do that I can't connect to the backend boxes from the frontend using telnet</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>#mds01_mechs: PLAIN<BR>mds01_password: mypassword</FONT></DIV><FONT face=Arial size=2></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>On the backend I have:</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>proxyservers: murder</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>and I set the password with both saslpasswd -c murder and passwd as well. </DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Gary<BR></DIV></FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Andrew Morgan [mailto:morgan@orst.edu]<BR><B>Sent:</B> Tue 12/9/2008 5:32 PM<BR><B>To:</B> Gary W. Smith<BR><B>Cc:</B> Wesley Craig; info-cyrus@lists.andrew.cmu.edu<BR><B>Subject:</B> RE: murder configuration issue final stretch<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Tue, 9 Dec 2008, Gary W. Smith wrote:<BR><BR>> Wesley,<BR>><BR>> I'm on the final stretch. I have mailboxes seen at all angles. If I telnet to the frontend I can see the backend mailboxes on both servers. Yay. The problem now is delivery. I tried setting up lmtpproxyd but I get some errors and the email gets queued up on the frontend server. This is fine for now while we have the mail going to the proper places on the backend but going forward we will need to be able to deliver via the frontend (or murder server).<BR>><BR>> on the frontend:<BR>> /etc/cyrus.conf<BR>> lmtp cmd="lmtpproxyd" listen="/var/lib/imap/socket/lmtp" prefork=0<BR>><BR>> /var/lib/imap/socket<BR>> srwxrwxrwx 1 root root 0 Dec 9 19:38 lmtp<BR>><BR>> mailq contains:<BR>> (host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server unavailable (in reply to end of DATA command))<BR>><BR>> Please correct me if I'm wrong but my understanding is that lmtp will be used to deliver the message from the frontend to the backend (thus bypassing postfix in this case). When I do a netstat -atunep on the backend server, I don't see the lmtp port open. I would assume that this could be part of the problem.<BR>><BR>> On the backend servers, we have this line in the /etc/cyrus.conf<BR>><BR>> lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1<BR>> I've also tried<BR>> lmtp cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1 (with prefork 0 and 1 -- example show zero).<BR><BR>That should probably be:<BR><BR> lmtp cmd="lmtpd" listen="lmtp" prefork=1 maxchild=100<BR><BR>You want one of them to listen on the lmtp network socket, rather than<BR>both listening on the lmtp unix socket.<BR><BR> Andy<BR></FONT></P></DIV></BODY></HTML>