[cobalt-users] Qube 2 & majordomo

[Jerry Ellis <jellis@xxxxxxx>]

I have been doing tech support for dial-up users for an ISP for 2 1/2 
years. I just wanted to state right away that my brain has turned to mush 
and I must apologize if I don't make any sense. :)

Background:

My customer has a Qube 2, Cobalt OS Release 4.0, Qube2-All-Security Release 
3.0.1-6453, Qube2-en-OSUpdate Release 3.0

I am trying to hack majordomo and discovered that if I use a 
list_name.config file I can make majordomo behave in a desired way. I've 
also discovered that config_parse.pl will trash the list_name.config file 
if one makes any changes to the list with the web interface. Fine, we won't 
use the web interface for list administration.

The problem:

That being said, if I send an email to majordomo from a user (Qube or not) 
with the request subscribe list_name, the user gets a reply from majordomo 
telling him that the request has been sent to the list owner for approval. 
However, the list owner (admin) never gets the email from majordomo asking 
for approval. I can send an approval from any account and subscribe or 
unsubscribe a user and the change gets made. The subscriber even gets the 
welcome message from majordomo. But for some reason majordomo will not send 
mail to the admin account..

I've searched the majordomo.cf and sendmail files looking for something 
that would send the responses elsewhere including aliases but everything 
points to the admin. I can send mail to and from the admin account so I'm 
thinking it is okay.

I've search the majordomo FAQs, the Cobalt Knowledge Base, the this mailing 
list's archives but can't find anything. I know very little about majordomo 
and Linux and I'm hoping someone will take pity on me and point me in the 
right direction. :)

Jerry

Jerry Ellis
Tech Support
Cumberland Internet
www.rr1.net

Mountain Dew and doughnuts... because breakfast is the most important meal 
of the day!