This is solved by creating self-signed CA (certificate authority) and
certificate+private key bundle. The essential detail is that when
generating the certificate you need to specify Common Name (CN) as a
fully qualified domain name (hostA.localdoman or hostA.imapsite.net,
etc.). This must be done
I've said before that I fixed the issue with authentication from
Master-Replica in a basic two-host setup in a mysterious way. Funny
thing is that I've managed to successfully replicate from M to R and
vice versa, swapping the roles of the hosts as many times as I wanted.
Everything worked as
:
dXNlcm5hbWU9InRlc3QiLHJlYWxtPSJkcmFjaGVudG9yIixub25jZT0iRUFtZE5odGhjUXF1S3RUM2E3RTVkOE9XbVJNeStoSmJWMW1ZSzM1M0pWTT0iLGNub25jZT0iNW1rR21SWkdtaGo0akdNVXdUbS8zcXdMK0hpZW5kWmZPcGVrcEhkQVpzST0iLG5jPTAwMDAwMDAxLHFvcD1hdXRoLWNvbmYsY2lwaGVyPXJjNCxtYXhidWY9MTAyNCxkaWdlc3QtdXJpPSJzaWV2ZS9sb2NhbGhvc3QiLHJlc3BvbnNlPThkOTFkOGZmY2ExMzdmODZjNzAyMDJiYjc1MGViMTcx
S: NO Authentication Error
Hi All,
I am running Cyrus Imap 2.2.3 on RH ES 3.0 using MySQL
3.23.58 as my database so I can use my mail server with virtual domains (maildir).
I believe that I have configured everything correctly except
I am getting the error below when I check pop3 email:
do_auth
: auth
,
Emma
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ken
Murchison
Sent: Monday, February 02, 2004 12:30 AM
To: Emma Grant
Cc: [EMAIL PROTECTED]
Subject: Re: PAM Authentication error...
Emma Grant wrote:
Hi All,
I am running Cyrus Imap 2.2.3
Murchison
Sent: Monday, February 02, 2004 12:30 AM
To: Emma Grant
Cc: [EMAIL PROTECTED]
Subject: Re: PAM Authentication error...
Emma Grant wrote:
Hi All,
I am running Cyrus Imap 2.2.3 on RH ES 3.0 using MySQL 3.23.58 as my
database so I can use my mail server with virtual domains (maildir).
I
Sent: Monday, February 02, 2004 4:47 AM
To: Emma Grant
Cc: [EMAIL PROTECTED]
Subject: Re: PAM Authentication error...
Emma Grant wrote:
Thanks for your reply.
I ended up fixing the error by adding account required
/lib/security/pam_permit.so at the top of my pop file in pam.d/pop
I first
: Re: PAM Authentication error...
Emma Grant wrote:
Thanks for your reply.
I ended up fixing the error by adding account required
/lib/security/pam_permit.so at the top of my pop file in pam.d/pop
I first tried pam_warn.so, and that told me that my account had
expired,
and since the really
I am installing a Cyrus box with the following configuration:
Machine: Dual Xeon 2GHz, 1Gb RAM
System: Debian GNU/Linux 3.0, Cyrus 2.1 (Backported) and SASL2 (Backported)
Authentication: LDAP
I have created a cyrus user under LDAP directory and the PAM modules has
been set up to lib_ldap.so.
Christiano Anderson wrote:
I am installing a Cyrus box with the following configuration:
Machine: Dual Xeon 2GHz, 1Gb RAM
System: Debian GNU/Linux 3.0, Cyrus 2.1 (Backported) and SASL2 (Backported)
Authentication: LDAP
I have created a cyrus user under LDAP directory and the PAM modules has
been
Ken Murchison wrote:
Christiano Anderson wrote:
I am installing a Cyrus box with the following configuration:
Machine: Dual Xeon 2GHz, 1Gb RAM
System: Debian GNU/Linux 3.0, Cyrus 2.1 (Backported) and SASL2
(Backported)
Authentication: LDAP
I have created a cyrus user under LDAP directory and
--- Mensagem Original
Assunto: Re: [Fwd: Re: Authentication error]
De: Marlon Dutra [EMAIL PROTECTED]
Data:Sex, Janeiro 9, 2004 12:56 pm
Para:[EMAIL PROTECTED
Hey guys,
I've finally found out the problem, and believe, it's really a bug, either
of Cyrus or SASL 2.
The problem happens only when I have my NSS using LDAP, through these
lines in nsswitch.conf:
--
passwd: compat ldap
group: compat ldap
shadow: compat ldap
---
If
On Fri, 9 Jan 2004, Christiano Anderson wrote:
Hey guys,
I've finally found out the problem, and believe, it's really a bug, either
of Cyrus or SASL 2.
The problem happens only when I have my NSS using LDAP, through these
lines in nsswitch.conf:
--
passwd: compat ldap
group:
Christiano Anderson wrote:
Hey guys,
I've finally found out the problem, and believe, it's really a bug,
either of Cyrus or SASL 2.
[...]
But it's a bug, and it must be fixed ASAP.
The bug is in LDAP, and the fix is OpenLDAP 2.1 (as a Debian 3.0 user -
like me - you have OpenLDAP 2.0). The
Hi all,
I'm having a problem using sieve on my linux box (SuSE 8.0). Cyrus and
timesieved are working fine. I can even auth to imap and cyradm with
plain method over saslauthd and pam. But I cannot login via sieveshell.
I'm always getting the same error message!
I've been googling around but I
I have a cyrus imapd 2.1.13 mail server w/ cyrus sasl 2.1.13 using the ldapdb
auxprop backend.. The auxprop backend is configured and working correctly.. the
issue is this.. when I log into the mail server using LOGIN with the username
[EMAIL PROTECTED] it works fine.. BUT if I use DIGEST-MD5 or
Kevin Williams wrote:
My imapd.conf file looks as follows:
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyrus root
sasl_pwcheck_method: saslauthd
I can successfully authenticate using the imtest command. When I
tried to use cyradm, I originally got a can't
Robert thanks for the help,
After changing the imapd.conf file as you directed (and rebooting to make sure the
changes took affect), I still got the error when running cyradm --user cyrus
localhost. I noticed in my auth.log file that the following messages occurred when
trying to log in:
Feb
On Thu, 27 Feb 2003, Robert Urban wrote:
I had this problem too. The answer is actually in the docs (install-auth),
but it can take days before you find it :( The whole authentication
business is pretty badly documented, IMHO.
If you have suggestions, we do take reasonably-written patches.
All,
I'm hoping someone can help me with this issue. I have a new install with Redhat 8.0.
I used the sasl RPM 2.1.7-2. I downloaded and installed cyrus imap version 2.1.12.
My imapd.conf file looks as follows:
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyrus root
I suspect you're trying to use one of the non plaintext mechanisms.
What mechanisms are offered when you connect using imtest?
The probably solution is to add a line to imapd.conf like:
sasl_mech_list: PLAIN LOGIN
-Rob
On Tue, 3 Dec 2002, Mark J. Lilback wrote:
Hi. I'm running in to a
On Tue, 3 Dec 2002, Mark J. Lilback wrote:
At 2:20 PM -0500 12/3/2002, Rob Siemborski wrote:
I suspect you're trying to use one of the non plaintext mechanisms.
What mechanisms are offered when you connect using imtest?
Digest-MD5. The transcript is below. If I add the line like you
At 2:20 PM -0500 12/3/2002, Rob Siemborski wrote:
I suspect you're trying to use one of the non plaintext mechanisms.
What mechanisms are offered when you connect using imtest?
Digest-MD5. The transcript is below. If I add the line like you
suggested, I still get the generic failure and the
: Authentication error at /usr/bin/sieveshell
line 149, STDIN line 1.
I can successfully telnet to my server :
$ telnet outerspace sieve
Trying 127.0.0.1...
Connected to outerspace.
Escape character is '^]'.
IMPLEMENTATION Cyrus timsieved v1.0.0
SASL PLAIN LOGIN DIGEST-MD5 CRAM-MD5
SIEVE
I use Cyrus 2.0.16 with Digest-MD5 SASL authentication on my Linux server
and it works well. But when I try to use sieveshell :
$ sieveshell -u nicko -a nicko outerspace
connecting to outerspace
Please enter your password: x
unable to connect to server: Authentication error at /usr/bin
Hello Mailinglist-User,
I login as user cyrus and input cyradm localhost to get the
opportunity to administrate the server. Then I made a auth cyrus, but
the program aborted currently with the following error message:
perl: digestmd5.c:1423: privacy_encode: Zusicherung »text-maxbuf 0«
nicht
Hi,
Okay, I've tried everything under the sun, but for some reason I can never get the
authentication to work
properly. Does anyone see into this error message? Any help would keep me from
jumping off the nearest bridge!
Result of :
tail /var/log/messages
tail /var/adm/auth.log
tail
28 matches
Mail list logo
