Inbound mail not getting delivered - intermittent
Hi.
We are running Server 10.3.9 on an XSERVE. Ever since using mailfbr to fix a database corruption, mail is not being delivered to us by at least one sender we know about. Can't find his email in the logs or mailq, but he gets a bounce with a header indicating our mailserver has rejected his email. I have turned off all filters, repaired privileges, rerun mailfbr several times and sudo postsuper -r ALL but nothing seems to work. His emails keep bouncing.
I don't believe there are any spam or virus routines running, but I did not set the server up initially and am trying to relearn my way around unix. Any help, ideas, etc. would be greatly appreciated.
Mark,
Do you see this message as sitting in your queue? (It
hasn't bounced it just wasn't delivered yet).
Not anymore.
The logs are in /var/log
look for mail.log and mailaccess.log
mailaccess.log
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost pop3[7497]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost pop3[7497]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost imap[7495]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7495]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7495]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7495]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7494]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7494 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service imap pid 7495 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7499]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7499]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7499]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7499]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7499]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7499]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7499]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7499 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7500]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7500]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7500]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7498]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7498 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service pop3 pid 7497 in READY state: terminated abnormally
Feb 14 14:51:44 localhost pop3[7502]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7500]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7500]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7500]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7500]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7500 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7503]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7503]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7503]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7501]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7501 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7503]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7503]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7503]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7503]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7504]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7504 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost pop3[7502]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost pop3[7502]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service pop3 pid 7502 in READY state: terminated abnormally
Feb 14 14:51:44 localhost pop3[7506]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost pop3[7506]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost pop3[7506]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service imap pid 7503 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7507]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7507]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7507]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7507]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7507]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7507]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7507]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7507 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7508]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7508]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7508]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7506]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7505]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7505 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7506]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7506]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7506]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7506 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7510]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7508]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7508]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7508]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7508]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7508 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7511]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7511]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7511]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7510]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7510]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7510 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7512]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7512]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7512]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7512 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7513]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7509]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7509 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7513]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7514]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7514 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7511]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7511]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7511]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7511]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7511 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7516]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7516]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7516]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7513]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7513 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7517]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7515]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7515 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7517]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7517]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7517 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7519]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7519]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7519]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7519 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7520]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7520]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7520]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7520 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7521]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7518]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7518 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7522]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost imap[7516]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7516]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7516]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7516]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7516 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7523]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7523]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7523]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7521]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7522 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7521]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7521 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7525]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7524]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7524 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7525]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7523]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7523]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7523]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7523]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7523 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7527]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7527]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7527]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7525]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7525 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7528]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7528]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7528]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7527]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7527]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7527]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7527]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7527 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7529]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7529]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7529]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7529]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7529]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7529]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7529]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7529 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7530]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7530]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7530]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7528]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7526]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7526 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7528]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7528]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7528]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7528 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7532]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7530]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7530]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7530]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7530]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7530 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7533]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7533]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7533]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7533]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7533]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7533]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7533]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7533 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7534]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7534]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7534]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7531]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7531 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7532]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7532]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7532 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7536]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7535]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7535 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7536]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7536]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7536 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7538]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7534]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7534]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7534]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7534]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7534 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7539]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7539]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7539]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7537]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7537 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7538]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7538]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7538 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7541]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7539]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7539]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7539]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7539]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost pop3[7541]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7541]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7541 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7542]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7540]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7540 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7543]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7543 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost master[349]: service imap pid 7539 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7545]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7545]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7545]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7542]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7542]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7542 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7546]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7544]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7544 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7546]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7546]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7546 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7548]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7548]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7548]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7547]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7547 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7545]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7545]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7545]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7545]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7545 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7550]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7550]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7550]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7549]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7549 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7550]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7550]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7550]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7550]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost pop3[7548]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7548]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7548]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7548]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7548 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7552]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7551]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7551 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7552]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7552]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7552 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7554]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost master[349]: service imap pid 7550 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7555]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7555]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7555]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7553]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7553 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7555]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7554]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7555]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7555]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7555]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7555 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7557]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7557]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7557]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7557]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7557]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7557]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7557]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7557 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7558]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7558]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7558]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7558]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7558]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7558]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7558]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7558 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7559]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7559]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7559]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7556]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7556 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7560]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7560 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7554]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7554 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7562]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7561]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7561 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7559]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7559]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7559]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7559]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7559 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7564]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7564]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7564]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7562]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7562]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7562 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7565]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7563]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7563 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7565]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7565]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7565 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7567]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7567]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7567]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7567 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7568]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7564]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7564]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7564]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7564]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7564 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7569]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7569]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7569]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7566]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7566 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7570]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7570 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7568]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7568]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7568 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7572]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7569]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7569]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7569]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7569]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7569 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7573]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7573]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7573]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7572]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7572]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7572 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7574]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7571]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7571 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7574]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost pop3[7574]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service pop3 pid 7574 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7576]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7575]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7575 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7577]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7577 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7576]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost pop3[7576]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service pop3 pid 7576 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7579]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7579]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7579]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost imap[7573]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7573]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost imap[7573]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost imap[7573]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service imap pid 7573 in READY state: terminated abnormally
Feb 14 14:51:48 localhost imap[7580]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost imap[7580]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost imap[7580]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7579]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7580]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7580]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost imap[7580]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost imap[7580]: Fatal error: can't read mailboxes f
Similar Messages
-
Exit Class for Inbound Mail not getting triggered
Hi Gurus,
I have created an exit class for processing the Inbound Mail that comes to SAP Inbox (SOIN).
I have set up the Inbound processing rule in transaction SO50 and set it to all recipients.
If i send a mail from any external id to the id configured in SAP then it is coming in SAP Inbox (SOIN) but the exit class for processing the email is not getting triggered.
I have made all the settings for SMTP.
Kindly guide me with the steps needed to be followed for triggering the Exit Class.Hi
Check u have maintained ur outgoing mail server IP in SCOT transation.
Check link step to configure PO mail.
http://architectsap.com/blog/sap/sap-mm-purchasing-send-purchase-order-by-mail-to-vendor-in-sap/ -
Why does a PDF file created in Pages, attached to e-mail, not get sent?
Why does a PDF file created in Pages, attached to e-mail, not get sent? I even blank copied myself and nothing seems to have been sent. Could it bee the size of the PDF file?
They send for me, my test document was 3.8 MB.
-
We are testing an app at work and Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered to these tow devices.
PUSH notification were delivered to some of the other iOS devices: (iPhone5 / iOS 6.1.4 and iPhone5 / iOS 7.0.3)Sounds like you have a battry issue but don't want to believe it.
If a car was running fine on one tank of gas, then you filled it up with another tank of gas and it began to run funny, one might suspect that tank of gas. But let's just say coincidence blew a valve-- would you think the new tank of gas was the culprit?
BUT WAIT!! It just might have been! The gas could have been of higher octane and put more more strain on the valves; you know, like going from 87 octane (OS6) to 93 octane (OS7) and showing you the engine was on the edge of compromise.
Sometimes you have to go with common sense. If everything else is ruled out, it must be the battery. And if it runs fine one moment in OS6 but immediately ***** in OS7, I'd believe my battery was suspect-- though comfy-- in OS6 but the OS7 showed its true power.
Moreover, if you had the answer-- or didn't want to believe someone's more competent advice-- why did you even call? You've already shown that you don't know much when you asked if you could go backwards after setting up the new OS as a new phone.
Additonally, if you're such the know-it-all, but yourself the $29 battery and put it in yourself. It's a piece of cake.
<Edited By Host> -
Where do i look for mail sent through thunderbird that does not get delivered
I have two email clients. One is thunderbird and the other through my local server. I know some of my emails are not being received because of address changes.where do i find or set up undelivered mail notification in thunderbird . To address airmails answer;Thunderbird is being promoted as an open source stand alone email client if i'm not mistaken
There is no such thing as a Thunderbird email account so not sure what you are talking about there. I am not even sure if you are talking about mail you have sent or mail you are expecting to receive.
Thunderbird connects to your actual email providers server Inbox and downloads what is there. Maybe you should contact your email provider. You could check your providers Spam folder to see if mail is getting filtered there. -
Mail not getting all messages from server and other strange behavior
Hello All,
Mail has been doing some odd things for me of late (at least the last week) and I'm lost for a solution to my problem. As far as I can tell, perhaps my Prefs. have become corrupted, or at least something in relation to Mail has become corrupted. Perhaps someone has a solution to this issue before I have to back it all up and NUKE the whole **** app to get back up and running properly.
The main issue I appear to be having is that Mail is not getting all of my Mail messages from my server. I can log into my web-mail interface provided by my domain host and can see there that there are many e-mails that don't appear to be coming down the pipe to the Mail.app client. I'm getting some e-mail's but not all....
*Here are all the things that I've checked:*
• The missing e-mails are not being picked up as Junk and are not in the Junk folder
• I have done a search within Mail for the missing e-mail's and nothing turns up anywhere.
• I have checked on the server end that I'm not maxing out my InBox or that there are any other service issues from my domain host provider.
• I have been into Prefs and checked my account settings - most (see below) of which appear to be as normal and are fine.
*Here are the weird things that I've noticed:*
• When I went into the Prefs. for the account in question, I noticed that my login had changed. For example - it usually it is "[email protected]", however it had seemed to have changed to just "johndoe" - I know this wasn't me as my domain host will not allow me to access any mail unless the login is the full mail address.
• In RULES, every rule I double click to check on seems mostly fine, apart from the fact that every "Account is:" the pull down menu just appears as blank. Usually it says "Account is: ([email protected])"
It's there last 2 items that make me think something is corrupted - so I guess my question is, what pref or file has corrupted and how can I fix it without having to give Mail.app a digital enema?
Any assistance would be most helpful - missing some but not all your incoming e-mail messages is quite annoying, as you can guess...!
Thanks,
BozHello Boz.
This appears to be a rules issue. Mail is almost certainly downloading those messages, but they’re probably being processed by your rules in an unexpected way — given the information you’ve provided, maybe because there is something wrong with the file where the account settings are stored.
Do you have any Mail plug-ins? In the Finder, go to each of the following folders (if they exist). What do you see there?
/Library/InputManagers/
/Library/Mail/Bundles/
~/Library/InputManagers/
~/Library/Mail/Bundles/
To make accurately reporting this information easier, you may open /Applications/Utilities/Terminal, type the following command (you can just copy it here and paste it in Terminal), and press <Return>. You can then copy the output of that command from Terminal and paste it in your reply to this post:
ls -1 /Library/InputManagers /Library/Mail/Bundles ~/Library/InputManagers ~/Library/Mail/Bundles
<hr>
Verify/repair the startup disk (not just permissions), as described here:
The Repair functions of Disk Utility: what's it all about?
After having fixed all the filesystem issues, if any, and ensuring that there’s enough space available on the startup disk (a few GB, plus the space needed to make a backup copy of the Mail folder), try this:
1. Write down your Mail > Preferences > Accounts settings or take screen shots of them.
2. If you have a .Mac account and .Mac synchronization of Mail data is enabled either in Mail > Preferences > General or in System Preferences > .Mac, disable it before proceeding.
3. Quit Mail.
4. Make a backup copy of the ~/Library/Mail folder, just in case something goes wrong while trying to solve the problem. You can do this in the Finder by dragging the Mail folder to the Desktop while holding the Option (Alt) key down, for example. This is where all your mail is locally stored.
5. In the Finder, go to ~/Library/Preferences/. Locate com.apple.mail.plist and move it to the Desktop (to be deleted if this solves the problem). If you have a backup of your data that includes a working copy of this file, you may try restoring it from the backup to avoid steps 6-8.
6. Open Mail. You’ll have to set up your non-.Mac accounts from scratch all over again. If given the option to import existing mailboxes or something like that, don’t. Just enter the account information and Mail will automagically rediscover the data in ~/Library/Mail/ when done.
7. You’ll have to re-configure some of your Mail > Preferences settings. For spam-related security reasons, the first thing you should do is go to Preferences > Viewing and disable Display remote images in HTML messages if it’s enabled.
8. As a side effect of re-creating com.apple.mail.plist, Mail might rename Outbox (which is where messages waiting to be sent are stored) to Delivered. The name of that mailbox is actually a misnomer, as it would contain messages (if any) that couldn’t be delivered for some reason. You can delete that mailbox if you wish.
9. If the problem is fixed now and .Mac synchronization of Mail data was enabled at the beginning, enable it again, go to System Preferences > .Mac > Advanced, click Reset Sync Data, and choose the appropriate options to reset the Mail data stored on the .Mac server with the data locally stored on the computer, i.e. sync data must flow from the computer to the .Mac server.
<hr>
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. You can easily locate any of the folders referred to in this post by copying the folder path here, doing Go > Go to Folder in the Finder, and pasting the folder path there. -
All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint. -
E-mail not being delivered - AGAIN!!!
This *****!!! You guys are really ruining my e-mail ability...since I do pay for this service!!! Stop blocking my e-mail! I'm really ******!!!!
This is the second week my e-mail has been rejected by the server and I've not been able to finish sending out my mail to people. I organize a class reunion. I e-mail about 200 people once a week. For some reason there was a change to a setting somewhere along the line and 2 weeks ago my mail stopped being delivered. I stated in my last contact that I would switch to a free service that would allow me to send my mail. I don't use all the .Mac services and I can get web space much cheaper.
Either fix this or consider me (a member for 4+ years) cancelled. I don't have time to write to you guys every week about this. Did I mention I was ******?
[email protected]
It's not like I am sending out huge files or something like that. See below.
This is what I am sending.
Hello Class of 1992,
Okay, you can stop waiting now. You've got to make your move and send in your money for tickets. Get them before the May 15 deadline and save yourself $40 dollars!
I've heard from so many of you over the past 5 years of working on this project and there has been a great deal of interest over this period of time. So...here we are...it's almost happening and you need a ticket to get in the door.
We had a meeting this weekend in the space rented for the 15 year reunion and we've got such a great location chosen for you guys. We'll be right on the beach which we have access to during the day for those who want to show up with coolers and beach chairs to relax, meet and greet. Bring your kids, spouses and spirit of fun to the afternoon beach time.
You are going to have a great time during the evening. We've got plenty of food available, drinks, music and how many reunions do you know of that have a tower to overlook the entire beach at their disposal?
It's gonna be awesome! And guess what...YOU ARE INVITED!!!
Get your ticket ordered early....save some $$$ and start off your summer right with old friends, fantastic times and new memories.
For a single person it's only $85.00 dollars. If you bring your spouse or date; only $125.00 per couple. And heck, if you've got anyone else you'd like to bring it's only $45.00 for each additional person. You can't beat it for an awesome time.
Make your check payable to Bill (Billy) Owens (Reunion Treasurer).
Mail to:
3765 Silina Drive
Virginia Beach, VA 23452
See you on June 16!
www.kempsville1992.comParsing through your rant which isn't directed at Apple, it seems you might be exceeding the sending limits included with a .Mac account which are not extreme by any means so take a deep breath and calm down.
All internet service providers and email account providers (even free ones) have sending limits or restrictions for non-business/personal email accounts.
These restrictions are in place as part of an overall effort to prevent spam emanating from an ISP's or email account provider's domain. In case you aren't aware, spammers make use of bulk spam mailings and these restrictions make it more difficult for a spammer to do his thing.
It makes no difference that you aren't a spammer or the content of your message is not spam since there is no way an ISP or email account provider can make this determination when you send a message but they can impose sending limits or restrictions.
Copied from the following link.
http://docs.info.apple.com/article.html?artnum=25301
.Mac has several safeguards in place to ensure that only .Mac members send messages with the Mac.com outgoing mail server. Among them are reasonable limitations on:
* The number of messages that can be sent each day (200 messages)
* The number of recipients that can be sent to each day (400 recipients)
* The number of recipients a message can be addressed to at one time (100 recipients)
* The size of outgoing messages
There is also a 10 MB maximum size for messages sent or received using the .Mac mail system.
.Mac Email has been designed primarily for personal use. Sending unsolicited bulk email messages through the .Mac email server is prohibited.
If your message is being rejected by a recipient's incoming mail server, what is the return email error message provided which is sent by the recipient's incoming mail server?
Regardless, this problem is with the recipient's email account provider. If the return email error message from the recipient's incoming mail server indicates the recipient has exceeded their allocated server storage space, this the recipient's problem.
So instead of ranting, how about providing more detailed information about the error message provided so someone here can help narrow down where the problem lies so you can direct your efforts there.
IMO - since you use your .Mac account for email only, you should cancel your account but keep in mind that even a "free" service includes sending restrictions which may not be identical to .Mac account restrictions but none are restriction free. -
Mail not be delived to one user, unless sent as a CC or if another user is also in the TO: Field
Hello All,
I have a strange issue that I hope someone has seen before. (Exchange 2003)
I have one user that does not receive mail to her outlook or OWA box if her address is in the To: field.
If her address is in the CC or BCC field she receives the message.
Additionally, She will receive the e-mail if her address is in the To: field along with another user.
Trouble shooting thus far:
1.) Confirmed that Exchange message tracker is reporting successful delivery. Yes
2.) Confirmed that the message is not going to deleted items. Yes
3.) Confirmed this is also occurring in OWA. Yes
4.) Confirmed no white or blacklists. Yes
5.) Confirmed Cache mode is enabled. Yes
6.) Setup the account on new workstation and have the same issue. Yes
This is a very strange issue which I have not seen before. If her name is the ONLY name in the To: field, the message reports successful, but does not show up in Outlook or OWA. If her name is the ONLY name in the CC ot BCC field the message
is delivered successfully.
If you add a second user to the To: field, the message is successful.
So to sum this up; If someone addresses a message just to her, it will report successful but will not be delivered.
If you add a second user to the To field; The message is delivered successfully.
Any help would be greatly appreciated on this one.
Thanks in advance!
GregHi,
Did you get any NDR message when her name is the only name in the To field?
Additionally, I recommend you check if any transport rules are applied to her mailbox.
If not, you can try to move the mailbox to other database and check if the issue persist.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support -
Inbound Activity not getting created with Campaign Response
Dear Experts,
I am working in a scenario where we are using Campaign Automation for sending Email Survey to business partners.
Mails are reaching the BPs, survey response also coming to the survey tables, But the Inbound activity is not getting created in the system.
I am using standard Transaction type ''0000'' for inbound activity. . which is ''Appointment'' and Category type ''Date'', direction ''inbound''
The Action profile for this activity is Campaign_Automation_Activity. . .
I have done questionnaire determination is customizing too.. .
Am I missing a something??
Some linking of this Activity with Campaign element?
Please suggest!!Hello Naresh,
Thanks for the reply, but can u explain me in details.
1. I am using the MKTCA PBO n PAI,
2.I have checked the BAdI CRM_SVY_MKTCA_PAI and checked the Transaction type ''0000'' hardcoded, so using the same Transaction type, the Category is hrdcoded as ''002''
3. Transaction type ''0000'' is active.
Please suggest? -
Automatic Mail not getting generated through background job
Hi Experts,
We have set up a job variant with spool recipients. We are getting the automatic mail if the job is getting finished successfully. But we are not getting the automatic mail if the job is in cancelled status. Earlier we used to get the mail even if the job is in cancelled status. We are not sure if there is any setting which would restrict the automatic mail based on the job status.
Appreciate your help in this regard.
Thanks and Regards,
Ranjani.Hi,
Just for a work around, try checking the SAP user inbox for the user who has scheduled the background job.
I don't there is any seperate configuration in Spool List Recipient for the canceled jobs. We need to confirm that the email ids provided in the Spool List recipient are correct and the background job creates a spool request even if it is canceled.
Also if possible try deleting the existing background job and create a new background job with the same parameters and valid email id's maintained in the Spool List recipient.
OR
Without deleting the existing background job, parallely create a new background job with the same parameters and valid email id's maintained in the Spool List recipient. If it works then delete the old background job.
Thanks
Harish -
JMS message not getting delivered
I'm trying to create a simple MDB with JDeveloper 10.1.3.2.
I've tried to configure the sender and receiver to use the embedded OC4J message service.
The code compiles and runs without any errors but the message doesn't seem to get delivered to the MDB.
How could I debug message delivery in this case?
What could be causing the message delivery to fail?
Here's the code from a session bean that sends the message:
@Resource(mappedName="jms/Topic/testTCF") private ConnectionFactory connectionFactory;
@Resource(mappedName="jms/Topic/testTopic") private Topic topic;
public void sendMessage() {
try {
Connection con = connectionFactory.createConnection();
Session session = con.createSession(true, 0);
MessageProducer producer = session.createProducer(topic);
TextMessage msg = session.createTextMessage();
msg.setText("hello");
producer.send(msg);
con.close();
} catch (JMSException e) { }
MDB:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName="connectionFactoryJndiName", propertyValue="jms/Topic/testTCF"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="jms/Topic/testTopic"),
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic")
public class MessageReceiver1Bean implements MessageListener {
public void onMessage(Message message) {
System.out.println("hello");
Message service configuration:
<jms-server port="9227">
<queue location="jms/Queue/testQueue" name="queue"/>
<queue-connection-factory location="jms/Queue/testQCF"/>
<topic location="jms/Topic/testTopic" name="topic"/>
<topic-connection-factory location="jms/Topic/testTCF"/>
<log><file path="../log/jms.log"/></log>
</jms-server>A few questions to better understand your case,
1) are you using pub/sub (topics) or ptp (queues) ?
2) are you producing inside a transaction (either use JTA or jms transacted session)
3) do you use/set TimeToDeliver parameter ?
4) when you monitor, do you see your messages under pending count ?
"Rajiv Kadayam" <[email protected]> wrote:
>
>I'm having trouble with the 6.1sp5 version of weblogic specifically with
>the JMS
>server not quite notifying my message listeners whenever a new message
>is received
>in the queue. I can see the messages via the console by way of clicking
>"monitor
>all desitinations". I don't see any exceptions at all. This piece of
>code does
>work in Weblogic 7 and it did work on weblogic 6.1sp4. I'm not quite
>using MDBs
>and my publishers are CORBA services and there are no EJB components
>involved.
>
>The trouble is there are no exceptions and my message listeners are just
>waiting.
>any tips or ideas would be greatly appreciated.
>
>thanks
>rajiv
-
Inbound Delivery not getting transferred to GTS
Hi Experts,
We are presently implementing GTS 7.2 Customs Management in my company and we are experiencing this issue. Here are steps completed for the document transfer.
1. GTS plugis are activated for the Inbound Delvieries along with other documents.
2. All the basic configuration is also complete in the GTS system.
When we create a inbound delivery in ECC 6.0, it is not getting transferred to GTS. But when I go set the incomplete check buttoen either at header or line item level of the delivery, then it is immediately transferred to GTS.
I checked all the config related to incomplete procedure for SD/MM documents in ECC. I am able to see the green light automatically set (after the config VI29 and VI49) at the header/item level but still incomplete set is not automatically set. Can you please help to find are there any other config which needs to be done to make this inbound delivery automatic. I understand there is a user exit for this, but I would like to accomplish without userexit.
Thanks in advance.
Vijay.Hi Vijay,
Ok, that's a lot clearer - thanks.
I'm fairly sure that those "SET" buttons have no influence on the transfer of the Inbound Delivery to GTS. And, as far as I know, they have no internal functionality - the toggling buttons are provided just so that you can flag manually if required for some reason. My guess is that making ANY change to the Delivery would have the same result.
The other question I should have asked is; why are you trying to transfer the Inbound Delivery?
- compliance checks?
- transit declaration?
- customs declaration before GR?
That's to say; what gets created in GTS when the Delivery transfers?
Best regards,
Dave -
Mails not getting sent from Receiver Mail Channel
Hi ALL
I have a File to mail scenario , I see chakred flag in SXMB_MONI ..but mail are not getting triggred from the Receiver mail adapter..
I gave the URL like this smtp://sxd123.abc.com
and the respective E-mail ID's
I dont see any message in the communication channel monitering also ..wht could be the reson.. ?
Thanks
SouzHi Dominic,
Since you are not seeing any entry in the communication channel (receiver), I think there is a problem with your configuration. Check whether you have used the correct channel (of type MAIL) in the receiver agreement.
Regards
Suraj -
F9N1 - Inbound FINSTA not getting generated
Hi,
When I execute F9N1, internal FINSTA are not getting generated..
The application log shows current Accounts being edited by end of day processing run
What could be wrong and what can be done? Any idea..
The next date in F9K3- Current Account is 11.02.2010
The F9N1 run date is 12.03.2010
The F9B1 date - Current date is 12.03.2010
New posting date - 15.03.2010
I am in Development server and trying to add a new company code to the IHC set up. Where can I look into? The internal FINSTA are not getting generated..
Regards,
SAPFICO
Edited by: SAPFICO on Mar 12, 2010 11:25 AMRavi,
I found the problem.
Let me explain the whole process for the benefit of other consultants like me.
Pre-requisites for generating FINSTA IDOC for any account in IHC:
1. In the account (F9K2 - change account) go to 'Account Statements' TAB and ensure that the 'Next date' is the date on which you are trying to create the bank statement.
2. In WE20 you should have created a partner profile for the Business Partner (Partner type GP) who is the Account holder.
3. In this partner profile for the BP there should be a Outbound parameter for FINSTA (without Message code IHC and Message function FI) with basic type FINSTA01. The port used for this Outbound Parameter should be LOCAL.
4. For the same BP there should be a Inbound parameter for FINSTA with port and this port should be your client where the subsidiary's company code resides.
Now when you run F9N1, it will create two FINSTA IDOC's, one with LOCAL as port and for this the Partner will be your BP who holds the account in the IHC.
Another FINSTA IDOC will have the House Bank as partner. This IDOC will be succesful only if you have created the account as a House Bank and Account ID in FI12 configuration for the subsidiary company code.
Hope I have made myself clear.
Kalyan
Maybe you are looking for
-
Report for vendor master changes
Good day, Please can you assist with this issue, Report S_ALR_87012089,program RFKABL00 Version ECC 6.0 This report does not reflect the old and the new values for changed bank details. It does not show anything under the old value and shows **delete
-
Hello all, I have a question about Apple's notes App. I've had my 3G iPhone for a couple years now and I've never really used the nots App. Within the last couple months however, I use it all the time for work. The problem I ran into is my notes all
-
How do I insert the value of an email field in the submit mailto: argument?
I want to create a button that will redirect a PDF form to an email address entered as a field in the form. In other words, a "return to sender" function. The button function has a submit to URL where you can use "mailto:[email protected]". How ca
-
IBooks Author-iTunes Producer publishing delivery problem
Why do I get an error message "Path specified for argument -f (/Users/tsoukadaris/Documents/������������/iBooks/10000422963.itmsp) is invalid.", since I've done everything needed and iTunes Producer has got me to the final step of publishing my iBook
-
Hello - my safari on my ipad2 gives the following message "safari could not open the page because the server stopped responding"...email works fine and I can download from the app store...seems to just be a safari issue