June 2024 - dovecot - dovecot.org

Re: "Read the 'bug reports page' …" -> 404
by H. Thiele 13 Jun '24

13 Jun '24

I also noticed this affects local documentation in the Dovecot release (v2.3.21), e.g. the old URL is referenced in many of the man files that get installed. It is probably a good idea to setup a 301 redirect rather than just dumping a 404 on the website too. On 12/06/24 8:05 AM, aki.tuomi wrote: > Thanks for letting us know. We'll fix this soon, use > https://dovecot.org/bugreport-mail > > Aki > > -------- Original message -------- > From: "H. Thiele via dovecot" <dovecot(a)dovecot.org> > Date: 6/12/24 06:49 (GMT+00:00) > To: dovecot(a)dovecot.org > Subject: "Read the 'bug reports page' …" -> 404 > > > Hi there, > > while investigating how to possibly report issues to the Dovecot > project I noticed that the link to the "bug reports page" in > the "mailing list" section on dovecot.org is broken and leads to > a 404. > > > https://www.dovecot.org/mailing-lists/ -> > "Read the 'bug reports page' before posting a bug report. …" > > -> "The page you are looking for is not found" > > > > regards, > H. Thiele > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org >

1 0

Duplicate "cache" in doveadm's help text
by H. Thiele 12 Jun '24

12 Jun '24

1 0

how to disable port 143
by Jeff Peng 10 Jun '24

10 Jun '24

Hello, I have commented out this line in 10-master.conf: service imap-login { inet_listener imap { #port = 143 } But this doesn't close the port 143. So I have changed it to: service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } This let port 143 listen on local address. my question, is it possible to close port 143 entirely in dovecot? Thanks.

5 8

Lots of "Corrupted dbox file" errors in log
by simon＠simonliebold.de 10 Jun '24

10 Jun '24

Hi, I'm leaving this here for others who may see the same issue and are equally perplexed as I was: Dovecot version 2.3.16 w/ sdbox mailbox format. Yesterday, I noticed that I did not see any new mail in Thunderbird. But for whatever reason, new mail did show up on my phone with K9 mail. So, new mails were retained. In the Dovecot logs, I was seeing multiple errors: Corrupted dbox file read() failed for file No buffer space available EOF while reading file header Mailbox INBOX: sdbox: Rebuilding failed Mailbox INBOX: Deleting corrupted cache: reset_id mismatch even after locking The "Corrupted dbox file" and "EOF while reading file header" error was caused by a message file in the INBOX mailbox that was 6681 bytes in size and had all NUL characters. File date of that file was more than two years ago. The "No buffer space available" error was caused by a file that also had a lot of NUL, but also a few other characters in it. Nothing resembling regular message files with headers and body. In total it was a handful of files causing issues. I deleted them all with: doveadm expunge -u {user} MAILBOX INBOX UID {filename without the leading 'u.'} Afterwards Thunderbird showed new mails again. I did not need to restart it. No more errors in the Dovecot logs. Not sure what had caused this. Maybe somebody has seen this before. Simon

1 0

[Patch] Allow sieve redirects to specified domains only
by Kadlecsik József 10 Jun '24

10 Jun '24

Hello, The use case is simple: we have to forbid sieve redirects to outside, but should be able to redirect inside. The patch below adds a new sieve configuration option sieve_allowed_redirects to list the domains to which redirects are permitted and otherwise are not allowed. Please consider it. diff --git a/pigeonhole/doc/example-config/conf.d/90-sieve.conf b/pigeonhole/doc/example-config/conf.d/90-sieve.conf index 238bcf4..3b4ac65 100644 --- a/pigeonhole/doc/example-config/conf.d/90-sieve.conf +++ b/pigeonhole/doc/example-config/conf.d/90-sieve.conf @@ -126,6 +126,10 @@ plugin { # script execution. If set to 0, no redirect actions are allowed. #sieve_max_redirects = 4 + # The comma/space separated list of email domains where redirection is allowed. + # If the list is empty, there is no restriction. + sieve_allowed_redirects = + # The maximum number of personal Sieve scripts a single user can have. If set # to 0, no limit on the number of scripts is enforced. # (Currently only relevant for ManageSieve) diff --git a/pigeonhole/src/lib-sieve/cmd-redirect.c b/pigeonhole/src/lib-sieve/cmd-redirect.c index 6a3b0a4..17e9031 100644 --- a/pigeonhole/src/lib-sieve/cmd-redirect.c +++ b/pigeonhole/src/lib-sieve/cmd-redirect.c @@ -107,6 +107,24 @@ const struct sieve_action_def act_redirect = { .commit = act_redirect_commit, }; +static bool +cmd_redirect_allowed(struct sieve_instance *svinst, + const struct smtp_address *to_address) +{ + const char **domain; + bool result = TRUE; + + if (!svinst->allowed_redirects) + return TRUE; + for (domain = svinst->allowed_redirects; *domain != NULL; ++domain) { + if (strcasecmp(*domain, to_address->domain) == 0) { + return TRUE; + } + result = FALSE; + } + return result; +} + /* * Validation */ @@ -127,6 +145,12 @@ cmd_redirect_validate(struct sieve_validator *validator, if (!sieve_validator_argument_activate(validator, cmd, arg, FALSE)) return FALSE; + if (svinst->max_redirects == 0) { + sieve_command_validate_error(validator, cmd, + "local policy prohibits the use of a redirect action"); + return FALSE; + } + /* We can only assess the validity of the outgoing address when it is * a string literal. For runtime-generated strings this needs to be * done at runtime. @@ -148,14 +172,17 @@ cmd_redirect_validate(struct sieve_validator *validator, } } T_END; + if (!result && + !cmd_redirect_allowed(svinst, + sieve_address_parse_str(raw_address, &error))) { + sieve_command_validate_error(validator, cmd, + "local policy prohibits the use of a redirect action"); + return FALSE; + } + return result; } - if (svinst->max_redirects == 0) { - sieve_command_validate_error(validator, cmd, - "local policy prohibits the use of a redirect action"); - return FALSE; - } return TRUE; } @@ -238,6 +265,11 @@ cmd_redirect_operation_execute(const struct sieve_runtime_env *renv, "local policy prohibits the use of a redirect action"); return SIEVE_EXEC_FAILURE; } + if (!cmd_redirect_allowed(svinst, to_address)) { + sieve_runtime_error(renv, NULL, + "local policy prohibits the use of a redirect action"); + return SIEVE_EXEC_FAILURE; + } if (sieve_runtime_trace_active(renv, SIEVE_TRLVL_ACTIONS)) { sieve_runtime_trace(renv, 0, "redirect action"); diff --git a/pigeonhole/src/lib-sieve/sieve-common.h b/pigeonhole/src/lib-sieve/sieve-common.h index e79fb4d..d980c9d 100644 --- a/pigeonhole/src/lib-sieve/sieve-common.h +++ b/pigeonhole/src/lib-sieve/sieve-common.h @@ -209,6 +209,7 @@ struct sieve_instance { const struct smtp_address *user_email, *user_email_implicit; struct sieve_address_source redirect_from; unsigned int redirect_duplicate_period; + const char **allowed_redirects; }; /* diff --git a/pigeonhole/src/lib-sieve/sieve-settings.c b/pigeonhole/src/lib-sieve/sieve-settings.c index 47f70da..70addc7 100644 --- a/pigeonhole/src/lib-sieve/sieve-settings.c +++ b/pigeonhole/src/lib-sieve/sieve-settings.c @@ -267,4 +267,10 @@ void sieve_settings_load(struct sieve_instance *svinst) svinst->user_email = address; } } + svinst->allowed_redirects = NULL; + str_setting = sieve_setting_get(svinst, "sieve_allowed_redirects"); + if (str_setting != NULL && *str_setting != '\0') { + svinst->allowed_redirects = + (const char **)p_strsplit_spaces(svinst->pool, str_setting, ", "); + } } Best regards, Jozsef -- E-mail : kadlecsik.jozsef(a)wigner.hun-ren.hu PGP key: https://wigner.hu/~kadlec/pgp_public_key.txt Address: Wigner Research Centre for Physics H-1525 Budapest 114, POB. 49, Hungary

1 0

[Patch] blocklist access control for dovecot pop3/imap and pigeonhole managesieve
by John Fawcett 10 Jun '24

10 Jun '24

Hi Just in case this is useful more generally, I'm posting it to the list. While Dovecot has an access control via allow_nets, it is a user database field that applies only at the authentication stage to deny access for the specific user when there is a connection attempt from an unauthorized ip for that user. https://doc.dovecot.org/configuration_manual/authentication/allow_nets/ I don't believe there is anything that checks access at connect time to deny unwanted traffic prior to authentication, for example from compromised machines, botnets etc. Though failed connection attempts do not appear to be a significant issue, maybe better to add some safety net for the future. The attached patch is proof of concept code that introduces the parameters rbl_check and rbl_check_timeout (msecs) to the protocol section. Tested for imap, pop3 and sieve. The following is an example for sieve. protocol sieve { rbl_check = zen.spamhaus.net=127.0.0.4 rbl_check_timeout = 5000 } If the lookup results in a hit the client is disconnected with a BYE "Disconnected for policy." message and the logs report: Jun 09 12:00:56 server.example.com dovecot[977650]: managesieve-login: Disconnected: Policy (disconnected before auth was ready, waited 1 secs): user=<>, service=sieve, rip=n.n.n.n, lip=n.n.n.n The patch also makes the number of pre-login errors and post-login errors configurable (max_login_command_errors and max_command_errors respectively) for pop3, imap and sieve protocols . protocol sieve { max_command_errors = 1 max_login_command_errors = 1 } A potential extension to the logic would be "allow_nets" and "disallow_nets" parameters or maybe something more sophisticated to allow ips/networks that would otherwise be blocked or deny additional ips/networks. John

2 3

Error: Mailbox Spam: Failed to autocreate mailbox: Mailbox can't be created
by Jordan Rosenthal 09 Jun '24

09 Jun '24

Hi, I am getting the error "Error: Mailbox Spam: Failed to autocreate mailbox: Mailbox can't be created" and cannot figure out what is causing it. It seems like some sort of permissions issue, but nothing I have tried seems to fix the problem. I was running my setup for many years without issue, and this error started occurring after a recent Ubuntu upgrade. I am using getmail 6.18.4 to fetch mail from a mail server, which then calls /usr/lib/dovecot/deliver to deliver the mail to my local system. It is during this delivery that the error occurs. The dovecot-lda executable exits with status 75 and the log file contains: Jun 09 08:05:54 honeydukes dovecot[1863]: lda(sally)<1863><L9pgDaKaZWZHBwAASkLcPA>: Error: Mailbox Spam: Failed to autocreate mailbox: Mailbox can't be created Jun 09 08:05:54 honeydukes dovecot[1863]: lda(sally)<1863><L9pgDaKaZWZHBwAASkLcPA>: msgid=<REDACTED>: save failed to open mailbox Spam: Mailbox Below is my dovecot configuration. Any help would be appreciated! ------------------ # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.15.0-112-generic x86_64 Ubuntu 22.04.4 LTS # Hostname: honeydukes.fios-router.home lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:~/Maildir mail_privileged_group = mail maildir_very_dirty_syncs = yes 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 Spam { auto = create special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap sieve" service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/dovecot/ssl/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it submission_host = <redacted>.com:465 userdb { driver = passwd }

1 0

Accessing IMAP from Python with Encrypted Password
by adam＠ardaemail.com 09 Jun '24

09 Jun '24

Hello again Dovecoters! I have a need to access an IMAP mailbox via a Python script to parse and stored DMARC reports in a SQL database. Right now, I have it working however I am storing the password in plaintext in my database which obviously is not secure. How would you approach this scenario? Would you store the password in the database encrypted and configure Dovecot to accept said encrypted password? If so, can you point me in the right direction to configure Dovecot to handle this? If not, what would you recommend? Is it possible to intercept the email and upload the attachments to an AWS S3 bucket then move the email to another folder? Likewise, if someone wants to help here as well, I need to send outbound email via an authenticated user from Postfix. How would you approach this scenario? Thank you!

3 2

Can't Empty Inbox that is Over quota
by Jason Hirsh 08 Jun '24

08 Jun '24

> I have been trying to update my Postix/Dovecot/MySQL?Postfixadmin installation > > > I am currently on Dovecot. 2.3.2.1 > > I used the guide set forth in Purplehat.org <http://purplehat.org/> which is what got me in trouble as I am in between with setup. (He went off to Maria-db and NGINX I stayed with Apache and MySQL > > > What has happened is may Dovecot Mailboxes are super super saturated. adI inadvertently allowed email from an alarm > > Quota name Type Value Limit % > User quota STORAGE 239754 5120 4682 > User quota MESSAGE 882 - > > > I tried to empty with the command > > sudo doveadm expunge -A mailbox INBOX ALL > > > I get this error > > Error: auth-master: userdb list: User listing returned failure > doveadm: Error: Failed to iterate through some users. > Is there anyway I can remove Dovecot from my server and reinstalll it? It is so messed up I don’t care about losing data Jasion Hirsh

2 4

Re: Can't Empty Inbox that is Over quota
by Jason Hirsh 06 Jun '24

06 Jun '24

> On Jun 6, 2024, at 11:00 AM, Jason Hirsh <kasdivi(a)mac.com> wrote: > > > >> On Jun 6, 2024, at 3:10 AM, Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: >> >>> >>> On 06/06/2024 04:11 EEST Jason Hirsh via dovecot <dovecot(a)dovecot.org> wrote: >>> >>> >>>> Begin forwarded message: >>>> >>>> From: Jason Hirsh <kasdivi(a)mac.com> >>>> Subject: Can't Empty Inbox that is Over quota >>>> Date: June 3, 2024 at 8:15:53 PM EDT >>>> To: dovecot(a)dovecot.org >>>> >>>> I have been trying to update my Postix/Dovecot/MySQL?Postfixadmin installation >>>> >>>> >>>> I am currently on Dovecot. 2.3.2.1 >>>> >>>> I used the guide set forth in Purplehat.org <http://purplehat.org/> which is what got me in trouble as I am in between with setup. (He went off to Maria-db and NGINX I stayed with Apache and MySQL >>>> >>>> >>>> What has happened is may Dovecot Mailboxes are super super saturated. adI inadvertently allowed email from an alarm >>>> >>>> Quota name Type Value Limit % >>>> User quota STORAGE 239754 5120 4682 >>>> User quota MESSAGE 882 - >>>> >>>> >>>> I tried to empty with the command >>>> >>>> sudo doveadm expunge -A mailbox INBOX ALL >>>> >>>> >>>> I get this error >>>> >>>> Error: auth-master: userdb list: User listing returned failure >>>> doveadm: Error: Failed to iterate through some users. >>>> >>> >>> >>> Is there anyway I can remove Dovecot from my server and reinstalll it? It is so messed up I don’t care about losing data >>> >>> >>> >> >> um.. you have multiple issues. >> >> First of all, try >> > > > >> sudo doveadm expunge -u targetuser mailbox INBOX ALL >> > > > Ok I tried that ,,say its ran but postfixadmn shows the mailbox WAY quote and new message to tha user are being rejected > > "Your message to <jason(a)kasdivi.com <mailto:jason@kasdivi.com>> was automatically rejected: > Storage quota for this account has been exceeded, please try again later.Reporting-MTA: dns; triggerfish.theoceanwindow.com <http://triggerfish.theoceanwindow.com/> > Final-Recipient: rfc822; jason(a)kasdivi.com <mailto:jason@kasdivi.com> > Action: failed > Status: 5.2.2” > > So on to > > >> rf /path/to/user/home > > > It all went away. By mail doesn’t not work. Postfixadmin still shows sett is over limited. I try deleting and get a > > Problems running mailbox postdeletion script! > The mailbox postdeletion script failed, check the error log for details! > > >> -A means all users, and it only works if your userdb iteration works. >> >> If you truly do not care about user data and want just get rid of it, >> you can just rm -rf /path/to/user/home >> >> Aki

1 0