Feature Request: Unique Email Addresses for Email Integration
Summary
I'd like to request an enhancement to the email integration: the ability to generate a unique, user-specific email address (e.g., [email protected]) instead of relying solely on sender verification through [email protected].
Current Limitation
The current email integration authenticates based on the sender's email address, which must match a registered account email. While this works for sending from personal devices, it creates friction in several common workflows:
Forwarding from other services: Many services (newsletters, receipts, notifications) can't be forwarded automatically because they come from third-party addresses
Automation platforms: Tools like Zapier, Make, n8n, or IFTTT often send from their own domains, making integration impossible
Proposed Solution
Implement a unique email address system similar to Drafts' "Mail Drop" feature:
Generate unique address: Each user gets a personal address like save-[unique-id]@capacities.io
Accept from any sender: Authentication is based on the unique address, not the sender
Reset capability: Allow users to regenerate their address if it gets compromised or receives spam
Coexistence: Keep the current sender-based verification as an additional option
Use Cases
Forward newsletters directly to Capacities for archiving
Connect automation workflows (e.g., "save all starred emails to Capacities")
Forward receipts or booking confirmations from any email account
Integrate with document scanners or OCR services that email results
Share the address with trusted services for automatic content capture
Privacy Consideration
Users would be advised to keep their unique address private, similar to how Drafts handles this. The reset functionality provides a safety valve if the address is accidentally shared.
1 Comment
Sign in to comment

I second this! Just recently got a Remarkable, and it would be great to be able to send directly from the tablet to Capacities. However, the sender of the email from the Remarkable is a generic address which isn't user specific, so I can't add it to the list of emails that can be sent to [email protected]. Unique email-addresses would solve this.