I tried everything !! The permissions were as they should be.
I entered majord in the trusted-users file, also in sendmail.cf
submit.cf and main.cf below TrustedUsers. The command to check
permissions worked fine and gave only "ok" back.
As I get back mails from majord which I send using info commands (lists,
who) I don't think it is a env problem.
But what the hell can it be then?
Here the complete error-msg:
Your message did not reach some or all of the intended recipients.
Subject: test newsletter
Sent: 05.03.2003 09:36
The following recipient(s) could not be reached:
listname-list@host.domain.com on 05.03.2003 09:34
Unable to expand a distribution list to deliver the message
to its members. Try again or contact your system administrator.
< host.domain.com #5.2.4>
Any help is apreciated a lot. Thanks to all who replied and will reply
helping me out.
Maurizio
-----Original Message-----
From: Gary Thandi [mailto:Gary.Thandi@360.net]
Sent: Tuesday, March 04, 2003 11:42 PM
To: 'Daniel Liston'; Cencigh, Maurizio {PGID~Kaiseraugst}
Cc: majordomo-users
Subject: RE: Error Msg sending newsletter
You can specify that majordomo is a trusted-user in one of two ways. 1.
Add the user name to your trusted-users file, make sure sendmail.cf has
the following line uncommented.
Ft/etc/mail/trusted-users
2. Add the entry "Tmajordomo" to sendmail.cf (Don't forget to stop and
start
sendmail)
Troot
Tmajordomo
- Permissions (if you are using smmsp)
Permissions Owner Group File/Directory
-rwxr-sr-x root smmsp /usr/lib/sendmail
drwxr-x--- root staff /var/spool/mqueue
drwxrwx--- smmsp smmsp /var/spool/clientmqueue
-rw-r--r-- root other /etc/mail/sendmail.cf
- Other mail file permissions
chmod go-w / /etc /etc/mail /usr /var /var/spool
/var/spool/mqueue
chown root / /etc /etc/mail /usr /var /var/spool
/var/spool/mqueue
- This command is kind of cool to report back permissions stuff
/usr/lib/sendmail -bi -d44.4
Keep in mind that my config is 8.12.6.
Gary.
-----Original Message-----
From: Daniel Liston [mailto:dliston@sonny.org]
Sent: Tuesday, March 04, 2003 11:00 AM
To: Cencigh, Maurizio {PGID~Kaiseraugst}
Cc: majordomo-users
Subject: Re: Error Msg sending newsletter
I am not certain if this is the same for solaris or linux using the same
version of sendmail 8.11.6, but the "trusted" majord user has to be
added to the submit.cf file as well as the sendmail.cf.
Dan Liston
Cencigh, Maurizio {PGID~Kaiseraugst} wrote:
> I don't think the problem concers uid and gid. I installed a fresh
> version of majordomo on the new machine. Compiling the wrapper and
> everything on the new machine with the uid and gid I gave. The ONLY
> thing I copied from the old machine is the content of the lists
> directory and then chown the listname, listname.conf, listname.poster.
>
> I tried the sendmail commands. When I run as root:
> sendmail -bv listname, gives as output the entry after listname of the
> aliases file. sendmail -bv listname-outgoing, tells me user unknown.
> I think this may be the problem.
>
> as the majord user I get:
> sendmail -bv listname, tells about misleading output for
> non-privileged user and says can not chdir (/var/spool/mqueue):
> Permission denied. Program mode requires special privilege, eg. root
> or TrustedUser. I tried to change the TrustedUser in sendmail.cf, and
> set it to majord and restarted sendmail. Same error msg. as usual.
> sendmail -bv listname-outgoing, gives the same.
>
> Can you tell me more about? I think or the user unknown is the problem
> or non-privilege thing on /var/spool/mqueue. What permissions are
> needed on /var/spool/mqueue. Or which TrustedUser should I configure
> in sendmail.cf?
>
> Thanks a lot.
> I feel getting near to the solution...
>
>
> -----Original Message-----
> From: Daniel Liston [mailto:dliston@sonny.org]
> Sent: Monday, March 03, 2003 8:51 PM
> To: Cencigh, Maurizio {PGID~Kaiseraugst}
> Cc: majordomo-users
> Subject: Re: Error Msg sending newsletter
>
>
> Please do these comparisons to validate uid:gid are the same between
> the old and the new systems. On each machine, run as root;
>
> grep majordom /etc/passwd
>
> majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash
> majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false
> majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash
>
> As you can see, I have three machines running majordomo, but none of
> them have the same uid or gid. For that matter, none of them even
> have the same home directory. There is no way I could just copy these
> instances between machines, I would have to recompile the wrapper for
> each system, not to mention chown'ing files and directories.
>
> Your majordomo address/alias is working, or you would not get replies
> to the lists and who commands. Have you tried using sendmail to
> verify your list or list-outgoing addresses?
>
> sendmail -bv listname
> sendmail -bv listname-outgoing
>
> Try these commands as both the root and the majordomo user.
>
> Dan Liston
>
> Cencigh, Maurizio {PGID~Kaiseraugst} wrote:
>
>>Hi once again,
>>
>>I tried with the faq article you send me. I changed sendmail.cf to
>>DontBlameSendmail=safe. The group is the same since installation. I
>>still get the same error msg. any more hints? I'm desperate seeking
>>the solution.....
>>
>>Thanks.
>>
>>
>>-----Original Message-----
>>From: Daniel Liston [mailto:dliston@sonny.org]
>>Sent: Wednesday, February 26, 2003 7:34 PM
>>To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users
>>Subject: Re: Error Msg sending newsletter
>>
>>
>>
>>I kind of have an aversion to using daemon for the majordomo group.
>>Please notice sendmail's FAQ on the majordomo subject:
>>
>>http://www.sendmail.org/faq/section3.html#3.32
>>
>>If you did change the group without recompiling majordomo's wrapper
>>you could get error messages in the log, but another possibility is
>>the version of sendmail you upgraded to (as a side effect of the newer
>
>
>>OS) might utilize a submit.cf similar to the sendmail.cf. If this is
>>the case, make sure you have a "trust" statement for the majordomo
>>user in that file too.
>>
>>Dan Liston
>>
>>
>>
>>>Hi again,
>>>
>>>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450
>>>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480
>>>Majordomo 1.94.5
>>>
>>>I only copied the lists. The lists directory was created by the
>>>majordomo installation. Then changed owner on the lists and
>>>list.config files. Uid still the same, but other group. Now I'm using
>>>group daemon before majord had an own group. In the Log file this
>>>error isn't logged. I don't understand the linking and the smrsh
>>>thing. And the group writable issue shouldn't be bothering as group
>>>has no write permission the hole path down to majordomo.
>>>
>>>Thank for help.
>>>Maurizio
>>>
>>>
>>>
>>>-----Original Message-----
>>>From: Daniel Liston [mailto:dliston@sonny.org]
>>>Sent: Friday, February 21, 2003 7:08 PM
>>>To: majordomo-users@greatcircle.com
>>>Subject: Re: Error Msg sending newsletter
>>>
>>>
>>>You also need to check down to /usr/local/majordomo/lists actually.
>>>NO, Definately do NOT change any permissions to group writable if you
>>>want to keep sendmail happy.
>>>
>>>You have not mentioned your hardware, operating system, or versions
>>>of
>>
>>
>>>sendmail or majordomo. If you just "copied" majordomo from one
>>>server
>>
>>
>>>to the other, did you make SURE that you used the same UID and GID on
>>>both machines? I mean the number, not the name. Wrapper is dependent
>>>on this. If sendmail is new on one machine than the other, you may
>>>also need to add a link to wrapper in the proper smrsh directory.
>>>Perhaps a cut and paste of the exact error message from the log file
>>>would be helpful here too.
>>>
>>>Dan Liston
>>>
>>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote:
>>>
>>>
>>>
>>>>I checked permissions on my subscriber files, but still get the
>>>>error.
>>>
>>>
>>>>The directory structure down to majordomo is not group writable. I
>>>>installed with daemon as group, but majord is not member of it. any
>>>>other hints? must the dir structure be group writable? I'm SysAdmin
>>>>but I don't know Sendmail and its behaviors...... any help is
>>>>apreciated a lot.
>>>>
>>>>Maurizio
>>>>
>>>>-----Original Message-----
>>>>From: Daniel Liston [mailto:dliston@sonny.org]
>>>>Sent: Friday, February 21, 2003 4:50 PM
>>>>To: Cencigh, Maurizio {PGID~Kaiseraugst};
>>>>majordomo-users@greatcircle.com
>>>>Subject: Re: Error Msg sending newsletter
>>>>
>>>>
>>>>Check the ownership/permission on your new majordomo installation.
>>>>If you are running sendmail on the new server, it might now allow
>>>>group or world "writable" permission down the path to majordomo's
>>>
> directory.
>
>>>
>>>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail
>>>>will also complain about group or world writable :include: files in
>>>>your lists directory. These are your list membership or zubscriber
>>>>files.
>>>>
>>>>Dan Liston
>>>>
>>>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>hi all,
>>>>>
>>>>>I'm migrating a Server, so I installed a new Majordomo on the new
>>>>>server. I copied the old lists and aliases. When I send a mail to
>>>>>majordomo like who listname or lists, I get back an answer. When I
>>>>
>>try
>>
>>
>>>>>to send a newsletter to a list I get the error message below.
>>>>>Anybody an idea? Please help. My majordomo isn't working right now.
>>>>>
>>>>>Unable to expand a distribution list to deliver the message to its
>>>>>members. Try again or contact your system administrator.
>>>>>
>>>>>Thanks in advance.
>>>>>Maurizio
>>>>
>>>>
>>>>
>>
>
>
|
|
