- dovecot - dovecot.org

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

Re: Log detective help
by Michael Slusarz 06 Jun '24

06 Jun '24

> On 06/05/2024 1:22 PM MDT GDS via dovecot <dovecot(a)dovecot.org> wrote: > > Hello all, I am seeing hundreds of lines like the one below in my mail.log from this specific IP address, which belongs to Google. Is there a way to determine why this "deferred (delivery temporarily suspended)" is happening? > > Jun 5 19:09:32 arthemis postfix/error[86771]: 5D9D148296D: to=<root(a)localhost.com>, orig_to=<root@localhost>, relay=none, delay=4099, delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out) "localhost.com" - you almost certainly are intending to connect to localhost (i.e. the local loopback address, 127.0.0.1) rather than the remote domain localhost.com. So it looks like a configuration error. michael

2 1

Fwd: EXPUNGED Folder Always Visible
by Pete Long 06 Jun '24

06 Jun '24

Sorry, forgot to change the To: field :/ Pete. > Begin forwarded message: > > From: Pete Long <pete(a)valar.uk.net> > Subject: Re: EXPUNGED Folder Always Visible > Date: 6 June 2024 at 09:43:50 BST > To: Robert L Mathews <lists(a)tigertech.com> > > > >> On 5 Jun 2024, at 19:18, Robert L Mathews via dovecot <dovecot(a)dovecot.org> wrote: >> >> On Jun 5, 2024, at 12:21 AM, Pete Long via dovecot <dovecot(a)dovecot.org> wrote: >> >>> After a restart of Dovecot, I see this in the logs: >>> >>> Jun 05 08:12:07 imap(pete)<19761><KPYfSB8aj4dWH1ne>: Error: Mailbox Deleted Messages: Lazy-expunge transaction failed: Mailbox Deleted Messages: UID=1 >>> 67: lazy_expunge: Couldn't open expunge mailbox: Failed to open mailbox .EXPUNGED: Invalid mailbox name: Begins with hierarchy separator >> >> Hmmm, I'm not sure about that -- in my setup I have something different, with no actual mailbox for it: >> >> namespace { >> hidden = yes >> inbox = no >> list = no >> location = maildir:~/expunged >> prefix = .EXPUNGED/ >> separator = . >> type = private >> } >> plugin { >> lazy_expunge = .EXPUNGED/ >> lazy_expunge_only_last_instance = yes >> ... >> >> Perhaps someone else who has a similar setup to you with it as a mailbox can offer more advice, sorry! >> > > Not to worry Robert, you've given me some useful information. > > I have a workaround now which 'works for me' (TM). The gist is to copy an acl file to the .EXPUNGED mailbox when it is created, which is usually when a mail is sent, moved or deleted. I am not using global acls so note the commented line in the next paragraph. > > In /etc/dovecot/conf.d/50-expunge.conf: > > namespace inbox { > mailbox EXPUNGED { > autoexpunge = 7days > autoexpunge_max_mails = 100000 > } > } > > > mail_plugins = $mail_plugins lazy_expunge acl > plugin { > # Move messages to an .EXPUNGED mailbox > lazy_expunge = EXPUNGED > > # Define ACL so that user cannot list the .EXPUNGED mailbox > #acl = vfile:/etc/dovecot/global-acls/expunged-acl > > # Expunged messages most likely don't want to be included in quota: > quota_rule = EXPUNGED:ignore > } > > > Once the ~/Maildir/.EXPUNGED directory is created, I copy this 'dovecot-acl' file in to that .EXPUNGED directory: > > owner wstipeka > > Note that there is no l,r or x. https://doc.dovecot.org/configuration_manual/acl/#acl > > > The end result is that the .EXPUNGED mailbox contains deleted and moved mail items but the user cannot see this mailbox and cannot delete it anyway. > > If necessary I can fire up Mutt and traverse to the relevant users .EXPUNGED folder to rescue deleted items. If they also happen to have FTP and/or SSH access, I can make the dovecot-acl immutable if necessary. > > Thanks again Robert for giving me some more options. > > > All the best, > > Pete. >

1 0

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

06 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. My dovecot configurations is # 2.3.21 (47349e2482): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: FreeBSD 13.2-RELEASE-p4 amd64 ufs # Hostname: triggerfish.theoceanwindow.com dict { quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 110 first_valid_uid = 110 hostname = triggerfish.theoceanwindow.com last_valid_gid = 110 last_valid_uid = 110 lmtp_rcpt_check_quota = yes mail_location = maildir:/usr/local/virtual/%d/%n mail_plugins = quota 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 imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { expire = Trash imapsieve_mailbox1_before = file:/usr/local/virtual/sieve/rspamd/rspamd-learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/local/virtual/sieve/rspamd/rspamd-learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/local/virtual/sieve/global/read.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Trash mail_home = /usr/local/virtual/%d/%n mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_max_mail_size = 100M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+30%% quota_rule3 = Sent:storage=+30%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning4 = -storage=100%% quota-warning -100 %u sieve = /usr/local/virtual/%d/%n/.dovecot.sieve sieve_before = /usr/local/virtual/sieve/global/default.sieve sieve_dir = /usr/local/virtual/%d/%n/sieve sieve_global = /usr/local/virtual/sieve/global/ sieve_global_dir = /usr/local/virtual/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/local/virtual/sieve/rspamd sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = admin(a)theoceanwindow.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vscan mode = 0660 user = vscan } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/virtual/bin/quota-warning.sh unix_listener quota-warning { user = vscan } user = dovecot } ssl_ca = </usr/local/etc/ssl/openssl/theoceanwindow.com/ca_bundle.crt ssl_cert = </usr/local/etc/ssl/openssl/theoceanwindow.com/certificate.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota quota sieve zlib } protocol imap { mail_plugins = quota quota imap_quota zlib } protocol pop3 { mail_plugins = quota } jason@triggerfish:/usr/local/etc/apache24/extra: Sorry about the colors. I am at whit ends with the system and dont have the energy to take on apple mail formating I imagine I have messed up a Mysql query? Thanks for bearing with me

2 2

Log detective help
by GDS 06 Jun '24

06 Jun '24

Hello all, I am seeing hundreds of lines like the one below in my mail.log from this specific IP address, which belongs to Google. Is there a way to determine why this "deferred (delivery temporarily suspended)" is happening? Jun 5 19:09:32 arthemis postfix/error[86771]: 5D9D148296D: to=<root(a)localhost.com>, orig_to=<root@localhost>, relay=none, delay=4099, delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out) Thank you,Greg

2 1

EXPUNGED Folder Always Visible
by Pete Long 05 Jun '24

05 Jun '24

Hi all, I'm having a bit of a time trying to get the EXPUNGED mailbox to not display when any mail is moved or deleted. Here's what I'm running: Operating System = Debian 11.9 Dovecot = 2.3.13 MUA = Mac OS X Mail 16.0 $3774.600.62$ Here is the information I think is relevant: # cat /etc/dovecot/conf.d/50-expunge.conf namespace INBOX { mailbox EXPUNGED { autoexpunge = 7days autoexpunge_max_mails = 10000 } } mail_plugins = $mail_plugins lazy_expunge acl plugin { lazy_expunge = EXPUNGED quota_rule = EXPUNGED:ignore } # cat /etc/dovecot/conf.d/90-acl.conf [...] plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 } [...] # cat /etc/dovecot/global-acls/expunged.acl EXPUNGED user=masteruser lr I have also tried setting 'expunged.acl' to the following, with no ACL flags: EXPUNGED owner This version doesn't seem to do anything different but that's probably down to me. No matter what I do with this current configuration, I cannot get the EXPUNGED folder to stop showing after any deletion or move. This point aside, Dovecot's doing almost exactly what I want: all mail moved or deleted ends up in EXPUNGED; I just don't want to see it, nor anyone else with an account on my server ;) Thanks for your time and any information you can provide. Pete.

2 3

Debug: open(/proc/self/io) failed: Permission denied
by se＠maildaddy.eu 01 Jun '24

01 Jun '24

Tried all kinds of user setup, and read what I found on different foras, but still get: "Debug: open(/proc/self/io) failed: Permission denied" Is anyone able to spot the misconfig? Thanks in advance! This is my dovecot -n: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.70-050470-generic x86_64 Ubuntu 20.04.6 LTS # Hostname: host auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %Ln mail_location = maildir:~/Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = create special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap pop3 lmtp imap lmtp pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.spijoing.com/fullchain.pem ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = passwd }

2 2

problem setting sieve_vacation_send_from_recipient = yes
by schuerbel＠vodafonemail.de 01 Jun '24

01 Jun '24

Hello, dovecot sieve sends vacation replies with an empty FROM: field by default. Sadly my provider rejects such emails. I tried to change this behavior by adding sieve_vacation_send_from_recipient = yes to the plugin section in dovecot.conf. But still vacation replies are send with empty FROM: fields. Is there any further setting i have to change ? My Version is dovecot 2.3.16 (7e2e900c1a) on Ubuntu 22.04 . Here is my setting from dovecot -n : log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir mail_privileged_group = mail 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 Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_vacation_send_from_recipient = yes } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/localcerts/servercert_pub.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = passwd } verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = torben(a)garfield.no-work.to quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } regards TS

1 0

sasl database
by Jeff P 01 Jun '24

01 Jun '24

Hello, Is there a guide for using a customized SASL database for dovecot? for example, SQLite. Thanks in advance.

3 2

Pigenohole bad commands limits and proposed minor patch
by John Fawcett 01 Jun '24

01 Jun '24

Hi I was looking into Pigeonhole behaviour in the case of managesieve receiving invalid input either before or after login. I can see that there are hard coded limits after 3 sequential bad commands prior to authentication and 20 after authentication. I was wondering if there is a reason for those values. Sieve is a protocol that is used with software and except for the limited use case of testing it is not used by people typing manually. I don't know of a lot of sieve clients. Unfortunately the one I used in Thunderbird is no longer maintained, so I only have roundcube. But do legitimate sieve clients in general make a lot of mistakes? An additional doubt about errors that I am seeing is that differently to imap and pop3 there doen't appear to be a dedicated ssl port. I only have starttls configured. I do see what look like people trying to connect with ssl directly on port 4190, which with my configuration is never going to be valid. I am attaching a very simple proposed patch to make the error limits configurable via the following settings in conf.d/20-managesieve.conf with defaults as per the existing hard coded ones: managesieve_max_command_errors = 20 managesieve_login_max_command_errors = 3 I have similar doubts about imap error limits but I'll start with sieve ones. John

1 0

Unable to get quotas working
by Adam Miller 01 Jun '24

01 Jun '24

Ubuntu Version: Linux 6.2.0-1017-aws x86_64 Ubuntu 22.04.4 LTS nfs4 Postfix: Version: 3.6.4 Dovecot Version: 2.3.16 (7e2e900c1a) Pigeonhole Version: 0.5.16 (09c29328) Rspamd Version: 3.8.4 Protocols: IMAP, LMTP, SMTP Setup: I have an email server running with virtual domains and virtual mailboxes that is currently hosting about 10GB of email across 15 domains and 8 mailboxes which will expand drastically once I get this to work. The server is an AWS EC2 instance with an AWS RDS instance for the database and using AWS EFS for storage. Everything works quite well except quotas! Problem: I am having an issue with getting quotas to work. When using “doveadm”, I can list the mailboxes however the “Limit” column is just a hyphen “-“ like there is no limit even though every account is set to 10GB for their limit in the database. At the same time, the actual used storage and messages is not getting updated in the database either yet there are no errors from what I can see in the logging. Configuration from “dovecot -n”: auth_debug = yes auth_mechanisms = plain login auth_verbose = yes auth_worker_max_count = 5 base_dir = /var/run/dovecot debug_log_path = /var/log/dovecot/debug.log default_internal_group = ardaemail default_internal_user = ardaemail dict { quota = mysql:/etc/dovecot/inc.d/inc.quota.user.sql.conf } info_log_path = /var/log/dovecot/info.log instance_name = ec2-us-east-1a-arda-mail-001.ardaemail.com listen = 172.16.0.200 log_path = /var/log/dovecot/general.log login_greeting = Welcome to ArdaEmail mail_debug = yes mail_gid = ardaemail mail_location = maildir:/mnt/mail/%d/%n mail_plugins = " quota" mail_uid = ardaemail maildir_stat_dirs = yes namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = no special_use = \Drafts } mailbox Junk { auto = no autoexpunge = 30 days special_use = \Junk } mailbox "Junk E-mail" { auto = no autoexpunge = 30 days special_use = \Junk } mailbox "Junk Email" { auto = no autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = no special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = no autoexpunge = 30 days special_use = \Trash } prefix = } passdb { args = /etc/dovecot/inc.d/inc.sql.conf driver = sql } plugin { imapsieve_mailbox1_before = file:/etc/dovecot/sieve.d/spam/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve.d/spam/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * quota = dict:quota::proxy::quota quota_exceeded_message = 452 4.2.2 Mailbox is full and cannot receive any more emails recipient_delimiter = + sieve_after = /etc/dovecot/sieve.d/after/ sieve_before = /etc/dovecot/sieve.d/before/ sieve_extensions = +spamtest +spamtestplus +virustest +notify +imapflags sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_quota_max_storage = 0 sieve_spamtest_max_header = X-Spam-Score: -?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]) sieve_spamtest_status_header = X-Spam-Score: (-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]] sieve_spamtest_status_type = score } protocols = imap lmtp service auth-worker { group = ardaemail user = ardaemail } service auth { group = ardaemail unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = ardaemail mode = 0666 user = ardaemail } user = ardaemail } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service imap { group = ardaemail user = ardaemail } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } service submission-login { inet_listener submission { port = 0 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.ardaemail.com/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/inc.d/inc.sql.conf driver = sql } verbose_ssl = yes protocol imap { mail_plugins = " quota imap_sieve imap_quota quota" } protocol lmtp { mail_plugins = " quota sieve imap_quota quota" } Configuration for “/etc/dovecot/inc.d/inc.quota.user.sql.conf”: connect = host=mydb dbname=mydb user=mydbuser password=mydbpass map { pattern = priv/quota/storage table = mailbox username_field = email value_field = size } map { pattern = priv/quota/limit/storage table = mailbox username_field = email value_field = quota } map { pattern = priv/quota/messages table = mailbox username_field = email value_field = size_messages } map { pattern = priv/quota/limit/storage table = mailbox username_field = email value_field = quota_messages } Configuration from “/etc/dovecot/inc.d/inc.sql.conf”: driver = mysql connect = host=mydb dbname=mydb user=mydbuser password=mydbpass default_pass_scheme = BLF-CRYPT password_query = SELECT email AS user, password FROM mailbox WHERE email = '%u'; user_query = SELECT maildir AS home, 10000 AS uid, 10000 AS gid, 'dict:quota::proxy::quota' AS quota FROM mailbox WHERE email = '%u'; iterate_query = SELECT email AS username, size, 'dict:quota::proxy::quota' AS quota FROM mailbox ORDER BY domainName ASC, email ASC; Database Table: “mailbox” CREATE TABLE `mailbox` ( `id` int(11) unsigned NOT NULL AUTO_INCREMENT, `uuid` varchar(36) NOT NULL, `domainUuid` varchar(36) NOT NULL, `domainName` varchar(96) DEFAULT NULL, `username` varchar(96) NOT NULL DEFAULT '', `password` varchar(128) NOT NULL, `firstname` varchar(32) NOT NULL, `lastname` varchar(32) NOT NULL, `email` varchar(192) NOT NULL DEFAULT '', `maildir` text NOT NULL, `quota` bigint(24) NOT NULL DEFAULT 0, `quota_messages` bigint(24) NOT NULL DEFAULT 0, `size` bigint(24) NOT NULL DEFAULT 0, `size_messages` bigint(24) NOT NULL DEFAULT 0, `isActive` tinyint(1) NOT NULL DEFAULT 1, `createdAt` datetime NOT NULL DEFAULT current_timestamp(), `updatedAt` datetime NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(), PRIMARY KEY (`id`), UNIQUE KEY `UNIQUE_UUID` (`uuid`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci; Where “username” is the first part of the email address and “email” is the full email address. I need to query using the full email address because of possible cross domain email addresses. Output from “doveadm quota get -A”: Username Quota name Type Value Limit % HIDDEN quota STORAGE 570742 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 1 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 1 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 1068 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 462 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 41165 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 1598246 - 0 HIDDEN quota MESSAGE 0 - 0 HIDDEN quota STORAGE 695776 - 0 HIDDEN quota MESSAGE 0 - 0 I have no idea what is wrong and I have been at this for over 12 hours trying to get the quotas to work. What I am expecting us when emails are delivered for the “quota” and “messages” columns in the “mailbox” table to be updated and when I run “doveadm quota get -A” to show me the current usages and limits for each mailbox. Once I have that working, I will move on to actually rejecting emails via Postfix + Dovecot LMTP when a users mailbox is full but right now, I am just trying to get this to work. Any help is greatly appreciated. Also, I tried creating an account for the mailing list but never received the email. Thank you!

3 5

Gather statistics to check effectivity of spam filter?
by Camilo Sperberg 30 May '24

30 May '24

Hi list :) We want to make some changes to our spam filter, but we first want to be able to check if what we do does have any effect. So I was thinking of storing in our statistics if somebody moves an email to their Junk folder (or even better: vice versa). I have created the following metric for this: metric imap_command_move { filter = event=imap_command_finished AND cmd_name="UID MOVE" AND (cmd_args = "* Junk" OR cmd_args = "* INBOX") group_by = cmd_args } And when I move something to the Junk folder I get the following after a doveadm stats dump: (...) imap_command_move duration 5 252529 27061 124989 50505.80 34476 37503.81 124989 imap_command_move_15_Junk duration 1 124989 124989 124989 124989.00 124989 0.00 124989 imap_command_move_14_Junk duration 1 38725 38725 38725 38725.00 38725 0.00 38725 imap_command_move_12_INBOX duration 1 27061 27061 27061 27061.00 27061 0.00 27061 imap_command_move_13_INBOX duration 1 27278 27278 27278 27278.00 27278 0.00 27278 imap_command_move_3_INBOX duration 1 34476 34476 34476 34476.00 34476 0.00 34476 In my example, I moved 6 messages: 2 from INBOX to Junk, 1 from INBOX to a separate folder, 2 from Junk back to INBOX and 1 from the separate folder back to INBOX. However, because I'm grouping by cmd_args, it includes the full parameters: IMAP command’s full parameters (e.g. 1:* FLAGS) https://doc.dovecot.org/admin_manual/list_of_events/#imap-command Is there a way to filter out the first part so that I ideally get a stat named imap_command_move_Junk & imap_command_move_INBOX? Is there perhaps a way to get to know specifically the from and to folders the user is moving the mail from and to? Thanks!

1 0

mbox parsing failed and crashed
by runtomaker＠gmail.com 28 May '24

28 May '24

In below data getting from Postfix. Dovecot imap protocol when fetching mails returns no data. So program crashing when parsing mbox file. Mbox file: "From info(a)asd.com Tue May 28 14:53:11 2024 Return-Path: <info(a)asd.com> X-Original-To: test(a)example.com Delivered-To: test(a)example.com Subject: asd " Error: "Panic: file istream-header-filter.c: line 663 (i_stream_header_filter_snapshot_free): assertion failed: (snapshot->mstream->snapshot_pending)"

1 1

Oauth2 MFA config
by Scott Q. 24 May '24

24 May '24

Anyone managed to get Dovecot working as smoothly with OAUTH2 as Gmail has with Outlook ? So that for example when you add the account up in Outlook it performs all the required steps for saving the device, getting tokens, etc. Ideally with a custom ID provider, not Google as described here: https://doc.dovecot.org/configuration_manual/authentication/oauth2/

2 1

I can't configure shared mailbox ACLs using LDAP information
by moso.mosoleu＠gmail.com 24 May '24

24 May '24

It shouldn't be impossible, but I've tried countless ways and not even ChatGPT 4o was able to help me! :D I use three LDIF files to get OpenLDAP ready for testing. In the first LDIF I just modify the schema to add the associatedDomain attributes (then I could configure the server to serve more than one domain). The second LDIF is to add 4 objects to the schema that I use to differentiate accounts that actually receive/send emails and have a password; another thing done in it is to add a "groupOfUniqueNamesWithMail" object that allows the "mail" and "mailEnabled" attributes that are then necessary to use in the entries created in the "shared-mailboxes" OU. Finally, the third LDIF populates the LDAP by creating OUs, user accounts and creating entries in "shared-mailboxes" that serve to say which user accounts have access to which other user accounts. When I start the email server, sending and receiving emails works perfectly. And mailbox shares work as expected if I manually use, for each share, the command: doveadm acl set -u admin(a)mydomain.com.br INBOX user=user.1(a)mydomain.com.br lookup read write write-seen write-deleted insert post expunge create delete But just as authentication works perfectly via LDAP, I believe there must be a way to configure Dovecot to dynamically adjust ACLs via LDAP. The configuration in principle would be this: acl_search_base = ou=shared-mailboxes,dc=mydomain,dc=com,dc=br acl_search_filter = (&(objectClass=groupOfUniqueNamesWithMail)(|(uniqueMember=mail=%u,ou=system-accounts,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=department-accounts ,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=mailing-accounts,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=person -accounts,dc=mydomain,dc=com,dc=br))) acl_user = %u Testing this filter on the command line with "ldapsearch" the expected results are returned. I mean, I enter an email address from a user account and the result is all the other user account email addresses that the first one would have access to. Any charitable soul who is willing to help and needs more information, just say what you need and I will try to respond as quickly as possible. I will place the content of the three LDIFs below. [ 01-modify_domain.ldif ] dn: dc=mydomain,dc=com,dc=br changetype: modify add: objectClass objectClass: domainRelatedObject - add: associatedDomain associatedDomain: mydomain.com.br - add: associatedDomain associatedDomain: anotherdomain.com.br [ 02-add_my_object_classes_to_schema.ldif ] # Object class for system user accounts dn: cn=SystemAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: SystemAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.1 NAME 'SystemAccount' DESC 'Object class for system accounts' SUP top AUXILIARY ) # Object class for department user accounts dn: cn=DepartmentAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: DepartmentAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.2 NAME 'DepartmentAccount' DESC 'Object class for department accounts' SUP top AUXILIARY ) # Object class for mailing user accounts dn: cn=MailingAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: MailingAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.3 NAME 'MailingAccount' DESC 'Object class for mailing accounts' SUP top AUXILIARY ) # Object class for person user accounts dn: cn=PersonAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: PersonAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.4 NAME 'PersonAccount' DESC 'Object class for person accounts' SUP top AUXILIARY ) # Object class that allows groupOfUniqueNames to have a mail attribute dn: cn=groupOfUniqueNamesWithMail,cn=schema,cn=config objectClass: olcSchemaConfig cn: groupOfUniqueNamesWithMail olcObjectClasses: ( 1.3.6.1.4.1.99999.1.5 NAME 'groupOfUniqueNamesWithMail' SUP groupOfUniqueNames STRUCTURAL MAY ( mail $ mailEnabled ) ) [ 03-initialize_mydomain.com.br.ldif ] ### Create organizaitonal units dn: ou=system-accounts,dc=mydomain,dc=com,dc=br ou: system-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=department-accounts,dc=mydomain,dc=com,dc=br ou: department-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=mailing-accounts,dc=mydomain,dc=com,dc=br ou: mailing-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=person-accounts,dc=mydomain,dc=com,dc=br ou: person-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=shared-mailboxes,dc=mydomain,dc=com,dc=br ou: shared-mailboxes objectClass: organizaitonalUnit objectClass: top ################################################################################ ## Create System User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=admin(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: admin userPassword: {SSHA} displayName: My Domain - Admin givenName: System sn: Admin cn: System Admin mail: admin(a)mydomain.com.br mailAlias: root(a)mydomain.com.br mailAlias: postmaster(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/admin/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/admin/ descripiton: My Domain - Admin (root/postmaster) objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=smtp(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: smtp userPassword: {SSHA} displayName: My Domain - SMTP givenName: System sn: SMTP cn: System SMTP mail: smtp(a)mydomain.com.br mailAlias: no-reply(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/smtp/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/smtp/ descripiton: My Domain - System SMTP objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=smtp-auditor(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: smtp-auditor userPassword: {SSHA} displayName: My Domain - SMTP Auditor givenName: System sn: SMTP Auditor cn: System SMTP Auditor mail: smtp-auditor(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/smtp-auditor/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/smtp-auditor/ descripiton: My Domain - System SMTP Auditor objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Department User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=it(a)mydomain.com.br,ou=department-accounts,dc=mydomain,dc=com,dc=br uid: it userPassword: {SSHA} displayName: My Domain - Information Technology givenName: My Domain sn: IT cn: My Domain - IT mail: it(a)mydomain.com.br mailAlias: information.technology(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/department-accounts/it/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/department-accounts/it/ descripiton: My Domain - Information Technology (IT) objectClass: PostfixBookMailAccount objectClass: DepartmentAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Mailing User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=everyone(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: everyone userPassword: {SSHA} displayName: My Domain - Everyone givenName: My Domain sn: everyone cn: My Domain - Everyone mail: everyone(a)mydomain.com.br mailAlias: everyone(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/everyone/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/everyone/ descripiton: My Domain - Everyone mailing list objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=mailing.list.1(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: mailing.list.1 userPassword: {SSHA} displayName: My Domain - Mailing List 1 givenName: My Domain sn: Mailing List 1 cn: My Domain - Mailing List 1 mail: mailing.list.1(a)mydomain.com.br mailAlias: ml.1(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/mailing.list.1/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/mailing.list.1/ descripiton: My Domain - Mailing List 1 objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=mailing.list.2(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: mailing.list.2 userPassword: {SSHA} displayName: My Domain - Mailing List 2 givenName: My Domain sn: Mailing List 2 cn: My Domain - Mailing List 2 mail: mailing.list.2(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/mailing.list.2/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/mailing.list.2/ descripiton: My Domain - Mailing List 2 objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Person User Accounts dn: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.1 userPassword: {SSHA} displayName: User 1 givenName: User sn: 1 cn: User 1 mail: user.1(a)mydomain.com.br mailAlias: user.one(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.1/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.1/ descripiton: My Domain - User 1 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.2 userPassword: {SSHA} displayName: User 2 givenName: User sn: 2 cn: User 2 mail: user.2(a)mydomain.com.br mailAlias: user.two(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.2/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.2/ descripiton: My Domain - User 2 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.3 userPassword: {SSHA} displayName: User 3 givenName: User sn: 3 cn: User 3 mail: user.3(a)mydomain.com.br mailAlias: user.three(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.3/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.3/ descripiton: My Domain - User 3 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## for Shared System User Accounts dn: cn=admin(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: admin(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared Department User Accounts dn: cn=it(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: it(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared Mailing User Accounts dn: cn=everyone(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: everyone(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top dn: cn=mailing.list.1(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: mailing.list.1(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top dn: cn=mailing.list.2(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: mailing.list.2(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared User Accounts dn: cn=user.2(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: user.2(a)mydomain.com.br mailEnabled: FALSE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top

3 3

Command "doveadm director kick ...." doesn't work
by g.carabella＠panservice.it 23 May '24

23 May '24

Hi, I have a Dovecot installation (version 2.3.16) with 3 directors and 4 backend servers. Three backend servers have the director_tag 'new', one has the director_tag 'old'. The users are on the DB, the director_tag is a table field. I want to migrate mailboxes from the old backend (Maildir format) to the new (mdbox format). For the migration I use the "doveadm backup" command and everything works fine. The problem I'm having is that I can't kick the user (if logged in). Once the migration is done (as indicated https://doc.dovecot.org/3.0/man/doveadm-sync.1/) I modify the user's home, mail_location and director_tag and then execute the command "doveadm director kick ..." but the connection on the directors is not killed. Why does this problem occur? Could it be due to the use of the director_tag and the fact that for the command "doveadm director kick ..." it is not possible to specify it? Even if I run the command "doveadm director move mailbox_account new_backend_server", the director adds a new connection but does not kill the previous one, with the result that there are two connections for the same user, one on the new backend and one on the old one. I also tried to configure the director_tag only for the 3 new servers, but the "director kick" still doesn't work.

1 0

Problems using non-libc memory allocators
by bl0v3 22 May '24

22 May '24

Hey I was trying to use dovecot2 with a not libc based memory allocation such as scudo or graphene-hardened or graphene-hardened-light but ran into the issues I described in https://github.com/NixOS/nixpkgs/issues/313721 I just wanted to mention this here as well as this behavior may suggest a flaw in the memory allocation mechanism of dovecot2/anvil. I haven't yet found the time to check the underlaying issue as I'm quite busy rn. So I thought id just mention what I came across in case this is actually unexpected or potentially even security relevant mis/behavior.

2 1

Dovecot calculating quota wrong or am I stupid?
by jarland＠mxroute.com 21 May '24

21 May '24

I'm currently running 2.3.21 on this system and here's what I'm seeing (a bit cut down for excess): # doveadm quota get -u emailuser(a)domain.net STORAGE 1052385 MESSAGE 2741 So the storage is roughly more than 1GB according to Dovecot. No change after quota recalc. But: root@arrow:/home/username/imap/domain.net# du -sh emailuser 692M emailuser There are no symlinks or anything like that. Quota config is pretty basic: root@arrow:/etc/dovecot# cat conf.d/90-quota.conf #add quota to end of line in: #/etc/dovecot/conf/mail_plugins.conf, eg: #mail_plugins = $mail_plugins quota #add imap_quota to end of line in: #/etc/dovecot/conf/imap_mail_plugins.conf, eg: #mail_plugins = $mail_plugins imap_quota plugin { quota = maildir } If anyone has advice I would greatly appreciate it.

1 1

Re: After user disconnect run the custom script
by Michael Slusarz 20 May '24

20 May '24

> On 05/20/2024 9:43 AM MDT Alexey Krylov via dovecot <dovecot(a)dovecot.org> wrote: > > Please, send me the link, where I can find the info about configuring > firing script after dovecot client is disconnected. > > I found post-login scripting. Than's cool, but... I need to fire script > a little bit later. See https://doc.dovecot.org/admin_manual/list_of_events/#mail-user-session-fini… You will need to build a event listener for this event, and then do your scripting in there. michael

1 0