What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users. Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Hi Nick, why should it cause trouble? I think sendmail got the rights to write in there, this is the outgoing mail "folder". Users shouldn't be able to access it, since you don't want me read your outgoing mail. ;-) Or are you mistaken it with /var/spool/mail, the *incoming* folder? Am I understanding something wrong?? Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Sun, 10 Sep 2000, juergen.braukmann@ruhr-west.de wrote:
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Hi Nick,
why should it cause trouble? I think sendmail got the rights to write in there, this is the outgoing mail "folder". Users shouldn't be able to access it, since you don't want me read your outgoing mail. ;-)
Thats the problem sendmail can't get to the dir. I'm guessing that the security update changed sendmail. So the problem isn't with the dir's perms but with the fact sendmail is running under the users ID. That's why everything works fine if I do things from root but any users gets an error. The change breaks all the "old" programs that call sendmail directly. Programs like this one give you the choice of connecting to a SMTP server or calling sendmail. Am I the only one to install the new sendmail rpm? Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Nick Zentena wrote:
On Sun, 10 Sep 2000, juergen.braukmann@ruhr-west.de wrote:
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Hi Nick,
why should it cause trouble? I think sendmail got the rights to write in there, this is the outgoing mail "folder". Users shouldn't be able to access it, since you don't want me read your outgoing mail. ;-)
Thats the problem sendmail can't get to the dir. I'm guessing that the security update changed sendmail. So the problem isn't with the dir's perms but with the fact sendmail is running under the users ID. That's why everything works fine if I do things from root but any users gets an error. The change breaks all the "old" programs that call sendmail directly. Programs like this one give you the choice of connecting to a SMTP server or calling sendmail.
Have you checked sendmail's permission's? It should be 104555, that is it has "set user ID on execution" set. I use mc all the time, just ,<control-x><c> sendmail and make sure the "set user ID on execution" is set. That will allow users to be able to get into mqueue as root. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Mon, 11 Sep 2000, zentara wrote:
Have you checked sendmail's permission's? It should be 104555, that is it has "set user ID on execution" set. I use mc all the time, just ,<control-x><c> sendmail and make sure the "set user ID on execution" is set. That will allow users to be able to get into mqueue as root.
No it's just 755. No suid set. The question now becomes was it supposed to be changed that way or did SuSE screw up with the new rpm? Time to go ask in the security mailing list I guess. Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Well for those following this little story. Suse has pulled the rpm for the moment. Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Mon, 11 Sep 2000, Nick Zentena wrote:
On Sun, 10 Sep 2000, juergen.braukmann@ruhr-west.de wrote:
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Hi Nick,
why should it cause trouble? I think sendmail got the rights to write in there, this is the outgoing mail "folder". Users shouldn't be able to access it, since you don't want me read your outgoing mail. ;-)
Thats the problem sendmail can't get to the dir. I'm guessing that the security update changed sendmail. So the problem isn't with the dir's perms but with the fact sendmail is running under the users ID. That's why everything works fine if I do things from root but any users gets an error. The change breaks all the "old" programs that call sendmail directly. Programs like this one give you the choice of connecting to a SMTP server or calling sendmail.
Am I the only one to install the new sendmail rpm?
What ``new sendmail rpm''? Version, date, place of origin? I can't see any sendmail updates for 6.4 -Kastus
Nick
-- ----------------------------- Anybody got plans for an ark? -----------------------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Should be up soon..I just copied it from Germany this afternoon. ;) --> -->What ``new sendmail rpm''? Version, date, place of origin? I can't see any -->sendmail updates for 6.4 --> -- Cheers, Ben Rosenberg mailto:ben@whack.org ------------------------- Warning to the Human Race: Objects in mirror are dumber than they appear. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Are you confusing mqueue(outgoing) with mail? My /var/spool/mqueue is 700, while /var/spool/mail is 777. If users can't write to mqueue, you may need to see if sendmail is started. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Sun, 10 Sep 2000, zentara wrote:
Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
Are you confusing mqueue(outgoing) with mail? My /var/spool/mqueue is 700, while /var/spool/mail is 777.
If users can't write to mqueue, you may need to see if sendmail is started.
No something is wierd. using Pine,mail,mailx I get: barley sendmail[30360]: NOQUEUE: SYSERR(zentena): can not chdir(/var/spool/mqueue): Permission denied In my logs. But kmail works fine. Assuming this makes it out-). It uses smtp. The rest may be calling sendmail directly. Actually Pine gives me a 421 error message from SMTP. Everything was working until I installed the security update. Maybe it's too secure. Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On 10 Sep, Nick Zentena wrote:
What should the perms and ownership be on /var/spool/mqueue be? I think the sendmail upgrade rpm may have changed it. I'm seeing 700 root root. Which is causing problems for non root users.
Nick
-- ----------------------------- Anybody got plans for an ark? -----------------------------
Hi Nick! Thoose permissions looks alright to me. Only root should be able too lock and cd into that directory. As an ordinary user you should be able to use the command 'mailq' to check the mail queue. TJo -- This Email is 100% Virus Free! How do I know? Because no Microsoft products were used to generate it! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (6)
-
ben＠whack.org -
juergen.braukmann＠ruhr-west.de -
kastus＠tsoft.com -
tjo＠telia.com -
zentara＠gypsyfarm.com -
zentena＠hophead.dyndns.org