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: Chip Old <fold @ bcpl . net>
Date: Sun, 13 Mar 2005 22:43:55 -0500 (EST)
To: MAJORDOMO-USERS <majordomo-users @ greatcircle . com>
In-reply-to: <Pine.LNX.4.44.0503132131010.14934-100000@lexiconn.serverhost.net>
References: <Pine.LNX.4.44.0503132131010.14934-100000@lexiconn.serverhost.net>

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.

We switched from 8.11.x to 8.12.x so long ago I don't remember all the 
details, but I do remember that there were two submit.cf issues related to 
Majordomo:

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

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

Of course in the actual submit.mc that is all one line.  After adding 
those two lines to submit.mc, do "./Build submit.cf" to get a new 
submit.cf.

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.

-- 
Chip Old (Francis E. Old)             E-Mail:  fold@bcpl.net
BCPL Network Administrator            Phone:   410-887-6180
BCPL.NET Internet Services Manager    FAX:     410-887-2091
320 York Road
Towson, MD 21204-5179  USA


Follow-Ups:
References:
Indexed By Date Previous: majordomo, sendmail 8.12, and aliases issues
From: Rob Mangiafico <rmang@lexiconn.com>
Next: Re: majordomo, sendmail 8.12, and aliases issues
From: Rob Mangiafico <rmang@lexiconn.com>
Indexed By Thread Previous: majordomo, sendmail 8.12, and aliases issues
From: Rob Mangiafico <rmang@lexiconn.com>
Next: Re: majordomo, sendmail 8.12, and aliases issues
From: Rob Mangiafico <rmang@lexiconn.com>

Google
 
Search Internet Search www.greatcircle.com