Mail service Manual 10.6 in Spanish

Does anyone knows where can i get Mail Service Administration Manual 10.6 in Spanish?

Mail should be in /var/imap unless you installed an alternate mail system: you referenced Dovecot? Did you have Dovecot running on SLS?
The /var/imap directory should be existent even if you never enabled SLS's Mail service, with contents like:
drwxr-xr-x 8 _cyrus mail 272 Oct 25 2010 db
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 log
-rw-------     1 _cyrus mail 144 Oct 25 2010 mailboxes.db
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 msg
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 proc
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 ptclient
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 socket
drwxr-xr-x 2 _cyrus mail   68 Oct 25 2010 sync
This is from a server that never had Mail enabled..
I have no idea whether the the command you referenced would do a migration if there is no /var/imap directory on the source volume.
-Doug

Similar Messages

Link to Mail Service Admin v10.4 pdf manual

I've acquired an Xserve with Server 10.4 and have been having difficulty finding the pdf manual for the 10.4 version of Mail Service Admin, most links pointing to the 10.5 version. Does anyone have a link to that older version o the pdf?
Thanks

Here you go.
http://manuals.info.apple.com/enUS/Mail_Servicev10.4.pdf

My emails no longer show up unless I go to the mail app manually. Never had a problem before this. Help!

My emails no longer show up unless I go to the mail app manually. Never had a problem before this. Help! I have shut off phone I have tried to change the time for how long the mail will show up but nothing is working

Do you mean you don't get notified of new emails automatically (eg. on the Lock Screen)? This could be because this function is turned off in Settings > Notifications. It could also be that the email account you use is having problems with its PUSH service, if it offers one.

PSE 7.0 Crashes w/Adobe E-Mail Service

PSE 7.0 crashes with the following response when I try to send an image using Photomail or as an attachment.
It appears to work fine (or at least gets to the point where I can edit the message) when using Outlook or Outlook Express. However, we use Thunderbird, so would prefer to use the Adobe E-Mail service. We upgraded from PSE 4, which worked on the Adobe E-Mail Service with no issues.
"Adobe Photoshop Elements 7.0 (Organizer) has encountered a problem and needs to close. We are sorry for the inconvenience."
It gets to the point where the email shows up on the right-hand sidebar, then the mouse goes to an hourglass for a few seconds and then the above error message.
I'm running XP Pro SP3.
Any ideas?
Thanks,
Marc

A couple of other thoughts:
1. Perhaps PSE 7 doesn't like the PSE 4 address book. That happens occasionally, though I recall it caused other symptoms, not a crash. You could find all copies of the file "contacts.xml" and delete them, and see if that helps. Different versions of PSE can hide these in dfferent folders, so configure Windows Explorer to show hidden files and then search your entire C drive.
2. You could try the sledgehammer approach of uninstalling PSE 7, manually removing all traces left behind by the uninstaller, and then re-installing in what Adobe calls "simplified mode", with anti-virus and all other background services disabled:
http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#Try_Adobes_generic_troub leshooting

Mail service setup basics

Dude!,
I have been searching and digging for days trying to understand this setup.
I purchased a mac mini with server software and trying to get mail services to work.
It should not be this hard! I have set up my dns for my local domain and doubled checked via terminal that my ip matches the name. I have mutiple doamins I would like to revcieve mail from on this server. All my users are the same on each domain. like, [email protected] and [email protected], ect.
In the general tab of mail services I set the following
domain name : mydomain.com
host name : mail.mydomain.com
in the advanced tab I checked include server daomain as local alias and added my other domain names like
myother.com
myother2.com
I then went to my mail client that I added the local email info,,
What should I use for the incoming mail?
Outgoing mail?
I have looked at mail services user guide, searched through tons of threads, googled everthing from smtp, dns, mail server setup, ect.
I am able however to manually set up a mail client and all works but that kinda defeats my reasoning of this server.
Is there a basic guide I can get that maybe clairifies the basic set issues?
I am sure I am not the only person having these issues?
Thanks

It should be this hard. It's actually quite simple once you take the time to ensure you have a fundamental understanding of numerous key concepts. Marketing for 10.6 server aside (a separate & interesting conversation), it's no more Apple's role to educate any would-be server administrator of these fundamentals than it is for Microsoft to do same with their product manuals, or for that matter Sun (Solaris) or RedHat...
http://www.google.com/search?&q=understanding+TCP/IP
Where/IF NAT is involved:
http://www.google.com/search?&q=understanding+NAT
http://www.google.com/search?&q=understanding+smtp
http://oreilly.com/catalog/9780596100575
http://www.zytrax.com/books/dns/
http://www.google.com/search?&q=postfix+mta
(for 10.6)
http://www.google.com/search?&q=dovecot+mda

Mail Service Errors

Hi,
I'm running Server 10.4.11 for a local newspaper and last week their e-mail services came to a crashing halt. It slowed the system down so much it started to interfere with operations between client/server, so I shut down the mail services until after their production cycle.
Today I turned back on the service and reconstructed the database (was getting a DBError last week). I also rebuilt all of the email accounts... none of which were anywhere near full.
I was getting this in the POP log (set to Information level logging) right after I turned back on the service this evening. It is just a small portion of the log... but it repeats basically the same thing. Can anyone point me in the direction of fixing the service?
Thanks,
Alan
Jan 21 19:27:21 BuffaloBulletin pop3[12406]: DBERROR: critical database situation
Jan 21 19:27:21 BuffaloBulletin master[28101]: service pop3 pid 12406 in READY state: terminated abnormally
Jan 21 19:27:21 BuffaloBulletin pop3[12407]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 19:27:21 BuffaloBulletin pop3[12407]: DBERROR: critical database situation
Jan 21 19:27:21 BuffaloBulletin master[28101]: service pop3 pid 12407 in READY state: terminated abnormally
Jan 21 19:27:22 BuffaloBulletin pop3[12410]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 19:27:22 BuffaloBulletin pop3[12410]: DBERROR: critical database situation
Jan 21 19:27:22 BuffaloBulletin master[28101]: service pop3 pid 12410 in READY state: terminated abnormally
Jan 21 19:27:22 BuffaloBulletin pop3[12411]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 19:27:22 BuffaloBulletin pop3[12411]: DBERROR: critical database situation
Jan 21 19:27:22 BuffaloBulletin master[28101]: service pop3 pid 12411 in READY state: terminated abnormally

Thanks for the suggestion. I followed the instructions for manually reconstructing the cyrus mail database in Terminal. Once I started the service back up (did this twice with same results), here is the log that was generated:
Jan 21 23:28:38 BuffaloBulletin reconstruct[28146]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:28:38 BuffaloBulletin reconstruct[28146]: DBERROR: critical database situation
Jan 21 23:29:18 BuffaloBulletin deliver[28168]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:18 BuffaloBulletin deliver[28173]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:18 BuffaloBulletin deliver[28176]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:19 BuffaloBulletin deliver[28182]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:19 BuffaloBulletin deliver[28188]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:19 BuffaloBulletin deliver[28187]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:19 BuffaloBulletin deliver[28189]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin master[28191]: process started
Jan 21 23:29:20 BuffaloBulletin deliver[28193]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28194]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28198]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28204]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28201]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28200]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:20 BuffaloBulletin deliver[28203]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:21 BuffaloBulletin deliver[28206]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:21 BuffaloBulletin deliver[28208]: connect(/var/mail/socket/lmtp) failed: Connection refused
Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: verifying cyrus databases
Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: skiplist: recovered /var/mail/mailboxes.db (29 records, 4480 bytes) in 0 seconds
Jan 21 23:29:22 BuffaloBulletin ctl_cyrusdb[28196]: done verifying cyrus databases
Jan 21 23:29:23 BuffaloBulletin master[28191]: No address associated with nodename, disabling sieve
Jan 21 23:29:23 BuffaloBulletin master[28191]: ready for work
Jan 21 23:29:23 BuffaloBulletin ctl_cyrusdb[28220]: checkpointing cyrus databases
Jan 21 23:29:24 BuffaloBulletin ctl_cyrusdb[28220]: done checkpointing cyrus databases
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29299 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29300]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29300]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29300 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29301]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29301]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29301 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29302]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29302]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29302 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29303]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29303]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29303 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29304]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29304]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29304 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29305]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29305]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29305 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29306]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29306]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29306 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29307]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29307]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29307 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29308]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29308]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29308 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29309]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29309]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29309 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29310]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29310]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29310 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29311]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29311]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29311 in READY state: terminated abnormally
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29312]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:44 BuffaloBulletin lmtpunix[29312]: DBERROR: critical database situation
Jan 21 23:30:44 BuffaloBulletin master[28191]: service lmtpunix pid 29312 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29313]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29313]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29313 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29314]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29314]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29314 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29315]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29315]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29315 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29316]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29316]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29316 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29317]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29317]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29317 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29318]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29318]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29318 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29319]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29319]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29319 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29320]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29320]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29320 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29321]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29321]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29321 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29322]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29322]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29322 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29323]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29323]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29323 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29324]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29324]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29324 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29325]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29325]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29325 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29326]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29326]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29326 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29327]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29327]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29327 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29328]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29328]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29328 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29329]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29329]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29329 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29330]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29330]: DBERROR: critical database situation
Jan 21 23:30:45 BuffaloBulletin master[28191]: service lmtpunix pid 29330 in READY state: terminated abnormally
Jan 21 23:30:45 BuffaloBulletin lmtpunix[29331]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:30:46 BuffaloBulletin lmtpunix[29331]: DBERROR: critical database situation
Jan 21 23:30:46 BuffaloBulletin master[28191]: service lmtpunix pid 29331 in READY state: terminated abnormally
: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29835]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29835 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29836]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29836]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29836 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29837]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29837]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29837 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29838]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29838]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29838 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29840]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29840]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29840 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29841]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29841]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29841 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29842]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29842]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29842 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29843]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29843]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29843 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29844]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29844]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29844 in READY state: terminated abnormally
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29845]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:19 BuffaloBulletin lmtpunix[29845]: DBERROR: critical database situation
Jan 21 23:31:19 BuffaloBulletin master[28191]: service lmtpunix pid 29845 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29846]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29846]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29846 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29847]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29847]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29847 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29848]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29848]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29848 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29849]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29849]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29849 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29850]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29850]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29850 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29851]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29851]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29851 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29852]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29852]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29852 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29853]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29853]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29853 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29854]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29854]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29854 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29855]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29855]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29855 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29856]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29856]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29856 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29857]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29857]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29857 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29858]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29858]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29858 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29859]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29859]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29859 in READY state: terminated abnormally
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29860]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:20 BuffaloBulletin lmtpunix[29860]: DBERROR: critical database situation
Jan 21 23:31:20 BuffaloBulletin master[28191]: service lmtpunix pid 29860 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29861]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29861]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29861 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29862]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29862]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29862 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29863]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29863]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29863 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29864]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29864]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29864 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29865]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29865]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29865 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29866]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29866]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29866 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29867]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jan 21 23:31:21 BuffaloBulletin lmtpunix[29867]: DBERROR: critical database situation
Jan 21 23:31:21 BuffaloBulletin master[28191]: service lmtpunix pid 29867 in READY state: terminated abnormally
Jan 21 23:31:21 BuffaloBulletin master[28191]: exiting on SIGTERM/SIGINT
Jan 21 23:31:21 BuffaloBulletin deliver[28264]: backend_connect(): couldn't read initial greeting: (null)

Major Mail Service Panic after upgrade! Customer about to kill me!

Me again.
As mentioned in another thread, I had to upgrade an Xserve from 10.3.9 to 10.4.3 for a customer. When I ran the upgrade I discovered that the volume containing the mail database was damaged. I wasted a day getting the data off this onto another drive, then did the upgrade. Because the mail database had been moved and might have the odd missing file I used mailbfr -o and mailbfr -f at this point. Now, all client mail folders are back as they should be but all new mail is stuck in the queue. Outgoing mail can be sent successfully.
Now, I know an amateur like me shouldn't be messing with the config files willy-nilly to try and fix this without a clear idea of what's going on. However, given that the customer and his 20 staff are going mad waiting for their mail I tried to get it right by directly comparing their config files with the equivalents on my own 10.4.3 server which is set up more or less identically and is working.
I will get lynched if I can't make this work soon. Here's postconf -n and a snippet of the smtp log. Please someone look at this and save my life!!
mail:/var/log root# postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
always_bcc =
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
inet_interfaces = all
luser_relay = postmaster
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains = dun.dnsrbl.net,relays.ordb.org,bl.csma.biz,bl.spamcop.net,sbl-xbl.spamhaus.org
messagesizelimit = 0
mydestination = $myhostname,localhost.$mydomain,mail.mandm.uk.com,192.168.1.100,mandm.uk.com,re ed-munkenbeck.com,212.18.249.218,mail.reed-munkenbeck.com
mydomain = mandm.uk.com
mydomain_fallback = localhost
myhostname = mail.mandm.uk.com
mynetworks = 127.0.0.0/8
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdclientrestrictions = permit_mynetworks hash:/etc/postfix/smtpdreject rejectrblclient bl.csma.biz rejectrblclient dun.dnsrbl.net rejectrblclient relays.ordb.org rejectrblclient bl.spamcop.net rejectrblclient sbl-xbl.spamhaus.org permit
smtpdenforcetls = no
smtpdpw_server_securityoptions = cram-md5
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtlsloglevel = 0
smtpduse_pwserver = yes
smtpdusetls = no
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
mail:/var/log root#
smtp log:
Jan 5 12:35:17 mail postfix/master[20503]: daemon started -- version 2.1.5
Jan 5 12:35:17 mail postfix/qmgr[20506]: 3C1983B7F0D82: from=<[email protected]>, size=5704, nrcpt=1 (queue active)
Jan 5 12:35:17 mail postfix/qmgr[20506]: 8C51A3B7F13CA: from=<[email protected]>, size=4047, nrcpt=1 (queue active)
Jan 5 12:35:17 mail postfix/qmgr[20506]: 91B7D3B7F13A8: from=<[email protected]>, size=2638, nrcpt=1 (queue active)
Jan 5 12:35:17 mail postfix/qmgr[20506]: CF9FB3B7F13AF: from=, size=5145, nrcpt=1 (queue active)
Jan 5 12:35:17 mail postfix/pipe[20510]: 3C1983B7F0D82: to=<[email protected]>, relay=cyrus, delay=4489, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
Jan 5 12:35:17 mail postfix/pipe[20517]: 8C51A3B7F13CA: to=<[email protected]>, relay=cyrus, delay=2301, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
Jan 5 12:35:17 mail postfix/pipe[20514]: CF9FB3B7F13AF: to=<[email protected]>, relay=cyrus, delay=2307, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
Jan 5 12:35:17 mail postfix/pipe[20515]: 91B7D3B7F13A8: to=<[email protected]>, relay=cyrus, delay=2307, status=deferred (temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ 421 4.3.0 deliver: couldn't connect to lmtpd_ )
Other symptoms since upgrade: Server Admin refuses to turn on Mailing Lists. There's one list that was in use before the upgrade. If I click 'Enable Mailing Lists' and press Save, the box goes unchecked again as soon as the screen refreshes. Mailaccess.log (as shown in SA as the IMAP log)remains empty. Like the Mailing Lists issue above, I can't change the log detail levels; they just reset to what they were before.
Anything else anyone wants to know I'll post it.
Xserve G5 2.0DP, 2Gb RAM, 10.4.3 (u/g from 10.3.9) Mac OS X (10.4)
G4 and Xserve Mac OS X (10.4)

aha. a-bloody-ha.
I'll live to fight another day. The log entries about the stage. folder got me thinking and I realised that there was something wrong with the permissions. because I'd had to 'rescue' the mail database by moving to another volume, the permissions weren't right. Now, I had run mailbfr and watched it say it was fixing the ownerships and permissions on all this; I shouldn't have taken this for granted. The stage. folder was owned by me (admin) with read-only for everyone else. I changed it (heck, I changed the whole directory tree) to read-write for everyone and instantly mail started pouring in to everyone's accounts.
Everything is now working normally. It still bothers me that the whole shebang seems so fragile - especially in so far as the Server Admin app has at best only a tenuous grasp on the config files it's supposed to be supporting. Looking back over the past two days I can see that the basic setup was right in the first place but the manual changes I've been making in the various conf and cf files were ones that SA was supposed to be able to do for me. The whole point of having Server Admin>Settings>Logging is so you can set the log level right there - not in bloody pico via the bloody command line. Sorry - I'm tired and a little punch-drunk. It also bothers me that, having learned my humble skills on AppleShare 6 (and MacDNS), we're now in a place where none of the key components of the server are actually made by Apple, documented by Apple, or properly supported by Apple. Since Mail Service isn't a closed box with 'Apple' written on it, but a collection of dozens of interconnected third-party processes working in tandem, there really ought to be a 'master document' that shows the complete flow through the system. Most of you guys are proper experts and I'm truly grateful you're there - but I'm not afraid to admit that I didn't actually know that every message had to pass though a folder called stage. on its way to delivery and it would have nice to have been able to find that information in one of Apple's manuals. If I'd known I might have looked at it sooner.
The customer in this case is a firm of architects; they're creatives; non-technical; Apple-lovers precisely because they love the ease of use, the style and the non-pointy-headed approach of Apple's kit. I'm reminded that when this customer bought this Xserve 18 months ago, I made them buy the 3 year service contract for it. But when during the initial setup NAT wouldn't work properly I called Apple for help and they told me that 'setup problems aren't covered'. Good Grief. 450 quid. And let's not forget 700 quid for the 10.4 software.
Now, having saved myself from being lynched by the customer I'm probably going to be strung up by the very people on this list that people like me have to rely on when we get into trouble.
So, to save you all the trouble - yes, I'm a rank amateur; yes, I should do more homework; yes, I promise to keep googling and searching and reading and playing with my in-house machine... I don't promise to do a course on it since 'MacOs Server Essentials' is $2,000 to start with, and I don't have that kind of money.
Think I'd better go have a lie down.

N8 Email - Unable to connect to mail service serve...

I have my Nokia N8 for a good few months. Email stop sync-ing so deleted my 1 and only email account (Hotmail) and now I can not get any email back.
I have played with internet settings, rebooted my phone but still nothing.
Basically, this is what happens:
Got to set up email
Some text comes up about what mail can do and you have the option of start of exit
Press start, and it says preparing for set up, then it comes up with Unable to connect to mail service server. try again later.
The next options I have are to enter email and password or cancel.
If I enter email and password it comes up with an option to click on mail for exchange and I have to start entering user name, domain, etc or I can exit.
So, can anyone help me restore the email function. When I got the phone you had an option of hotmail, yahoo, etc etc. And that is what I want back.
Also I should mention, I don't have any options around pushing or pulling email as it never gets that far into setting up email.
I live in the UK, so was wondering if I should just take it into my local carphone warehouse who deal with Nokia support and demand it gets repaired? It's part of what I paid for so they should repair/replace for me?
Any advice would be good,
Thanks
Vicki
Solved!
Go to Solution.

For the answer of both how and why please refer to the post by Abi99 earlier this week:
http://discussions.nokia.com/t5/Symbian-Devices/quot-Unable-to-connect-to-mail-service-server-quot-o...
Please click the star below that post to draw attention to the expired Nokia certificate, which Microsoft Mobile Oy must renew to solve the problem! - Also use the false username and false password trick, if it is a first time mail setup on a freshly reset Symbian phone, to avoid any Nokia Messaging clutter, and then input server details manually.
EDIT: The expired certificate was renewed is now valid until 2015-07-10
Hans

How Do You Set Mail To 'Manual' ?

Never had problem with iPhone until yesterday. I am not receiving 'push' e-mail anymore. I did not do any changes to the iPhone at all. Any e-mail now I have to go to inbox and click on the curved arrow symbol at bottom left of page in order to load the waiting e-mails. In a different posting someone mentioned to test 'push' function by setting e-mail to 'manual' and then sending your Yahoo account an e-mail from your computer (I assume using a different e-mail service). In the 'settings' menu for 'mail' I do not see where you set for 'manual'. How do you set mail to 'manual' setting? And do you think I should just RESET the iPhone (using the iPhone or hooking it up to iTunes on the computer to RESET) ?

I have no other e-mail accounts set up. Anyway I did RESET my iPhone (using the RESET button on the iPhone) and all is well again (how long I do not know). My e-mails are being 'pushed' again so that I can see from the main menu the little red dots (with the numerals inside) showing how many e-mails are waiting for me. I love this feature. I had 'push' e-mail on my ex-Blackberry. BUT, I do not see the AUTO-CHECK anywhere. I am heading over to the Apple Techies at my local Apple store to ask them about this missing AUTO-CHECK. I have a feeling you need two account set up on your iPhone for this feature to appear. I could be wrong. Thanks, everybody........

Setting up Mail service for first time

I am setting up an internal mail server for the first time. Some questions:
1) What should my domain and host names be listed as in Mail settings?
2) It appears that the mail is set up by the server as [email protected] How do I get the email addresses such that they don't include the 'server' part?
3) I am using a Time Capsule (similar to AEBS) as a router. Which ports do I need to open to allow mail service?
Thanks!

This is based on my observation not any documentation, so take it for what it is worth. The information that you changed determines what mail the email system will accept and pass on. It passes it on based on the shortnames and nothing else.
The email address that is listed in the account information on Server Preferences determines what shows up as "suggested finishes" when a user starts typing an address in while they are in mail.
The email address that is listed in the users Mail setup info on their machine determines what is shown as a return address when they send mail out. It will show what is there even if the return address has no chance of working.
If you delete all of your users on the server and then reenter them, they will be in correctly on the Server Preferences window, but they are still going to have to be changed on the users machines. I've had some problems with the old setup not working on a user machine even after putting something back in exactly the way it was before, resulting in the need to totally remove the account on the users machines mail setup and reenter it. I really think the quick way, which won't be very quick if you have a lot of accounts is to go into both the Server Preferences and manually change the address there, and they either send the users instructions on how to change it on their machines or go to the machine and change/help them change it there.
There may be a quick way, but I haven't found it.

Outgoing mail service offline charter

I cannot send email from my imac. Out going mail service shows offline with no other options. I can send email from my iphone. Help?

maybe some some helphere
http://support.apple.com/kb/index?page=search&src=support_site.kbase.search&loca le=en_US&q=off%20line%20email%2010.6.6
http://support.apple.com/kb/index?page=search&product=&q=send%20email%20iPhone&s rc=support_site.kbase.search.searchresults

Setting up mail services. Name of server needs to be changed?

I setup my xserve with snow leopard. By default it was named server.ourcompanyname.private.
Here is my problem Im trying to host our company web site along with mail services. Need to bring all this in-house.
I have with my web provider 5 dedicated IP address, and router address. I bridged the modem to an airport extreme to hand out all the ip address and DHCP, this was done with apple support.
I need advise on how to go about setting up all the services. Can the name of the server be changed without causing major problems?
Any advise would be appreciated.

One other note. Can I change the .private. to .com and will this help me setup mail and hosting services?

ERROR: Cannot start mail services, configuration directory does not exist

I'm running an Xserve G5 with one internal boot drive and one RAID using the other two internal drives. I used Apple's Disk Utility to set-up the RAID.
Back in early December, I moved my mail database and mail store to the RAID. Ever since, when I restart the server, the mailaccess.log generates the following error:
Jan 23 18:51:33 mail master[47]: ERROR: Cannot start mail services, configuration directory does not exist: /Volumes/RAID/mail.data/db
I'm speculating this is a timing error that gets created when Postfix initially can't find the RAID. Then, it must try again and find it because the error message does not repeat and mail starts running.
Is this something to worry about?

Hi Joel,
You're right, it's a timing issues. The mail system is ready for work before the file system is mounted. It's benign.
Jeff

How do I set up Mail service for simple IMAP with SSL?

This should be easy but something isn't working. I have an Xserve with 10.6. I've enabled the Mail service, and want to add this server as an Account under Entourage. I've put in the IP address, my username/password, etc. but something isn't working. It appears under the Accounts folder tree, but when I try to send an email, I have a window that says "4.7.0 TLS not available due to local problem", Error -17099". I've also seen errors telling me the password is being sent in cleartext and I can't see where I enable the same (SSL, password needed) settings on the client and the server menus. Can someone clue me in - what are the right settings on both ends to have a simple IMAP w/o cleartext passwords? I had this working fine in 10.4 Server... Thanks!
Mike

I see dropdown menus for SMTP SSL and IMAP/POP SSL. I have them both set as "Require"
Do not to this if your server is handling incoming mail from outside your network.
Few remote mail servers will use SSL, so if your server requires SSL then you will not be able to receive mail from outside your domain.
'Use', on the other hand, advertises the fact your server supports SSL, so clients and remote servers can use if if they like, but this still allows other mail in.
What should "Authentication" be - "Login" or "Plain"
Do not use Plain unless you absolutely trust all your clients (i.e. they're all on a LAN or all using SSL). Plain sends an unencrypted password over the wire, which is susceptible to sniffing.
what will the client be using?
Whatever you set it to.
The client complains about a correct root certificate not being installed).
Are you using a self-signed certificate? if so, you're going to get that unless you do a lot of extra work. Getting a real certificate from a trusted authority should resolve this.
As for the slow connections, the use of SSL shouldn't significantly impact connection or delivery/transfer times, so something else is amiss.

Why cant i disable mail service ?

Mail service got enabled when I enabled some other services (don't know which one) i checked a couple and it got enabled, i tried to disable it then but it wouldn't let me, back then i didn't pay much attention to it so of course it's not configured. Right now the server is going crazy with disk IO, ran iotop and found out there are 2 processes to blame, 1 is mds (i'll murder spotlight soon) and the other is qmgr which from the man page i found it's mail related, my mail is hosted on gmail so i have no intention of using this service. If i click stop nothing happends, same if i uncheck it under services.
this is the ouput on the syslog when i try to stop
servermgrd[69]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) syncClientServicesConfigRecord]: Error writing ClientServices config record: Error Domain=com.apple.OpenDirectory Code=4001 UserInfo=0x10652ad30 "Unable to set value or values for dsAttrTypeStandard:XMLPlist in the record ClientServices."
servermgr_info: markrunning_servicesconfigured(): marked running services configured: com.apple.ServerAdmin.DNS, com.apple.ServerAdmin.SWUpdate, com.apple.ServerAdmin.Web, com.apple.ServerAdmin.NFS, com.apple.ServerAdmin.DirectoryServices
also, my syslog is full of
postfix/qmgr[3830]: warning: connect #1 to subsystem private/rewrite: Connection refused
I'm guessing it's required by some other service, i currently have...
DNS
Mail -> DIE
NFS
Open Directory
Software Update
Web
Xgrid - Stopped ( just testing )
Is there any way to kill it, or is my only way around it to figure out what's wrong with it (no one is using it for mail so i don't get why is it so busy).

Unchecked 'Enable SMTP', 'Enable IMAP' and 'Enable POP', then checked 'Deliver to /var/mail
That seemed to 'disable the mail service'
As for disk usage, i'm running a cron job every minute so que queue had close to 6k mails it couldn't deliver. deleted them all " sudo postsuper -d ALL " and redirected output on the cron job to /dev/null

Mail service Manual 10.6 in Spanish

Similar Messages

Maybe you are looking for