- dovecot - dovecot.org

Re: Dovecot installation and ssl certificates
by Joseph Tam 12 Mar '24

12 Mar '24

Jerry Stuckle writes: > I'm starting with POP3 (because it's easy to handle from the CLI). I > have it working from localhost - I can telnet to port localhost 110 and > access emails (of course I can't do this from a remote system because it > requires SSL). Sure you can: (STARTTLS style) openssl s_client -starttls pop3 -connect your.pop.server:110 (SSL style) openssl s_client -connect your.pop.server:995 You can also use ncat (exercise left to the reader). "localhost", I believe, is a specific exclusion where SSL in *not* enforced during the session. > Trying to access this from a remote system with Thunderbird is not > working. /var/log/mail.log shows the following: > > 2024-03-03T22:18:54.887061-05:00 debian-server dovecot: pop3-login: > Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL > routines::sslv3 alert bad certificate: SSL alert number 42 (no auth > attempts in 0 secs): user=<>, rip=206.223.85.12, lip=206.223.85.137, TLS > handshaking: SSL_accept() failed: error:0A000412:SSL routines::sslv3 > alert bad certificate: SSL alert number 42, session=<l6qBL80SOePO31UM> This looks like an error message stating STARTTLS was expected but the client used a plaintext session. Try enabling STARTTLS on your Thunderbird. If that is not the cause ... Ref: https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/ The most important dovecot configurations are ssl_cert = </path/to/your/server.crt ssl_key = </path/to/your/server.key You can have protocol specific certificates e.g. protocol pop3 { ssl_cert = ... ssl_key = ... } but you'll typically put this outside the protocol section so that there is one default certificate. > I need help. First of all, an explanation as to how to configure the > dovecot-openssl.cnf file (an example with actual values - real or fake - > would be a real help). > > Second, where does this go? Maybe running doveconf will tell you where your installation expects the main configuration file to be. This file may include other config files. > Note that for right now I'm trying to just get one domain working but > eventually this will serve at least 4 domains. Once I get the first > domain working, thoughts about how to get multiple domains working would > also be appreciated. This depends on how you set up your filesystem and authentication and your security constraints. You'll have to be more specific on your setup. Confining my reply to just SSL setup, you can obtain a SSL certificate with multiple domains named listed, which makes multi-domain SSL support easier. Joseph Tam <jtam.home(a)gmail.com>

1 0

Remote IP address in dovecot
by Andre Rodier 12 Mar '24

12 Mar '24

Hello, I am using a webmail, SOGo, to access Dovecot mail server in IMAP. SOGo correctly logs the remote IP address, using the standard nginx headers, especially X-Forwarded-For. However, when I check the IMAP logs, I see my server's IP address for the "remote_ip" value. I think there is a way to override this value from the environment, but I could not find it. Thanks for your help, -- André Rodier

2 1

Dovecot installation and ssl certificates
by Jerry Stuckle 12 Mar '24

12 Mar '24

Hi, all, First of all, I will admit I am totally a noob with Dovecot. I am trying to install it on Debian and am somewhat lost. Right now this is a test system on our LAN. I'm starting with POP3 (because it's easy to handle from the CLI). I have it working from localhost - I can telnet to port localhost 110 and access emails (of course I can't do this from a remote system because it requires SSL). Trying to access this from a remote system with Thunderbird is not working. /var/log/mail.log shows the following: 2024-03-03T22:18:54.887061-05:00 debian-server dovecot: pop3-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42 (no auth attempts in 0 secs): user=<>, rip=206.223.85.12, lip=206.223.85.137, TLS handshaking: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42, session=<l6qBL80SOePO31UM> I tried to create a certificate with mkconf.sh but obviously don't have the right information in the configuration file and/or didn't get the files in the right place (I've seen different places they should be). I need help. First of all, an explanation as to how to configure the dovecot-openssl.cnf file (an example with actual values - real or fake - would be a real help). Second, where does this go? Note that for right now I'm trying to just get one domain working but eventually this will serve at least 4 domains. Once I get the first domain working, thoughts about how to get multiple domains working would also be appreciated. I know we noobs are a PITA but I really appreciate the help. Jerry

2 1

[dovecot 2.3.4.1] Pigeonhole sieve: Howto use vacation extension with virtual users and subject/message stored in database?
by phren＠ist-einmalig.de 11 Mar '24

11 Mar '24

Hi, we're about to replace our current auto-responder with pigeonhole sieve vacation extension. Currently the (virtual) users are able to enable and disable the auto-responder, besides subject and message, in the webinterface and the setting is stored in a database. Now we're looking for a way for the vacation extension to use the database as source for enabled/disabled/subject/message. The goal is *not* to use the virtual home directory as storage. On the first sight the extdata plugin seems to have an interface to the database, but I'm unable to find a way for conditional SQL statements. Our last resort could be the extprograms plugin, but we try to avoid shell scripts. Virtual users are common usage and so we're pretty sure that there is a way to use pigeonhole sieve vacation extension with database storage. But we're unable to find it. Can please someone point to us to the right direction? Every hint is appreciated. -- Phren

1 0

Remote IP address in dovecot
by André Rodier 11 Mar '24

11 Mar '24

Hello, I am using a webmail, SOGo, to access Dovecot mail server in IMAP. SOGo correctly logs the remote IP address, using the standard nginx headers, especially X-Forwarded-For. However, when I check the IMAP logs, I see my server's IP address for the "remote_ip" value. I think there is a way to override this value from the environment, but I could not find it. Thanks for your help, -- André Rodier

1 0

Documentation error for sieve_redirect_envelope_from
by Thomas Mechtersheimer 11 Mar '24

11 Mar '24

Hi, the documentation at https://doc.dovecot.org/settings/pigeonhole/ says regarding sieve_redirect_envelope_from setting option user_email: | The user’s primary address is used. This is configured with the | sieve_user_email setting. If that setting is not configured, user_email | is equal to sender. But checking dovecot-2.3-pigeonhole-0.5.21/src/lib-sieve/sieve-address-source.c ~line 79: | if ( type == SIEVE_ADDRESS_SOURCE_USER_EMAIL && | svinst->user_email == NULL ) | type = SIEVE_ADDRESS_SOURCE_RECIPIENT; So if sieve_user_email is not configured, "user_email" is equal to "recipient" (which is the observed behaviour). Either the documentation is incorrect and should be updated, or the source has a bug . btw: I was looking at this cause I search for a way to change the envelope sender on redirect only for a specific user. But it looks like this is impossible: sieve_redirect_envelope_from is a server wide setting; and the sieve script doesn't allow changing the envelope... -- Thomas Mechtersheimer - Necklenbroicher Str. 45a - D-40667 Meerbusch - Germany EMail: thomasm(a)wupper.com IRC-Nick: Mechti Of course I'm crazy, but that doesn't mean I'm wrong. I'm mad but not ill.

1 0

deliverability test
by Aki Tuomi 11 Mar '24

11 Mar '24

Test Aki

2 1

Abort IMAP COPY command from imapsieve?
by Tom Hendrikx 10 Mar '24

10 Mar '24

Hi, I'm finding myself regularly moving messages to the wrong folder in my MUA. Most of the time this is easily corrected, but sometimes this is a bit harder. Imagine selecting all messages in the 'Trash' or 'Junk' folder, and moving them in the 'Archive' folder (by clicking on the MUA's 'Archive' button in stead of the 'Delete' button). I'm looking into blocking this server-side using an IMAPSieve script. So far I've been able to log relevant details of such a message move, but I don't how I can abort the message move altogether. I'm now using the following config, which result in log messages like: dovecot: imap(tom(a)example.org)<540588><TmDbwVATNOoqEDeBFZcAASOvWpPsXcmR>: sieve: DEBUG: move-to-archive: Message archived: mailbox-from=INBOX mailbox-to=Archives.2023 message-id=<648ab0b4-8439-4b2d-8e53-b97e700ff9d0(a)mail.example.org> subject='Testing IMAPSieve' File: dovecot.conf ----- protocol imap { mail_plugins = $mail_plugins imap_sieve } plugin { sieve_plugins = sieve_imapsieve sieve_implicit_extensions = +vnd.dovecot.debug # Find out how to block messages from being from 'Trash' to 'Archive' folder imapsieve_mailbox1_name = Archives.* #imapsieve_mailbox1_from = INBOX imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/move-to-archive.sieve } ----- File: move-to-archive.sieve ----- require "environment"; require "variables"; require "vnd.dovecot.debug"; require "vnd.dovecot.imapsieve"; if header :matches "Message-ID" "*" { set "message_id" "${1}"; } else { set "message_id" "UNKNOWN"; } if header :matches "Subject" "*" { set "subject" "${1}"; } else { set "subject" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-from" "*" { set "mailbox_from" "${1}"; } else { set "mailbox_from" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-to" "*" { set "mailbox_to" "${1}"; } else { set "mailbox_to" "UNKNOWN"; } debug_log "move-to-archive: Message archived: mailbox-from=${mailbox_from} mailbox-to=${mailbox_to} message-id=${message_id} subject='${subject}'"; ----- I tried the "reject" sieve command but that only works in the context of delivery. Is there a way to abort the actual move, and return an error to the MUA? Or am I on the wrong track altogether, and is there a better approach? NB: While doing research I found that not all environment variables in RFC 6785 (https://www.rfc-editor.org/rfc/rfc6785.html#section-4) are implemented in Pigeonhole? I tried to access the 'imap.cause' and 'imap.mailbox' variables but they were empty, only the variables from RFC 5183 seem to be available. This is inline with the docs at https://github.com/dovecot/pigeonhole/blob/main/README, but not with https://github.com/dovecot/pigeonhole/blob/main/doc/plugins/imapsieve.txt and https://doc.dovecot.org/configuration_manual/sieve/plugins/imapsieve/, which both seems to imply that RFC 6785 is implemented? Kind regards, Tom

1 0

Fw: User-configurable time-based mail deletion in specific folders
by Rupert Gallagher 10 Mar '24

10 Mar '24

> Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven -- https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org > Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven - - https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list - - dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

6 8

JMAP status?
by Brad Koehn 08 Mar '24

08 Mar '24

Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world. Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world.

3 2