I’ve read several kBase entries on mailing lists at DH, and it seems I may be able to do much of what I’d like to, but not all…
I’d like to build a branded front-end for the/a mailing list management interface, which I can install on my web clients’ sites. My main reason for this is to allow the use of confirmed opt-in, which I’m now requiring of all new clients, and to which I’ll be upgrading all existing ones.
From what I can tell, I can do these:
Create an opt-in confirmation system by creating a layer in front of the DH CGIs that control list subscriptions. This uses Procmail and Perl (I’m already almost done with this feature).
Allow the client to edit Confirmation and Welcome messages (via the above layer)
Allow the client to create a special “List Help” address via a regular autoresponder
Allow the client to sub and unsub users via the DH CGIs (add_list.cgi, etc?).
But can I allow my client to do the following without forcing them to use the DH CP?
Create or delete mailing lists
View and edit a list of subscribers, as in the DH CP
I’d rather not have to create and delete lists on behalf of the client, and the DH CP would be totally bewildering to most of the folks I design for (besides the fact that I’d rather not allow them an admin password).
Second subject… I’ve never used MySQL, so I’m wondering what would be better for very small sites, with mailing lists of only 200 subscribers or so-- Flat files and a SendMail interface, DH mailing lists, or some sort of MySQL API?
One major wrinkle is that I’d like to be able to integrate email list info with postal list info and other “user preferences”, and it seems that using the DH mailing list facility might make that a little more complicated than it could otherwise be.
Thanks for all experience anyone might be able to shed!