IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2022/10/05
~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens_
+Xeha
+acetone
+bak83_
+hk
+mareki2p
+profetikla
+r00tobo_BNC
+snex
+uop23ip
+weko
Arch
Danny
DeltaOreo
Irc2PGuest12249
Irc2PGuest25220
Irc2PGuest90883
Irc2PGuest92478
Junkyard5
Leopold_
Meow
Nausicaa
Onn4l7h
Onn4|7h
aisle1
anu3
ardu
boonst
deadface
dickless
duck
enoxa
evasiveStillness
foobar_
mareki2pb
maylay
not_bob_afk
poriori_
qend-irc2p
radakayot_
shiver_
simprelay
solidx66
tr
u5657
usr001
woodwose
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.