[ 
https://issues.apache.org/jira/browse/JAMES-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey B. updated JAMES-3022:
-----------------------------
    Description: 
According to [RFC3848|https://tools.ietf.org/html/rfc3848], keyword "ESMTPS" 
indicates the use of ESMTP when STARTTLS is also successfully negotiated to 
provide a strong transport encryption layer and keyword "ESMTPSA" indicates the 
use of ESMTP when both STARTTLS and SMTP AUTH are successfully negotiated.

James should conform to this standard. Curently it provides only SMTP, ESMTP 
and ESMTPA transmission types.

  was:
According to [RFC3848|https://tools.ietf.org/html/rfc3848], keyword "ESMTPS" 
indicates the use of ESMTP when STARTTLS is also successfully negotiated to 
provide a strong transport encryption layer and keyword "ESMTPSA" indicates the 
use of ESMTP when both STARTTLS and SMTP AUTH are successfully negotiated.

James should conform to this standard. Now it provides only SMTP, ESMTP and 
ESMTPA transmission types.


> Add ESMTPS and ESMTPSA Transmission Types to Received header
> ------------------------------------------------------------
>
>                 Key: JAMES-3022
>                 URL: https://issues.apache.org/jira/browse/JAMES-3022
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Sergey B.
>            Priority: Major
>
> According to [RFC3848|https://tools.ietf.org/html/rfc3848], keyword "ESMTPS" 
> indicates the use of ESMTP when STARTTLS is also successfully negotiated to 
> provide a strong transport encryption layer and keyword "ESMTPSA" indicates 
> the use of ESMTP when both STARTTLS and SMTP AUTH are successfully negotiated.
> James should conform to this standard. Curently it provides only SMTP, ESMTP 
> and ESMTPA transmission types.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to