On 13/08/20 9:16 pm, Michael Ströder wrote:
On 8/13/20 10:56 AM, Aki Tuomi wrote:
On 13/08/2020 11:31 Michael Ströder wrote:
I'm trying to update openSUSE package on OBS [1] which builds for
various OS versions and hardware platforms. To me it seems that a test
fails on 32bit platforms:
Exc
On 17/08/20 9:17 pm, Timo Sirainen wrote:
Looks like it's a gcc bug. It's not initializing the end_of_lines field in the
unit test. Since it's in the unit test only, it's not harmful. Of course, the
same gcc bug could be hitting some important places in the code.. but that's
not a new issue. O
On Mon, 17 Aug 2020, Johannes Rohr wrote:
You need to set
ssl_min_protocol = TLSv1.2 # or TLSv1
Thanks, tried both, but unsuccessfully.
Don't give up too easily/early on this.
I said this before, but MacOSX Mail behaves weirdly. I've more than
once changed a server setting, without appare
Further to below.
I'm getting these errors in the logs:
failed: read(/#userdir#/mdbox/storage/m.19) failed:
zlib.read(/#userdir#/mdbox/storage/m.19): gz trailer has wrong CRC value
at 10376033 (FETCH BODY[])
I'm not sure if it's relevant, but I've set bz2 as the compression
method and not
On 17 Aug 2020, at 05:10, Gerald Galster wrote:
> I don't know how detailed this is in older Apple Mail versions
I don't think the detail has changed in many many years, if at all. I remember
using the logs to troubleshoot security issues 15 years ago.
Mac OS 10.11 El Capitan was released in 20
Am 17.08.20 um 13:10 schrieb Gerald Galster:
>>> You need to set
>>>
>>> ssl_min_protocol = TLSv1.2 # or TLSv1
>> Thanks, tried both, but unsuccessfully. Again, is there any debug
>> setting that allows me to see what SSL version was requested? Without
>> this, this is fumbling in the dark.
> In th
ssl_cert =
This is wrong, it should be:
ssl_cert = The address idaweb-mail.rooot.de does not resolve. There is a
webmail.rooot.de , but its certificate is for mail.rooot.de , which is
wrong. There is also a mail.rooot.de , whose certificate is also for
mail.rooot.de , which is okay.
>> You need to set
>>
>> ssl_min_protocol = TLSv1.2 # or TLSv1
>
> Thanks, tried both, but unsuccessfully. Again, is there any debug
> setting that allows me to see what SSL version was requested? Without
> this, this is fumbling in the dark.
In the german version of Apple Mail go to menu "Fenst
Am 17.08.20 um 12:16 schrieb Aki Tuomi:
> You need to set
>
> ssl_min_protocol = TLSv1.2 # or TLSv1
Thanks, tried both, but unsuccessfully. Again, is there any debug
setting that allows me to see what SSL version was requested? Without
this, this is fumbling in the dark.
Cheers,
Johannes
> On 17/08/2020 12:51 Johannes Rohr wrote:
>
>
> |Dear all,|
>
> |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04,
> thereby upgrading dovecot from 2.2.x to 2.3.x.
> |
>
> |Since then, some older versions of apple's mail.app (bundled with el
> Capitano, released in 201
|Dear all,|
|a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04,
thereby upgrading dovecot from 2.2.x to 2.3.x.
|
|Since then, some older versions of apple's mail.app (bundled with el
Capitano, released in 2016) no longer connect. When I turn on SSL
debugging, I see:|
|Debug:
|Dear all,|
|a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04,
thereby upgrading dovecot from 2.2.x to 2.3.x.
|
|Since then, some older versions of apple's mail.app (bundled with el
Capitano, released in 2016) no longer connect. When I turn on SSL
debugging, I see:|
|Debug:
On 15. Aug 2020, at 14.18, Peter wrote:
>
> Getting this when attempting to build 2.3.11.3 on CentOS 6:
>
> test-mail-cache.c:176: Assert failed:
> strcmp(str_c(str),"123\nfoo\n456\nbar\n")
>"" != "123
> foo
> 456
> bar
> "
> test-mail-cache.c:176: Assert failed:
> strcmp(str_c(str),"1
13 matches
Mail list logo
