>>>>> "RS" == Randy Saxton <email@example.com> writes:
RS> Hoping that this is the correct list to ask this question
Well, sort of. We went through this on the majordomo-users list but it
didn't turn out to be Majordomo-specific.
RS> Now the customer says that when he approves a subscription for the
RS> list-digest, the user is sent copies of *all* previous digests!
OK, here's the common denominator we found: Smail. All affected systems
were Linux machines running Smail. Linux only seemed to factor in because
Slackware seems to come with Smail as the default.
When sending mail to a list, Smail keeps a list of addresses that it's
already sent to. If one of the addresses has delivery problems, the
message will stick around in the queue. When Smail runs the queue, it
checks toe list of delivered addresses against the address list and tries
to deliver to any addresses the message hasn't made it to yet. This
includes new addresses added since the message was queued. (Note that I
don't use Smail and am repeating this from the conclusions of others.)
Is your client running Smail?
One solution is to switch to sendmail. Another is to use something like
TLB [*] (or bulk_mailer with the number of addresses per batch set really
high) to turn the address into a single SMTP transaction, disabling this
[*] TLB is a package I've written which is used to enhance mailing list
delivery performance. It's not finished yet, but works fine for those who
are currently using it. It's in ftp.hpc.uh.edu:/pub/tlb.
Jason L. Tibbitts III - firstname.lastname@example.org - 713/743-8684 - 221SR1
System Manager: University of Houston High Performance Computing Center
1994 PC800 "Kuroneko" DoD# 1723