Server Admin cannot update any mail settings on nearly fresh 10.4 server

Question

I can no longer use the Server Admin application to change settings under Mail (and I need to make some changes - would like to change logging settings and require authentication for SMTP). I made some initial settings with no problems, but now it chokes...
For example, I click on Mail, Settings, Advanced... and then try to click the box to require Kerberos Authentication for SMTP-- everything is normal until I hit SAVE. Then there is a delay of 10 or 15 seconds, followed by the error message:
"A connection with a server or service was lost. Try to disconnect from XServe.local and then reconnect, or contact your network administrator."
At this point the mail indicator is red, not green... after clearing the message the changes I've made to settings appear intact, but if I quit server admin the truth comes out... I'm asked would I like to save changes, if I say yes the error will repeat-- I have to quit without saving. Relaunching Server Admin reveals that indeed the changes have not been made.
I've heard of this type of problem when hand editing config files, but I've not done that with any mail-related files (I made two minor changes to a http config file a while ago, otherwise it's all been through Server Admin).
Is there any way to reset the mail-related files so that Server Admin will return to life, or do I have to reformat the drive and reinstall OS X 10.4.4 hoping it doesn't happen again?
By the way, the problem started a few days ago, and the upgrade to 10.4.4 didn't magically cure it.

Answer 1

I'm having the same problem (and updating to 10.4.5 did not fix it either).
In my case, it takes 30 seconds for the "A connection with a server or service was lost." to come up; I have a lot of mailing lists, and was wondering if it was some sort of timeout value on the server admin server end. (I hope that Server Admin doesn't write out every mailing list's membership every time you change any Mail setting!)
You can make some changes using the serveradmin command line tool. For example, I noticed this problem when trying to turn on log-rolling.
First, to find the appropriate command:
sudo serveradmin settings mail > mailsettings
I grepped for "log":
grep "log" mailsettings | grep -v mailman
(grep -v mailman drops any mailman settings, such as all of the users where "log" appears in their e-mail address)
And found:
mail:postfix:logrolling_daysenabled = no
I then ran the command:
sudo serveradmin settings mail:postfix:logrolling_daysenabled = yes
to turn log rolling on. Quitting Server Admin and getting back into it showed that logrolling_daysenabled was enabled.
So that might be a temporary solution for simple changes.
In my case, this is a very fresh server: purchased and put into play over a period of three weeks. It worked until I copied the mailing lists over, but a small number of mailing lists copied did not trigger the error. This is what leads me to believe there is some kind of timeout happening.
Jerry