On 4 May 1998, Jason L Tibbitts III wrote:
> Some MLMs these days have one address per command, at least for the very
> common commands like zubscribe. Sending a message to that address results
> in the command being executed with the From: address as the victim. Should
> we do this with Majordomo?
This is a very convenient thing, and it makes it easy for neophytes to
understand a one-liner on how to get off the stinkin' list:
"to unzubscribe: send a message to firstname.lastname@example.org"
> I have a vaguely bad feeling about it. It's not difficult to do at all; I
> can write a new mj_command interface to do it in just a few minutes.
I've used lists like this. The only bad feelings I have is remembering
what method to use. This shouldn't be a stopper.
> But then we have to decide which commands get their own separate
Do we? Why not write it such that any command could have it's own
address. Write mj_command to read it's command line as a format string,
and treat the result as a command.
foo-freaks-remove: | mj_command unzubscribe foo-freaks %F
lists-which: | mj_command which %F
lists-command: | mj_command %S
Where mj_command replaces %F with the contents of the From: header, %S
with Subject:, %x with X-MajorDomo, etc., and then executes the command.
I have no initial clue what interpolations other than From: might be
If this is too complicated (too clever by half, I believe, is the phrase),
then just a dedicated unzub address per list would be helpful and anything
else is gravy.
> about sites that don't want to add a pile of additional aliases,
They don't have to. Only the "basic" MJ command method works on those
> or sites running 1.94? They then become 'incompatible'.
Yes and no. All methods that worked on 1.94 still should work on 2.0.
There are now just new options available in addition.
> And you end up issuing
> confirmation tokens for every spam that hits these addresses.
True, but tokens are pretty cheap. Parsing and generating errors for the
spam sent to the majordomo address is probably a whole lot worse.
Mark Rafn email@example.com <http://www.halcyon.com/dagon/> !G