Am Monday 18 September 2006 19:00 schrieb Sam Smith:
> The saslauthd output when run in debug mode while I login - doesn't show
> any problems:
> saslauthd[2194] :do_auth : auth success: [user=sam]
> [service=imap] [realm=] [mech=pam]
> saslauthd[2194] :do_request : response: OK
Loo
Andreas Winkelmann wrote:
Am Thursday 14 September 2006 18:23 schrieb Sam Smith:
We've been using cyrus faithfully with pam->NIS for years, but I have to
change to pam->LDAP.
I'm using saslauthd -a pam, with a solaris 9 box that authenticates just
fine using pam->ldap to a fedora directory s
Am Thursday 14 September 2006 18:23 schrieb Sam Smith:
> We've been using cyrus faithfully with pam->NIS for years, but I have to
> change to pam->LDAP.
> I'm using saslauthd -a pam, with a solaris 9 box that authenticates just
> fine using pam->ldap to a fedora directory server.
>
> I'm using cyr
We've been using cyrus faithfully with pam->NIS for years, but I have to
change to pam->LDAP.
I'm using saslauthd -a pam, with a solaris 9 box that authenticates just
fine using pam->ldap to a fedora directory server.
I'm using cyrus 2.3.7, and sasl 2.1.22. I did not compile in ldap
support fo
Good day, im setting up setting web-cyradm and it
working fine. Now im tried again but using different
version of cyrus-imap, cyrus-sasl2 and
cyrus-sasl2-saslauthd. I strangely got this error when
im trying to authenticate using outlook express where
the config is the same as the config of my previ
Good day, im setting up setting web-cyradm and it
working fine. Now im tried again but using different version of cyrus-imap,
cyrus-sasl2 and cyrus-sasl2-saslauthd.
I strangely got this error when im trying to authenticate using
outlook express where the config is the same as the config of
Hi,
In my Murder, about once a week, the lmtp proxy on both frontend stop
taking delivery of mail. We restart the mupdate master, and everything
goes back. I have the following in Postfix log :
Feb 10 00:00:23 frontend1 postfix/lmtp[9779]: 03C9D33E29: to=<[EMAIL PROTECTED]>,
relay=none, delay=
> On 07 Jul 2003 18:17:29 -0700,
> Scott Bronson <[EMAIL PROTECTED]> (sb) writes:
sb> As long as they don't indicate something amiss, I can live with them.
sb> Thanks.
Incidentally, they're gone in 2.1.14.
--
Amos
As long as they don't indicate something amiss, I can live with them.
Thanks.
- Scott
On Mon, 2003-07-07 at 12:54, Ken Murchison wrote:
> These are harmless (I could give you a technical reason if you care).
> Reduce you logging level from DEBUG down to something like INFO or
> NOTICE and
These are harmless (I could give you a technical reason if you care).
Reduce you logging level from DEBUG down to something like INFO or
NOTICE and these will disappear.
Scott Bronson wrote:
Can anyone tell me why my logs are filling with messages
like these?
Jul 5 17:41:08 eden cyrus/lmtpd[28
Can anyone tell me why my logs are filling with messages
like these?
Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down
filedescriptor 0: Bad file descriptor
Jul 5 17:41:08 eden cyrus/lmtpd[28993]: Could not shut down
filedescriptor 1: Bad file descriptor
Jul 5 17:41:08 eden cyrus/lmtp
11 matches
Mail list logo
