james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTOCOLS-118) Continuation Response can't handle Login
Date Tue, 15 May 2018 08:15:00 GMT

    [ https://issues.apache.org/jira/browse/PROTOCOLS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475475#comment-16475475
] 

ASF GitHub Bot commented on PROTOCOLS-118:
------------------------------------------

Github user Flyffies commented on the issue:

    https://github.com/apache/james-project/pull/115
  
    Hi, thanks I didn't saw the comment policy anywhere, so its noted for the future.
    
    As to the second part of my ticket, I Tcpdumped the actual NGINX to James communication
with my change applied, here it is:
    
    N -> J: 1 login {8}
    J -> N: + Ok
    N -> J: testUser {8}
    
    Then James doen not reqest more content. 
    While attaching to it in Debug I saw the field `retry` in `AbstractNettyImapRequestLineReader`
chenges to true as `AbstractNettyImapRequestLineReader` is recreated.
    
    Thats prevents any other continuation request from being send.
    
    But... When I changed the value to false during debug, nothing got written to nginx and
James tried to send multiple continueation request that time... Its really strange...



> Continuation Response can't handle Login
> ----------------------------------------
>
>                 Key: PROTOCOLS-118
>                 URL: https://issues.apache.org/jira/browse/PROTOCOLS-118
>             Project: James Protocols
>          Issue Type: Bug
>          Components: imap
>    Affects Versions: 1.6.3
>         Environment: Docker
>            Reporter: Marc
>            Assignee: Eric Charles
>            Priority: Major
>
> I was testing with the NGINX Imap Proxy and notices the login just times out.
> The first and Major issue is that the login is split into multiple requests.
> The expected communication from NGINX is the following:
> C -> N: 1 login testUser testPass
> N -> J: 1 login {8}
> J -> N: + Ok
> N -> J: testUser {8}
> J -> N: + Ok
> N -> J: testPass
> J -> N: 1 Ok...
> N -> C: 1 Ok...
> It seems James does not handle the repeated continuation request correctly.
> NGINX is expecting some text after the initial continuation Tag ("+").
> I Submitted a PR to github for that. Changed it so an "+ Ok" is send.
> It seems to be specified by the [RFC 3501|https://tools.ietf.org/html/rfc3501#page-79],
though it is a very vague description. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message