Doichain/dapp

Write smtp-filter for postfix

Open

#101 opened on Mar 29, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (13 forks)auto 404
A prioritybountyfeaturehelp wantedtesttext & doc

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Every Doichain-dApp in confirm-mode holds data of it's own recipients and allowed senders from outside. If an email comes in, postfix should check over REST-API verify call, if this record exists and if the Double-Opt-In permissions are valid.

So far Doichain-dApp has a REST-API "verify" interface which takes 4 arguments instead of only two! This call works on all dApps because it checks directly inside the blockchain. https://github.com/Doichain/dapp/blob/master/doc/en/rest-api.md#verify-opt-in

We need to add a second verify call which takes only 2 arguments (recipient_mail & sender_email) which will work only at the Doichain-dApp of the responsible (trusted third party) Node.

Please see https://bounties.doichain.org/ how to apply for Doichain bounties.

Contributor guide

Research direction
Study the existing verify endpoint that accepts 4 arguments, then implement a new endpoint that takes only recipient email and sender email, querying the local dApp database instead of the blockchain. Refer to the REST API documentation and route handlers.
Tech stack
javascriptnodejsrest api
Domain
backendapibackend api design
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScriptNode.jsREST API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65