[
https://issues.apache.org/jira/browse/JAMES-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943632#comment-15943632
]
Shrumit Mehta commented on JAMES-1933:
--------------------------------------
Hi Benoit,
Thanks for the reply. I've had a look at your links.
So it looks like the following tasks are pending:
jSPF
- some more tests on the library
- tests for Mailets
jDKIM
- SMTP Handler + tests
DMARC
- complete jDMARC library + tests
- SMTP Handler, Mailets, tests
Is everything listed here is within the scope of Summer of Code? Are there
existing design/architecture plans for jDMARC? Do you expect a thorough
architecture plan in the Proposal?
I've been going through the James, jSPF, jDKIM codebase and the Wiki pages
trying to understand everything and it's definitely quite daunting. My
knowledge of email protocols is a bit hazy from Networks class which I took 2
years ago, so I'm brushing up on that as well. How much of an understanding of
the codebase and email protocols are you looking for at the Proposal stage?
Is there anything else I should look at? Do you have any other tips or
expectations?
Thanks,
Shrumit
> 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: [email protected]
For additional commands, e-mail: [email protected]
