I'm fearful about going live with the list so, --- what are some
sure-fire ways to pull the plug on the list and play it SUPER SAFE, end
mail-loops, flame-wars, etc? What do the pro's do?
By pulling the plug, I'd like to allow for subscription requests to
continue - so mail sent to email@example.com should stay active. Might
be nice to allow for other commands about the list info, which, info,
etc. But, I want to be sure that no mail would go to the list(s).
My newbie guess says one option is to go to the alais file and comment
out the list with
# as the first character of each line.
At the same time I would put a new alias into the top of the alias file
and and reflect all list mail to the list owner too -- while the #
comments are in place later in the file.
Is that it? Mess with alias file and make mail with list address go to
list-owner and all coments to list with #s. ??
When this is up and running as it should be, I should be able to send in
a MODERATE mode with a new list config file, but I've got a ways to go
I saw an older thread in the searchable archives -- but the reasons in my
case are different:
At 9:55 5/30/95, RS wrote:
>Is there any way to temporarily suspend the operation of a Majordomo
>system --- subscription, mailing list activity et al --- but not have
>the messages bounce or disappear?
So long as you are running an SMTP Server, all messages addressed to
Majordomo will be accepted and queued until it comes back up. If there is
no SMTP server running, then the mail will sit on the sender's Server
waiting for your Server to come back up. If you're only down for a day or
2, nothing should get lost (just delayed).
Mark Rauterkus, Publisher, S.S.S.