- dovecot - dovecot.org

error: no member named 'st_ctim' in 'struct stat'
by Lasse Törngren 09 Apr '24

09 Apr '24

Hello James, I get the exact same error when trying to compile Dovecot 2.3.21 on both Mac OS Monterey 12.7.3 and Mac OS Ventura 13.6.4. dbox-storage.c:296:32:error:no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24:error:no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; Dovecot 2.3.20 compiles without any issue. Did you ever understand how to solve the problem? Best regards Lasse Törngren Hello James, I get the exact same error when trying to compile Dovecot 2.3.21 on both Mac OS Monterey 12.7.3 and Mac OS Ventura 13.6.4. dbox-storage.c:296:32:error:no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24:error:no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; Dovecot 2.3.20 compiles without any issue. Did you ever understand how to solve the problem? Best regards Lasse Törngren

1 0

doveadm sync - I/O has stalled
by songliny 09 Apr '24

09 Apr '24

Hi All, We are using dovecot 2.3.19.1 We created a account with more than 1000 mail folders in Maildir format to reproduce the issue. After weeks of testing, we have found a logic that may cause dsync to encounter the error - no activity for 900 seconds.... The function, dsync_ibc_stream_input, is the callback function after some data are ready for be read. This is part of what it does. o_stream_cork(ibc->output); ibc->ibc.io_callback(ibc->ibc.io_context); o_stream_uncork(ibc->output); Normally, ibc->ibc.io_callback(ibc->ibc.io_context) reads some data and then processes it. But when dsync connects over tcps, it uses function implementations in lib-ssl-iostream to send and receive data. And this simplified call stack would result in some data are read when calling o_stream_uncork o_stream_uncork => o_stream_flush => o_stream_ssl_flush_buffer => openssl_iostream_bio_sync => openssl_iostream_bio_input If some data arrive after ibc->ibc.io_callback(ibc->ibc.io_context) and before o_stre am_uncork, o_stream_uncork would read the data and then return. After o_stream_uncork returns, dsync then waits for new data to be read or written. But because the data had been read in o_stream_uncork, and there may be no new data to be read, dsync may then wait until timeout is met. It may happen, but it is hard to reproduce. If you also encounter this situation, you may try to use dsync over tcp connection. It does not read data when calling o_stream_uncork. As a result, it may not stuck. Back to the error itself, Maybe openssl-stream should not read data when doing uncork(flush)? Song-Lin Yang

2 4

DMARC setting change
by Aki Tuomi 05 Apr '24

05 Apr '24

We've changed the list dmarc mitigation to happen unconditionally now. This will likely have an impact on people's mails, so this is a headsup for everyone so they know. Please let me know if this causes too much bother, but keep in mind that right now lot of emails are being bounced and rejected. Aki

3 2

Re: Users with enough rope to hang themselves
by Joseph Tam 05 Apr '24

05 Apr '24

Rupert Gallagher writes: > I keep finding myself in a corner with a user. He uses mail extensively, which > is fine, he has a huge archive of own professional correspondence, which is > fine, but he uses mail folders as if they were regular system folders, with > very long paths, and keeps renaming them and moving them around, daily, > breaking the mail index Tangentially query: is Dveocot smart enough to optimize mailbox renaming to do index renaming (i.e. does not try to copy or recreate indices)? > and ultimately wasting his own time looking around for > lost mail. His Inbox holds a gargantuan of subfolders, causing both the client > and the server to overwork each time he opens the mail. His Archive is a maze > of subfolders with repeating names. I advised him almost daily across 20 year > on how to stay organised, but he keeps abusing the service. Semantically, he may be inept/disorganized/unappreciative, but I wouldn't raise this to abuse. However, the damages are often the same. Maybe the fix is not technical but social by making it clear you're done trying to fix his mistakes and he's on his own. Just sayin'. > I want to help him by limiting what he can do with folders. This is the agenda: > 1. the Archive is the only place where he can create folders; I'm guessing https://doc.dovecot.org/configuration_manual/acl/ > 2. folder names have a maximum length of 20 characters. No clue here: maybe artful remapping of namespaces? https://doc.dovecot.org/configuration_manual/mail_location/#custom-namespac… Joseph Tam <jtam.home(a)gmail.com>

5 13

2.4 ballpark release date?
by Shawn Heisey 05 Apr '24

05 Apr '24

I'm wondering whether there is a ballpark release date for Dovecot 2.4. I know an exact release date is probably not available, but can it at least be narrowed to a specific quarter? Is it likely in 2023? I have seen on previous messages that an Ubuntu repository for 22.04 (jammy) will appear with the 2.4 release. My mail server in AWS is running Ubuntu 20.04 (focal), which I have avoided upgrading for various reasons, including websites that don't work with PHP 8.1. Now the last remaining hurdle is the fact that there is no dovecot repository for jammy. I would prefer the official Dovecot repo over dovecot packages included with Ubuntu, because it's likely to be a newer release, and built from vanilla project code. At the moment jammy includes dovecot 2.3.16, which is even older than the 2.3.20 that I am running on focal from the official dovecot repo. Again, I know that a precise release date won't be possible. I'm just hoping for something like "soon" or "in about six months." Thanks, Shawn

3 5

Re: Fwd: Dovecot, Load Balancing and SSL
by Joseph Tam 04 Apr '24

04 Apr '24

leon(a)relay.gb.net writes: > I wonder if someone would provide me with some advice. I've been setting > up a couple of Postfix servers just for fun. I've got two Postfix > servers m1.domain.com and m2.domain.com. I can send and receive mail via > both of them. Ive also got Postfixadmin and RoundCube on them and I'm > replicating the database over both servers. > > I introduced a load balancer. Postfixadmin and Roundcube work perfectly. > However. When I send mail from Thunderbird. M1 reports that the > certificate does not match. It's expecting a certificate for > mail.domain.com. Complaints when you're sending mail? This is not Dovecot's problem, but Postfix's. If you're setting your SMTP outgoing to M1, then the certificate M1 uses have M1 as a subject. If you're setting the outgoing mail server as "mail.domain.com" load balanced to M1/M2, then both your Postifx servers need to use the same certificate with "mail.domain.com" as a subject. Simple as that. Joseph Tam <jtam.home(a)gmail.com>

1 0

Dovecot, Load Balancing and SSL
by leon＠relay.gb.net 03 Apr '24

03 Apr '24

Hi Everyone! I wonder if someone would provide me with some advice. I've been setting up a couple of Postfix servers just for fun. I've got two Postfix servers m1.domain.com and m2.domain.com. I can send and receive mail via both of them. Ive also got Postfixadmin and RoundCube on them. I introduced a load balancer. Postfixadmin and Roundcube work perfectly. However. When I send mail from Thunderbird. M1 reports that the certificate does not match. It's expecting a certificate for mail.domain.com. On M1 I thought I would try to specify the location of the SSL when using mail.domain.com. I placed the certificate in the NAS and specified it in the 10-ssl file. I did this as per the docs. mail.domain.com local_name mail.domain.com { ssl_cert = </nas/ssl/fullchain.pem ssl_key = </nas/ssl/privkey.pem } It doesn't work. And I'm not entirely sure why M2 works and M1 doesn't. As far as I can see I haven't specified or placed a certificate for mail.domain.com on M2 and searching my bash history doesn't produce anything related to mail.domain.com. So how can I load balance email connections over my two servers without getting a damn certificate warning? Any help would be much appreciated. Thanks.

2 3

Any way to make a shared mailbox(not a shared folder)
by Maksim Rodin 02 Apr '24

02 Apr '24

Hello I wonder if there is a right way to make a shared mailbox? I do not mean "shared folder" but a whole mailbox. E.g. I have a mailbox info(a)company.com and I have a user mailbox user1(a)company.com. I would like that a user which can already authenticate as user1(a)company.com can setup another account in his Thunderbird as, say, user1@company.com\info@company.com or something like user1*info, enters his own password and can use the mailbox info(a)company.com as his second mailbox. It might be something similar to master user feature but I do not want the user1(a)company.com to have access to all the mailboxes on the dovecot imap server. -- Regards Maksim Rodin

4 6

Implications of LMTP socket being world readable and writable (0666) by default
by da-dovecotlist-15＠abelonline.de 31 Mar '24

31 Mar '24

I was surprised to find that the LMTP socket has permission mode 0666 by default and since configs are merged with defaults, there is no way to disable this AFAICS. # doveconf -d ... service lmtp { unix_listener lmtp { group = mode = 0666 user = } ... } Is this also how it is supposed to be used in production? I understand that LMTP is just for delivering new mails but is there really no need to restrict this further? To me it seems reasonable, to force all services on this machine to go through Postfix and not be able to just put e-mails in the users mailboxes via LMTP. Am I missing something? My use case is a "small" NixOS mail server with Postfix, Nextcloud a.o. installed on the same machine. No chroot jails because of NixOS.

3 4

Re: [Dovecot] [dovecot-2.1.15] mdbox corruption, doveadm force-resync can't repair it (throws segfault)
by Manish Prajapati 31 Mar '24

31 Mar '24

3 2