Dear List, Thanks for solving my last problem about migrating user address book across from an old openbsd 3.0 squirrelmail box to my new unit. That stopped a virtual user riot, well, maybe not a riot, but you know...
Currently, we also have a two-thousand-leagues-under-the-sea deep need to deploy some kind of mailing-list functionality to help manage alot of the diverse kinds of work we do. Question: 1. How do I deploy mailing list functionality to my RH-based squirrelmail deployments without breaking my k-rad squirrelmail builds? 2. What app do you recommend I use that is least likely to break my nifty QVCS builds? Mailman? Majordomo? Lyris? Background: Mailman: I've already tried to make a few dev servers and Mailman's required vrsion of Python has alot of weird dependencies that show conflicts with some of what's on the QVCS-based builds... Should a brother just install Yum and set it loose? I want to assure the list server knows when a mail is for a person, or for the list. Mailman's config files mention some techniques, but when asking the list to clarify, not much of a response as i'd hoped... Majordomo: Gonna try that one right now on OpenBSD 3.4 and see if I can't point it at my test QVCS nodes. Any idea what commands to issue to the squirrelmail box that would enable this? ----- Any input would be much appreciated, it will keep qvcs on the table for me as an option to make someone a mail server on the quick... Karl R. Balsmeier ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
