Due practice and proper diligence, and troubleshooting, are part of
the territory.
Yes, but poor sw QA and QC by the vendor are not. A computer
configured with the supplied software should operate and update
cleanly. While Leopard Server Mail is riddled with problems, this is
the first time I've seen a Mac OS update crash in several years, and
is all the more surprising to me given that the client upgrade went
so smoothly on another of my boxes. To me, given the past six months
of using it and trying to work with Apple to get it to work as
advertised, Leopard Server is a great example of how not to do QA and
QC before releasing a product on an unsuspecting user base.
There's little in what you've said that allows anyone to try to help you.
I gave you all the information I had and that was obvious.
However, this is the first I've heard of Mail Services "not working"
as in, not at all.
Wow! Please try perusing the discussion lists. Virtual domains are
REALLY broken in Leopard Server (to the point that they, effectively,
do not work at all), as are several other parts of Mail, such as
users with multiple addresses in multiple virtual domains, the limit
on the number of user aliases, etc.. I'm not going to go into those
in this thread, however.
I'd suggest checking the system disk, run a permissions repair (not
a panacea but apropos here),
Good idea. Did not help. :-(
and re-apply the update using the Combo updater
Novel approach. I'll try it later, once I've calmed down and I've
allowed a reasonable time from the previous inavailability of the
server.
Is that exactly the problem you're having? What error messages are you seeing?
Please be explicit in the problem details not the ranting.
I gave all the information I had at the time: the check box refused
to let me set incoming SMTP on. I now have extra information since
that post to this list. I get this error message in the SMTP log:
May 29 17:19:30 mini postfix/master[6148]: fatal: 0.0.0.0:smtps:
nodename nor servname provided, or not known
I have now noticed that each time the above error happens, I also get
these two lines in the system log:
May 29 17:33:32 mini com.apple.launchd[1] (org.postfix.master[6368]):
Exited with exit code: 1
May 29 17:33:32 mini com.apple.launchd[1] (org.postfix.master):
Throttling respawn: Will start in 9 seconds
There are no other lines in the system log. The mail log shows only
the postfix error line (many, many times; i.e. every ten seconds).
If you're seeing the discussions error "postfix/masterXXXX: fatal"
(where XXXX is some number):
I said that in my post to the above thread. :-/
I'm not trying to be nasty, either. I'm just soooo fed up with
Leopard Server Mail (and other parts of Server). My frustration is
showing.
sudo launchchtl list | grep postfix
Hmmmm:
sudo: launchchtl: command not found
Even after repairing permissions. Not encouraging.... :-/
Thanks for the help.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
