Timo Sirainen kirjoitti 28.4.2015 kello 11.35:
>
>> On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
>> When can we expect 2.2.17 to resolve this?
>
> As far as I know this doesn't affect any of the major distributions where
> Dovecot is commonly used (Debian/Ubuntu/Redhat/CentOS). I've only he
On 4/28/15, Timo Sirainen wrote:
> On 28 Apr 2015, at 11:35, Timo Sirainen wrote:
>>
>> On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
>>> When can we expect 2.2.17 to resolve this?
>>
>> As far as I know this doesn't affect any of the major distributions where
>> Dovecot is commonly used (Debi
On 28 Apr 2015, at 11:43, Marc Schiffbauer wrote:
>
> * Timo Sirainen schrieb am 28.04.15 um 11:35 Uhr:
>> On 28 Apr 2015, at 11:35, Timo Sirainen wrote:
>>>
>>> On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
When can we expect 2.2.17 to resolve this?
>>>
>>> As far as I know this doesn
* Timo Sirainen schrieb am 28.04.15 um 11:35 Uhr:
On 28 Apr 2015, at 11:35, Timo Sirainen wrote:
On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
When can we expect 2.2.17 to resolve this?
As far as I know this doesn't affect any of the major distributions where
Dovecot is commonly used (D
On 28 Apr 2015, at 11:35, Timo Sirainen wrote:
>
> On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
>> When can we expect 2.2.17 to resolve this?
>
> As far as I know this doesn't affect any of the major distributions where
> Dovecot is commonly used (Debian/Ubuntu/Redhat/CentOS). I've only hea
On 28 Apr 2015, at 04:15, Edwardo Garcia wrote:
> When can we expect 2.2.17 to resolve this?
As far as I know this doesn't affect any of the major distributions where
Dovecot is commonly used (Debian/Ubuntu/Redhat/CentOS). I've only heard it
happening with some self-compiled OpenSSL versions (A
When can we expect 2.2.17 to resolve this?
