t yet myself.
Yes of course. I use FreeBSD on all sparc64 servers (FreeBSD/sparc64
runs only 64bit binaries).
At some point will need to do 64-bit though because getting some large
quota needs for some shared folders.
:-)
--
Alex Deiter
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wik
long b;
enum enum_value e;
Thanks a lot!
--
Alex Deiter
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Amos wrote:
I'm seeing the same thing on Solaris 8, 9, and 10 (s10_69) using a not
so old cc (-xarch=v9 option) and gcc 3.3.3 (-m64). These are all on
sparc boxes. I got non-zero values by changing 'int' to 'long'.
Quite right!
--
Alex Deiter
---
Cyrus Home Page: htt
Hi,
Cyrus IMAP on 64bit arch incorrectly interprets defaults numerical
parameters of a imapd.conf: all of them are equal to zero!
For example, compile source in attach:
# gcc -m64 test.c
# file a.out
a.out: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically
linked, not stripped
#
Hi,
I running Cyrus-IMAP on FreeBSD 5.3 sparc64. After update Cyrus-IMAP
from 2.2.3 up to 2.2.10 got error:
Dec 27 21:23:19 satira nntp[24755]: DBERROR db4: PANIC: fatal region
error detected; run recovery
Dec 27 21:23:19 satira nntp[24755]: DBERROR: critical database situation
Dec 27 21:23:19 s
Igor Brezac пишет:
But cyrus-imap 2.1.16 works fine for me with same configurion as
cyrus-imap 2.2.3:
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: ldapdb
sasl_ldapdb_uri: ldap://server.komi.mts.ru
sasl_ldapdb_mech: GSSAPI
# cyradm --user test --auth CRAM-MD5 solveig
Password:
solveig.k
Igor Brezac пишет:
If ldapdb auxprop plugin contacts with remote ldap server (i.e.
sasl_ldapdb_mech: EXTERNAL is not possible):
Why not?
How will ldapdb contact with removed ldap the server using EXTERNAL?
Use TLS ?
Can you use GSSAPI mech with ldapsearch?
Yes:
# kinit -k -t /etc/kr
If ldapdb auxprop plugin contacts with remote ldap server (i.e.
sasl_ldapdb_mech: EXTERNAL is not possible):
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: ldapdb
sasl_ldapdb_uri: ldap://server.komi.mts.ru
sasl_ldapdb_mech: GSSAPI
i got error:
slapd[5483]: do_sasl_bind: dn () mech GSSAPI
sl
Igor Brezac wrote:
2.2 CVS HEAD (A little newer than 2.2.3)...
If liblber.so.202 comes from openldap 2.2.6 you should be good to go.
After rebuild & reinstall cyrus-sasl-2.1.17, openldap-2.2.6, ldapdb (from contrib openldap-2.2.6) and cyrus-imap-2.2.3 it works fine for me:
# /usr/local/bin/im
> Well, this is a bug in cyrus and openldap libs (and the sasl lib which
> prevents cyrus from being fixed). Fortunately,
> http://www.openldap.org/its/index.cgi?findid=2926 fixes the problem.
> Although, the fix is available in openldap 2.2.6 and 2.1.27.
Yes, therefore I have updated OpenLDAP up
hi,
After upgrade Cyrus IMAP from 2.1.16 up to 2.2.3 following setup does
not work:
mail client -> Cyrus IMAP -> Cyrus SASL -> ldapdb auxprop -> OpenLDAP
cyrus log:
pop3[32386]: bad userid authenticated
pop3[32386]: badlogin: server.komi.mts.ru[1.1.1.1] plaintext bill
SASL(-13): user not found:
11 matches
Mail list logo
