IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2022/10/05
~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Irc2PGuest92669
+Xeha
+cumlord
+j6
+onon
+profetikla
+r00tobo
+snex
+uop23ip
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
Irc2PGuest45008
Irc2PGuest68141
Irc2PGuest71319
Irc2PGuest91332
Irc2PGuest92810
Onn4l7h
acetone_
anon2
anontor
anu
bak83_
boonst
goose
itsjustme
mareki2pb
no1
poriori_
qend-irc2p
shiver_
u5657
unwr
AmyMalik had a dumb idea
AmyMalik it's for preventing MAIL FROM forgery in i2p and tor, by providing a token system, where the recipient server would hold up the sender, contact the putative sender server's token program, ask the sender server "do you recognize this token?", and it'd give a K for yes, Z for "maybe quarantine it?" or D for no - which would then be used to decide the disposition of the message. Unlike
AmyMalik with clearnet email, where there's an IP address, and my personal recommended action for SPF fail is to quarantine, I would recommend, for a token exchange fail, that the receiving mailer drop the message, either 4xx 4.x.x for a Z or a "you forgot to turn up your token server", or 5xx 5.x.x barred by sender policy for a D from the token server.