Displaying 11 results from an estimated 11 matches similar to: "lmtp Panic Buffer write out of range"
2018 Aug 22
0
lmtp Panic Buffer write out of range
Op 21-8-2018 om 14:57 schreef Gabriele Nencioni:
> Hi all,
> as described here:
> https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html
>
> we are experiencing the same error on dovecot version 2.3.2.1
> while it never occurs on an old version as 2.2.15
This looks a lot like:
https://dovecot.org/list/dovecot/2018-July/112167.html
That one is fixed pending release.
2018 Aug 07
4
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
Hi all,
we are upgrading our dovecot platform from:
# dovecot --version
2.2.15.14 (39f57c379ded+)
to
# dovecot --version
2.3.2.1 (0719df592)
Our platform is debian based and it is configured as director and
backend proxy.
We have just upgrade only 4 servers (2 directors and 2 backends) and
when the lmtp traffic flow goes through an upgraded director and a
not-upgraded backend sometimes the
2018 Aug 08
0
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
Hi,
Op 07/08/2018 om 09:35 schreef Gabriele Nencioni:
> Hi all,
> we are upgrading our dovecot platform from:
>
> # dovecot --version
> 2.2.15.14 (39f57c379ded+)
Great! A mummy from ancient times.
That is going to make reproducing the circumstances here a bit difficult
(difficult to get that compiled here anymore). I cannot reproduce
anything like that so far with current
2018 Aug 23
1
lmtp Panic Buffer write out of range
On 08/22/2018 04:03 PM, Stephan Bosch wrote:
> Op 21-8-2018 om 14:57 schreef Gabriele Nencioni:
>> Hi all,
>> as described here:
>> https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html
>>
>> we are experiencing the same error on dovecot version 2.3.2.1
>> while it never occurs on an old version as 2.2.15
>
> This looks a lot like:
>
2018 Aug 17
2
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
On 08/16/2018 11:48 PM, Stephan Bosch wrote:
> Op 16/08/2018 om 12:01 schreef Stephan Bosch:
>> I have a theory. Will try something later today.
>
> Yes, I can reproduce the problem. I am working on a fix.
Thank you very much!
I'm here if you need something.
Regards,
--
Gabriele Nencioni
System Administrator
eml gabriele.nencioni at register.it
2018 Oct 08
1
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
Op 8-10-2018 om 11:43 schreef Gabriele Nencioni:
> On 8/17/18 8:17 AM, Gabriele Nencioni wrote:
>> On 08/16/2018 11:48 PM, Stephan Bosch wrote:
>>> Op 16/08/2018 om 12:01 schreef Stephan Bosch:
>>>> I have a theory. Will try something later today.
>>> Yes, I can reproduce the problem. I am working on a fix.
>> Thank you very much!
>> I'm here
2018 Aug 16
2
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
Op 16-8-2018 om 11:47 schreef Gabriele Nencioni:
>>>> On 08/09/2018 09:12 AM, Stephan Bosch wrote
>>>>>>> Can you make a pcap log of the LMTP communication between the two
>>>>>>> Dovecot hosts? That may give me a clue on which side of the
>>>>>>> communication is causing the issue.
>>>>>> Yes sure, where
2019 Sep 09
1
CVE-2019-11500 and LMTP error
Hi all,
does the dovecot fixed version: 2.3.7.2, 2.2.36.4 (as the CVE-2019-11500
says) fix the LMTP error "Got unexpected reply" as well?
The LMTP error "Got unexpected reply" is described here:
https://dovecot.org/pipermail/dovecot/2018-August/112562.html
https://dovecot.org/pipermail/dovecot/2018-August/112666.html
Thanks in advance
Regards,
--
Gabriele Nencioni
2012 Apr 09
2
Problem with quota warning
Hi again,
my test environment is working now and finally I tried to implement my
quota warning but it is not working. LDA says the mailbox is full even
it is not (only 81% and that is why the quota warning is executed).
Further I used :noenforcing in my script.
Apr 9 15:08:21 backend01 dovecot: lda(test at k-team.info): Debug:
Namespace INBOX.: Using permissions from
2018 Aug 16
0
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
>>> On 08/09/2018 09:12 AM, Stephan Bosch wrote
>>>>>> Can you make a pcap log of the LMTP communication between the two
>>>>>> Dovecot hosts? That may give me a clue on which side of the
>>>>>> communication is causing the issue.
>>>>> Yes sure, where I can send it?
>>>>> Here on list or at your address?
2018 Oct 08
0
Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
On 8/17/18 8:17 AM, Gabriele Nencioni wrote:
> On 08/16/2018 11:48 PM, Stephan Bosch wrote:
>> Op 16/08/2018 om 12:01 schreef Stephan Bosch:
>>> I have a theory. Will try something later today.
>>
>> Yes, I can reproduce the problem. I am working on a fix.
>
> Thank you very much!
> I'm here if you need something.
Hi,
does the release 2.3.3 fix this