- dovecot - dovecot.org

Dovecot as transparent proxy for Exchange<->Dovecot<->Yahoo.com/Yandex.com with mail synchronization between servers !
by CpServiceSPb 25 Jun '18

25 Jun '18

We have Exchange as internal mail server, also we have gate where we plant to install Dovecot, also we have external mail at servers such as yahoo.com ort yandex.com. There are some mailboxes at Exchange, for example: user1(a)internal.ltd to user10(a)internal.ltd. There are some mailboxes at Ynadex.com, for example: personel1(a)external.com to personel10(a)external.com. 1. For messages flow: We need that Dovecot would act as at least transparent IMAP proxy for Exchange/Yandex and vise versa. For incoming messages - some messages comes to personel5(a)external.com located at Yandex.com, then Dovecot gets it from Yandex using IMAP IDLE, tnen stores it locally (where Dovecot is installed) to MySQL (using DBMail) or at least maildir format and after that sends it forward (using IMAP PUSH) to appropriate account user5(a)internal.ltd or triggers (signals) Fetchmail to sends forward it to specified Exchange acoount. And so on - for each external/interla pairs of accounts (Yandex.com/Exchange) . For outgoing messages - Exchange send out it using Exim4, Exim4 stores it locally (where Dovecot is installed) to MySQL (using DBMail) and then Exim4 sends it out to Yandex.com and in the same time Dovecot uploads this message to Yandex.com to "Sent" folder. And this messages is sent through Yandex.com. 2. For messages storage: When messages are deleted at Exchange, it are deleted from Dovecot (MySQL storage) and deleted from Yandex.com as well. Or when messages are deleted from Yandex.com, it are deleted from Dovecot (MySQL storage) and deleted from Exchange as well. Is it possible to set up Dovecot and may be some other soft (Fetchmail, imapsyncd and so on) to get point 1 working or point 1 and point 2 working ?

1 0

More and better logging
by Tom Sommer 25 Jun '18

25 Jun '18

In general I feel there is a lack of debug and "when things go wrong"-logging in Dovecot (information that should perhaps be provided with a verbose toggle). I was debugging problems with sasl user logins and a generic "SASL CRAM-MD5 authentication failed: Connection lost to authentication server" error in postfix, but nothing is logged in Dovecot when the error occurs. After extensive debugging I finally discovered auth-penalty and auth_penalty_to_secs after digging in the code. I suspect this to be the cause, but truly I have no way of confirming this, since no log is provided when this is triggered? - it would be nicer if events such as these were simply logged for better debugging and troubleshooting. Two cents :) Thanks -- Tom

2 1

Released Pigeonhole v0.5.2.rc1 for Dovecot v2.3.2.rc1.
by Stephan Bosch 24 Jun '18

24 Jun '18

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.2 release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release contains the new IMAP FILTER=SIEVE capability, which was also released earlier with 2.2.24 (with a few additional fixes). Changelog v0.5.2: + Implement plugin for the a vendor-defined IMAP capability called "FILTER=SIEVE". It adds the ability to manually invoke Sieve filtering in IMAP. More information can be found in doc/plugins/imap_filter_sieve.txt. - The Sieve address test caused an assertion panic for invalid addresses with UTF-8 codepoints in the localpart. Fixed by properly detecting invalid addresses with UTF-8 codepoints in the localpart and skipping these like other invalid addresses while iterating addresses for the address test. - Make the length of the subject header for the vacation response configurable and enforce the limit in UTF-8 codepoints rather than bytes. The subject header for a vacation response was statically truncated to 256 bytes, which is too limited for multi-byte UTF-8 characters. - Sieve editheader extension: Fix assertion panic occurring when it is used to manipulate a message header with a very large header field. - Properly abort execution of the sieve_discard script upon error. Before, the LDA Sieve plugin attempted to execute the sieve_discard script when an error occurs. This can lead to the message being lost. - Fix the interaction between quota and the sieve_discard script. When quota was used together with a sieve_discard script, the message delivery did not bounce when the quota was exceeded. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.2.… http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.2.… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Can't build pigeonhole against dovecot 2.3.2rc1
by tai74＠vfemail.net 22 Jun '18

22 Jun '18

Help? ntfy-mailto.c: In function ‘ntfy_mailto_send’: ntfy-mailto.c:505:5: error: too few arguments to function ‘smtp_address_create_from_msg_temp’ sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note: declared here int smtp_address_create_from_msg_temp(const struct message_address *msg_addr, ^ ntfy-mailto.c: In function ‘ntfy_mailto_action_execute’: ntfy-mailto.c:682:4: error: too few arguments to function ‘smtp_address_create_from_msg_temp’ sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note: declared here int smtp_address_create_from_msg_temp(const struct message_address *msg_addr, ^ make[6]: *** [ntfy-mailto.lo] Error 1 ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 2

variable forwarding buglet
by Jan-Pieter Cornet 22 Jun '18

22 Jun '18

I wanted to forward information from the director to the backend dovecot (original login name), so I had the userdb on the director return a forward_ologin variable. However, when I tried to use that variable in the "password_key" query on the backend dovecot, ${forward_ologin} was expanded to UNSUPPORTED_VARIABLE_forward_ologin. After testing a bit and looking around in the source a bit, and turning on debugging logging, it appeared that the forwarded variables actually appear as "passdb/userdb extra fields". So in my case, the forwarded information is available as %{passdb:forward_ologin}. So, problem solved, but this is either an implementation bug, or a documentation bug, or oversight. -- Jan-Pieter Cornet <johnpc(a)xs4all.net> Systeembeheer XS4ALL Internet bv www.xs4all.nl

1 0

Location of dovecot.sieve
by ratatouille 22 Jun '18

22 Jun '18

Hello! If I set sieve = file:~/sieve;active=~/.dovecot.sieve in dovecot.conf like I read in the documentation I get Jun 22 16:36:01 lda(a.meyer): Error: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Jun 22 16:36:01 lda(a.meyer): Error: sieve: failed to access user's Sieve script file:~/sieve;active=~/.dovecot.sieve (temporary failure) What is wrong with this one? Kind regards Andreas

1 0

enable dovecot.sieve.log
by ratatouille 22 Jun '18

22 Jun '18

Hello! How do I enable dovecot.sieve.log? I see nothing about that in 90-sieve.conf Kind regards Andreas

1 1

doveadm backup -A does not create user dirs
by Vladimir Tiukhtin 20 Jun '18

20 Jun '18

Hello doveadm backup -A mdbox:/tmp/test does not create per user folders, instead it tries to override same catalog again and again doveadm backup -A mdbox:/tmp/test/%u does not work as well Is there a solution for local backups? Thanks Vladimir

2 1

v2.3.2 release candidate released
by Timo Sirainen 18 Jun '18

18 Jun '18

https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). * old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security problems if the process is ptrace()d at the same time. Instead, open it while still running as root. + doveadm: Added mailbox cache decision&remove commands. See doveadm-mailbox(1) man page for details. + doveadm: Added rebuild attachments command for rebuilding $HasAttachment or $HasNoAttachment flags for matching mails. See doveadm-rebuild(1) man page for details. + cassandra: Use fallback_consistency on more types of errors + lmtp proxy: Support outgoing SSL/TLS connections + lmtp: Add lmtp_rawlog_dir and lmtp_proxy_rawlog_dir settings. + submission: Add support for rawlog_dir + submission: Add submission_client_workarounds setting. + lua auth: Add password_verify() function and additional fields in auth request. - doveadm-server: TCP connections are hanging when there is a lot of network output. This especially caused hangs in dsync-replication. - Using multiple type=shared mdbox namespaces crashed - mail_fsync setting was ignored. It was always set to "optimized". - lua auth: Fix potential crash at deinit - SSL/TLS servers may have crashed if client disconnected during handshake. - SSL/TLS servers: Don't send extraneous certificates to client when alt certs are used. - lda, lmtp: Return-Path header without '<' may have assert-crashed. - lda, lmtp: Unencoded UTF-8 in email address headers may assert-crash - lda: -f parameter didn't allow empty/null/domainless address - lmtp, submission: Message size limit was hardcoded to 40 MB. Exceeding it caused the connection to get dropped during transfer. - lmtp: Fix potential crash when delivery fails at DATA stage - lmtp: login_greeting setting was ignored - Fix to work with OpenSSL v1.0.2f - systemd unit restrictions were too strict by default - Fix potential crashes when a lot of log output was produced - SMTP client may have assert-crashed when sending mail - IMAP COMPRESS: Send "end of compression" marker when disconnecting. - cassandra: Fix consistency=quorum to work - dsync: Lock file generation failed if home directory didn't exist - Snippet generation for HTML mails didn't ignore &entities inside blockquotes, producing strange looking snippets. - imapc: Fix assert-crash if getting disconnected and after reconnection all mails in the selected mailbox are gone. - pop3c: Handle unexpected server disconnections without assert-crash - fts: Fixes to indexing mails via virtual mailboxes. - fts: If mails contained NUL characters, the text around it wasn't indexed. - Obsolete dovecot.index.cache offsets were sometimes used. Trying to fetch a field that was just added to cache file may not have always found it.

1 0

TCP replication: high connection rate and looping in incomplete state
by tok 16 Jun '18

16 Jun '18

Hi, I am trying to establish TCP(s)-based replication between two FreeBSD 11.1 machines, both running Dovecot 2.2.35 (via pkg) with 10 virtual users and 1.2GB maildir. I followed the Wiki description (https://wiki2.dovecot.org/Replication) just skipped the SSH part. My resulting configurations are attached below. Problem: After reloading both Dovecot instances, a few seconds later they start to initiate connections in an absurdly high rate (30-50 new connections during 10 secs, closing old ones after 2-3 secs) and even after 1 hour they do not „calm down". E-mails are copied, but judging by size and file count, not completely (approx. 1GB and maybe 90% of files are getting synced). What is going on here? On the destination host (with empty storage before replication) I see "incremental - Waiting for dsync to finish“ in dsync-status, constantly flipping between handshake and waiting, for solely 4 out of 10 accounts. Replicator status says 0 requests and 10 total users. On the source host, replicator status says 4 queued full resyncs, 3 waiting failed and 10 total users. I already tried both tcps and tcp; activating debug log did not reveal any errors (e.g. SSL). Would be happy for any advice to track this down. Best regards, tok Config source host: ----- # 2.2.35 (b1cb664): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.23 (b2e41927) # OS: FreeBSD 11.1-RELEASE-p10 amd64 zfs # Hostname: srv1.TLD auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 lmtp_save_to_detail_mailbox = yes login_trusted_networks = 172.16.1.110/32 mail_location = maildir:/srv/mail/vhosts/%d/%n mail_plugins = quota mailbox_alias notify replication namespace inbox { […] } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcps:srv2.TLD:12345 quota = maildir:User quota quota_grace = 10%% quota_max_mail_size = 50M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10%% quota_rule3 = Junk:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is over quota / full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u [...] } postmaster_address = postmaster@TLD quota_full_tempfail = yes service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { process_min_avail = 1 service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { process_min_avail = 1 service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh user = vmail } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = vmail mode = 0666 } } ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem ssl_client_ca_file = /etc/ssl/cert.pem userdb { args = username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = quota mailbox_alias notify replication quota sieve } protocol lda { mail_plugins = quota mailbox_alias notify replication sieve } protocol imap { mail_plugins = quota mailbox_alias notify replication imap_quota imap_sieve } ----- Diff config of destination host: ----- 4c4 < # Hostname: srv2.TLD --- > # Hostname: srv1.TLD 9a10 > login_trusted_networks = 172.16.1.110/32 60c61 < mail_replica = tcps:srv1.TLD:12345 --- > mail_replica = tcps:srv2.TLD:12345 156c157 < ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem --- > ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem -----

1 0