[cobalt-users] Re: Broken Majordomo

[Clayton McGow <mrwilder@xxxxxxxxxxx>]

> Hi all,
> 
> I apparently broke majordomo when I was changing one of the
> lists' configuration files... I forgot to set the
> permissions.
> 
> I've set the permissions correctly now, but I can no longer
> send an email to majordomo@xxxxxxxxxxx without getting an
> "invalid recipient" email, nor can I send any commands to
> any of the lists, like "subscribe" or whatnot without
> getting a:
Regarding the information at the bottom of the page, I'm
wondering if its possible that the raq2 is not  reading the
aliases.majordomo file at all, since I can't write to
majordomo@xxxxxxxxxxxx

Also, there is no job called majordomo in ps aux...  on the
other hand, even if I manually start majordomo with
"./wrapper majordomo" nothing goes through.

Any ideas?


>        
> "BOUNCE example-list_site1@xxxxxxxxxxx: Admin request:
> /^subject:\s*help\b/i Admin request of type /^\s*help\s*$/i
> at line 1"
> 
> and for that matter, even the  BOUNCE notification doesn't
> make it back to me because:
> "   ----- The following addresses had permanent fatal errors
> -----
> owner-example-list_site1@xxxxxxxxxxx
> 
>    ----- Transcript of session follows -----
> 550 owner-example-list_site1@xxxxxxxxxxxxxx User unknown"
> 
> I tried to restart majordomo by typing "./majordomo&" but it
> seems to be looking for its dependencies in a new place, for
> example it tries to find "majordomo_version.pl" in the perl
> library, which I'm sure is where it ought to be but
> majordomo ran quite nicely for 2 years with
> majordomo_version.pl in the same directory as itself. Same
> goes for majordomo.cf, which it now is expecting to find in
> /etc/majordomo.cf... although it ran for a long time with
> majordomo.cf in /usr/local/majordomo.
> 
> The last thing in the log file is from when I forgot to set
> the read permission on the changed config file:
> Nov 07 14:22:27 atoznet.com resend[3379] {site_admin_site1}
> ABORT Can't open
> /usr/local/majordomo/lists/site_admin_site1.config
> 
> OK... I'm stumped. Does anybody know how I fix this? 
> 

-- 
Clayton McGow
mrwilder@xxxxxxxxxxx