I want to send daily several different subscription mails with randomly
generated content (ie a quote of the day type list). So if I have the text
files with the varying content all made up with perl scripts. Then I have 10
different text files with batches of addresses. So anyone on the main list
can get any of the random daily mails.
Let me rephrase it:
Is it possible to use Majordomo to send out 'batches' of mails? For example
I have several versions of the daily mail and I have them broken up into a
few different files consisting of headers, footers and text body. I also
have a few txt files of email addresses to combine into a randomly generated
Black Samba Design Services
BLACK SAMBA IS NOW!
> -----Original Message-----
> From: majordomo-users-owner@GreatCircle.COM
> [mailto:majordomo-users-owner@GreatCircle.COM]On Behalf Of Rick Green
> Sent: Tuesday, April 27, 1999 10:08 PM
> To: Brian Sullivan
> Cc: majordomo-users@GreatCircle.COM
> Subject: Re: Config and general questions from a struggling new user
> On Tue, 27 Apr 1999, Brian Sullivan wrote:
> > I have been trying to set up a mailing list using majordomo and
> have most of the
> > parameters under control ( I think).
> By this, I take it to mean that you've got a working test list. Do your
> working lists use 'resend', or are they simple distribution aliases?
> > Things I can't seem to get a handle on:
> > 1) digests -- my understanding is that this is handled by
> setting up some sort of
> > parallel mailing list that by magic gets messages from the real
> list sent it --
> > can anybody elaborate or provide concrete config file examples
> ( I am Unix
> > impaired so be gentle please)
> Digests are not defined in the .config files. The 'digest-' variables
> there were intended for future use, and most are not implemented. Read
> the comments carefully. The digest is actually a separate list, with it's
> own .config file. They are linked by the entries in the aliases file, per
> the third example set of aliases given in the NEWLIST document.
> > 2) I would like to have subscribers that can post ( my mailing list
> > will be subscriber sending only) but do not receive mail -- I would
> > like this function to be subscriber controlled - is this possible?
> This was recently covered in an extensive thread. Basically, set up
> another list, with a <listname1>.config, and a <listname1> file, but do
> not define a <listname1> alias, or it's kin (mebbe a <listname1>-request,
> if your users tend to that style). Instead, declare the <listname1> file
> in the restrict_post variable of the <listname>.config, along with
> <listname> itself. Thus, anyone may subscribe to <listname1>, which gives
> them posting rights to <listname>, but will not deliver any mail to them.
> Rick Green
> Microsoft has just announced it is renaming Windows NT version 5 to
> "Windows 2000."
> Is that the ultimate millennium bug or what?