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!
Greg
Hi,
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
Similar Messages
-
A magnifying glass and search box show up in my e-mails and I can't read them unless I hit reply or forward. how do I get rid of the magnifying glass and search box?
First, some clarification:
* The location bar (often called the "awesome bar") is the larger bar on the left that shows you the address of the page you are currently viewing. As you type in the location bar it searches your history and bookmarks for matches.
* The search bar is the smaller one on the right. It typically displays an icon of whichever search engine is currently selected and may display search suggestions as you type in it.
It sounds like you are referring to the search bar rather than the location bar. You can change search engines for the search bar by clicking on the icon on the left edge of the search bar and choosing a different one. You can also choose "Manage Search Engines" to remove ones you aren't interested in using.
It also sounds like Bearshare might have changed your homepage in Firefox. To restore that you will need to open the preferences menu (click Tools > Preferences), go to the General tab (first on the top left), and click "Restore to Default". -
What is the best charging cable for the iPad Air (that is not made by Apple)? I need a long cable (over 6ft or more). I also need the cable to be of high quality and the cord part of the cable to be made of strong material. Apple does not make one this long. Is there a cable out there that is sturdy like this and is safe to use?
yes, but I'm trying to use my iPad to type notes (using pages) and I have the smart case which I use as a stand. I need a cable long enough to fit through the back of my desk and the charging brick for the iPad won't fit behind the desk. I have to put it on the floor and then the apple cables aren't long enough to reach.
-
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. -
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 -
I have looked everywhere for this icon. I was looking at a video and all of a sudden my screen changed and I had a pop up asking me to hide. I thought I was hiding the strange pop but my @ icon disappeared instead. I looked in applications and do not see it anywhere.
If you mean the address field in Safari, choose Show Toolbar or Customize Toolbar from the View menu.
If you mean the spring icon in the Dock, that's not an application. Open any site in Safari and drag the little icon of it to the Dock; the preset icon points to http://www.apple.com/macosx/
rkaufmann87: The Safari Dock icon doesn't contain an @, and no other Mac web browser icon I've seen does.
(59088) -
Fast user switching and "ipod is in use by another user on this computer"
Is there any way to suppress the "ipod is in use by another user on this computer" message that appears when you use fast user switching.
my wife and I share a mac pro and when flipping between sessions, this message gets to be a bit annoying. i.e. if her itouch is plugged in and she is managing it through her library, if I fast user switch to my session, I get the warning dialog (ok to clear) I mention above. This is kind of annoying now, since I understand I won't be able to manage that ipod from my itunes session.
is there anyway to suppress this behavior?Hi again,
Glad to hear you got all your music files back into your library.
I've seen this iPod error before, but I don't know why it occurs. In my experience, restarting the computer solves the problem.
Cheers,
Sara. -
Redirect internal email sent to a distribution list to another user mailbox
Dear all,
We are running on Exchange 2010 and would like to know if it would be possible to redirect email sent to a distribution list to another mailbox if source is internal, meaning from address is *@company.com
Let me explain: We have a DL like [email protected] and a ticketing system which checks a mailbox [email protected] on a regular basis.
We would like to redirect only the messages from our users to helpdesk in order to automatically create cases for their problems.
Have been checking EMC and ADUC but couldn't find anything related to this.
Kind regards,
Tudor.Hi,
Yes, creating transport rule will achieve the goal.
Glad to know that we have solved this problem.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Voice mail not being delivered
Cisco Unity 4.0(4):
Error message stating:Event Type: Error
Event Source: CiscoUnity_UMR
Event Category: UMR Thread Error
Event ID: 137
Date: 10/6/2008
Time: 12:26:46 PM
User: N/A
Computer: COBUNITY1
Description:
Attempts to deliver Unity Message Repository messages have failed due to Unity configuration or connectivity issues with the Partner Mail Server.
AvUMRSyncSvr will suspend message delivery for 300 seconds, after which message delivery will be attempted again.
During this outage, messages may accumulate in the temporary store. 0x00000F58
All the undelivered messages can be found in UnityMTA folder. Is there a service I can start and stop to get the voice mail moving out to the intended recipients?Actually the UMR service (AvUMRSyncSvr). Type services.msc under Run in the Unity service to access the services.
Also make sure that Unity is running, on the system tray check if it is up or on the services itself. -
I sometime need to send attachments such as pegs to a Uscg.mil address. The attachments do not show up to the addressee, and it is probably due to a security firewall on the military side. However, the same attachment goes through fine if sent using web mail (Gmail). There must be some difference in the way Apple embeds an attachment that causes it to be rejected by the military security firewall. Any thoughts on this?
Did you ever find a solution to your problem sending email with attachments? I am getting the same message - "please select a different server" when I try to send emails with attachements...VERY FRUSTRATING...!
-
I have tried numerous solutions being posted in this support forum. I went in and deleted my places.sqlite file so that it created a whole new profile. I then tried to restore my bookmarks, and nothing happened.
I went in and discovered I had a places.sqlite.corrupt file. As suggested by one of the links provided in other articles, I deleted the other places.sqlite files, and then renamed the corrupt one as just places.sqlite. I restarted firefox and still nothing.
Please don't just copy and paste the links to the two articles that have no yet helped me. I need to find out how to fix this because I had a lot of important information in my bookmarks!Hi,
You can try creating a [https://support.mozilla.org/en-US/kb/Managing-profiles new profile], copy the '''bookmarkbackups''' folder from the old profile to the new and '''Restore''' a dated backup via Firefox '''Bookmarks''' ('''Alt''' + '''B''') > '''Import and Backup''' on the new profile.
To open the profile folder within Firefox: '''Help''' ('''Alt''' + '''H''') > '''Troubleshooting Information''' > '''Show Folder'''.
[http://kb.mozillazine.org/Profile_folder Firefox Profile Folder]
[http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder & Files]
You can also try to [https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems Reset Firefox] on the old (previous) profile via '''Help''' ('''Alt''' + '''H''') > '''Troubleshooting Information'''. -
I do not know what the problem is, but after the latest update it is really hard to send text messages. It is taking alot of time to send the messages, it is not the problem with the carrier because sending text messages with the same number in the same area is really easy on my normal nokia 1100. Please suggest me what I should check. Second problem I am facing is the carrier signal drops to nothing when I turn on the cellular data. It has to then search for the network and connect again the same happens when I turn the data off again. Please tell a solution. I do not think it is the problem with the hardware because the phone is hardly 2weeks old and everything was working properly with ios 6. It initaly had problem with the battery on updating to ios7 but that was rectified with the new update but again these are the new issues am facing.
This may sound stupid, but I'm gonna throw it out there anyway. Is it possible, that if I have enough junk on my desktop it might disrupt the signal? It seems odd, but it kind of looks like my signal is strong and relatively steady now that I've cleaned my desktop. I do tend to get very cluttered. I use a lot of reference images and save text clippings to use later... it just piles up very quickly.
So, I wonder if all that extra effort my system has to do keeping up with the junk might have something to do with the drop outs? -
Best way to not allow more than one user on page.
Do not want another user editing a record on a page when another user is on that page. Any ideas on the approach I should use?
Please provide more information. What you describe is the normal, default situation anyway.
A thousand of us have opened a page. Our browsers each caches a copy of the page. So, in normal circumstances, one is not really on the page. If the 1001st client were to open the page and edit the record, we wouldn't be aware of the change till we refresh or revisit the page. -
"message could not be delivered"
MAILER-DAEMON are replying that message can not be delivered when sendin to my mac addresses!?
this started last night.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.Nothing made sense I thought but I just recieved an answer from my web host and they explained it like this:
Our technicians are aware about this issue and they have contacted the proof point support to get the block removed
This should be done in the next couple of days and then you shoudl be able to send emails without any issues
No explanation though why there was a block.
Thanks
Maybe you are looking for
-
How can I get music onto my 2nd gen iPod Touch?
My mum recently gave me her old iPod, a 2nd gen. My sister tried to upgrade it up to iOS 5 but couldn't. Every time I plug my iPod into charge it pops up in iTunes saying, "This iPod cannot be used because it requires iTunes version 10.1 or later. Go
-
ITunes 10.4 can't drag songs into playlists
There is one glaring difference in the new iTunes 10.4 (80). I can't drag songs from one playlist to another. It doesn't matter whether the source is a smart playlist or a regular dumb one, or even the main music library. smart playlist or dumb playl
-
Hi All, I need to add 4 new fields to "Status" screen of FD32 transaction. I cannot use the already existing standard fields so I need to add custom fields. I have searched the forum and found the following enhancement and BADI : RFDRRANZ FI_DUZI_ROU
-
Expecting a respone withing a specified time frame
I need urgent help please. I am expecting some data from the server within 20 seconds. If I dont receive this data within the time frame,I exit from the application else If i receive this data I will display it. Please can any write a small example f
-
I need help accessing my final cut movie.
Okay, so I've been at college working on a final cut project, and I was almost done, but then I came home. I made the file in the latest final cut express, and now I'm trying to open the file in final cut pro 4.5 However, when I try to open it, it in