Hanging cyrus process stopps mail service
Yesterday it happened the second time that a cyrus process hanged. I couldn't kill and even shutting down the server did not succeed (because it couldn't kill the hanging process I think). So I had to switch off the server with all those ugly side effekts (databases corrupted).
Is there anyone here who had simular problems?
The first time it happened it was a process that tried to delete a large mail. Why it hanged I could not see. The second time I have no idea.
Has someone an idea how to kill a process that ignores kill -9 ? And how to reboot without getting problems with the other services? I am used to kill them first by hand and then pulling the plug, but launchd respawns them so fast that e.g. slapd ist running again before I could reach to the plug.
I hope there are some BSD cracks around for help.
Stefan
Log entries for that time frame would help.
Similar Messages
-
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,
LeeHi,
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 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?? -
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 abnormallyThanks 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. -
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 Services connection times out after 10.5.8 - 10.6.4 upgrade
I have been running a mail server on my macosxserver02.binghamton.edu (128.226.xx.x) for Podcast Producer email notifications only. The mail service has been running fine until I recently upgraded the server to Apple's latest server software: Snow Leopard Server (10.6.4).
After the upgrade I'm no longer able to receive mail to the mail server from outside it's domain (macosxserver02.binghamton.edu). I can send and receive mail locally from within that domain. I can send mail outside of the domain without any trouble to my personal email account [email protected], but not my work account: [email protected]. If I try to send from outside the domain -- say with my Binghamton Univ account -- the mail bounces back with this message:
Delivery to the following recipient has been delayed:
[email protected]
Message will be retried for 2 more day(s)
Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720
[macosxserver02.binghamton.edu (1): Connection timed out]
---- Original message -----
Received: by 10.224.102.202 with SMTP id h10mr6012071qao.49.1277903965341;
Wed, 30 Jun 2010 06:19:25 -0700 (PDT)
Return-Path: <[email protected]>
Received: from [128.226.62.7] ([128.226.62.7])
by mx.google.com with ESMTPS id v20sm41975621qce.46.2010.06.30.06.19.24
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 30 Jun 2010 06:19:24 -0700 (PDT)
From: Cheryl Tarbox <[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: another attempt
Date: Wed, 30 Jun 2010 09:19:22 -0400
Message-Id: <[email protected]>
To: [email protected],
[email protected]
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
One thing to note about the .binghamton.edu domain is that we recently switched to Google Mail and .binghamton.edu is our branded domain within google.com.
DNS is managed on another server. I had an MX record added to my server this morning.
I have these ports open on my firewall: 143, 993, 25, 587 (POP is not enabled)
In ServerAdmin>Mail>Settings>Relay 'Accept SMTP relays only from these hosts and networks' is checked with
127.0.0.0/8
128.226.62.0/26 (my local subnet)
In ServerAdmin>Mail>Settings>Filters Junk Mail and Virus filtering is not enabled, so greylisting should not be a problem. I did confirm this line in main.cf: smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reje ct_unauth_destination permit
10MB quota is set, Mailing Lists not enabled, Logging set at Information
In ServerAdmin>Mail>Settings>Advanced>Security I am not using SSL. I do have a valid certificate that I would like to use after I get this back up and running.
In ServerAdmin>Mail>Settings>Hosting 'Include server's domain as local host alias' is checked with
localhost
binghamton.edu
Virtual hosting is not enabled.
Here is the output of: postconf -n:
macosxserver02:~ academic$ postconf -n
2bounce_notice_recipient = postmaster
access_map_reject_code = 554
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map =
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_poll_count = 3
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = $double_bounce_sender
address_verify_sender_dependent_relayhost_maps = $sender_dependent_relayhost_maps
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
allow_mail_to_commands = alias, forward
allow_mail_to_files = alias, forward
always_bcc =
anvil_rate_time_unit = 60s
anvil_status_update_time = 600s
application_event_drain_time = 100s
authorized_flush_users = static:anyone
authorized_mailq_users = static:anyone
authorized_submit_users = static:anyone
backwards_bounce_logfile_compatibility = yes
berkeley_db_create_buffer_size = 16777216
berkeley_db_read_buffer_size = 131072
best_mx_transport =
body_checks_size_limit = 51200
bounce_notice_recipient = postmaster
bounce_queue_lifetime = 5d
bounce_service_name = bounce
bounce_size_limit = 50000
bounce_template_file =
canonical_classes = envelope_sender, envelope_recipient, header_sender, header_recipient
check_for_od_forward = yes
cleanup_service_name = cleanup
command_directory = /usr/sbin
command_execution_directory =
command_expansion_filter = 1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
command_time_limit = 1000s
config_directory = /etc/postfix
connection_cache_protocol_timeout = 5s
connection_cache_service_name = scache
connection_cache_status_update_time = 600s
connection_cache_ttl_limit = 2s
content_filter =
cyrus_sasl_config_path =
daemon_directory = /usr/libexec/postfix
daemon_timeout = 18000s
data_directory = /var/lib/postfix
debug_peer_level = 2
debug_peer_list =
default_database_type = hash
default_delivery_slot_cost = 5
default_delivery_slot_discount = 50
default_delivery_slot_loan = 3
default_destination_concurrency_failed_cohort_limit = 1
default_destination_concurrency_limit = 20
default_destination_concurrency_negative_feedback = 1
default_destination_concurrency_positive_feedback = 1
default_destination_rate_delay = 0s
default_destination_recipient_limit = 50
default_extra_recipient_limit = 1000
default_minimum_delivery_slots = 3
default_privs = nobody
default_process_limit = 100
default_rbl_reply = $rbl_code Service unavailable; $rbl_class [$rbl_what] blocked using $rbl_domain${rbl_reason?; $rbl_reason}
default_recipient_limit = 20000
default_recipient_refill_delay = 5s
default_recipient_refill_limit = 100
default_transport = smtp
default_verp_delimiters = +=
defer_code = 450
defer_service_name = defer
defer_transports =
delay_logging_resolution_limit = 2
delay_notice_recipient = postmaster
delay_warning_time = 0h
deliver_lock_attempts = 20
deliver_lock_delay = 1s
destination_concurrency_feedback_debug = no
detect_8bit_encoding_header = yes
dont_remove = 0
double_bounce_sender = double-bounce
duplicate_filter_limit = 1000
empty_address_recipient = MAILER-DAEMON
empty_address_relayhost_maps_lookup_key =
enable_original_recipient = yes
enable_server_options = yes
error_notice_recipient = postmaster
error_service_name = error
execution_directory_expansion_filter = 1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
export_environment = TZ MAIL_CONFIG LANG
fallback_transport =
fallback_transport_maps =
fast_flush_domains = $relay_domains
fast_flush_purge_time = 7d
fast_flush_refresh_time = 12h
fault_injection_code = 0
flush_service_name = flush
fork_attempts = 5
fork_delay = 1s
forward_expansion_filter = 1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
forward_path = $home/.forward${recipient_delimiter}${extension}, $home/.forward
frozen_delivered_to = yes
hash_queue_depth = 1
hash_queue_names = deferred,defer
header_address_token_limit = 10240
header_checks =
header_size_limit = 102400
hopcount_limit = 50
html_directory = no
import_environment = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY DISPLAY LANG=C
in_flow_delay = 1s
inet_interfaces = all
inet_protocols = ipv4
initial_destination_concurrency = 5
internal_mail_filter_classes =
invalid_hostname_reject_code = 501
ipc_idle = 5s
ipc_timeout = 3600s
ipc_ttl = 1000s
line_length_limit = 2048
lmtp_bind_address =
lmtp_bind_address6 =
lmtp_body_checks =
lmtp_cname_overrides_servername = no
lmtp_connect_timeout = 0s
lmtp_connection_cache_destinations =
lmtp_connection_cache_on_demand = yes
lmtp_connection_cache_time_limit = 2s
lmtp_connection_reuse_time_limit = 300s
lmtp_data_done_timeout = 600s
lmtp_data_init_timeout = 120s
lmtp_data_xfer_timeout = 180s
lmtp_defer_if_no_mx_address_found = no
lmtp_destination_concurrency_failed_cohort_limit = $default_destination_concurrency_failed_cohort_limit
lmtp_destination_concurrency_limit = $default_destination_concurrency_limit
lmtp_destination_concurrency_negative_feedback = $default_destination_concurrency_negative_feedback
lmtp_destination_concurrency_positive_feedback = $default_destination_concurrency_positive_feedback
lmtp_destination_rate_delay = $default_destination_rate_delay
lmtp_destination_recipient_limit = $default_destination_recipient_limit
lmtp_discard_lhlo_keyword_address_maps =
lmtp_discard_lhlo_keywords =
lmtp_enforce_tls = no
lmtp_generic_maps =
lmtp_header_checks =
lmtp_host_lookup = dns
lmtp_initial_destination_concurrency = $initial_destination_concurrency
lmtp_lhlo_name = $myhostname
lmtp_lhlo_timeout = 300s
lmtp_line_length_limit = 990
lmtp_mail_timeout = 300s
lmtp_mime_header_checks =
lmtp_mx_address_limit = 5
lmtp_mx_session_limit = 2
lmtp_nested_header_checks =
lmtp_pix_workaround_delay_time = 10s
lmtp_pix_workaround_maps =
lmtp_pix_workaround_threshold_time = 500s
lmtp_pix_workarounds = disable_esmtp,delay_dotcrlf
lmtp_quit_timeout = 300s
lmtp_quote_rfc821_envelope = yes
lmtp_randomize_addresses = yes
lmtp_rcpt_timeout = 300s
lmtp_rset_timeout = 20s
lmtp_sasl_auth_cache_name =
lmtp_sasl_auth_cache_time = 90d
lmtp_sasl_auth_soft_bounce = yes
lmtp_sasl_mechanism_filter =
lmtp_sasl_path =
lmtp_sasl_security_options = noplaintext, noanonymous
lmtp_sasl_tls_security_options = $lmtp_sasl_security_options
lmtp_sasl_tls_verified_security_options = $lmtp_sasl_tls_security_options
lmtp_sasl_type = cyrus
lmtp_send_xforward_command = no
lmtp_sender_dependent_authentication = no
lmtp_skip_5xx_greeting = yes
lmtp_starttls_timeout = 300s
lmtp_tcp_port = 24
lmtp_tls_CAfile =
lmtp_tls_CApath =
lmtp_tls_cert_file =
lmtp_tls_dcert_file =
lmtp_tls_dkey_file = $lmtp_tls_dcert_file
lmtp_tls_enforce_peername = yes
lmtp_tls_exclude_ciphers =
lmtp_tls_fingerprint_cert_match =
lmtp_tls_fingerprint_digest = md5
lmtp_tls_key_file = $lmtp_tls_cert_file
lmtp_tls_loglevel = 0
lmtp_tls_mandatory_ciphers = medium
lmtp_tls_mandatory_exclude_ciphers =
lmtp_tls_mandatory_protocols = SSLv3, TLSv1
lmtp_tls_note_starttls_offer = no
lmtp_tls_per_site =
lmtp_tls_policy_maps =
lmtp_tls_scert_verifydepth = 9
lmtp_tls_secure_cert_match = nexthop
lmtp_tls_security_level =
lmtp_tls_session_cache_database =
lmtp_tls_session_cache_timeout = 3600s
lmtp_tls_verify_cert_match = hostname
lmtp_use_tls = no
lmtp_xforward_timeout = 300s
local_command_shell =
local_destination_concurrency_failed_cohort_limit = $default_destination_concurrency_failed_cohort_limit
local_destination_concurrency_limit = 2
local_destination_concurrency_negative_feedback = $default_destination_concurrency_negative_feedback
local_destination_concurrency_positive_feedback = $default_destination_concurrency_positive_feedback
local_destination_rate_delay = $default_destination_rate_delay
local_destination_recipient_limit = 1
local_header_rewrite_clients = permit_inet_interfaces
local_initial_destination_concurrency = $initial_destination_concurrency
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
local_transport = local:$myhostname
luser_relay = pcastadmin
mail_name = Postfix
mail_owner = _postfix
mail_release_date = 20080902
mail_spool_directory = /var/mail
mail_version = 2.5.5
mailbox_command =
mailbox_command_maps =
mailbox_delivery_lock = flock, dotlock
mailbox_size_limit = 0
mailbox_transport = dovecot
mailbox_transport_maps =
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maps_rbl_domains =
maps_rbl_reject_code = 554
masquerade_classes = envelope_sender, header_sender, header_recipient
masquerade_domains =
masquerade_exceptions =
max_idle = 100s
max_use = 100
maximal_backoff_time = 4000s
maximal_queue_lifetime = 5d
message_reject_characters =
message_size_limit = 10485760
message_strip_characters =
milter_command_timeout = 30s
milter_connect_macros = j {daemon_name} v
milter_connect_timeout = 30s
milter_content_timeout = 300s
milter_data_macros = i
milter_default_action = tempfail
milter_end_of_data_macros = i
milter_end_of_header_macros = i
milter_helo_macros = {tls_version} {cipher} {cipher_bits} {cert_subject} {cert_issuer}
milter_macro_daemon_name = $myhostname
milter_macro_v = $mail_name $mail_version
milter_mail_macros = i {auth_type} {auth_authen} {auth_author} {mail_addr}
milter_protocol = 2
milter_rcpt_macros = i {rcpt_addr}
milter_unknown_command_macros =
mime_boundary_length_limit = 2048
mime_header_checks = $header_checks
mime_nesting_limit = 100
minimal_backoff_time = 300s
multi_recipient_bounce_reject_code = 550
mydestination = $myhostname, localhost.$mydomain, localhost, binghamton.edu, $mydomain
mydomain = binghamton.edu
mydomain_fallback = localhost
myhostname = macosxserver02.binghamton.edu
mynetworks = 127.0.0.0/8,128.226.62.0/26
mynetworks_style = subnet
myorigin = $myhostname
nested_header_checks = $header_checks
newaliases_path = /usr/bin/newaliases
non_fqdn_reject_code = 504
non_smtpd_milters =
notify_classes = resource, software
parent_domain_matches_subdomains = debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_a uthorized_clients,relay_domains,smtpd_access_maps
permit_mx_backup_networks =
pickup_service_name = pickup
plaintext_reject_code = 450
prepend_delivered_header = command, file, forward
process_id_directory = pid
propagate_unmatched_extensions = canonical, virtual
proxy_interfaces =
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps
proxy_write_maps = $smtp_sasl_auth_cache_name $lmtp_sasl_auth_cache_name
qmgr_clog_warn_time = 300s
qmgr_fudge_factor = 100
qmgr_message_active_limit = 20000
qmgr_message_recipient_limit = 20000
qmgr_message_recipient_minimum = 10
qmqpd_authorized_clients =
qmqpd_client_port_logging = no
qmqpd_error_delay = 1s
qmqpd_timeout = 300s
queue_directory = /private/var/spool/postfix
queue_file_attribute_count_limit = 100
queue_minfree = 0
queue_run_delay = 300s
queue_service_name = qmgr
rbl_reply_maps =
readme_directory = /usr/share/doc/postfix
receive_override_options =
recipient_bcc_maps =
recipient_canonical_classes = envelope_recipient, header_recipient
reject_code = 554
relay_clientcerts =
relay_destination_concurrency_failed_cohort_limit = $default_destination_concurrency_failed_cohort_limit
relay_destination_concurrency_limit = $default_destination_concurrency_limit
relay_destination_concurrency_negative_feedback = $default_destination_concurrency_negative_feedback
relay_destination_concurrency_positive_feedback = $default_destination_concurrency_positive_feedback
relay_destination_rate_delay = $default_destination_rate_delay
relay_destination_recipient_limit = $default_destination_recipient_limit
relay_domains = $mydestination
relay_domains_reject_code = 554
relay_initial_destination_concurrency = $initial_destination_concurrency
relay_recipient_maps =
relay_transport = relay
relayhost =
relocated_maps =
remote_header_rewrite_domain =
resolve_null_domain = no
resolve_numeric_domain = no
rewrite_service_name = rewrite
sample_directory = /usr/share/doc/postfix/examples
send_cyrus_sasl_authzid = no
sender_bcc_maps =
sender_canonical_classes = envelope_sender, header_sender
sender_canonical_maps =
sender_dependent_relayhost_maps =
sendmail_path = /usr/sbin/sendmail
service_throttle_time = 60s
setgid_group = _postdrop
showq_service_name = showq
smtp_bind_address6 =
smtp_body_checks =
smtp_cname_overrides_servername = no
smtp_connect_timeout = 30s
smtp_connection_cache_destinations =
smtp_connection_cache_on_demand = yes
smtp_connection_cache_time_limit = 2s
smtp_connection_reuse_time_limit = 300s
smtp_data_done_timeout = 600s
smtp_data_init_timeout = 120s
smtp_data_xfer_timeout = 180s
smtp_defer_if_no_mx_address_found = no
smtp_destination_concurrency_failed_cohort_limit = $default_destination_concurrency_failed_cohort_limit
smtp_destination_concurrency_limit = $default_destination_concurrency_limit
smtp_destination_concurrency_negative_feedback = $default_destination_concurrency_negative_feedback
smtp_destination_concurrency_positive_feedback = $default_destination_concurrency_positive_feedback
smtp_destination_rate_delay = $default_destination_rate_delay
smtp_destination_recipient_limit = $default_destination_recipient_limit
smtp_discard_ehlo_keyword_address_maps =
smtp_discard_ehlo_keywords =
smtp_enforce_tls = no
smtp_fallback_relay = $fallback_relay
smtp_generic_maps =
smtp_header_checks =
smtp_helo_name = $myhostname
smtp_helo_timeout = 300s
smtp_host_lookup = dns
smtp_initial_destination_concurrency = $initial_destination_concurrency
smtp_line_length_limit = 990
smtp_mail_timeout = 300s
smtp_mime_header_checks =
smtp_mx_address_limit = 5
smtp_mx_session_limit = 2
smtp_nested_header_checks =
smtp_pix_workaround_delay_time = 10s
smtp_pix_workaround_maps =
smtp_pix_workaround_threshold_time = 500s
smtp_pix_workarounds = disable_esmtp,delay_dotcrlf
smtp_quit_timeout = 300s
smtp_quote_rfc821_envelope = yes
smtp_rcpt_timeout = 300s
smtp_rset_timeout = 20s
smtp_sasl_auth_cache_name =
smtp_sasl_auth_cache_time = 90d
smtp_sasl_auth_soft_bounce = yes
smtp_sasl_mechanism_filter =
smtp_sasl_password_maps =
smtp_sasl_path =
smtp_sasl_security_options = noplaintext, noanonymous
smtp_sasl_tls_security_options = $smtp_sasl_security_options
smtp_sasl_tls_verified_security_options = $smtp_sasl_tls_security_options
smtp_sasl_type = cyrus
smtp_send_xforward_command = no
smtp_sender_dependent_authentication = no
smtp_starttls_timeout = 300s
smtp_tls_CAfile =
smtp_tls_CApath =
smtp_tls_cert_file =
smtp_tls_dcert_file =
smtp_tls_dkey_file = $smtp_tls_dcert_file
smtp_tls_enforce_peername = yes
smtp_tls_exclude_ciphers =
smtp_tls_fingerprint_cert_match =
smtp_tls_fingerprint_digest = md5
smtp_tls_key_file = $smtp_tls_cert_file
smtp_tls_loglevel = 0
smtp_tls_mandatory_ciphers = medium
smtp_tls_mandatory_exclude_ciphers =
smtp_tls_mandatory_protocols = SSLv3, TLSv1
smtp_tls_note_starttls_offer = no
smtp_tls_per_site =
smtp_tls_policy_maps =
smtp_tls_scert_verifydepth = 9
smtp_tls_secure_cert_match = nexthop, dot-nexthop
smtp_tls_security_level =
smtp_tls_session_cache_database =
smtp_tls_session_cache_timeout = 3600s
smtp_tls_verify_cert_match = hostname
smtp_use_tls = no
smtp_xforward_timeout = 300s
smtpd_authorized_verp_clients = $authorized_verp_clients
smtpd_authorized_xclient_hosts =
smtpd_authorized_xforward_hosts =
smtpd_banner = $myhostname ESMTP $mail_name
smtpd_client_connection_count_limit = 50
smtpd_client_connection_rate_limit = 0
smtpd_client_event_limit_exceptions = ${smtpd_client_connection_limit_exceptions:$mynetworks}
smtpd_client_message_rate_limit = 0
smtpd_client_new_tls_session_rate_limit = 0
smtpd_client_port_logging = no
smtpd_client_recipient_rate_limit = 0
smtpd_client_restrictions =
smtpd_data_restrictions =
smtpd_delay_open_until_valid_rcpt = yes
smtpd_discard_ehlo_keyword_address_maps =
smtpd_discard_ehlo_keywords =
smtpd_end_of_data_restrictions =
smtpd_enforce_tls = no
smtpd_error_sleep_time = 1s
smtpd_etrn_restrictions =
smtpd_expansion_filter = \t\40!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghi jklmnopqrstuvwxyz{|}~
smtpd_forbidden_commands = CONNECT GET POST
smtpd_hard_error_limit = 20
smtpd_helo_required = no
smtpd_helo_restrictions =
smtpd_history_flush_threshold = 100
smtpd_junk_command_limit = 100
smtpd_milters =
smtpd_noop_commands =
smtpd_null_access_lookup_key =
smtpd_peername_lookup = yes
smtpd_policy_service_max_idle = 300s
smtpd_policy_service_max_ttl = 1000s
smtpd_policy_service_timeout = 100s
smtpd_proxy_ehlo = $myhostname
smtpd_proxy_filter =
smtpd_proxy_timeout = 100s
smtpd_pw_server_security_options = login,plain
smtpd_recipient_limit = 1000
smtpd_recipient_overshoot_limit = 1000
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination permit
smtpd_reject_unlisted_recipient = yes
smtpd_reject_unlisted_sender = no
smtpd_restriction_classes =
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = no
smtpd_sasl_exceptions_networks =
smtpd_sasl_path = smtpd
smtpd_sasl_security_options = noanonymous
smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
smtpd_sasl_type = cyrus
smtpd_sender_login_maps =
smtpd_sender_restrictions =
smtpd_soft_error_limit = 10
smtpd_starttls_timeout = 300s
smtpd_timeout = 300s
smtpd_tls_CAfile = /etc/certificates/*.binghamton.edu.1C15A00CCD190A0295A8587B951BA187BFD560ED.cha in.pem
smtpd_tls_CApath =
smtpd_tls_always_issue_session_ids = yes
smtpd_tls_ask_ccert = no
smtpd_tls_auth_only = no
smtpd_tls_ccert_verifydepth = 9
smtpd_tls_cert_file = /etc/certificates/*.binghamton.edu.1C15A00CCD190A0295A8587B951BA187BFD560ED.cer t.pem
smtpd_tls_dcert_file =
smtpd_tls_dh1024_param_file =
smtpd_tls_dh512_param_file =
smtpd_tls_dkey_file = $smtpd_tls_dcert_file
smtpd_tls_exclude_ciphers =
smtpd_tls_fingerprint_digest = md5
smtpd_tls_key_file = /etc/certificates/*.binghamton.edu.1C15A00CCD190A0295A8587B951BA187BFD560ED.key .pem
smtpd_tls_loglevel = 0
smtpd_tls_mandatory_ciphers = medium
smtpd_tls_mandatory_exclude_ciphers =
smtpd_tls_mandatory_protocols = SSLv3, TLSv1
smtpd_tls_received_header = no
smtpd_tls_req_ccert = no
smtpd_tls_security_level =
smtpd_tls_session_cache_database =
smtpd_tls_session_cache_timeout = 3600s
smtpd_tls_wrappermode = no
smtpd_use_pw_server = yes
smtpd_use_tls = no
stale_lock_time = 500s
stress =
strict_mailbox_ownership = yes
syslog_facility = mail
syslog_name = postfix
tls_daemon_random_bytes = 32
tls_export_cipherlist = ALL:+RC4:@STRENGTH
tls_high_cipherlist = ALL:!EXPORT:!LOW:!MEDIUM:+RC4:@STRENGTH
tls_low_cipherlist = ALL:!EXPORT:+RC4:@STRENGTH
tls_medium_cipherlist = ALL:!EXPORT:!LOW:+RC4:@STRENGTH
tls_null_cipherlist = eNULL:!aNULL
tls_random_bytes = 32
tls_random_exchange_name = ${data_directory}/prng_exch
tls_random_prng_update_period = 3600s
tls_random_reseed_period = 3600s
tls_random_source = dev:/dev/urandom
trace_service_name = trace
transport_maps =
transport_retry_time = 60s
trigger_timeout = 10s
undisclosed_recipients_header = To: undisclosed-recipients:;
unknown_address_reject_code = 450
unknown_client_reject_code = 450
unknown_hostname_reject_code = 450
unknown_local_recipient_reject_code = 550
unknown_relay_recipient_reject_code = 550
unknown_virtual_alias_reject_code = 550
unknown_virtual_mailbox_reject_code = 550
unverified_recipient_reject_code = 450
unverified_sender_reject_code = 450
use_getpwnam_ext = yes
use_od_delivery_path = no
verp_delimiter_filter = -=+
virtual_alias_domains = $virtual_alias_maps
virtual_alias_expansion_limit = 1000
virtual_alias_maps =
virtual_alias_recursion_limit = 1000
virtual_destination_concurrency_failed_cohort_limit = $default_destination_concurrency_failed_cohort_limit
virtual_destination_concurrency_limit = $default_destination_concurrency_limit
virtual_destination_concurrency_negative_feedback = $default_destination_concurrency_negative_feedback
virtual_destination_concurrency_positive_feedback = $default_destination_concurrency_positive_feedback
virtual_destination_rate_delay = $default_destination_rate_delay
virtual_destination_recipient_limit = $default_destination_recipient_limit
virtual_gid_maps =
virtual_initial_destination_concurrency = $initial_destination_concurrency
virtual_mailbox_base =
virtual_mailbox_domains = $virtual_mailbox_maps
virtual_mailbox_limit = 51200000
virtual_mailbox_lock = fcntl, dotlock
virtual_mailbox_maps =
virtual_minimum_uid = 100
virtual_transport = virtual
virtual_uid_maps =
macosxserver02:~ academic$
Could someone please help me figure out what is wrong?
Cheryl Tarbox
Macintosh Support Specialist
Binghamton University
[email protected]I found two things that were causing my troubles.
First, port 25 on the switch going to the server was blocked. After this was opened I was able to receive mail to macosxserver02.binghamton.edu. Since this mail server is only used for Podcast Producer notifications, I'm hoping to have this port closed back down after I get Pcast Producer back up and running and fully tested.
Second, when the upgrade from 10.5 -> 10.6 was performed, in ServerAdmin>Mail>Settings>Domain Name, only the .binghamton.edu was populated in this field, not the full domain name of macosxserver02.binghamton.edu. This was preventing me sending mail to our Google branded .binghamton.edu email addresses. Apparently 10.6 was looking locally for all the .binghamton.edu email addresses.
A big thank you to Gordon for looking into this and helping me get this resolved.
Cheryl -
Questions about Mail Service and Campaign in Portal 8.1
1.How to disable batch mode email in portal 8.1 Mail Service using
Campaign?
2.For batch mode email, when will it deliver?
3.Where can I admin those parameter besides the fields mapping in
portal Admin->Campaign Server and Mail Service?The docs haven't been moved over to the 8.1 docsite, but the 7.0 docs
for campaigns are still pretty much valid in 8.1. Look at:
http://e-docs.bea.com/wlp/docs70/dev/cmpaign.htm#998197
for more information.
Basic answers:
1. You can't from a campaign. It will always batch emails in the database.
2. Use the bea/weblogic81/portal/bin/mainmanager.bat|sh script, which
uses the com.bea.p13n.mail.MailManager command-line java class (JavaDoc
at http://e-docs.bea.com/wlp/docs81/javadoc/index.html). This can be
invoked from cron or at for regular email delivery. Also, the emails are
deposited in the MAIL_* tables
(http://e-docs.bea.com/wlp/docs81/db/4Schemas.html#1064602), so you
could implement a delivery system from that as well.
3. There are no parameters since the email delivery is invoked from a
command-line process.
Greg
surfboy wrote:
1.How to disable batch mode email in portal 8.1 Mail Service using
Campaign?
2.For batch mode email, when will it deliver?
3.Where can I admin those parameter besides the fields mapping in
portal Admin->Campaign Server and Mail Service? -
A135-S4527 Host Process for Windows Services stopped...
I have started getting a Windows error: Host Process for Windows Services stopped working and was closed. Laptop runs fine except my network connection says Connection Status: Unknown The service to detect this status is turned off and McAfee stopped working. Can't run any of the MS tools either. I am suspicous of conficker e but don't know how to detect or remove it. Have seen the b variant on an XP machine at work, but the tools we used on it don't work on Vista.
I am running Vista Home Edition (came on Laptop) upgraded to SP1 with auto-updates on. McAfee was also set for auto-updates and nightly full scans, active e-mail and internet scanning. No recent software downloads except for updates.
Have been having the issue since about April 28. Tried to restore but no dates exist past May 5. Tried the F8 Startup recovery no problems found. Have tried restarting services but they quickly stop again. Uninstalled McAfee and tried AVG. It allowed defintion updates and I scanned all files. No viruses, trojans or malware detected.
Any suggestions? I have a tasklstserv file I can copy and paste if it will help.That's a bad-sector event. At a command prompt (cmd.exe), run chkdsk /r.
Event ID 7 Source Disk
But it doesn't seem likely that's the cause of the message. When you get another one, note the time and check the Application and System logs for entries at that exact time.
Thanks for the detailed information.
What virus protection do you use?
-Jerry -
How to configure Mail Services in B1
Hi All,
I want to cinfigure the mail services in SAP B1 currently I am using SAP 2007 SP00 PL 12 My client wants that the daily reports and the Sales order should be mailed by B1 to cuntomer mail id. PLease tell the process to how to configure mail services in B1.
Thanks & Regards
pankaj Sharma.Hi Pankaj Sharma,
The suggestion above would be a good solution to you. However, if you do not want to use this add-on, you may just configure SBO-Mailer to perform the task. You may check all available setting for the mailer and read through Administrator Guide for how to set it up.
Thanks,
Gordon -
Postfix error, no Queue, mail service dosen't work anymore.
Hi,
I reinstall my osx server 10.5.5 and now the mail service dosent work anymore. In the SMTP log I get this error every time anyone try to send a email to this server.
postfix/smtpd[12554]: NOQUEUE: reject: RCPT from relais.videotron.ca[24.201.245.36]: 451 4.3.5 Server configuration error;
this is my postconf
alias_maps = hash:/etc/aliases
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 = leclap
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
messagesizelimit = 0
mydestination = $myhostname,localhost.$mydomain,localhost,mail.clap.ca,clap.qc.ca,clap.ca,69.70 .105.2,production.clap.ca,production.clap.qc.ca
mydomain = mail.clap.ca
mydomain_fallback = localhost
myhostname = clap.ca
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 bl.spamcop.net permit
smtpdpw_server_securityoptions = cram-md5
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpduse_pwserver = yes
unknownlocal_recipient_rejectcode = 550
I already try mailbfr, and nothing append.
If anybody know how to completly erase the mail service to startover whithout reinstall the server, I'm willing to do that to!
Thanks!
Message was edited by: robinplamondonEdit /etc/postfix/main.cf in Terminal or a text editor (not Word).
Change:
smtpdclientrestrictions = permit_mynetworks bl.spamcop.net permit
to:
smtpdclientrestrictions = permit_mynetworks rejectrblclient bl.spamcop.net permit
When done, issue:
sudo postfix reload
HTH,
Alex
mailbfr is for fixing the Cyrus database or backing up mail services. It has nothing to do with Postfix/SMTP -
I'm trying to set up a leopard home server and have rebuilt it several times now trying toiget the mail service to work correctly.
I will no doubt omit lots of necessary information but please bear with me
I have a registered domain and a static ip. My ISP supplies a broadband modem which just acts as a bridge to my own wireless router. I have done what I understand to be the required port forwarding - 21, 25, 80 & 110.
I have DNS at the ISP but have also set up DNS internally since I couldn't get anything to work without it!
Whilst I can send mail from the server my users can only send to the outside & receive no mail from inside or out.
The SMTP since the last restart:-
Feb 24 17:56:19 merlin postfix/master[37]: daemon started -- version 2.4.3, configuration /etc/postfix
Feb 24 18:08:53 merlin postfix/smtpd[282]: connect from demokritos5.cytanet.com.cy[195.14.130.179]
Feb 24 18:08:54 merlin postfix/smtpd[282]: NOQUEUE: reject: RCPT from demokritos5.cytanet.com.cy[195.14.130.179]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<demokritos5.cytanet.com.cy>
Feb 24 18:08:54 merlin postfix/smtpd[282]: disconnect from demokritos5.cytanet.com.cy[195.14.130.179]
Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max connection rate 1/60s for (smtp:195.14.130.179) at Feb 24 18:08:53
Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max connection count 1 for (smtp:195.14.130.179) at Feb 24 18:08:53
Feb 24 18:12:14 merlin postfix/anvil[284]: statistics: max cache size 1 at Feb 24 18:08:53
Feb 24 18:12:16 merlin postfix/smtpd[317]: connect from demokritos3.cytanet.com.cy[195.14.130.227]
Feb 24 18:12:16 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from demokritos3.cytanet.com.cy[195.14.130.227]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<demokritos3.cytanet.com.cy>
Feb 24 18:12:16 merlin postfix/smtpd[317]: disconnect from demokritos3.cytanet.com.cy[195.14.130.227]
Feb 24 18:12:46 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:12:46 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
Feb 24 18:12:47 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:12:58 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:12:59 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
Feb 24 18:12:59 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:13:28 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:13:29 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
Feb 24 18:13:29 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:14:09 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:14:09 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
Feb 24 18:14:09 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:14:20 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:14:20 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:15:50 merlin postfix/smtpd[317]: connect from unknown[213.149.189.165]
Feb 24 18:15:50 merlin postfix/smtpd[317]: NOQUEUE: reject: RCPT from unknown[213.149.189.165]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.4]>
Feb 24 18:15:50 merlin postfix/smtpd[317]: disconnect from unknown[213.149.189.165]
Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max connection rate 3/60s for (smtp:213.149.189.165) at Feb 24 18:13:28
Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max connection count 1 for (smtp:195.14.130.227) at Feb 24 18:12:16
Feb 24 18:19:10 merlin postfix/anvil[318]: statistics: max cache size 2 at Feb 24 18:12:46
Feb 24 18:20:09 merlin postfix/smtpd[376]: connect from merlin.2ndwivesclub.eu[192.168.1.2]
Feb 24 18:20:09 merlin postfix/smtpd[376]: 4D4ED8123E: client=merlin.2ndwivesclub.eu[192.168.1.2]
Feb 24 18:20:09 merlin postfix/cleanup[378]: 4D4ED8123E: message-id=<[email protected]>
Feb 24 18:20:09 merlin postfix/qmgr[100]: 4D4ED8123E: from=<[email protected]>, size=583, nrcpt=1 (queue active)
Feb 24 18:20:15 merlin postfix/smtpd[385]: connect from localhost[127.0.0.1]
Feb 24 18:20:15 merlin postfix/smtpd[385]: B202081265: client=localhost[127.0.0.1]
Feb 24 18:20:15 merlin postfix/cleanup[378]: B202081265: message-id=<[email protected]>
Feb 24 18:20:15 merlin postfix/qmgr[100]: B202081265: from=<[email protected]>, size=1037, nrcpt=1 (queue active)
Feb 24 18:20:15 merlin postfix/smtpd[385]: disconnect from localhost[127.0.0.1]
Feb 24 18:20:15 merlin postfix/smtp[386]: B202081265: to=<[email protected]>, relay=none, delay=0.05, delays=0.02/0.03/0/0, dsn=5.4.6, status=bounced (mail for 2ndwivesclub.eu loops back to myself)
Feb 24 18:20:15 merlin postfix/cleanup[378]: CBEAD81267: message-id=<[email protected]>
Feb 24 18:20:15 merlin postfix/qmgr[100]: CBEAD81267: from=, size=2928, nrcpt=1 (queue active)
Feb 24 18:20:15 merlin postfix/bounce[387]: B202081265: sender non-delivery notification: CBEAD81267
Feb 24 18:20:15 merlin postfix/qmgr[100]: B202081265: removed
Feb 24 18:20:15 merlin postfix/smtp[386]: CBEAD81267: to=<[email protected]>, relay=none, delay=0.02, delays=0.01/0/0/0, dsn=5.4.6, status=bounced (mail for 2ndwivesclub.eu loops back to myself)
Feb 24 18:20:15 merlin postfix/qmgr[100]: CBEAD81267: removed
Feb 24 18:20:15 merlin postfix/smtp[379]: 4D4ED8123E: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.7, delays=0.2/0.13/0.4/6, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B202081265)
Feb 24 18:20:15 merlin postfix/qmgr[100]: 4D4ED8123E: removed
Feb 24 18:21:09 merlin postfix/smtpd[376]: disconnect from merlin.2ndwivesclub.eu[192.168.1.2]
And conf:-
merlin:~ alf$ postconf -n
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 = postmaster
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,localhost
mydomain = 2ndwivesclub.eu
mydomain_fallback = localhost
myhostname = mail.2ndwivesclub.eu
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 = none
smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
smtpduse_pwserver = no
unknownlocal_recipient_rejectcode = 550
merlin:~ alf$
And a rejection notice.
Some help would be really appreciated.
Cheers.
JohnAdd 2ndwivesclub.eu to local host aliases in Server Admin -> Mail -> Settings -> Advanced -> Hosting
-
Mail service SSL doesn't work after migration
Well, the migration worked well, EXCEPT that I cannot get SSL to work for the mail service.
The same SSL certificate that works fine for the web service doesn't seem to work properly for mail. Prior to the in place upgrade, everything was fine, now, mail clients get the message that certificate may have been issued by an unknown authority -- BUT ONLY FOR IMAP and POP. Using the same certificate for SMTP seems to work just fine.
My working theory is that at one point I had to reissue the certificate completely, and that somehow, Cyrus was using the older certificate and private key, and that during the migration, things got really hosed.
Is there any way to get the new dovecot service to use the same cert? The GUI suggests it is, but I suspect some command line trickery may be needed.
On one final note: how does one run Keychain First Aid on the system keychain?For reasons I cannot explain, dovecot.conf contains a line commented out specifically excluding the CA chain file -- saying it usually isn't required.
Removing the comment from this field (the installer generated a new file and created it on the disk, it's just commented out) resulted in SSL magically working again.
Now the bigger question: why was option in the dovecot.conf file intentionally disabled, even though the correct information (correct imported file path, correct imported files) were populated? -
Mail service on, SMTP on, but clients can't connect -- please help a novice
Hi all,
We use 10.4 Server on a G5 Xserve. A few days ago we had a problem with our server being used for spam. That was fixed quickly enough, but the problem is: while being fixed, the mail queue accumulated more and more mail, and it wasn't going out. The "retry" button didn't work. Repairing the database didn't work.
To make a long story shorter, after reading different things here and on the web, I managed to delete all the messages in the queue. All the users are still there. But now, when I turn the mail service back on, everyone gets a "can't connect" error.
I've used the terminal before, but I've always been following directions; I don't know what to type or why. But if someone with patience can help, I can follow directions, and would really appreciate the help. Right now I'm dead in the water.OK, I've already admitted that I know nothing about this, so I'm sure this will give some people some laughs. That's OK, so the only thing I've changed was the name of the company. I have more peace of mind knowing I'm not showing who's got problems. The other thing is that I don't know when my part of the history begins. Maybe it's all me, but I don't remember doing anything even remotely close to changing IPs. So here it is:
1 telnet mail.abcde.com 110
2 telnet mail.abcde.com 110
3 telnet mail.abcde.com 110
4 sudo /etc/squirrelmail/config/conf.pl
5 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/
6 update_list.txt
7 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/
8 update_list.txt
9 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/update_list.txt
10 softwareupdate
11 man changeip
12 changeip
13 exit
14 changeip -checkhostname
15 sudo changeip
16 changeip -checkhostname
17 sudo changeip -checkhostname
18 man changeip
19 sudo changeip -gethostname
20 sudo changeip -gethostname
21 sudo changeip
22 /usr/sbin/changeip /LDAPv3/127.0.0.1 10.10.10.3 10.10.10.3 mail.abcde.org mail.abcde.org
23 sudo changeip -checkhostname
24 sudo /usr/sbin/changeip /LDAPv3/127.0.0.1 10.10.10.3 10.10.10.3 mail.abcde.org mail.abcde.org
25 changeip -checkhostname
26 sudo changeip -checkhostname
27 sudo rm -rf /usr/share/swupd/html/061-4590/
28 sudo rm -rf /usr/share/swupd/html/061-4589/
29 sudo rm -rf /usr/share/swupd/html/061-4589
30 sudo rm -rf /usr/share/swupd/html/061-4590/
31 sudo rm -rf /usr/share/swupd/html/061-4590/
32 sudo rm -rf /usr/share/swupd/html/061-2089/
33 grep swupd /etc/swupd/com.apple.server.swupdate.plist > ~/Desktop/update_list.txt
34 sudo mkdir /usr/sieve
35 sudo mkdir /usr/sieve
36 sudo pico /etc/services
37 netstat -an | grep 2000
38 telnet localhost 2000
39 sudo mkdir -p /usr/sieve
40 sudo mkdir -p /usr/sieve
41 sudo chown cyrusimap /usr/sieve
42 sudo chgrp wheel /usr/sieve
43 cd
44 pwd
45 ls
46 cd /usr
47 ls
48 ls -l
49 exit
50 sudo pico /etc/services
51 telnet localhost 2000
52 netstat
53 netstat -an | grep 2000
54 exit
55 changeip
56 sudo changeip
57 changeip -checkhostname
58 sudo changeip -checkhostname
59 exit
60 sudo ls -al /var/spool/imap/user/diradmin
61 sudo ls -al /var/spool/imap/user/kbentley
62 sudo /usr/share/mailman/bin/check_perms -f
63 su root
64 su root
65 su root
66 su root
67 su root
68 fsck -f
69 fsck
70 sudo fsck -f
71 sudo fsck /?
72 fsck /help
73 fsck \help
74 pwd
75 ..
76 12345
77 sudo /System/Library/CoreServices/Finder.app/
78 sudo /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
79 su root
80 su root
81 sudo -u cyrusimap
82 su cyrus
83 su cyrus
84 su cyrus
85 su cyrus
86 su cyrus
87 cyrus
88 sudo cyrus
89 su cyrus
90 su cyrus
91 su cyrus /usr/bin/cyrus/bin/reconstruct -r -f /var/spool/imap/bbills
92 postfix reload
93 sudo postfix reload
94 sudo postfix reload
95 ls -l /var/spool/imap/user/bbills
96 history -
Error during configuring mail Service
Dear BASIS Gurus n Experts,
Can we configure the mail services on SAP without having a exchange/mail Server.
For this I have tries following but it is not working:
In Systems Default profile I have added: icm/server_port_1 PROT=SMTP,PORT=25,TIMEOUT=180, than
1. Used transaction SCOT
2. From top menu: View -> System Status
3. Double Click on SMTP
4. In Pop window entered description
5. Ticked on "Node in use" box
6. Entered the SMTP server name
7. Entered port 25
8. Clicked on the button next to Internet called "Set"
9. On next window Enter the * in "address area" box.
10. Click Continue --> Continue buttons to exit the main window
11. From top menu: Settings -> Default Domain enter the domain name as "companyname.com"
12. Now defined the job to process the mail, from top menu: View -> Jobs
13. From top menu: Job -> Create
14. Enter a name as SMTP
15. Click on "INT" in the list then "Schedule job" button
16. Entered start date and time, then click on "Schedule Periodically" button
17. Entered 10 minutes.
Now I create a message in workplace, and send it to a mail id but get an error message:
Definately cannot transfer message to node SMTP due to connection error
Please Guide me where I am wrong.
Thanks in advance. Early response will be highly appreciated.
DSCDear Venktesh,
In SMICM --> Go to service, I found two entries:
No. Protocol Service Name Port Host Name Time Out active Ext. Bind
1. HTTP 8000 Development 60 X X
2. SMTP 2500 Development 180 X
When I try to send a mail I found following error:...
Definately cannot transfer message to node SMTP due to connection error
Message no. XS816
Diagnosis
Due to a technical fault, the system could not set up a connection to the RFC destination Check port and mail server for SMTP nodes. Therefore, the message could not be transferred to node SMTP.
System Response
The system was unable to transfer the message.
Additional information of the node used (in the system language of the node):
Procedure
Check the connection from R/3 to node SMTP. Perhaps the node is not assigned to the correct RFC destination. If so, correct this in Customizing.
Otherwise use RFC destination management to check the RFC connection to destination Check port and mail server for SMTP nodes.
If R/3 is in productive operation, it is advisable to reroute provisionally to another node.
You should therefore notify your system administrator.
Please suggest.
With thanks,
DSC
Maybe you are looking for
-
Windows 7/8.0/8.1 NIC teaming issue
Hello, I'm having an issue with Teaming network adapters in all recent Windows client OSs. I'm using Intel Pro Dual Port or Broadcom NetExtreme II GigaBit adapters with the appropriate drivers/applications from the vendors. I am able to set up teamin
-
Retriving company code in R3 from service organisation in CRM
Hi, I have service organisation of CRM in R3 , now I need the corresponding company code/plant in R3. how to retrive it, is there any FM or method by which we can retrive. thanks bobby
-
Asian characters displaying in my english language PDF.
This morning I opened a PDF and got a message that I needed to install a language pack. I installed the asian language pack as requested and when I opened my PDF there were asian characters displaying in my english language PDF. How do I fix this i
-
i have worked through all of the support suggested items and i cannot get evnets that are put on my Outlook calendar to go to my icloud calendar and therefore my ipad and iphone or vice versa with events put on my iOS devices. i want my staff to ent
-
Table cell objects removed by Pages ver 5.1
I created a document in the previous version of Pages, and now when I open it with Pages 5.1, it removes the objects from the table cells. How can I overcome this? I thought I might work around by opening it in the previous version, but I cant figure