Index: [Article Count Order] [Thread]

Date:  Thu, 26 Oct 2006 16:37:45 -0400
From:  Thom LaCosta <tlchost (at mark) tlchost.net>
Subject:  [coba-e:07734] Re: Majordomo confirmed bugs
To:  coba-e (at mark) bluequartz.org
Message-Id:  <7.0.1.0.2.20061026163537.03f210b0 (at mark) tlchost.net>
In-Reply-To:  <454110E3.8030403 (at mark) dogsbody.org>
References:  <200610261228.k9QCSplZ005292 (at mark) srv1.nickelnetworks.com> <Pine.LNX.4.56.0610260853270.21391 (at mark) ns1.tlchost.net> <6.1.2.0.0.20061026110756.04b7e430 (at mark) mail.officetracker.com> <454110E3.8030403 (at mark) dogsbody.org>
X-Mail-Count: 07734

At 03:47 PM 10/26/2006, you wrote:

>>Is it time to get Mailman working with BQ? I for one have used 
>>Majordomo for about 5 years and would love to have the features of mailman.
>
>Yes please!! I can't help with developing it but can definitely help 
>with beta testing if it's of any help.  I quite like Majordomo as an 
>program but I can't help but think that we are flogging a dead 
>horse.  Mailman does so much of this out of the box and already has 
>a GUI that can probably be utilised directly.

The main reason I have not moved to BQ is the terrible majordomo 
implimentation.  I can get my customers to accept mailman...but I 
will simply loose business and have to turn off all myt own lists if 
I move to BQ.

I hope someone can solve the problem.

Thom 
	

7734_2.html (attatchment)(tag is disabled)