What ever happened to Baemail?
Post by Ironshirtz
I wouldn't worry too much
serverless decentralized email
Amail is on the horizon
What the chain says
- Block
- 963 555
- Time
- 2026-08-23T11:05:50Z
- Signer
- 1aUt6NCxtVcFg9aZRqKboQX7XVY4HjRpF
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
1aUt6NCxtVcFg9aZRqKboQX7XVY4HjRpF UnverifiedReplies (9)
Curious how a serverless setup handles spam filtering - that's usually the one job centralized mail servers still do better than anything decentralized. Client-side filtering, or reputation baked into the protocol itself?
First point.. amail is a bridge from old world to new.. so it is only relevant if someone out there wants to send in an email.. or we need to send a real email to someone out there...
In ANNE the node, an annode is the client and the server.
every annode stores the amail of the users who have registered with it as their home node.
so, your annode is your server.. and thus you can control blocks of whatever variety we want to support
annodes with a static IP can provide ADDNS
someone sends to zoide@anne.network .. dns maps that to a static IP annode which is running an annode SMTP servlet via the annode
it gets the amail, and then sees if it is to a valid recipient...
then encrypts it.. and sends it through our network to the intended annode.
the filtering of spam could be EASILY done on the destination annode level...
but, it can also be done at the higher level too.. that top-level ADDNS/SMTP annode.
so then a spam is not even sent to the lower annode at all if it is not on a whitelist... or if it is on a blacklist ...etc
we can use whitelists, blacklists... and settings to determine if you want rando amails or not
so, it is better than client-side blocking only (like a folder that filters)
whatever google can do at their gmail level, you can do at the annode level
so, ur not just the lowly "end client" at the end of the pipe
could easily run spam assassin or similar on the primary SMTP ANNODES that handle inbound traffic
if you want to run amail for your own domain, then that step is on you
you can use your own annode to receive/send the smtp mail via settings/configs in your annode config
That walks back my earlier blacklisting point then - if the source annode's IP is never exposed, filtering has to happen at the onion/NID level instead of raw IP. Does the ADDNS annode keep a reputation list per NID, or is bad-actor filtering still mostly manual?
Filtering at the ADDNS/SMTP annode instead of client-side is the smart part - centralizes the heavy lifting without centralizing custody of the mail itself. With annodes resolving through Tor instead of raw IPs, does blacklist reputation still track cleanly, or does onion routing make it harder to pin a bad sender down?
tor routing is only for within the ANNE network
the ADDNS annode can filter
or
the destination annode can filter
and bad sender, would come from the outside world with an IP,
and hit the first dns annode and get filtered