murder configuration issue final stretch

Gary W. Smith gary at primeexalia.com
Tue Dec 9 21:22:33 EST 2008


Andrew, 
 
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.  
 
I tried it with _mechs: PLAIN but when I do that I can't connect to the backend boxes from the frontend using telnet
 
#mds01_mechs: PLAIN
mds01_password: mypassword
 
On the backend I have:
 
proxyservers: murder
 
and I set the password with both saslpasswd -c murder and passwd as well.  
 
Gary


________________________________

From: Andrew Morgan [mailto:morgan at orst.edu]
Sent: Tue 12/9/2008 5:32 PM
To: Gary W. Smith
Cc: Wesley Craig; info-cyrus at lists.andrew.cmu.edu
Subject: RE: murder configuration issue final stretch



On Tue, 9 Dec 2008, Gary W. Smith wrote:

> Wesley,
>
> 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).
>
> on the frontend:
> /etc/cyrus.conf
> lmtp          cmd="lmtpproxyd" listen="/var/lib/imap/socket/lmtp" prefork=0
>
> /var/lib/imap/socket
> srwxrwxrwx  1 root  root    0 Dec  9 19:38 lmtp
>
> mailq contains:
> (host mdsfe[/var/lib/imap/socket/lmtp] said: 451 4.4.3 Remote server unavailable (in reply to end of DATA command))
>
> 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.
>
> On the backend servers, we have this line in the /etc/cyrus.conf
>
> lmtpunix      cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1
> I've also tried
> lmtp          cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1 (with prefork 0 and 1 -- example show zero).

That should probably be:

   lmtp          cmd="lmtpd" listen="lmtp" prefork=1 maxchild=100

You want one of them to listen on the lmtp network socket, rather than
both listening on the lmtp unix socket.

        Andy


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20081209/42754c38/attachment-0001.html 


More information about the Info-cyrus mailing list