Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'fix dosn't work' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
fix dosn't work
Authored by: macubergeek on Jun 06, '02 02:18:15PM

none of the fixes works for me
WHY DOES APPLE INSIST ON BREAKING MY MAIL COMMAND.



[ Reply to This | # ]
fix dosn't work
Authored by: ppmax on Jun 06, '02 02:36:59PM

first: thanks to poster #2 who provided excellent reading materials. the mailing lists are an excellent resource.

next: here is a post of two relevent discussions. the first is relevent to macubergeek; the second is a step by step for configuring sendmail for 10.1.5. to give credit where credit is due: these were copied from the macosx-server-mailing list referenced above and posted by Chuq Von Rospach, and apple employee.

1. Every vendor will stomp on config files -- this ain't new to Software
Update. Apple's a lot better than most Unix vendors in my experience at
trying to do the right thing here. But think about the situation with, say,
sendmail.cf. If you update sendmail from 8.11 to 8.12, the sendmail.cf has
to be regenerated. Apple has three choices with that file:
1) install a new sendmail.cf, erasing your customizations. You're upset.
2) leave it alone, breaking sendmail. You're upset.
3) do either of the above, but install a README telling you what needs to be
done -- which you won't read until long after you realize things are broken
and you're upset. If then.
There is no way to successfully handle an upgrade case like this without
breakage in common cases. Fortunately, upgrades like this are pretty rare.

The answer is to always, always keep copies of the files you've changed in
the areas of the filesystem that is "owned" by the OS



2. First -- sendmail is now 8.12.x instead of 8.11. That changes some stuff,
mostly for security-improvement reasons. "it worked in 8.10.4"
unfortuantely, isn't a good reason to hack that stuff back out again. You
want the security upgrades. Honest.

But one thing the upgrade didn't do is install an updated sendmail.cf along
with the sendmail binary. So if you're a generic system, you have sendmail
8.12, and a sendmail 8.11 cf file. Those don't like each other, so the
system is broken out of the box. I've filed a bug in RADAR on that -- at the
least, we need to generate a .cf and put it somewhere with a README. Note
if you generated your own .cf file under 10.1.4 and before, you'll have to
generate a new one for 10.1.5, but in almost all circumstances, that's
simply running m4. If you did something that requires tweaking because of
the upgrade -- you probably know sendmail well enough to work it out.

To get up and running, here's what you do:

1) follow the instructions in /etc/mail/README. You do not need to change
the mc file -- it should work without changes, so you can skip the second
and third instructions (sudo cp and sudo vi) and run the m4 on the
generic-darwin.mc file.

2) the upgrade leaves the sendmail client queue directory with the incorrect
group, so you can't use it. To fix:
o ch /var/spool
o sudu chgrp smmsp clientmqueue

(I've filed a bug on this in RADAR)

3) the ugprade turns on write for group on the '/' directory. The correct
thing to do, I think, is to set DontBlameSendmail to not nag you about this,
but I've decided not to change the sendmail.cf files, so the quick way to
Fix this nis:
o sudo chmod g-w /

Note this will mean you can't copy stuff into the root in the finder. If you
need that, figure out the DontBlameSendmail config items.

4) Add the line:

/usr/sbin/sendmail -C /etc/mail/submit.cf -q1h

To

/Library/StartupItems/Sendmail/Sendmail

After the first invocation of sendmail.

5) Set MAILSERVER to YES in /etc/hostconfig

6) restart.

You should now have a functioning mail system under 10.1.5.

Note: under sendmail 8.11 (MacOS X 10.1.4 and before) you didn't need a
sendmail daemon running for local-only mail delivery. Under sendmail 8.12
(MacOS 10.1.5) you do. If you want to, say, mail to "root,
root@serverbox.com" you now need to turn on a sendmail daemon. This is
required by the new security regimen in sendmail 8.12 to protect sendmail (a
setuid-root program) from access by hackers on the local system.

If you change this (by hacking or replacing submit.cf), you are opening
yourself up to security problems. My recommendation: DON'T DO IT. If you
insist, don't complain to me later.

If you only want to send mail to non-local accounts (i.e.,
root@serverbox.com with no copy kept on the machine), you can configure
submit.cf to use a system other than localhost for delivery. You'll need to
decipher sendmail's instructions on how to do so -- I haven't done it yet.
If you aren't comfortable whacking sendmail, then don't do it. Just do the
above and keep it simple. I've filed an RFE in RADAR to suggest that
creating a submit.mc that is configured for this case, and a README
explaining how to customize it for your smart mailhost, is a very good thing
to have.

Hopefully, this will get this straightened out a bit for folks.



[ Reply to This | # ]
fix does work
Authored by: cj69collins on Jun 10, '02 09:39:38PM
Thank you. Between your hint for getting sendmail working, it works like a champ. Using this article to setup IMAP, and figuring out I could forward mail to IMAP:username@localhost, I now get my system messages through Entourage. Notes: > Get the latest devtools to compile WU IMAPd. [Found this hint in the forums.] > Beware of fiximap.pl. It did not work for me. I edited env_unix.c, replacing line 676 with this:
sprintf(tmp, "%s/Library/Mail/Mailboxes", home); myHomeDir = cpystr (tmp); /* set home directory */
> You need to change ~root/.forward from /dev/null to IMAP:username@localhost for the trick to work. > You also need to change /etc/crontab to something similar to the following
30 17 * * * root sh /etc/daily 2>&1 | tee /var/log/daily.out | mail -s "daily output" root 40 17 * * 2 root sh /etc/weekly 2>&1 | tee /var/log/weekly.out | mail -s "weekly output" root 50 17 1 * * root sh /etc/monthly 2>&1 | tee /var/log/monthly.out | mail -s "monthly output" root


[ Reply to This | # ]
fix dosn't work
Authored by: richardjpratt on Jun 14, '02 11:37:49PM

If you want to know how to set DontBlameSendmail you can see this article:

http://www.macdevcenter.com/pub/a/mac/2002/06/07/sendmail_1015.html

It duplicates a lot of the good advice you've already mentioned.
Thanks!



[ Reply to This | # ]