Great Circle Associates Majordomo-Users
(June 2005)
 

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

Subject: Re: newbie question
From: Daniel Liston <dliston @ sonny . org>
Date: Wed, 29 Jun 2005 18:11:40 -0500
To: david besancon <david . besancon @ mgccc . cc . ms . us>
Cc: majordomo-users @ greatcircle . com
In-reply-to: <8BED9CC88F1DCC49AB7A1B48550DD4EE02924F@mgcccmail.mgccc.cc.ms.us>
References: <8BED9CC88F1DCC49AB7A1B48550DD4EE02924F@mgcccmail.mgccc.cc.ms.us>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2

If you have "root" access to the server you are installing on, this
RPM file may be much easier for you to deal with.

ftp://ftp.redhat.com/pub/redhat/linux/updates/6.1/en/powertools/i386/majordomo-1.94.5-2.i386.rpm

I have just installed FC4, and the RPM still works, but with a caveat.
I had to manually edit the /etc/passwd, /etc/shadow, and /etc/group
files, then run `rpm -Uhv majordomo-1.94.5-2.i386.rpm --force` to get
everything installed the way it worked up to redhat 9.

These are the lines I inserted
/etc/passwd...majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash
/etc/shadow...majordomo:!!:12915:0:99999:7:::
/etc/group....majordomo:x:91:mail,dliston,smmsp

I did not have to create any of the directories, the .rpm still does
that for you, and sets the permissions properly, but did complain...

[dliston] 17:48:23 # rpm -Uhv majordomo-1.94.5-2.i386.rpm --force
Preparing...                ########################################### [100%]
groupadd: group majordomo exists
useradd: user majordomo exists
    1:majordomo              ########################################### [100%]

Oddly enough, even as the root user, I could not successfully use the
groupadd or useradd tools from the command line that I am so accustomed to.
Rather than find the cause, I used the work-around of editing files manually.
I am sure this is why the RPM failed as well.

The above will get you into a standardized majordomo installation for
redhat.  It will not solve your misunderstanding of sendmail aliases
however.  The aliases file is for sendmail, not majordomo.  It is the
mechanism to call majordomo from sendmail.  When defining an alias, or
in this case a mailing list, NEVER use HTML URI style addresses.  Real
mail has no idea what HTML is, what it does, or what it means.  Get rid
of all those mailto: and <> entries.

I don't even know where this alias is trying to go;
tech-info-owner: x <mailto:x@y.edu> @ <mailto:x@s> y.edu

VERY poor form!  Only use address@domain.tld formatted addresses.
If you need more than one address per alias, separate them with a comma.
test-owner: my@mydomain.com,you@yourdomain.net,other@theirdomain.org

If you are going to force a "From:" address from the aliases file,
rather than using the listname.config settings, make sure that address
is trusted by sendmail.  That address MUST be in the /etc/mail/trusted-users
file.  While I am on the sendmial topic, I believe smrsh is still enabled
by default in redhat/fedora.  Either disable this in sendmail.cf or add
a symbolic link to /usr/lib/majordom/wrapper to /etc/smrsh/wrapper.

Dan Liston

david besancon wrote:
> Hello All.
>   I am sure that this has been answered several times, but I have searched for about eight hours to no solution.
>  
> I am running Fedora Core 4 with sendmail 8.13.4
>  
> I have created a user called majordomo in the daemon group (with the appended o)
> A view of my directory /home/majordomo:
> drwxr-xr-x  2 majordomo daemon     4096 Jun 28 07:35 bin
> -rwxr-xr-x  1 majordomo daemon     2795 Jun 28 02:04 bounce-remind
> -rwxr-xr-x  1 majordomo daemon    51130 Jun 28 02:04 config_parse.pl
> -rwxr-xr-x  1 majordomo daemon    10671 Jun 28 02:04 config-test
> -rwxr-xr-x  1 majordomo daemon    14201 Jun 28 02:04 digest
> drwxr-x--x  2 majordomo daemon     4096 Jun 28 13:26 lists
> -rw-rw-r--  1 majordomo daemon     5981 Jun 28 10:50 Log
> -rwxr-xr-x  1 majordomo daemon    62511 Jun 28 02:04 majordomo
> -rw-r--r--  1 majordomo daemon     1502 Jun 28 13:25 majordomo.aliases
> -rw-r--r--  1 majordomo daemon    10463 Jun 28 11:12 majordomo.cf
> -rwxr-xr-x  1 majordomo daemon    24381 Jun 28 02:04 majordomo.pl
> -rw-rw----  1 majordomo daemon        6 Jun 28 02:05 .majordomo_registration
> -rwxr-xr-x  1 majordomo daemon      137 Jun 28 02:04 majordomo_version.pl
> drwxr-xr-x  4 majordomo daemon     4096 Jun 28 02:04 man
> -rwxr-xr-x  1 majordomo daemon     3791 Jun 28 02:04 request-answer
> -rwxr-xr-x  1 majordomo daemon    29919 Jun 28 02:04 resend
> -rw-r--r--  1 majordomo daemon    10462 Jun 28 02:04 sample.cf
> -rwxr-xr-x  1 majordomo daemon     8060 Jun 28 02:04 shlock.pl
> drwxr-xr-x  2 majordomo daemon     4096 Jun 28 02:04 Tools
> -rwsr-xr-x  1 root      daemon     7609 Jun 28 02:04 wrapper
> 
>  
> 
> the list that I am trouble shooting is tech-info (/home/majordomo/lists:)
> 
> drwxr-x--x  2 majordomo daemon  4096 Jun 28 13:26 .
> drwxr-x--x  7 majordomo daemon  4096 Jun 28 13:25 ..
> -rw-r-----  1 majordomo daemon   105 Jun 28 10:50 tech-info
> -rw-rw----  1 majordomo daemon 16534 Jun 28 11:30 tech-info.config
> 
> the majordomo alias file (/home/majordomo/majordomo.aliases)
> majordomo:  "|/home/majordomo/majordomo-1.94.5/wrapper majordomo"
> majordomo-owner: x@y.edu <mailto:x@y.edu> 
> owner-majordomo: x@y.edu <mailto:x@y.edu> 
> test:           "|/home/majordomo/wrapper resend -l test test-list"
> test-list:      :include:/home/majordomo/lists/test
> owner-test:     x@y.edu <mailto:x@y.edu> 
> test-owner:     x@y.edu <mailto:x@y.edu> 
> test-request:   x@y.edu <mailto:x@y.edu> 
> owner-tech-info: tech-info-owner
> tech-info: "|/home/majordomo/wrapper resend -p bulk -M 10000 -R -l tech-info -f tech-info-owner -h lists.mgccc.edu -s tech-info-outgoing"
> #tech-info: besancon
> tech-info-owner: x <mailto:x@y.edu> @ <mailto:x@s> y.edu
> tech-info-approval: tech-info-owner
> tech-info-outgoing:
>    :include:/home/majordomo/lists/tech-info
> owner-tech-info-outgoing: tech-info-owner
> tech-info-archive: /home/majordomo/archive/tech-info/tech-info
> owner-tech-info-archive: tech-info-owner
> tech-info-request: "|/home/majordomo/wrapper request-answer tech-info"
> owner-tech-info-request: tech-info-owner
> 
> my tech-info-owner gets the following message when a member trys to send to the tech-info@lists.mgccc.edu:
> 
> Your message did not reach some or all of the intended recipients. 
> 
> 
> 
> Subject:	 test	
> Sent:	 6/28/2005 1:24 PM	
> 
> 
> The following recipient(s) could not be reached: 
> 
>   tech-info-outgoing@lists.mgccc.edu on 6/28/2005 1:24 PM
>   The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.
>   < lists.mgccc.edu #5.3.0 X-Unix; 73> 
> 
>  
> 
> the /var/log/maillog give this error:
> 
> Jun 28 13:33:29 lists sendmail[26988]: j5SIXSeS026988: to="|/home/majordomo/wrapper resend -p bulk -M 10000 -R -l tech-info -f tech-info-owner -h lists.mgccc.edu -s tech-info-outgoing", ctladdr=<tech-info@lists.mgccc.edu <mailto:tech-info@lists.mgccc.edu> > (8/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=30524, dsn=2.0.0, stat=Sent
> Jun 28 13:33:29 lists sendmail[26992]: j5SIXTG3026991: j5SIXTG3026992: clone: owner=tech-info-owner
> Jun 28 13:33:29 lists sendmail[26992]: j5SIXTG3026992: j5SIXTG4026992: DSN: Unable to deliver mail
> 
>  
> 
> I know this is a lot of detail.. Please if you have time or energy, let me know what I might be doing wrong.
> 
> thanks,
> 
> David A. Besancon
> 
>  
> 



References:
Indexed By Date Previous: Problems compiling bulk_mailer
From: Stewart Dean <sdean@bard.edu>
Next:
From: (nil)
Indexed By Thread Previous: Re: newbie question
From: "Peter P. Benac" <ppbenac@emacolet.com>
Next: Problems compiling bulk_mailer
From: Stewart Dean <sdean@bard.edu>