Mail service keeps corrupting.

Hello all,
My mail service keeps corrupting on my PowerMac running Mac OS X 10.3 Server.
I have reinstalled my server 3 times due to this problem.
Any one else having the same problem?
any solutions?
Thanks,
Chris

In addition to Alex's request for logs, and more info- I would point out that you are TWO major revs behind. I bet the downtime is worth more than the 499 upgrade (the 10 user limit applies only to filesharing). Give tiger or 10.5.1 a try.
It rarely makes sense to troubleshoot something thats already been fixed by Apple.
my $.02
Sean

Similar Messages

Mail Service Keeps Stopping For No Reason

Hi There everyone. Over the past few days my Mail Service keeps stopping. Not giving any particular error, the only clue is this log message:-
Jan 6 13:12:39 server master[371]: exiting on SIGTERM/SIGINT
Is that helpful? I can start the service again and it seems OK... for a few hours then it stops again.
I have tried, reconstructing and repairing until I am blue in the face. Any other suggestions please? Thanks in advance.

I have just had the same thing happend again today with this in the log file:-
Jan 12 08:52:53 server imap[1413]: AOD: user options: no lookup required for: paul
Jan 12 08:52:53 server imap[1413]: login: localhost [::1] paul plaintext user logged in
Jan 12 08:52:53 server imap[1413]: quota set to "unlimited" for mailbox user.paul
Jan 12 08:52:53 server imap[1413]: open: user paul opened INBOX
Jan 12 08:52:53 server imap[1413]: accepted connection
Jan 12 08:52:53 server imap[1413]: AOD: user options: no lookup required for: paul
Jan 12 08:52:53 server imap[1413]: login: localhost [::1] paul plaintext user logged in
Jan 12 08:52:53 server imap[1413]: quota set to "unlimited" for mailbox user.paul
Jan 12 08:52:53 server imap[1413]: open: user paul opened INBOX
Jan 12 08:52:53: --- last message repeated 2 times ---
Jan 12 08:52:53 server imap[1413]: SQUAT failed to open index file
Jan 12 08:52:53 server imap[1413]: SQUAT failed
Jan 12 08:53:07 server master[367]: process 1399 exited, status 0
Jan 12 08:54:21 server master[367]: process 1413 exited, status 0
Jan 12 09:02:07 server master[51]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:02:07 server master[51]: process started
Jan 12 09:02:08 server master[177]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:02:12 server ctl_cyrusdb[177]: verifying cyrus databases
Jan 12 09:02:14 server ctl_cyrusdb[177]: skiplist: recovered /var/imap/mailboxes.db (15 records, 2784 bytes) in 2 seconds
Jan 12 09:02:16 server ctl_cyrusdb[177]: skiplist: recovered /var/imap/annotations.db (0 records, 144 bytes) in 2 seconds
Jan 12 09:02:28 server master[261]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:02:29 server master[261]: process started
Jan 12 09:02:29 server master[262]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:03:42 server master[335]: process started
Jan 12 09:03:42 server master[337]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:04:00 server ctl_cyrusdb[337]: DBERROR db4: unable to join the environment
Jan 12 09:04:15 server ctl_cyrusdb[337]: verifying cyrus databases
Jan 12 09:04:16 server ctl_cyrusdb[337]: skiplist: recovered /var/imap/mailboxes.db (15 records, 2784 bytes) in 1 second
Jan 12 09:04:16 server ctl_cyrusdb[337]: skiplist: recovered /var/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Jan 12 09:04:41 server master[352]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:04:41 server master[352]: process started
Jan 12 09:04:41 server master[354]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:04:51 server ctl_cyrusdb[354]: verifying cyrus databases
Jan 12 09:04:51 server ctl_cyrusdb[354]: skiplist: recovered /var/imap/mailboxes.db (15 records, 2784 bytes) in 0 seconds
Jan 12 09:04:52 server ctl_cyrusdb[354]: skiplist: recovered /var/imap/annotations.db (0 records, 144 bytes) in 1 second
Jan 12 09:05:17 server master[387]: process started
Jan 12 09:05:27 server master[447]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:05:27 server master[447]: process started
Jan 12 09:05:27 server master[448]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:05:41 server master[451]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:05:41 server master[451]: process started
Jan 12 09:05:41 server master[452]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:05:59 server ctl_cyrusdb[452]: DBERROR db4: unable to join the environment
Jan 12 09:06:01 server ctl_cyrusdb[452]: verifying cyrus databases
Jan 12 09:06:01 server ctl_cyrusdb[452]: skiplist: recovered /var/imap/mailboxes.db (15 records, 2784 bytes) in 0 seconds
Jan 12 09:06:02 server ctl_cyrusdb[452]: skiplist: recovered /var/imap/annotations.db (0 records, 144 bytes) in 1 second
Jan 12 09:06:21 server master[479]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:06:21 server master[479]: process started
Jan 12 09:06:21 server master[480]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:06:31 server master[481]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:06:42 server master[483]: getrlimit: max processes limit set to cur=2068 max=2068
Jan 12 09:06:43 server master[483]: process started
Jan 12 09:07:01 server ctl_cyrusdb[485]: DBERROR db4: unable to join the environment
Jan 12 09:07:02 server ctl_cyrusdb[485]: verifying cyrus databases
Jan 12 09:07:02 server ctl_cyrusdb[485]: skiplist: recovered /var/imap/mailboxes.db (15 records, 2784 bytes) in 0 seconds
Jan 12 09:07:02 server ctl_cyrusdb[485]: skiplist: recovered /var/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Jan 12 09:07:28 server ctl_cyrusdb[485]: done verifying cyrus databases
Jan 12 09:07:28 server master[497]: about to exec /usr/bin/cyrus/bin/idled
Jan 12 09:07:29 server master[483]: Cyrus POP/IMAP Server v2.3.8 ready for work
Jan 12 09:07:29 server master[499]: about to exec /usr/bin/cyrus/bin/ctl_cyrusdb
Jan 12 09:07:29 server ctl_cyrusdb[499]: checkpointing cyrus databases
Jan 12 09:07:29 server ctl_cyrusdb[499]: archiving database file: /var/imap/annotations.db
Jan 12 09:07:29 server ctl_cyrusdb[499]: archiving log file: /var/imap/db/log.0000000001
Jan 12 09:07:29 server ctl_cyrusdb[499]: archiving database file: /var/imap/mailboxes.db
Jan 12 09:07:29 server ctl_cyrusdb[499]: archiving log file: /var/imap/db/log.0000000001
Jan 12 09:07:29: --- last message repeated 1 time ---
Jan 12 09:07:29 server ctl_cyrusdb[499]: done checkpointing cyrus databases
Jan 12 09:07:29 server master[483]: process 499 exited, status 0
Jan 12 09:08:16 server master[512]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:16 server imap[512]: executed
Jan 12 09:08:16 server imap[512]: accepted connection
Jan 12 09:08:16 server master[513]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:16 server imap[513]: executed
Jan 12 09:08:16 server imap[513]: accepted connection
Jan 12 09:08:17 server imap[512]: login: [172.16.1.99] paul plaintext user logged in
Jan 12 09:08:17 server imap[512]: quota set to "unlimited" for mailbox user.paul
Jan 12 09:08:17 server master[514]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:17 server imap[513]: login: [172.16.1.99] florensis CRAM-MD5 User logged in
Jan 12 09:08:17 server imap[513]: quota set to "unlimited" for mailbox user.florensis
Jan 12 09:08:17 server master[515]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:17 server imap[515]: executed
Jan 12 09:08:17 server imap[515]: accepted connection
Jan 12 09:08:17 server master[516]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:17 server imap[516]: executed
Jan 12 09:08:17 server imap[516]: accepted connection
Jan 12 09:08:17 server imap[516]: login: [172.16.1.99] paul plaintext user logged in
Jan 12 09:08:17 server imap[516]: quota set to "unlimited" for mailbox user.paul
Jan 12 09:08:17 server imap[515]: login: [172.16.1.99] florensis CRAM-MD5 User logged in
Jan 12 09:08:17 server imap[515]: quota set to "unlimited" for mailbox user.florensis
Jan 12 09:08:17 server imap[516]: seen_db: user paul opened /var/imap/user/p/paul.seen
Jan 12 09:08:17 server imap[516]: open: user paul opened Junk
Jan 12 09:08:17 server imap[515]: skiplist: recovered /var/imap/user/f/florensis.seen (7 records, 14904 bytes) in 0 seconds
Jan 12 09:08:17 server imap[515]: seen_db: user florensis opened /var/imap/user/f/florensis.seen
Jan 12 09:08:17 server imap[516]: SQUAT failed to open index file
Jan 12 09:08:17 server imap[515]: open: user florensis opened INBOX
Jan 12 09:08:17 server imap[516]: SQUAT failed
Jan 12 09:08:18 server master[517]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:18 server imap[517]: executed
Jan 12 09:08:18 server imap[517]: accepted connection
Jan 12 09:08:18 server imap[517]: login: [172.16.1.99] florensis CRAM-MD5 User logged in
Jan 12 09:08:18 server imap[517]: quota set to "unlimited" for mailbox user.florensis
Jan 12 09:08:18 server master[518]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:18 server imap[518]: executed
Jan 12 09:08:18 server imap[519]: executed
Jan 12 09:08:18 server imap[518]: SQUAT failed to open index file
Jan 12 09:08:18 server imap[518]: SQUAT failed
Jan 12 09:08:18 server master[520]: about to exec /usr/bin/cyrus/bin/imapd
Jan 12 09:08:18 server imap[520]: executed
Jan 12 09:08:18 server imap[520]: accepted connection
Jan 12 09:08:19 server imap[516]: Expunged 7 messages from user.paul.Junk
Jan 12 09:08:19 server imap[520]: login: [172.16.1.99] florensis CRAM-MD5 User logged in
Jan 12 09:08:19 server imap[520]: quota set to "unlimited" for mailbox user.florensis
Jan 12 09:08:19 server imap[517]: seen_db: user florensis opened /var/imap/user/f/florensis.seen
Jan 12 09:08:19 server imap[517]: open: user florensis opened Junk
Jan 12 09:08:19 server imap[517]: SQUAT failed to open index file
Jan 12 09:08:19 server imap[517]: SQUAT failed
Jan 12 09:08:19 server imap[519]: seen_db: user florensis opened /var/imap/user/f/florensis.seen
Jan 12 09:08:19 server imap[519]: open: user florensis opened Apple Mail To Do
Jan 12 09:08:19 server imap[520]: seen_db: user florensis opened /var/imap/user/f/florensis.seen
Jan 12 09:08:19 server imap[520]: open: user florensis opened Deleted Messages
Jan 12 09:08:19 server imap[520]: SQUAT failed to open index file
Jan 12 09:08:19 server imap[520]: SQUAT failed
Jan 12 09:08:20 server imap[513]: accepted connection
Jan 12 09:08:20 server imap[513]: login: [172.16.1.99] paul plaintext user logged in
Jan 12 09:08:20 server imap[513]: quota set to "unlimited" for mailbox user.paul
Jan 12 09:08:20 server imap[514]: Expunged 1 messages from user.paul
Jan 12 09:08:20 server imap[513]: seen_db: user paul opened /var/imap/user/p/paul.seen
Jan 12 09:08:22 server imap[513]: open: user paul opened Apple Mail To Do
Jan 12 09:08:22 server imap[516]: open: user paul opened Sent Messages
Jan 12 09:08:22 server imap[515]: Expunged 1 messages from user.florensis
Jan 12 09:08:23 server imap[517]: open: user florensis opened Apple Mail To Do
Jan 12 09:08:23 server imap[518]: open: user paul opened Junk
Jan 12 09:08:24 server imap[518]: Expunged 1 messages from user.paul.Junk
Does this help? It then cleared itself??

AFter the latest download, my e-mail service keeps getting a bar at the top "Firefox prevented this page from automatically redirecting to another page". I have to keep hitting the "Allow" link? How do I get rid of this?

Ever since the last update, I'm having problem accessing my e-mail account. I keep getting an annoying bar at the top of the screen "Firebox prevented this page from automatically redirecting to another page." I have to keep hitting the allow button, sometimes twice. And when I do get into the accounts the bar jumps in and out every time I open a new e-mail, or delete and old one.
How do I get rid of this. I've had this account for years, with a very reputable private e-mail provider. This is nuts.

See:
*Firefox/Tools > Options > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"
The setting in "Tools > Options > Advanced > General" is meant as an accessibility feature, as you can see by the label of that section, so that people with disabilities or people who use screen readers do not get confused and is not meant as a safety protection to stop redirecting.
See also:
*https://support.mozilla.com/kb/Options+window+-+Advanced+panel#General_tab
*http://kb.mozillazine.org/accessibility.blockautorefresh
*http://kb.mozillazine.org/Accessibility_features_of_Firefox

Mail Services keeps shutting down

I have been plaque with this problem for about two months. I have 5 static ips and I use one of the ips to host a webserver and very small mail server. I am on DSL. My problem is my mail server always shuts down after a couple hours. The error is
127.0.0.1 port 25 is already in use.
I usually restart the server and everything is fine for a few hours and the mail is shut down.
I am using 10.4.5 OS X Server G4 1.4 GHZ Sawtooth.
this is my postconf -n:
always_bcc = [email protected]
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
html_directory = no
inet_interfaces = all
localrecipientmaps =
luser_relay = virus
mail_owner = postfix
mailspooldirectory = /var/mail
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,kents.mine.nu
mydomain = kents.mine.nu
mydomain_fallback = localhost
myhostname = mail.kents.mine.nu
mynetworks = 127.0.0.1/32,kents.mine.nu,mail.kents.mine.nu
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdpw_server_securityoptions = login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_keyfile =
smtpduse_pwserver = yes
unknownlocal_recipient_rejectcode = 550
I also checked to see if port 25 is being used some where else:
samuel$ netstat -atn | grep 25
tcp4 0 0 127.0.0.1.10025 . LISTEN
tcp4 0 0 *.25 . LISTEN
tcp4 0 0 *.625 . LISTEN
1f12660 stream 0 0 0 1f12550 0 0 /var/tmp/SCDynamicStoreNotifyFileDescriptor-21763
1f12550 stream 0 0 0 1f12660 0 0
1f126e8 dgram 0 0 0 1769330 0 1f125d8
1f125d8 dgram 0 0 0 1769330 0 1f12990
Thanx in advance for any help in this matter.
Mac OS X (10.4)

Apr 6 18:08:56 KentsServer postfix/smtpd[10770]: warning: connect #3 to subsystem public/cleanup: Connection refused
Apr 6 18:09:06 KentsServer postfix/smtpd[10771]: warning: connect #4 to subsystem public/cleanup: Connection refused
Apr 6 18:09:06 KentsServer postfix/smtpd[10770]: warning: connect #4 to subsystem public/cleanup: Connection refused
Apr 6 18:09:16 KentsServer postfix/smtpd[10771]: warning: connect #5 to subsystem public/cleanup: Connection refused
Apr 6 18:09:16 KentsServer postfix/smtpd[10770]: warning: connect #5 to subsystem public/cleanup: Connection refused
Apr 6 18:09:26 KentsServer postfix/smtpd[10771]: warning: connect #6 to subsystem public/cleanup: Connection refused
Apr 6 18:09:26 KentsServer postfix/smtpd[10770]: warning: connect #6 to subsystem public/cleanup: Connection refused
Apr 6 18:09:36 KentsServer postfix/smtpd[10771]: warning: connect #7 to subsystem public/cleanup: Connection refused
Apr 6 18:09:36 KentsServer postfix/smtpd[10770]: warning: connect #7 to subsystem public/cleanup: Connection refused
This what I get when the mail server shuts down. The previous post suggestion didn't work. Shuts down the mail server even quicker....seems like every 10 minutes the mail server shuts down.

Mail service appears to be corrupt

Mail service on my server appear to be corrupt. I had a crash about a week ago and periodic unresponsiveness of the server only occurs when mail services are enabled. The "Configure Mail service" button is appearing in the lower right hand corner now even though it is configured. I decided to repeat the process of configuring it using that button and all the processes attempt to start but mailing lists attempted and failed. That suggests there is something wrong. Should I try reconfiguring mail services from scratch. If so, how do I do it?

Things are still limping along. Digging into the log files, I find the following:
Here are some examples of error messages I see:
Jun 22 08:23:01 mini postfix/postfix-script[1442]: fatal: the Postfix mail system is not running
Jun 22 08:23:12 mini postfix/postfix-script[1486]: warning: damaged message: corrupt/1B1B3EA0C70
Jun 22 08:23:12 mini postfix/postfix-script[1487]: warning: damaged message: corrupt/1E360755445
Mailaccess.log
Jun 22 09:02:11 mini imaps[1564]: Fatal error: tlsstartservertls() failed
Jun 22 09:02:17 mini pop3s[1998]: Fatal error: tlsstartservertls() failed
I am considering doing a clean install of the entire server, but I do not want to do that unless I have to. Any help would be appreciated!

Mac Mail in 10.6.8 keeps corrupting

My mac mail keeps corrupting and I keep running my disk utilities to fix the preferences which helps for a day or so the back to weird stuff, where when typing characters jump around or it won't let me type at all, then can't send the message after battling through it. Had to shut off one of my mail boxes because it could connect to the server and would just keep spinning. Tried to reistall Snow Leopard and it helped for a couple of days then back to same old. Also rebuilt the boxes.
What should I do to get my mail functioning again?

Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
Any improvement?

Cannot edit text sufficiently within the Photo E-mail service (Elements 11)

Greetings to all, a little help required please....
Just purchased Elements 11 - excellent product at the price and am having a great deal of fun using it.
One frustrating flaw within the Photo E-mail service....
I've been using the Adobe e-mail service and it sends e-mail just fine having set up the account as required.
Each new e-mail appears with the text "Here are the files I want to share with you."
Now I'd like to replace that with some different text. I can delete it and replace it on the first editing page, and it stays there after I click 'Next' to the following 'Customise Layout' section.
Clicking on 'Next' after this page, we have the final e-mail page, and the text has reverted back to 'Here are the files I want to share with you' again......
I can delete it again, but cannot type in any further text anywhere on that screen.
Any help on this??
Shame, because the programme generally is superb. Have transformed a number of pics already, and it would be nice to use the e-mail prog that's built in as I'd like to use it, adding text as required. Otherwise, why have all the font and layout choices available if not??

I tried the same and its changing at my side.
Try to reset you preferences :
Open PSE just to the Welcome Screen and press Ctrl + Alt + Shift (Mac: Cmd + Opt + Shift) and keep pressing.
Click on organizer from the Welcome Screen but keep pressing the keyboard keys - don't let up.
You will get a little dialog box asking if you want to delete the settings file. Click "Yes." You can let go of the keyboard keys now.
This will rebuild the file for you and often solves the issue.
Try to send the email again.
Thanks
Harshit

Why does my Mac Mail programme keep turning on the SSL option?

For a couple of years now my wife's Mac Mail programme has from time to time stopped getting most of the emails sent to it for a week or more. I've wasted many hours on the phone to our service provider without ever getting to the bottom of the problem. Now I believe I know what's been happening. It seems that her Mail preferences keep turning on the SSL option without any human involvement. Apparently emails sent to an SSL selected email address will only make it into her in-box if they come from an SSL selected mail programme. Yesterday, scratching my head as to why, once again, few emails were getting through, I once again looked at the preferences and noticed that the SSL option, which I had recently unchecked, was once again checked. I unchecked it. It immediately re-checked itself. I unchecked it. It immediately re-checked itself. And so on, for ten minutes when, suddenly, it remained unchecked.
Why is this happening? My wife never, and I mean never fiddles with settings on her computer and nobody else uses it. The checking of the SSL option is being done entirely at the behest of the machine itself. Can anybody tell me how this could be happening? And could anybody tell me how I can stop it from happening again?

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Step 1 should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary, and if everything is working as expected after step 1.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Mail service unexpectedly down

Starting two days ago, my mail service stopped working. After checking the logs, I found this entry in the smtp log. This just keeps repeating every minute or so:
Feb 15 10:19:45 insanity postfix/master[7794]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
Feb 15 10:19:45 insanity postfix/master[7794]: warning: process /usr/libexec/postfix/trivial-rewrite pid 7904 exit status 1
Feb 15 10:19:45 insanity postfix/master[7794]: warning: /usr/libexec/postfix/trivial-rewrite: bad command startup -- throttling
Feb 15 10:19:45 insanity postfix/master[7794]: warning: process /usr/libexec/postfix/smtpd pid 7902 exit status 1
Feb 15 10:19:45 insanity postfix/master[7794]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
Feb 15 10:20:45 insanity postfix/trivial-rewrite[7920]: fatal: open database /etc/postfix/virtualvirus_quarantine.db: No such file or directory
Feb 15 10:20:45 insanity postfix/smtpd[7918]: fatal: open database /etc/postfix/virtualvirus_quarantine.db: No such file or directory
Feb 15 10:20:45 insanity postfix/cleanup[7919]: fatal: open database /etc/postfix/virtualvirus_quarantine.db: No such file or directory
Feb 15 10:20:46 insanity postfix/master[7794]: warning: process /usr/libexec/postfix/trivial-rewrite pid 7920 exit status 1
Feb 15 10:20:46 insanity postfix/master[7794]: warning: /usr/libexec/postfix/trivial-rewrite: bad command startup -- throttling
Feb 15 10:20:46 insanity postfix/master[7794]: warning: process /usr/libexec/postfix/smtpd pid 7918 exit status 1
Feb 15 10:20:46 insanity postfix/master[7794]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
Feb 15 10:20:46 insanity postfix/master[7794]: warning: process /usr/libexec/postfix/cleanup pid 7919 exit status 1
Feb 15 10:20:46 insanity postfix/master[7794]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
Any help will be greatly appreciated,
Lee

Hi,
I had something similar happen to me.
Mar 4 12:16:23 foxcroft postfix/master[56]: daemon started -- version 2.1.5
Mar 5 12:59:22 foxcroft postfix/smtpd[7889]: connect from nk219-91-64-208.adsl.dynamic.apol.com.tw[219.91.64.208]
Mar 5 12:59:29 foxcroft postfix/smtpd[7889]: fatal: net/mask pattern 67.79.179.210/29 has a non-null host portion; specify 67.79.179.208/29 if this is really what you want
Mar 5 12:59:30 foxcroft postfix/master[56]: warning: process /usr/libexec/postfix/smtpd pid 7889 exit status 1
Mar 5 12:59:30 foxcroft postfix/master[56]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
That's what I got as well - and I haven't got any new messages since. I've restarted and updated and turned SMTP on and off in Server Admin and restarted that service and... and.. and...
Here's the output of my postconf -n command:
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps =
luser_relay = sr
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydomain = fox5pharma.com
mydomain_fallback = localhost
myhostname = ns.fox5pharma.com
mynetworks = 127.0.0.1/32,67.79.179.210/29,172.16.2.1/24,192.168.1.100/24,65.33.104.163
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdpw_server_securityoptions = plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_keyfile =
smtpduse_pwserver = yes
unknownlocal_recipient_rejectcode = 550
Help! Please! I'm at my wit's end! haaaaalp!
PowerBook G4 Mac OS X (10.4.4)

Mail service stuck starting in Mavericks

After installing Mavericks server I've got a problem with the mailserver. In the Server.app it keeps showing as starting, but it never starts.
the terminal command 'serveradmin fullstatus mail' shows that everything is started as it should, except the Mail Transfer Agent. It shows the error Warning: SMTP mail service is enabled but not running.
The command 'serveradmin start mailtransferagent' results in the error "CANNOT_LOAD_BUNDLE_ERR"
Console shows no helpfull messages except the obscure "serveradmin: posting dist not" right after entering the 'serveradmin start mailtransferagent' command.
Any idea how I can get the mail service to start?

It's sort of an upgraded system. The Mavericks installation is actually a fresh one, but data was then restored with TimeMachine from a previous 10.6 system. So old configs are a possibility.
Belowe is all that showed in the log. Besides some (IMHO) non critical permission warnings, there is nothing. The mailaccess.log was actually empty.
Mail.log:
postfix/postfix-script[67467]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./custom_header_checks
postfix/postfix-script[67468]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.default
postfix/postfix-script[67469]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.orig
postfix/postfix-script[67470]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual.db
postfix/postfix-script[67471]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual_domains
postfix/postfix-script[67472]: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual_users
System.log:
mds[63]: (/)(Warning) IndexQuery in virtual bool SISearchCtx_FSI::performSearch(struct PartialQueryResults *):Retried searchfs 4 times
mds[63]: (/)(Warning) IndexQuery in virtual bool SISearchCtx_FSI::performSearch(struct PartialQueryResults *):Throttling slow file system query
xpcd[916]: restored permissions (100600 -> 100700) on /private/var/root/Library/Containers/com.apple.TextEdit/Container.plist
WindowServer[107]: disable_update_timeout: UI updates were forcibly disabled by application "TextEdit" for over 1.00 seconds. Server has re-enabled them.
com.apple.appkit.xpc.openAndSavePanelService[68212]: Bogus event received by listener connection:
<error: 0x7fff7af06b50> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7af06e60> { length = 18, contents = "Connection invalid" }
quicklookd[68202]: generateImageInProcess Failed to composit image for binding VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: pps, UTI: com.microsoft.powerpoint.pps, fileType: ????.
quicklookd[68202]: generateImageInProcess Failed to composit image for binding VariantBinding [0x403] flags: 0x8 binding: FileInfoBinding [0x303] - extension: GIF, UTI: com.compuserve.gif, fileType: ????.
WindowServer[107]: common_reenable_update: UI updates were finally reenabled by application "TextEdit" after 5.36 seconds (server forcibly re-enabled them after 1.00 seconds)
quicklookd[68202]: generateImageInProcess Failed to composit image for binding VariantBinding [0x603] flags: 0x8 binding: FileInfoBinding [0x503] - extension: gif, UTI: com.compuserve.gif, fileType: ????.
quicklookd[68202]: generateImageInProcess Failed to composit image for binding VariantBinding [0x803] flags: 0x8 binding: FileInfoBinding [0x703] - extension: tiff, UTI: public.tiff, fileType: ????.
quicklookd[68202]: generateImageInProcess Failed to composit image for binding VariantBinding [0xa03] flags: 0x8 binding: FileInfoBinding [0x903] - extension: gif, UTI: com.compuserve.gif, fileType: ????.
kernel[0]: Sandbox: xcscredd(164) deny file-read-metadata /private/var/root
--- last message repeated 11 times ---
birds-srv-03.local sandboxd[191] ([164]): xcscredd(164) deny file-read-metadata /private/var/root
--- last message repeated 7 times ---

Logger Service keeps shutting down and restarting

Hello,
I have upgraded my lab UCCE call center to v9.0
I have a simplexed environment
Ever since, the logger service keeps shutting down and restarting.
Recently, the node manager issued an error message and shut down the server
I tried to check some logs but I point out the problem, there are errors in different processes.
Attached are the logs.

Hi,
if the NM tries to reload the server, it indicates a Problem (capital inteded).
Indeed, there's something interesting going on:
08:29:11:822 la-rpl Trace: Starting Recovery Key for Admin table is 6717118506000.0
08:29:11:822 la-rpl Trace: The largestkey = 7201232308043.0 >= startkey = 6717118506000.0
08:29:11:823 la-rpl Trace: To correct this problem: Stop logger service. Use ICMDBA tool to sync configuration data from its partner logger database. Restart logger service.
08:29:11:823 la-rpl Fail: Assertion failed: largestkey < startkey. File: ICRDB.CPP. Line 742
08:29:11:860 la-rpl Trace: CExceptionHandlerEx::GenerateMiniDump -- A Mini Dump File is available at logfiles\replication.exe_20130523082911824.mdmp
08:29:12:074 la-rpl Unhandled Exception: Exception code: 80000003 BREAKPOINTFault address: 754A3219 01:00012219 C:\Windows\syswow64\KERNELBASE.dllRegisters:EAX:00000000EBX:00000000ECX:00001890EDX:E1043F00ESI:015F8AB0EDI:00000005CS:EIP:0023:754A3219SS:ESP:002B:003CE2D8 EBP:003CE2E0DS:002B ES:002B FS:0053 GS:002BFlags:00000246Call stack:Address Frame754A3219 003CE2E0 DebugBreak+26EB1459C 003CE2EC EMSAbortProcess+C6EB1ACD1 003CF7F8 EMSReportCommon+1A16EB1ADBB 003CF818 EMSFailMessage+2B013BBE5A 003CF8A8 ICRDb::ICRDb+44A013B2FE2 003CF9B8 main+582015D96C2 003CF9FC NtCurrentTeb+174767333AA 003CFA08 BaseThreadInitThunk+1277449EF2 003CFA48 RtlInitializeExceptionChain+6377449EC5 003CFA60 RtlInitializeExceptionChain+36
The short version: configuration data is corrupt.
The longer version: the above message in red informs about the result of a sanity check. Each configuration change creates a new row in one of the tables holding the config info, and each row contains a RecoveryKey which is usually a large number incremented by the insertion. The error message says the largest key (= last key) contains a value that is lower than the first key. Naturally, this is something to consider for a lonely philosopher, but the rigid world of Cisco ICM does not allow metaphysical phenomena. Lower numbers are supposed to be lower than higher numbers.
This, of course, raises an exception and the Logger service restarts. If there are too many restarts, the Node Manager kicks in and restarts the machine - this is just a mechanism that prevents a larger extent of data corruption.
Now, if there's an other side Logger - fine, as the error message suggests, you can initiate manual replication (provided the other Logger database contains valid information).
Unfortunately, as you have written, this is a side A only environment. This may mean:
- accepting the situation, stopping ICM, throwing out the logger database, recreating it and reinstalling the Logger service,
- poking around in various tables to check what may be saved - this may mean the beginning of an adventure.
G.

Mail Service

Dear All, I am migrating from Exchange server to our new Xserve.
There is a mailbox in exchange that we used to catch all the incoming and outgoing mail of the whole organization. Where we can keep archiving all mail in and out, the department managers can logon as IMAP to view all the emails.
Is there a way I can do this with the mail service on my Xserve? Any help will be greatly appreciate and thank you in advance.
JM

Both, the E-mail client and that Social-media client were proxy services handled by a server at Nokia. Those services got turned-off in November. Which E-mail provider(s) do you want to use? Which Social-media service(s) do you want to use? Then, we are able to give step-by-step guides how to use them today, without changing your phone.

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.

Mail settings keep disappearing

Randomly, the 'view' mail settings keep disappearing. I'll set them to show date recieved, date sent, etc etc and once or twice a day, Mail will revert to having no settings and I have to reset.
Not serious, just annoying
Thanks
Bruce Black

Your Preferences file could be corrupted. Try quitting Mail and go to Users/Library/Preferences and look for the com.apple.mail.plist file; drag it to your Desktop. Now relaunch Mail and set those parameters again, then quit Mail.
Relaunch Mail and see if your parameters stayed this time. If they do, then you can Trash the old preferences file on your Dekstop.
Mulder
If any of my answers helped solve your problem, please consider awarding some points. Why Reward Points?
iMac G4 700Mhz Mac OS X (10.3.9)

Ddns mail service

I am using a Mac mini server (Mountain Lion) and want to use it as web server and mail server with server.app.
I also have my own domain name of 'scheduler.co.kr'.
Mac mini server is connect to internet via the router's port forwarding of 80, 25...etc.
Mac mini server IP is private like 192.168.0.x.
The router's IP is dynamic not static.
So I registered to the DDNS (dynamic domain name service) provider and I can configure the records of A, CNAME, MX and etc in it.
My problem is I can not use 'Mac mini server's mail service'.
The web service is good through wordpress and MySQL.
But mail service is not.
My question is followed;
1) Should I make DNS configuration in the MAc mini server using server.app?
2) In the case of router's dynamic IP environment, can I configure a mail service of sending and receiving using Mac mini server?
If it is possible, how can I configure my mac mini server in DNS and Mail service feature?
3) Should I use mac mini server With DDNS service of outside provider?
Or can I configure all services of mac mini server.app without DDNS service?
I want to receive the reply from the experienced or Expert.
All the best.

Things are still limping along. Digging into the log files, I find the following:
Here are some examples of error messages I see:
Jun 22 08:23:01 mini postfix/postfix-script[1442]: fatal: the Postfix mail system is not running
Jun 22 08:23:12 mini postfix/postfix-script[1486]: warning: damaged message: corrupt/1B1B3EA0C70
Jun 22 08:23:12 mini postfix/postfix-script[1487]: warning: damaged message: corrupt/1E360755445
Mailaccess.log
Jun 22 09:02:11 mini imaps[1564]: Fatal error: tlsstartservertls() failed
Jun 22 09:02:17 mini pop3s[1998]: Fatal error: tlsstartservertls() failed
I am considering doing a clean install of the entire server, but I do not want to do that unless I have to. Any help would be appreciated!

Mail service keeps corrupting.

Similar Messages

Maybe you are looking for