Still having trouble I see. Let's look at your resend alias first, and
compare it to settings in your internetpublishing.config file.
1. -p == precedence = bulk (redundant, .config overrides anyway)
2. -R == purge_received = yes (redundant, .config defaults to no)
3. -l internetpublishing == (this one is required, no special comment)
4. -f == sender = owner-internetpublishing (redundant)
5. -h == resend_host = (useful only if you are doing virtual hosting)
6. -s == administrivia = yes (redundant, default)
7. missing comma between outgoing and archive delivery addresses
7a. I would not put the archive alias on this line anyway, it is better
suited to be put on the same line with your outgoing :include: file.
Speaking of an :include: file, have you considered commenting out your
outgoing alias using bulk_mailer, and reverting to a standard :include:?
If the membership is less than 1000, you may want to consider this, at
least as a test.
If you were getting duplicates "every" time, I would also question your
-owner alias of intlist. Where does intlist expand to?
Your archive alias is interesting that you have chosen a daily archive
with only a 2 digit year in the suffix of the filename.
paul quattro wrote:
> I was wondering if someone could take a look at my aliases file? I still am
> getting duplicates mail to the list.
> # Majordomo list
> owner-internetpublishing: internetpublishing-owner
> internetpublishing: "|/usr/majordomo/bin/wrapper resend -p bulk -R -l
> internetpublishing -f internetpublishing-owner -h listsrv.quark.com -s
> internetpublishing-outgoing internetpublishing-archive"
> internetpublishing-owner: intlist
> internetpublishing-approval: internetpublishing-owner
> internetpublishing-outgoing: |"/usr/local/bin/bulk_mailer
> owner-internetpublishing-outgoing: internetpublishing-owner
> internetpublishing-archive: "|/usr/majordomo/bin/wrapper archive -f
> /usr/majordomo/archives/internetpublishing/internetpublishing -d -a"
> owner-internetpublishing-archive: internetpublishing-owner
> internetpublishing-request: "|/usr/majordomo/bin/wrapper request-answer
> owner-internetpublishing-request: internetpublishing-owner
> Thank you,
> Paul Quattro
> -----Original Message-----
> From: Dan Liston [mailto:email@example.com]
> Sent: Friday, May 19, 2000 8:12 AM
> To: paul quattro
> Cc: 'firstname.lastname@example.org'
> Subject: Re: Duplicate messages with large lists
> There is a slight difference, except the taboo_ settings are more for
> catching a message that loops back through the list. The moderated
> setting is acting as your catcher, but the taboo_ settings become your
> backstop. This is also transparent to the end users, as the filters
> I suggest are headers that are in every majordomo processed message
> anyway. You are just looking for the catch rather than the delivery
> for now.
> Dan Liston
> paul quattro wrote:
> > Thanks Dan,
> > Not doing digests or archives on this list. I decided to moderate the list
> > to stop any resends, because the "Approved: password" line gets yanked
> > before sending. I assume this would do the same thing as the taboo_headers
> > or taboo_body would?
> > Thank you,
> > Paul Quattro
> > -----Original Message-----
> > From: Dan Liston [mailto:email@example.com]
> > Sent: Thursday, May 18, 2000 4:48 PM
> > To: paul quattro
> > Cc: 'firstname.lastname@example.org'
> > Subject: Re: Duplicate messages with large lists
> > Paul,
> > If the list is getting another header/footer, it is going through resend a
> > second time. Possibly a misconfigured digest setting? You might try to
> > add something like this to your list.config and/or list-digest.config;
> > taboo_headers << END
> > /^Sender: owner-listname/
> > /^Precedence: bulk/
> > END
> > where owner-listname is the exact spelling of the sender setting in
> > the listname.config file, and bulk the setting used for precedence from
> > the same .config file. Since these headers are not added until it goes
> > through resend the first time, having them there on a second time through
> > will bounce the message instead of sending it back through the list again.
> > The /^Precedence: bulk/ filter also helps make sure your list is not a
> > subscriber to some other list. Even if it is, you just have to approve
> > the messages before they go into the list for distribution.
> > You could also use a taboo_body setting that has some unique word or
> > phrase from your footer, but this could also catch replies people send
> > where they quote the entire message without trimming the fat.
> > Dan Liston
> > paul quattro wrote:
> > >
> > > Update:
> > >
> > > This occurs when sendmail's queue run "-q1h" happens before the entire
> > list
> > > is sent...
> > >
> > > Well,
> > >
> > > I guess this is only one reason, I have removed the queue all together
> > > still, sometimes, the list gets re-sent, with another header/footer
> > > attached, I'm running Majordome 1.94.3/Sendmail 8.9.3/Linux 2.0.36
> > > 5.2), posting is restricted to my address.
> > >
> > > Thank you,
> > >
> > > Paul Quattro