- dovecot - dovecot.org

Re: Dovecot 2.2.25 compiling error
by Joseph Tam 12 Jul '16

12 Jul '16

>> I've reduced the problem to this: >> >> void foo(int X[static 20]); >> >> will compile but if you remove "X", it won't. > > The change was to replace "int" with "unsigned char" in the above test > program, and the test started failing then in CentOS 5's gcc. I'd > expect the same to happen for you also. No, it will fail with both "int" and "unsigned char" without the dummy argument "X", and works for both if one is inserted. I don't know why -- perhaps a bug with my version of gcc. Joseph Tam <jtam.home(a)gmail.com>

1 1

dovecot master password without "auth_master_user_separator"
by Miguel C 12 Jul '16

12 Jul '16

Looking at the doc its sugest we can either use auth_master_user_separator to login with a master user (i.e user(a)email.com*master and the master password defined in a file or db) I'm able to use this method with a password file and works just fine, however we need to sync some imap users to another destrination that does not allow us to use this format in the "email address source" (shame) But the doc also sugests if I don't use this flag I should be able to just use the same login used in the SASL mecahnisms which is not working (testing with plain text ). Is there anything more to this? I have tried to add a username to the password file with the same master password but still doens't work :| What am I missing? Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer*

1 0

Feature Request
by Doug Hardie 12 Jul '16

12 Jul '16

I would like to request an additional optional argument for queue-id to dovecot-lda. The intended use for this argument is to include in the logging. From what I can tell, the queue-id size is not consistent between the various MTAs and so would need to be allocated dynamically when read during initialization. This element in the log messages would make it easier to find the trace of a received email. Generally I can easily get the queue-id generated by postfix (or sendmail - I use both). One grep would then give me the whole picture rather than having to dig out the message-id and doing a secondary grep to obtain the lda log messages. — Doug I find it interesting that every submission to this list results in a quick response that says moderation is required since I "am not a member". However, I am a member...

2 1

is it possible to run a post-login script in a dovecot proxy with local auth?
by Luca Lesinigo 12 Jul '16

12 Jul '16

We’re using dovecot v2.2.22, authenticating on a local database (passdb with sql driver), and then proxying the connections to the backend server returned by passdb (proxy=y and backend in “host” column). To support some legacy clients we should keep POP/IMAP-before-SMTP running for some time, but right know I don’t know how to hook up a successful authentication in the dovecot proxy. I did read from http://wiki2.dovecot.org/PostLoginScripting: “...it's not currently possible to run post-login scripts in proxies, because they're not actually logging in to the local Dovecot” Does that also holds true even if the proxy is authenticating users locally before proxying them? Failing that, any idea on how to get successful logins, other than parsing the log file? thank you, -- Luca Lesinigo

2 1

Re: Dovecot 2.2.25 compiling error
by Joseph Tam 12 Jul '16

12 Jul '16

Aki Tuomi wrote: >>> Well, tried with or without patches, but got still same error: >>> >>> sha1.h:80: error: static or type qualifiers in abstract declarator >> >> For what it's worth, I get the same error compiling on Solaris 10. >> It may be because I have a rather old gcc (3.4.4). Editing out >> the "static" keyword from config.h allowed it to finish the compile. > > It still happened even with > https://github.com/dovecot/core/commit/d9c865ce774aae9f2f17b89e7e94c3cfca29… > > You need to rerun autotools on this before it can do anything. I don't grok autotools, but I don't think this will solve the problem. If I understand the patch correctly, it modifies the small program used by configure to test a C99 feature. Manually compiling the small test program (with and without the changes made by the patch) will result in a successful compile, but if you compile sha1.h (line 80,81), it will fail. I've reduced the problem to this: void foo(int X[static 20]); will compile but if you remove "X", it won't. Joseph Tam <jtam.home(a)gmail.com>

2 1

a question about dovecot-sieve
by 刘莹莹 11 Jul '16

11 Jul '16

question discribe: example: > vim .dovecot.sieve require ["fileinto"]; # rule:[filter1] if anyof (header :contains "Subject" "测试邮件") { fileinto "sieve"; } when i write a mail ,give subject "这是一封测试邮件" , then server convert this subject to " SUBJECT: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=B8=80=E5=B0=81=E6=B5=8B=E8=AF=95=E9=82=AE?= =?UTF-8?Q?=E4=BB=B6?= " the essential question is when the mail go through dovecot-sieve plugin, the sieve plugin get mail subject is "这是一封测试邮件" not "这是一封测试邮件"，there is a extra space added(which as segmentation between "=?UTF-8?Q?"). SIMPLY SAY：edit subject"这是一封测试邮件" ——>server convert "SUBJECT: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=B8=80=E5=B0=81=E6=B5=8B=E8=AF=95=E9=82=AE?= =?UTF-8?Q?=E4=BB=B6?="——>sieve plugin get "这是一封测试邮件" The result is filter failure. is this a bug ? How can I avoid it？ thanks

2 1

"anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid"
by Ralf Hildebrandt 11 Jul '16

11 Jul '16

I updated to 2.3.0 today, and now I'm getting these entries in my log: Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:21 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17654 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:23 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid lmtp on the other seems to be working ok -- I'm not seeing any mails queueing up... Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Connect from local Jul 7 14:28:01 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Disconnect from local: Successful quit -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

4 3

Raw backtrace multiple passwords not allowed
by Leon Kyneur 10 Jul '16

10 Jul '16

Hi Recently enabled support for encrypted passwords on my proxies - CRAM-MD5, DIGEST-MD5, NTLM and APOP to support some new users. Most users are working perfectly though every so often I see this happening in the logs: Jul 09 06:32:51 auth: Error: ldap(user(a)domain.com,192.168.10.90,<mOWiFi431eDKOsBS>): Multiple password values not supported Jul 09 06:32:51 auth: Panic: file passdb-ldap.c: line 99 (ldap_lookup_finish): assertion failed: (password == NULL || scheme != NULL) Jul 09 06:32:51 auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x86aae) [0x7ff4db08faae] -> /usr/lib64/dovecot/libdovecot.so.0(+0x86b8e) [0x7ff4db08fb8e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff4db033b5d] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(+0x720b) [0x7ff4d967a20b] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(+0x5e2f) [0x7ff4d9678e2f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7ff4db0a338c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0x7ff4db0a47ef] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7ff4db0a3415] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7ff4db0a35c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff4db03a033] -> dovecot/auth [13 wait, 1 passdb, 0 userdb](main+0x39c) [0x7ff4db5454ac] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff4da61fb15] -> dovecot/auth [13 wait, 1 passdb, 0 userdb](+0xf6a1) [0x7ff4db5456a1] Jul 09 06:32:51 imap-login: Warning: Auth connection closed with 1 pending requests (max 0 secs, pid=8759, EOF) Jul 09 06:32:51 imap-login: Warning: Auth connection closed with 1 pending requests (max 1 secs, pid=8764, EOF) Password debug shows: Jul 09 06:38:25 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<xSSOKi438ODKOsBS>): Credentials: 4b616e6761733138 Jul 09 06:38:27 auth: Debug: client passdb out: FAIL 2541 user=user(a)domain.com pass=NotPassword original_user=user Jul 09 06:38:37 auth: Debug: passwd-file(tassiedevil,192.168.10.90,<weQKKy438eDKOsBS>): username changed user -> user(a)domain.com Jul 09 06:38:37 auth: Debug: passwd-file(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): Allowing any password Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): pass search: base=o=domains,dc=mail,dc=com scope=subtree filter=(&(objectClass=mail)(status=active)(|(|(mail=user@domain.com)(&(uid=user@domain.com)))(&(enabledService=shadowaddress)(shadowAddress user(a)domain.com)))) fields=mail,userPlaintextPassword,userPlaintextPassword,mailstoreHost Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): result: mail=user(a)domain.com userPlaintextPassword=NotPassword; mail,userPlaintextPassword unused Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): result: mail=user(a)domain.com userPlaintextPassword=NotPassword; mailstoreHost missing Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): PLAIN( Jenni) != 'NotPassword' Jul 09 06:38:39 auth: Debug: client passdb out: FAIL 2826 user=user(a)domain.com original_user=user This particular user has a space in their password.. some other users do not when seeing this error. I run multiple passdb and config is: passdb { args = /etc/dovecot/dovecot-ldap-proxy-alias.conf.ext default_fields = nopassword=y password= driver = ldap result_failure = continue-fail result_internalfail = continue-fail result_success = continue-ok } passdb { args = scheme=plain username_format=%l@%d /etc/dovecot/passwd.domains default_fields = nopassword=y password= driver = passwd-file result_success = continue-fail } passdb { args = /etc/dovecot/dovecot-ldap-proxy.conf.ext driver = ldap } LDAP passdb specifies 'PLAIN' as default_pass_scheme. [root@S605 dovecot]# dovecot --version 2.2.24 (a82c823) Any ideas what's going on here?

2 3

Dovecot threading implementation
by Gabriele Bulfon 08 Jul '16

08 Jul '16

Hi, I was trying to compare avrious thread refs/references implementation, both server side and client side. While testing dovecot, it looks to me that issuing thread=references or thread=refs I get the same response, while the refs drafts says it should reverse the date ordering inside a branch. Is this correct? Does Dovecot implements references and refs with same sorting? Also, cyrus has subject grouping included in references (which is bad!). What's dovecot doing in references alg? Thanks for any help, Gabriele ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

1 0

Re: Dovecot 2.2.25 compiling error
by Joseph Tam 08 Jul '16

08 Jul '16

> Well, tried with or without patches, but got still same error: > > sha1.h:80: error: static or type qualifiers in abstract declarator For what it's worth, I get the same error compiling on Solaris 10. It may be because I have a rather old gcc (3.4.4). Editing out the "static" keyword from config.h allowed it to finish the compile. Joseph Tam <jtam.home(a)gmail.com>

2 1