At 06:52 AM Friday, 1/20/2006, you wrote -=>
>Ed Kasky wrote:
>>At 01:39 AM Friday, 1/20/2006, Nigel Horne wrote -=>
>>>I've set up a digest according to the instructions in 3.11
>>>and using the file .../majordomo-1.94.5/Doc/digest.aliases
>>>as a template but:
>>>1) Subscribers who elected to receive in digest form can't
>>>post to the list
>>Is the file of the recipients of the digest listed under restrict_post of
>>the config file?
>I've added that, thanks. I couldn't see that mentioned in the FAQ.
It's in the config file:
# 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
restrict_post = therox therox-digest
>>How are you calling mkdigest?
>echo mkdigest brass-band xxx | mail majordomo
You've told it which digest to make but seem to be missing the recipient.
Were the digests created and put in the proper folder under lists/digest or
however you configured it?
This is one of my digest cron jobs:
echo mkdigest therox-digest therox-digest-outgoing therox.passwd | mail
The passwd is stored in the file "therox.passwd" which is in the same
location as the config file. A copy is left in
Pertinent digest recipient alias:
Randomly Generated Quote (363 of 498):
Knowing ignorance is strength; ignoring knowledge is sickness.
-Lao-Tzu, philosopher (6th century BCE)