Displaying 8 results from an estimated 8 matches for "hwhy".
Did you mean:
_why
2018 Jul 30
2
dovecot 2.3.x, ECC and wildcard certificates, any issues
Hi,
Thanks, good news is that worked. Bad news is it all looks good which
means I do not know hwhy my remote clients can't get their email,
looked like from the logs it was that.
Would 143 be better or 993 for the external clients?
Thanks.
Dave.
On 7/30/18, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
>> On 30 July 2018 at 19:16 David Mehler <dave.mehler at gmail.com>...
2018 Jul 30
2
dovecot 2.3.x, ECC and wildcard certificates, any issues
...can use ssl_alt_cert to provide RSA cert too.
>
> Aki
>
>> On 30 July 2018 at 20:05 David Mehler <dave.mehler at gmail.com> wrote:
>>
>>
>> Hi,
>>
>> Thanks, good news is that worked. Bad news is it all looks good which
>> means I do not know hwhy my remote clients can't get their email,
>> looked like from the logs it was that.
>>
>> Would 143 be better or 993 for the external clients?
>>
>> Thanks.
>> Dave.
>>
>>
>> On 7/30/18, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>&g...
2018 Jul 30
4
dovecot 2.3.x, ECC and wildcard certificates, any issues
...;
> >>> On 30 July 2018 at 20:05 David Mehler <dave.mehler at gmail.com> wrote:
> >>>
> >>>
> >>> Hi,
> >>>
> >>> Thanks, good news is that worked. Bad news is it all looks good which
> >>> means I do not know hwhy my remote clients can't get their email,
> >>> looked like from the logs it was that.
> >>>
> >>> Would 143 be better or 993 for the external clients?
> >>>
> >>> Thanks.
> >>> Dave.
> >>>
> >>>
>...
2018 Jul 30
0
dovecot 2.3.x, ECC and wildcard certificates, any issues
...nnot understand ECC certificates? You can use ssl_alt_cert to provide RSA cert too.
Aki
> On 30 July 2018 at 20:05 David Mehler <dave.mehler at gmail.com> wrote:
>
>
> Hi,
>
> Thanks, good news is that worked. Bad news is it all looks good which
> means I do not know hwhy my remote clients can't get their email,
> looked like from the logs it was that.
>
> Would 143 be better or 993 for the external clients?
>
> Thanks.
> Dave.
>
>
> On 7/30/18, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> >
> >> On 30 July 201...
2018 Jul 30
0
dovecot 2.3.x, ECC and wildcard certificates, any issues
...too.
>>
>> Aki
>>
>>> On 30 July 2018 at 20:05 David Mehler <dave.mehler at gmail.com> wrote:
>>>
>>>
>>> Hi,
>>>
>>> Thanks, good news is that worked. Bad news is it all looks good which
>>> means I do not know hwhy my remote clients can't get their email,
>>> looked like from the logs it was that.
>>>
>>> Would 143 be better or 993 for the external clients?
>>>
>>> Thanks.
>>> Dave.
>>>
>>>
>>> On 7/30/18, Aki Tuomi <aki.t...
2018 Jul 30
2
dovecot 2.3.x, ECC and wildcard certificates, any issues
Hello,
Does dovecot 2.3.x have any issues recognizing or using certificates
that are ECC and wildcard? I'm trying to switch my letsencrypt
implementation from acme-client which does not support either of those
capabilities to acme.sh which does. Since then external clients
checking their email has not worked. A manual telnet to
mail.example.com 993 gives a connected message but then nothing
2018 Jul 30
0
dovecot 2.3.x, ECC and wildcard certificates, any issues
...0 July 2018 at 20:05 David Mehler <dave.mehler at gmail.com> wrote:
>> >>>
>> >>>
>> >>> Hi,
>> >>>
>> >>> Thanks, good news is that worked. Bad news is it all looks good which
>> >>> means I do not know hwhy my remote clients can't get their email,
>> >>> looked like from the logs it was that.
>> >>>
>> >>> Would 143 be better or 993 for the external clients?
>> >>>
>> >>> Thanks.
>> >>> Dave.
>> >>...
2018 Jul 30
2
dovecot 2.3.x, ECC and wildcard certificates, any issues
...05 David Mehler <dave.mehler at gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Thanks, good news is that worked. Bad news is it all looks good which
>>>>>> means I do not know hwhy my remote clients can't get their email,
>>>>>> looked like from the logs it was that.
>>>>>>
>>>>>> Would 143 be better or 993 for the external clients?
>>>>>>
>>>>>> Thanks.
>>>>>> Dave...