Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Large lists
From:
[log in to unmask]
Reply To:
LISTSERV give-and-take forum <[log in to unmask]>
Date:
Mon, 30 Jun 1997 14:24:49 -0400
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2131 bytes) , application/pgp-signature (291 bytes)
On Mon, 30 Jun 1997 13:04:16 +1000, you said:
> Why isn't this available for UNIX??? :( My list would send about 200-300 X
> 1,500-2,000 = 300,000-600,000 messages per day if I could run it to full
> boost (which I cannot unfortunately cause sendmail can't handle the load
> and it just queues and queues...)

Umm.. unless you're running on a *very* small 486-based system running
Linux with insufficient memory, sendmail *can* handle that load.

For a long time, Listserv.vt.edu was an rs6000-250 (66mz PowerPC 601)
with 192M of memory.  With just a few tweaks, it was handling well into
the 400K RCPT TO: range per day with a load average of under 2.

Things you need to do:

1) put 'feature(nocanonify)' in your sendmail.mc file
2) Run multiple queues.  The sendmail distrib has a Perl script to do it,
look at 'contrib/re-queue.pl'.  Here's how we configure it in the root crontab:

#
# re-mqueue and sendmail
#
# Run the just-submitted queue every 15 mins
5,20,35,50 * * * * /usr/lib/sendmail -q 1>/dev/null 2>/dev/null
# if it isn't delivered in an hour, move to mqueue2 and try once every hour
10 * * * * /usr/local/bin/re-mqueue /var/spool/mqueue /var/spool/mqueue2 3600
22 * * * * /usr/lib/sendmail -oQ/var/spool/mqueue2 -q 1>/dev/null 2>/dev/null
# if it isn't delivered in a day, move to mqueue4 and try every 4 hours
15 * * * * /usr/local/bin/re-mqueue /var/spool/mqueue2 /var/spool/mqueue4 86400
19 * * * * /usr/lib/sendmail -oQ/var/spool/mqueue4 -q 1>/dev/null 2>/dev/null
27 * * * * /usr/lib/sendmail -oQ/var/spool/mqueue3 -q 1>/dev/null 2>/dev/null
# Once a day, dump stuff over 5 days old into mqueue5 and give it one more chance
27 2 * * * /usr/local/bin/re-mqueue /var/spool/mqueue4 /var/spool/mqueue5 432000
35 2 * * * /usr/lib/sendmail -oQ/var/spool/mqueue5 -q 1>/dev/null 2>/dev/null
# Clean up the shared files once a day, keep inode count down
* 2 * * * /usr/sbin/purgestat

As always, your mileage may vary.. but this worked fine for us even on a VERY
small machine by today's standards.

--
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech




ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV