- dovecot - dovecot.org

Virtual POP3 namespaces and quota-status
by Aurélien Beaujean 09 Jan '17

09 Jan '17

Hi, I've tried to do configure Virtual POP3 INBOX (dovecot version 2.2.18) as explained here http://wiki.dovecot.org/Plugins/Virtual with a static userdb and nopassword=y so I dont have any database on the dovecot server without the possibility to distinguish POP3 or IMAP in the userdb extra field to change the namespace on the fly. So I've put the namespace virtual informations inside the protocol pop3 { ... }, I did the same for the protocol imap { }: protocol pop3 { mail_plugins = $mail_plugins last_login virtual namespace inbox { prefix = separator = / list = yes } namespace virtual { inbox = yes prefix = virtual/ separator = / location = virtual:/etc/dovecot/virtual:INDEX=MEMORY list = no hidden = yes } namespace real { prefix = RealMails/ separator = / list = no hidden = yes } } protocol imap { mail_plugins = $mail_plugins imap_quota last_login namespace inbox { inbox = yes } } protocol lda { mail_plugins = " quota sieve" namespace inbox { inbox = yes } } passdb { args = nopassword=y uid=vmail gid=vmail home=/var/mail/%2Mn/%2.2Mn/%n driver = static } userdb { args = nopassword=y uid=vmail gid=vmail home=/var/mail/%2Mn/%2.2Mn/%n driver = static } service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } process_min_avail = 8 } But the service quota-status getting lost with a message: namespace configuration error: inbox=yes namespace missing I didn't find a way to tell quota-status which namespace to use as you can't setup a default one. If I declare a "global" namespace inbox pop3 deamon fails because of duplicated namespace inbox in the configuration files: pop3(xxx): Error: User initialization failed: namespace configuration error: There can be only one namespace with inbox=yes Any idea before I will patch some piece of code to disable the unique restriction of inbox namespace ? Thanks, -- Auré

1 2

dsync for subscription on public/shared folder
by Mike Fröhner 09 Jan '17

09 Jan '17

Hello, I already wrote regarding that, but maybe it sounded too complex. I will write it a bit softer now. The replication through dsnyc works perfectly with one exception. I am having an issue with the replication of the subscriptions file on shared folder. We have a public mailbox defined: namespace public-test { location = maildir:/opt/mail/_public/test prefix = public/test/ separator = / subscriptions = no type = public } There 2 subfolder .Test1 and .Test2 which I would like to subscribe on my user "ldaptestuser" which is part of the group "ldaptestgroup" The dovecot-acl file on /opt/mail/_public/test and /opt/mail/_public/test/.Test{1,2} are the same and are containing: group=ldaptestgroup lrwstipekxa Now if I login through my client (Thunderbird or Roundcubemail) I can see the following debug log: dovecot: imap(ldaptestuser): Debug: acl: acl username = ldaptestuser dovecot: imap(ldaptestuser): Debug: acl: owner = 0 dovecot: imap(ldaptestuser): Debug: acl: group added: domain users dovecot: imap(ldaptestuser): Debug: acl: group added: ldaptestgroup dovecot: imap(ldaptestuser): Debug: acl: group added: all_mailuser I created one new private folder on the mailbox of my test user and also subscribed it. This subscription is successfully replicated. After that I am trying to subscribe the public folder. I can see the folder in my client after I subscribed them. But on the 2nd dovecot server the subscription file is not updated. imap-1 # cat subscription Private1 public/test/Test1 imap-2 # cat subscription Private1 The debug log on both dovecot server tells me: dovecot: doveadm(<ip>,ldaptestuser): Debug: Effective uid=834603987, gid=991, home=/opt/mail/ldaptestuser dovecot: doveadm(<ip>,ldaptestuser): Debug: acl: No acl_shared_dict setting - shared mailbox listing is disabled dovecot: doveadm(<ip>,ldaptestuser): Debug: maildir++: root=/opt/mail/_public/test, index=, indexpvt=, control=, inbox=, alt= dovecot: doveadm(<ip>,ldaptestuser): Debug: acl: initializing backend with data: vfile dovecot: doveadm(<ip>,ldaptestuser): Debug: acl: acl username = ldaptestuser dovecot: doveadm(<ip>,ldaptestuser): Debug: acl: owner = 0 dovecot: doveadm(<ip>,ldaptestuser): Debug: acl vfile: Global ACLs disabled It looks like the doveadm() cannot find the group or is not checking/initalizing the groups. Anybody any idea if I missconfigured something or is this just a bug? I really would appreciate some help. kind regards, Mike;

1 1

Auth-policy: auth_policy_server_url and https support
by gregc＠olypensupport.com 08 Jan '17

08 Jan '17

When using Auth policy server it doesn’t currently doesn’t support https. In version 2.2.27: Policy server HTTP error: 9002 Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) and in version 2.3.devel Policy server HTTP error: 9002 Requested https connection, but no SSL settings given dovecot.conf does have “ssl_client_ca_dir = /etc/ssl/certs” set. Looking around the source, http-client-settings are not given the ssl_ca_dir or ssl_ca_file setting from the config. Admittedly SSL tear up/down is little expensive per auth, but I think it maybe it should still work?

2 1

.dovecot.sieve location issue
by Jibeji 08 Jan '17

08 Jan '17

Hello, I am trying to set sieve up on a Centos 7 server. It's a configuration with postfix, Maildir, MySQL and virtual domains which works fine. I have created a simple .dovecot.sieve in the user's directory: # cat /home/mail/domain.com/user/.dovecot.sieve require "fileinto"; redirect "other_address(a)other_domain.com"; Here are the logs: dovecot: lda(user(a)domain.com): Debug: sieve: Pigeonhole version 0.4.2 initializing lda(user(a)domain.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. dovecot: lda(user(a)domain.com): Debug: sieve: script file /home/mail/ domain.com/.dovecot.sieve not found dovecot: lda(user(a)domain.com): Debug: sieve: user's script ~/.dovecot.sieve doesn't exist (trying default script location instead) lda(user(a)domain.com): Debug: sieve: no default script configured for user lda(user(a)domain.com): Debug: sieve: user has no valid location for a personal script lda(user(a)domain.com): Debug: sieve: no scripts to execute: reverting to default delivery. dovecot: lda(user(a)domain.com): msgid=<005b01d269ca$f287ebf0$d797c3d0$@fr>: saved mail to INBOX It tells that user's script ~/.dovecot.sieve doesn't exis However, on the troubleshooting guide, I can see these logs: dovecot: lda(hendrik): Debug: sieve: using sieve path for user's script: /home/hendrik/.dovecot.sieve dovecot: lda(hendrik): Debug: sieve: opening script /home/hendrik/.dovecot.sieve As you can see, it refers to "lda(hendrik)" but not "lda(user(a)domain.com" I am wondering whether Sieve looks for the file elsewhere than /home/mail/ domain.com/user/.dovecot.sieve Do you have any idea?

3 3

Dovecot Selinux Setting
by Günther J. Niederwimmer 08 Jan '17

08 Jan '17

Hello, can any tell me the correct selinux Settings for the Maildir Setting ? in the Moment I have this setting Jan 8 15:04:52 2017 from 192.168.100.100 [root@mx03 ~]# ls -Z /srv/vmail drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example.com drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example.at drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 eu-example.at drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example1.com -rw-rw----. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 shared- mailboxes I mean this not correct, I have problems with sieve to enable the Link and with Sync ? I can't found the correct setting with goo..... Thanks for Help and a answer, -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer

2 1

auth: Error: BUG: Authentication client sent unknown handshake command
by Marcus Endberg 08 Jan '17

08 Jan '17

Hello! I run dovecot for many years now, but today it ran into a bug I've never seen before. Searching the archives, this bug seems to occur very seldom. The current server installation & configuration is running since mid 2015, uptime of the server today is more than two months. It is a virtual machine in a data center, debian 7 / reiserfs, 'dovecot -n' output below. Just within normal operation, suddenly my users could no longer check their IMAP accounts, log shows lots of entries like this: ----------------------- /var/log/mail.log excerpt --------------------- 2017-01-08 08:15:23 dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?3484549121?11364?1?74fa603b892f9a262605ae6c2ce1d9a1 2017-01-08 08:15:23 dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext 2017-01-08 08:15:23 dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=11364 client-id=1) 2017-01-08 08:15:23 dovecot: imap-login: Internal login failure (pid=11364 id=1) (internal failure, 1 succesful auths): user=<USER_NAME>, method=PLAIN, rip=<USER_IP>, lip=85.214.143.57, mpid=11368, TLS, session=<0oiwA5BFmQBQhoL1> ----------------------------------------------------------------------- Strangely, sending mails still worked fine (postfix uses dovecot SASL authentification). I could not find any hint what might have caused the error in any logfile. After restarting dovecot everything is back to normal operation. Is there any other information I can / should provide? Thanks for your efforts, Marcus ----------------------- output of 'dovecot -n' ------------------------ # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.41-042stab120.16 i686 Debian 7.11 mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </correct_path_to/mailbox.endberg.net-chain.cert ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_key = </home/sslcerts/keys/mailbox.endberg.net.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } -----------------------------------------------------------------------

1 0

OP/PSA: Net Systems Research mail port diddlers
by lists＠lazygranch.com 07 Jan '17

07 Jan '17

http://netsystemsresearch.com/ dovecot.log.1.bz2:Jan 05 17:28:15 pop3-login: Info: Disconnected (no auth attempts in 3 secs): user=<>, rip=169.54.233.124, lip=MYIP, TLS handshaking: Disconnected, session=<z/L0OVxFetOpNul8> Their "research" pokes your email ports. Block if you want or participate in the (cough cough) research. IP addresses and opt-out email address on webpage.

2 1

Dovecot dsync tcps sends incomplete certificate chain
by Juri 06 Jan '17

06 Jan '17

Hi, I'm trying to configure a Dovecot dsync service between two servers, using a tcp+ssl connection and a valid Let's Encrypt certificate. I followed the guide on the wiki (http://wiki.dovecot.org/Replication) using the tcps method, but when I launch the replication it fails writing on the log (/var/log/mail.err): (Server 1 - sync "client" )| Error: sync: Disconnected from remote: Received invalid SSL certificate: unable to get local issuer certificate: /CN=mail.dividebyzero.it (Server 2 - sync "server")| Error: doveadm client disconnected before handshake: <no error> If I try to connect to the server using openssl s_client, on the port 993 (imaps) the server correctly sends the full chain: $ openssl s_client -connect server1.fqdn:993 CONNECTED(00000003) depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify return:1 depth=0 CN = mail.dividebyzero.it verify return:1 --- Certificate chain 0 s:/CN=mail.dividebyzero.it i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 i:/O=Digital Signature Trust Co./CN=DST Root CA X3 ... while on the doveadm port it fails: $ openssl s_client -connect server1.fqdn:7557 CONNECTED(00000003) depth=0 CN = mail.dividebyzero.it verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 CN = mail.dividebyzero.it verify error:num=21:unable to verify the first certificate verify return:1 --- Certificate chain 0 s:/CN=mail.dividebyzero.it i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ... I run Dovecot 2.2.13 on Debian 8.6: $ dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_default_realm = dividebyzero.it auth_mechanisms = plain login doveadm_password = (redacted) doveadm_port = 7557 mail_location = maildir:~/Maildir mail_plugins = " notify replication" namespace inbox { (removed) } passdb { driver = pam } passdb { args = username_format=%n /etc/vmail/%d/passwd driver = passwd-file } plugin { mail_replica = tcps:otherserver.fqdn } protocols = " imap lmtp" service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } unix_listener auth-userdb { user = vmail } } service doveadm { inet_listener { port = 7557 ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.dividebyzero.it/fullchain.pem ssl_client_ca_file = /etc/letsencrypt/live/mail.dividebyzero.it/chain.pem ssl_key = </etc/letsencrypt/live/mail.dividebyzero.it/privkey.pem userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/var/local/vmail/%d/%n driver = static } Is it a known problem, or has it been resolved in a subsequent version? If it is not, can you suggest me a workaround in the meantime? Thank you.

3 5

IMAP proxy for Exchange - encrypted backend Communication?
by tom 06 Jan '17

06 Jan '17

Hello, I try to setup a IMAP proxy for my old Exchange server. Running Dovecot v2.x on Centos 7. So far I follow http://wiki2.dovecot.org/HowTo/ImapcProxy and it seem to work. The only but major thing is with this setup - the communication between proxy and backend is not encrypted. :( To fix this, I changed the config and add: imapc_ssl=imaps imapc_port=993 but it doesnt work, because of verify failure of the self signed backend certificate: Jan 5 21:48:55 imap dovecot: imap(user1): Error: imapc(192.168.1.1:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Jan 5 21:48:55 imap dovecot: imap(user1): Error: imapc(192.168.1.1:993): No SSL context Jan 5 21:48:55 imap dovecot: imap(user1): Error: imapc: Command failed: Disconnected from server Jan 5 21:48:55 imap dovecot: imap(user1): Error: user tkoenig: Initialization failed: Initializing mail storage from mail_location setting failed: Mailbox list driver imapc: Failed to access imapc backend Jan 5 21:48:55 imap dovecot: imap(user1): Error: Invalid user settings. Refer to server log for more information. I didnt found anything in the documentation which tells dovcot not verify the backend certificate. Is there a know way to get it runing? Many thanks for any hint! regrds, Tom

3 2

dovecot-pigeonhole running external script ends with signal 11
by Tobi 06 Jan '17

06 Jan '17

Hi, I'm running a dovecot 2.2.26 (self compiled) on a Centos 7. I have a sieve script which should run an external script (in filter mode) that encrypts the mail using the users pub key. I configured 90-plugin.conf as follows plugin { sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.filter sieve_filter_bin_dir = /etc/dovecot/sieve-filters sieve_filter_exec_timeout = 10000 } The script is named SCRIPT and is called in my sieve script require "vnd.dovecot.filter"; if blabla { filter "SCRIPT" ["me(a)example.com"]; } the script returns the encrypted mail. I can call this SCRIPT without any error manually on the console as dovecot user (vmail). Also sieve-test "says" that the script called sucessfully su vmail sieve-test -e -t - -Tlevel=commands -r me(a)example.com -l /home/vmail/example.com/me/.Maildir /home/vmail/example.com/me/.dovecot.sieve /tmp/test.mail ... 23: filter action 23: execute program `SCRIPT' 23: executed program successfully 23: changed message ... info: msgid=<B5OEuIEvrCZzcoJ7A6fCF-ka2Nwz-Ze2UCO840Panvw.w7zr1vruaJMbDBwK63natps3v__yOgbhHy3ntACTU0s@redacted>: stored mail into mailbox 'INBOX'. sieve-test(vmail): Info: final result: success and I get the encrpted message in my mailbox. Just when it's called upon delivery via lmtp the script ends with signal 11 Jan 3 15:59:48 mbox2 dovecot: lmtp(me(a)example.com): Error: program `/etc/dovecot/sieve-filters/SCRIPT' terminated abnormally, signal 11 And in ~/.dovecot.sieve.log I can find the following .dovecot: line 23: error: filter action: failed to execute to program `SCRIPT': refer to server log for more information. [2017-01-03 15:59:48]. I have no idea why the manual call runs perfect and the call from sieve file ends up in this error. Does anyone have an idea how I could narrow down the source of this error? Or even better how to fix it? :-) Thanks for any answer tobi

4 8

dovecot.index.pvt view is inconsistent: error messages for public mailbox folder
by Andreas Ntaflos 04 Jan '17

04 Jan '17

Hi list, running Dovecot 2.2.27 on Ubuntu 14.04. A public mailbox "Public/Spam-Learning" in a public namespace with per-user "Seen" flags is configured like this: namespace pub { hidden = no inbox = no list = children location = maildir:/var/vmail/public:INDEXPVT=~/Maildir/public prefix = Public/ separator = / subscriptions = no type = public mailbox "Spam-Learning" { auto = subscribe } } The log files are full of error messages like these (got about 15000 in the last three days): 2017-01-03T11:19:28.242386+01:00 mailserver01 dovecot: imap(foo.bar(a)example.org): Error: /var/vmail/example.org/foo.bar/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:19:28.248524+01:00 mailserver01 dovecot: imap(foo.bar(a)example.org): Error: /var/vmail/example.org/foo.bar/Maildir/public/.Spam-Learning/dovecot.index.pvt view is inconsistent 2017-01-03T11:23:50.209732+01:00 mailserver01 dovecot: imap(baz.quux(a)example.org): Error: /var/vmail/example.org/baz.quux/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:23:50.775940+01:00 mailserver01 dovecot: imap(some.user(a)example.org): Error: /var/vmail/example.org/some.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:25:38.419536+01:00 mailserver01 dovecot: imap(other.user(a)example.org): Error: /var/vmail/example.org/other.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:34:14.351346+01:00 mailserver01 dovecot: imap(more.user(a)example.org): Error: /var/vmail/example.org/more.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent 2017-01-03T11:41:37.488916+01:00 mailserver01 dovecot: imap(support.user(a)example.org): Error: /var/vmail/example.org/support.user/Maildir/public/.Spam-Learning/dovecot.index.pvt reset, view is now inconsistent This problem did not seem to manifest itself in Dovecot 2.2.25, we see it only after upgrading to 2.2.27. I am not sure what the effects are. It seems that messages moved to the Public/Spam-Learning folder are deleted after a short while (not by the sa-learn cron job, which runs every morning) but I currently cannot say if this is because a user deletes them explicitly or because Dovecot does something it shouldn't. So this observation is possibly not relevant. It also doesn't seem to matter what kind of IMAP client access the Spam-Learning folder. Our users use Thunderbird, Apple Mail, Outlook, Roundcube, Horde and various mobile clients as well. I have attached the output of doveconf -n for reference. What could be the issue here? Are we doing something wrong or is this a bug in Dovecot? Thanks! Andreas

1 0

expunging all mailboxes
by Michael Fox 03 Jan '17

03 Jan '17

Evidently, the 'doveadm expunge' command requires a "mailbox" to be defined in the search string. But is there a way tell it all mailboxes for a user? For example, something like: doveadm expunge -u user@domain mailbox ALL savedbefore 30d Thanks, Michael

4 10

two listeners with different "driver = " configs
by mj 03 Jan '17

03 Jan '17

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver = ldap" and imap2/144 with "driver = pam" Just to explain why i would like this: I am using pam-script-saml (https://github.com/ck-ws/pam-script-saml) to enable saml-based access to dovecot. I would like to have one listener 144 to only serve this saml authentication listener, and the regular 143 listener with driver = ldap. Is that config possible? Best regards, MJ

5 10

differential SETACL silently fails if no vfile exists
by Vincent Breitmoser 02 Jan '17

02 Jan '17

In version 2.2.13, with `acl = vfile`, setting a differential ACL permission doesn't work if there are no permissions set yet. Example IMAP log: b1 GETACL test * ACL test valodim lrwstipekxacd b1 OK Getacl completed. b2 SETACL test valodim -l b2 OK Setacl complete. b3 GETACL test * ACL test valodim lrwstipekxacd b3 OK Getacl completed. My expectation was that the file would be created with default permissions, and the requested change then applied. However, no acl permission is set and no vfile is created for this mailbox in the process. This does work as expected (and a file is created) if I set a non-differential ACL first: b4 SETACL test valodim lrwstipekxacd b4 OK Setacl complete. b5 GETACL test * ACL test valodim akxeilprwtscd b5 OK Getacl completed. b6 SETACL test valodim -l b6 OK Setacl complete. b7 GETACL test * ACL test valodim akxeiprwtscd b7 OK Getacl completed. - V

1 0

dovecot and sssd
by Günther J. Niederwimmer 02 Jan '17

02 Jan '17

Hello, is there a way to configure dovecot over sssd ? like driver = sss Thanks for a answer, -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer

2 1

Re: FreeBSD / dovecot 2.2.27 / libwrap
by Jim Pazarena 30 Dec '16

30 Dec '16

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena <dovecot(a)paz.bz> wrote: > >> I have compiled dovecot2 for FreeBSD with the tcpwrap option. >> >> A tcpwrap binary gets built and resides in the FreeBSD directory >> /usr/local/libexec/dovecot >> >> an examination of the compiled options (using the FreeBSD pkg install >> dovecot2) confirms: LIBWRAP : on >> >> yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap >> >> I get the following logged error message: >> >> 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file >> or directory >> >> Is there any way to turn up some super logging so that I can find just >> what dovecot feels is the failure ? >> >> Or, does anyone have an idea how to figure this out? What little hair I >> have is rapidly getting pulled out in frustration! >> >> Thank you. >> >> >> >> -- >> Jim Pazarena dovecot(a)paz.bz >> > > -- Jim Pazarena dovecot(a)paz.bz

2 1

FreeBSD / dovecot 2.2.27 / libwrap
by Jim Pazarena 30 Dec '16

30 Dec '16

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file or directory Is there any way to turn up some super logging so that I can find just what dovecot feels is the failure ? Or, does anyone have an idea how to figure this out? What little hair I have is rapidly getting pulled out in frustration! Thank you. -- Jim Pazarena dovecot(a)paz.bz

2 1

doveadm expunge -A Error: Dictionary commit failed
by Alessio Cecchi 29 Dec '16

29 Dec '16

Hi, with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run “doveadm expunge -A mailbox Spam savedbefore 30d” dovecot an error: doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) doveadm: Error: expire: Dictionary commit failed Probably also "doveadm quota recalc -A" fail. Everything worked fine up to version 2.2.24 I hope can be fixed. Thanks -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice

3 6

dovecot-ldap.conf.ext for FreeIPA usage
by Matt . 29 Dec '16

29 Dec '16

Hello, I'm figuring out how to auth users against FreeIPA and I wonder if someone did this without GSAPI. My users are stored in a mysql DB where I wonder what I shall use as authname, the username or the mailaddress. As the mailaddress is always unique it could be best but if a user has multiple mailaddresses under seperate domains username might be better. Any clue here and maybe an example for dovecot-ldap.conf.ext when using FreeIPA ? Thanks! Matt

2 1

IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused
by Michael Grimm 28 Dec '16

28 Dec '16

Hi — I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } | local> host remote.test: remote.test has IPv6 address fd00:b::1 working well. Currently: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = * } } | local> host remote.test: remote.test has address 10.2.0.1 remote.test has IPv6 address fd00:b::1 Now, Replication stops and throws an error like: | <mail.crit> local.test dovecot: doveadm(user): Fatal: connect(fd00:b::1:12345) failed: Connection refused If I either #) remove IPv6 from my lokal DNS, #) use "mail_replica = tcp:10.2.0.1", or #) define the appropriate IPv4 address of remote.test in /etc/hosts, then replication works as usual. Hmm, shouldn't doveadm be more persistent in using every IP address of that entry of mail_replica *before* throwing a "Fatal:" error? Or do I miss something, and it's a feature, instead? Regards, Michael

1 0

Versioning Problem
by Günther J. Niederwimmer 28 Dec '16

28 Dec '16

Hello List, I have installed dovecot 2.2.25 on three Systems with two I have a problem with doveadm / dsync ? first: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) second: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) But I have this Error in the Logs ? Dec 27 12:00:12 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) Dec 27 12:01:08 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) can any tell me why ? -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer

1 0

Identify if a message_part is an attachment ?
by Sai Kiran Gummaraj 27 Dec '16

27 Dec '16

Hello, This is my first post to this group. I have read through the instructions before posting. I hope am doing the right thing. If not my sincere apologies. I am in the process of developing a dovecot IMAP plugin (over v2.2.25). The plugin works with mdbox/sdbox which has ability to keep attachments as external references (via SiS POSIX). The plugin must enable fetching attachment from REDIS instead of local-store. To accomplish this I was following dovecot via my debugger. I wanted to understand if there was a way to determine a message_part to be of an attachment type ? Thanks. -- Regards, Sai Kiran cmd_fetch() |_ imap_fetch_more() |_ imap_fetch_more_int() |_ imap_fetch_state *state = &ctx->state; state->cur_mail is NULL. search mailbox |_ mailbox_search_next(state->search_ctx, &state->cur_mail) |_ mailbox_search_next_nonblock (via vfunc) |_ index_storage_search_next_nonblock |_ search_more_with_prefetching(ctx, mail_r) |_ mail = index_search_get_mail(ctx) |_ allocates mail (vfunc mail_alloc) and calls hook. |_ also allocates index_mails ret = search_more_with_mail(ctx, mail); |_ call handler (*h) => fetch_body_msgpart |_ imap_msgpart_open |_ imap_msgpart_find_part(mail, msgpart, &part); /* only mail comes here */ mail (uid=1739, seq=5) msgpart (section_number = 2, fetch_type = FETCH_MIME_BODY, partial_offset = 0, partial_size = 512, decode_cte_to_binary = 0) |_ mail_get_parts(mail, &parts) /* atmail send msgpart */ |_ call to p->v.get_parts(mail, parts_r) (index_mail_get_parts) /* atmail over-ride this function */ |_ get_cached_parts(mail) /* sets data->part */ |_ get_unserialized_parts(index_mail) |_ get_serialized_parts(mail, &part_buf) |_ index_mail_cache_lookup_field |_ mail_cache_lookup_field |_ imap_msgpart_open_normal() |_ .. see call stack below ..

2 1

permissions and doveadm
by dovecot 26 Dec '16

26 Dec '16

I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm fails. I went from an self-compiled source, to 'repsitory'-version (from version 2.1.6, to 2.2.13) luuk@opensuse:~/bin> id uid=1000(luuk) gid=100(users) groups=100(users),7(lp),33(video),118(vboxusers) luuk@opensuse:~/bin> doveadm quota recalc luuk@opensuse:~/bin> doveadm quota recalc -u luuk doveadm(luuk): Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection refused doveadm(luuk): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. Why is it that with the '-u' option, doveadm is getting a connection refused? -- Luuk

4 4

postlogin script - still confused
by Michael Fox 26 Dec '16

26 Dec '16

> You need to use executable = script-login -- /path/post-login.sh -a -r -g > note the double-dash. it tells getopt to stop processing arguments. > > Aki OK. Thanks. So let me make sure I have this right, since there is no syntax defined on the wiki - just an example which doesn't show the above syntax. The valid possibilities are: executable = script-login [-d] /path/script1 /path/script2 ... -or- executable = script-login [-d] -- /path/script1 -a -r -g -s In other words, I can either call multiple scripts, each with no arguments, or I can call one script with arguments. But I cannot call multiple scripts, some with arguments, some without arguments. Is that correct? If not, please show all valid syntax options. Also, regarding the exec "$@" line shown at the end of the wiki examples. If I pass arguments "-a -r -g -s" to my script, as in: executable = script-login -- /path/script1 -a -r -g -s then doesn't the exec "$@" line at the end become: exec -a -r -g -s And surely that's not right. So, could you please explain in words the purpose of the exec line at the end - what it does, why it's needed, and what to do if I'm sending arguments to my postlogin script? Thanks, Michael

1 0

Domains on different IPs
by Mark Constable 23 Dec '16

23 Dec '16

I want to supply separate Letsencrypt certificates for each virtual domain and seeing that SNI does not work I need to allocate separate IPs. Could anyone give some pointers, or keywords to search for, on... a) how to make dovecot listen for different domains on different IPs? b) how to configure separate SSL certs for each of these IPs?

3 2