Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTOWN-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Menu
LISTSERV Archives LISTSERV Archives
LSTOWN-L Home LSTOWN-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Reply-To Question from a New Listserv Admin
From:
Pete Weiss <[log in to unmask]>
Reply To:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Wed, 20 Mar 2002 14:17:36 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
At 10:34 03/20/2002 Wednesday, Kevin Parris wrote:
 >Send a command something like this:
 >
 >  quiet set list-name repro noack nodigest for *@*
 >
 >to set those options for all subscribers to your "list-name" list.  You
 >can use other wildcard patterns to refine the affected subscribers to
 >various subsets of the population.  The "quiet" prefix stops the server
 >from sending an email to each subscriber telling them about the changes
 >you just made.  Now, to be extremely precise, the way to change the
 >"default settings" is to use the list-header keyword by that name, since
 >anything you do by a SET command as illustrated above, actually apples to
 >the "current settings" in effect for the subscribers at the time the
 >command finishes.  The list header keyword determines what settings a
 >subscriber will be given at the time they join the list, but they are free
 >to change most of them later as they wish.

So, for completeness:

1) first update the list definitions, then

2) do the QUIET SET

Of course there are always second order effects e.g., a batch job system
like you might find in MVS (OS/390) might not "want" to get an ack or
repro since the auto- mail might be unexpected.  Or for certain
distribution options, it might "break" the receiver's successful
processing of the inbox.

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV