similar to: [SOLVED] dovecot -2.2.24 on Fedora 31

Displaying 20 results from an estimated 100000 matches similar to: "[SOLVED] dovecot -2.2.24 on Fedora 31"

2019 Nov 12
0
dovecot -2.2.24 on Fedora 31
Hi! Can you try follow this guide to get a core dump https://www.dovecot.org/bugreport-mail then provide gdb /usr/lib/dovecot/auth /path/to/core bt full on it. Would help narrowing down that bug. Also doveconf -n could be useful. Aki On 12.11.2019 9.19, Frank Elsner wrote: > On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote: >> On Mon, 11 Nov 2019 23:47:27
2019 Nov 11
0
dovecot -2.2.24 on Fedora 31
> On 11/11/2019 17:22 Frank Elsner via dovecot <dovecot at dovecot.org> wrote: > > > Hi, > > I try to compile dovecot -2.2.24 on Fedora 31 and get the following error: > > iostream-openssl.c: In function ?openssl_iostream_verify_client_cert?: > iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type ?X509_STORE_CTX? {aka ?struct
2019 Nov 11
3
dovecot -2.2.24 on Fedora 31
Hi, I try to compile dovecot -2.2.24 on Fedora 31 and get the following error: iostream-openssl.c: In function ?openssl_iostream_verify_client_cert?: iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type ?X509_STORE_CTX? {aka ?struct x509_store_ctx_st?} 118 | subject = X509_get_subject_name(ctx->current_cert); | ^~ make[3]: ***
2019 Nov 11
2
dovecot -2.2.24 on Fedora 31
On Mon, 11 Nov 2019 17:30:37 +0200 (EET) Aki Tuomi via dovecot wrote: [ ... ] > Is there some reason you want to use ancient dovecot? You should use 2.2.36 at least. I got dovecot-2.2.36.4 compiled but at start the log shows dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap dovecot[342617]: ssl-params: Generating SSL parameters dovecot[342614]: master: Error:
2019 Nov 12
1
dovecot -2.2.24 on Fedora 31
On Tue, 12 Nov 2019 09:22:56 +0200 Aki Tuomi via dovecot wrote: > Hi! > > Can you try follow this guide to get a core dump > > https://www.dovecot.org/bugreport-mail > > then provide > > > gdb /usr/lib/dovecot/auth /path/to/core > > bt full Sorry, I'm not familiar with gdb and can only provide this # gdb /usr/local/dovecot//libexec/dovecot/auth GNU
2019 Nov 12
2
dovecot -2.2.24 on Fedora 31
On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote: > On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote: [ ... ] > I narrowed the probelem down to the warnings > > Warning: service auth { client_limit=128 } is lower than required under max. load (768) > Warning: service anvil { client_limit=256 } is lower than required under max. load (643) These
2019 Nov 11
0
dovecot -2.2.24 on Fedora 31
On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote: [ ... ] > I got dovecot-2.2.36.4 compiled but at start the log shows > > dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap > dovecot[342617]: ssl-params: Generating SSL parameters > dovecot[342614]: master: Error: service(auth): command startup failed, throttling for 2 secs >
2019 Nov 20
0
[SOLVED] Doveadm replicator ssl issues
Solved, thank you. TCPS was the issue. From: Aki Tuomi <aki.tuomi at open-xchange.com> Sent: Wednesday, November 20, 2019 08:54 To: Miro Igov <miro.igov at gmail.com>; dovecot at dovecot.org Subject: Re: Doveadm replicator ssl issues On 18.11.2019 22.30, Miro Igov via dovecot wrote: Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard certificates. Email
2021 Dec 07
3
Dovecot v2.3.17.1 Released
We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.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 -- - dsync: Add back
2021 Dec 07
3
Dovecot v2.3.17.1 Released
We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.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 -- - dsync: Add back
2016 Jul 04
3
Configure Dovecot for GSSAPI [formerly: Looking for GSSAPI config]
On Mon, 4 Jul 2016 08:54:27 +0300 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > http://wiki2.dovecot.org/Authentication/Kerberos > > It has been now updated. Excellent! That was quick! Although, you used my actual local domain in your example: mail.hprs.local. Not that I care, no one can get to that, but it might be clearer to those of us who uncomprehendingly monkey-type
2016 Dec 12
1
Dovecot 2.2.27 > 2.2.24 downgrade errors
Aki Tuomi wrote: > Hi! > > Did you get a core file? Can you install debugging symbols and send > > gdb /path/to/bin /path/to/core > bt full > > to us? > Seems no cores, atleast in /usr/sbin/ ( binary is in /usr/sbin/dovecot) is none. -- Mart
2010 Feb 22
1
Migration 1.2.10 -> dovecot-2.0.beta
Hello *, I've a well functioning dovecot.1.2.10 installation. I'd like to migrate to dovecot.2.0.beta. Is it possible to use one (big) dovecot.conf or must I split it into pieces into directory conf.d? What is the best procedure to convert the configuration file? Any pointers welcome. --Frank Elsner
2008 Sep 05
10
Error starting dovecot
Hello, I have a linux system (Ubuntu 7.04 server edition) running Postfix 2.3.8 Today i installed Dovecot through apt-get (got version 1.0.rc17 installed) and configured it to do sasl auth only, (i already have other pop3,smtp and imap servers running) following the howto's at dovecot.org The thing is that if i try to start dovecot or run dovecot -n i get this message: Error: Can't use
2012 May 08
1
Exim / Dovecot and AUTH LOGIN
Hi to both adressed mailing lists, I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL exim.conf: | plain: | driver = dovecot | public_name = PLAIN | server_socket = /var/run/dovecot/auth-client | server_set_id = $auth1 | | login: | driver = dovecot | public_name = LOGIN | server_socket = /var/run/dovecot/auth-client |
2019 Oct 18
1
Dovecot v2.3.8 released
> On 18/10/2019 14:25 Tom Sommer via dovecot <dovecot at dovecot.org> wrote: > > > On 2019-10-08 13:18, Aki Tuomi via dovecot wrote: > > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > - imap: SETMETADATA with literal value
2016 Dec 12
0
Dovecot 2.2.27 > 2.2.24 downgrade errors
On 12.12.2016 14:49, Mart Pirita wrote: > Hello. > > Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some gettings > errors for some users: > > Dec 12 14:42:17 server dovecot: imap(user): Panic: file > mail-index-sync-keywords.c: line 227 (keywords_update_records): > assertion failed: (data_offset >= sizeof(struct mail_index_record)) > Dec 12 14:42:17
2012 May 08
0
[+]: Exim / Dovecot and AUTH LOGIN
On Tue, 8 May 2012 15:22:11 +0200 Frank Elsner wrote: > > Hi to both adressed mailing lists, > > I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL Forgot to mention the versions :-( exim 4.77 dovecot 2.1.6 self compiled under Fedora 14. --Frank Elsner
2019 Dec 13
0
Dovecot 2.3.9 - lmtp crashes with Signal 11
Hi! We have released v2.3.9.1 fixing this issue. Thank you for your effort! Aki On 13.12.2019 12.27, Michael Stilkerich wrote: > Hallo Aki, > > the affected code location seems to be concerned with parsing to ?To:? header. I checked all the mails causing the crash, the To: header is either empty (but present) or contains ?undisclosed-recipients:;?. > > I checked this manually
2016 Jul 04
4
Configure Dovecot for GSSAPI [formerly: Looking for GSSAPI config]
On 07/04/2016 03:30 AM, Mark Foley wrote: > Actually, I see that you used host.domain.name further down. That's a good substitute for mail.hprs.local. > > Also, not to be a literary critic, but it might not hurt to show an example keytab beneath your > "Make sure your keytab has entry for ...". Just in case people don't exactly know how to "make sure: > > $