Where is Lion Server's .ServerBackup Equivalent?

On a Snow Leopard Server with Time Machine configured, servermgrd would run a TimeMachinePreBackupHook as well as a TimeMachinePostBackupHook which involved creating a backup of key things like the Directory, and more, e.g.:
bash-3.2# ls -la /Volumes/Time\ Machine\ Backups/Backups.backupdb/Server/Latest/Server\ HD/.ServerBackups/
total 16
drwxr-xr-x@ 2 root admin    68 Aug 19 11:01 (null)
drwxr-xr-x@ 12 root admin   476 Aug 19 11:01 .
drwxr-xr-t@ 19 root admin   952 Aug 19 10:58 ..
-rw-r--r--@ 1 root admin    37 Aug 19 11:01 .serverBackupSignature
drwxr-xr-x@ 2 root admin    68 Aug 19 11:01 addressBookServer
drwxr-xr-x@ 2 root admin    68 Aug 19 11:01 calendarServer
drwxr-xr-x@ 2 root admin   170 Aug 19 11:01 iChatServer
drwxr-xr-x@ 5 root admin   204 Aug 19 11:01 mailServer
-rw-r--r--@ 1 root admin 3282 Aug 19 11:01 master.browse.plist
drwxr-xr-x@ 2 root admin   136 Aug 19 10:58 openDirectory
drwxr-xr-x@ 2 root admin 2074 Aug 19 10:59 serverSettings
drwxr-xr-x@ 2 root admin   170 Aug 19 10:59 sharePoints
drwxr-xr-x@ 3 root admin   272 Aug 19 11:01 webServer
drwxr-xr-x@ 2 root admin    68 Aug 19 11:01 wikiServer
This isn't happening with Lion Server, or at least not in that location. Does anyone have any insight as to whether this process or concept has been maintained, and what its particulars are?

It appears the Server does not create this is you have Time Machine set to exclude System files. Once I removed that exclusion, this directory is now present in my backups.

Similar Messages

Where can i get a copy to OS X lion Server?

I can't upgrade to OS X Mountain Lion because i really need to use a piece of software that does not work with Mountain Lion but i also need to get OS X Server. When i try and get it from the mac app store it says i need mountain lion. Where could i get OS X lion Server?

Phone the online Apple Store and order a download code for it.
(72627)

Where to edit sharepoint permisssions on lion server

Could anybody tell me where the correct place to edit sharepoint permissions is on Lion Server?
1. by selecting the sharepoint from the File Sharing in the server.app
2. by selecting the server in the devices in the server.app, choosing storage and then selecting the folder that is used as the sharepoint
3. by going to the sharing system preference, selecting file sharing, choosing the shared folder used as the sharepoint and changing the permissions in the user box.
Many Thanks in advance.

I use the second method to manage my servers sharing and regulary propergate permissions from this menu due to the permissions bug in Lion server...
Make sure you have server tools as well to get a better grasp on your users with Workgroup Manager. Other ways can produce unwanted home folders being created etc, I had to download this on ours as it wasn't already installed!
http://support.apple.com/kb/DL1528
I have no idea why the server management has become so complex now! With so many different places to do things no wonder there are so many issues with the latests software releases! Lets hope Mountain Lion is addressing all of this!

HT4770 where can i download lion server?

Where can I download OSX Lion Server?

Now that Mountain Lion is out, you can't buy older versions of OSX directly from the Apple Store. However, you can try calling Apple (1-800-MY-APPLE) and tell them that your hardware doesn't support Mountain Lion. I'm sure they still have copies of Lion. It's not like they destroy all traces of previous versions of OSX every time a new version is released.

Where can I download lion server app

I can't find a copy of lion server app anywhere not even when I contacted apple. Does anyone know where can I find it?

Now that Mountain Lion is out, you can't buy older versions of OSX directly from the Apple Store. However, you can try calling Apple (1-800-MY-APPLE) and tell them that your hardware doesn't support Mountain Lion. I'm sure they still have copies of Lion. It's not like they destroy all traces of previous versions of OSX every time a new version is released.

Where can I configure mail quotas in Lion Server?

One (minor) problem for me, after upgrading from SnowLeopard Server to Lion Server is the fact, that I can't figure out where to administer the mail quotas. So far I have just managed to find the "Server Admin". Here, under Mail -> Maintenance I can see the quotas and under Mail->Settings->Quotas I can enable quota warnings and edit them. But I can't find a place to configure individual quotas. The quota settings from SnowLeopard server have been migrated and are still in place. But how should I change them. It used to be in WorkgroupManager. But in WorkgroupManager this item is gone.
Many thanks for your replies.

Followng up a bit,
In looking into OD records on my Snow Leopard Server via the Inspector in WGM, I see the following attribute for one of my users for whom I've set a 1024mb mail quota.
Name:
MailAttriute
Value:
<?xml version="1.0" encoding="UTF-8"?>
<dict>
          <key>kAPOPRequired</key>
          <string>APOPNotRequired</string>
          <key>kAltMailStoreLoc</key>
          <string></string>
          <key>kAttributeVersion</key>
          <string>Apple Mail 1.0</string>
          <key>kAutoForwardValue</key>
          <string></string>
          <key>kIMAPLoginState</key>
          <string>IMAPAllowed</string>
          <key>kMailAccountLocation</key>
          <string>[redacted].[redacted].org</string>
          <key>kMailAccountState</key>
          <string>Enabled</string>
          <key>kPOP3LoginState</key>
          <string>POP3Allowed</string>
          <key>kUserDiskQuota</key>
          <string>1024</string>
</dict>
I'm wondering if manually entering this attribute, and an XML value with at least the kUserDiskQuota key included will be all I need to do to implement per-user quotas in Lion Server.
If I get time, I will test and report back.

Where to buy lion server

Hallo,
i want to use an mac, which isn't compatible to Mountain Lion, as Server.
In the Mac App Store i can't find the Lion Server App.
Where can i buy Lion Server?
Thanks.

Welcome to the Apple Support Communities
OS X Lion and Lion Server aren't sold anymore in the App Store, so now you have to call Apple to purchase OS X Lion or OS X Lion Server > http://support.apple.com/kb/HE57 They'll give you a redeem code that you will have to insert in the Mac App Store to install Lion Server

User Mail folder under Lion Server? Where....?

Does anyone know where the mail Postbox in the lion Server file system are stored if i use open Directory?
The local users have the mail folder in their home folder, (user/Mail/Dovecot/cur/) but where is the folder for the Domain Users?
Hint: i use MailServeForLion ;-)
Thx a lot

Ha,
i´ve found it.
The User must login once, then the folder mail will be create in the home folder.
But why did i have no access to my own mail folder as normal User? The Folder Icon is shown with a red -
Anyone?
Thx

Where is the DHCP Server-Pref in Mountain-Lion Server?

Hello
I am testing the Mountain Lion Server. What I missing is the DHCP Server. Ist their an Seperate Tool to configure this? I can't find it
Any Ideas?
Gérard

Mountain Lion has not been released yet, and can't be discussed here - please use the appropriate developer forum that has been set up for this purpose.

Where's the Mountain Lion Server Documentation?

Been waiting all day for Mountain Lion Server Documentation the be posted to no avail. What gives? Especially need the Mountain Lion Server Upgrading & Migrating manual. I help run a small educational cmoputer center in Santa Cruz CA and we need to transition from 10.5 Leopard Server on an old G5 Power Mac to 10.8 Mountain Lion Server on a new 2012 Mac mini as soon as it goes on sale. We particularly need the Workgroup Manager migration app documentation ASAP. Can any Apple employees explain why the Mountain Lion server documentation is not posted even though you can download the Mountain Lion Server since this morning?

Good Luck in Migrating from 10.5 Server to 10.8 Server... There's soo many changes.. Each time I've upgraded since 10.2.X server, I've always had to manual migrate things. Forget the automated upgraded process since it always hangs for me.
As for 10.6.8 Server, Apple changed the imap/pop server software from cyrus to dovecot. There's a script if I recall somewhere in 10.6.8 Server convert the imap mail of all the users. However before you run that script I recommend that you rebuild the imap structure in cyrus before you do...
http://support.apple.com/kb/HT3120
as for mirgrating OD user.... archive the users...
and import it...

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

OSX Lion Server/Clients TimeMachine Location

Dear Community,
I have a problem with Timemachine for OSX Lion Server on a MacMini and hope you can help me out. I have an attached TB drive (Pegasus R6, RAID5) and set up TM sharing for the clients of my small workgroup to this drive. The Backup folder location on the server is /Volumes/Backup-Volume/Shared\ Items/Backups. Everything fine so far, clients can backup into that folder with TM sparsebundles.
My Problem is that when switching "on" TM Backup for the Server itself, I am able to choose the Volume "Backup-Volume", but it backs up to /Volumes/Backup-Volume/Backups.backupdb as a folder, not a sparsebundle.
Don't beat me, I know this is just a cosmetic issue, but why ain't it possible to store them in the same folder, with an equivalent type of structure (sparsebundle/folder). I like to have my system clean and don't like to search on different locations for my backups.
Does anybody know a workaround to manually set the location for Backups, either for clients or server. I don't care which folder it actually is, /Volumes/Backup-Volume/Shared\ Items/Backups/xxx.sparsebundle or /Volumes/Backup-Volume/Backups.backupdb/..., both are fine but it should be consistent.
A different question in this context: If this works out, I will set the HDDs the following way:
Pegasus:
2*2TB RAID 0 as Share Point "Data-Volume" for fast access, backuped
4*2TB RAID 5 as Share Point "Backup-Volume" as the name indicates for backups :-)
Mac Mini:
1*500 GB for OS, backuped
1*500 GB as Share Point "Scratch-Volume" not backuped
Any objections regarding this setup?
Thanks, Alex

When you say 'manage', what do you mean?
If you're talking directory services where you're just sorting account credentials that clients use to authenticate, then... oh several thousand... or tens of thousands, because the server is only involved when a user logs in - it validates the user's credentials and passes back details about the user's account.
However, if the user's home directories are also on the server (so the client mounts the user's home directory when they log in) well now you have a file sharing component, and network bandwidth requirements when the user logs in, etc.
Assuming you have 100 active users and a perfect gigabit network (which never, ever happens) then each user is going to get an average of 10mpbs to the server (and to their home directory, for opening/saving files, etc.). Double that to 200 users and you're down to 5mbps each. Consider that most networks never work at more than about 50% efficiency (due to protocol overheads, etc.) and you're down to 2-3mpbs each. That could be an issue.
Of course, if you have 200 users in your directory, but there's only ever 10 or 20 people active at a time those numbers change, but the point is there IS no hard number as to how many clients you can support - it's dependent on multiple factors, and way more than you've listed here.
None of that is directly relevant to whether you need a second machine or not. I'd argue that with 80 users you absolutely need another machine, if only for redundancy's sake if not load. Consider the business impact f that server is offline for any reason and you don't have a spare server to carry the load.

How can I use LDAP searching from OSX Lion Server to Mozilla Thunderbird?

How can I use LDAP searching from OSX Lion Server to Mozilla Thunderbird? We have a super awesome contacts server that works great for our Mac users. About 30% of our company are on PCs, and I would like to use the Mozilla Thunderbird mail client for them. I see that in Thunderbird I can set up LDAP searching, and would like to have this feature point to our contacts server. I've tried several different settings, and looked all over the web, but could not find the proper way to configure this. Does anyone know if this can be done, or if not, would have a better suggestion? Thank you for your time!!

try double clicking keychain acces should launch and ask if you want to install login, system, System roots
A dialog box will launch asking where to install the cert since your configuring a vpn I would put the certificate it in system.

What I wish I'd Known Before My Lion Server Install

The truth is that I am on my FIFTH Lion Server install on the same box this week. While I was working on #4, I went ahead and submitted a ticket with Apple and arranged a timeslot for this morning to work with them to help me past my struggles with Lion Server. This post is the result of that experience. Big props to Apple support techs Chuck and Don - you know who you are!
What I Wish I'd Known Before My Lion Server Install
1. Do NOT migrate user accounts, apps, and files, until AFTER you have the Server set up and working correctly.
- This one tip, which is brilliantly simple, would have saved me four very long days of head bashing.
2. Server Admin Tools are mandatory.
- The first time around I used the Server App to configure the system (after an upgrade install, and subsequently after a clean install + migration).
- Server Admin allows you to set up the foundation of your server - which it NEEDS!
- DNS - configure a local, pseudo domain for your server if you're doing this at home. Something like "mynet.private" - if you don't, your SSL certificates can get all jacked up, your clients will not trust your certs. This breaks a lot of stuff.
3. Do NOT accept the mDNS .local domain suffix for your Server
- At each step, if something auto-fills your server name as name.local reject it, and use the fully qualified domain name that you set up above (server.mynet.private).
- If you do not do this, anything that requires certificates could/will have big problems.
4. Enable services one at a time. Reboot after EACH major phase past the core Lion install.
- Base install ... Server install. REBOOT
- DNS configuration. REBOOT
- validate your host name - I needed to force a 'changeip' command because there was a problem with the HOSTNAME retaining the mdns .local domain name.
- OD Master config. REBOOT
- Set up Podcast Producer (which will also setup your Xgrid). REBOOT
5. Take images of your hard drive as you go.
- Once I got the core server installed, the basic services above, I rebooted and held the option key, then restarted on the Recovery HD image.
- Use Disk Utility to take a snapshot image of your hard disk so you can get back to this wonderful place of everything working! It's cheap insurance, and adds a bit of extra time, but is well worth it. If you leave the default settings alone (the 'compressed' one in particular) it will use as little space as possible. My server at this stage of configuration created a 4GB disk image.
6. Use the Migration Assistant After the above
- Now you can migrate your apps
- Migrate your users
- etc.
If you use the Migration option while you're installing the server, or if you upgrade on top of your Snow Leopard (or whatever), I can almost guarantee you that you are in for a world of hurt.
I struggled through all kinds of issues with files having embedded information, scattered throughout all the various subsystems, that gummed up my installation and would case all manner of the flakey Lion Server behavior that you read about ("Error Reading Configuration").
If you want to use Podcast Producer, or any of the Profile Manager features, the above methodology was the only way that I could get them to work. Often times I'd have everything working, then reboot and it would break. After I did the above, the system is as solid as a rock.
Today, I love Lion Server. Yesterday I was cursing it.
Best of luck!!

There are 2 distinct apps in Lion Server.... Podcast (in Server app) and Podcast Producer (Server admin which is deemed legacy from SNS). Podcast uses Podcast Publisher instead of Podcast Capture to produce, edit and submit to Podcast app. Podcast doesn't requre Xgrid where PCP did. The two don't mix.
It's as clear as mud in all the documentation about this.
We're finding that Podcast Publisher has much more flexibility that Podcast Capture (edit, episodes & more), can use existing workflow from PCP, doesn't require xgrid, and podcasts can easily be managed by non-IT people via the Podcast wiki as opposed to the CLI pcast commands to edit & modify PCP feeds.
Hope this helps.

Lion Server is killing me!!

We have a Mac Mini (new Nov. 2011) runnig Lion Sever 10.7.2 and I can't get it to work properly. I have done two instals including the original startup. I have an OD running, I have added users and groups. The Mac's and PC's in the office can access the shared folders and files without any problems. We are using a new Time Capsule and it is working fine. I'm even running Rumpus FTP software using port 8000 and that is working fine.
When I set up the server the second time I followed the instructions from lynda.com. I have a SSL cert. from GoDaddy installed.
Problem #1:
If I set the Server's DNS Server to its own IP address, to run MiniDNS the server has a very hard time connecting to the internet. Safari is super slow and will time out when trying to reach websites like Apple.com.
Problem #2:
The Wiki, Web & Profile Manager do not work. When I go to my domain (server.saterdesign.com) I get the "Safari can't connect to the server".
Problem #3:
When a local Mac tries to Add the server by going to the System Preferences, Mail, Contacts & Calendars and chosing "Add Account" and then clicking "Add a Max OS X Server account => clicking create, the server shows but if you choose it and try to Set Up, it says "Unable to verify user credentials". I have also tried to connect to the server using its fully qualified domain name without success.
All the Lion Server seems to be able to do is run the OD, and share files. I can't use the Server Address book, or iCal or iChat, or Web, or Wiki, or Profile Manager.
I've turned all the services off and on again. I've set the SSL to None, and to a self signed SSL.
After the second instal the Web, Wiki, and Profile Manager worked for awhile. Then I had to change the IP address of the Server, that broke all that stuff. When I changed it back, it still didn't work. BUT, even when the Web & Wiki . . . etc. was working, I could not get the client Mac's to Set Up and use the Server services, other than File Sharing.
P.S. Doing things in the "Terminal" give me the runs . . . . I'm a GUI guy - a Graphics Guy forced into the IT world by horrible career choices.

Anad Nosbig wrote:
I tried using Terminal, I typed in /var/named and it just said:
-bash: /var/named: is a directory
You'd need to use the cd command to change to the /var/named directory. Type man cd for more info on the cd command.
Anad Nosbig wrote:
I truly appreciate the help, I do . . but this is beyond ridiculous. When you buy a new car it runs, you don't have to go home and learn how to adjust the computer controlled variable timing BEFORE the engine will run!!
I'm trying to help you. If you just want to complain, call Apple.
Anad Nosbig wrote:
Do I have to run DNS??
If all I want is Address Book and iCal, is DNS a MUST??
Is DNS necessary for file sharing??
Yes, DNS is a must for OS X server. If you want services to run reliably (or at all) you will need functional DNS.
Anad Nosbig wrote:
The first time I had this set up I was not running OD. I wiped it clean and re-installed the OS so I could start fresh and do it correct from the start with a FQDN and a trusted SSL, and OD. After all that I'm back at where I was when all it was doing is sharing files. This came from Apple as a Mac Mini Server, it should just be and DO that!
It is and can do everything you want it to, but not without proper configuration. If you were expecting to plug it in, turn it on and just go without any configuration, then maybe a server isn't for you.

Where is Lion Server's .ServerBackup Equivalent?

Similar Messages

Maybe you are looking for