This thread and a recent note from someone with the same problems reminded
me of the way I used to debug the semislug (local sun users group) list.
About once a year rather than sending the normal meeting announcement, I'd
do:
#!/bin/sh
exec < ~/.maillists/semislug.members
while read ADDR NAME
do
mail -s 'Monthly SEMiSLUG Meeting Announcement' $ADDR < announcement
done
This generates a message exactly like what the users expected, but each
send has a unique To: field and Message-ID: field. Now you
know exactly which list entry caused the bounce. If, God forbid, some
brain-dead relayer generated a new msg-id and To: line, you can modify the
script to
#!/bin/sh
exec < ~/.maillists/semislug.members
while read ADDR NAME
do
mail -s 'Monthly SEMiSLUG Meeting Announcement for $NAME' $ADDR < announcement
done
but then you wind up having to explain why everyone's name shows up in the
subject line.
--
Yea, the heavens shall open and the NP-complete solution given forth.
ATT executives shall give birth to two-headed operating systems, and
copyrights shall be expunged. The voice of the GNU shall be heard,
but the faithless will be without transcievers.
|
|
