On Tue, Oct 19, 1999 at 04:57:08PM -0400, John R. Levine wrote:
> >Or use serialmail. This limits the concurrency to one and you'll have
> >to trigger serialmail from time to time, but it is easier I think to
> >install serialmail for a few band-aided sites than to have qmail
> >installations multiplying.
>
> Actually, you can run multiple instances of serialmail out of the same
> maildir, so if you want up to four deliveries, do something like this
> in your trigger script
If I remember right, only one instance of maildirsmtp was supposed to
run on one Maildir at any one time, otherwise there could be
duplications. However, when I checked out the manpages of the current
serialmail (0.75), there is no such limitation mentioned. Let me do a
test...
I attempted delivery of 3 messages out of a maildir to a host, using 3
simultaneous instances of maildirsmtp running in the background, and each
message was delivered thrice. Additionally, the second and third
instances of maildirserial complained that they could not unlink
messages so and so, and that it would be delivered twice (this is
misleading, because the message file has indeed been unlinked, by
another maildirserial).
In the past, I have solved such a problem of a slow host, by first
collecting their email in 'n' maildirs (where n is the concurrency I
want), and then running one copy of maildirsmtp on each maildir.
DJB: Why did you remove that warning about simultaneous use of
maildirserial on a Maildir? The problem still exists.
--
See complete headers for more info
