similar to: test67 ldap_connection

Hello, I'm wondering if the following situation is valid (though I think it isn't since I still cannot authenticate with ldap pass/userdb on test67 running on FreeBSD-5.3). Is it normal that the passdb_ldap_conn->attr_names second element (for instance) "turns to" "homeDirectory" as the following step by step gdb run sample shows ? : -- Breakpoint 1,

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Hello Timo, I'm curious about 2 points (I'm using alpha2 but these are general questions) : Background : . I connect to dovecot-1.0.alpha2 through thunderbird . I use ldap pass/userdb and PLAIN mech . I've only got one auth block in dovecot.conf (all pass/userdb/mech except ldap/PLAIN are commented) 1) I notice that, for one thunderbird connection trial, imap-login

http://dovecot.org/test/ Hopefully better release than last one. Fixes several problems test66 had and also some older problems reported in this list. It also contains a pretty large mbox code cleanup, fixing several problems (especially related to X-IMAP/X-IMAPbase headers) and making it a bit faster. Maybe I'll backport it to 1.0-stable too when it looks like it's stable.. BTW. mbox

Just a note, I backported some larger mbox changes from 1.0-test67. Hopefully works, but if you're going to try it test it well first :) Should fix some issues related to X-IMAP/X-IMAPbase header handling and maybe some other mbox related problems as well. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186

Hello Timo, your patch introducing pass_attr_names and user_attr_names fixed the problem of the 'shared' attr_names member of [passdb|userdb]_ldap_conn as I answered in the relative thread. Now I think there is a problem while comparing user-provided and ldap-provided passwords causing a false 'password mismatch' situation, while using PLAIN mechanism with LDAP authentication.

Hello, The installation of 1.0-test66 (still on FreeBSD 5.3-RELEASE-p1 with openldap-2.1.27) solved the SIGSEV problem I posted here on March 30 but I still cannot authenticate correctly with ldap. logs report "ldap(dovetest,127.0.0.1): No password in reply" and my client gets a "NO Temporary authentication failure." Obviously the attr_names array of the

Hello, It seems that mbox format mailboxes holding \r\n (CR + LF) character sequences (instead of \n only) still cause assertion failures when moving messages from one folder to another. -- dovecot: Jul 19 17:14:52 Error: IMAP(dovetest): file istream-raw-mbox.c: line 38 3 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != ( uoff_t)-1) -- I seems to work in -test78

I've finally got it to work, kind of .. It should allow you to log in, but several settings don't work yet and there are probably many bugs. Anyway, I thought I'd show this already in case someone is interested of looking how it works :) One thing I'm still wondering a bit is if I should show process names as: 32602 pts/19 S 0:00 dovecot/config 32603 pts/19 S

The attached patch makes the local IP address to which the client connected available to the authentication modules; i.e., the local IP address is available for substitution as %i for the mysql and pgsql modules. We needed this feature to support thousands of our legacy accounts which are authenticated by username/local_part (not the full email address) and IP address (one per domain). Timo,

Am 27.02.20 um 11:32 schrieb L.P.H. van Belle via samba: > But your missing the important part. > > How ? > > Kerberos ? NTLM ? LDAP ? > > ;-) Ah ok Actually I want to use secure LDAP from a PHP docker container. So far no Kerberos involved as far as I see. (I have to dockerize a php app which is badly written ... and I want to clean up a bit, and let it bind

I've been using the 1.0 test series (currently 1.0test 67 and before that 1.0-test59) and both exhibited this issue.. I use Thunderbird and will open one or two of my nested Maildir folders via imap and find that it goes out there trying to open the folder (according to the messages that Thunderbird claims) and it never comes back.. I've attached to the various dovecot processes to

Hi, I'm using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 there seems to be the same bug/feature). The userdb and passdb use LDAP. All further configuration is done in auth-ldap.conf.ext. uri = ldaps://<host>/ # tls = tls_cert_file = /etc/ssl/certs/client-cert.pem tls_key_file = /etc/ssl/certs/client-key.file Dovecot ignores the

Hi, User iteration doesn't work, we're getting: > auth: Error: Trying to iterate users, but userdbs don't support it The way I understand it, I need to set iterate_attrs and iterate_filter for iteration to work. I have set it, and yet it does't work with the above failure. Our config is against ldap (active directory) and generdoveadm user -u "*" oalally works

Timo or anyone, This may be a bug or maybe a design decision. Either way I am curious to hear comments. Why do the dovecot-0.99.14 server's .imap.index files contain a cached copy of each message's date and time as supplied by the filesystem, as opposed to the date and time found in each message header? When testing various imap clients (eg. tbird-1.0.2, evolution-2.0, outlook2003,

We received no replies to this email that we sent a few days ago. We're not sure why. If we miss something that is obvious to everybody, kindly point it out. We ?ould like to get iteration working, to be able to mass-delete specific emails from all mailboxes, in case of for example received virusses... Here is my question again: Hi, User iteration doesn't work, we're getting:

Hello Timo, I just tried the master user feature with a very simple setup (Dovecot v2.2.15) : !include auth-master.conf.ext -> passwd-file passdb !include auth-ldap.conf.ext -> ldap passdb (userdb prefetched) without auth_bind=yes without pass=yes I get this userdb lookup error : dovecot: auth: passwd-file(masteruser,157.99.64.42,master,<4Pgesh0OygCdY0Aq>): Master user logging in

timo, i think i found a small problem with the ldap implementation: when using auth_bind (this might be in all conditions, not just that one - i haven't tested further), if the server lost connection to the ldap server (ie, the ldap server died) dovecot-auth would never reconnect to the ldap server and all subsequent auth attempts would fail. after a little more digging, i discovered that

Hi guys, I had a look in the sources about this problem. the problem seems to be the ldap_escape function that is called from ldap_verify_plain_auth_bind_userdn(..) I dont really know if this escaping is needed at this point, but with this change it works for me. No other problems discovered so far. could somebody, who is deeper in the sources give me a hint if this will make some troubles?

--- dovecot-1.0.rc17/src/auth/db-ldap.~h 2007-01-15 03:23:09.000000000 +0200 +++ dovecot-1.0.rc17/src/auth/db-ldap.h 2006-11-07 18:47:00.000000000 +0200 @@ -38,6 +38,7 @@ const char *default_pass_scheme; const char *user_global_uid; const char *user_global_gid; + const char *user_global_mail; /* ... */ int ldap_deref, ldap_scope; ---