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

Tellier Benoit updated JAMES-1933:
----------------------------------
    Component/s: Matchers/Mailets (bundled)

> James should implement all protocols that secure email delivery on the web
> --------------------------------------------------------------------------
>
>                 Key: JAMES-1933
>                 URL: https://issues.apache.org/jira/browse/JAMES-1933
>             Project: James Server
>          Issue Type: Task
>          Components: Matchers/Mailets (bundled)
>            Reporter: Matthieu Baechler
>              Labels: asciidoc, backend, docker, frontend, gsoc2017, java, js, 
> json, rest, sse
>
> James aims at becoming a leading email solution in the next few years.
> For that to become real, we need to ensure all protocols related to email 
> delivery security are well implemented.
> Today, the protocols are (at least) :
> * SPF
> * DKIM
> * DMARC
> There's already some code about these features in James but we would be sure 
> people interested into James email hosting can configure this protocols 
> easily and that implementations are compatible with most big email providers 
> out there.
> To handle this project, the student have to know enough java to manage James 
> codebase and be confortable in reading RFC and dissecting protocols.
> The James team has a strong focus on testing because email is a serious 
> matter and you would not want to loose user's emails, so we will explain how 
> to work on these tasks with the right testing strategy and tools.
> Finally, this project should conclude with a well-written asciidoc 
> documentation about how one should deploy james with security features 
> configured



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to