- dovecot - dovecot.org

auth_mechanisms per listener or local_name?
by Kees van Vloten 01 Dec '23

01 Dec '23

Hi all, I would like to use kerberos authentication on the local network but not for connections from internet, which are forwarded by haproxy. So both types of login can be distinguished by a different inet_listener and also a different by local_name. Is there a way to set auth_mechanisms such the it will impossible to use kerberos via haproxy connections or by filtering on local_name? - Kees.

1 0

client port int auth-worker log
by Joao Reis 29 Nov '23

29 Nov '23

Hello, Can the client's port number be included in the log entries generated by auth-worker, without needing to recompile Dovecot? Currently, the log entries look like this: |auth-worker(3538137): sql(user(a)domain.tld,123.123.123.123): Password mismatch | I would like the log entries to appear as follows: |auth-worker(3538137): sql(user(a)domain.tld,123.123.123.123,45343): Password mismatch | In this format, the client's port number (e.g., 45343) is also logged. thanks in advance. Hello, Can the client's port number be included in the log entries generated by auth- worker, without needing to recompile Dovecot? Currently, the log entries look like this: auth-worker(3538137): sql(user(a)domain.tld,123.123.123.123): Password mismatch I would like the log entries to appear as follows: auth-worker(3538137): sql(user(a)domain.tld,123.123.123.123,45343): Password mismatch In this format, the client's port number (e.g., 45343) is also logged. thanks in advance.

1 0

Re: Replication going away?
by Peter Wienemann 28 Nov '23

28 Nov '23

Hi, On 2023-11-28 16:20:56 +0100, gerben.wierda(a)rna.nl wrote: >From what version on is replication gone? I am running 2.3.20 and it still there. it will be gone from version 2.4/3.0 onward (see [0]). Best regards, Peter [0] https://doc.dovecot.org/3.0/installation_guide/upgrading/from-2.3-to-3.0

1 0

I've sent a question to dovecot@dovecot.org via mail. Why is it not ending up here?
by gerben.wierda＠rna.nl 28 Nov '23

28 Nov '23

This is what my postfix server says: Nov 28 14:23:12 albus postfix/qmgr[654]: 823D71CDE2714: from=<gerben.wierda(a)rna.nl>, size=9144, nrcpt=1 (que ue active) Nov 28 14:23:12 albus postfix/smtp[2294]: Untrusted TLS connection established to talvi.dovecot.org[94.237.1 05.223]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server -signature RSA-PSS (2048 bits) server-digest SHA256 Nov 28 14:23:13 albus postfix/smtp[2294]: 823D71CDE2714: to=<dovecot(a)dovecot.org>, relay=talvi.dovecot.org[9 4.237.105.223]:25, delay=2.1, delays=0.51/0.02/0.75/0.83, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E5 C425DEEF) Nov 28 14:23:13 albus postfix/qmgr[654]: 823D71CDE2714: removed But I can't see it here nor do I get it sent back to me.

1 0

OT? Maybe so, maybe no.
by joe a 27 Nov '23

27 Nov '23

Dovecot installation on OpenSuse LEAP 15.5. Works fine via Thunderbird. Roundcube install works great. Astonishing given my rusting skills. But only until . . . I try to send email. Then RoundCube tells me smtp error(): connection to server failed. Well, yeah, 'you're trying port 587, when I told you to use port 25. Whatareya, dense?'. Nah, yer just a machine, must be me. Posted on Roundcube board, views but no replies. Perhaps someone here knows what else I need to change besides: ~etc/roundcubemail/config.inc.php //$config['smtp_port'] = 587; $config['smtp_port'] = 25; I don't find any other relevant referenced to SMTP port in RC configuration.

2 5

Couldn't get vsize Issue
by duluxoz 26 Nov '23

26 Nov '23

Hi All, Looking for a little help, please. We're getting the following showing up in our dovecot logs: `Debug: Mailbox Junk: Couldn't get vsize from mailbox list index: Record for vsize`. This is happening for all(?) the different mailboxes We're not sure what we're looking at or looking for to even begin the t/shoot. I dropped the above into google but couldn't *seem* to find anything relevant. Would someone(s) be able to point me in the right direction as to what the actual issue is (ie some more in-depth detail than just the log message - yes, it may be obvious to some but not to me) and, more importantly, what to look at to get it resolved, please. :-) Thanks in advance Dulux-Oz

3 4

Re: How to temporarily make all mailboxes read-only for backup purposes?
by Matthias Nagel 26 Nov '23

26 Nov '23

I would like to avoid making a local deep copy first. This essentially doubles the required storage on the local disk and it also wears down the disk much faster as I will write gigabytes of data onto the disk every 24 hours. I would prefer an option which allows the backup program (Borg backup in my case) to only read the local data and send it to the remote backup space directly.

3 3

2 users who are the same user
by Michael Grant 26 Nov '23

26 Nov '23

I have been using system users (/etc/passwd). I recently started using, in addition, passwd-file with a separate dovecot password database so that I could have user@domainname users with a different password as their shell login password. This means I have dovecot authenticating on users in both /etc/passwd and /etc/dovecot/users. If I have a user in /etc/passwd, for example 'joe' and a user in /etc/dovecot/users, joe(a)example.org, and both of these users are in fact the same user but different password. They use the same inbox and the same mail files. Dovecot does not seem to like this very much. I am seeing many errors like this: Error: Mailbox INBOX: Sync failed for mbox: UID inserted in the middle of mailbox (4315358 > 4312144, seq=1, idx_msgs=3212) I think I'm causing this by having 2 users that are in fact the same user and dovecot is stepping on itself. Is it possible to tell Dovecot that these 2 users are in fact the same, as in like an alias user? Or is it possible to tell dovecot not to process mail for say for 'joe' the system user? Michael Grant

3 5

RE: How to temporarily make all mailboxes read-only for backup purposes?
by Matthias Nagel 25 Nov '23

25 Nov '23

> Why would you want to do that? Afaik sdbox stores email per file. There is also an index file which stores meta attributes per mail/file and I want them to be consistent. > The mta just delivers the email later and your backup is already old. That's not really am argument. Just imagine the mail would have been sent some moment later after the backup has been started. In that case the mail wouldn't be in the backup either. A backup on a regular schedule for catastrophe recovery always has the "issue" that it will be old by half the time of the schedule on average in case one really needs it. Regarding snapshots on ZFS an similar file system: Not an option as I am using a shared hoster and the file system does not allow snapshots. Am 22. November 2023 21:46:19 schrieb Marc <Marc(a)f1-outsourcing.eu>: > Why would you want to do that? Afaik sdbox stores email per file. The mta > just delivers the email later and your backup is already old. Are you > making a snapshot and backup that, that is a very short time window. > >> >> I am using Dovecot sdbox format for mailboxes. Is there an option to >> temporarily make Dovecot read-only while the mailboxes are being backed-up >> such that a consistent state is backed-up? >> >> I am looking for some command which I can use as pre- and post-hook for >> Borgbackup. I am looking for a way such that Dovecot defers any mail coming >> in via LMTP from Postfix, denies modifying mails/mailboxes via IMAP while >> Dovecot still allows to browse mails read-only.

2 1

How to temporarily make all mailboxes read-only for backup purposes?
by Matthias Nagel 24 Nov '23

24 Nov '23

Dear all, I am using Dovecot sdbox format for mailboxes. Is there an option to temporarily make Dovecot read-only while the mailboxes are being backed-up such that a consistent state is backed-up? I am looking for some command which I can use as pre- and post-hook for Borgbackup. I am looking for a way such that Dovecot defers any mail coming in via LMTP from Postfix, denies modifying mails/mailboxes via IMAP while Dovecot still allows to browse mails read-only. Is that possible? Bests, Matthias

2 1