Am 21.04.2016 um 19:29 schrieb Brendan Cully:
> On Thursday, 21 April 2016 at 10:06, Kevin J. McCarthy wrote:
>> On Thu, Apr 21, 2016 at 05:19:00PM +0100, Arnt Gulbrandsen wrote:
>>
>>> One workaround is to send the three commands separately, not at the same
>>> time. I don't like that, it slows do
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: closed
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution: wontfix
On Thursday, 21 April 2016 at 10:06, Kevin J. McCarthy wrote:
> On Thu, Apr 21, 2016 at 05:19:00PM +0100, Arnt Gulbrandsen wrote:
>
> > One workaround is to send the three commands separately, not at the same
> > time. I don't like that, it slows down login in all cases and if really is
> > pipeli
;Kevin J. McCarthy writes:
I suppose we could try that, but I agree this is less than ideal, and
Mutt does using the pipelining in other places. Is Mutt doing
something wrong here (posed to you too Brendan)?
Mutt is behaving perfectly correctly.
Arnt
On Thu, Apr 21, 2016 at 05:19:00PM +0100, Arnt Gulbrandsen wrote:
> One workaround is to send the three commands separately, not at the same
> time. I don't like that, it slows down login in all cases and if really is
> pipelining, then I don't feel confident that the bug only affects THIS
> insta
Kevin J. McCarthy writes:
Did you hear anything back about this? It seemed as if the proxy
couldn't handle any pipelining, from the later comments in the ticket.
I wanted to get back to the ticket reporter, but it would be nice to
know if it was fixed or being worked on.
I heard back, but I'm
On Wed, Apr 13, 2016 at 08:19:54PM +0100, Arnt Gulbrandsen wrote:
> I wrote:
> > That looks more like a load balancer or some sort of frontend... I
> > looked at the full protocol trace in the bug report now and think it's
> > most likely the Oracle server, so I've sent one of the maintainers there
I wrote:
That looks more like a load balancer or some sort of
frontend... I looked at the full protocol trace in the bug
report now and think it's most likely the Oracle server, so I've
sent one of the maintainers there mail about the issue.
The Oracle maintainer will talk to the proxy mainta
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
Brendan Cully writes:
On Wednesday, 13 April 2016 at 07:58, Arnt Gulbrandsen wrote:
I would love to know which server this is.
It appears to be Apple's homegrown IMAP server for imap.mail.me.com
(iCloud).
OK [CAPABILITY mr11p00im-iscream005 15E205 XAPPLEPUSHSERVICE IMAP4
IMAP4rev1 SASL-IR AUT
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
On Wednesday, 13 April 2016 at 07:58, Arnt Gulbrandsen wrote:
> I would love to know which server this is.
It appears to be Apple's homegrown IMAP server for imap.mail.me.com
(iCloud).
OK [CAPABILITY mr11p00im-iscream005 15E205 XAPPLEPUSHSERVICE IMAP4
IMAP4rev1 SASL-IR AUTH=ATOKEN AUTH=PLAIN] iSC
I would love to know which server this is.
Arnt
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
--+
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major| Milestone: 1.6
Component: IMAP |Version: 1.6.0
Resolution
#3832: Cannot connect to IMAP4 mail server
+-
Reporter: mikeegg | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone: 1.6
Component: IMAP|Version: 1.6.0
Keywords
27 matches
Mail list logo
