On 06/08/11 11:44 +0100, John wrote:
>On 05/08/11 22:32, Dan White wrote:
>>Does your cyrus user have permissions to access the saslauthd mux?
>>
>>Try running your testsaslauthd command as your cyrus user... I'm assuming
>>that during testing you were using root, or another account.
>>
>Aha! Thank
On 05/08/11 22:32, Dan White wrote:
> Does your cyrus user have permissions to access the saslauthd mux?
>
> Try running your testsaslauthd command as your cyrus user... I'm assuming
> that during testing you were using root, or another account.
>
Aha! Thank you so much. I had checked the permissio
On 05/08/11 22:10 +0100, John wrote:
>I have a server, currently running 2.4.7 and all is well (and has been
>for a very long time). I am trying to build a new server with 2.4.10 but
>I can't get anything to authenticate on it.
>
>configdirectory: /srv/mail/cyrus
>partition-default: /srv/mail/cyrus
Hello, I have a problem with a new installation. I've been trying to
sort this for several days now without any luck so post here in the hope
for a solution.
I have a server, currently running 2.4.7 and all is well (and has been
for a very long time). I am trying to build a new server with 2.4
We had a nice trouble free cyrus running until it was updated
with updates from Redhat today.
I've tested with testsaslauthd (no service name given) and it works OK,
so I'd think things are fine on the pam, AD and ldap end.
In the cyrus server's maillog I'm seeing messages like this
from attempts
Good day, List,
I'm trying to set up murder here. I have let's say three servers. One for
backend, one for frontend and one for mupdate server. Problem is, that I'm
not able to set up mupdate part. Mupdate server is working as master(mupdate
-m on the master server). Authentication is done via
sa
Andrew Morgan wrote:
On Thu, 18 May 2006, Brenden Conte wrote:
I've been wrestling with a new cyrus murder setup. At this point,
edits made to a backend server are properly propigated through the
master and frontends.
Now, i'm trying to test administration through the frontend servers.
F
Quoting Michael Leupold <[EMAIL PROTECTED]>:
> Am Donnerstag, 18. Mai 2006 21:26 schrieb Andrew Morgan:
> > On Thu, 18 May 2006, Brenden Conte wrote:
> > > True, and i perhaps used a bad example - this occurs anytime
> i try to
> > > connect to the backend, not just on CREATE. for example, i
> ca
Am Donnerstag, 18. Mai 2006 21:26 schrieb Andrew Morgan:
> On Thu, 18 May 2006, Brenden Conte wrote:
> > True, and i perhaps used a bad example - this occurs anytime i try to
> > connect to the backend, not just on CREATE. for example, i can
> > successfully, log in with a valid account, but if i
On Thu, 18 May 2006, Brenden Conte wrote:
True, and i perhaps used a bad example - this occurs anytime i try to connect
to the backend, not just on CREATE. for example, i can successfully, log in
with a valid account, but if i try to `SELECT INBOX`, I get the same error.
I don't know enough
True, and i perhaps used a bad example - this occurs anytime i try to
connect to the backend, not just on CREATE. for example, i can
successfully, log in with a valid account, but if i try to `SELECT
INBOX`, I get the same error.
Thanks.
-Brenden
Andrew Morgan wrote:
On Thu, 18 May 2006,
Am Donnerstag, 18. Mai 2006 17:57 schrieb Andrew Morgan:
> On Thu, 18 May 2006, Brenden Conte wrote:
> > I've been wrestling with a new cyrus murder setup. At this point, edits
> > made to a backend server are properly propigated through the master and
> > frontends.
> > Now, i'm trying to test ad
On Thu, 18 May 2006, Brenden Conte wrote:
I've been wrestling with a new cyrus murder setup. At this point, edits made
to a backend server are properly propigated through the master and frontends.
Now, i'm trying to test administration through the frontend servers. For
example, when i conne
I've been wrestling with a new cyrus murder setup. At this point, edits
made to a backend server are properly propigated through the master and
frontends.
Now, i'm trying to test administration through the frontend servers.
For example, when i connect to a frontend server and issue a `CREATE
> Sent: Thursday, September 29, 2005 12:25 PM
> To: ×××× ×§××צ'×× ×¡×§×
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Ant: RE: RE: RE: RE: Cyrus Imap
> Authentication Problems
>
> Hi,
>
> i've installed the whole thing new from scratch, but
> i sti
Am Thursday 29 September 2005 11:24 schrieb evildad:
> i've installed the whole thing new from scratch, but i
> still get these errors:
>
> evildad saslauthd[14425]: DEBUG: auth_pam:
> pam_acct_mgmt failed: User account has expired
> evildad saslauthd[14425]: do_auth : auth
> failure: [use
Tuesday, September 27, 2005 1:11 PM
> To: ×××× ×§××צ'×× ×¡×§×
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Ant: RE: RE: RE: Cyrus Imap Authentication
> Problems
>
> HI,
> i've created this folder and the smtpd.conf but i
> still get these errors.
> For tes
Am Tuesday 27 September 2005 12:11 schrieb evildad:
> Sep 27 12:03:54 evildad saslauthd[20837]: DEBUG:
> auth_pam: pam_acct_mgmt failed: User account has
> expired
Well, time to check if the Account is expired.
--
Andreas
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ
E: RE: RE: Cyrus Imap Authentication Problems
HI,
i've created this folder and the smtpd.conf but i still get these errors.
For testing purposes i created a new User and tested it.
This is what syslog tells me
Sep 27 12:03:54 evildad imap[21012]: sql plugin Parse the username evildad Sep
2
> -Original Message-
> From: evildad [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 27, 2005 12:17 PM
> To: ×××× ×§××צ'×× ×¡×§×
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Ant: RE: RE: Cyrus Imap Authentication
> Problems
>
> HI,
> yes
-Original Message-
From: evildad [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 27, 2005 12:17 PM
To: לאון קולצ'ינסקי
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Ant: RE: RE: Cyrus Imap Authentication Problems
HI,
yes it is the real Password for the User mail.
--- [EMAIL PROT
nal Message-
> From: evildad [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 26, 2005 10:31 PM
> To: ×××× ×§××צ'×× ×¡×§×
> Cc: info-cyrus@lists.andrew.cmu.edu
> Subject: Ant: RE: Cyrus Imap Authentication Problems
>
> Hi,
> i had created the file /etc/pam.d
-
>
> Regards,
> Leon Kolchinsky
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of evildad
> Sent: Sunday, September 25, 2005 10:31 PM
> To: info-cyrus@lists.andrew.cmu.edu
> Subject: Cyrus Imap Authentication P
ix_acct.so
-
Regards,
Leon Kolchinsky
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of evildad
Sent: Sunday, September 25, 2005 10:31 PM
To: info-cyrus@lists.andrew.cmu.edu
Subject: Cyrus Imap Authentication Problems
HI
hi,
try installing the sasl authentification packages ... i had the same
thing ...
cyrus-sasl-md5
cyrus-sasl-plain
cyrus-sasl-ntlm
cyrus-sasl-gssapi
"plain" is the minimum install ...
cheers
chalres
On Sun, 2005-09-25 at 21:31 +0200, evildad wrote:
> HI there,
> i'd like to set-up an worki
HI there,
i'd like to set-up an working IMAP Server on my Gentoo
System. I used the Postfix-Cyrus-Web-cyradm-HOWTO from
http://www.delouw.ch/linux/Postfix-Cyrus-Web-cyradm-HOWTO/html/index.html
Because I use Gentoo, I compiled all the packages
with the emerge command. Here are the versions for
On 8/24/05, Igor Brezac <[EMAIL PROTECTED]> wrote:
>
> On Wed, 24 Aug 2005, Fred Blaise wrote:
>
> > On 8/24/05, Etienne Goyer <[EMAIL PROTECTED]> wrote:
> >> Fred Blaise wrote:
> >>> I am trying to fix the cyrus SASL authentication against openLDAP, I
> >>> guess.
> >>>
> >>> When I run that, h
On Wed, 24 Aug 2005, Fred Blaise wrote:
On 8/24/05, Igor Brezac <[EMAIL PROTECTED]> wrote:
On Wed, 24 Aug 2005, Fred Blaise wrote:
On 8/24/05, Etienne Goyer <[EMAIL PROTECTED]> wrote:
Fred Blaise wrote:
I am trying to fix the cyrus SASL authentication against openLDAP, I guess.
When I ru
On 8/24/05, Igor Brezac <[EMAIL PROTECTED]> wrote:
>
> On Wed, 24 Aug 2005, Fred Blaise wrote:
>
> > On 8/24/05, Etienne Goyer <[EMAIL PROTECTED]> wrote:
> >> Fred Blaise wrote:
> >>> I am trying to fix the cyrus SASL authentication against openLDAP, I
> >>> guess.
> >>>
> >>> When I run that, h
On Wed, 24 Aug 2005, Fred Blaise wrote:
On 8/24/05, Etienne Goyer <[EMAIL PROTECTED]> wrote:
Fred Blaise wrote:
I am trying to fix the cyrus SASL authentication against openLDAP, I guess.
When I run that, here is the error:
OX1:~# ldapsearch -D "c
On 8/24/05, Etienne Goyer <[EMAIL PROTECTED]> wrote:
> Fred Blaise wrote:
> > I am trying to fix the cyrus SASL authentication against openLDAP, I guess.
> >
> > When I run that, here is the error:
> >
> > OX1:~# ldapsearch -D "cn=manager,dc=ilr,dc=lu" -
Fred Blaise wrote:
I am running TLS.. an ldapsearch -ZZ works fine with the -x simple bind.
However, cyrus -> saslauthd (PAM) -> pam_ldap requires an SASL
authentication on the ldap server, am I right?
Not supposed to ... it use simple bind AFAIK.
Have you checked if testsaslauthd give positiv
Fred Blaise wrote:
I am trying to fix the cyrus SASL authentication against openLDAP, I guess.
When I run that, here is the error:
OX1:~# ldapsearch -D "cn=manager,dc=ilr,dc=lu" -h ldapsmb-pdc.ilr.lu
-b "dc=ilr,dc=lu" "(uid=sp)"
SASL/DIGEST-MD5 authen
Hello all
I am seeking help on sasl authentication against openldap.
Debian stable 3.1 on all servers.
On one server, I have slapd 2.2.23. It is used to authenticate samba
(works, same server), and a groupware on another server (works, 2nd server).
On the second server, I have a cyrus imap serve
Greetings!
This may not be the correct forum for this issue, but I thought I'd
start here and find a more appropriate newsgroup if one exists. I also
apologize for the length of this message, but there is a lot of log info
down here. I would be happy to send conf. file info as well if anyone
need
> You need to word your imtest request differently (add another option)
> according to the error you got its expecting roots password not testuser
>
>
> imtest -u testuser -a testuser -m login localhost
>
> that way you are useing testusers mailbox an authenticateing as testuser
> as
You need to word your imtest request differently (add another option)
according to the error you got its expecting roots password not testuser
> [EMAIL PROTECTED] root]# imtest -u testuser -m login localhost
> Please enter your password:
> C: L01 LOGIN root {11}
> S: + go ahead
this is because y
>> With your config, forget saslpasswd, you don't have to use it. You can
>> add
>> unix users and then create the mailboxes for them. Call cyradm like
>> this:
>>
>> cyradm --user cyrus --auth login localhost
>>
>> then use 'cm user.name' to create the mailboxes.
>
> Simon,
>
> OK, makes sense, no
>
> Is saslauthd running, and if so, with which option(s)? It might be
> easier to forget about imtest and make sure that saslauthd is happy
> first by using the testsaslauthd program? Once this is working, then
> you can move on to imtest.
Keep in mind that authentication is working for all ex
>IIRC you can only do this
> with the encrypted passwd. Please try 'passwd testuser'.
DOH! Thanks again, works now. The man page for adduser (or useradd) admits
to the -p passwd argument, but evidently it doesn't work so well...
Doug
Confidential: This electronic message and all contents con
Doug Koobs wrote:
BTW, here is the relevant entry in imapd.log from using imtest:
mail imapd[24864]: badlogin: localhost.localdomain[127.0.0.1] plaintext
testuser SASL(-13): authentication failure: checkpass failed
Is saslauthd running, and if so, with which option(s)? It might be
easier to for
> With your config, forget saslpasswd, you don't have to use it. You can add
> unix users and then create the mailboxes for them. Call cyradm like this:
>
> cyradm --user cyrus --auth login localhost
>
> then use 'cm user.name' to create the mailboxes.
Simon,
OK, makes sense, no more saslpasswd
BTW, here is the relevant entry in imapd.log from using imtest:
mail imapd[24864]: badlogin: localhost.localdomain[127.0.0.1] plaintext
testuser SASL(-13): authentication failure: checkpass failed
Doug
Confidential: This electronic message and all contents contain information from
Financial
> I've set up a Cyrus IMAP server (on RH9), and it's working great. However,
> I
> didn't document the process of adding users/mailboxes, and know when I try
> to add someone, they can't authenticate. I don't have a good understanding
> of how authentication works in Cyrus, but here are (I think) r
I've set up a Cyrus IMAP server (on RH9), and it's working great. However, I
didn't document the process of adding users/mailboxes, and know when I try
to add someone, they can't authenticate. I don't have a good understanding
of how authentication works in Cyrus, but here are (I think) relevant
en
On Tue, Jun 24, 2003 at 04:11:19PM +0400, Pavel A Crasotin wrote:
> The 1st problem:
> cyradm --user cyrus localhost
> says
> cyradm: cannot authenticate to server with as cyrus
> Corresponding message in syslog:
> badlogin: localhost[127.0.0.1] DIGEST-MD5 [SASL(-13): user not found: no se
Hello all
I've installed cyrus-imapd-2.1.13, cyrus-sasl-2.1.13 on FreeBSD 4.8
box.
In imapd.conf I have:
configdirectory:/var/imap
defaultpartition: default
partition-default: /var/spool/imap
unixhierarchysep: yes
allowplaintext: yes
admins: cyrus [
Hmmm, looks like that was it, thanks much for the second pair of eyes!
Just can't seem to see those things at 4am!?!? Ohh well, some more wasted disk space for the archives... :)
Thanks again,
LukeJ.
Chris Hilts wrote:
sasl_mysql_statement: select pass from email where eaddr ='%u' and mid=1
and
> sasl_mysql_statement: select pass from email where eaddr ='%u' and mid=1
> and active=1"
Well, assuming this isn't a transcription typo, you've got an unbalanced
quote at the end of your statement.
--
Chris Hilts
[EMAIL PROTECTED]
Howdy,
Problem:
So, I'm setting up a new Cyrus server, pretty standard config (see below)
It seems that in Simon's mysql auxprop code, the mysql_query() is failing. I'm always getting back a -1 (error) result
I'm about to write a test program, to try the mysql libs away from sasl, and see if
Jon Drukman wrote:
>
> At 07:42 AM 9/27/2002, Ken Murchison wrote:
> >You can't turn plaintext off and specify PLAIN as the only SASL
> >mechanism, because cyram doesn't support SSL/TLS (which is this only way
> >that PLAIN or IMAP LOGIN would be allowed with your config). Either
> >allow plai
At 07:42 AM 9/27/2002, Ken Murchison wrote:
>You can't turn plaintext off and specify PLAIN as the only SASL
>mechanism, because cyram doesn't support SSL/TLS (which is this only way
>that PLAIN or IMAP LOGIN would be allowed with your config). Either
>allow plaintext, or add some other mechs (ie
Jon Drukman wrote:
>
> I'm trying to set up a system where there are no normal user accounts, but
> people can get mail. I'm using sasl-2.1.7 and cyrus-imapd-2.1.9 on FreeBSD4.
>
> I set up some accounts using saslpasswd2. I can see them with sasldblistusers2
>
> # sasldblistusers2
> [EMAIL
I'm trying to set up a system where there are no normal user accounts, but
people can get mail. I'm using sasl-2.1.7 and cyrus-imapd-2.1.9 on FreeBSD4.
I set up some accounts using saslpasswd2. I can see them with sasldblistusers2
# sasldblistusers2
[EMAIL PROTECTED]: userPassword
[EMAIL PROT
I have a similiar config and it is working, here is what I have:
For Cyurs-SASL 2.1.2
# ./configure --disable-anon --disable-cram --disable-digest --with-gssapi=no --with-des=no --disable-otp --with-opie=no --disable-srp --disable-krb4 --enable-plain --enable-login --with-saslauthd
For Cyrus-IMA
when I run cyradm authentication failures and when I look in the log, I find:
May 1 15:15:22 mail imapd[29838]: unknown password verifier saslauthd
May 1 15:15:22 mail imapd[29838]: badlogin: localhost.localdomain[127.0.0.1]
plaintext root SASL(-4): no mechanism available: checkpass failed
May
I'm having problems about my users except for 1 authenticating. For some reason the
user
'damm' can authenticate, but none of the others can. Now is there a way i can make
Imapd
call saslauthd and make saslauthd get the passwords via login or getpwent, or even
shadow?
I have saslauthd runnin
Hi,
I am having a couple of problems with SASL authentication. First of all,
the authentication mechanisms CRAM-MD5 DIGECT-MD5 done't appear as being
supported, even though I have used the the sample programs that come
with SASL those appear to work.
Also, I have set the pwcheck_method to pwche
Hello all,
I am having trouble configuring Cyrus in any way that will allow me to
authenticate. I've tried doing this several different ways according to the
docs, the HOWTO, the O'Reilly IMAP book, and various list posts. I keep
getting incorrectly rejected when I try to login using imtest
Hy!
Are you sure the SASL libs are in place? I think they're placed in
/usr/local/lib, but that might not be in /etc/ld.so.conf (in Linux systems). If
this is done, then you need to run ldconfig.
If that doesn't help maybe you could try strace-ing the imapd process.
And a maybe faster test (
Can the cyrus user read the /etc/shadow file?
Andrew Kirilenko wrote:
> Hello!
>
> I've problems with authentication :(
> Can somebody help me with this problem? It's really urgent and important!
>
> Here's log:
> cyrus@isserver:/home/iced$ imtest -p imap -m login localhost
> C: C01 CAPABILITY
Hello!
I've problems with authentication :(
Can somebody help me with this problem? It's really urgent and important!
Here's log:
cyrus@isserver:/home/iced$ imtest -p imap -m login localhost
C: C01 CAPABILITY
S: * OK isserver Cyrus IMAP4 v1.6.24 server ready
S: * CAPABILITY IMAP4 IMAP4rev1 ACL Q
When I try an initial connect to imapd (via cyradm) to create a usermailbox,
the server doesn't let me in. The according Message in syslog is
"Berkley-DB: cannot open /etc/sasldb: Invalid argument"
Does anyone have an idea of what's going on there?
I have created the sasldb and i have inserted t
, authentication problems
Hi--
I'm having trouble figuring out how to authenticate to the
cyrus server I'm trying to install.
Environment:
linux debian 2.2 potato, 2.2.18 kernal
sleepycat berkeley db version 3.2.mumble in /usr/local,
sasl 1.5.24, imap 2.0.12, openssl 0.9.6,
and
Hi--
I'm having trouble figuring out how to authenticate to the
cyrus server I'm trying to install.
Environment:
linux debian 2.2 potato, 2.2.18 kernal
sleepycat berkeley db version 3.2.mumble in /usr/local,
sasl 1.5.24, imap 2.0.12, openssl 0.9.6,
and I believe that I have linked sasl and
I have been trying to install cyrus on Solaris 2.7 (with PAM),
So far I have successfully started up the imap / pop3 servers via master,
my IMAP client MS Outlook! can successful login in.
Feb 22 20:42:04 mail imapd[6581]: login: WJSPC[10.0.1.2] wshenfi
plaintext
But I can not get cyradm
On Wed, Feb 07, 2001 at 12:15:16PM +0100, Jason Quigley wrote:
> Hi!
>
> Has anybody using freeBSD managed to get Cyrus up and running from the
> packages on the ports page?
>
Not exactly from the packages, but it did work fine with me using the
/usr/ports entries for sasl and imapd
I did have
Hi!
Has anybody using freeBSD managed to get Cyrus up and running from the
packages on the ports page?
I installed the pkgs, but, first off, pwcheck would not start as it couldn't
find the file /var/pwcheck/pwcheck. I created a pwcheck directory off var
and it started.
I created a login using s
68 matches
Mail list logo
