On Mon, Jun 4, 2018, at 7:23 PM, Jean-Christophe Delaye wrote:
> Note, if I choose login mech , it works !
I feel like I've seen something like this before. If I recall correctly, the
DIGEST-MD5 mech doesn't support proxy authentication, so if anything in your
stack has this enabled (possibly
On 06/04/2018 03:30 PM, Dan White wrote:
> !!!
> Please be aware that the password for mailproxy was exposed below in
> uuencoded form.
> !!!
Thanks, this is an (internal) lab platform !
I finally focus on the fact that authentication fails if userid and
authid differ.
So, my primary setup was (
!!!
Please be aware that the password for mailproxy was exposed below in
uuencoded form.
!!!
On 06/04/18 11:23 +0200, Jean-Christophe Delaye wrote:
On 06/01/2018 07:54 PM, Dan White wrote:
On 06/01/18 18:03 +0200, Jean-Christophe Delaye wrote:
[root@cassandra etc]# /opt/cyrus-imapd_3.0.7-cyru
>> From client(s), connection to frontend is the issue
>>
>> 001 login standard xxx
>
>> X-QUOTA=X-NUM-FOLDERS IDLE] User logged in
>
>> Once I get connected and authenticated, I launch the command
>> “select inbox”, but I receive the message
>>
couldn't authenticate to backend server: authentication failure
From backend:
imap1 cyrus1/master
about to exec /opt/cyrus-imapd_3.0.7-cyrus1/libexec/imapd
imap1 cyrus1/imap[11632]: SASL could not find auxprop plugin, was
searching for '[all]'
The above error is probably not imp
plete operation
In the log files there is an error from both frontend and backend
From frontend:
cassandra cyrus/imap[19868]:
couldn't authenticate to backend server: authentication failure
From backend:
imap1 cyrus1/master
about to exec /opt/cyrus-imapd_3.0.7-cyrus1/libexec/imapd
imap1 cyru
Thank you for your suggestions! I figured out what was the problem in my
case.
This was the OPTIONS setting in /etc/deafault/saslauthd. Since I run my
Postfix chrooted I had:
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd"
In order for cyradm to identify users using I saslauthd, I also added
Vladimir Vassiliev wrote, at 06/17/2009 09:02 AM:
>> Here is an extract from my imapd.conf file:
>>
>> admins: cyrus
>> imap_admins: cyrus
>> sasl_mech_list: LOGIN
>> sasl_minimum_layer: 1
>> sasl_maximum_layer: 256
>> sasl_pwcheck_method: saslauthd
>
> Maybe it's because of sasl_minimum_layer: 1
> Here is an extract from my imapd.conf file:
>
> admins: cyrus
> imap_admins: cyrus
> sasl_mech_list: LOGIN
> sasl_minimum_layer: 1
> sasl_maximum_layer: 256
> sasl_pwcheck_method: saslauthd
Maybe it's because of sasl_minimum_layer: 1
LOGIN gives you no security layer.
--
Vladimir Vassiliev
Hello,
I have a problem with Cyrus IMAP SASL authentication.
When I try to login to create Cyrus IMAP mailboxes, I see the following:
$ cyradm --user cyrus --auth login localhost
IMAP Password:
Login failed: generic failure at /usr/lib/perl5/Cyrus/IMAP/Admin.pm line 119
cyradm: cannot authentica
brian wrote:
> I'd like to use imapsync to migrate some mailboxes but haven't been able
> to authenticate to the source server with it.
>
> First, here's the failed transaction (run from a 3rd machine):
> -- snip --
did you try:
allowplaintext: 0
Allow the use of cleartext passwords on the w
READ=REFERENCES ANNOTATEMORE IDLE
AUTH=PLAIN AUTH=LOGIN SASL-IR LISTEXT LIST-SUBSCRIBED X-NETSCAPE
Read: 1 OK Completed
Host mail.SRC_DOMAIN.org says it has CAPABILITY for AUTHENTICATE PLAIN
Sending: 2 AUTHENTICATE PLAIN
Sent 22 bytes
Read: +
Sending: YnJpYW5[ ... ]
Sent 74 bytes
Read: 2 NO authent
Dear list,
Here is the config I had with working cyrus
/etc/imapd.conf
---
servername: lvps87-230-8-228.dedicated.hosteurope.de
defaultdomain: dedicated.hosteurope.de
loginrealms: dedicated.hosteurope.de
---
here is the change I have done after getting a
On Mon, 2005-12-05 at 16:20 +0200, Paul-Erik Törrönen wrote:
> But sivtest fails:
> $ sivtest -a poltsi localhost
> S: "IMPLEMENTATION" "Cyrus timsieved v2.2.12-Invoca-RPM-2.2.12-6.fc4"
> S: "SASL" "PLAIN"
> S: "SIEVE" "fileinto reject envelope vacation imapflags notify
> subaddress relational comp
Hello,
We have a problem similar to that described by Andrew Morgan, ie. sieve
(both sieveshell and sivtest) is not accepting the given password. The
difference is that we use the Cyrus-Imapd (2.2.12-6.fc4) provided by
FC4. We use LDAP and saslauthd is configured to validate the login
against it.
On Mon, Jul 28, 2003 at 04:08:34PM -0700, rahul wrote:
I don't use PAM, however I think this should be:
> [/etc/imapd.conf]
> allowanonymouslogin: no
> allowplaintext: yes
> sasl_mech_list: PLAIN
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> admins: sr_imapadmin
> sasl_pwche
Hello Everybody ,
I
am using sasldb for authentcation of user from Outlook Express. & I am
using PAM for authentication From Web (PHP) .
Problem is that , before configuaration of sasldb , all was working fine . But
when i configured Sasldb then it is not authen
phelia master[30583]: process 12301 exited, status 0
Jul 18 17:21:53 ophelia master[12305]: about to exec
/usr/cyrus/bin/timsieved
Jul 18 17:21:54 ophelia sieve[12305]: executed
Jul 18 17:21:54 ophelia sieve[12305]: accepted connection
Jul 18 17:21:56 ophelia timsieved[12305]: badlogin:
localhost.lo
Hello,
I've installed Cyrus IMAP 2.1.13 and Cyrus SASL 2.13 with OpenLDAP 2.1.22
libraries.
When I run saslauthd with shadow mechanism all works fine, but when I tried
ldap authentication working against
Lotus Domino eDirectory this is the response when I make the test:
./testsaslauthd -u 001
No, unfortunately not any more..
You HAVE to use the saslauthd daemon.
This is to get around all the security problems with SASL 1.5.x using
pam.. With sasl 1.5.x AS you have to relax your security to get cyrus to
authenticate via pam (as pam is supposed to run as ROOT, especially to
access /etc/sh
k1680792 wrote:
Hi all,
I want to know:Doese Cyrus-SASL-2.1.10 support /usr/lib/sasl/*.conf with
the following method
pwcheck_method: pam
I don't want to use saslauthd . My another server with Cyrus-SASL-1.5.28
supports 'pwcheck_method:pam' well.
There are significant differences between SASL
Hi all,
I want to know:Doese Cyrus-SASL-2.1.10 support /usr/lib/sasl/*.conf with
the following method
pwcheck_method: pam
I don't want to use saslauthd . My another server with Cyrus-SASL-1.5.28
supports 'pwcheck_method:pam' well.
Thanks!
---
Kai
__
Subject: Re: SASL2+POSTFIX PAM authentication failure
: k1680792 wrote:
:
: >Hi all,
: > I am going to use SASL pam method to complete Postfix's authentication.
: > I compiled Cyrus-sasl-2.1.10 with the following options.
: >--disable-sample
: >--disable-saslauthd
: >--di
ifier
postfix/smtpd[15914]: warning: SASL authentication failure:
Password verification failed
If you want to use PAM, you need to use saslauthd and run it with
saslauthd -a pam. I don't use postfix, but for IMAP you specify
sasl_pwcheck_method: saslauthd in /etc/imapd.conf, so perhap
smtpd[15914]: warning: SASL authentication failure:
Password verification failed
Thanks a lot !
-
Kai
__
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
From: Joshua Szmajda <[EMAIL PROTECTED]>
Hey all,
I'd really like to use cyrus imapd as my imap server. I've got a mid to
large-scale webmail deployment coming up and cyrus's internal user database
seems to be right up my alley. I'm having some trouble though, and I
haven't been able to find t
Hey all,
I'd really like to use cyrus imapd as my imap server. I've got a mid to
large-scale webmail deployment coming up and cyrus's internal user
database seems to be right up my alley. I'm having some trouble though,
and I haven't been able to find the answer in the list-archive.
I am tryin
I can login into cyrus-imap's pop3 server. However, I saw the log shows as
below:
May 13 20:03:49 thunderbolt pop(pam_unix)[4918]: authentication failure;
logname= uid=76 euid=76 tty= ruser= rhost= user=testuser
May 13 20:03:49 thunderbolt pop3d[4918]: login:
thunderbolt.chao
[EMAIL PROTECTED] schrieb am Tue, Mar 12, 2002 at 09:12:46AM -0500:
[...]
>
> My /var/log/auth.log tells me:
> Mar 12 08:55:38 garvey_ imapd[17588]: unable to open Berkeley db /etc/sasldb:
>Invalid argument
> Mar 12 08:55:41 garvey_ imapd[17588]: unable to open Berkeley db /etc/sasldb:
>Invalid
HI,
I have pulled downn Berkeley db 3.3.11
if the jump to 4 would have cause issues...
I recomipiled and installed it,
Then recompiled and installed sasl 1.5.27
Then recompiled and installed cyrus imapd 2.0.16
I configured cyrus with --with-auth=unix (since I am not using Kerberos)
As per th
[EMAIL PROTECTED] schrieb am Tue, Mar 12, 2002 at 02:20:42AM -0500:
[...]
>
> sh-2.05$ cyradm localhost
> IMAP Password:
> Login failed: authentication failure at
>/usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 78
> cyradm: cannot authentic
localhost
IMAP Password:
Login failed: authentication failure at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm line 78
cyradm: cannot authenticate to server with as cyrus
can someone, anyone please let me in on how to solve this problem...!
Thanks a million
I think I am very close to having this all work, I
have postfix working with ldap properly but when a
user tries to authenticate via a mail client it gets
authentication failure, while this is going on the
logs are showing connections to the slapd daemon so it
must be close to working at the
I think I am very close to having this all work, I
have postfix working with ldap properly but when a
user tries to authenticate via a mail client it gets
authentication failure, while this is going on the
logs are showing connections to the slapd daemon so it
must be close to working at the
> On Fri, 14 Dec 2001 10:57:49 -0500 (EST),
> Rob Siemborski <[EMAIL PROTECTED]> (rs) writes:
rs> I suspect that the user you are running as is not an admin in the cyrus
rs> configuration file. (e.g. if sieveshell isn't given an authentication
rs> name, it tries to authenticate as whatev
ai" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, December 14, 2001 10:57 AM
Subject: Re: sieveshell DIGEST-MD5 authentication failure
> On Fri, 14 Dec 2001, Taro Ikai wrote:
>
> > I just installed Cyrus on my FreeBSD server. IMAP access is working fine.
>149, chunk 1.
> Dec 14 10:32:28 saba timsieved[66837]: badlogin: localhost[::1] DIGEST-MD5
>authentication failure
>
> What's going on?
I suspect that the user you are running as is not an admin in the cyrus
configuration file. (e.g. if sieveshell isn't given an authe
/bin/sieveshell line
149, chunk 1.
Dec 14 10:32:28 saba timsieved[66837]: badlogin: localhost[::1] DIGEST-MD5
authentication failure
What's going on?
Taro
CxjaGFyc2V0PXV0Zi04LGRpZ2VzdC11cmk9ImltYXAvbWluaS5kaWdpdGFscGxhY2Uub3JnI
ixyZXNwb
25zZT0wMzk0MzE4MTE0NGUwYTVhMTU1YmU0OTIyY2EwY2RjNA==
S: A01 NO authentication failure
Authentication failed. generic failure
Security strength factor: 1
This is my error log:
Jul 24 10:10:27 mini imapd[32471]: accepted
39 matches
Mail list logo
