> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; info-cyrus@lists.andrew.cmu.edu
> Subject: RE: IMAPD "Authentication failed. generic failure"
> Date: Tue, 18 M
> CC: info-cyrus@lists.andrew.cmu.edu
> From: [EMAIL PROTECTED]
> Subject: Re: IMAPD "Authentication failed. generic failure"
> Date: Mon, 17 Mar 2008 18:00:28 -0400
> To: [EMAIL PROTECTED]
>
> First failure:
>
> On
J.J. Day wrote, at 03/17/2008 11:25 AM:
>>> auth.log
>>> ==
>>> Mar 16 23:38:40 dc-mail imap[3700]: could not find auxprop plugin, was
>>> searching for [all]
>> It's been a while since I compiled my own Cyrus SASL, but when I did, I
>> used to need a symlink:
>>
>> ln -s /usr/local/lib/sasl
First failure:
On 17 Mar 2008, at 17:18, J.J. Day wrote:
> C: A01 AUTHENTICATE PLAIN
> S: A01 NO no mechanism available
> Mar 17 14:34:11 dc-mail imaps[5423]: badlogin: dc-mail.training.int
> [192.168.251.3] PLAIN [SASL(-4): no mechanism available: Couldn't
> find mech PLAIN]
PLAIN authN was
> CC: info-cyrus@lists.andrew.cmu.edu
> From: [EMAIL PROTECTED]
> Subject: Re: IMAPD "Authentication failed. generic failure"
> Date: Mon, 17 Mar 2008 15:31:40 -0400
> To: [EMAIL PROTECTED]
>
> On 17 Mar 2008, at 11:25, J.J
On 17 Mar 2008, at 11:25, J.J. Day wrote:
> #allowplaintext: yes
This is likely to be your problem.
:wes
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
>> auth.log
>> ==
>> Mar 16 23:38:40 dc-mail imap[3700]: could not find auxprop plugin, was
>> searching for [all]
>
> It's been a while since I compiled my own Cyrus SASL, but when I did, I
> used to need a symlink:
>
> ln -s /usr/local/lib/sasl2 /usr/lib/sasl2
>
> Give it a try, and if
J.J. Day wrote, at 03/17/2008 01:53 AM:
> auth.log
> ==
> Mar 16 23:38:40 dc-mail imap[3700]: could not find auxprop plugin, was
> searching for [all]
It's been a while since I compiled my own Cyrus SASL, but when I did, I
used to need a symlink:
ln -s /usr/local/lib/sasl2 /usr/lib/sasl2
SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES
ANNOTATEMORE CATENATE CONDSTORE IDLE URLAUTH
S: C01 OK Completed
Please enter your password:
C: L01 LOGIN cyrus {5}
S: + go ahead
C:
S: L01 NO Login failed: authentication failure
Authentication failed. generic failure
Security strength f
J.J. Day wrote, at 03/17/2008 12:12 AM:
> [EMAIL PROTECTED] etc]# imtest -u cyrus -m login localhost
Try this instead:
imtest -u cyrus -a cyrus -t "" localhost
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://a
ES ANNOTATEMORE CATENATE CONDSTORE IDLE URLAUTH
S: C01 OK Completed
Please enter your password:
C: L01 LOGIN root {5}
S: L01 NO Login only available under a layer
Authentication failed. generic failure
Security strength factor: 0
. logout
* BYE LOGOUT received
. OK Completed
Connection closed.
[EMAIL
Thanks a lot! I'll try that but I've solved changing password for cyrus
user in Linux:
passwd cyrus
etc.
Thanks a lot for your smart support !!
We have solved!! :-)))
Stefano C.
> Am Tuesday 03 October 2006 12:23 schrieb [EMAIL PROTECTED]:
>
>> > sasl_mech_list: plain login
>> >
>>
Am Tuesday 03 October 2006 12:23 schrieb [EMAIL PROTECTED]:
> > sasl_mech_list: plain login
> >
> > is missing. Then test again with cyrus and "other" users. Do "other"
> > users work anymore?
> >
> > Then show how you start saslauthd.
>
> Sorry I've forgotten
> I start saslauth as following:
> sasl_mech_list: plain login
>
> is missing. Then test again with cyrus and "other" users. Do "other" users
> work anymore?
>
> Then show how you start saslauthd.
>
Sorry I've forgotten
I start saslauth as following:
rcsaslauthd start
Stefano C.
Cyrus Home Page: http://cyrusimap.web.
a plaintext backup of mailboxes.db using (as root):
>> >> su -cyrus -c "ctl_mailboxlist -d" > mailboxlist.txt
>> >>
>> >> I've build a database from the plaintext using:
>> >> cvt_cyrusdb mailboxlist.txt
>> >>
>> >
r from my system.
> >> >>
> >> >> I overrided the folowing directories:
> >> >> /var/spool/imap
> >> >> /var/lib/imap
> >> >> /var/lib/sieve
> >> >> with the ones of te system I would recover.
> >> &g
; >> cvt_cyrusdb mailboxlist.txt
> >>
> >> Now I can connect to Cyrus with:
> >> telnet localhost 143
> >> as every user listed with:
> >> sasldblistusers
> >> except as cyrus.
> >> My server IMAP can receive mails from inside and outside the
ry
>
> The User has no Sieve-Script. Either ignore these Errors or don't log
> DEBUG-Messages in Syslog.
>
>> My server IMAP can receive mails from inside and outside the LAN.
>> Anyway, it's unconfortable I receive:
>> 0: NO "authentication failed"
&
og.
> My server IMAP can receive mails from inside and outside the LAN.
> Anyway, it's unconfortable I receive:
> 0: NO "authentication failed"
>
> for the command:
> testsaslauthd -u cyrus -p cyrus
Above you tell something about sasldb, here you test with s
or directory
My server IMAP can receive mails from inside and outside the LAN.
Anyway, it's unconfortable I receive:
0: NO "authentication failed"
for the command:
testsaslauthd -u cyrus -p cyrus
Any suggestions?
Thanks in advance!
Stefano C.
Cyrus Home Page: http://
use the
replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no
mechanism available
here is the result of the synctest:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication failed
nstall the the new version of cyrus-imap to use the
>>> replication.
>>>
>>> but I can't authenticate on my replica server:
>>>
>>> here is the error in the log:
>>>
>>> sync_client[26757]: couldn't authenticate to backend server: no
ckend server: no
mechanism available
here is the result of the synctest:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication failed. no mechanism available
Security strength factor: 0
it seems the auth mechs are not advertised
I use saslauthd for my imap+pop auth and it works fine.
t
try to install the the new version of cyrus-imap to use the replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no mechanism
available
here is the result of the synctest:
S: * OK mai
ult of the synctest:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication failed. no mechanism available
Security strength factor: 0
it seems the auth mechs are not advertised
I use saslauthd for my imap+pop auth and it works fine.
Do imapd and pop3d advertise any SASL mechs? You must have at
use the replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no mechanism
available
here is the result of the synctest:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication
:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication failed. no mechanism available
Security strength factor: 0
it seems the auth mechs are not advertised
I use saslauthd for my imap+pop auth and it works fine.
there should be a special option for the advertising of mechs but I
haven't f
You should bugzilla this.
OpenMacNews wrote:
hi earl,
-- On Tuesday, November 2, 2004 8:17 AM -0500 Earl R Shannon
<[EMAIL PROTECTED]> wrote:
I see the PLAIN mech being advertised by the server. I'd check and
make sure the SASL libraries can be found by the imtest client.
Regards,
Earl Shanno
hi earl,
-- On Tuesday, November 2, 2004 8:17 AM -0500 Earl R Shannon <[EMAIL PROTECTED]> wrote:
I see the PLAIN mech being advertised by the server. I'd check and make sure the SASL
libraries can be found by the imtest client.
Regards,
Earl Shannon
well, I'll be ... I thought I'd proactively fix
s-imap/bin/imtest -t "" -m plain -a testuser -p
imap testdomain.com
it fails with an "Authentication failed. no mechanism available":
S: * OK testserver.testdomain.com Cyrus IMAP4 v2.2.8 server ready
C: C01 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUO
ting cyrus-imap w/ TLS, however, i'm having some issues. specifically, when i:
% /usr/local/cyrus-imap/bin/imtest -t "" -m plain -a testuser -p imap
testdomain.com
it fails with an "Authentication failed. no mechanism available":
S: * OK testserver.testdomain.
Hi,
The imtest runs well, I can login to imap and pop3 server without problem.
But sending email thru smtp authentication failed.
Here is the error:
# smtptest -v -a [EMAIL PROTECTED]
127.0.0.1
S: 220 at.mydomain.com ESMTP Exim 4.43 Mon
--On Wednesday, September 01, 2004 11:40:40 -0400 Ken Murchison
<[EMAIL PROTECTED]> wrote:
Cyrus isn't finding your SASL plugins, because no SASL mechs are listed
in the capability list. Make sure you have SASL installed correctly.
SNIP
Hi Ken,
actually IMAP is authenticating against SASL.
I
Gerald Griessner wrote:
--On Wednesday, September 01, 2004 08:49:25 -0400 Ken Murchison
<[EMAIL PROTECTED]> wrote:
Gerald Griessner wrote:
Hi,
I migrated from Cyrus Imap 2.1.16 to 2.2.8 a couple of days ago.
Since then I can not login to Sieve any more.
Can anyone help me?
below I included my im
--On Wednesday, September 01, 2004 08:49:25 -0400 Ken Murchison
<[EMAIL PROTECTED]> wrote:
Gerald Griessner wrote:
Hi,
I migrated from Cyrus Imap 2.1.16 to 2.2.8 a couple of days ago.
Since then I can not login to Sieve any more.
Can anyone help me?
below I included my imapd.conf, sivtest output
ATION" "Cyrus timsieved v2.2.8"
S: "SIEVE" "fileinto reject envelope vacation imapflags notify
subaddress relational regex"
S: "STARTTLS"
S: OK
Cyrus isn't finding your SASL plugins, because no SASL mechs are listed
in the capability list. Make s
Cyrus timsieved v2.2.8"
S: "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational regex"
S: "STARTTLS"
S: OK
Authentication failed. generic failure
Security strength factor: 0
C: LOGOUT
OK "Logout Complete"
Connect
On Tue, 11 May 2004, Nicolas Schmitz wrote:
> Hello,
>
> >
> >This tests saslauthd only. You need to use sample client and server
> >($cyrus-sasl-src/sample) to test sasl lib.
> >
> >
> >
> here is the output :
> SERVER :
> pc-schmitz-vm:/appli/distrib/cyrus-sasl-2.1.18/sample# ./server -s ldap
Hello,
This tests saslauthd only. You need to use sample client and server
($cyrus-sasl-src/sample) to test sasl lib.
here is the output :
SERVER :
pc-schmitz-vm:/appli/distrib/cyrus-sasl-2.1.18/sample# ./server -s ldap
trying 10, 1, 6
socket: Address family not supported by protocol
trying 2,
On Mon, 10 May 2004, Nicolas Schmitz wrote:
> Thank you for your quick answer.
> I've tried to add --with-plugindir=/appli/cyrus-sasl/lib/sasl2 to my .configure,
> but the problem is the same... I have also tried to recompile cyrus-imap, with
> no result.
>
> I think sasl works ok because I can d
Thank you for your quick answer.
I've tried to add --with-plugindir=/appli/cyrus-sasl/lib/sasl2 to my .configure,
but the problem is the same... I have also tried to recompile cyrus-imap, with
no result.
I think sasl works ok because I can do :
pc-schmitz-vm:~# /usr/local/bin/testsaslauthd -u sc
verything works fine, except
> sieve...
>
> Here is the output :
>
>
> pc-schmitz-vm:~# /appli/cyrus-imapd/bin/sivtest -a schmitz localhost
> S: "IMPLEMENTATION" "Cyrus timsieved v2.2.3"
> S: "SIEVE" "fileinto reject envelope vacation imapflag
:~# /appli/cyrus-imapd/bin/sivtest -a schmitz localhost
S: "IMPLEMENTATION" "Cyrus timsieved v2.2.3"
S: "SIEVE" "fileinto reject envelope vacation imapflags notify
subaddress relational regex"
S: "STARTTLS"
S: OK
Authentication failed. generic failur
I assured that libraries were all in-sync by running 'portupgrade' under
FreeBSD. (Thanks Oliver for the idea.)
I cannot yet create a mailbox. Here is what I get when I try:
[mail2] ~> whoami
cyrus
[mail2] ~> cyradm -u cyrus localhost
Password:
localhost.familyradio.org> lm
localhost
dmins:" line in your imapd.conf).. This account will need a
password, so do whatever it takes in your setup to create a 'real' cyrus
account.
On Tue, 2003-09-09 at 22:00, Mike Allen wrote:
Gentlemen:
When I run 'imtest' on my system, I get the following failure:
-->: snip &l
Mike Allen wrote:
Gentlemen:
When I run 'imtest' on my system, I get the following failure:
-->: snip <--
S: A01 NO user not found
Authentication failed. generic failure
Security strength factor: 256
. logout<< manually typed-in because it stalled here.
* BYE LOGOUT r
;real' cyrus
account.
On Tue, 2003-09-09 at 22:00, Mike Allen wrote:
> Gentlemen:
>
> When I run 'imtest' on my system, I get the following failure:
> -->: snip <--
> S: A01 NO user not found
> Authentication failed. generic failure
> Security strength fa
Gentlemen:
When I run 'imtest' on my system, I get the following failure:
-->: snip <--
S: A01 NO user not found
Authentication failed. generic failure
Security strength factor: 256
. logout<< manually typed-in because it stalled here.
* BYE LOGOUT received
. OK Compl
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Simon Matter
> > Sent: Tuesday, February 26, 2002 9:32 AM
> > To: Keith Kee
> > Cc: Ken Murchison; Cyrus Info
> > Subject: Re: sieveshell authentication failed on Solaris
> >
> >
> On Tue, 26 Feb 2002 16:59:28 +0100,
> Simon Josefsson <[EMAIL PROTECTED]> (sj) writes:
sj> I was wondering why all copies from Simon Matter on this list ended up
sj> in my junk folder instead of my info-cyrus folder, and it seems to be
sj> because S.M.'s messages contain invalid RFC 282
Simon Matter <[EMAIL PROTECTED]> writes:
> >Received: from mobile.sauter-bc.com (unknown [10.1.6.21])
> by basel1.sauter-bc.com (Postfix) with ESMTP
> id D4BA757306; Tue, 26 Feb 2002 15:32:25 +0100 (CET)
...
> Sender: [EMAIL PROTECTED]
I was wondering why all copies from Simon Matter
ent: Tuesday, February 26, 2002 9:32 AM
> To: Keith Kee
> Cc: Ken Murchison; Cyrus Info
> Subject: Re: sieveshell authentication failed on Solaris
>
>
> Hm, sorry, I don't know whats wrong with your setup. IIRC when you have
> more than PLAIN in your mechlist, sieveshell can not us
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Simon Matter
> > Sent: Tuesday, February 26, 2002 2:38 AM
> > To: Keith Kee
> > Cc: Ken Murchison; Cyrus Info
> > Subject: Re: sieveshell auth
Info
> Subject: Re: sieveshell authentication failed on Solaris
>
>
> As you mentioned you have started saslauthd to use PAM. Therefore you
> need to have the different configs in PAM. If timsieved needs
> authentication, it sends the request to saslauthd with service sieve,
> sasl
cess 1434
> exited
> , status 75
>
> Thanks
> keith
>
> > -Original Message-
> > From: Ken Murchison [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, February 25, 2002 8:24 PM
> > To: Keith Kee
> > Cc: Cyrus Info
> > Subject: Re: sieves
xited
, status 75
Thanks
keith
> -Original Message-
> From: Ken Murchison [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 25, 2002 8:24 PM
> To: Keith Kee
> Cc: Cyrus Info
> Subject: Re: sieveshell authentication failed on Solaris
>
>
>
>
> Keith Kee wrote:
Keith Kee wrote:
>
> Hi:
>I am running cyrus-imap 2.1.2 and cyrus-sasl 2.1.1 on Solaris 8, and I am
> having problem getting timsieved to authenticate right. Following the
> instructions written in "installing sieve" in the docs included with the
> source, I should be able to check my login
Hi:
I am running cyrus-imap 2.1.2 and cyrus-sasl 2.1.1 on Solaris 8, and I am
having problem getting timsieved to authenticate right. Following the
instructions written in "installing sieve" in the docs included with the
source, I should be able to check my login to timsieved using
sieveshell -
lhost' as user cyrus works, authenticating from
a remote mail client works too.
But if I try to use cyradm localhost, I always get the message:
Password:
application-specific initialization failed: authentication failed
with cyradm -m plain localhost another Password question appears:
Pl
Ramiro Morales <[EMAIL PROTECTED]> wrote:
> After fiddling a bit I found that I must pass also the -a switch to
> imtest
>
> [root@imap /root]# imtest -u cyrususer -a cyrususer localhost
>
> to achieve success.
I managed to succeed to get correct responce!! Thank you very much :)
But I don't
ed info as sugested by other users of the
Cyrus packages).
When I tried imtest I encountered the same error message
S: A01 NO authentication failure
Authentication failed. generic failure
Security strength factor: 128
After fiddling a bit I found that I must pass also the -a switch to
imtest
ellGMGtJZFRweVFZPSIsY25vbmNlPSJqZVJKd1h5REthRjcrRHVYOHozRW5RZDBtTjJ2N0E2QmNqdDE2TDB3QmRrPSIsbmM9MDAwMDAwMDEscW9wPWF1dGgtY29uZixjaXBoZXI9InJjNCIsY2hhcnNldD11dGYtOCxkaWdlc3QtdXJpPSJpbWFwL2ltYXAuczEuaXRkLm5lcy5uZWMuY28uanAiLHJlc3BvbnNlPTFiYjc3NWY1NzAyNDE0OWUxYmU2Nzk3OTE5YjBkYmMz
S: A01 NO authentication failure
Authenticat
t;
> S: A01 NO authentication failure
> Authentication failed. generic failure
>
> I tried to use sasldb method and this must be easiest way to
> authenticate user. Please give me a help.
Hello:
I'm the maintainer of the packages. Please
excuse me for the delay in this r
ave a question. I have decided to use Cyrus IMAP system a few days
> ago, so I am a beginner of Cyrus. I encountered an error at first
> step. My headache is the messages on console when inputing 'imtest'
> command.
>
> S: A01 NO authentication failure
> Authentication
Hi everybody.
I have a question. I have decided to use Cyrus IMAP system a few days
ago, so I am a beginner of Cyrus. I encountered an error at first
step. My headache is the messages on console when inputing 'imtest'
command.
S: A01 NO authentication failure
Authentication faile
=ORDEREDSUBJECT THREAD=REFERENCES
IDLE
AUTH=ANONYMOUS AUTH=DIGEST-MD5 AUTH=CRAM-MD5
S: C01 OK Completed
Password:
C: L01 LOGIN cyrus {7}
+ go ahead
C:
L01 NO Login failed: no mechanism available
Authentication failed. generic failure
Security strength factor: 0
Now it tells me there is a generic failure
66 matches
Mail list logo
