Great Circle Associates Majordomo-Users
(March 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: majordomo, sendmail 8.12, and aliases issues
From: Rob Mangiafico <rmang @ lexiconn . com>
Date: Sun, 13 Mar 2005 23:00:11 -0500 (EST)
To: Chip Old <fold @ bcpl . net>
Cc: MAJORDOMO-USERS <majordomo-users @ greatcircle . com>
In-reply-to: <Pine.GSO.4.61.0503132207220.26026@mail>

On Sun, 13 Mar 2005, Chip Old wrote:

> On Sun, 13 Mar 2005 21:38 -0500, Rob Mangiafico wrote to majordomo-users@gr...:
> 
> > We have been running majordomo 1.94.5 successfully for a long time using 
> > sendmail 8.11.x. We recently switched to 8.12.11, and now are having an 
> > issue with alias list expansion.
> >
> > listname: "|/usr/local/majordomo/wrapper resend -l listname listname-out"
> > listname-out: :include:/usr/local/majordomo/lists/listname
> >
> > When an email is sent to the list, sendmail tries to deliver the email to:
> > listname-out@server.name
> >
> > instead of parsing the include list for sending to the subscribers. It
> > seems the MSP/MSA portion with submit.cf is causing the problem. We can
> > work around it by changing the $mailer command in majordomo.cf by adding:
> > -Am -OQueueDirectory=/usr/local/majordomo/queue
> >
> > to force sendmail.cf local delivery and setting a queue that majordomo has
> > write permission on. However, I would think the system should work without
> > having to go this route. Any ideas? Running RHEL 3 with default sendmail
> > configuration, and standard majordomo 1.94.5.
> >
> > If the -Am method is the only way to make it work, are there any drawbacks
> > or problems with using this method?
> 
> Sendmail 8.12.11 is pretty old.  Why not 8.13.3, the current version?  Not 
> that it has anything to do with the problem, but I'm curious.

8.12.11 is what ships with RHEL 3, albeit patched as needed by RH.

> 1) The standard build of submit.cf didn't tell Sendmail in MSA mode to use 
> the trusted-users file, so the MSA didn't recognize the Majordomo user 
> (majordom in our case) as a trusted user.  I had to add this to submit.mc:
> 
> FEATURE(`use_ct_file')dnl

Yes, this has been added.

> 2) The standard build of submit.cf didn't include a define for ALIAS_FILE. 
> That might not matter if you have a single aliases file including 
> Majordomo aliases as well as all your system and user aliases, but it 
> breaks Majordomo if you use a separate file for Majordomo aliases like we 
> do.  I had to add this to submit.mc:
> 
> define(`ALIAS_FILE', 
> ``/etc/mail/aliases,/usr/local/majordomo/majordomo.aliases'')dnl

Yes, /etc/aliases is referenced, and all aliases go in there.

> I seem to remember some permissions issues too, caused by the fact that 
> Sendmail has become progressively stricter about permissions, but I don't 
> remember the details.

All /usr/local/majordomo/lists directories and file are owned by 
majordomo, and none are group or world writable. Still getting delivery to 
the email address instead of the include alias expansion as expected.

Anything else we can check? Or are we limited to -Am and a separate mail 
queue...

Rob



Follow-Ups:
References:
Indexed By Date Previous: Re: majordomo, sendmail 8.12, and aliases issues
From: Chip Old <fold@bcpl.net>
Next: sendmail bounces. Please help. I am so close I can taste it!
From: ebay2@readynote.com
Indexed By Thread Previous: Re: majordomo, sendmail 8.12, and aliases issues
From: Chip Old <fold@bcpl.net>
Next: Re: majordomo, sendmail 8.12, and aliases issues
From: "Pettit, Paul" <ismanager@ccbnpts.com>

Google
 
Search Internet Search www.greatcircle.com