- dovecot - dovecot.org

User's mail encryption with mail-crypt-plugin
by André Rodier 26 Apr '20

26 Apr '20

Hello, I have a question about the "mail-crypt-plugin". If each user is having its own mail encryption key, is there a way to encrypt the key with the user password, and to decrypt it when the user logs in? I want to, if this is possible, to prevent any user, even root, to access another user's emails. Thanks, André

1 1

Creating folders
by Andrei Petru Mura 25 Apr '20

25 Apr '20

Hi, I managed to install dovecot 2.2.36 along postfix, with virtual users. When I send mails from my thunderbird client a Sent folder is created, which is mirrored on server by Maildir/cur/.Sent. If I try to create other directories the same thing happenes, adding to the created folder name . prefix. For example, created a_folder would be found on server under Maildir/cur/.b_dir. If I remove the client from thunderbird (with cached data) and reconfigure it, this folders are no longer available. How can I make them be available? Indication for right documentation pages is much appreciated. Thanks, Mura Andrei

2 5

error service quota-status
by Admin Beckspaced 25 Apr '20

25 Apr '20

dear dovecot users, trying to setup this quota-status thingy in dovecot so postfix can query the quota on the mailbox via following in main.cf smtpd_recipient_restrictions = ... check_policy_service inet:127.0.0.1:12340 I got this in my dovecot config service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } plugin { ... quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is over quota / Mailbox ist voll quota_status_success = DUNNO ... } but whenever I try I get this error: Apr 24 20:04:32 cx20 dovecot[7236]: quota-status(beckidouche(a)domain.com)<7290><qQpiJzAqo156HAAAct2Jzg>: Error: quota check failed: Failed to get quota resource STORAGE_BYTES for INBOX: quota-dict: dict_lookup(priv/quota/storage) failed: net_connect_unix(/var/run/dovecot/dict) failed: Permission denied (euid=303(vmail) egid=303(vmail) missing +r perm: /var/run/dovecot/dict, we're not in group 489(dovecot), dir owned by 0:0 mode=0755) (reply took 0.000 secs (0.000 in dict wait, 0.000 in other ioloops, 0.000 in locks)) what am I missing here? perhaps too many hours in front of the screen today already ;) thanks a lot for your time & help greetings Becki /* ==================================================================================================================================== */ cx20: # doveconf -n # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) # OS: Linux 4.12.14-lp151.28.48-default x86_64 ext4 # Hostname: cx20.domain.com auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 apop auth_verbose = yes auth_verbose_passwords = yes dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_uid = 300 mail_debug = yes mail_gid = vmail mail_home = /srv/maildirs/%d/%n mail_location = maildir:/srv/maildirs/%d/%n mail_plugins = " quota" mail_privileged_group = vmail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext 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 = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::quota quota_grace = 10%% quota_rule = *:bytes=102400000 quota_rule2 = Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is over quota / Mailbox ist voll quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { mode = 0777 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 10042 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } ssl_cert = </etc/dehydrated/certs/webmail.domain.com/fullchain.pem ssl_cipher_list = ALL:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { mail_plugins = " quota imap_quota" } /* ==================================================================================================================================== */

2 2

replication newbie: some beginner questions
by Stefan G. Weichinger 25 Apr '20

25 Apr '20

At a customer we run dovecot-2.3.10 along with postfix and mariadb, using postfixadmin as GUI. Now I plan to migrate to a new hardware (bigger machine) and in the same step to migrate from Gentoo Linux to Debian Linux. So I think about how to get the mailboxes from A to B. We use one UID afaik: mail_home = /home/vmail/%d/%u mail_location = maildir:~ I read about dsync and wonder: * does it make sense in this case to set up replication and let the servers replicate at first while still running on the old server? * do I have advantages over doing some rsync-jobs? * I somewhere read about not being able to sync sieve-scripts below the maildirs? We have: plugin { sieve = /home/vmail/%d/%u/sieve/.dovecot.sieve sieve_before = /etc/dovecot/sieve/global/default.sieve sieve_dir = /home/vmail/%d/%u/sieve/scripts/ sieve_extensions = +imapflags } * would the replication sync over all the existing mails/mailboxes or only the ones created *after* starting the replication? Stupid question maybe, but I just want to be sure before I screw up the installation. - sure, backups backups all the way ;-) thanks for any feedback on this! Stefan

5 13

IMAP ghost login
by Jos Chrispijn 25 Apr '20

25 Apr '20

Would it be possible to generate a user list that Dovecot permits to fetch mail from? Thanks, Joz

1 0

Dovecot Load balancing - Please Please Please help me
by Kishore Potnuru 24 Apr '20

24 Apr '20

I need your help on my issue very badly. I have the dovecot version 2.0.9 installed on RHEL linux 6.10 version. It's a single Live server. I need to add a load balancer by adding another server for resilience. I cannot upgrade the dovecot version at this time as it is a single live server. If something goes wrong, I will be in trouble. Basically the requirement/issue is: a) it's a single live dovecot POP3/IMAP server b) people are accessing their emails from microsoft outlook (by giving the same server name as IMAP and SMTP server). But more than 100000 emails will be travelled/routed. c) This server is not rebooted from couple of years. d) Now they are worried about, just in case if the server is having any issues during the reboot or if something goes wrong with the server in any case, there will be huge issues. e) They would like to create resilience by adding another server and emails will be travelled from both the servers. If one server is having any issues due to any technical issue and if it doesn't come back easily, then the emails will be travelled through the other server and there will no disturbance to the emails. atleast it travels from the other server. I have very less knowledge on this. Could you please help me providing the best solution for this. I will wait for your reply. Please please please help me. Thanks, Kishore Potnuru

4 8

Batching quota clone updates
by micah anderson 23 Apr '20

23 Apr '20

Hi, I like the quota count+clone configuration. However, I'm wondering if the cloning process could batch its updates into chunks, or spread them out over time? The clone updates happen whenever the quota is updated, typically this is fine, but when a tsunami of spam comes resulting in delivery to every user on the system, then can be quite overwhelming for a sql server to do an update for every user. Thanks! -- micah

1 0

Help with Shared Mailboxes
by Alan Stevens 23 Apr '20

23 Apr '20

dovecot version = 2.2..27 I have a running debian server ( jessie-backports ) supporting email for three different domains. It is working fine. My boss has asked me to look into using Shared folders/mailboxes - for instance, he wants selected users of Domain-A to be able to see the shared Inbox of the user "support" who is also in Domain-A. Sorry if my questions are basic, but here goes:- 1. Can I simply change the relevant dovecot configuration files and introduce Shared mailboxes into an already running system? Very basically, add the imap-acl plugin, the shared namespace, the dict file and restart dovecot? 2. If I can do this, would it wipe out the tens of thousands of existing emails I have on the system now? i.e. Does Sharing have to be introduced when new email server is being brought up? Can it be added on-the-fly to my working server? Would the emails in /var/mail/vmail/Domain-A/alan/mail seemlessly populate /var/mail/vmail/Domain-A/Shared/alan/mail after making such changes? 3. If adding the Sharing to my running system is possible, can I add it on only one of my three domains? I have a test domain with one user. My principle domain ( Domain-A ) has many users, and as I stated previously, very very many stored emails. Emails I absolutely cannot afford to lose. Any insights are appreciated. Alan Stevens ---||--- alanrstevens(a)yahoo.com https://www.linkedin.com/in/alanrstevens

1 0

Testing COI
by lists＠mlserv.org 23 Apr '20

23 Apr '20

Hi, I am playing around with the COI plugin and try to get things working. I followed the Dovecot docs and also got the source from Github (dovecot/coi). I have compiled and installed coi successfully. IMAP seems to be fine, but LMTP has some errors in the logs, so I removed imap_coi for the moment: Apr 23 17:05:16 mx dovecot: lmtp(10752): Fatal: Couldn't load required plugin /usr/lib64/dovecot/lib11_imap_coi_plugin.so: dlopen() failed: /usr/lib64/dovecot/lib11_imap_coi_plugin.so: undefined symbol: client_add_capability I am running Dovecot 2.3.10 and coi at the same version. Am I missing something here? Thanks in advance Christian -- Rößner-Network-Solutions Karl-Bröger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

2 2

Re-to-archived-thread: Dict issue with PostgreSQL for last_login plugin (duplicate key)
by lists＠mlserv.org 23 Apr '20

23 Apr '20

Hi, I have tried to implement last_login with PostgreSQL and I found an old thread from June 2019. I have found a simple solution that I want to share with you: I followed the instructions on how to set up a last_login on the official documentation. Therefor I creates a very simple table having userid and last_login fields. Added plugin and dict information. I received the duplicate key errors and I did this trick for now, which seems to solve this issue: CREATE OR REPLACE RULE insert_to_update AS ON INSERT TO users WHERE EXISTS (SELECT userid FROM users WHERE userid = NEW.userid) DO INSTEAD UPDATE users SET last_login = NEW.last_login WHERE userid = NEW.userid With this rule in place, INSERTs are changed to UPDATEs, if a userid entry already exists. No ned to patch code. Feel free to comment :-) Christian Thread online: https://www.dovecot.org/list/dovecot/2019-May/115921.html -- Rößner-Network-Solutions Karl-Bröger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

1 0

Recommendations on intrusion prevention/detection?
by Johannes Rohr 23 Apr '20

23 Apr '20

Dear all, what are the key strategies for intrusion prevention and detection with dovecot, apart from installing fail2ban? It is a pity that the IMAP protocol does not support 2 factor authentication, which seems to stop 90% of intrusion attempts in their tracks. Without it, if someone has obtained your password and reads your mail without modifying it, you will hardly ever notice. Is there a reasonable way of detecting and preventing logins from unusual IP ranges? Or are there other strategies you would recommend? Cheers, Johannes

10 13

Dovecot and thunderbird authentication issue?
by David Mehler 23 Apr '20

23 Apr '20

Hello, I'm using Dovecot 2.2, Postfix 3.5, and am atempting to get the latest version of Thunderbird to work. I tried account autoconfig which did not work, so I had to manually enter information and correct other information. On my server dovecot supports plane and login authentication methods but only over starttls i've got a letsencrypt certificate. My thunderbird configuration looks good, right hosts for incoming and outgoing mail, right ports, 143 starttls, and 587 smtp submission, and thunderbird has the authentication method set for normal password. This I interpreted to mean thunderbird is going to starttls then send the username and password. Thunderbird is giving me this error: imap server does not support the selected authentication method I realize this is vague, any suggestions? Thanks. Dave.

2 2

sieve question
by mj 23 Apr '20

23 Apr '20

Hi, We are trying to auto-reply to emails that still use one of our old domains. To do this, I have setup a catch-all mailbox for anything sent to that old domain using postfix virtual: @old.domain.com catch-all(a)new.domain.com Then I defined a sieve script for catch-all(a)new.domain.com, like: > require ["vacation"]; > if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe", "list-owner", "list-post", "list-archive", "list-id", "Mailing-List"] ) > > { vacation text: > This message is sent automatically, and your message has NOT been read nor forwarded. > > Please update your addressbooks! > > All the best! :-) > . > ; > } However, sieve never sends any auto-reply, because it logs: > discarding vacation response for implicitly delivered message; no > known (envelope) recipient address found in message headers > (recipient=<catch-all(a)new.domain.com>, and no additional `:addresses' > are specified) I have googled this, but adding :addresses in this case will not work, as we are trying to answer (basically) emails sent to any email addresses sent to that domain, and thus I cannot define specific :addresses Can anyone suggest what to do here? Thanks and stay healthy! MJ

5 11

Still interested in SMTPUTF8 support
by David Bürgin 22 Apr '20

22 Apr '20

I haven’t seen this term on the mailing list for a while. I don’t know if you’re tracking this somewhere, in any case I’m curious if you are still planning to add support for SMTPUTF8. Cheers,

2 1

Dovecot 2.3.10 fails to start due to missing dependency
by Jacob Shea 21 Apr '20

21 Apr '20

Greetings, I installed Dovecot 2.3.10 on my Centos 7.7.1908 server, however it fails startup. This is a fresh/default install, meaning all the configs are default, downloaded from the dovecot.repo. Here is my PasteBin: https://pastebin.com/376UQFLs ### Error Log, copied from Journalctl print out ### Apr 20 21:10:01 server101 systemd[1]: Started Session 955 of user root. Apr 20 21:10:01 server101 CROND[8057]: (root) CMD (/usr/lib64/sa/sa1 1 1) Apr 20 21:10:18 server101 polkitd[1293]: Registered Authentication Agent for unix-process:8065:44125203 (system bus name :1.2058 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/Polic Apr 20 21:10:18 server101 systemd[1]: Starting One-time Dovecot init service... Apr 20 21:10:18 server101 systemd[1]: dovecot-init.service: main process exited, code=exited, status=2/INVALIDARGUMENT Apr 20 21:10:18 server101 systemd[1]: Failed to start One-time Dovecot init service. Apr 20 21:10:18 server101 systemd[1]: Dependency failed for Dovecot IMAP/POP3 email server. Apr 20 21:10:18 server101 systemd[1]: Job dovecot.service/start failed with result 'dependency'. Apr 20 21:10:18 server101 systemd[1]: Unit dovecot-init.service entered failed state. Apr 20 21:10:18 server101 systemd[1]: dovecot-init.service failed. Apr 20 21:10:18 server101 polkitd[1293]: Unregistered Authentication Agent for unix-process:8065:44125203 (system bus name :1.2058, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8 lines 6106-6158/6158 (END) ### Linux Server Version ### [root@server101 log]# cat /etc/centos-release CentOS Linux release 7.7.1908 (Core) ### Dovecot Version ### Installed Packages Name : dovecot Arch : x86_64 Epoch : 2 Version : 2.3.10 Release : 2 Size : 15 M Repo : installed From repo : dovecot-2.3-latest Summary : Secure imap and pop3 server URL : http://www.dovecot.org/ License : MIT and LGPLv2 Description : Dovecot is an IMAP server for Linux/UNIX-like systems, written with security : primarily in mind. It also contains a small POP3 server. It supports mail : in either of maildir or mbox formats. : : The SQL drivers and authentication plug-ins are in their subpackages. ---- Any help or suggestions are appreciated. Sincerely, Jacob S.

2 4

Unicode in mail addresses
by Jasper Michalke 21 Apr '20

21 Apr '20

Dear Dovecot people, I have a question concering Unicode support: Does Dovecot support Unicode characters in both parts of the mail address? E.g. dфҿ@.tld Thank you for any reply, The one with the braid | Der mit dem Zopf

1 0

Doc pointer request
by David Favor 18 Apr '20

18 Apr '20

At one point seems like I found a write up in the Dovecot docs about having Dovecot directly listen on port 25 using Opportunistic TLS along with port 587 authentication, so only Dovecot was required to handle incoming email. Said another way, no requirement for Sendmail, or Postfix or EXIM. Just straight up Dovecot. If I'm remembering correctly, someone point me to the correct docs for this setup. Thanks!

4 4

setup sdbox per user with userdb
by Maciek Jackowski 18 Apr '20

18 Apr '20

Hi welcome I want to set some virtual users with sdbox mail_location so I return in password_query and user_query extra field mail which contains sdbox:/var/mail/example.com/user:INDEX=/var/mail_indexes/example.com/user:A… and then when i send email to user(a)example.com I see all sdbox dirs created but when i login with thunderbird IMAP - Maildir structure is always created with an empty INBOX I tried to override namespace inbox with mail AS "namespace/inbox/location" with content sdbox:/var/mail/example.com/user:INDEX=/var/mail_indexes/example.com/user:A… but nothin change what am I doing wrong? regards

2 1

Problems with compressed mail_attachment_dir
by Claudio Cuqui 17 Apr '20

17 Apr '20

Hi there ! I´m using dovecot 2.3.10 (manually compiled on Centos 8 x86_64 - fully updated), XFS filesystem, with mdbox and a separated compressed attachment directory: mail_attachment_fs = sis compress:lz4:6:posix mail_attachment_hash = %{sha256} mail_attachment_dir = /ATTACHMENTS I'm using dovecot LDA (for mail delivery). Everything works fine with the delivery and compression. The first test, I send one tar file with 7Mb. It was correctly compressed (2791959) and stored in mail_attachment_dir. But when I tried to access it via IMAP ( thunderbird/evolution) I got this message on dovecot logs: Error: Mailbox INBOX: UID=1: read(attachments-connector(zlib(/mailboxes/domain/h1/h2/test/mdbox/storage/m.1))) failed: read(/ATTACHMENTS/19/53/19536d7b190e5ba68337625a29e7b8a6129a2dfb5935eafa424ba4da2a878532-2e9c960b7dd2985e245e0000f484007a[base64:19 b/l]) failed: Stream is smaller than expected (2791959 < 7981633) (FETCH BODY[]) The 7981633 is the original attachment size. 2791959 is the compressed size (on attachment directory). I also see 2791959 in mail message size field (instead of 7981633 that is the original size BEFORE compression) in Thunderbird. In Evolution was not even possible to open the message. Thunderbird allow me even download the attachment, but the downloaded file is corrupted. Looks like dovecot is showing the properties of the compressed attachment instead of the proprerties of the original attachment (before compression). I'm also using imap_zlib and zlib plugins: plugin { zlib_save_level = 6 # 1..9; default is 6 zlib_save = lz4 # or bz2, xz, lz4 or zstd } protocol imap { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins imap_quota imap_zlib } # Space separated list of plugins to load for all services. Plugins specific to # IMAP, LDA, etc. are added to this list in their own .conf files. mail_plugins = quota fts fts_xapian mailbox_alias zlib This happens with every message that exceed mail_attachment_min_size (in my case, 32k) and is stored at mail_attachment_dir = /ATTACHMENTS When I comment: mail_attachment_dir = /ATTACHMENTS, everything works fine (compression included) with imap viewing on Thunderbird/Evolution. Please, let me know if you need further information or have any suggestions about this issue. TIA, Claudio

1 0

Headsup on feature removal
by Aki Tuomi 17 Apr '20

17 Apr '20

Hi! Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. We are starting to gradually remove some of these parts, which are unused, untested or deprecated. We will provide advance notification before removing anything. To start, the following features are likely to be removed in next few releases of Dovecot. - Authentication drivers: vpopmail, checkpassword, bsdauth, shadow, sia - Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5 - Authentication mechanisms: ntlm, rpa, skey - Dict drivers: memcached, memcached-ascii (use redis instead) - postfix postmap support - autocreate & autosubscribe plugins (use built-in auto=create/subscribe setting instead) - expire plugin (use built-in autoexpunge setting) - fts-squat plugin - mailbox alias plugin - mail-filter plugin - snarf plugin - xz compression algorithm For the authentication drivers that are being removed, we suggest using Lua as a replacement. See https://doc.dovecot.org/configuration_manual/authentication/lua_based_authe… For information about converting between password schemes, see https://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes If you are using any of these features, please start preparing for their removal in the near future. Features will begin to be dropped as of v2.3.11. Additionally, the mbox format will no longer receive new development. It will still be maintained, however its use beyond migrations and other limited use cases will be discouraged. Please contact us via the mailing list if you have any questions. Regards, Dovecot Team

15 23

Bug maybe already resolved? Sieve rule does not accept special use folder names
by Marc Roos 17 Apr '20

17 Apr '20

Sieve rule fileinto Spam fails, while fileinto Junk succeeds mailbox Spam { special_use = \Junk auto = no } dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64 dovecot-2.2.36-3.el7_7.1.x86_64 CentOS Linux release 7.7.1908 (Core

2 7

Dovecot Failed to initialize SSL server context
by Adam Raszkiewicz 17 Apr '20

17 Apr '20

I'm trying to configure TLS for Dovecot 2.3 but after setting all things up I'm not able to start Dovecot: Apr 16 20:56:02 master: Info: Dovecot v2.3.9.3 (9f41b88fa) starting up for imap, pop3, lmtp (core dumps disabled) Apr 16 20:56:25 auth: Debug: Loading modules from directory: /usr/lib/dovecot/auth Apr 16 20:56:25 auth: Debug: Module loaded: /usr/lib/dovecot/auth/lib20_auth_var_expand_crypt.so Apr 16 20:56:25 auth: Debug: Read auth token secret from /usr/var/run/dovecot/auth-token-secret.dat Apr 16 20:56:25 auth: Debug: auth client connected (pid=30750) Apr 16 20:56:25 imap-login: Error: Failed to initialize SSL server context: Can't load SSL private key: Key is for a different cert than ssl_cert: user=<>, rip=::1, lip=::1, secured, session=<JKh/qm6j/rMAAAAAAAAAAAAAAAAAAAAB> Apr 16 20:56:25 imap-login: Info: Disconnected: TLS initialization failed. (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<JKh/qm6j/rMAAAAAAAAAAAAAAAAAAAAB> Apr 16 20:57:47 master: Fatal: Dovecot is already running with PID 30727 (read from /usr/var/run/dovecot/master.pid) Apr 16 20:57:47 master: Warning: Killed with signal 15 (by pid=30823 uid=0 code=kill) I have created a brand new key pair, csr and the cert but still it complains to start. Any thoughts on that? Thanks, Adam

2 1

How to specify pattern for share folder using ACL vfile
by Adam Raszkiewicz 15 Apr '20

15 Apr '20

My `90-acl.conf` file looks like: plugin { #acl = vfile:/etc/dovecot/global-acls:cache_secs=300 #acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext acl = vfile } # To let users LIST mailboxes shared by other users, Dovecot needs a # shared mailbox dictionary. For example: plugin { #acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes acl_shared_dict = proxy::acl } When ACLs were set for particular mailbox I can see that dovecot-acl file were created but I have no idea how to specify a pattern for shared folder like is in the `dovecot-dict-sql.conf.ext` map { pattern = shared/shared-boxes/user/$to/$from table = user_shares value_field = dummy fields { from_user = $from to_user = $to } } My goal is to control how it appears on the client site. As for now is as `shared/user@domain/folder/` but I have no idea where it is defined. Thanks, Adam

1 0

Removal of metrics.dovecot.org
by Aki Tuomi 15 Apr '20

15 Apr '20

Hi! metrics.dovecot.org will be removed by end of April. It's not really used that much and it's not compatible with new style metrics. --- Aki Tuomi Open-Xchange oy

1 0

got a listener on 993
by David Mehler 15 Apr '20

15 Apr '20

Hello, Before I get in to my question is ssl on 993 or starttls on 143 better from a security perspective? I've noticed that I've got a dovecot listener on port 993, below is my doveconf -n output I don't have an imaps listener uncommented should I do so and set it's port to 0? Will that disable the 993 listener? Thanks. Dave. # 2.3.10 (0da0eff44): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: FreeBSD 12.1-RELEASE-p2 amd64 # Hostname: hostname.example.com auth_cache_size = 10 M auth_default_realm = example.com auth_mechanisms = plain login auth_realms = example.com dict { lastlogin = mysql:/usr/local/etc/dovecot/dovecot-last-login.conf } first_valid_gid = 2100 first_valid_uid = 2100 hostname = hostname.example.com imap_client_workarounds = delay-newhostname tb-extra-hostnamebox-sep tb-lsub-flags imap_idle_notify_interval = 1 mins last_valid_gid = 2100 last_valid_uid = 2100 lda_hostnamebox_autocreate = yes lda_hostnamebox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = xxx.xxx.xxx.xxx lmtp_rcpt_check_quota = yes log_timestamp = "%Y-%m-%d %H:%M:%S " hostname_access_groups = vhostname hostname_fsync = never hostname_gid = vhostname hostname_home = /var/vhostname/hostnameboxes/%d/%n hostname_location = dbox:~/hostname hostname_plugins = acl fts fts_lucene mail_log notify quota trash virtual welcome zlib mail_crypt hostname_privileged_group = vhostname hostname_server_admin = hostnameto:postmaster@example.com hostname_uid = vhostname managesieve_notify_capability = hostnameto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment hostnamebox date index ihave duplicate mime foreverypart extracttext spamtest spamtestplus virustest editheader imapflags notify imapsieve vnd.dovecot.imapsieve namespace { location = sdbox:/var/vhostname/public/:CONTROL=~/hostname/public:INDEX=~/hostname/public prefix = Public/ separator = / subscriptions = yes type = public } namespace { hidden = no list = yes location = hostnamedir:/var/vhostname/shared/office/.hostnamedir:CONTROL=~/.hostnamedir/control/office:INDEX=~/.hostnamedir/index/office prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = hostnamebox Drafts { auto = subscribe special_use = \Drafts } hostnamebox Sent { auto = subscribe special_use = \Sent } hostnamebox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } hostnamebox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 fts = lucene fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_exclude3 = \Spam fts_autoindex_max_recent_msgs = 80 fts_index_timeout = 90 fts_lucene = whitespace_chars=@. normalize no_snowball imapsieve_hostnamebox1_before = file:/var/vhostname/sieve/global/learn-spam.sieve imapsieve_hostnamebox1_causes = COPY imapsieve_hostnamebox1_name = Spam imapsieve_hostnamebox2_before = file:/var/vhostname/sieve/global/learn-ham.sieve imapsieve_hostnamebox2_causes = COPY imapsieve_hostnamebox2_from = Spam imapsieve_hostnamebox2_name = * last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it hostname_crypt_curve = prime256v1 hostname_crypt_global_private_key = # hidden, use -P to show it hostname_crypt_global_public_key = # hidden, use -P to show it hostname_crypt_save_version = 2 hostname_log_events = delete undelete expunge copy hostnamebox_delete hostnamebox_rename hostname_log_fields = uid box msgid size quota = count:User quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_rule2 = Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 hostnamebox is full quota_status_success = DUNNO quota_vsizes = true quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u quota_warning5 = storage=75%% quota-warning 75 %u sieve = file:/var/vhostname/sieve/%d/%n/scripts;active=/var/vhostname/sieve/%d/%n/active-script.sieve sieve_before = /var/vhostname/sieve/global/spam-global.sieve sieve_extensions = +notify +imapflags +spamtest +spamtestplus +virustest +editheader sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment sieve_max_redirects = 30 sieve_max_script_size = 1M sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_user_log = /var/vhostname/sieve/sieve_error.log sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected trash = /usr/local/etc/dovecot/trash.conf welcome_script = welcome %n postmaster@%d welcome_wait = yes } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve sendhostname_path = /usr/local/sbin/sendhostname service auth-worker { user = vhostname } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vhostname mode = 0666 user = vhostname } } service dict { unix_listener dict { mode = 0600 user = vhostname } user = root } service imap-login { inet_listener imap { port = 143 } process_min_avail = 1 } service imap { executable = imap } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 172.16.21.3 port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { group = vhostname mode = 0660 user = vhostname } user = vhostname } service stats { unix_listener stats-reader { group = vhostname mode = 0660 user = vhostname } unix_listener stats-writer { group = vhostname mode = 0660 user = vhostname } } service welcome { executable = script /usr/local/etc/dovecot/welcome.sh unix_listener welcome { user = vhostname } user = vhostname } ssl = required ssl_cert = </usr/local/etc/ssl/acme.sh/example.com/fullchain.crt ssl_cipher_list = EECDH+AESGCM:EDH+AESGCM ssl_curve_list = P-256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_options = no_ticket ssl_prefer_server_ciphers = yes userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { hostname_fsync = optimized hostname_plugins = acl fts fts_lucene hostname_log notify quota trash virtual welcome zlib hostname_crypt sieve } protocol lda { hostname_fsync = optimized hostname_plugins = acl fts fts_lucene hostname_log notify quota trash virtual welcome zlib hostname_crypt sieve } protocol imap { hostname_max_userip_connections = 20 hostname_plugins = acl fts fts_lucene hostname_log notify quota trash virtual welcome zlib hostname_crypt imap_acl imap_quota imap_sieve imap_zlib last_login quota welcome } protocol sieve { info_log_path = /var/log/dovecot/dovecot-sieve.log log_path = /var/log/dovecot/dovecot-sieve-errors.log }

6 6

replication_full_sync_interval
by Ivo 14 Apr '20

14 Apr '20

Default value for replication_full_sync_interval is 24 hours. How is it then possible to get doveadm replicator status results like this one username priority fast sync full sync success sync failed someuser none 24:23:39 24:23:39 24:23:37 - # doveconf -a | grep replication_full_sync_interval replication_full_sync_interval = 1 days # dovecot --version 2.2.33.2 (d6601f4ec)

2 2

Variable expansion in password field
by Simone Lazzaris 14 Apr '20

14 Apr '20

Hi list! I've recently updated a small dovecot cluster from 2.2.29 to 2.3.10. I've found an issue with variable expansion. My user/password database is on a mysql table, with password saved in plain text field. The cluster receives mail via lmpt and users fetch them via imap. On the 2.2.29 version, no issues. After the upgrade, I've found some lines in the log: Apr 14 14:36:05 archive-front1 dovecot: lmtp(19671, fakeusername(a)fakedomain.com) Error: lmtp-server: conn 212.183.164.212:34642 [4]: rcpt fakeusername(a)fakedomain.com: Failed to initialize user: Failed to expand plugin setting password = 'sd78F6aS9%Lggxf': Unknown variable '%g' (I've faked /some/ information for obvious reasons, but I've kept the password after the '%' sign). Apparently, dovecot 2.3.10 is trying to expand some variables IN the password field. I'm trying to fool him expanding the '%' into '%%' on the password query, but without luck... I can also contact the user and make him choose a different password, without '%'. Anyway, I feel that this behaviour should be seen as a bug. Am I missing something? -- Simone Lazzaris QCom SpA

2 1

%d ignored from auth-passwdfile.conf.ext configuration file
by Andrei Petru Mura 13 Apr '20

13 Apr '20

I try to configure dovecot with virtual users. I put my users file in folder /etc/dovecot/my_domain_name/users. My auth-passwdfile.conf.ext file looks like this: passdb { driver = passwd-file args = username_format=%n /etc/dovecot/%d/users } When I try to log in, I get this: dovecot: auth: Error: passwd-file(test,some.ip.addr.here,<rQT+ziijGE1tpoAB>): stat(/etc/dovecot//users) failed: No such file or directory As you can see, %d isn't interpreted. Why is this happening? Any hints? Thanks, Mura Andrei

2 3

Missing permissions
by Andrei Petru Mura 13 Apr '20

13 Apr '20

Hi, Dovecot version 2.2.36 In log files I get this error: dovecot: imap(test): Namespace '': mkdir(/home/mail/domain/test/Maildir) failed: Permission denied (euid=1005(vmail) egid=1005(vmail) missing +w perm: /home/mail/domain, UNIX perms appear ok (ACL/MAC wrong?)) My authentication configuration is this: passdb { driver = passwd-file args = username_format=%n /etc/dovecot/users } userdb { driver = static args = uid=vmail gid=vmail home=/home/mail/domain/%n username_format=%n /etc/dovecot/users } /home/mail/domain/test directory is owned by vmail user. How to fix this? Mura Andrei

4 12

doveadm backup from gmail with imapc
by Ben Mulvihill 11 Apr '20

11 Apr '20

I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted@expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - reconnecting (delay 0 ms) dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.109:993 (local 10.7.1.179:59052) dsync(ted): Error: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - disconnecting dsync(ted): Error: User initialization failed: imapc: Login to imap.gmail.com failed: Disconnected from serv I am using dovecot version 2.2.33.2 on ubuntu, with the configuration below. I have also enabled "allow access from unsecure apps" in my gmail settings. My first thought looking at the error messages was has that perhaps doveadm-backup was trying to connect with ssl3, which is no longer supported by gmail or anyone else nowadays. But apparently the ssl3_read_bytes function in openssl also handles tls, so the reference to ssl3 in the message is misleading, and the real problem must be elsewhere. If anyone can help me debug this I'd be grateful. Many thanks, Ben root@expectation:/etc/dovecot# doveconf -N # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-91-generic x86_64 Ubuntu 18.04.4 LTS auth_mechanisms = plain imapc_features = rfc822.size gmail-migration fetch-headers imapc_host = imap.gmail.com imapc_password = # hidden, use -P to show it imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no imapc_user = MY_GMAIL_ADDRESS mail_location = maildir:~/Maildir mail_prefetch_count = 20 mail_privileged_group = mail 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 name = } protocols = " imap" ssl = yes ssl_cert = </etc/dovecot/private/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 userdb { driver = passwd name = }

6 13

doveadm replicator command
by Ivo 09 Apr '20

09 Apr '20

Can someone please explain to me what do commands "doveadm replicator add" and "doveadm replicator remove" really do. According to https://wiki.dovecot.org/Tools/Doveadm/Replicator they "Add the specified user(s) to the replicator." and "Remove the specified user from replicator.". Do they really do that? Since the default list of users for replication comes from doveadm user '*' (https://wiki.dovecot.org/Replication) I tried removing one user (e.g. xyz) from replication by using "doveadm replicator remove xyz" and it didn't work. Namely, after entering that command the only thing that I noticed is that "doveadm replicator status xyz" does not return any information. BUT, as soon as one mail arrives for that user "doveadm replicator status xyz" displays valid information and mail is replicated. Thanks in advance for any reply. # dovecot --version 2.2.33.2 (d6601f4ec)

1 0

doveadm backup into IMAP folder
by Gionatan Danti 09 Apr '20

09 Apr '20

Hi all, I am migrating a number of account from an old domain to a new one. I would like to store all imported email from the old domain under a specific IMAP folder. For example, if having test(a)domain.old, I would like to import all old email to test(a)domain.new/fromold. While I succeeded using doveadm backup / dsync to successfully replicate the old mailbox to the new one, I am unable to store all imported mail under a specific folder. So, I have some questions: - can the above be done? - if yes, can you confirm that email outside the specific destination folder will not be touched/deleted/whatever by doveadm backup? - does a "dry-run" option exists for doveadm backup / dsync? Thank you all. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 1

alternatives for imapproxy
by Maciej Milaszewski 08 Apr '20

08 Apr '20

Hi System debian 8.11 and dovecot-2.2.36.4 My webmail is roundcube with imapproxy. I have one problem. My dovecot servers is are in a cluster with keepalived like: dovecot1----VIP-IP--------dovecot2 All works fine I have a problem with imapproxy when a server dovecot1 had a problem (kernel panic sic!) Keepalived works perfecty and moved VIP to dovecot2 - all works fine for normal users but imapproxy gave a timeout and webmail clinet cannot connect what do you recommend alternative to imapproxy ? I use imapproxy because is fast ...

2 2

Warning: Failed to do incremental sync
by Laura Smith 08 Apr '20

08 Apr '20

Setup dovecot sync along the lines of (https://wiki2.dovecot.org/Replication) I am doing one way replication. The initial full replication happened without issue, but now I'm seeing these errors on the slave server: doveadm: Warning: /data/mail/foo/bar/Maildir/dovecot-uidlist: Duplicate file entry at line 26397: 1562173159.M215923P17350.mxp,S=2290,W=2339 (uid 143128 -> 143142) Warning: Failed to do incremental sync for mailbox Sent Messages, retry with a full sync (Modseq 1766 no longer in transaction log (highest=17617, last_common_uid=17559, nextuid=17560)) Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 2540 no longer in transaction log (highest=13870, last_common_uid=19912, nextuid=19913)) I guess dovecot automatically tries a full replication because eventually the messages get pushed and "sync failed" status changes from 'y' to '-'

2 1

Dovecot "User-Agent" equivalent
by Plutocrat 08 Apr '20

08 Apr '20

Hi, I was trying to debug an IMAP connection problem. The client accesses an account via webmail, mobile phone, and desktop. I was wondering if there was a way of determining which of these they were using at a given time. My googling turned up the following settings in the imap{} section: protocol imap { imap_id_log = * imap_id_send = "name" * "version" * } ... but setting these didn't seem to log any more information that I could use. Have I misunderstood the usage of these settings? Shouldn't they log a "user agent" type information in /var/log/dovecot.log ? Or are there any other ways I can get information on the client? P.

1 0

\Noselect missing after deleting mailbox
by Onno Molenkamp 07 Apr '20

07 Apr '20

Hi, With mailbox_list_index enabled (which is the default), Dovecot won't return \Noselect when LISTing a mailbox that was deleted but still has subordinate mailboxes. Before creating such a mailbox in the first place, it does return \Noselect. 1 LIST "" Test 1 OK List completed (0.002 + 0.000 + 0.001 secs). 2 CREATE Test/Test 2 OK Create completed (0.014 + 0.000 + 0.014 secs). 3 LIST "" Test * LIST (\Noselect \HasChildren) "/" Test 3 OK List completed (0.001 + 0.000 secs). 4 CREATE Test 4 OK Create completed (0.006 + 0.000 + 0.005 secs). 5 LIST "" Test * LIST (\HasChildren) "/" Test 5 OK List completed (0.001 + 0.000 secs). 6 DELETE Test 6 OK Delete completed (0.011 + 0.000 + 0.011 secs). 7 LIST "" Test * LIST (\HasChildren) "/" Test 7 OK List completed (0.001 + 0.000 secs). Like response 3, response 7 should contain \Noselect. (and it does, when mailbox_list_index is disabled) It looks like Dovecot isn't updating dovecot.list.index properly when deleting such a mailbox. Forcing Dovecot to rebuild the index by deleting dovecot.list.index* will cause \Noselect to re-appear in responses. Onno

1 0

Query change mdbox_rotate_size & mdbox_rotate_interval after sometime
by Durga Prasad Malyala 06 Apr '20

06 Apr '20

Hello All, If I change the mdbox_rotate_size to 100 MB & mdbox_rotate_interval to say 3 days after a year of usage what would be the impact on existing mails and new mails? Thanks/DP

1 1

replication and spam removal ("doveadm expunge")
by Olaf Hopp 06 Apr '20

06 Apr '20

Hello everybody, since now I did no replication and spam is delivered into users folder "spambox" Every night there is a cronjob which deletes spam older than 30 days via something like "find .... -ctime +30 -delete" Now I'm going to set up replication (two way) and I thought that doing "rm" is not a good idea. So I modified the job to something like /usr/bin/doveadm expunge -u test1 mailbox INBOX.spambox BEFORE 30d which works like intended, but I see that on the replication partner the spam isn't deleted. Even if I do a doveadm force-resync -u test1 '*' or log in via imap to the replication partner I still see the old spam. So my question is: is this the intended behaviour and I have to run the "doveadm expunge" on both replication partners or should the deletion via "expunge" being replicated to the partner and I have a misconfiguration or maybe I hit a bug ? Regards, Olaf /etc/dovecot/conf.d/12-replication.conf: mail_plugins = $mail_plugins notify replication service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service doveadm { inet_listener { port = 1109 } } doveadm_password = XXXXX plugin { mail_replica = tcp:X.Y.Z.X:1109 } -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu www.atis.informatik.kit.edu www.kit.edu KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

2 4

net_connect_unix(imap) failed
by Philipp Ewald 06 Apr '20

06 Apr '20

Hello everyone, we have a huge problem with dovecot and IMAP connections. we got the following errors: 39665 today dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=29066, client-id=1755, rip=IP, created 562 msecs ago, received 0/4 bytes) we thinks this may be a problem with authorization take too long? Authorization is not local and with SQL. i found the following in source code of Dovecot: #define SOCKET_CONNECT_RETRY_MSECS 500 #define SOCKET_CONNECT_RETRY_WARNING_INTERVAL_SECS 2 [...] i_error("master(%s): %s (client-pid=%u, client-id=%u, rip=%s, created %u msecs ago, received %u/%zu bytes)", This is no process limit problem: ps auxf | grep -c "[d]ovecot/imap$" 688 ps auxf | grep -c "[d]ovecot/imap-login$" 100 cat /proc/`pidof dovecot`/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 64053 64053 processes Max open files 65535 65535 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 64053 64053 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us ulimit -n 1024 dovecot --version 2.3.4.1 (f79e8e7e4) protocols = imap pop3 service imap-login { process_min_avail = 4 service_count = 0 } service imap { process_limit = 4096 } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3 { process_limit = 4096 } Can someone explain why we got this error and how to fix? If you need another information please tell me. -- Philipp Ewald Administrator DigiOnline GmbH, Probsteigasse 15 - 19, 50670 Köln E-Mail: philipp.ewald(a)digionline.de Web: www.digionline.de, www.webweaver.de AG Köln HRB 27711, St.-Nr. 5215 5811 0640 Geschäftsführer: Werner Grafenhain Informationen zum Datenschutz: www.digionline.de/ds

2 2

Panic due to assertion failure
by Bert JW Regeer 06 Apr '20

06 Apr '20

Hey all, I continue to receive the following messages every so often: dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Panic: file mail-storage.c: line 2122 (mailbox_get_open_status): assertion failed: (box->opened) dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Fatal: master: service(imap): child 39982 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Even with core dumps enabled I haven't been able to get good information. I'm using FreeBSD and have installed dovecot from the pkg repositories dovecot-2.3.9.3 Is the package I have installed. (I just noticed there is an update available, so I'll upgrade, but this has been happening for a long time now, across multiple versions). What I was wondering, is there a way to rebuild all files that dovecot uses, indexes/caches/everything. Is there a doveadm command I can use for this? Bert JW Regeer

2 2

Disabling system users from mail
by Andrei Petru Mura 04 Apr '20

04 Apr '20

I'm using dovecot 2.2.36 on CentOS 7.7. My configurations are (dovecot -n): disable_plaintext_auth = no first_valid_uid = 1000 mail_location = maildir:~/Maildir mbox_write_locks = fcntl 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 = } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it I want to disable accounts for system users. Only virtual users will have accounts (not configured yet). Is this possible? Thanks, Mura Andrei

2 3

index problems after update
by Ajay Guleria 04 Apr '20

04 Apr '20

I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. Sometimes it happens, that dovecot stops showing new mail. There is no error in the log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/user (for some users only) emails are delivered again if I delete index-files from .imap folder. Ajay Guleria

1 0

Background operations
by Joan Moreau 03 Apr '20

03 Apr '20

Hello, Moving a large number of email from one folder to another does create timeout on roundcube, due to either a very very large number of emails or indexing process that increases the processing time. Would it make sense to have a background thread, to process orders asynchronously, instead of executing it on the spot ? For instance, orders (like moving or indexing or others) would be stored in a backlog instead of executing them in place, and then a background operation would process it ? Makes any sense ? Thank you

1 0

Sieve with links?
by ＠lbutlr 03 Apr '20

03 Apr '20

Is there any reason that a .active_sieve file would not load because it is a symbolic link? The target of the link is readable by the mail user, but instead of getting the trace for the .active_sieve file, I only get the trace for the default sieve file. -- 'Winners never talk about glorious victories. That's because they're the ones who see what the battlefield looks like afterwards. It's only the losers who have glorious victories.' --Small Gods

3 6

Disable Dovecot LDA
by Adam Raszkiewicz 02 Apr '20

02 Apr '20

Hi, Is there any way to disable Dovecot LDA? I want to always send email via postfix and relay server even it will be a local delivery within the Dovecot server Thanks, Adam

6 9

auth service stops responding
by Michael Redert 02 Apr '20

02 Apr '20

Hi all, I am running postfix with dovecot configured for local mail delivery. Everything works as expected for a while, but after successfully delivering ~250 mails, dovecot does not accept requests anymore and mails start queueing up in the postfix mailqueue. After restarting dovecot, another ~250 mails are processed and the problem occurs again. The server is running ubuntu 18.04 with dovecot 2.2.33.2 and postfix 3.3.0 installed. Users are stored locally in /etc/dovecot/users. Based on the log messages below and the output of netstat, it seems to me, that the auth service is not accepting any requests on the corresponding socket anymore. Any help is very much appreciated! Kind regards, Michael --- postfix error messages --- Mar 28 09:36:13 srv postfix/lmtp[3850]: 2423F7A21C: to=<system(a)mydomain.de>, relay=srv.mydomain.de[private/dovecot-lmtp], delay=155, delays=0.01/0/0/155, dsn=4.3.0, status=deferred (host srv.mydomain.de[private/dovecot-lmtp] said: 451 4.3.0 <system(a)mydomain.de>Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) Mar 28 09:38:48 srv postfix/lmtp[3850]: 45A0C7A2B5: to=<system(a)mydomain.de>, relay=srv.mydomain.de[private/dovecot-lmtp], delay=308, delays=0.01/153/0.02/155, dsn=4.3.0, status=deferred (host srv.mydomain.de[private/dovecot-lmtp] said: 451 4.3.0 <system(a)mydomain.de>Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) -- dovecot error messages --- Mar 28 09:36:13 lmtp(2631): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Request timed out Mar 28 09:36:14 lmtp(2623): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Request timed out Mar 28 09:38:48 lmtp(2631): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:38:49 lmtp(2623): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:41:23 lmtp(system(a)mydomain.de): Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:41:24 lmtp(system(a)mydomain.de): Error: userdb lookup(system(a)mydomain.de): Connecting timed out --- relevant netstat output when dovecot hangs ---- root@srv:~# netstat | grep dovecot | sort unix 2 [ ] STREAM CONNECTED 1449174 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTED 1449995 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 3 [ ] STREAM CONNECTED 1468180 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1468267 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1468271 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1469651 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1470606 /var/spool/postfix/private/dovecot-lmtp unix 3 [ ] STREAM CONNECTED 1470614 /var/spool/postfix/private/dovecot-lmtp unix 3 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 3 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb --- dovecot configuration ---- root@srv:~# dovecot -n # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider removing it from ssl_protocols. # OS: Linux 4.19.75-meson64 aarch64 Ubuntu 18.04.4 LTS auth_debug = yes auth_username_format = %n auth_verbose = yes debug_log_path = /var/log/dovecot-info.log default_client_limit = 16 default_process_limit = 32 first_valid_uid = 1000 hostname = mail.mydomain.de info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes listen = * lock_method = dotlock log_path = /var/log/dovecot.log mail_debug = yes mail_fsync = always mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mmap_disable = yes namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } postmaster_address = postmaster(a)mydomain.de protocols = " imap lmtp pop3" service replication-notify-fifo { name = aggregator } service { client_limit = 102 unix_listener { mode = 00 path = anvil-auth-penalty } name = anvil } service auth-worker { user = root name = auth-worker } service { client_limit = 160 name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service { executable = imap-login -R rawlogs inet_listener { port = 0 name = imap } service_count = 0 vsz_limit = 256 M name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service { process_limit = 8 name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service { unix_listener { group = postfix mode = 0660 user = postfix path = /var/spool/postfix/private/dovecot-lmtp } name = lmtp } service log-errors { name = log } service { inet_listener { port = 0 name = pop3 } inet_listener { port = 0 name = pop3s } name = pop3-login } service { process_limit = 4 name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl = required ssl_cert = </etc/ssl/certs/srv.mydomain.de.pem ssl_cipher_list = ALL:HIGH:!SSLv2:!MEDIUM:!LOW:!EXP:!RC4:!MD5:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 !TLSv1 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_ssl = yes protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol !indexer-worker { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol pop3 { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

1 0

"auth_cache_verify_password_with_worker = yes" does not work with proxy
by Theo Pannen 02 Apr '20

02 Apr '20

Hello, i use a proxy only configuration with version 2.2.22 (Ubuntu 16.04) and have now transferred it to version 2.3.10. This works as before. But as soon as i use "auth_cache_verify_password_with_worker = yes", it does not work anymore. The first login still works, but from the second one, where the answer comes from the cache, there is an error. The login is still accepted but dovecot searches the mailbox locally. The configuration for cache and proxy (from dovecot -n): auth_cache_verify_password_with_worker = yes auth_cache_negative_ttl = 0 auth_cache_size = 64 M passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } The sql from /etc/dovecot/dovecot-sql.conf.ext: password_query = SELECT pwdCrypt AS password, \ NULL AS nopassword, \ 'MyMasterUser' AS master, \ 'MyMasterPass' AS pass, \ ipv4address AS host, \ '%u' AS destuser, \ 'Y' AS proxy \ FROM mailbox \ WHERE user = '%u' AND activeFlg = '1' LIMIT 1 The logfile extracts with "auth_cache_verify_password_with_worker = yes": - First Login from mail.log (work's) Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=6fZiPkyiWHJSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=29272#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Performing passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): cache miss Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): Server accepted connection (fd=16) Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): Sending version handshake Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<1>: Handling PASSV request Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Performing passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): query: SELECT pwdCrypt AS password, NULL AS nopassword, 'MyMasterUser' AS master, 'MyMasterPass' AS pass, ipv4address AS host, 'testuser' AS destuser, 'Y' AS proxy FROM mailbox WHERE user = 'testuser' AND activeFlg = '1' LIMIT 1 Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Finished passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<1>: Finished Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Finished passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Auth request finished Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser#011master=MyMasterUser#011pass=<hidden>#011host=10.1.2.3#011destuser=testuser#011proxy Apr 2 12:27:11 mf-19 dovecot: imap-login: proxy(testuser): started proxying to 10.1.2.3:143 (master MyMasterUser): user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, TLS, session=<6fZiPkyiWHJSZMhl> - Further logins from mail.log (searches locally): Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=L4PQPkyi7plSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=39406#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Performing passdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): cache hit: <hidden>#011master=MyMasterUser#011pass=MyMasterPass#011host=10.1.2.3#011destuser=testuser#011proxy=Y Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): cache: validating password on worker Apr 2 12:27:18 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<2>: Handling PASSW request Apr 2 12:27:18 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<2>: Finished Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Finished passdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Auth request finished Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser Apr 2 12:27:18 mf-19 dovecot: auth: Debug: master in: REQUEST#011219414529#01118975#0111#011f78b3499f7157a5daf7eb2050cd79e60#011session_pid=18980#011request_auth_token Apr 2 12:27:18 mf-19 dovecot: auth: Debug: static(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Performing userdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: static(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Finished userdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: master userdb out: USER#011219414529#011testuser#011#011auth_mech=PLAIN#011auth_token=e6819f7eac20f6520440abd937322ff13618741f Apr 2 12:27:18 mf-19 dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, mpid=18980, TLS, session=<L4PQPkyi7plSZMhl> Apr 2 12:27:18 mf-19 dovecot: imap(testuser)<18980><L4PQPkyi7plSZMhl>: Debug: Added userdb setting: plugin/=yes Because it is pure proxy there is no userdb configuration and no local user. mail.err therefore contains the error message: Apr 2 12:27:18 mf-19 dovecot: imap(testuser)<18980><L4PQPkyi7plSZMhl>: Error: Couldn't drop privileges: User is missing UID (see mail_uid setting) - Further logins without "auth_cache_verify_password_with_worker = yes" works as expected: Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=9cvDTkyi7XxSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=31981#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Performing passdb lookup Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): cache hit: <hidden>#011master=MyMasterUser#011pass=MyMasterPass#011host=10.1.2.3#011destuser=testuser#011proxy=Y Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Finished passdb lookup Apr 2 12:31:46 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Auth request finished Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser#011master=MyMasterUser#011pass=<hidden>#011host=10.1.2.3#011destuser=testuser#011proxy Apr 2 12:31:46 mf-19 dovecot: imap-login: proxy(testuser): started proxying to 10.1.2.3:143 (master MyMasterUser): user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, TLS, session=<9cvDTkyi7XxSZMhl> Apr 2 12:32:37 mf-19 dovecot: auth-worker(19036): Debug: conn unix:auth-worker (pid=19032,uid=109): Disconnected: Connection closed (fd=-1) Did I forget something in the configuration or is this a bug? Thanks Theo

1 0

[Dovecot] Postfixadmin/MySQL/Dovecot 2 and quota
by Matt 01 Apr '20

01 Apr '20

Hi all, I'm setting up a new email server based on the softwares list below: * Postfix * Dovecot 2.0.9 * MySQL * Postfixadmin 2.3.6 My current problem is I'm unsure whether quota feature is well configured or not. In order to test and validate, I use Roundcubemail GUI which provides percentage of the space used by the mailbox (quota should be applied per mailbox). Here, my dovecot configuration: dovecot.conf: dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } dovecot-dict-quota.conf: connect = host=localhost dbname=postfix user=postfix password=postfix map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } dovecot-sql.conf.ext: driver = mysql connect = host=localhost dbname=postfix user=postfix password=postfix default_pass_scheme = PLAIN-MD5 password_query = SELECT username AS user, password, \ CONCAT('*:storage=', CAST(quota AS CHAR), 'b') AS quota_rule \ FROM mailbox WHERE username = '%u' AND active='1' user_query = SELECT maildir, 89 AS uid, 12 AS gid, \ concat('dict:storage=',floor(quota/1000),'::proxy::quotadict') AS quota, \ CONCAT('*:storage=', CAST(quota AS CHAR), 'b') AS quota_rule \ FROM mailbox WHERE username = '%u' AND active='1' conf.d/90-quota.conf: plugin { quota = dict:user::proxy::quotadict quota_rule2 = Trash:storage=+10%% } conf.d/20-imap.conf: protocol imap { mail_plugins = $mail_plugins imap_quota } When I check postfixadmin GUI, I can see that quota in realtime in quota2 table, no problem. But Roundcubemail cannot get this information and shows a unknown quota. If I add this line: quota_rule = *:storage=1G in conf.d/90-quota.conf file, it works, I mean roundcubemail gets and shows information (but not the one stored in db of course). I think I'm close to the right configuration but I need your help to complete this setup. Thank you in advance for your help. Best, Matt

7 20

sieve compile error
by Johannes Rohr 01 Apr '20

01 Apr '20

Dear all, I try to recompile my learn_ham.sieve script, which fails with the message root@ida:/etc/dovecot# sievec sieve-scripts/report-ham.sieve report-ham: line 1: error: require command: unknown Sieve capability `vnd.dovecot.pipe'.report-ham: line 1: error: require command: unknown Sieve capability `imapsieve'.report-ham: line 19: error: unknown command 'pipe' (only reported once at first occurrence).report-ham: error: validation failed.sievec(root): Fatal: failed to compile sieve script 'sieve-scripts/report-ham.sieve' Yes, in conf.d/20-imap.conf, imapsieve and vnd.dovecot.pipe are explicitly enabled: protocol imap { mail_plugins = $mail_plugins imap_sieve imap_acl mail_max_userip_connections = 50 plugin {sieve_plugins = sieve_imapsieve sieve_extprograms # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/sieve-scripts/report-ham.sieve#sieve_pipe_bin_dir = /etc/dovecot/sieve-scriptssieve_global_extensions = +vnd.dovecot.execute +vnd.dovecot.pipe }} I am obviously overlooking something here, but what? Any hints will be greatly appreciated! Johannes

2 2

Re: limit for user exceeded
by Maciej Milaszewski 31 Mar '20

31 Mar '20

Hi I Dont understand or I im thinking wrong: process_limit = 25000 Older: #fs.inotify.max_user_watches= 8192 #fs.inotify.max_user_instances = 16384 New: fs.inotify.max_user_instances = 8192 fs.inotify.max_user_watches= process_limit x 2 + fs.inotify.max_user_instances fs.inotify.max_user_watches= 58192 On 31.03.2020 13:44, Aki Tuomi wrote: > I would prefer replies on the list... =) > > no. the idea is to *increase* the *current* value of fs.inotify.max_user_watches and fs.inotify.max_user_instances with 50000 > > fs.inotify.max_user_watches = 8192 + 50000 = 58192 > > Aki > >> On 31/03/2020 14:21 Maciej Milaszewski <maciej.milaszewski(a)iq.pl> wrote: >> >> >> Hi >> How I understood it correctly >> >> service imap { >> process_limit = 25000 >> } >> >> fs.inotify.max_user_watches= 50000 >> fs.inotify.max_user_instances = 50000 >> >> ? >> >> >> On 31.03.2020 12:14, Aki Tuomi wrote: >>> Sorry, ment that we *increase* the current value with twice the process limit for IMAP. >>> >>> Aki >>> >>>> On 31/03/2020 13:12 Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: >>>> >>>> >>>> We usually set them to twice the number of process_limit for imap. >>>> >>>> Aki >>>> >>>>> On 31/03/2020 12:29 Maciej Milaszewski <maciej.milaszewski(a)iq.pl> wrote: >>>>> >>>>> >>>>> Hi >>>>> System debian 8.11 dovecot-2.2.36.4 and I have some warnings in log likes: >>>>> >>>>> Warning: Inotify watch limit for user exceeded, disabling. Increase >>>>> /proc/sys/fs/inotify/max_user_watches >>>>> >>>>> >>>>> cat /proc/sys/fs/inotify/max_user_watches >>>>> 8192 >>>>> >>>>> in sysctl i change >>>>> >>>>> #fs.inotify.max_user_watches= 8192 >>>>> #fs.inotify.max_user_instances = 16384 >>>>> >>>>> fs.inotify.max_user_watches= 16384 >>>>> fs.inotify.max_user_instances = 24576 >>>>> >>>>> One questions - should these values be equal?

1 0