Who we are   Organizations   Get Involved!   Helpdesk   Weblog   About FLORA   Server project   F.A.Q.

Election 2006 (and beyond): Digital Copyright Canada

Re: Thanks Krishna, but more queries on 1) & 2)

From: Russell McOrmond <russell_-at-_flora.ca>
To: flora-admin-help_-at-_flora.ottawa.on.ca
Date: Thu, 15 Nov 2001 18:59:16 -0500 (EST)

On Thu, 15 Nov 2001, Richard Sanders wrote:

> (1) The digest seems to be merely a way of packing the whole text of
> multiple messages into single emails.  This saves no room, just the number
> of emails one gets.

Correct.

> Does it mean at least that at the top of the email you
> get a list of the messages that are below?

  In your -digest config look at message_fronter.

Here is a cut from the mai-not-digest config file:


---cut---

        # message_fronter      [string_array] (undef) <resend,digest>
        # Text to be prepended to the beginning of all messages posted to
        # the list. The text is expanded before being used. The following
        # expansion tokens are defined: $LIST - the name of the current
        # list, $SENDER - the sender as taken from the from line, $VERSION,
        # the version of majordomo. If used in a digest, only the expansion
        # token _SUBJECTS_ is available, and it expands to the list of
        # message subjects in the digest
message_fronter     <<  END
In this issue:
_
_SUBJECTS_

END

---cut---




> (2) I note that it says:
>                                                                           if
> 	     # restrict_post is defined, only the addresses in those files are
>             # allowed access.
> 
> so actually then it seems that I can put my address in a file somewhere so
> that I'll still be able to use the "who" command.  That would be the best
> option, at least for me.  


  restrict_post is the feature that is used to define "member of list",
and who can and cannot post to your list.  It points to the list names,
and thus the files that represent the membership of the list:


From mai-not-nomail config file:

---cut---

        # restrict_post        [restrict_post] (undef) <resend>
        # If defined, only addresses listed in these files (colon or space
        # separated) can post to the mailing list. By default, these files
        # are relative to the lists directory. These files are also checked
        # when get_access, index_access, info_access, intro_access,
        # which_access, or who_access is set to 'list'. This is less useful
        # than it seems it should be since there is no way to create these
        # files if you do not have access to the machine running resend.
        # This mechanism will be replaced in a future version of
        # majordomo/resend.
restrict_post       = mai-not:mai-not-nomail:mai-not-digest

---cut---



  You don't want to use this for the 'who' command if you want it to be
private, as using it would mean that all list members would still have
access to it.


  If you want to use the who command yourself, then just use the approval
password:

EG:

approve listpassword who listname

---
 Russell McOrmond, Internet Consultant: <http://www.flora.ca/>
 See http://weblog.flora.org/ for announcements, activities, and opinions
 Oppose DMCA in Canada! (C) reform process....  IP Counter Essay Contest!
 It is time to mourn and reflect, not anger.... Appeal 'No more violence!' 

Please read the FLORA.org Terms and Conditions before you submit information to FLORA.org
Join the Blue Ribbon Online Free Speech Campaign (USA) (Canada)	FLORA Community Web (FLORA.ORG) is sponsored by FLORA Community Consulting (FLORA.CA).