Phil,

I had the same issue with the absolute paths with my webhosting company (IX Webhosting) They don't impose any limits on outbound email at all once you tell them what you are doing, and only moderate limits until then My biggest list has over 170 subscribers (it's for a home owners association) Their service includes ezmlm, but they've got just about all the features disabled, leaving only the basic stuff, so Dada Mail has been a godsend I run my dada_bridge cron job every 10 minutes, no problem I highly recommend this hosting company I don't think there's a better deal on the Internet Their tech support is outstanding, and I believe they have shared server plans as low as around $75/year It's an amazing deal (http://ixwebhosting com) Not trying to plug this host, I just have been very pleased with the overall value

Cheers, Bruce

Bruce Scherzinger * bruce@joomlander net

Phil McKerracher wrote:

I'm trying out www servage net as a webhost, and found that their mailing list feature doesn't support discussion lists, so I'm trying Dada Mail It seems to do what I want (it's unusual to find an open-source app that's so bug-free and well documented, fantastic!) but there are a few unusual features with this host:

1. Servage use 'clustered' hosting and there's no SSH access, which can make debugging a little difficult I've seen occasional 500 errors using Dada Mail, but pages always refresh successfully I haven't seen the errors since configuring absolute paths in mail cgi, but that may be coincidence

2. CRON jobs can't be more frequent than one per hour, and to achieve that you have to manually set up 24 'daily' jobs at hourly intervals, which is a bit of a pain

3. The sending limit is 100 messages per minute, which is unusually generous Anything legal is allowed (including, unusually, 'adult' messages) Their supplied announce-only mailing lists seem to run much slower than this, so Dada Mail is a good alternative for them as well

4. Batch sending stops after the first batch (sleep() not allowed?) if the sending window isn't open Leaving the window open isn't really practical for discussion lists, so here's an improvement request: could auto_pickup be incorporated into dada_bridge? It's not a big problem though, because discussion lists tend to have less than 100 members anyway

5. Servage don't seem to support HTML::Scrubber, so archiving discussion list messages would be a security risk (I didn't want to archive them, so I haven't persued this )

I do have one other improvement suggestion: Could a link to the complete documentation (local or remote) be added prominently to all the admin pages somewhere? I keep forgetting where it is