Re: Dovecot with LDAP Proxy
Hi, yes sure, we already use proxy with mysql auythentication. On the same server we have the proxy working with mysql and it regularly uses the backends servers, but when we configure the proxy to use LDAP instead it always uses the default localhost and not the backend IPs. Regards -federico Il 21/05/2019 07:25, Aki Tuomi ha scritto: > > > On 20.5.2019 20.06, Federico Bartolucci via dovecot wrote: >> Hello, >> >> configuring Dovecot with LDAP authentication, adding the parameter in >> ther sql config file: >> >> pass_attrs = \ >> =proxy=y >> >> I see then backend connections always addressed to localhot port 143: >> >> /user=uten...@domanin.com proxy lip=127.0.0.1 lport=143 / >> >> while I expect that connections would be managed by the director and >> then addressed to my backend IPs and specific port. >> Is there a way to configure ldap proxy to get that behavior? >> >> Thanks in advance. >> >> -federico > > Hi! > > Have you read https://wiki2.dovecot.org/Director ? > > Aki > signature.asc Description: OpenPGP digital signature
Dovecot with LDAP Proxy
Hello, configuring Dovecot with LDAP authentication, adding the parameter in ther sql config file: pass_attrs = \ =proxy=y I see then backend connections always addressed to localhot port 143: /user=uten...@domanin.com proxy lip=127.0.0.1 lport=143 / while I expect that connections would be managed by the director and then addressed to my backend IPs and specific port. Is there a way to configure ldap proxy to get that behavior? Thanks in advance. -federico signature.asc Description: OpenPGP digital signature
Imap special-use with IOS 11
Hello, has anyone experiened any issues with IMAP SPECIAL-USE extension with ios11? After the update to ios11 the Ios mail client seems to not recognize anymore the imap special-use, so that system folders (Sent, Trash etc..) are not authomatically recognized and set during the configuration. Regards Federico
Re: Search problem
Hello, thank you for your suggestion, I can obtain just this from the backtrace: /[Thread debugging using libthread_db enabled]/ /Using host libthread_db library "/lib64/libthread_db.so.1"./ /Core was generated by `dovecot/imap'./ /Program terminated with signal 6, Aborted./ /#0 0x7f44637bb1f7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56/ /56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);/ What could we understand from this? -federico Il 09/05/2018 18:52, Reio Remma ha scritto: > On 09.05.2018 19:48, Federico Bartolucci wrote: >> Hello, >> >> when doing a simple search through the lucene indexes in some >> mailboxes (with actually many subfolders) the search terminates after >> a few seconds with no result and the dovecot log shows this error: >> >> Fatal: master: service(imap): child 15433 killed with signal 6 (core >> not dumped) >> >> >> Any clue about the reasons? the lucene indexes have been already >> rebuilt and look OK. > > Probably worth gathering more info by getting a full backtrace as per > instructions in: > > https://www.dovecot.org/bugreport.html > > Good luck, > Reio
Search problem
Hello, when doing a simple search through the lucene indexes in some mailboxes (with actually many subfolders) the search terminates after a few seconds with no result and the dovecot log shows this error: Fatal: master: service(imap): child 15433 killed with signal 6 (core not dumped) Any clue about the reasons? the lucene indexes have been already rebuilt and look OK. Regards -federico
Dovecot proxy
Hello, has someone already tested the dovecot-proxy with more than 10 nodes? or someone knows anyway if is it officially supported up to a certain number? Thanks.
Locks directory change
Hello, it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line: mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are there other things to change or to do or what could be the reason? (for instance to login in a specific way or doing a particular operation). Regards, Federico
