} We are currently trialing exim on our list server machine. Often
} this generates a single message with a hundred or more recipients.
Oh, small lists :-)
} The way things work at the moment, such messages can take an hour or
} more before the last person in the list gets a delivery attempt.
}
} Is there any way we can get more processes working in parallel on
} such messages?
I would strongly suggest doing this outside the MTA, and splitting
the message prior to it hitting exim. I don't know what list
processor you are using, but several have capabilities of doing just
that!
If you are rolling your own, take the complete address list, sort on
domain (a cheats way of doing this is to sort on reversed domain - in
non optomised perl something like sort({lc(reverse($a)) <=>
lc(reverse($b))} @Addresses) - carve the address list into chunks
(keeping identical domain parts together, and pass the message
multiple times to the mailer, each time with a chunk of addresses.
However it would be nice if exim *could* effectively split up huge
delivery sets into multiple smaller sets, but how this would best be
acheived, and at what point (after routing them all, after directing,
during delivery...?), is a non-trivial task!
Nigel.
}
} On an more trivial point, can the queue text area in eximon give some
} feedback as to whether a message is currently being processed.
}
} Martyn
}
} --
} +--------------------------------------------------------------------+
} | Martyn Hampson | Tel: 0171 594 6973 |
} | Imperial College | Fax: 0171 594 6958 |
} | Computer Centre | E-Mail: M.Hampson@??? |
} | London SW7 2BP, ENGLAND | "Don't just do something, sit there!" |
} +--------------------------------------------------------------------+
}
--
[ Nigel.Metheringham@??? - Unix Applications Engineer ]
[ *Views expressed here are personal and not supported by PLAnet* ]
[ PLAnet Online : The White House Tel : +44 113 251 6012 ]
[ Melbourne Street, Leeds LS2 7PS UK. Fax : +44 113 2345656 ]
