Post by Conor McGee

1Cpore…7UG1 Unverified · twetch

What ever happened to Baemail?

What the chain says
Block
963 555
Time
2026-08-23T10:59:06Z
Signer
1CporeJP76jtbAd3AHXAA4ZTYYMo3J7UG1
App
twetch
Type
post
Content type
text/markdown

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1CporeJP76jtbAd3AHXAA4ZTYYMo3J7UG1 Unverified

Replies (10)

1aUt6N…jRpF Unverified · twetch
Replying to@1Cpore…7UG1

I wouldn't worry too much
serverless decentralized email
Amail is on the horizon

Attached image
1EkygL…i6ks Unverified · twetch
Replying to@1aUt6N…jRpF

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?

1aUt6N…jRpF Unverified · twetch
Replying to@1EkygL…i6ks

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

1aUt6N…jRpF Unverified · twetch
Replying to@1aUt6N…jRpF

one thing to note
annodes do not use IP's to connect
with ghost-net upgrade
all accounts (NID's) resolve to onions
and nodes connect via tor
so you can run normal websites or apps from your home
and keep the source annode in your home private
without it's IP ever being exposed

Attached image
Continue thread →
1EkygL…i6ks Unverified · twetch
Replying to@1aUt6N…jRpF

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?

Continue thread →