March 2021 - dovecot - dovecot.org

Panic: file mdbox-map.c: line 1494 (mdbox_map_get_uid_validity): assertion failed: (map->view != NULL)
by Marc 12 Mar '21

12 Mar '21

Does this mean I have some problems with filesystem uid's? Currently I have only u=rwx, go is nothing. dovecot-2.2.36-6.el7_8.1.x86_64

3 8

auto scaling dovecot server on AWS
by girivasan.rajasekaran＠minfytech.com 10 Mar '21

10 Mar '21

Hello There - I'm trying to setup dovecot server on AWS and would like to understand the approach on the email server sizing? The emails are expected to surge at times seasonally. How do I plan the email server sizing to handle such load? Does this support auto-scaling? Probably I'm missing the basics. Appreciate your help in giving some clarity.

1 0

invalid vsize-hdr
by Christopher Wensink 10 Mar '21

10 Mar '21

Good afternoon everyone, I have one account on our internal dovecot server that keeps throwing the same repeated error: The user is on a Windows 10 computer running the latest version of Thunderbird. Here's the log: -------------------------------------------------------------------------------------------------------------------- Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has invalid size: 36 Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=1578244 out=2878370 Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, session=<AvLvkCC9w9kKBQFN> Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=319541 out=1272761 Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, session=<85YInSC95NkKBQFN> Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 --------------------------------------------------------------- I have tried the following: -Restarting the workstation - Compacting folders in Thunderbird - Repaired the Inbox Folder in Thunderbird - Restarting the dovecot service - Set the connections in Thunderbird Account settings to not check for messages automatically (manual only) - Set the user to own all folders and sub-folders in his home directory on the server I found old message in the archives from 2017 that had the same error but I did not see a posted solution. dovecot --version 2.2.36 (lfl0bfa63) config file: [root@mario2 dovecot]# cat dovecot.conf ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Protocols we want to be serving. #protocols = imap pop3 lmtp protocols = imap pop3 # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Name of this instance. In multi-instance setup doveadm and other commands # can use -i <instance_name> to select which instance is used (an alternative # to -c <config_path>). The instance name is also added to Dovecot processes # in ps output. #instance_name = dovecot # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = login_trusted_networks = 10.5.1.0/24 # Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do # proxying. This isn't necessary normally, but may be useful if the destination # IP is e.g. a load balancer's IP. #auth_proxy_self = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf ----------- I need assistance. I appreciate the help. Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwensink(a)five-star-plastics.com www.five-star-plastics.com

6 6

DMARC problems with some emails from the list
by Ángel L. Mateo 09 Mar '21

09 Mar '21

Hello, I'm having problems with some emails from the list, been classified as SPAM in my system because of DMARC failures. I'm not sure but this may be a problem with the list configuration. I attach the log for the failures in the last week. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

3 8

Dovecot v2.3.14 released
by Aki Tuomi 09 Mar '21

09 Mar '21

Hi! We are pleased to release v2.3.14 of Dovecot. IMPORTANT NOTE: We have removed some components from the software, please review changelogs carefully prior upgrading. Please find source tarballs at https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * Added new aliases for some variables. Usage of the old ones is possible, but discouraged. (These were partially added already to v2.3.13.) See https://doc.dovecot.org/configuration_manual/config_file/config_variables/ for more information. * Optimize imap/pop3/submission/managesieve proxies to use less CPU at the cost of extra memory usage. * Remove autocreate, expire, snarf and mail-filter plugins. * Remove cydir storage driver. * Remove XZ/LZMA write support. Read support will be removed in future release. * doveadm -D: Add timestamps to debug output even when LOG_STDERR_TIMESTAMP environment variable is not set. Timestamp format is taken from log_timestamp setting. * If BROKENCHAR or listescape plugin is used, the escaped folder names may be slightly different from before in some situations. This is unlikely to cause issues, although caching clients may redownload the folders. * imapc: It now enables BROKENCHAR=~ by default to escape remote folder names if necessary. This also means that if there are any '~' characters in the remote folder names, they will be visible as "~7e". * imapc: When using local index files folder names were escaped on filesystem a bit differently. This affects only if there are folder names that actually require escaping, which isn't so common. The old style folders will be automatically deleted from filesystem. * stats: Update exported metrics to be compliant with OpenMetrics standard. + doveadm: Add an optional '-p' parameter to metadata list command. If enabled, "/private", and "/shared" metadata prefixes will be prepended to the keys in the list output. + doveconf: Support environment variables in config files. See https://doc.dovecot.org/configuration_manual/config_file/config_file_syntax… for more details. + indexer-worker: Change indexer to disconnect from indexer-worker after each request. This allows service indexer-worker's service_count & idle_kill settings to work. These can be used to restart indexer-worker processes once in a while to reduce their memory usage. - auth: "nodelay" with various authentication mechanisms such as apop and digest-md5 crashed AUTH process if authentication failed. - auth: Auth lua script generating an error triggered an assertion failure: Panic: file db-lua.c: line 630 (auth_lua_call_password_verify): assertion failed: (lua_gettop(script->L) == 0). - configure: Fix libunwind detection to work on other than x86_64 systems. - doveadm-server: Process could crash if logging was done outside command handling. For example http-client could have done debug logging afterwards, resulting in either segfault or Panic: file http-client.c: line 642 (http_client_context_close): assertion failed: (cctx->clients_list == NULL). - dsync: Folder name escaping with BROKENCHAR didn't work completely correctly. This especially caused problems with dsync-migrations using imapc where some of the remote folder names may not have been accessible. - dsync: doveadm sync + imapc doesn't always sync all mails when doing an incremental sync (-1), which could lead to mail loss when it's used for migration. This happens only when GUIDs aren't used (i.e. imapc without imapc_features=guid-forced). - fts-tika: When tika server returns error, some mails cause Panic: file message-parser.c: line 802 (message_parser_deinit_from_parts): assertion failed: (ctx->nested_parts_count == 0 || i_stream_have_bytes_left(ctx->input)) - lib-imap: imapc parsing illegal BODYSTRUCTUREs with NILs could have resulted in crashes. This exposed that Dovecot was wrongly accepting atoms in "nstring" handling. Changed the IMAP parsing to be more strict about this now. - lib-index: If dovecot.index.cache has corrupted message size, fetching BODY/BODYSTRUCTURE may cause assert-crash: Panic: file index-mail.c: line 1140 (index_mail_parse_body_finish): assertion failed: (mail->data.parts != NULL). - lib-index: Minor error handling and race condition fixes related to rotating dovecot.index.log. These didn't usually cause problems, unless the log files were rotated rapidly. - lib-lua: Lua scripts using coroutines or lua libraries using coroutines (e.g., cqueues) panicked. - Message PREVIEW handled whitespace wrong so first space would get eaten from between words. - FTS and message PREVIEW (snippet) parsed HTML &entities case-sensitively. - lib-mail: When max nested MIME parts were reached, IMAP BODYSTRUCTURE was written in a way that may have caused confusion for IMAP clients and also Dovecot itself when parsing it. The truncated part is now written out using application/octet-stream MIME type. - lib-oauth2: HS512 and HS384 JWT token algorithms crash when you try to use them: Panic: file hmac.c: line 26 (hmac_init): assertion failed: (meth->context_size <= MAC_MAX_CONTEXT_SIZE). - event filters: NOT keyword did not have the correct associativity. NOT a AND b were getting parsed as NOT (a AND b) instead of (NOT a) AND b. - Ignore ECONNRESET when closing socket. This avoids logging useless errors on systems like FreeBSD. - event filters: event filter syntax error may lead to Panic: file event-filter.c: line 137 (event_filter_parse): assertion failed: (state.output == NULL) - lib: timeval_cmp_margin() was broken on 32-bit systems. This could potentially have caused HTTP timeouts to be handled incorrectly. - log: instance_name wasn't used as syslog ident by the log process. - master: After a service reached process_limit and client_limit, it could have taken up to 1 second to realize that more client connections became available. During this time client connections could have been unnecessarily rejected and a warning logged: Warning: service(...): process_limit (...) reached, client connections are being dropped - stats: Crash would occur when generating openmetrics data for metrics using aggregating functions. - stats: Event filters comparing against empty strings crash the stats process.

5 5

start dovecot multiple instances
by Gonzalo Palacios Goicolea 08 Mar '21

08 Mar '21

Hi All, I'm trying to run dovecot with dovecot-director on the same server, using two different instances, but I'n not able to make the two instances start with systemctl (we are using RHEL7) May be I shueld create a /etc/systemd/system/dovecot.service.d/service.conf file and add there any command? Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco

2 1

director implementation
by Gonzalo Palacios Goicolea 08 Mar '21

08 Mar '21

Hi All, We're going to put into production dovecot-director. As I wrote in a previous message, we have a lot of errors like these: Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Log is locked - newer log can't exist (initial_mapped=1, reason=Index mapped) Feb 28 08:50:42 server5 dovecot: imap(user@domain): Warning: fscking index file path/Maildir/dovecot.index Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged (initial_mapped=1, reason=Index mapped) Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map view for path/Maildir/dovecot.index: Missing middle file seq=5 (between 5..5, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged My doubt is if it's recommended to delete all dovecot.index* files before passing the traffic through de director servers or it's not required. Any information on this way will be appreciated. We've dovecot-2.2.36-8.el7.x86_64 over RHEL7 Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/"> Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.

2 1

not getting internal errors logged
by Arkadiusz Miśkiewicz 08 Mar '21

08 Mar '21

Hello. dovecot 2.3.13, 2.3.14 web imap client when doing search is getting error induced by me by deleting lucene-indexes folder: UID SEARCH: Internal error occurred. Refer to server log for more information. [2021-03-08 15:08:01] (0.002 + 0.000 + 0.001 secs). but I'm not getting that internal error logged in syslog. Other information like from lmtp, imap logging in, out etc is logged just fine. In my configs log_path info_log_path debug_log_path are not set, so dovecot default syslog is used. Tested log_path = /tmp/file.txt, too but the effect was the same (regular logs logged there, internal errors not logged) stracing dovecot process I see error message only write()n once (to client) but nowhere else (in a strace visible way). Is anything else controlling internal errors logging? Can't find anything in docs. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Mailbox configuration questions
by justina colmena ~biz 08 Mar '21

08 Mar '21

I am having subtle problems with IMAP mailbox configuration on certain clients such as KMail and Thunderbird, whereas the previous setup was working on K9Mail (mobile) and Trojitá (desktop). I was using Maildir folders, which were mostly working before, but for some reason I had to create explicitly named namespaces for the flatfile (mbox) Inbox and the Maildir "Home" folders. I also specified an INDEX directory for the inboxes, which I made world-writable and sticky, because of permission problems creating subdirectories in it. KMail always seems to put sent mail into a local "sent-mail" folder, rather than the IMAP Sent folder associated with the sending account. (KMail and Thunderbird have a more POP-oriented architecture for the desktop, whereas Trojitá is exclusively IMAP.) Is there an easier better way to organize some of this stuff? Or how is it "usually" done?

3 2

Re: Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
by Roland Martinez 05 Mar '21

05 Mar '21

1 0