The whole idea is your email is stored on your local computer and that of your recipient's.
This is how it works:
first the user downloads and installs the email server on his machine. Then create a private and public
keys for encrypting his/her data.
The user then registers his account with a public server which only keeps public keys and trackers for
individual email servers.
So when an individual create an email, the email is encrypted with the recipient public key
and with the help of the tracker the email is send directly to the recipient's local emails server for any
reason if the recipient email is off line the public server gives the option to store the encypted email for only
a time determined by the sender.

By the way this is an open source project

What do you guys think of this project and will it fly? if it is good how do we get some crowdfunding for it
and who will like to partiner me do this project? :)

Dani AI

Generated

As pointed out, the concept has precedents in fiction, and 's PGP note highlights the obvious cryptographic baseline. Turning the idea into a usable, trustworthy project depends on solving engineering and UX problems that often sink otherwise-promising designs. The most important practical concerns are:

  • Reachability and NAT/firewall traversal. True peer-to-peer delivery to arbitrary home or mobile devices requires STUN/TURN-style techniques or an encrypted relay fallback; handling dynamic IPs and intermittent connectivity must be designed up front.
  • Key discovery and trust bootstrapping. A single public registry is simple but centralizes trust; alternatives include signed directory records, DHT pinning, DNS-based proofs, and clear, user-facing fingerprint verification. Plan for revocation and key rotation.
  • Metadata leakage. Even if message contents are encrypted, directory entries and delivery receipts leak who talks to whom and when. If metadata resistance is a goal, it needs explicit design (mixing, relays, onion routing).
  • Spam and abuse control. Decentralized inboxes are attractive to spammers. Consider rate limits, lightweight proof-of-work, sender reputation, or opt-in whitelisting to avoid degrading usability.
  • Multi-device sync and backups. Local-only mailboxes complicate multi-device use and lost-key recovery. Provide client-side encrypted backups, device pairing (scannable fingerprints/QR), and a clear recovery strategy.
  • Forward secrecy and message lifecycle. Static keys protect content but not past messages if keys are later compromised. Design for ephemeral session keys or a ratchet mechanism and clear deletion semantics.

A pragmatic MVP: a reference client that uses audited crypto libs, a minimal signed key directory, NAT traversal plus an encrypted relay fallback, clear fingerprint verification UI, and basic anti-abuse measures. Prioritize a simple threat model and demonstrable proof-of-concept before expanding features.

For funding and adoption, transparent documentation, a live demo, a short roadmap, contributor-friendly governance, and interoperability with existing secure-mail tooling will attract both backers and developers. Legal/privacy implications ( subpoenas, data retention ) and non-technical user experience are the highest-risk obstacles to address early.

Recommended Answers

All 4 Replies

Member Avatar for Member #120589

Sounds like the system mentioned in Neal Stephenson's "Cryptonomicon" (published 1999). You sure there isn't something like this out there already?

It just dropped into my head when reading about diaspora project but now u mention it i will Search for it and see

The whole idea is given the sender power over his or her emails your emails are stored locally on your pc or device More over ur emails are encrypted OK I just reax of bitmail but i did not see any thing about encryption

Sounds like PGP.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.