Sorry folks but it looks like the SCRoots Forum email server got confused a 
while back.  For some reason it seems that the Forum setup was 
changed.  I've reconfigure the settings back to the way I had them set 
before this glitch happened.  For those who may be interested, shown below 
are the email settings I've re-established for the SCRoots Forum.


Settings for SCROOTS Mailing List
--------------------------------------------------------------------------------

  Largest allowable message, in characters:

If you select a value larger than your digest, you will on occasion have 
someone respond to a message from the digest and quote the entire digest. 
Selecting a smaller value can protect against that error, and also protects 
against new subscribers who innocently attempt to post large GIFs of 
tombstone photographs, etc.

Current setting: 30000

Options: 10000 15000 20000 30000 50000 75000 100000 190000

--------------------------------------------------------------------------------

  Number of bounces before removing an address (mail mode):

If you select a small value, you will sometimes remove addresses that are 
only temporarily bad. If you select a large value, you may go nuts as the 
bounces pile up in your mailbox.

Current setting: 16

Options: 3 4 8 12 16

--------------------------------------------------------------------------------

  Number of bounces before removing an address (digest):

Current setting: 12

Options: 3 4 8 12 16

--------------------------------------------------------------------------------

  Allow only subscribers to access archive via e-mail?

Once the new archiving system is in place, there will only be a limited 
number of messages available via the e-mail archive: probably the last two 
or four weeks' messages. This switch has no effect on the web archives for 
your mailing list, if they exist.

Current setting: no

Options: yes no

--------------------------------------------------------------------------------

  Allow people to subscribe themselves by sending the command "subscribe" 
to the -request address?

If you select "no" for this option, all requests to subscribe will be 
forwarded to you, and only you will be able to add new subscribers to your 
mailing list.

Current setting: yes

Options: yes no

--------------------------------------------------------------------------------

  Moderate this list?

If the list is moderated, then only people on the accept list will be 
permitted to post. Mail from other people will say {not a subscriber} even 
if they are subscribers. This can be an effective way to deal with 
troublemakers, but use it sparingly. Important! Make sure that YOUR OWN 
ADDRESS is on the accept list if you choose this option!

Current setting: unmoderated

Options: moderated unmoderated

--------------------------------------------------------------------------------

  Send the semi-useless "help" file when a bad command is received?

How useless? It is very generic and geeky. I only recommend this for lists 
where the listowner is having to intervene so frequently to assist with bad 
commands that he/she is going nuts. (We use it on ROOTS-L...)

Current setting: yes

Options: yes no

--------------------------------------------------------------------------------

  Notify the list manager when someone subscribes?

Notification in this case consists of the list owner being sent a copy of 
the request to subscribe. There will be an X-Diagnostic line of some type 
saying what action SmartList took on the request. I like this option on my 
small lists, I do not use it on my large ones.

Current setting: no

Options: yes no

--------------------------------------------------------------------------------

  Notify the list manager when someone unsubscribes?

Notification in this case consists of the list owner being sent a copy of 
the request to unsubscribe. There will be an X-Diagnostic line of some type 
saying what action SmartList took on the request.

Current setting: no

Options: yes no

--------------------------------------------------------------------------------

  Prepend something to the subject of each message?

If you enter ``SCROOTS'' here, then a subject line that says ``Looking for 
John Smith'' will be changed to ``[SCROOTS] Looking for John Smith.'' To 
disable the subject-line prepend, leave this box blank.

Note: the best thing for the subject prepend is generally the full list 
name, i.e. SCROOTS. If you want to use a different prepend, remember that 
the one you choose may already be in use on another list! That would make 
things confusing for anyone subscribed to both lists. Listen to your 
subscribers, and try to avoid namespace collisions.

Prepend this to each subject line:

Current setting: [SC]

--------------------------------------------------------------------------------

If the person sending a message to the list did not include a Reply-to line:
(SmartList will never overwrite a Reply-to that the person sending the 
message includes, so even if you select reply-to-list, there will still be 
some messages where the reply only goes to the sender. The SmartList 
documentation discourages the use of reply-to-list, but I have never seen 
it malfunction myself. Caveat emptor?)

Current setting: do nothing (reply should go to sender)

Options:

do nothing (reply should go to sender)

insert a line to direct replies to the list

--------------------------------------------------------------------------------

  When should a digest be sent?

Whenever a message is received, SmartList will evaluate whether it is time 
to send the digest. If it has been longer than the time specified here, or 
if the digest would be larger than the size specified below, the digest is 
released. Note that if no message is received for weeks, it may be weeks 
before the digest is released, even if a much smaller time was specified 
here. Times are given in seconds.

Current setting: 172800

Options: 43200 (12 hours) 64800 (18 hours) 86400 (24 hours)
          172800 (48 hours) 259200 (72 hours)

--------------------------------------------------------------------------------

  How large of a digest should be sent?

Whenever a message is received, SmartList will evaluate whether it should 
release the digest. If it has been longer than the time specified above, or 
if the digest would be larger than the size specified here, the digest is 
released. Sizes are given in bytes or characters.

Current setting: 32768

Options: 20000 25000 28000 32768 40000

--------------------------------------------------------------------------------

  Use RootsWeb's commercial taglines?

RootsWeb offers some tagline space for companies that want to put 
commercial messages there. These taglines are added to unsponsored lists. 
One of the ways you can help RootsWeb is by voluntarily adding these 
commercial taglines to your list as well. They will be added below any 
regular taglines you may already be using, and won't interfere with them.

Current setting: Use commercial taglines

Options:

  Use commercial taglines
  Don't use commercial taglines

--------------------------------------------------------------------------------
   

==== SCROOTS Mailing List ====