Hi
Just as an aside;
It's hard to say. Apple ships that as a closed black box, so virtually everything under the hood is hidden from view, even from those people who would otherwise know what they're doing.
Its a bitter truth but Apple's position is that " they don't support 'their' Mailman ". Expect a lot more traffic from drowning MacHeads on this list, of which I am one.
I find it kind of unethic given that OS X Server is *sold* on the basis that it has all this cool Open Source software, but in my experience, when you call up tech support they know nothing beyond pushing buttons. The Mailman is not even included in free support days.
I had a really simple problem [ hostname incorrect due to setting up X server prior to knowing domain name ] and wasted a couple of hours over a few days with countless techs ending in a semantic debate over what the support contract included. [ They would not even show me what their guidelines are ].
With MacOS X Server, about the only thing we can recommend is that you contact Apple to find out how to fix what they've shipped.
There is nothing in the kbase or their inhouse knowledge base and the frontline are told to merely sell you a paid consultation with professional tech support services [ for which price you could have bought Communigate ].
No guaranties given your problem with be solved but credit card details taken.
Beware!
MA
I've recently gotten some more contacts inside Apple and I'm trying to get contacts with the team that is responsible for creating MacOS X Server. So far, I'm not having any luck.
Good luck!
At 11:43 PM +0100 2004-09-02, demo wrote:
Its a bitter truth but Apple's position is that " they don't support 'their' Mailman ". Expect a lot more traffic from drowning MacHeads on this list, of which I am one.
I'm picking up some contacts within Apple, and they tell me that
the team which is responsible for developing and maintaining MacOS X Server is non-responsive to them, too. They don't just blow off their customers, they also blow off their co-workers.
There's not much you can do in the face of those kinds of problems.
-- Brad Knowles, <brad@stop.mail-abuse.org>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
SAGE member since 1995. See <http://www.sage.org/> for more info.
On 2-Sep-04, at 7:36 PM, Brad Knowles wrote:
I'm picking up some contacts within Apple, and they tell me that the team which is responsible for developing and maintaining MacOS X Server is non-responsive to them, too. They don't just blow off their customers, they also blow off their co-workers.
There's not much you can do in the face of those kinds of problems.
The pity of it is that on the regular MacOS X it is trivial to get Mailman going. After a head crash took out my hard drive last week I installed MacOS 10.3 on the new drive, set up my network environment, and made sure my connections to the net were OK. Next I downloaded Postfix Enabler, ran it to set up and start Postfix, checked my addresses were working, then download Mailman 2.1.5, followed the regular install instructions, ran check_perms -f, linked the alias db to Postfix per the Postfix READ ME, fixed up httpd.conf, and fired up my lists. I still have to set MM as a startup application, but that's just laziness on my part. I used to run qmail with MM, but the Postfix set up was so easy I couldn't be bothered jumping through djb's hoops (that laziness factor again).
participants (3)
-
Brad Knowles -
demo -
Peter Tattersall