On Sun, 30 Mar 1997, Le chaud-lapin wrote:
> 2 simple questions which my brain for some reason refuses to comprehend.
> In the config file for a digested version of a list, do i want to set the
> reply_to value to be the list name or the digest name?
> Do people who are subscribed to the digest version send their posts to
> the list or digest address?
If you want the replies to be readable by both the list and list-digest
members, then the reply-to: header should be pointing to the normal relay
address (which is the default value of the reply_to parameter in a new digest
config file). This is the normal way to handle this.
> Is there anyway to have majordomo realise that members of list are
> members of list-digest for purposes of indexing and getting files?
> I see no real point in using archiving since the messages are saved
> in the digest file.
Why don't you create a soft link from listname-digest.archive pointing to
'listname.archive' (or whatever filedir suffix you are using for your
archives). Example (taken from my site):
% ln -s vocalist-digest.archive vocalist.archive
After you have done this, people may issue either:
get vocalist v03.n130 OR
get vocalist-digest v03.n130
no matter which mailing list they are subscribing to.
> If not, the only solution I can see is a cron job that will copy the
> digest files to an archive directory for the regular list.
No need for that, as you can see... The only problem arises if you have set
get_access = list
Marko Hotti <firstname.lastname@example.org>
System Administrator / Medical Student / Vocalist & Pianist
Phones: +358 40 552 8415 (mobile) +358 8 530 4268 (home) +358 8 312 7172 (otho)
SnailMail: Tervontie 4 C 11, FIN-90230 OULU, Finland
Public PGP encryption key available on request --> email@example.com
www.lists.oulu.fi (list services home page) www.cc.oulu.fi/~mhotti (personal)
From: firstname.lastname@example.org (Le chaud-lapin)