> What about sites that don't want to add a pile of additional aliases,
Two additional aliases per list (for zunscribe and unzubscribe) really
isn't that bad, given that for a list with digest we also get rid of two
-outgoing aliases.
> or sites running 1.94? They then become 'incompatible'.
I don't consider that a valid reason against including a feature which is
a real time-saver for the list-owner.
> And you end up issuing
> confirmation tokens for every spam that hits these addresses.
A simple implementation of single-command addresses would generate
confirmation tokens only for reasonably short messages (say, ten lines or
less) and respond to longer messages with a specific help message that
explains how to zubscribe (or unzubscribe).
Any implementation which generates tokens in reaction to spam is very
risky. On a site with many lists (and hence a lot of single-command address
aliases) you need to be careful to make sure that no amount of spam can
crash your MLM.
Has any effort been made yet to secure Majordomo to make sure that the
token generation process can not be abused to make denial-of-service
attacks? (This is an issue which is not specific to single-command
addresses, but one which could potentially become much worse when
single-command addresses are implemented.)
-- NB.
Follow-Ups:
References:
|
|
