@@ Protocol — The Email Arrives, But Doesn't Travel
New times, new technologies, new demands, new threats. Do you want to continue with an email protocol that is over 50 years old?
eHead and eBody need each other. One without the other is nothing, and therefore, they never travel together.
Same split-body protocol and features. Choose your preferred domain for your @@ address.
usuario@@q-day.email
usuario@@doubleat.email
🔐 Split-Body Architecture
The email body (eBody) is split from the message and stored separately. Without both parts, the content cannot be reconstructed — not even with the password.
📤 Two-Part System
The message is split into: eHead (max 50 KB, travels by email) and eBody (stored on the server). Each part is useless without the other.
👂 Only Recipient Can Read
Only the recipient can join eHead with eBody, therefore only they can reconstruct the original message.
🌍 Universal @@ Format
DAE emails are identified by their unique format aaa@@bbb.ccc, easy to recognize and compatible with any traditional email system.
⏰ Secure Downloads
eBodys have unique tokens and configurable expiration dates. All downloads are logged for complete security and traceability.
📋 Complete Logging
Unlike '@' email, '@@' email has no attachment size limit, only the limitation imposed by the service provider.