Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

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(5

Ok 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.

Similar Messages

  • 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.com

    Parsing through your rant which isn't directed at Apple, it seems you might be exceeding the sending limits included with a .Mac account which are not extreme by any means so take a deep breath and calm down.
    All internet service providers and email account providers (even free ones) have sending limits or restrictions for non-business/personal email accounts.
    These restrictions are in place as part of an overall effort to prevent spam emanating from an ISP's or email account provider's domain. In case you aren't aware, spammers make use of bulk spam mailings and these restrictions make it more difficult for a spammer to do his thing.
    It makes no difference that you aren't a spammer or the content of your message is not spam since there is no way an ISP or email account provider can make this determination when you send a message but they can impose sending limits or restrictions.
    Copied from the following link.
    http://docs.info.apple.com/article.html?artnum=25301
    .Mac has several safeguards in place to ensure that only .Mac members send messages with the Mac.com outgoing mail server. Among them are reasonable limitations on:
    * The number of messages that can be sent each day (200 messages)
    * The number of recipients that can be sent to each day (400 recipients)
    * The number of recipients a message can be addressed to at one time (100 recipients)
    * The size of outgoing messages
    There is also a 10 MB maximum size for messages sent or received using the .Mac mail system.
    .Mac Email has been designed primarily for personal use. Sending unsolicited bulk email messages through the .Mac email server is prohibited.
    If your message is being rejected by a recipient's incoming mail server, what is the return email error message provided which is sent by the recipient's incoming mail server?
    Regardless, this problem is with the recipient's email account provider. If the return email error message from the recipient's incoming mail server indicates the recipient has exceeded their allocated server storage space, this the recipient's problem.
    So instead of ranting, how about providing more detailed information about the error message provided so someone here can help narrow down where the problem lies so you can direct your efforts there.
    IMO - since you use your .Mac account for email only, you should cancel your account but keep in mind that even a "free" service includes sending restrictions which may not be identical to .Mac account restrictions but none are restriction free.

  • Mail nots being sent because of SMTP?

    Hey all I had to reset my Mail which caused my Server Ports to all go default. Does anybody know what the server port should be for the SMTP so that it will send mail out. Mine is set at 25 and I got help once with it and changed it and it fixed my problems. So if anybody knows of any server ports to try I would greatly appreciate it. Thanks again

    Is this email account and SMTP server provided by your internet service provider or other?

  • 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.

  • Outgoing mails are either being rejected or not being delivered - Exchange 2010

    Mails sent out to some domains not being delivered or being rejected;
    Receiving different errors as below:
    1.
    B6.7host.com rejected your message to the following e-mail addresses:
    '[email protected]' ([email protected]) <mailto:[email protected]
    B6.7host.com gave this error:
    unknown user <[email protected]
    A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
    Diagnostic information for administrators:
    Generating server: exchsrv.mydomain.com
    [email protected]
    B6.7host.com #550 unknown user <[email protected]> ##
    ====================================================================================
    2.
    Diagnostic information for administrators:
    Generating server: exchsrv.mydomain.com
    [email protected]
    #554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
    [email protected]
    #554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
    [email protected]
    #554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
    ======================================================================================
    3. --9B095B5ADSN=_01CF0B73B41F3F480004B263dub0?omc1?s26.du
    Content-Type: message/delivery-status
    Reporting-MTA: dns;dub0-omc1-s26.dub0.hotmail.com
    Received-From-MTA: dns;DUB127-W1
    Arrival-Date: Mon, 27 Jan 2014 03:18:13 -0800
    Final-Recipient: rfc822;[email protected]
    Action: failed
    Status: 5.5.0
    Diagnostic-Code: smtp;550 #5.1.0 Address rejected.
    ==========================================================
    For No. 2, I m seeing that the DNS name is not resolving. How can I be sure this issue is not from my side ?
    For No. 3, It seems to be some problem from that domain itself, and even mails from outlook.com are being rejected.
    Is there any best practice that I am missing out on ?
    How can these issues be resolved ?

    MX record of ju.ahg.com.sa seems to work via SMTP testing. 
    This was useing the MXtoolbox site. 
    Connecting to 78.93.11.251
    220 [874 ms]
    EHLO MXTB-PWS3.mxtoolbox.com
    250-S-34-8.AHGJU.COM.SA Hello [64.20.227.133]
    250-SIZE
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-XXXXXXXA
    250-XXXXXXXXXXXXXB
    250-AUTH NTLM
    250-XXXXXXXXXXXXXXXXXC
    250-8BITMIME
    250-BINARYMIME
    250-XXXXXXXD
    250-XXXXXXE
    250-XXXXF
    250 XXXXXXG [858 ms]
    MAIL FROM: <[email protected]>
    250 2.1.0 Sender OK [858 ms]
    RCPT TO: <[email protected]>
    550 5.7.1 Unable to relay [5897 ms]
    MXTB-PWS3v2 10390ms
    Seems to be ok, sent a test message to [email protected]
    and it seems to have gone through from were I am. 
    Check your Exchange Servers DNS settings. 
    Also, please let me know if you have a Edge server setup OR have your SMTP connect setup to use Smart Hosting.

  • Sent emails not being delivered from Outlook

    For the past week emails sent from Outlook although appearing in my Sent mailbox are not being delivered.  This is not a problem where emails are sent from my iphone.  I have made no settings changes.  This seems to be a familiar problem but research has not produced a solution as most people give up.
    I am using a Windows 8 laptop with Outlook 2013.  I have set up numerous new accounts with automated settings with no success.
    Please help!!

    I too knowingly have had this problem since at least 19/1/2015.
    I have Windows 7 with Outlook 2013 and two BT accounts plus Sky and Google accounts (for fallback). All have functioned well for the past three years.
    No changes to my PC have been made for at least 6 months (apart from MS updates).
    My wife's laptop runs Windows 7 with Outlook 2010 and has found the same issue. At a Womens Instutute meeting last night in the village it became apparent (without my wife initiating the issue) that a number of other BT eMail account customers have the same problem too.
    I spent about an hour yesterday trying various combinations of operation to confirm the issues. I have found:
    1 - eMails sent from either BT account self addressed will bounce back the eMails (presumably from the BT Server)
    2 - eMails sent from either BT account to BT accounts will not forward (send/deliver)
    3 - eMails sent from either BT account to non BT addresses will not forward (but will bounce back if the self address is included in the addresses showing that at least the eMail is reaching the BT mail server).
    4 - eMails sent from Outlook through Sky and Google systems are being received by the BT system and recieved into the Outlook BT accounts.
    5 - All eMails sent in Outlook appear in the Sent box
    6 - eMails sent from Webmail accounts all work normally
    All these tests can be replicated on my wife's laptop with other BT and non-BT addresses.
    I then spent about an hour whilst a BT Technician (ABHISHEK SEN) through CHAT accessed my PC, checked all settings and declared no fault found.
    Later I spent another hour on the phone to the BT Help Desk (with VIKRAM) who did much of the same, declared that there was a problem and that I would have to hire a local PC expert technician to come and sort out the problem on my PC. He would not acknowledge that there just might be a problem with the BT eMail Server system.
    Finally the only common thread is that the BT accounts are sub-accounts of my main account and that I pay the bills - and of course the router and copper lines to the exchange.
    HOW OR WHERE DO I/WE RAISE THIS ISSUE WITH A HIGHER AUTHORITY TO GET IT RESOLVED?
    Oh! And then there is the rest of the village and gwood's machine also need to have their similar issue resolved too.
    To use gwood's last paragraph: PLEASE HELP!!

  • Email not being delivered

    I am trying to send email from the icloud web mail.  all email is not being delivered.  When I send from iphone or ipad all works fine.  Icloud webmail can receive mail normally.  Email does show up in the sent mail folder but is not being delivered.

    I repeatedly and randomly have the same problem:
    1.   I send mail to another icloud user or to  some other recipient (e.g., yahoo mail).
    2.   The sent message appears in my iCloud.com Sent folder signifying that it was transmitted successfully.
    3.   The message is never delivered.
    4.   It does not appear in the recipient's Spam folder (or any other filter).
    5.   I never receive followup email from any server's postmaster indicating an error in transmission or reception.
    6.   The whole experience is purely silent -- "went to the bit bucket."
    There is no rhyme or reason to this.   The phenomenon is random but has repeated over a series of many months.   I could say that I am running 10.8.5, but it is an iCloud server event, not a local OS event.   The recipient might be running OS X, Linux, or Windows (etc).

  • 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

  • Pictures are not being delivered after saying delivered on iMessage.

    Pictures are not being delivered after saying delivered on iMessage.
    Txting through iMessage works fine. Pic's won't send.
    I turned on and off everything and did all the necessary trouble shooting.
    I'm on a Verizon 4S. and I'm sure Verizon has nothing to do with iMessage system, since it's on its on server.

    bump

  • Messages with zip files or multiple attachments are not being delivered

    Has anyone else come across this? I've discovered that files sent from my .mac account are not being delivered if they contain zip files or multiple attachment. A single .docx file goes through, but multiple doc files or a single zip file do not.
    I get no error message, and neither does the recipient. The message sends on my end but simply doesn't show up on their end.
    Any thoughts on what might be causing this?

    Another follow-up: Now, for whatever reason, even attachments of a single document aren't going through.
    Again, I'm receiving no error message, and it shows up in my sent folder. It just never makes it to the recipient.
    This is very frustrating, and makes my iCloud mail account all but useless. Does anyone have any idea at all what might be happening?

  • Messages in queue not being delivered

    Hi
    I am using IMS 5.2. After a recent migration of user accounts to an new login ID, some user's emails are not being delivered to thier accounts and are accumulating in the ims-ms queue. When I did the migration, I copied the user's email to thier new account. I did reconstruct -f -r a couple of times, and emails appeared to be delivered to the new login accounts.
    There were a few emails left in the queue but now there are close to 6000 and users are not getting emails delivered. When I look at the message in the queue, they state the user is overquota. I checked the user's account and they are not overquota.
    Any suggestions on how to correct the problem or get the message to be delivered?
    Thanks
    Randy

    Jay,
    iPlanet Messaging Server 5.2 (built Feb 21 2002)
    libimta.so 5.2 (built 15:07:23, Feb 21 2002)
    SunOS cpmail 5.8 Generic_108528-27 sun4u sparc
    SUNW,Ultra-60
    This is the original release. There have been over thirty patch/hotfix releases, and hundreds of fixes. I URGE you to go to Sun's download site, and get 5.2p2, and install it immediately.Thanks for the advice Jay. The product is installed as part of the portal we are using(which I upgraded last June). I was unaware of the versioning and patches that are associated with the version of IMS that was installed. I will move forward with confirming with our portal vendor that the latest sp and patches will support the integrated IMS.
    >>
    >>
    How did you "migrate" your users to new login id?When you "copied" the files, did you re-set
    ownership/permisions of the files?
    I used the following process in a script to migrate
    the users from old login to new login:
    1. created the new login mailbox with mboxutil -c
    2. moved new mailbox to different partitions
    There is a utility/command that does all of this for you.
    mboxutil -r
    When you "moved" the mailbox, I assume you use unix cp, right? Bad Idea.
    current versions of mboxutil do this all for you, and don't need reconstruct afterwards.
    I suspect that you have either not properly "moved" your user in LDAP, folder database, or have gotten file ownership or permissions wrong after the move.
    Unix files are owned by a user and group, and have various read/write permissions set by the OS. YOu're on a Unix system, so you should know about such.I tried using the mboxutil -r initially but was getting a lot of errors with it in my test environment. In hindsight, I am thinking this had to do with the version of IMS I have installed. The unix file move was done with the IMS admin so would also own all the the messages etc on the OS side. I have obviously made a mess of things! So again, I will put in a support call to our portal vendor about how to proceed on this. I really appreciate your input into this.
    3. retrieved hashed directory information for old and
    new mailbox for user
    4. copied files from old to new mailbox with cp -R
    oldmailbox/* newmailbox/
    5. after all users were migrated, I did a reconstruct
    -f -r, and a reconstruct -f -m
    I am not sure what you mean by re-set
    ownership/permissions.
    Have you looked at the "default" log for an errormessage?
    I found the following errors in the default log:
    default.60.1093908097:[31/Aug/2004:04:15:01 -0600]
    cpmail stored[28697]: Store Critical: Error checking
    mailbox database: Ignoring log file:
    /usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
    00543: magic number 0, not 40988
    default.62.1094084554:[02/Sep/2004:04:15:02 -0600]
    cpmail stored[20883]: Store Critical: Error checking
    mailbox database: Ignoring log file:
    /usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
    00543: magic number 0, not 40988
    Your reconstruct command may have been wrong, too. That's what the errors are telling you.
    Also, there are other problems in your system. Permission problems, most likely.
    I would do a reconstruct -m, first. and see if the above goes away.I will proceed with what you suggested, and let you know the results. Again, thank you very much for your time and input for this.
    >>
    >>
    AS well, when I do a mboxutil -u on an affected user,
    the quota information says the user is well under
    quota. For example:
    $ mboxutil -u xxxxxxxxx
    diskquota size(K) %use msgquota msgs %use user
    25600 2604 10% no quota 19
    19 xxxxxxxxxxx
    The error message doesn't really have anything todo with quota.>>
    >>
    In imta/queue/ims-ms, the user has 183 messages
    waiting to be delivered. All of the messages say the
    user is over quota.
    Any suggestions?
    Randy, you need to re-think how you're moving users. You have somewhat messed up your mailstore. . . I will in re-think things. In fact, I have a number of users to migrate. I will stop what I am doing and get this right before I proceed! There is no sense compounding the problem when there is a better alternative. One thing for sure, I will continue using this forum before I proceed with messing with a production system!
    You may need to contact tech support for the immediate help you will need to straighten this all out.>>
    >>
    RandyThanks Jay.
    Randy

  • E mail not being received

    Hi, I use BT yahoo mail through outlook 2010, sent mails show as sent in outbox, i get no error message but they are not going to recipients. I have deleted account and re set up in outlook i am using the IMAP settings as on the BT web site. When i send mail from my apple devices using same e mail account they are recieved ok? Any ideas ? Thanks in advance.I should add when i set up account in outlook and hit test message that gets received ok . In additon I can send myself emails using outlook.

    I suspect that you may have the same issue as
    https://community.bt.com/t5/Email/One-particular-recipient-not-receiving-my-Outlook-mail-but-can/td-...
    https://community.bt.com/t5/Email/e-mail-not-being-received/td-p/1343373
    https://community.bt.com/t5/Email/Cannot-send-emails/td-p/1343253   
    One solution may be to temporarily change your SMTP server to 
    smtp.mail.yahoo.co.uk

  • Lion Server DNS service not working for locally created zones. Caching working fine.

    OS Lion Server DNS service not working for local zones. Was fine under Snow leopard server but Lion server upgrade has severely broken my DNS and web sites. Zones look fine under Server Admin but keep getting "query failed (SERVFAIL) for xxxx at /SourceCache/bind9/bind9-42/bind9/bin/named/query.c:3921" in the logs. BTW - Server Admin cant seem to see the log file either.
    Surely someone actually tested that DNS still worked on Lion?

    I upgraded from Snow Leopard Server to Lion Server on day 01.  I hit the same issue where, after the upgrade, my Lion Server stopped serving names for my private local domain.
    I finally took a few minutes to figure out what was wrong.  After turning on debug logging and looking through the logs, I found my particular issue, now resolved.
    The issue I had was, when the domain initially was setup when I installed Snow Leopard Server, for some reason it created a zone just for the server (in my case, something like zone "s-01.mydomain.priv"), and a separate zone for all the other machines (zone "mydomain.priv", containing all the private IPs for my local domain).  I never messed with it because it worked, but generally I would have put all of them in the same zone.
    My zone "mydomain.priv" had a nameserver and mail exchanger entry for my server, s-01.mydomain.priv.  I could see this in the Server Admin app on the DNS bubble, Zones tab, mydomain.priv selected, and the General Info panel.  This was fine in Snow Leopard.  This was failing the zone load in the updated bind for Lion Server, though.  The issue was that the "mydomain.priv" zone was referencing the s-01.mydomain.priv server, which was not defined in the "mydomain.priv" zone but rather in the "s-01.mydomain.priv" zone.
    My fix:
    1. In Server Admin, add the server to the zone "mydomain.priv".  I put an A record (Add Machine) in the "mydomain.priv" zone for my server named s-01.mydomain.priv.
    2. shut down DNS on the OS X Lion Server (hit the Stop DNS button on Server Admin).
    3. edit /etc/named.conf by hand, removing the specialized zones that contianed just the server.  In this case, it would be the section titled 'zone "s-01.mydomain.priv"' and the section titled 'zone "3.10.1.10.in-addr.arpa"'.  Your in-addr.arpa zone name will change based on whatever your server IP address was.  My internal one happened to have s-01.mydomain.priv mapped to 10.1.10.3.
    4. Once the specialized zones for just the server were removed, I started the DNS up again.  Instead of serving four zones as it had in OS X Snow Leopard Server, it now servers two zones.  And, now, it is resolving my local machines for the mydomain.priv zone.
    YMMV.  I did note that it wasn't totally necessary to do step 3, but I never really understood the need for the specialized domain, and keeping it around would have a copy of data that would just confuse things.
    Hope that helps.  That's been the only hiccup I've noticed updating to OS X Lion Server thus far.

  • Is anyone having issues with imessages disappearing or not being delivered?

    Is anyone having issues with imessages disappearing or not being delivered?

    I too am experiencing this on my iPhone 4 after upgrading to 4.3.3. I am fairly convinced that it is a software issue. The last update seems jumpy. There appear to be more pauses and stuttering with screen changes too.  Sometime the button operates perfectely (even with repeated light touches). Other times, it doesn't matter how hard I press; it takes several presses. I notice it more when i am using a battery case or connected to an AT&amp;T MicroCell. I am having a hard time pinpointing problematic apps, although i suspect that mail with my work Exchange account may be a culprit. I suggest posting your issues on Apple's iPhone feedback page, www.apple.com/feedback/iPhone.html, to ensure that they are looking into this problem. If it is a hardware issue, I'll be pretty upset as I received my iPhone 4 on day 1 of availability and it is out of warranty. Hoping for a fix with an update. Please post on the feedback page.

  • Unity 9.1.2 - VM not being delivered to Outlook

    Hello All,
    VM is not being delivered to user's Outlook, when anyone tries to leave a message it disappears in a couple of minutes and does not get delivered to Outlook, message count from Unity Admin page shows 0.  If Unified Messaging is disabled the messages don’t disappear.
    Unity Connection version 9, if anyone encountered this issue or has any ideas please let me know.
    Thanks,
    AK

    If they don't disappear when UM is disabled I would suspect that the outlook client is deleting them or sending them to junk mail.  I had a situation once where I had to change the default smtp domain from @ to @company.com in order for the Exchange/Outlook powers NOT to junk the voicemail.  I also has the side effect of allowing the users to reply to the VM messages using the Outlook client, so it was a win-win.
    you could also change the Exchange policy, never tried this.
    http://www.cisco.com/c/en/us/products/collateral/unified-communications/unity-connection/guide_c07-728014.pdf
    disclaimer to consider though
    https://supportforums.cisco.com/docs/DOC-16892
    Kasey

Maybe you are looking for

  • Get Document ID based on specific folder in SharePoint 2013 document library

    Hi, I have created document library with multiple folders in SharePoint 2013.I have created workflow to assign file name convention like this "attachment name-ID".When i created document in one folder the ID is 1 and when I created document in anothe

  • Yoga 2 13 still loud as hell -- why this is a failure

    I never wanted to write this post, but it's very hard at this point not to say that the Yoga 2 13 is a failure. The third generation is now available with the Yoga 3 Pro and Yoga 3 14 and somehow, the Yoga 2 13 is fallen in a black hole where nobody

  • Problem in Picking the file in  FTP to RFC Scenerio

    Hi, I am using FTP to RFC scenerio, i have a CSV file and need to use file Content COnversion at the sender Communication Channel. But its not picking up the file from my  FTP.. My data is like 11    Munish     IT My Message Type is like : MT_ABAPPRO

  • Why wont my Ipod 5 front camera work?

    Why wont my Ipod 5 front camera work I tired restarting it but its not doing anything

  • HR module for Personal administration

    Hi all, I am new to HR module ,i Need to implement Personal administartion in BI 7.0 . To achieve one report i need to enhace 0EMPLOYEE_ATTR, 0EMPLOYEE_0022_ATTR  ans some other datasources also with some additional fields like baseloaction,Universit