Upgrade from Lion Server to ML 10.8.1 Broke Mail server!

....10.8.1 OD seems to work, files and AFP available, but Mail server not working correctly.  Now users don't see mail, postfix issues numerous errors about missing system_user_maps and delivers no mail?  Must recover mails!  Help!  Where should I look, and what to read for Diagnosis ?
After upgrade in place from SL to Lion to ML. most services did not work correctly; except for Mail and DNS and OD.   Reinstalled.   Now most everything seems to work including Card Services, Calendars, Wiki, Web, DNS, OD.  But Mail is off and missing???  No delivery of INcoming mail, No Sending Mail, no IMAP Mail login for users.
On Mail configuration in Server.App:  Turned off All Filtering. Have rebooted Server several times,  Restarted Mailserver from Server,app and Terninal.   Same Results.  Somewhere along the line from Server 10.5 to SL to Lion to 10.8  incoming Maill started going to [email protected] rather than simply [email protected].
    Is it possible that virtual domains are fuzzing up the works?  The error logs use the longer virtual domain (with the sevrer name prefix) rather than the domain name?
Here are some sample Log messages:
From SYStem Log:
Sep  7 19:33:56 plg1.plg-law.com postfix/cleanup[1998]: warning: 8273B199E3F8: recipient_canonical_maps map lookup problem for [email protected]
Sep  7 19:33:56 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ECF3A196A4FE: error writing 8273B199E3F8: queue file write error
Sep  7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: E5AC9199E3F9: message has been queued for 1 days
Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep  7 19:33:58 plg1.plg-law.com postfix/cleanup[1998]: warning: E5AC9199E3F9: recipient_canonical_maps map lookup problem for [email protected]
Sep  7 19:33:58 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/ED4AB196A4FF: error writing E5AC9199E3F9: queue file write error
Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep  7 19:33:59 plg1.plg-law.com postfix/cleanup[1998]: warning: 385DD199E3FB: recipient_canonical_maps map lookup problem for [email protected]
Sep  7 19:33:59 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/EE2A9199B211: error writing 385DD199E3FB: queue file write error
From SMTP Log:
Sep  7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: 3652E199E487: uid=78 from=<_mailman>
Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps is unavailable. open database /etc/postfix/system_user_maps.db: No such file or directory
Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: hash:/etc/postfix/system_user_maps lookup error for "[email protected]"
Sep  7 19:35:24 plg1.plg-law.com postfix/cleanup[1998]: warning: 3652E199E487: recipient_canonical_maps map lookup problem for [email protected]
Sep  7 19:35:24 plg1.plg-law.com postfix/pickup[1324]: warning: maildrop/8E82B199AD06: error writing 3652E199E487: queue file write error

here's my configured postfix main.cf file from /etc/postfix/main.cf   (mountain lion server 10.8.1)
Server.app should have somewhat configured it correctly for you in someways, but something got messed up in the import script I guess.
Hope this helps...
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, 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 = /Library/Server/Mail/Data/spool
# 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
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /Library/Server/Mail/Data/mta
# 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) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception:  delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for   
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for   
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients.  By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for   
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter.  The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
           PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
           xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
#          PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#          echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#          >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
#          PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#          -dmS $process_name gdb $daemon_directory/$process_name
#          $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = /usr/share/doc/postfix/html
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
#======================================================================
# dovecot
dovecot_destination_recipient_limit = 1
# default mailbox size limit set to no limit
mailbox_size_limit = 0
# List of ciphers or cipher types to exclude from the SMTP server cipher
# list at all TLS security levels.
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
# Protect SSL/TLS encryption keys
tls_random_source = dev:/dev/urandom
# (APPLE) Credentials for using URLAUTH with IMAP servers.
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
# (APPLE) The SACL cache caches the results of Mail Service ACL lookups.
# Tune these to make the cache more responsive to changes in the SACL.
# The cache is only in memory, so bouncing the sacl-cache service clears it.
use_sacl_cache = yes
# sacl_cache_positive_expire_time = 7d
# sacl_cache_negative_expire_time = 1d
# sacl_cache_disabled_expire_time = 1m
#======================================================================
mydomain_fallback = localhost
message_size_limit = 104857600
biff = no
mynetworks = 127.0.0.0/8,www.yourvirtaldomain.com
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject_rbl_client zen.spamhaus.org permit
recipient_delimiter = +
smtpd_tls_ciphers = medium
inet_protocols = all
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
recipient_canonical_maps = hash:/etc/postfix/system_user_maps
smtpd_use_pw_server = yes
smtpd_sasl_auth_enable = yes
content_filter = smtp-amavis:[127.0.0.1]:10024
inet_interfaces = loopback-only
smtpd_helo_required = yes
smtpd_pw_server_security_options = cram-md5,gssapi
header_checks = pcre:/etc/postfix/custom_header_checks
smtpd_tls_CAfile = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.chain.pem
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
relayhost =
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks  reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_enforce_tls = no
smtpd_use_tls = yes
enable_server_options = yes
smtpd_tls_key_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.key.pem
smtpd_tls_cert_file = /etc/certificates/computer.yourdomain.com.D800DD955D66179EEA4321DAA0617A19FFCD1 5C1.cert.pem
mydomain = yourdomain.com
virtual_alias_maps = $virtual_maps hash:/etc/postfix/virtual_users
virus_db_update_enabled = 1
mailbox_transport = dovecot
postscreen_dnsbl_sites = zen.spamhaus.org*2
maps_rbl_domains =
virtual_alias_domains = $virtual_alias_maps hash:/etc/postfix/virtual_domains
config_directory = /Library/Server/Mail/Config/postfix

Similar Messages

  • Mavericks Mail not working properly with Exchange server after upgrade from Lion

    Mail will no longer maintain a stable connection to my company's Exchange server after upgrading to Mavericks from Lion.  Nothing has been changed on the Exchange server.  It has only partially downloaded the messages that are on the server.  It seems to download current messages when they hit the server.  It has difficulty sending messages.  When I send a message, it gets stuck in the Outbox.  It is constantly losing the connection to the server.  The problem is only occuring with Exchange email.  My iCloud email works properly as well as a POP3 account.

    No shortage of pre-existing threads on Mavericks mail issues...
    https://discussions.apple.com/message/23706759#23706759
    https://discussions.apple.com/message/23469853#23469853
    https://discussions.apple.com/message/24277596#24277596
    https://discussions.apple.com/message/23769976#23769976
    https://discussions.apple.com/message/19077388#19077388
    https://discussions.apple.com/message/24170482#24170482
    https://discussions.apple.com/message/24483692#24483692

  • Hi i upgrade from lion to mountain lion to day on my mini mac,Since the upgrade i am getting no sound through my HDMI cable which was working fine on lion Checked the midi audio settings and system preferences to out on HDMi nothing no sound whats so ever

    Hi i upgraded from lion to mountain lion to day on my mini mac,Since the upgrade i am no longer getting sound through my HDMI cable which was working fine on lion Checked the midi audio settings and system preferences to out on HDMi nothing no sound whats so ever.Any one any ideas?
    I use a samsung TV for my monitor via HDMI.Tried all the system Audi setting nothing .Head phone and internal speakers are fine.

    Similar issue; Audio was working fine on Lion, now not on Mountain Lion. Have a Macbook Pro early 2011 with AMD Radeon HD 6750M, connected by thunderbolt through a Lacie LBD to a mini-displayport to HDMI adapter (n.b. same problem when not going through the LBD) to a Pioneer VSX 521 AV receiver. For me when I go into audio Midi settings all the volume sliders for the displayport device are greyed out and at zero. But when I click 'configure speakers', it's able to send out the test signals to each speaker. Part of the problem could be that I'm not getting the option to put out 6channel sound, only 2 or 8 channel. Since my system is Dolby 5.1, and I only have 6 speakers, I would have expected the 6ch option to be available. But I imagine there's more to it than that. Elsewhere someone has suggested playing with Remote Interactive over HD on an Onkyo device; I'll see if there's something similar on the Pioneer that can be changed. Any other suggestions welcome.

  • Windows 7 no longer boots after upgrade from Lion to Mountain Lion

    I got a late 2011 MacBook Pro, on which I installed Windows 7 with Boot Camp. After I upgraded from Lion to Mountain Lion, I can no longer boot Windows. If I keep the option button pressed during boot I only get the OS X and recovery options, and if I choose to boot Windows from the system preferences pane, I get a message that says that no bootable device was found. However, I'm sure that the partition is still there, because I can see it in finder and browse the files normally. How can I boot Windows again?

    "Easier" in this case as an alternative is defined as repartitioning/reformatting your disk, and restoring from backups (which for most people also means starting from scratch with Boot Camp Assistant and Windows since most users aren't backing that environment up).
    What you did is, in my opinion, easier and faster. But if you don't know what you're doing can lead to data loss. But then, by definition, blowing away your disk and starting over with a restored backup begins with data loss!

  • While intending to perform a clean install of Mountain Lion while continuing with old apps and files, is it a waste to restore a backup that was made while running Mountain Lion as an UPgrade from Lion?

    While intending to perform a clean install of Mountain Lion while continuing with old apps and files, is it a waste to restore a backup that was made while running Mountain Lion as an UPgrade from Lion?
    Originally I was running Mountain Lion as an UPgrade from Lion. I created a backup in Time Machine, performed a clean install of Mountain Lion, then I proceeded to use Time Machine to restore the back up.
    When thinking about the essence of a back up restore, it occurrs to me that for all I know, I may have just wated my time IF Time Machine also restores all the old unneeded files that remain from Lion after an upgrade.
    Since the backup was made while running Mountain Lion as an upgrade from Lion, did restoring this backup defeat the purpose of a clean install by reinstalling old Lion files?
    If so, how can I re-do the last portion of the process so that I get all my home-folder files and apps back without the full bulk of old Lion files? Migration assistant I'm guessing?
    -Chris

    Hello John!
    Thank you for your response which solved my problem. For other users who may stumble upon this, I'll clear up the confusion and share how I solved the problem with your help; When looking for answers to my computer problems, finding unresolved questions where person B offers a solution and person A never comes back and says "That worked, thank you.", it demonstrates a "k-thnx-bye" user mentality that leaves others with the same problem lost. Without further ado:
    It is not clear what you did because the meaning of "clean install" is vague. You can erase a volume and install an OS which leaves none of its previous content intact,
    This is what I did: I erased the volume leaving no previous content intact, while then installing OS X Mountain Lion.
    or you can upgrade an existing OS (or reinstall the same one) which does not alter your user - installed files.
    An upgrade to Mountain Lion from Lion is what I started with initially before erasing anything. This was undesirable. Since this can cause Macs to run slower (especially whereas I'm using a mid-2011 Mac Mini), my goal was to go from operating within an upgrade to Mountain Lion, to operating within an installation of Montain Lion that was not preceded by any other oprating system.
    Hence a "clean install of Mountain Lion while continuing with old apps and files" is confusing.
    Well put and understood. What I should have said was:
    1.Erase the volume
    2.Install Mountain Lion clean
    3.Confirm that Mountain Lion is functioning properly
    4.Proceed to use either Time Machine or Migration Assistant to Import/Migrate/Copy over only two things; My old apps (That had been stored originally in the designated Applications folder) and all files and folders originally stored in the home folder under users.
    If you restore from a Time Machine backup then all modifications that occurred subsequent to that backup become erased. It renders moot any OS X upgrade performed subsequent to that backup.
    That makes sense and is just as I later suspected.
    If so, how can I re-do the last portion of the process so that I get all my home-folder files and apps back without the full bulk of old Lion files? Migration assistant I'm guessing?
    Yes.
    This is what I did and everything works perfectly. Thank you so much once again!
    -Chris

  • Need help upgrading from Lion 10.6.8 to Lion 10.7.2.

    I want to upgrade from Lion 10.6.8 to Lion 10.7.2 in order to use iCloud that is on my other devices.  The software updater on my Mac says there are no updates available.  What to do to get the latest OS?

    10.6.8 is Snow Leopard, not Lion. Lion is 10.7.x. Select About This Mac from the Apple menu. The installed version will be shown in the display window.
    If you are running 10.7 or 10.7.1 you can download the OS X Lion Update 10.7.2 Client Combo.

  • How can I upgrade from Lion OS X to Mountain Lion OS X

    Hi my question is "How can I upgrade from Lion OS X to Mountain Lion OS X?"
    I don't want to lose any data from my current Lion OS X, at the same time I don't have enough external HDD to backup. I tried to do the same was as http://www.apple.com/osx/how-to-upgrade/ says but I didn't get Mountain Lion OS X as an option for update.
    Pleade advice,
    Mustafa

    Well, right.  In 99.99% of cases you shouldn't lose any data.
    But if something goes wrong, well, if you don't have a backup you're SOL.
    You truly don't have ANY drive that you're using for Time Machine?
    FYI: It's not a matter of IF, but WHEN, your hard drive will fail.  It will eventually happen, so you should have a backup, unless you don't have any data you care about.

  • What are the benifits of upgrading from Lion to Mountain Lion?

    I'm looking for the benifits of upgrading from Lion to Mountain Lion

    You cannot upgrade to Mountain Lion anymore. Mavericks is now the current version. Got to Apple's website to see what the features of Mavericks are, then decide if upgrading is something you should do.
    Upgrading to Mavericks
    You can upgrade to Mavericks from Lion or directly from Snow Leopard. Mavericks can be downloaded from the Mac App Store for FREE.
    Upgrading to Mavericks
    To upgrade to Mavericks you must have Snow Leopard 10.6.8 or Lion installed. Download Mavericks from the App Store. Sign in using your Apple ID. Mavericks is free. The file is quite large, over 5 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
          Macs that can be upgraded to OS X Mavericks
             1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
             2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
             3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
             4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
             5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
             6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
             7. Xserve (Early 2009) - Model Identifier 3,1 or later
    To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
         Are my applications compatible?
             See App Compatibility Table - RoaringApps.

  • Why would upgrading from Lion to Mountain Lion more than double the size of my Time Machine backup?

    I have a 500GB Time Capsule that has 248 GB used. After upgrading from Lion to Mountain Lion, Time Machine reported that there was no longer enough room on the TC to complete the backup. Surely the new system files aren't taking up over 200GB? Does it somehow want to copy all of my user files again, even though the vast majority of those haven't changed since the previous backup?
    I'd like not to have to upgrade to a larger TC just because of a system upgrade.
    Thanks in advance.

    If it is working as expected, what do you need with the old backup?
    If you want to be able to go back to where you were prior to an upgrade, isolate that backup and don't use it again. As far as Time Machine can tell, the whole drive changed.
    The link I posted contains probably everything that anybody knows about Time Machine and how to manipulate it to work as you would like as opposed to how it was designed to work. There are FAQs to continue a backup as opposed to starting fresh, but I wouldn't recommend it for the reasons above. Pondini probably doesn't, either.
    If you are going to do a wholesale upgrade of the OS, I would create a bootable clone using something like Carbon Copy Cloner or Super Duper. A bootable clone on an external drive can have you back up and running instantly if the upgrade fails in any way. If the upgrade goes fine, store it away in case you find the current system isn't to your liking.

  • Can I upgrade from Lion OS X 10.7.5 to Mavericks 10.9.4?

    Can I upgrade from Lion OS X 10.7.5 to Mavericks 10.9.4?

    Yes, if your Mac is compatible; the Mac App Store will check this before allowing the upgrade to be downloaded.
    (111277)

  • Can't upgrade from Lion 10.7.4 to 10.7.5.

    I keep trying unsuccessfully to upgraded from Lion 10.7.4 to 10.7.5.  I keep getting an error that says to power down and restart after the upgrade.  Is there a work around for this?  I'm worried that my security updates aren't being done.  I also cannot upgrade from Lion to Mountain Lion either.  I have successfully restored everything from time machine backup several times.  Just can't update.  My MBP is a late 2008 5,1.  In an effort not to flood this forum, my specs are at http://pastebin.com/kCdgnG5T. 
    Thanks,
    tsairox

    I've tried the MacOSXCombo update with pressing the Option key upon restarting with no success before my first post here (then restored the whole system), but not the Shift key you're speaking of.  Do you feel this will make a big difference?
    Thanks,
    tsairox

  • I don't want Mavericks yet, how do I upgrade from Lion to Mountain Lion?

    Been reading lots of good and bad about Mavericks so I'm not ready to upgrade from Lion to Mavericks yet.  I would like to upgrade my OS to Mountain Lion.  How can I do this when the App store doesn't offer Mountain Lion anymore?
    Thanks

    http://store.apple.com/us_smb_78313/product/D6377Z/A/os-x-mountain-lion-consumer -single

  • How do I upgrade from Lion to Snow Leopard?

    Snow Leopard has this great feature called Expose which is a great improvement on Lion's App Expose (and Mission Control).
    Can someone point me to the steps I need to take to upgrade from Lion to Snow Leopard?

    Written just for you (ok it's a paste)
    Back to Snow Leopard from Lion install method
    Read and print out these instructions, your computer is going to be offline and you wil be cutoff from help until your machine is restored.
    Clear the Desktop, Downloads and Trash of anything you wish to keep by placing their files in the respective Documents, Music, Pictures, Movie folders.
    Disconnect other drives except the backup drive as to avoid any mistake.
    Backup ALL your Users folders (Documents, Pictures, Movies, Music etc) manually (drag and drop methods) to a (not TimeMachine) external powered drive (HFS+ journaled formatted in Disk Utility) and disconnect, your going to be wiping the entire disk of ALL DATA. (warning, everything will be gone and not recovered, OS, programs, files, Windows etc all gone.)
    Note: You might want to hold c and boot off the 10.6 installer disk and use Disk Utility to format the new blank external drive instead of using OS X Lion that's hosed. Then reboot into Lion and copy files, be safer that way perhaps.
    Here we go!
    Hold c and boot off the 10.6 installer disk that comes with your computer and second screen in just STOP there, don't install OS X yet.
    Look at the Utilities Menu for Disk Utility.
    On the left is the name of your hard drive maker, click it and Erase (format HFS+ Journaled), give it the same drive name as before, and click Erase...
    (note: if you want to "scrub" the drive of old files that haven't been overwritten yet, then use the Security Option > Zero Erase, takes a lot longer)
    This should wipe the drive of ALL partitions (GUID, OS X and 10.7 Recovery, Windows if present)
    When it's done, quit and install OS X 10.6. Then install all your programs from fresh sources and validate/update.
    When you setup a first account, use the same user name as before, this way you can simply drag and drop the content of your previous Users folders from the external drive right back into the new Users folders and everything should work peachy. Links in iTunes to music, playlists and iPhoto links especially.
    Update OS X to 10.6.8 using the Combo Update for best results.
    http://support.apple.com/kb/DL1399
    (Note: If your original machine had 10.5 and you want the free iLife that comes with the disks with the computer, then you'll have to install 10.5 first using the same c boot/erase/format methods as above, then update to 10.6 via the disk, then Combo Update 10.6.8)
    Final step optional but highly recommended.
    A lot of people use a Carbon Copy Clone of their boot drive to a new HFS+Journaled external drive (used only for this purpose) as a "hold the option key" bootable backup in case something goes wrong with their boot drive or need to restore to a previous OS X version..  (in addition to TimeMachine drive for more immediate backups.)
    It's not advised to have a Bootable Clone and a TimeMachine partition on the same external drive, as two drives gives hardware protection in case one fails.

  • Does the Mountain Lion upgrade include the upgrades from Lion?

    I was wondering if I should update to Mountain Lion, and I was wondering if it includes the upgrades from Lion as well?

    You only need one OS. I'd use Mountain Lion, but you should first figure out if you have any old programs that are not compatible with either Mountain Lion or Lion.
    Old PowerPC programs will not work on Lion or Mountain Lion.
    To view which programs you have that are PowerPC, hold down option key and select System Profiler from the Apple menu. Then, select Applications in the Software section. Click on the Kind column header to sort by kind. Look for programs that are PowerPC. Those won't work. If you need them, don't upgrade.
    Additionally, Roaring Apps has compatibility information for other software: http://roaringapps.com/apps:table

  • I am trying to upgrade from Lion 10.7.5 to mavericks, it says I need 10.9 before 10.9.5. I cannot find 10.9, any suggestions?

    Upgrading from Lion 10.7.5 to Maverick, will not allow upgrade to 10.9.5, says I need 10.9, which I cannot find. Any suggestions?

    You probably downloaded the 10.9.5 Update, which only updates previous versions of Mavericks.
    Mavericks itself is only available through the App Store:
    https://itunes.apple.com/us/app/os-x-mavericks/id675248567?mt=12

Maybe you are looking for

  • How do I move my itunes account from one country to another?

    How do I move my itunes account from one country to another?  I set up my itunes account in the United States and now I live in England.  I would like to transfer my purchases from my US account to my British account and then download them onto my ne

  • Windows Live Messenger Keeps Disconnecting!!!

    Hi, I have a Linksys WRT54G v6, and I've noticed that everytime I'm either wired or wirelessly connected to the router,  WL Messenger tends to disconnect every so often and then reconnects again right after.   When I'm not connected to the router, an

  • Why is trimming video inaccurate in Aperture 3

    In Aperture 3 I'm creating a Slideshow made up of images and videos. I noticed that the sections I trim are not reflected when I preview the end result. I tried shutting down and restarting Aperture only to find that the video is trimmed in the wrong

  • Handling  Faults in a Business process JCAPS 513

    Hi All, We are testing the faults in a WSDL file. Fault message has three fields viz Type/Message/Trace. When i invoke the webservice in a JCD , all the 3 fields are getting populated with the proper error description. But when i invoke the same serv

  • [SOLVED]xfce4-topmenu-plugin-git, nothing happens except with firefox

    Hello guys, I just installed xfce4-topmenu-plugin-git from the AUR, and also other topmenu utilities (optional dependencies) : pacman -Qs topmenu local/topmenu-gtk-git 2015.03.22-1 A standalone global menu bar for Gtk+ 2.0 based desktop environments.