In article Pine.LNX.4.33.0112042111570.20046-100000@boink.hartzler.home, Peter Hartzler pete@hartzler.net writes:
Paul --
After a brief grep of the manual, and the sources and rc.init, I suspect you might get some joy out of playing with choplist's run-time parameters (supplied on the command line); overriding it's default values... These are:
minnames = 32 # minimum number of names per call mindiffnames = 8 # minimum for maxnames-minnames maxnames = 64 # maximum number of names per call maxsplits = 0 # maximum number of parts to split dist in maxsize = 200000 # maximal disk space to be taken up per mail maxconcur = 4 # maximum number of concurrent sendmail calls
Perhaps lowering maxnames would help?
We had the same problem with some extremely large announcement lists here. The solution was to reduce the `maxnames' parameter *and* to set `maxsize' to 0. Reducing `maxnames' means increasing the number of batches that are sent; increasing the number of batches means increasing the total amount of disk space consumed in the spool. If `maxsize' is left at 200000, then choplist would attempt to satisfy it by increasing the number of recipients per batch, even beyond the number specified in `maxnames'.
Leaving `maxsplits' and `maxsize' at 0 forces choplist to consider only the `maxnames' parameter in deciding how to split up into batches.