1. sasldb access
For the hell of it I changed access to Sasldb* to 777
-rwxrwxrwx 1 cyrus mail 16384 Dec 20 21:20 sasldb.db
-rwxrwxrwx 1 cyrus mail 16384 Dec 21 13:27 sasldb2.db
%cyradm -user cyrus --auth digest-md5 localhost imap
Password:
localhost> cm user.jdoe
createmailbox: Permis
I'm also a bit of a newbie but FWIW comments inline;
On Fri, 2004-12-24 at 05:21, Bungee [EF] wrote:
SU’d to cyrus
Ran “saslpasswd2 -c cyrus” and set password
Ran “saslpasswd2 -c jdoe” and set password
Don't need to be cyrus user to do this as far as I'm awa
> Ok what have I done wrong? I think it may be a configuration problem but
I don't know enough about cyrus to confirm where the fault is.
i don't know all the answers, but here is something to get you further
> Although this appears to work ok, I notice in my error messages
> (saslpasswd2: Couldn'
> Ok what have I done wrong? I think it may be a configuration problem but I
> don't know enough about cyrus to confirm where the fault is.
i don't know all the answers, but here is something to get you further
> Although this appears to work ok, I notice in my error messages
> (saslpasswd2: Could
Ok what have I done wrong? I think it may be a configuration problem
but I don’t know enough about cyrus to confirm where the fault is.
OS = FreeBSD 5.2.1
Installed “/usr/ports/security/cyrus-sasl” (make install)
Installed “/usr/ports/mail/cyrus-imapd2” (make install)
Ran
Hi everybody
I'm a newbie with cyrus-imapd2
I installed cyrus-sasl2 with bdb version = 41
and the same for cyrus-imapd2, everythinh is done via the freebsd 5.1 ports.
I managed to launch imapd when moving the script to the /etc/rc.cd/cyrus_imapd
directory and by enablig cyrus-imapd in rc
Nikola Milutinovic <[EMAIL PROTECTED]> wrote:
250-AUTH=NTLM PLAIN LOGIN DIGEST-MD5 CRAM-MD5
I don't have this second line on Sendmail 8.12.9 - am I missing something?
No, it is for (again) broken clients which are using "AUTH=". Some kind of
legacy auth.
Is it for sure that O and OE cannot use D
> So I would have to disable all but NTLM to be sure AUTH=NTLM is the first
> or only "AUTH" visible. No I won't do this for Microsoft users only because
> of their broken clients.
Maybe there is a way... Basically the ordering of the clients is the ordering of how
the *.la files are picked up
Rob Siemborski <[EMAIL PROTECTED]> wrote:
Mostly Randomly. Somewhat based on the order the plugin is loaded.
Security requirements of SASL basicly dictate that the client ignore the
order they are advertised.
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks w
Pascal Gienger wrote:
We have some kind of - problem.
We try to understand HOW the different SASL plugins are ordered when
doing an announcement (. CAPABILITY).
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks when "AUTH=NTLM" is not the FIRST method annou
On Fri, 12 Sep 2003, Pascal Gienger wrote:
> We have some kind of - problem.
>
> We try to understand HOW the different SASL plugins are ordered when doing
> an announcement (. CAPABILITY).
Mostly Randomly. Somewhat based on the order the plugin is loaded.
Security requirements of SASL basicly d
We have some kind of - problem.
We try to understand HOW the different SASL plugins are ordered when doing
an announcement (. CAPABILITY).
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks when "AUTH=NTLM" is not the FIRST method announced! It gives
me an er
On Fri, 3 Jan 2003, Martin Y. Chiu wrote:
> After reading some document and tracing some code of imapd2 and
> sasl, I found that cyrus-imapd2 use the different authentication
> method with IMAP 'LOING' and 'AUTHENTICATE' command. LOGIN uses
> s
Dear all,
After reading some document and tracing some code of imapd2 and
sasl, I found that cyrus-imapd2 use the different authentication
method with IMAP 'LOING' and 'AUTHENTICATE' command. LOGIN uses
sasl_checkpass() and AUTHENTICATE uses sas
14 matches
Mail list logo
