IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2022/10/05
~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%cumlord
+FreefallHeavens
+Xeha
+ardu
+bak83
+mareki2p
+onon_
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
AHOH2
Arch
BubbRubb1
Danny
DeltaOreo
FreeB
HowardPlayzOfAdmin
Irc2PGuest32661
Irc2PGuest63604
Irc2PGuest79272
Irc2PGuest89963
Meow
Onn4l7h
Onn4|7h
acetone_
anontor2
boonst_
duck
maylay
pisslord
poriori_
r3med1tz
reburial
shiver_
simprelay
solidx66
thetia
u5657
usr003
weko_
zer0bitz
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.