IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2022/10/05
~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%acetone
%mareki2p
%snex
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+fa
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sexy
+uop23ip
Arch
Holmes
Irc2PGuest28384
Irc2PGuest44044
Irc2PGuest48199
Irc2PGuest75571
Irc2PGuest86649
Irc2PGuest95381
Meow
RTP_sleep
[-_-]
ahiru
anontor2
cims
entity
floatyfloatilla
interesting
justaperson
mahlay
makoto
n2
nilbog
not_bob_afk
pinotto
r00tobo[2]
uberius
user1
user_ygg2_
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.