I answered my own question. Sorry! It's that I'm using the zlib plugin
with maildir. Though I welcome ideas for a smooth transition to a better
quota system that won't demolish large servers as hard as dirsize would.
On 2024-05-20 17:07, jarland--- via dovecot wrote:
I'm currently running
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 emailu...@domain.net
STORAGE 1052385
MESSAGE2741
So the storage is roughly more than 1GB according to Dovecot. No change
after quota recalc. But:
root@arrow:/home
On 20/05/24 01:55, Richard Rosner via dovecot wrote:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute
permission the process can't access the logfile.
Why on earth does a process supposed to write to a file need
> Am 19.05.2024 um 16:49 schrieb Richard Rosner via dovecot:
> > It most certainly isn't. nginx isn't running as root, yet it can log
> > without execution permissions just fine. Absolutely nothing should have
> > execution permissions if they aren't meant to be executed,
Am 19.05.2024 um 16:49 schrieb Richard Rosner via dovecot:
It most certainly isn't. nginx isn't running as root, yet it can log
without execution permissions just fine. Absolutely nothing should have
execution permissions if they aren't meant to be executed, which should
only be true
As Alexander wrote - posix behaviour. To change into a directory the directory
itself needs execute permission for owner/group/other (what ever is meant). Not
the file itself. BTW even a chmod 110 /var/log/dovecot (so only execute and no
read/write) would work.
On 19.05.24 16:49, Richard
Am 19.05.24 um 16:02 schrieb Alexander Dallou via dovecot:
Am 19.05.2024 um 15:55 schrieb Richard Rosner via dovecot:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile
Am 19.05.2024 um 15:55 schrieb Richard Rosner via dovecot:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute
permission the process can't access the logfile.
Why on earth does a process supposed to write to a file need
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile.
Why on earth does a process supposed to write to a file need execution
permission? This most certainly is very unwelcome
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile.
On 19.05.24 12:25, Richard Rosner via dovecot wrote:
Am 19.05.24 um 04:02 schrieb Peter via dovecot:
> Check the permissions of the entire path, as dovecot:
>
> name
Am 19.05.24 um 04:02 schrieb Peter via dovecot:
Check the permissions of the entire path, as dovecot:
namei -l /var/log/dovecot/error.log
It might be selinux, check your audit.log file, or set selinux to permissive
mode and see if it works:
setenforce 0
This can't be the case
On 19/05/24 04:31, Richard Rosner via dovecot wrote:
I have a mailing server setup based on Debian Stable that uses postfix
(v3.7.10) for SMTP and dovecot (v2.3.19.1 (9b53102964)) for IMAP. I now
wanted to set dovecot to not write to syslog, but to dedicated files in
/var/log/dovecot. While
I have a mailing server setup based on Debian Stable that uses postfix
(v3.7.10) for SMTP and dovecot (v2.3.19.1 (9b53102964)) for IMAP. I now wanted
to set dovecot to not write to syslog, but to dedicated files in
/var/log/dovecot. While everything indicates that this happens successfully
On 01/05/2024 04:39 EEST David Mehler via dovecot
wrote:
Hello,
I've got a task to migrate a Dovecot mailstore, mailboxes, public
folders, etc from an older server (it runs Dovecot 2.2.x) to a new
server (running Dovecot 2.3.x). At the same
Hello,
I've got a task to migrate a Dovecot mailstore, mailboxes, public
folders, etc from an older server (it runs Dovecot 2.2.x) to a new
server (running Dovecot 2.3.x). At the same time I'm needing to change
mailbox storage formats, going from Mbox (on old server) to Maildir (on
new
Hello,
I'm using Thunderbird 102 to atempt to retrieve my messages via imap
(have tried both 143 and 993) first I wasn't getting any error messages
now I am. This is with Dovecot 2.3 on Debian 12.5. Here's the error
messages. I do not believe the first set related to public mailboxes
David Mehler via dovecot skrev den 2024-04-25 06:49:
Hello,
I have a quick question. Can Debian, and/or it's
Postfix/Dovecot/MySQL/MariaDB packages support the argon2 password
hashing scheme? I had a previously-working e-mail setup on a *BSD
system, utilizing the argon2ID scheme with Dovecot
Hello,
I have a quick question. Can Debian, and/or it's
Postfix/Dovecot/MySQL/MariaDB packages support the argon2 password
hashing scheme? I had a previously-working e-mail setup on a *BSD
system, utilizing the argon2ID scheme with Dovecot, Postfix, and MySQL.
Since changing systems
Hi
When I try to "detach"
(https://en.cppreference.com/w/cpp/thread/thread/detach) a thread
running inside a plugin, it seems the core dovecot has some influence on
that , tries to close this for some unknown reason and usually ends up
crashing
What is the cause of this ?
rols over your IMAP account, they can
create messages with a format totally different than what your mail server
can make.
Joseph Tam
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
/M2, then both your Postifx servers need to use the same
certificate with "mail.domain.com" as a subject. Simple as that.
Joseph Tam
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
leon--- via dovecot skrev den 2024-04-03 22:21:
Does anyone have any suggestions for this?
certbot --apache -d m1.domain.tld -d m2.domain.tld
after this is done you have it ready to be renewed, if you need more
loadbalancers add more -d hostnames
put this cert on all loadbalancers so its
for this?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
be much appreciated.
Thanks.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 31/03/2024 13:33 EEST Marc wrote:
Subject: Re: [Dovecot] [dovecot-2.1.15] mdbox corruption,
doveadm force-
resync can't repair it (throws segfault)
Are you sure it is not something else, your message is even empty
> Subject: Re: [Dovecot] [dovecot-2.1.15] mdbox corruption, doveadm force-
> resync can't repair it (throws segfault)
>
Are you sure it is not something else, your message is even empty.
_______
dovecot mailing list -- dovecot@dovecot.org
To un
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 30/03/2024 12:30 EET Aki Tuomi via dovecot
wrote:
On 30/03/2024 11:33 EET Joan Moreau wrote:
To do that kind of a change, mailbox migration is required.
Meaning ?> To do that kind of a change, mailbox migration is
requi
Aki
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
> To do that kind of a change, mailbox migration is required.
Meaning ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
mail_location = mdbox:/files/mail/%d/%n:INDEX=/data/mailindexes/%d/%n
then dovecot gets totally lost and tries to reach mailboxes content
and
tree from the INDEX location instead of the original location
What is wrong ?
Thank youHi
I have large number
Hi
I have large number of email (~TB) and want to put the index in a separate,
rapid drive
Initially, I have
mail_location = mdbox:/files/mail/%d/%n
If I put
mail_location = mdbox:/files/mail/%d/%n:INDEX=/data/mailindexes/%d/%n
then dovecot gets totally lost and tries to reach mailboxes content
Will skrev den 2024-03-26 13:32:
Hi again,
Sorry for the incomplete information. Here is the dovecot -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# OS: Linux 5.14.0-362.24.1.el9_3.x86_64 x86_64 AlmaLinux release 9.3
(Shamrock Pampas Cat)
# Hostname: dcsnow.com
auth_mechanisms = plain
Hi again,
Sorry for the incomplete information. Here is the dovecot -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# OS: Linux 5.14.0-362.24.1.el9_3.x86_64 x86_64 AlmaLinux release 9.3
(Shamrock Pampas Cat)
# Hostname: dcsnow.com
auth_mechanisms = plain login
first_valid_uid = 1000
> On 26/03/2024 00:02 EET Will wrote:
>
>
> Hi,
>
> This is my first time using this group and I have the same question as
> the subject. I can't seem to get dovecot to read a mbox inbox that is
> in /var/mail/%u with /home/%u/Maildir as maildir. This just wo
Hi,
This is my first time using this group and I have the same question as
the subject. I can't seem to get dovecot to read a mbox inbox that is
in /var/mail/%u with /home/%u/Maildir as maildir. This just worked on
my old server that I am now upgrading to AlmaLinux release 9.3 with
dovecot
Hi,
is there somebody who can help me here?
Thanks in advance
Christian
> Am 19.03.2024 um 10:54 schrieb Christian Rößner via dovecot
> :
>
> Hi,
>
> I have defined a service and a protocol that shall honor quota, but in an
> non-enforcing mode (required).
>
Hi,
I have a fedora38 system with dovecot-2.3.21 for a few hundred users and just
noticed there are 4000 dovecot/dict processes running:
2203938 ? S 0:15 dovecot/dict
or sleeping, as the case may be. Some time ago I installed the last_login_dict
plugin to record login details per
Hi!
I can see the crash now, thanks.
For 2.3, I would suggest as workaround to enable the fetch-size imapc_feature.
Aki
> On 20/03/2024 09:58 EET John van der Kamp via dovecot
> wrote:
>
>
> See attached script I used. If you get EOF then you've hit the crash
See attached script I used. If you get EOF then you've hit the crash.
John
-Original message-
From: Aki Tuomi
Sent: Wednesday, 20th March 2024, 8:40
To: John van der Kamp ; John van der Kamp via
dovecot
Subject: RE: Crash in dovecot snippet when using
Could you provide some simple way to reproduce this, minimal config etc?
Aki
> On 19/03/2024 17:44 EET John van der Kamp via dovecot
> wrote:
>
>
> Hi, sorry for the late reply.
>
> The commit you've pointed at before is the commit introducing code for the
> s
github.com/dovecot/core/commit/
7810b38d30b7dbb2155f78873fe760bc9e2e6212 However, the default imapc_features
value stays the same, so all the "negative" features are suddenly enabled.
I've reset the defaults in the frontend config to what it was before:
imapc_features = no-fetch-s
= 24000
}
protocol = lmtp_noenforcing
}
protocol lmtp_noenforcing {
postmaster_address = postmaster@
mail_plugins = quota sieve fts fts_solr
# Just for testing, if this works.
userdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
override_fields = quota
On 15-03-2024 08:10, Aki Tuomi via dovecot wrote:
On 14/03/2024 17:28 EET dovecot--- via dovecot wrote:
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
I could be wrong, but i believe dovecot submission is only a proxy to postfix
> On 15/03/2024 10:53 EET Michael Grant via dovecot wrote:
>
>
> I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a
> slew of these in my log:
>
> Mar 14 10:02:38 strange.networkguild.org dovecot[865654]:
> imap(mgrant)<1939553>: Panic
I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a slew of
these in my log:
Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap
(mgrant)<1939553>: Panic: file istream-header-filter.c: line
663 (i_stream_header_filter_snapshot_free): assertion failed: (sn
> On 14/03/2024 17:28 EET dovecot--- via dovecot wrote:
>
>
> > it is possible to do antispoofing, like
> > reject_authenticated_sender_login_mismatch from postfix ?
>
>
> I could be wrong, but i believe dovecot submission is only a proxy to postfix
> subm
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
I could be wrong, but i believe dovecot submission is only a proxy to postfix
submission. Dovecot does not directly delivery mail to the world. Meaning the
mail is still passing through postfix
Hi,
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Hi
I have 1 director and ~8 dovecot nodes. I thinking about Solr cluster beacuse
one server solr probably is not enough.
I thinking about SolrCloud Mode but I don't know if it will work with Dovecot
And if not SolrCloud Mode, then what?
I don't have much experience in Solr clustering and I want
ent -connect mail.example.com:993
-servername mail.example.com -crlf -quiet
-servername works with newer versions of s_client but is required for
older versions, if you include it in everything you can't go wrong.
Peter
___
dovecot mailing list -- dove
On 2024-03-12, steffan--- via dovecot wrote:
> I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips=
> that=92s been fine for quite some time. Recently I started getting complai=
> nts related to SNI.
>
> I test with this: openssl s_client -connect mail
Dear maintainer,
there is potentially conflicting information in dovecot doc about the
count quota backend.
According to
https://doc.dovecot.org/configuration_manual/quota/quota_count/
the count quota backend is the recommended way of calculating quota on
recent Dovecot
installations
> On 12/03/2024 22:54 EET steffan--- via dovecot wrote:
>
>
> I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips
> that’s been fine for quite some time. Recently I started getting complaints
> related to SNI.
>
> I test with this: o
I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips
that’s been fine for quite some time. Recently I started getting complaints
related to SNI.
I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quiet
On macOS using OpenSSL LibreSSL 3.3.6 I test
rying to access this from a remote system with Thunderbird is not
> working. /var/log/mail.log shows the following:
>
> 2024-03-03T22:18:54.887061-05:00 debian-server dovecot: pop3-login:
> Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL
> routines::sslv3 al
> On 10/03/2024 09:27 EET Andre Rodier via dovecot wrote:
>
>
> Hello,
>
> I am using a webmail, SOGo, to access Dovecot mail server in IMAP.
>
> SOGo correctly logs the remote IP address, using the standard nginx headers,
> especially X-Forwarded-For.
>
&g
Jerry Stuckle skrev den 2024-03-04 04:39:
First of all, I will admit I am totally a noob with Dovecot. I am
trying to install it on Debian and am somewhat lost. Right now this is
a test system on our LAN.
... i see Debian so ask on debian maillist for dovecot
I know we noobs are a PITA
Hello,
I am using a webmail, SOGo, to access Dovecot mail server in IMAP.
SOGo correctly logs the remote IP address, using the standard nginx headers,
especially X-Forwarded-For.
However, when I check the IMAP logs, I see my server's IP address for the
"remote_ip" value
Hi, all,
First of all, I will admit I am totally a noob with Dovecot. I am
trying to install it on Debian and am somewhat lost. Right now this is
a test system on our LAN.
I'm starting with POP3 (because it's easy to handle from the CLI). I
have it working from localhost - I can telnet
to the right direction?
Every hint is appreciated.
--
Phren
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Hello,
I am using a webmail, SOGo, to access Dovecot mail server in IMAP.
SOGo correctly logs the remote IP address, using the standard nginx headers,
especially X-Forwarded-For.
However, when I check the IMAP logs, I see my server's IP address for the
"remote_ip" value
I'm trying to run the Dovecot Authentication Protocol (port 12345) [1]
via SSL. Here is my non-SSL config:
service auth {
inet_listener {
port = 12345
haproxy = yes
}
}
Adding ssl=yes to the inner block doesn't seem to change anything, I
can't connect via "openssl s_c
Hi all,
I'm running dovecot-pigeonhole-2.3.21-1.x86_64 & dovecot-2.3.21-1.x86_64 +
roundcube 1.6.6 on my redhat server. Mailserver is working as expected with the
exception fo the Filters. I've installed and configure everything that i'm
aware of but unfortunatelly its not working.
I thin
ng locally and accepting
connections on that socket?
Am Montag, dem 19.02.2024 um 21:57 +0100 schrieb r.barc...@habmalnefrage.de:
Hi Richi,
You create a user in PostgreSQL (arbitrary name, e.g.
dbuserofdovecot) and use it in the Dovecot settings in the connection
string:
So connecting via the socket is not supported? because it is with mysql
according to the docs?
Am Montag, dem 19.02.2024 um 21:57 +0100 schrieb r.barc...@habmalnefrage.de:
Hi Richi,
You create a user in PostgreSQL (arbitrary name, e.g.
dbuserofdovecot) and use it in the Dovecot
Hi Richi,
You create a user in PostgreSQL (arbitrary name, e.g. dbuserofdovecot) and use
it in the Dovecot settings in the connection string:
/etc/dovecot/dovecot-sql.conf.ext
driver = pgsql
connect = host=127.0.0.1 dbname=mymailserverdb user=dbuserofdovecot
password
> On 19/02/2024 22:26 EET burkha...@konsultaner.de
> wrote:
>
>
> Hi! The docs for dovecot with postgres are outdated and I somehow cannot
> connect from my dovecot instance to my postgresql database.
>
> I tried a lot but the debug output dosn't help me.
>
>
ilbox unsubscribe -u
Aki
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Hi! The docs for dovecot with postgres are outdated and I somehow cannot
connect from my dovecot instance to my postgresql database.
I tried a lot but the debug output dosn't help me.
What user is actually trying to connect to the postgresql? the dovecot user or
root or the actual user from
Hello,
Would you be able to show what you did in order to make this command
unsubscribe as well? The link provided with the answer, no longer works.
Thank you, Ryan
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email
from the production
server so there is a lot of emails transfer a day. The warnings occur at
random times and with random users.
I reinstalled 2.3.21 from source (originally was using Dovecot repo
packages) and tested by reverting that commit. The warnings continued.
Next I tried
On 2024-02-10 2:24 a.m., Timo Sirainen wrote:
On 12. Jan 2024, at 9.37, John Alex. via dovecot
wrote:
since I upgraded dovecot to version 2.3.21 on a FreeBSD
13.2 system, I've been seeing a few occurences of the
following warnings daily:
Jan 11
On 12. Jan 2024, at 9.37, John Alex. via dovecot wrote:
>
> Hi,
>
> since I upgraded dovecot to version 2.3.21 on a FreeBSD 13.2 system, I've
> been seeing a few occurences of the following warnings daily:
>
> Jan 11 13:13:25 dimokritos dovecot[33170]:
> lmtp(user
Hello,
for our testing environment, I would like to configure a CA that is trusted by
Dovecot when making TLS connections. As you can see below in the config
snippets, this is for example used when proxying to itself during a login with
credentials for the OIDC provider. The Dovecot
I have the same problem after updating dovecot 2.3.21, I am receiving the
errors below for the accounts when I perform backups.
doveadm(u...@user.com.br): Error: Purging namespace '' failed: BUG: Unknown
internal error
Error: failed sync dir: doveadm(us...@user2.com.br): Warning: mdbox
/data
messages in the
inbox
as duplicates into their mailbox.
I suppose I can do:
doveadm -v expunge -u mailbox INBOX all
rm dovecot* in the Maildir folder
doveadm force-resync -u INBOX
then use dsync to migrate the INBOX
Here I need
protocol pop3 {
...
pop3_reuse_xuidl = yes
}
Maybe that's of use to you?
Joseph Tam
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
dovecot* in the Maildir folder
doveadm force-resync -u INBOX
then use dsync to migrate the INBOX
Here I need some hints to how setup it and wich syntax use.
If useful I can copy or mount the /var/mail/ folder of the old server that
contains the users INBOX to the new server.
Thanks, B
Sorry, the provided patch link was wrong, it's already in 2.3.21, my bad.
Anyways, it is still fixed in main, since it does not happen there.
Aki
> On 19/01/2024 09:13 EET Aki Tuomi via dovecot wrote:
>
>
> Hi!
>
> I was able to reproduce this issue with 2.3.21, but it
Hi!
I was able to reproduce this issue with 2.3.21, but it seems to have been fixed
in main. I think
https://github.com/dovecot/core/commit/1c1b77dbf9a548aac788efb76973ce2d0fa6c732.patch
will fix this.
Aki
> On 18/01/2024 22:51 EET John van der Kamp via dovecot
> wrote:
>
&g
Hello,
I've found a crash in a very specific setup. A dovecot server with imapc
connection needs to receive an email with no body contents for the intent of
generating a preview/snippet. It crashes somewhere deep in the jungle of
istream and snapshots. I've included a script which sets up
---
> From: Aki Tuomi
> Sent: Thursday, January 18, 2024 8:37:07 AM
> To: Lucas Rolff ; dovecot@dovecot.org
>
> Subject: Re: Dovecot imap-hibernate errors in 2.3.21
> Did you check if maybe selinux is interfering here? I tested the 2.3.21-CE in
> a RHEL
sadly that points towards
> anything related to hibernate itself.
> "Debug: open(/proc/self/io) failed: Permission denied" being the main "thing"
> that seems a bit odd, but that also happens under 2.3.20 as well by the looks
> of it:
>
> ```
> Jan 17 20:4
as well by the looks
of it:
```
Jan 17 20:42:16 de-mail01 dovecot[3631433]: imap-login: Login:
user=, method=PLAIN, rip=193.36.xx.xx, lip=176.9.151.xxx,
mpid=3631534, TLS, session=
Jan 17 20:42:16 de-mail01 dovecot[3631433]:
imap(custo...@example.com)<3631534>: Debug: Loading modules
Jan 13 01:09:03 mail01 dovecot[3646235]: imap-hibernate: Error: conn
unix:imap-hibernate (pid=3646265,uid=1010): IMAP client fd not received
This is bit weird. Can you try enabling mail_debug=yes and trying once more on
test system?
Aki
> On 17/01/2024 21:06 EET lu...@lucasrolff.com wr
Hello,
I recently upgraded a Dovecot install from 2.3.20 to 2.3.21 from the 2.3-latest
repository (
http://repo.dovecot.org/ce-2.3-latest/rhel/$releasever/RPMS/$basearch )
However since then, I seem to be getting:
Jan 13 01:08:32 mail01 dovecot[3646235]: imap-login: Login:
user=, method=PLAIN
> On 17/01/2024 14:47 EET André Rodier via dovecot wrote:
>
>
> Hello, all.
>
>
> Postfix allows me to configure multiple characters to be used as
> recipient delimiter.
>
> However, I don't see that in dovecot, it seems I can only use one
> character i
Hello, all.
Postfix allows me to configure multiple characters to be used as
recipient delimiter.
However, I don't see that in dovecot, it seems I can only use one
character in recipient_delimiter ?
Am I right ? Does dovecot would only let me use email+...@domain.com, or
can I use other
> On 09/01/2024 17:45 EET Steve Button wrote:
>
>
> Hi,
>
>
>
> I have recently moved a dovecot installation from 2.2.36 on RHEL7.9 onto
> 2.3.20 on Amazon Linux 2023 and I'm now seeing the error message in the
> title relating to /usr/bin/checkpassword
Hi,
I have recently moved a dovecot installation from 2.2.36 on RHEL7.9 onto 2.3.20
on Amazon Linux 2023 and I'm now seeing the error message in the title relating
to /usr/bin/checkpassword (which doesn't exist on either). This is a project
that I've inherited, and I've never used dovecot
Hi,
since I upgraded dovecot to version 2.3.21 on a FreeBSD 13.2 system, I've been seeing a
few occurences of the following warnings daily:
Jan 11 13:13:25 dimokritos dovecot[33170]: lmtp(user1)<8209>:
Warning: mdbox /var/vmail/users/user1/mdbox/storage: Inconsistency in map index
On 03/01/2024 10:16, Aki Tuomi via dovecot wrote:
On 09/12/2023 15:02 EET John Fawcett wrote:
Hi
I've just made updated versions of 3 patches against the latest release
2.3.21 in case they are useful to someone or might get considered for
official inclusion.
John
> On 09/12/2023 15:02 EET John Fawcett wrote:
>
>
> Hi
>
> I've just made updated versions of 3 patches against the latest release
> 2.3.21 in case they are useful to someone or might get considered for
> official inclusion.
>
> John
>
> *dovecot-2.3.
On 12/14/23 13:29, Dmitry Melekhov wrote:
I guess you need to alter openssl.cnf
Yes, that worked. Thank you!
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Still the client is not working. I used testssl.sh to check the
available ssl versions and it says that tls1.1 is not offered:
I guess you need to alter openssl.cnf
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to
d
TLS 1.1 not offered
TLS 1.2 offered (OK)
TLS 1.3 offered (OK): final
Kind regards,
Nils
_______
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Op 14-11-2023 om 17:44 schreef Kees van Vloten:
I did another test: I have just downgraded the dovecot packages to
the version in Bullseye, i.e. 2.3.19 -> 2.3.13, without making any
other change.
This solved the issue! Thunderbird (which was not even restarted) can
Hi
I've just made updated versions of 3 patches against the latest release 2.3.21
in case they are useful to someone or might get considered for official
inclusion.
John
dovecot-2.3.21-tika-http-auth.patch
Allows specification of username and password in the fts_tika setting for basic
auth against
1 - 100 of 59890 matches
Mail list logo