* Rick Updegrove <[EMAIL PROTECTED]> writes:
> "Robin S. Socha" <[EMAIL PROTECTED]>
>> OK, so qmailadmin does not grok "&[EMAIL PROTECTED]" .qmail files as I just
>> found out. Thank God for Perl...
>> Anyway, this remains unsolved:
[ML paths]
> permissions?
Nope. The lists actually have to reside in the top level directory. That
sucks. I know it's rude to criticise free software in this fashion without
offering patches, but I'm not in a position to do that. Sorry. :-(
> note: I have been using qmailadmin since .38 and the mailing list
> features have never quite worked right according to the qmailadmin
> interface.
Well, things work OK now that I've recreated the lists in the top level
dir and piped ezmlm-list to ezmlm-sub for the old/new lists. Honestly, I
couldn't care less if $NEW_ADMIN were to run this forever, but I'm not
really looking forward to working with a directory containting 500+
lists and about that many users soon. Maybe I'm intellectually
challenged, old, and boring, but I *DO* want my lists in a list
dir. Dammit. ;-)
Otherwise, qmailadmin works really, really well. Great piece of software.
--
Robin S. Socha <http://socha.net/>
"The new glue is, unfortunately, ignored by recent versions of the BIND
cache; the detailed technical explanation for this is that the BIND
company is a bunch of idiots." (DJB)
