Frank Bax wrote:
> Yesterday Joseph stated:
>
>>Sendmail can handle multiple queue runners with no duplication.
>>That's why it makes lock files. Run the queue by hand with
>>'sendmail -q -v' and watch it skip the messages that are locked.
>>
File locking is a setting in sendmail, and is dependant upon the capabilities of
the operating system. Factors such as your OS version, filesystem of the mail
queue, and compile time options in sendmail can change how locking works. (NFS
mail queue's are bad).
This is why some people will experience a problem and others won't. In my case,
we compiled sendmail by hand, rather than using an older Debian package. I am
still trying to determine how locking behaves on *my* system, as I wasn't the
one who compiled the version of sendmail we are running.
This is a sendmail issue, as Majordomo's resend wrapper sends the message on to
the actual list alias, which is typically :
foo: "|/usr/lib/majordomo/wrapper resend -l foo foo-list"
foo-list: :include:/var/lib/majordomo/lists/foo
The :include: directive is a part of sendmail, so what happens after the message
goes through the majordomo wrapper is up to sendmail.
>
> If these statements are true, it would imply that while the message is
> locked, another process can't send it. If it gets unlocked without being
> deleted, then delivery must have failed, so it's ok for another process to
> try it. Therefore, no problem; unless two COPIES of the message end up in
> the queue.
>
> Is there a way to test this on a small scale?
>
> Frank
I would say send a message to a small test list with an address on it that will
take time to bounce (like to a system that uses a dialup connection and ETRN to
get mail). That way the message will sit in the queue for a while.
Then run sendmail -q -v as suggested by joseph, and see if your list message is
indeed locked. If it is, you won't need to worry about duplicates, because your
locks are working.
>
> At 03:27 AM 6/20/01 -0500, Daniel Liston wrote:
>
>>This is not a bug, but a setting, in sendmail. Some people want their queue
>>directory emptied more often than others. When the queue gets too large to
>>empty within the specified setting, you get multiples of the same message.
>>
>>If your server take several hours to deliver to a few thousand addresses,
>>please take the time to sort your list by domain so sendmail can send many
>>messages with a single connection to each domain, rather than sending a
>>single message during each of multiple connections to the same domain.
>>
>>Bulk_mailer does some of this sorting for you, and can restrict the number
>>of addresses per message.
>>
>>Dan Liston
>>
>>Frank Bax wrote:
>>
>>>As a newbie to sendmail/majordomo, I wonder: is this a bug in sendmail? Or
>>>there a good reason why sendmail would start another delivery queue? I
>>>recently setup Majordomo specifically to handle a list of about 4,000
>>>entries which was taking many hours to deliver directly from Outlook
>>>Express client. We were about to test it with the 'live' subscriber list
>>>when I caught this thread.
>>>
References:
|
|
