Given the recent thread in list-managers about which MLMs save the headers
from incoming email requests and a bit of prompting from Norbert Bollow, I
took a day and implemented this kind of functionality.
Whenever a client starts up Majordomo, it passes to it the useful
information it has about the current session. For email, that's the
headers. For a CGI, it's the environment (although someone who knows more
about CGI will have to tell me something about what information there is
actually worth saving). For the shell it's currently a few environment
This session info gets stuffed in a file. All commands that are executed
in this session and all tokens that are generated are tagged with the
session ID. There is a "sessioninfo" command that retrieves these, and a
"tokeninfo" command that retrieves everything known about a confirmation
token, including the session info. There will eventually be code that goes
through and expires them after some number of days.
When someone rejects a confirmation token, the alarms go off and
responsible parties (including the token recipient) are mailed a copy of
the session information.
So day you're browsing your daily list report (i.e. some time after I've
written the code to do list reports) and you see a pile of consecutive
"lists" commands. You can then take the given session IDs, look them up,
and raise hell with the postmaster at whatever site they went through.