Displaying 20 results from an estimated 216 matches for "v2.3".
Did you mean:
2.3
2008 Aug 15
4
[LLVMdev] Which linux distribution required the least effort to install LLVM 2.3?
Hi!
I'm a new LLVM user.
I want to start using the LLVM System v2.3. However, I don't want to spend
all my time hunting, pecking, downgrading, and/or upgrading packages to get
LLVM v2.3 running. I was wondering which Linux distrubutions(FC7, Ubuntu,
NetBSD, etc) have required the least effort out of the box to start running
LLVM v2.3.
tia,
Bernardo Elayda
-------------- next part
2016 Apr 13
1
v2.3 development tree forked in git
The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch.
The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.
2016 Apr 13
1
v2.3 development tree forked in git
The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch.
The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.
2019 Aug 08
1
Upgrading to v2.3.X breaks ssl san?
On Wed, 7 Aug 2019 20:24:13 +0300 (EEST), Aki Tuomi via dovecot wrote:
>> i thought ssl_ca is where to put the intermediate cert?
Well, it surely worked that way until v2.3...
> (Sorry for duplicate mail, keyboard acted up...)
>
> No, that has always been a mistake and it was fixed in 2.3. Our SSL
> pages in documentation & wiki have always recommended concatenating
>
2020 Jul 14
0
Fwd: Dsync mail migration from v2.2 --> v2.3
Two items I forgot to mention in my initial post:
(A) I am running the sync command on the new v2.3 server.
(B) To get sync to work, I had to add the following to the old v2.2 server:
auth_socket_path = /var/run/dovecot/auth-master
I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location.
I say this because when I was
2019 Aug 07
0
Upgrading to v2.3.X breaks ssl san?
> On 07/08/2019 14:28 telsch <telsch at gmx.de> wrote:
>
>
> with v2.2.34 i can use:
>
> ssl_ca = </etc/ssl/ca-bundle.pem
> ssl_cert = </etc/ssl-imap.pem
>
> after upgrade to v2.3.X it doesn't work like before.
>
> it's working if i manual cat ca-bundle.pem and ssl-imap.pem into one
> file and using only:
>
> ssl_cert =
2015 Dec 08
3
v2.2.20 released
On Tuesday 08 of December 2015, Gerhard Wiesinger wrote:
> On 07.12.2015 20:13, Timo Sirainen wrote:
> > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz
> > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig
> >
> > This could be (one of) the last v2.2.x release. We're starting v2.3
> > development soon.
>
> Great!
>
> What's on
2017 Dec 18
2
Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.
Hello Dovecot users,
Here is the Pigeonhole release candidate that goes with the Dovecot
v2.3 release candidate. Of course, a large part of this release consists
of compatibility changes for Dovecot v2.3. Apart from that, not much
changed, just a few additions and fixes that accumulated over the last
few months.
Most of these changes will be back-ported to Pigeonhole v0.4, but that
release will
2017 Dec 18
2
Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.
Hello Dovecot users,
Here is the Pigeonhole release candidate that goes with the Dovecot
v2.3 release candidate. Of course, a large part of this release consists
of compatibility changes for Dovecot v2.3. Apart from that, not much
changed, just a few additions and fixes that accumulated over the last
few months.
Most of these changes will be back-ported to Pigeonhole v0.4, but that
release will
2019 Aug 06
7
Upgrading to v2.3.X breaks ssl san?
2018 Jan 06
0
TLS problem after upgrading from v2.2 to v2.3
Hi Jan,
fair enough. You may want to try mine to see if it works - if yes, it
might be worthwhile digging deeper. Tbh I had not default settings on
for a long time.
Thanks and regards
Goetz R. Schultz
On 06/01/18 18:30, Jan Vejvalka wrote:
> Thanks for your reply; I used the defaults, both before and after the
> upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting
2019 Aug 06
0
Upgrading to v2.3.X breaks ssl san?
On Tue, 6 Aug 2019, telsch wrote:
> if i cat ssl_ca and ssl_cert into one file and only use ssl_cert it's working with 2.3.X
> ssl_ca = </etc/ssl/ca-bundle.pem ssl_cert = </etc/ssl-imap.pem
In the words of Montoya, "I do not think it means what you think it
means", referring to "ssl_ca". That file is not used to to establish
the trust chain to your server
2019 Aug 07
1
Upgrading to v2.3.X breaks ssl san?
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 07/08/2019 00:37 Joseph Tam via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
2020 Jul 14
0
Dsync mail migration from v2.2 --> v2.3
Hello all,
I?ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades.
The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against
2017 Dec 29
0
Automatic Debian repository (Xi) updated
Hi,
Now that we have a new Dovecot v2.3 release, I've created a new Xi
builder that follows the git master branch to automatically produce
Debian packages for the future Dovecot v2.4. The existing v2.3
repository now follows the master-2.3 branch, meaning that this will
only follow developments/fixes ported to the v2.3 stable release series.
This was already true for the v2.2 oldstable
2018 Jan 04
1
TLS problem after upgrading from v2.2 to v2.3
Hi *,
The change in default SSL settings between 2.2 and 2.3 cut off a few
clients; Microsoft-hosted Exchange (?) being one of them:
Jan 4 11:02:56 kremail dovecot: pop3-login: Disconnected (no auth
attempts in 0 secs): user=<>, rip=40.101.4.hisip, lip=myip, TLS
handshaking: SSL_accept() failed: error:1408A0C1:SSL
routines:SSL3_GET_CLIENT_HELLO:no shared cipher,
2018 Jan 08
1
TLS problem after upgrading from v2.2 to v2.3
Jan Vejvalka <jan.vejvalka at lfmotol.cuni.cz> writes:
>> Mine are below and they work just fine:
>>
>> ssl_cipher_list =
>>
2015 Dec 07
7
v2.2.20 released
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig
This could be (one of) the last v2.2.x release. We're starting v2.3 development soon.
+ Added mailbox { autoexpunge=<time> } setting. See
http://wiki2.dovecot.org/MailboxSettings for details.
+ ssl_options: Added support for no_ticket
+ imap/pop3/managesieve-login:
2015 Dec 07
7
v2.2.20 released
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig
This could be (one of) the last v2.2.x release. We're starting v2.3 development soon.
+ Added mailbox { autoexpunge=<time> } setting. See
http://wiki2.dovecot.org/MailboxSettings for details.
+ ssl_options: Added support for no_ticket
+ imap/pop3/managesieve-login:
2018 Jan 06
2
TLS problem after upgrading from v2.2 to v2.3
Thanks for your reply; I used the defaults, both before and after the
upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting default
changes. The new defaults broke the connection.
Jan
> what are your settings?
>
> Mine are below and they work just fine:
>
> ssl_cipher_list =
>