On Sunday, June 3, 2001, at 07:44 AM, Jay R. Ashworth wrote:
Good question -- I don't use mailman for this, all of my broadcast work is with a custom front-end, and it usually talks to bulk_mailer on the back end, and I build the rate limiting into a custom version of bulk_mailer.
Um... should I know about that, instead? I'm not married to mailman for this...
Not necessarily. Bulk_mailer is a tool written for majordomo installations that splits up deliveries into small batches. postfix can do this using the default_destination_concurrency_limit option, so if you're using postfix, you don't really need it. Once I finish migration, I'll rewrite my sending tools to take advantage of that isntead of using bulk_mailer, and phase it out (bulk_mailer also does some other stuff, like set up some headers, but my custom tools can easily do that as well)
my front ends are just custom perl scripts that take pieces of content and address lists and puts it together. Nothing fancy (and not distributable), and all really stop-gap stuff while I write a real publishing tool for this stuff, which is the project I'm designing now (we want to be able to send out fully-customized e-mail using a template system with volume up to about 500K an hour, with full versioning control of the content and automatic access of the user data from the corporate database. A fun summer project)
I have to keep reminding people in my company that want to borrow my tools that the tolls I'm currently using are very stupid; it's the person hacking them that is doing most of the work. Once I finish this new mail publishing system, the tools will be smart, but since it's designed for corporate use, they won't need to borrow the tools, just have an account on them...
-- Chuq Von Rospach, Internet Gnome <http://www.chuqui.com> [<chuqui@plaidworks.com> = <me@chuqui.com> = <chuq@apple.com>] Yes, yes, I've finally finished my home page. Lucky you.
Any connection between your reality and mine is purely coincidental.