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.
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
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.
>>
>> Frank
>>
>> At 03:38 AM 6/15/01 -0500, you wrote:
>> >The most common reason for this is that your sendmail is starting to run
>> another
>> >delivery queue before the first one is completed. You could speed this up
>> by
>> >keeping your "large" list sorted by domain, and using bulk_mailer.
>> Bulk_mailer
>> >would probably be most beneficial.
>> >
>> >Your other choice is to extend the time between sendmail queue runs. By
>> default
>> >(in RedHat anyway) sendmail tries to deliver the queue every 30 minutes.
>> If you
>> >have a very beefy server, and high bandwidth connection to the
internet, you
>> >might be able to deliver 18k messages (depending on how big they are too)
>> in an
>> >hour. If you are able to deliver 6k messages in an hour, you would still
>> need
>> >three hours to deliver all the mail.
>> >
>> >You should consider a combination of bulk_mailer and extending the
>> sendmail time
>> >between queue runs.
>> >
>> >Dan Liston
>> >
>> >Kirk Ismay wrote:
>> >>
>> >> I've recently set up a new mailing list for announcements to customers,
>> with
>> >> about 18,000 addresses on it. The addresses were collected legitimately
>> (we are
>> >> not spamming).
>> >>
>> >> This is the first list I've set up with that many addresses (our next
>> biggest
>> >> list has 9,000 on it), and the problem is that a message sent to the
>> list has
>> >> resulted in the same message being sent to recipients several times (up
>> to 10
>> >> duplicates have been reported).
>> >>
>> >> Some customers were understandably upset.
>> >>
>> >> We're using Majordomo version 1.94.5 & sendmail 8.11.3 on a Debian Linux
>> server.
>> >>
>> >> Can anyone give me advice on preventing this problem? Would Keith
Moore's
>> >> bulk_mailer software fix the problem?
>> >
>> >
>
Follow-Ups:
References:
|
|
