Hi,
José Abílio Matos wrote:
After today's update to openssl-1:3.0.2-4.fc36.x86_64 the problem is
gone. :-)
This means your mail server does not support TLS 1.2. You will have to keep
your system set to crypto-policy LEGACY to connect to the server.
I would recommend contacting your mail
On Monday, 14 March 2022 16.53.18 WEST José Abílio Matos wrote:
> Thank you.
>
> I copied and pasted and while changing the option I left one of those rogue
> characters, keeping always the preffix. :-(
>
>
> I will try and see your suggestion.
After today's update to
On Monday, 14 March 2022 16.53.18 WET José Abílio Matos wrote:
> Thank you.
>
> I copied and pasted and while changing the option I left one of those rogue
> characters, keeping always the preffix. :-(
>
>
> I will try and see your suggestion.
After a reboot:
# update-crypto-policies --show
On Monday, 14 March 2022 16.46.39 WET Simo Sorce wrote:
> If you have actually copy/pasted from the terminal it looks to me you
> used an incorrect character when trying to pass a long option, at least
> my MUA shows me you prepend long option names with "–-" instead of
> using the correct "--",
On Mon, 2022-03-14 at 16:35 +, José Abílio Matos wrote:
> On Monday, 14 March 2022 11.04.56 WET Simo Sorce wrote:
> > Have you tried setting crypto policies to LEGACY in case the server is
> > old and supports only bad cryptography?
> >
> > Simo.
>
> How do I do that?
>
> Running
On Monday, 14 March 2022 10.49.38 WET Richard W.M. Jones wrote:
> What's the version of openssl?
The version on F36, that I am using is 3.0.0.
> Is there a public server which you can tell us the name of which gives
> this error?
I am connecting to an exchange email server (2010) using imap
On Monday, 14 March 2022 11.04.56 WET Simo Sorce wrote:
> Have you tried setting crypto policies to LEGACY in case the server is
> old and supports only bad cryptography?
>
> Simo.
How do I do that?
Running update-crypto-policies always returns an error saying that the
argument is not
Have you tried setting crypto policies to LEGACY in case the server is
old and supports only bad cryptography?
Simo.
On Sun, 2022-03-13 at 09:43 +, José Abílio Matos wrote:
> In one, and just one, of my email accounts the upgrade to F36 failed with
> this:
>
> The underlying socket is
On Sun, Mar 13, 2022 at 09:43:43AM +, José Abílio Matos wrote:
> In one, and just one, of my email accounts the upgrade to F36 failed with
> this:
>
>
> The underlying socket is having troubles when processing connection to
> imap.xxx.xx.xx:993: Error during SSL handshake:
> On 13 Mar 2022, at 13:58, Barry wrote:
>
>
>
>
>>> On 13 Mar 2022, at 09:44, José Abílio Matos wrote:
>>>
>>
>> In one, and just one, of my email accounts the upgrade to F36 failed with
>> this:
>>
>> The underlying socket is having troubles when processing connection to
>>
> On 13 Mar 2022, at 09:44, José Abílio Matos wrote:
>
>
> In one, and just one, of my email accounts the upgrade to F36 failed with
> this:
>
> The underlying socket is having troubles when processing connection to
> imap.xxx.xx.xx:993: Error during SSL handshake: error:0A0C0103:SSL
>
In one, and just one, of my email accounts the upgrade to F36 failed with
this:
The underlying socket is having troubles when processing connection to
imap.xxx.xx.xx:993: Error during SSL handshake: error:0A0C0103:SSL
routines::internal error
No email program works, I tried kmail, trojitá,
12 matches
Mail list logo
