james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Baechler (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1933) James should implement all protocols that secure email delivery on the web
Date Tue, 07 Mar 2017 08:50:32 GMT

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

Matthieu Baechler commented on JAMES-1933:
------------------------------------------

Hi,

The source is here : https://github.com/apache/james-project

The README.adoc explains how to setup a running james. Once everything is set up, we can help
you explore the code base to find where protocols are located and how it works.

> 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
>            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.3.15#6346)

---------------------------------------------------------------------
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