On Tue, 09 Jan 2007 08:52:21 -0500, "Ken Murchison" <murch@xxxxxxxxxxxxxx> said: > > http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff > > Why not just run 'sync_server -p 2' ? I believe that I added the 'p' > option to all services for just this reason. It didn't work in my testing for some reason. I'm happy to try it out again, but I was pretty sure it wasn't enough. It may just be that it wasn't happy to use the saslauthd, which is OK because I'm putting sync passwords in /etc/sasldb2 now anyway. The other thing is that sync may have been broken due to other issues like binding to the wrong IP address on the machine thanks to hostname lookups. There were a few different weird things I had to solve before I got sync working, and this patch appeared to solve one of them. Besides which, I didn't understand SASL much when I wrote that, and it works. Actually, I still don't understand SASL much. It appears to take an already difficult problem and abstract it away so much that its becomes even more complex (and yet you still can't pass an error message back from the authd explaining why the user isn't allowed to log in right now) Bron. -- Bron Gondwana brong@xxxxxxxxxxx ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
