james-server-dev mailing list archives

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

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

Tellier Benoit commented on JAMES-1933:
---------------------------------------

Hi,

Basically, nobody was born "email specialist". All you need is understand the problem that
SPF, DKIM and DMARC are trying to solve and their internal behaviour. For this, even Wikipedia
is a good start.

Then, when you need it, you can go and read the specific RFCs when working on a specific topic.
Here they are:
 - https://tools.ietf.org/html/rfc7208 SPF
 - https://tools.ietf.org/html/rfc6376 DKIM
 - https://tools.ietf.org/html/rfc7489 DMARC

You can refer to them when you are working on these topics. We will, of course, provide support
during the implementation process.
 - Reviews on GitHub as needed
 - Of course, answer your questions

About JSPF, I executed some test coverage tests that seems pretty good (80%). However, JSPF
seems to be written for RFC-4408, which have been obsoleted by RFC-6376. However, the list
of changes between RFCs versions is rather small https://tools.ietf.org/html/rfc7208#appendix-B

It can be cool to have a mailet for JDKIM also as part of James project. The mailet is included
in james-jdkim mailets. Maybe as a first task, you can move this mailet in james-project/server/mailets?
This would allow JDKIM to live as a completely separated library, and avoid troubles upon
releases.

I created this ticket: https://issues.apache.org/jira/browse/JAMES-1975. Could you get a try,
and open relevant pull requests on both JDKIM project and JAMES project?

Cheers,

Benoit

> 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