similar to: ssl_min_protocol

OK, I did read <http://wiki2.dovecot.org/LDA> but it doesn't answer the question I have since it doesn't tell me what I can do with -o, exactly. What I would like to do is be able to call dovecot-lda and pass along '\\Seen', is that possible? -- Up the airy mountains, down the rushy glen... From ghosties and bogles and long-leggity beasties... My mother said I never

Good $daytime, as per the recommendations of Mozilla?s SSL config generator[0], I wanted to set ssl_min_protocol=TLSv1.3 in my dovecot config. This produced the error: imap-login: Error: Failed to initialize SSL server context: Unknown ssl_min_protocol setting 'TLSv1.3' After some digging, I found the function that parses this setting in

Hi all, I'm trying to set up my server with support for TLS 1.3 only, but that does not seem to be supported. First off, TLS 1.3 itself does work fine, so it's not the config or ssl library, and 1.3-only works fine with Postfix. The problem is only in disabling TLS 1.2 for Dovecot. On connection, I'm getting an error that 1.3 is an "Unknown ssl_min_protocol setting". Reading

hi sorry if question was asked already. Was reading https://wiki2.dovecot.org/Upgrading/2.3 first I'm confused on diffie hellman parameters file. I never set up ssl-parameters.dat before (should i have? do I have one that was automatically made for me by dovecot?) Do I need to make a fresh dh.pem? The upgrade doc tells how to convert ssl-parameters.dat but how to make a new one? other

Thanks Joseph, Aki, but something missing from upgrade document, where does the dh param file go? I located ssl-parameters.dat so I will put it there. Quoting Joseph Tam <jtam.home at gmail.com>: > On Fri, 22 Jun 2018, Joseph Tam wrote: > >> However, recent advances make this condition obsolete [*] and not >> really safer, so a much faster way to generate a DH key is

I'm attempting to install the gsl package using the following command: install.packages("c:/users/mike/documents/R/win-library/gsl_1.9-9.tar.gz",repos=NULL,type="source") My attempt is failing. Please help. The message supplied is: Installing package(s) into ‘C:/Users/Mike/Documents/R/win-library/2.15’ (as ‘lib’ is unspecified) * installing *source* package

> On 13/04/2020 12:35 Thomas Schneider <qsx at chaotikum.eu> wrote: > > > Good $daytime, > > as per the recommendations of Mozilla?s SSL config generator[0], I > wanted to set ssl_min_protocol=TLSv1.3 in my dovecot config. This > produced the error: > > imap-login: Error: Failed to initialize SSL server context: Unknown > ssl_min_protocol setting

> On 22 June 2018 at 10:18 tai74 at vfemail.net wrote: > > > > hi sorry if question was asked already. Was reading > https://wiki2.dovecot.org/Upgrading/2.3 > > first I'm confused on diffie hellman parameters file. I never set up > ssl-parameters.dat before (should i have? do I have one that was > automatically made for me by dovecot?) > > Do I need

On 26.11.2019 19.34, Laurens Post via dovecot wrote: > Hi all, > > I'm trying to set up my server with support for TLS 1.3 only, but that > does not seem to be supported. > First off, TLS 1.3 itself does work fine, so it's not the config or > ssl library, and 1.3-only works fine with Postfix. The problem is only > in disabling TLS 1.2 for Dovecot. > On connection,

On Fri, 22 Jun 2018, Joseph Tam wrote: > However, recent advances make this condition obsolete [*] and not > really safer, so a much faster way to generate a DH key is > > openssl dhparam -dsaparam -out dh.pem 4096 > > DH generation is a one time operation, so if you're paranoid and you've > got time to burn, go ahead and generate the "safe" DH key. >

On Fri, 22 Jun 2018, Aki Tuomi wrote: >> Do I need to make a fresh dh.pem? The upgrade doc tells how to convert >> ssl-parameters.dat but how to make a new one? > > ... or you can make a fresh one using openssl > gendh 4096 > dh.pem This also works openssl dhparam -out dh.pem 4096 > Note that this will require quite a lot of entropy, so you should > probably

Full_Name: Levi Waldron Version: 2.5.1 OS: Ubuntu Gutsy Submission from: (NULL) (206.248.157.88) I installed libgsl0-dev then tried to install the gsl cran package, unsuccessfully (see output below). As a workaround I created a symbolic link to /usr/bin/gcc-4.2, ie: sudo ln -s /usr/bin/gcc-4.1 /usr/bin/gcc-4.2 The correct behavior of the gsl package should be to use the executable

On 22 November 2007 at 20:00, leviwaldron at gmail.com wrote: | Full_Name: Levi Waldron | Version: 2.5.1 | OS: Ubuntu Gutsy | Submission from: (NULL) (206.248.157.88) | | | I installed libgsl0-dev then tried to install the gsl cran package, | unsuccessfully (see output below). As a workaround I created a symbolic link to | /usr/bin/gcc-4.2, ie: | | sudo ln -s /usr/bin/gcc-4.1 /usr/bin/gcc-4.2

Hello! Benny Pedersen <me at junc.eu> schrieb am 18.07.20 um 13:04:37 Uhr: > ratatouille skrev den 2020-07-18 12:33: > > ssl_min_protocol = TLSv1.2 > > ssl_cipher_list = PROFILE=SYSTEM > > ssl_prefer_server_ciphers = yes > > comment this lines, then i belive k9 works > > if it still does not, then drop k9 mail Commenting just ssl_min_protocol = TLSv1.2

18.07.2020, 14:30, Benny Pedersen <me at junc.eu>ratatouille skrev den 2020-07-18 13:20: > Commenting just ssl_min_protocol = TLSv1.2 seems to solve the problem. > So I have the default ssl_min_protocol = TLSv1 with means that the device running k9 is not supporting TLS 1.2 yet TLS 1.2 is enabled by default in Android versions 5.0 and newer. For earlier Android versions, K9

Hello! On my testserver running CentOS8 I have installed dovecot v2.3.8. I can connect to the server using claws-mail on my PC but can't using K9-mail on android device. Jul 18 12:24:57 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL:

Hi, Save over 50% on your medication http://www.ledrx .com Remove space in the above link month will affect you, with reference to your personal chart, she snapped, sounding much more like Professor McGonagall than her usual airy-fairy self. I want it ready to hand in next Monday, and no excuses!

On 16/7/20 5:54 am, Benny Pedersen wrote: >>> FWIW I meant if the client is Windows7/old-Outlook then changing >>> either 993/SSL or 143/STARTTLS to 143/NONE could help pick up the >>> mail. > > windows 7 just need tls 1.0, why its need to disabled all, is as well > beyong me, do not disable tls 1.0 in dovecot aslong one have windows > 7 clients Would anyone

Hi, I have two servers replicating mail as required, the directory structure (per user), however they will not replicate the sieve scripts directory: server 1 Maildir sieve server 2 Maildir Output of doveconf -n on server 1: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn >

I currently use Ubuntu 20.04 with Dovecot 2.3.7.2 and OpenSSL 1.1.1f. A few months ago there was an update to all these systems and since then I've had to talk W7 and old Mac clients through disabling ports 993/995 with TLS enabled back to ports 143/110 without SSL or they could not pick up email. Thunderbird users (ie; me) were unaffected. Could anyone share a set of port 993/995 SSL