- dovecot - dovecot.org

failed to access user's Sieve script file
by ratatouille 26 Jun '18

26 Jun '18

Hello! I set sieve = file:~/sieve;active=~/Postfach/.dovecot.sieve because I got error Debug: sieve: user's script ~/.dovecot.sieve doesn't exist But with sieve = file:~/sieve;active=~/Postfach/.dovecot.sieve I get Jun 22 01:55:21 lda(a.meyer): Error: sieve: sieve file backend: invalid option `active=~/Postfach/.dovecot.sieve' Jun 22 01:55:21 lda(a.meyer): Error: sieve: failed to access user's Sieve script file:~/sieve;active=~/Postfach/.dovecot.sieve (temporary failure) What can I do so that LDA finds the sievescript of the user? Kind regards Andreas

2 2

use instance-name for syslog?
by A. Schulze 26 Jun '18

26 Jun '18

Hello, When running multiple instances of dovecot on the same host (or running multiple docker container), it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" It is hardcoded here: https://github.com/dovecot/core/blob/master/src/lib-master/master-service.c… Would it make sense to use the already implemented instance-name as syslog ident? How do others solve that problem? Andreas

5 8

sievec prints an error if no dovecot running with mail_plugins = stats
by SATOH Fumiyasu 25 Jun '18

25 Jun '18

Dovecot 2.2.36 + Pigeonhole 0.4.24 Is this an intended behavior? ``` # service dovecot status dovecot is stopped # doveconf mail_plugins mail_plugins = stats # ls foo.* foo.sieve # sievec foo.sieve sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such device or address # echo $? 0 # ls foo.* foo.sieve foo.svbin ``` -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: https://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 1

sieve for systemusers
by ratatouille 25 Jun '18

25 Jun '18

Hello! I enabled LDA for systemusers bei adding mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" to main.cf of postfix. I have done this because I want to use sieve for systemusers too, not only for virtual users. But the sievescripts do not work for those systemusers. What else needs to be done to get sieve to work for systemusers? Kind regards Andreas

2 1

upgrade 2.2 to 2.3, diffie-hellman, ssl_min_protocol
by tai74＠vfemail.net 25 Jun '18

25 Jun '18

hi sorry if question was asked already. Was reading https://wiki2.dovecot.org/Upgrading/2.3 first I'm confused on diffie hellman parameters file. I never set up ssl-parameters.dat before (should i have? do I have one that was automatically made for me by dovecot?) Do I need to make a fresh dh.pem? The upgrade doc tells how to convert ssl-parameters.dat but how to make a new one? other question is if I copy ssl_min_protocol from example config into my existing config is that enough? do experts on this list recommend any tweaks that increase client requirements more than dovecot developers are comfortable with but will ensure more secure protocol usage? ------------------------------------------------- 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!

3 5

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