murder configuration issue final stretch

[Gary W. Smith]

Andy/Wesley,
 
First off, thanks for all of the help.  I've gotten pretty far I think.  I ran into a couple problems and some notes on some list groups about dead options that were shown in examples.
 
http://garysmith.pbwiki.com/Cyrus
 
I have put all of my configs into a wiki (broken down by server/type).  The problem that I'm running into right now is that if I log into the frontend box using cyradmin (as root or cyrus) I can see mailboxes but when I go to create one on a backend server, cyradm prompts me for the password for the corresponding account on the remote machine.  I'm not sure if this is by design or an issue.
 
The other big issue is that I have lmtp configured on the frontend to forward to the backend.  The lmtp process is running on the backend as I can telnet to it (telnet ip lmtp).  On the backend I seem to be getting a SASL2 auth error.  
 
badlogin: 10.80.72.1 PLAIN SASL(-13): authentication failure: Password verification failed
 
I believe this is the final problem.  Now there is another crazy setting in the mix (but it shoudln't be an impact).  We use pam/nss mysql.  This has been working for some time and is working well on stand alone servers.  I have configured it on the frontend server as well.  I can login to the frontend just fine (which is a mysql account).
 
That's my outstanding issues at this time that (as I can't get past those).  
 
The last thing that I'm looking into is autocreatequota setting.  We used this on the standalone boxes and it worked well for us.  When we attempt to create an account on the frontend it fails as we don't have it enabled on the frontend.  When we enable it on the frontend the account is created on the frontent and attempts to delete or move (rename) fail.  Is there any hope for autocreate?
 
 

________________________________

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/69eefeb1/attachment.html