[vox-tech] Change to vox-tech list moderation

[Rick Moen]

Quoting Bill Kendrick (nbs at sonic.net):

> My problem was that the subject lines were all the same: a generic
> message telling me something got auto-discarded.

Just to be clear, I wasn't referring to the '(n) messages were
discarded' advisories.

In the model where non-subscriber postings get held and expire out, the
listadmin gets a daily summary of main headers of all held messages,
which is _usually_ enough information to spot quickly any held non-spam.
What I was saying is that, in the event of uncertainty about that
judgement, if you _also_ receive an immediate notice on each message
being held, then even if a non-spam expired out of the queue before you
could approve it, you as listadmin can retrieve the full message from
the immediate-notice advisory message and re-send it manually.

I find this a workable routine, especially with a 3-day hold duration.
Obviously, Views Differ{tm}.  ;->

IMO, if the spam is too onerous even with intelligent management of the
Mailman queues, then it means you aren't doing good enough
spam-rejection inside the receiving MTA, and should concentrate on
improving _that_.  

Linux MTAs have totally inadquate default antispam defences on (to my
knowledge) all Linux distributions.  I would guess this has been one of
the biggest motivators driving the ongoing flight away from people
operating their own MTAs and onto outsourced webmail (e.g., GMail,
Fastmail, and competitors).  Being stubborn, I went the other way:  'Ah, 
needs better early-SMTP antispam', and tightened things up.

Again, absolutely not being critical of other people finding different
solutions.  Being caught in the middle of the spam war is a difficult
situation, and mailing list managers, being SMTP forwarders, are
inherently caught in the crossfire more than other systems are.