Re: majordomo, sendmail 8.12, and aliases issues

On Mon, 14 Mar 2005, Pettit, Paul wrote:

> > > > 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:
> > > > [email protected]
> > > >
> 
> I'm running much the same setup (sendmail 8.12.8-9.80, majordomo 1.94.5)
> but I've not seen this behavor.
> 
> > > > 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
> > > >
> 
> What is in your submit.mc? 

divert(0)dnl
include(`/usr/share/sendmail-cf/m4/cf.m4')
VERSIONID(`linux setup for Red Hat Linux')dnl
define(`confCF_VERSION', `Submit')dnl
define(`ALIAS_FILE', `/etc/aliases')dnl
define(`__OSTYPE__',`')dnl dirty hack to keep proto.m4 from complaining
define(`_USE_DECNET_SYNTAX_', `1')dnl support DECnet
define(`confTIME_ZONE', `USE_TZ')dnl
define(`confDONT_INIT_GROUPS', `True')dnl
define(`confPID_FILE', `/var/run/sm-client.pid')dnl
dnl define(`confDIRECT_SUBMISSION_MODIFIERS',`C')
FEATURE(`use_ct_file')dnl
dnl
dnl If you use IPv6 only, change [127.0.0.1] to [IPv6:::1]
FEATURE(`msp', `[127.0.0.1]')dnl

> > > > 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.
> > > >
> 
> That might be the problem, I seem to remember that the default
> sendmail.mc used to make the sendmail.cf when I first set the box up
> that has majordomo on it was less than optimal. What is in your
> sendmail.mc? Do you have the 8.11 sendmail.mc that was used to make the
> previous sendmail.cf to compare?

Current sendmail.mc:
---
divert(-1)dnl
include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
VERSIONID(`setup for Red Hat Linux')dnl
OSTYPE(`linux')dnl
define(`confDEF_USER_ID',``8:12'')dnl
define(`confTO_CONNECT', `1m')dnl
define(`confTRY_NULL_MX_LIST',true)dnl
define(`confDONT_PROBE_INTERFACES',true)dnl
define(`PROCMAIL_MAILER_PATH',`/usr/bin/procmail')dnl
define(`ALIAS_FILE', `/etc/aliases')dnl
define(`STATUS_FILE', `/var/log/mail/statistics')dnl
define(`UUCP_MAILER_MAX', `2000000')dnl
define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl
define(`confAUTH_OPTIONS', `A')dnl
TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN 
PLAIN')dnl
define(`confTO_IDENT', `0')dnl
FEATURE(`no_default_msa',`dnl')dnl
FEATURE(`smrsh',`/usr/sbin/smrsh')dnl
FEATURE(`mailertable',`hash -o /etc/mail/mailertable.db')dnl
FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable.db')dnl
FEATURE(redirect)dnl
FEATURE(always_add_domain)dnl
FEATURE(use_cw_file)dnl
FEATURE(use_ct_file)dnl
FEATURE(local_procmail,`',`procmail -t -Y -a $h -d $u')dnl
FEATURE(`access_db',`hash -T<TMPF> -o /etc/mail/access.db')dnl
FEATURE(`blacklist_recipients')dnl
EXPOSED_USER(`root')dnl
DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl
FEATURE(`accept_unresolvable_domains')dnl
LOCAL_DOMAIN(`localhost.localdomain')dnl
MAILER(smtp)dnl
MAILER(procmail)dnl
---

Unforutnately, the old sendmail.cf on 8.11.x was manually generated a long 
time ago, so no .mc file to fall back on.

> > > > If the -Am method is the only way to make it work, are 
> > there any drawbacks
> > > > or problems with using this method?
> > > 
> 
> Not sure, I've never used that.

Just forces LDA to process all majordomo, no hand off to MSP/MSA. Less 
than optimal, as we have to run a separate queuerunner as well. My 
understanding on this is shaky at best.  ;)

> > Anything else we can check? Or are we limited to -Am and a 
> > separate mail 
> > queue...
> > 
> > Rob
> > 
> 
> If your using 8.12 is smrsh configured? If so did you replace the
> wrapper link in /etc/smrsh to point it to the majodomo wrapper? Not sure
> that would cause the odd mailing, it's been a long time since I had to
> set up majordomo. :)

smrsh is configured and working properly. Subscribe/unsub requests work 
well, config changes via email, etc... It's just sending to a list with 
double alias expansion that is the problem.

I really appreciate the help, and hope to get this solved soon.  :)

Rob