On Wed, 2005-11-23 at 10:38 -0600, Saltmarsh, Evan M wrote:
> I seen to be having issues with the cyradm command. I’m using sasl to
> talk to the ldap server and for regular users logging in to their
> mailboxes, things work fine. When I try to use the cyradm command I
> get
> cyradm: cannot aut
Ok, obviously cyrus is not a user in the
LDAP database, I was focused on the “No worthy mechs found” entry
and missed the true cause completely.
Sorry.
Evan Saltmarsh
UNIX Systems Administrator
Information Technology Services
Vanderbilt University
From:
[EMAIL PROTE
I seen to be having issues with the cyradm command. I’m
using sasl to talk to the ldap server and for regular users logging in to their
mailboxes, things work fine. When I try to use the cyradm command I get
cyradm: cannot authenticate to server with as cyrus
the following errors
I got a bunch of errors like this last night on our murder master
before the mupdate process died.
the errors then repeated again this morning.
Nov 22 20:14:09 notdog mupdate[16698]: Bad file descriptor, closing
connection
Nov 22 20:14:09 notdog mupdate[16698]: Bad file descriptor, closin
Casper schrieb:
Timo Eissler wrote:
Hello List,
we want to transfer our shared folders from our old mail server with
cyrus imap to our new
server with cyrus imap.
I successfully transfered the user folders with imapsync, but i can´t
transfer the shared folders.
I thought i can transfer th
> Sorry, I didn't read closely enough. I don't believe there is a way to
> disable this without making changes to the source. Some SASL mechs
> require the IPs, so we do the lookup before authentication.
A local dns cache may mitigate the cost of the lookup, if that's what you're
hoping to avoid
Hello List,
we want to transfer our shared folders from our old mail server with
cyrus imap to our new
server with cyrus imap.
I successfully transfered the user folders with imapsync, but i can´t
transfer the shared folders.
I thought i can transfer the files of the shared folders an then ru
Scott Balmos wrote:
Ken Murchison wrote:
Scott Balmos wrote:
Hi all,
I know in a virtual domain setup, if a user connects with an
unqualified username, the server does a reverse DNS lookup on the
*server's* incoming connection IP, to determine a default virtual
domain name.
But how do I