- dovecot - dovecot.org

RE: dovecot disk space settings
by Marc Roos 22 Oct '19

22 Oct '19

Ok, what about placing a dummy file of 5GB or so on the partition, that you can remove when necessary? -----Original Message----- Subject: Re: dovecot disk space settings >> I don't want to restrict each mailbox size. It's just to prevent > running out space completely. > > Why? (If I may ask) > > To provide mailboxes with unlimited space. And to make it easier to administrate. My question is about an emergency option if someone has forgotten to migrate to new hardware. It's possible but a bit harder if the partition is out of space and there is no free byte left. Best, Marcel

4 3

dovecot.conf from problem installation
by Steve Matzura 22 Oct '19

22 Oct '19

*** dovecot.conf *** ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Enable installed protocols !include_try /usr/share/dovecot/protocols.d/*.protocol # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Name of this instance. In multi-instance setup doveadm and other commands # can use -i <instance_name> to select which instance is used (an alternative # to -c <config_path>). The instance name is also added to Dovecot processes # in ps output. #instance_name = dovecot # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = # Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do # proxying. This isn't necessary normally, but may be useful if the destination # IP is e.g. a load balancer's IP. #auth_proxy_self = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf log_path = /var/log/dovecot.log passdb { driver = static args = noauthenticate temp_user=%u user=%Ln } passdb { driver = pam } passdb { driver = static args = noautenticate user=%{passdb:temp_user} skip = unauthenticated } *** End *** If I try to start the daemon, or even attempt 'dovecot -n output', I get: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 107: Expecting '{' Line 107 is where the first passdb block begins. If I remove the three passdb blocks--everything below line 106--I get a clean startup, but the log looks like this: *** Begin *** Oct 22 12:22:04 auth-worker(13722): Info: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: redacted) Oct 22 12:22:06 auth: Debug: client passdb out: FAIL 1 user=yourvoice(a)theglobalvoice.info Oct 22 12:22:06 auth: Debug: client in: AUTH 2 PLAIN service=imap secured session=BXn+2H6VKelsKTkL lip=95.142.174.193 rip=108.41.57.11 lport=993 rport=59689 local_name=mail.theglobalvoice.info resp=AHlvdXJ2b2ljZUB0aGVnbG9iYWx2b2ljZS5pbmZvAFRoJEJvYTQxMFlu (previous base64 data may contain sensitive data) Oct 22 12:22:10 auth-worker(13722): Debug: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): lookup service=dovecot Oct 22 12:22:10 auth-worker(13722): Debug: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): #1/1 style=1 msg=Password: Oct 22 12:22:12 auth-worker(13722): Info: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: redacted) Oct 22 12:22:14 auth: Debug: client passdb out: FAIL 2 user=yourvoice(a)theglobalvoice.info Oct 22 12:22:14 imap-login: Debug: SSL alert: close notify [108.41.57.11] Oct 22 12:22:14 imap-login: Debug: SSL alert: close notify [108.41.57.11] Oct 22 12:22:14 imap-login: Info: Disconnected (auth failed, 2 attempts in 12 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<BXn+2H6VKelsKTkL>

1 0

dovecot disk space settings
by marcel bendler 22 Oct '19

22 Oct '19

Hi, is there an option to leave some disk space free? Let's say, don't store new mails if the storage mount point has less than 1% free disk space. What's the way to go? I don't want to restrict each mailbox size. It's just to prevent running out space completely. Thanks! Best regards, Marcel

4 3

More on problems with new install
by Steve Matzura 22 Oct '19

22 Oct '19

Sorry for having lost the original chain of this problem. It's been a very long day. New output from 'dovecot -n output', including the contents of dovecot.conf, conf.d/10-master.conf, conf.d/10-mail.conf and conf.d/10-ssl.conf: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4 auth_debug = yes auth_debug_passwords = yes first_valid_gid = 109 first_valid_uid = 105 last_valid_gid = 109 last_valid_uid = 105 log_path = /var/log/dovecot.log mail_debug = yes mail_gid = postfix mail_location = maildir:/var/mail/vmail/%d/%n mail_uid = postfix 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 lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 0 service_count = 1 } service lmtp { unix_listener lmtp { mode = 0666 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 1024 } ssl = required ssl_cert = </etc/ssl/private/tgv2018.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes The two key files are where it says they are, although the hidden one isn't shown, it's there and properly owned and permissioned. Here's the only thing from tailing the log: Oct 22 07:24:50 master: Info: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap, lmtp (core dumps disabled) This may help - from a message delivery failure email: *** Begin *** Message Delivery Failure This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed permanently: * rock(a)theglobalvoice.info Reason: There was an error while attempting to deliver your message with [Subject: "Testing again"] to rock(a)theglobalvoice.info. MTA p3plsmtpa11-09.prod.phx3.secureserver.net received this response from the destination host IP - 95.142.174.193 - 550 , 550 5.1.1 <rock(a)theglobalvoice.info>: Recipient address rejected: User unknown in local recipient table . Reporting-MTA: dns; p3plsmtpa11-09.prod.phx3.secureserver.net [68.178.252.101] Received-From-MTA: dns; [192.168.1.140] [108.41.57.11] Arrival-Date: Mon, 21 Oct 2019 23:39:25 -0700 Final-recipient: rfc822; rock(a)theglobalvoice.info Diagnostic-Code: smtp; 550 5.1.1 <rock(a)theglobalvoice.info>: Recipient address rejected: User unknown in local recipient table Last-attempt-Date: Tue, 22 Oct 2019 00:23:38 -0700 Received: from [192.168.1.140] ([108.41.57.11]) by :SMTPAUTH: with ESMTPSA id MnpFiaSdxUnHgMnpFiYE6m; Mon, 21 Oct 2019 23:39:25 -0700 To: rock(a)theglobalvoice.info From: Steve Matzura <number6(a)noisynotes.com> Subject: Testing again Message-ID: <61b4f0c2-89fa-c4de-8288-871a8708f2d0(a)noisynotes.com> Date: Tue, 22 Oct 2019 02:39:26 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CMAE-Envelope: MS4wfC8H5kkZhXB1zicGDqvcQlC1Tl3lMTOcElvh0Efz70YGRgQalgb4N6/9XVLjnqOVd5XtxwgTWuvuCEhwp/JZ2oHrdLkl4d7unSyOefbSkgcd/M5tlQn5 m+FMjUC5HJopO89WJXHQNp0ruK6VmVwHwxMAn0YDVu4FQQqVIUkN6KVyOfdC/TYD6t6vxOqv2OUxKQ== Subject: Testing again From: Steve Matzura <number6(a)noisynotes.com> Date: 10/22/2019, 2:39 AM To: rock(a)theglobalvoice.info Let's see what happens now. *** End *** There is no user 'rock', it's just a Postfix mailbox.

2 6

Problems with new installation
by Steve Matzura 22 Oct '19

22 Oct '19

I had Dovecot running very well on Ubuntu 14.04. Then I decided that since That version of Ubuntu was now out of support, I would build a new server on 18.04, which has been done. I thought I could take the old dovecot.conf and everything in conf.d that had been customized and drop it in place, and everything would just work. That has proven not to be correct. The files that had been edited were the main /etc/dovecot/dovecot.conf, and in conf.d, 10-master.conf, 10-ssl.conf, and 10-mail.conf. I have restored the original package-supplied versions of these files and restarted Dovecot, but still no one can connect. Here's my configuration, with the version number at the top: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS auth_debug = yes auth_debug_passwords = yes mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u 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 } protocols = " imap lmtp" userdb { driver = passwd } verbose_ssl = yes The edits that were made to the aforementioned files were not actually done by me, so I can't explain why certain choices were made, except for obvious ones such as SSL key paths. But I figured the system should work at least on a vanilla configuration. Postfix is also involved in this, so the problems may not at all be with Dovecot, but with Postfix. I think I just need to draw the line between them and be able to know definitely that at least one half of the system is functioning correctly so I know I can mark that part as working, and proceed with debugging the other. My bet at this point is that it's not a Dovecot problem, but I'm not clear on how to determine this, with or without my changed files. Thanks in advance.

2 1

Dovecot v2.3.8 released
by Aki Tuomi 20 Oct '19

20 Oct '19

https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig Binary packages in https://repo.dovecot.org/ Changes + Added mail_delivery_started and mail_delivery_finished events, see https://doc.dovecot.org/admin_manual/list_of_events/ for details. + dsync-replication: Don't replicate users who have "noreplicate" extra field in userdb. + doveadm service status: Show total number of processes created. + When logging to syslog, use instance_name setting's value for the ident. This commonly is added as a log prefix. + Base64 encoding/decoding code was rewritten with additional features. It shouldn't cause any user visible changes. - v2.3.7 regression: If a folder only receives new mails without any other mail access, dovecot.index.log keeps growing forever and dovecot.index keeps being rewritten for every mail delivery. - dsync-replication may lose keywords after syncing mails restored from another replica. This only happened if the mail only had keywords and no system flags. - event filters: Non-textual event fields could not be filtered using wildcards. - auth: Scope parameter was missing from OAuth password grant request. - doveadm client-server communication may hang in some situations. It is also using unnecessarily small TCP/IP packet sizes. - doveadm who and kick did not flush protocol output correctly. - imap: SETMETADATA with literal value would delete the metadata value instead of updating it. - imap: When client issues FETCH PREVIEW (LAZY=FUZZY) command, the caching decisions should be updated so that newly saved mails will have the preview cached. - With mail_nfs_index=yes and/or mail_nfs_storage=yes setuid/setgid permission bits in some files may have become dropped with some NFS servers. Changed NFS flushing to now use chmod() instead of chown(). - quota: warnings did not work if quota root was noenforcing - acl: Global ACL file ignored the last line if it didn't end with LF. - doveadm stats dump: With JSON formatter output numbers using the number type instead of as strings - lmtp_proxy: Ensure that real_* variables are correctly set when using lmtp_proxy. - event exporter: http-post driver had hardcoded timeout and did not support DNS lookups or TLS connections. - auth: Fix user iteration to work with userdb passwd with glibc v2.28. - auth: auth service can crash if auth-policy JSON response is invalid or returned too fast. - In some rare situations "ps" output could have shown a lot of "?" characters after Dovecot process titles. - When dovecot.index.pvt is empty, an unnecessary error is logged: Error: .../dovecot.index.pvt reset, view is now inconsistent - SMTP address encoder duplicated initial double quote character when the localpart of an address ended in '..'. For example "user+..(a)example.com" became ""user+.."@example.com in a sieve redirect. --- Aki Tuomi Open-Xchange Oy

5 9

BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting
by Alex Ha 20 Oct '19

20 Oct '19

Hi all! I have two dovecot servers with dsync replication over tcp. Replication works fine except for one user. # doveadm replicator status username priority fast sync full sync success sync failed customer(a)example.com none 00:00:33 07:03:23 03:22:31 y If i run dsync manually, i get the following error message: dsync-local(customer(a)example.com): Debug: brain M: -- Mailbox renamed, restart sync -- dsync-local(customer(a)example.com): Error: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting dsync-local(customer(a)example.com): Error: Mailbox INBOX.Foldername sync: mailbox_rename failed: Invalid mailbox name 'Foldername-temp-1': Missing namespace prefix 'INBOX.' For more info see the attached sync_loop.log Thanks for your help, Alex

3 5

Coredump v2.3.8 specific msg fetch, corrupted record in index cache, Broken physical size
by Erik de Waard 20 Oct '19

20 Oct '19

Hi, i'm getting a coredump on a specific msg, i've attached the gdb. file on disk i noticed W=<vsize> is missing. 1571209735.M744550P1608.rwvirtual65,S=15886:2,S Best regards, mail.log Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Mailbox INBOX.Debug: UID=1041: read(/data/mail/ company.nl/users/johndoe/Maildir/.Debug/cur/1571209735.M744550P1608.rwvirtual65,S=15886:2,S) failed: Cached message size smaller than expected (15886 < 16367, box=INBOX.Debug, UID=1041) (read reason=mail stream) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Corrupted record in index cache file /data/indexes/ johndoe(a)company.nl/.Debug/dovecot.index.cache: UID 1041: Broken physical size in mailbox INBOX.Debug: read(/data/mail/ company.nl/users/johndoe/Maildir/.Debug/cur/1571209735.M744550P1608.rwvirtual65,S=15886:2,S) failed: Cached message size smaller than expected (15886 < 16367, box=INBOX.Debug, UID=1041) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xe5c31) [0x7f5237d8cc31] -> /usr/lib/dovecot/libdovecot.so.0(+0xe5cd1) [0x7f5237d8ccd1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f5237ce4103] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x300) [0x7f5237d9abd0] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x35) [0x7f5237d9aca5] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f5237d9b64d] -> /usr/lib/dovecot/libdovecot.so.0(+0xc4da1) [0x7f5237d6bda1] -> /usr/lib/dovecot/libdovecot.so.0(+0xc5d4b) [0x7f5237d6cd4b] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x65) [0x7f5237d6da05] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_body+0x31) [0x7f5237d6dcf1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc19d4) [0x7f52381099d4] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x3aa) [0x7f5238109e9a] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x74b25) [0x7f52380bcb25] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream_because+0x70) [0x7f52380833a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x748d7) [0x7f52380bc8d7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x44) [0x7f5238082ea4] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x21523) [0x561f6425f523] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x1f759) [0x561f6425d759] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](imap_fetch_more+0x39) [0x561f6425eb99] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](cmd_fetch+0x342) [0x561f6424ef32] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](command_exec+0x7c) [0x561f6425bb0c] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](+0x1bb72) [0x561f64259b72] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x1bc04) [0x561f64259c04] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](client_handle_input+0x1a5) [0x561f6425a025] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](client_input+0x82) [0x561f6425a6c2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x75) [0x7f5237da6845] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x11b) [0x7f5237da825b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f5237da6959] Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Fatal: master: service(imap): child 15868 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps)

2 2

dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
by Ralf Hildebrandt 16 Oct '19

16 Oct '19

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig -c topfiles_bytes; This command quickly pointed to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp That file was written excessively. I then put ~/mdbox/mailboxes/INBOX/dbox-Mails/ into tmpfs and alas, the queue would drain quickly. But why is that? Why would the index file be updated so often? This is dovecot 2.3.7.2-1~bionic # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # OS: Linux 5.0.0-29-generic x86_64 Ubuntu 18.04.3 LTS default_vsz_limit = 2 G lmtp_user_concurrency_limit = 10000 mail_attachment_dir = /home/copymail/attachments mail_attachment_hash = %{sha256} mail_fsync = never mail_location = mdbox:~/mdbox mail_plugins = zlib fts fts_lucene mdbox_rotate_size = 128 M 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 { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } plugin { fts = lucene fts_languages = de,en fts_lucene = whitespace_chars=@. } protocols = " imap lmtp" service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 10.0.5.208 port = 1025 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_ca = /etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/ssl/certs/mail-cbf.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } protocol lmtp { mail_plugins = zlib fts fts_lucene } -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

3 9

Vacation Fcc
by Gregory Heytings 14 Oct '19

14 Oct '19

Hi list, I use Dovecot's Pigeonhole Sieve implementation, and there is one little feature I'm missing: When a vacation message is sent, I'd like to keep a copy of that message in my "sent" mailbox. There is an RFC draft (draft-ietf-extra-sieve-fcc-09) for this, which adds a ":fcc" argument to vacation, but apparently it's not supported by Pigeonhole. I have two questions: Will ":fcc" be supported in the future? In the meantime (or if supporting ":fcc" is not planned), is it possible to achieve the same result with the existing Sieve extensions? (I can imagine a way to do this at the MTA level by checking the presence of the "Auto-Submitted:" header, but did not test it.) Thanks, Gregory

2 3