Do I need to configure Open Directory before I configure mail?

I am doing a slow step-by-step configuration of a new 10.6.2 box and I am marginally skilled. Before I migrate a handful of accounts from the old server to the new, I want to make sure mail services work on the new server. Later I would like to try experimenting with Open Directory. Since I will be creating local user accounts on the server to configure mail, will these migrate to Open Directory later or will I need to reconfigure the accounts? If the latter is true, it suggests I should install Open Directory first.
(I apologize if this belongs in another discussion group.)
Paul

I have discovered that the answer is that I do not have to configure Open Directory first. Found this on the OD discussion area:
http://discussions.apple.com/thread.jspa?threadID=2243066&tstart=0
Paul

Similar Messages

Configure Open Directory using CLI

We have a Leopard Server in Advanced Mode.
If you have a fresh install of Leopard Server with nothing configured, is there a way to configure Open Directory to be an Open Directory Master completely using CLI utilities?
Wasn't able to find anything in Apple's PDFs

I agree with Dal78 Apple using a base DN of servername.example.com rather than just example.com is illogical. In fact originally they did seem to use just example.com as the format but in recent years now use server.example.com as the format. When I first encountered this change it was still possible to overridge the use of servername.example.com and force it to use just example.com as the format. In more recent times I have decided to leave things the way Apple do it.
I don't know if there is an official answer as to why, but a possible guess is that you can now have multiple Open Directory servers for a single domain. This is the 'Locales' option in Server.app. It maybe that including the servername makes it possible/easier to implement this.
I also agree Strontium90 do not use a .local root domain for Open Directory. In theory there are hacks to (sort of) get this to work, but Apple engineers will typically run screaming for the woods when they encounter this.
PS. Briefly Apple also did the same illogical thing with DNS zones, whereby the zone name for a domain was servername.example.com instead of example.com this at least they have stopped doing.

How to configure Open Directory base DN

Hi,
I have been using OpenLDAP on a Synology NAS drive, but this has some serious shortcomings with Mac clients (eg. roaming profiles simply doesn't work).
So I have bought a MacMini which among other things will replace my existing LDAP server with Open Directory.
As a dry run, I enabled the Open Directory and went through the simple set up and I had a basic system up in no time. However I have come up against an annoying issue with the base DN used by Open Directory and I hope someone will be able to help me.
My existing LDAP has a base DN that looks like this: dc=myorg, dc=local
So when users log in, they can use a username which conforms to the following format: [email protected]
The problem is that Open Directory likes to set the base DN to: dc=macservername, dc=myorg, dc=local
meaning that a fully qualified user account name now becomes: [email protected]
This seems bonkers to me. For example, what would happen if I introduce a second Mac server into the mix and failover to it - the servername element of the DN becomes redundant or if it changes, I need to communicate with all users.
I must be missing something obvious - but there doesn't seem to be much in the way of configuration that I can see through the Server application.
So, my question is, how can I configure my base dn without the servername so that my existing username context remains the same?
Many thanks - I look forward to any responses.

I agree with Dal78 Apple using a base DN of servername.example.com rather than just example.com is illogical. In fact originally they did seem to use just example.com as the format but in recent years now use server.example.com as the format. When I first encountered this change it was still possible to overridge the use of servername.example.com and force it to use just example.com as the format. In more recent times I have decided to leave things the way Apple do it.
I don't know if there is an official answer as to why, but a possible guess is that you can now have multiple Open Directory servers for a single domain. This is the 'Locales' option in Server.app. It maybe that including the servername makes it possible/easier to implement this.
I also agree Strontium90 do not use a .local root domain for Open Directory. In theory there are hacks to (sort of) get this to work, but Apple engineers will typically run screaming for the woods when they encounter this.
PS. Briefly Apple also did the same illogical thing with DNS zones, whereby the zone name for a domain was servername.example.com instead of example.com this at least they have stopped doing.

Do I need to use open directory on Yosemite Server, I'm only looking to use file sharing and VPN

I'm setting up a new mac mini server with Yosemite and I was wondering if there are any advantages or disadvantages to not using the open directory service? The only services I'm planning on using are File Sharing and VPN.

You don't need Open Directory unless you want to manage user accounts centrally on the server.

Can´t configure Open Directory Master

After a reinstall I can´t config Open Directory Master. I have this logs:
Mar 4 12:22:28 servidor slapd[14293]: @(#) $OpenLDAP: slapd 2.4.23 (Oct 19 2011 00:16:13) $
[email protected]:/private/var/tmp/OpenLDAP/OpenLDAP-186.2~3/servers/slapd
Mar 4 12:22:28 servidor slapd[14293]: daemon: SLAP_SOCK_INIT: dtblsize=8192
Mar 4 12:22:28 servidor slapd[14293]: bdb_monitor_db_open: monitoring disabled; configure monitor database to enable
Mar 4 12:22:28 servidor slapd[14293]: slapd starting
Mar 4 12:22:28 servidor slapd[14293]: daemon: posting com.apple.slapd.startup notification
Mar 4 12:22:47 servidor slapd[14293]: SASL [conn=1025] Failure: no secret in database
Mar 4 12:22:50 servidor slapd[14293]: SASL [conn=1028] Failure: no secret in database
Mar 4 12:22:51 servidor slapd[14293]: => bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994)
Mar 4 12:22:51 servidor slapd[14293]: conn=1014 op=37: attribute "entryCSN" index delete failure
Mar 4 12:23:10 servidor slapd[14293]: => bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994)
Mar 4 12:23:10 servidor slapd[14293]: conn=1014 op=101: attribute "entryCSN" index delete failure
Mar 4 12:23:17 servidor slapd[14293]: SASL [conn=1036] Failure: no secret in database
Mar 4 12:23:20 servidor slapd[14293]: SASL [conn=1040] Failure: no secret in database
Mar 4 12:23:47 servidor slapd[14293]: SASL [conn=1098] Failure: no secret in database
Mar 4 12:23:51 servidor slapd[14293]: SASL [conn=1111] Failure: no secret in database
Mar 4 12:24:18 servidor slapd[14293]: SASL [conn=1179] Failure: no secret in database
Mar 4 12:24:21 servidor slapd[14293]: SASL [conn=1182] Failure: no secret in database
Mar 4 12:24:24 servidor slapd[14293]: daemon: shutdown requested and initiated.
Mar 4 12:24:24 servidor slapd[14293]: daemon: posting daemon shutdown notification.
Mar 4 12:24:24 servidor slapd[14293]: slapd shutdown: waiting for 0 operations/tasks to finish
Mar 4 12:24:30 servidor slapd[14293]: slapd stopped.
and:
2012-03-04 12:04:51.855 CET - opendirectoryd (build 172.10) launched...
2012-03-04 12:04:52.073 CET - Logging level limit changed to 'error'
2012-03-04 12:04:52.153 CET - Initialize trigger support
2012-03-04 12:04:52.486 CET - Registered node with name '/Active Directory' as hidden
2012-03-04 12:04:52.487 CET - Registered node with name '/Configure' as hidden
2012-03-04 12:04:52.487 CET - Discovered configuration for node name '/Contacts' at path '/Library/Preferences/OpenDirectory/Configurations//Contacts.plist'
2012-03-04 12:04:52.487 CET - Registered node with name '/Contacts'
2012-03-04 12:04:52.575 CET - Registered node with name '/LDAPv3' as hidden
2012-03-04 12:04:52.620 CET - Registered node with name '/Local' as hidden
2012-03-04 12:04:52.672 CET - Registered node with name '/NIS' as hidden
2012-03-04 12:04:52.697 CET - Discovered configuration for node name '/Search' at path '/Library/Preferences/OpenDirectory/Configurations//Search.plist'
2012-03-04 12:04:52.698 CET - Registered node with name '/Search'
2012-03-04 12:04:52.920 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/legacy.bundle'
2012-03-04 12:04:53.159 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/search.bundle'
2012-03-04 12:04:54.162 CET - '/Search' has registered, loading additional services
2012-03-04 12:04:54.162 CET - Initialize augmentation support
2012-03-04 12:04:54.217 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/SystemCache.bundle'
2012-03-04 12:04:54.247 CET - Successfully registered for Kernel identity service requests
2012-03-04 12:04:54.264 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/PlistFile.bundle'
2012-03-04 12:04:54.310 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/FDESupport.bundle'
2012-03-04 12:04:54.707 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ConfigurationProfiles.bundle'
2012-03-04 12:04:54.708 CET - Registered subnode with name '/Local/Default'
2012-03-04 12:05:17.128 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ldap.bundle'
2012-03-04 12:07:47.863 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/configure.bundle'
2012-03-04 12:07:48.030 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/keychain.bundle'
2012-03-04 12:08:42.226 CET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/AppleODClient.bundle'
2012-03-04 12:10:17.881 CET - Registered subnode with name '/LDAPv3/127.0.0.1'
2012-03-04 12:10:29.747 CET - Unregistered node with name '/LDAPv3/127.0.0.1'
2012-03-04 12:24:08.488 CET - Registered subnode with name '/LDAPv3/127.0.0.1'
2012-03-04 12:24:30.792 CET - Unregistered node with name '/LDAPv3/127.0.0.1'
Anyone may help me?

It happens after a clean install and posterior data recovery through TimeMachine. With Server Admin it was imposible change Standalone to Master.
Thanks a God I have only a few users and after a hard week end I back up data and I did a new clean installation with a enterely new OD.
Thanks for your interest.

Are there open directory "preferences" to configure NTP on client workstations?

A quick query, is there a way to set NTP settings for OD clients via preferences? or possibly a script that can be used to set the NTP server?
Thanks

If you have Apple Remote Desktop send this unix command.
systemsetup -setnetworktimeserver time.apple.com
Just change time.apple.com to your local time server.

Open Directory or LDAP Problem with 10.5 Client and 10.4 Server

Yesterday, the client-server setup we've been using successfully FOR YEARS decided not to work on a v10.5.8 MacBook Pro client. Did not do anything to the v10.5 client recently (other than to boot it up). Not sure if any software was updated on the server recently (where do I check for this?). Curiously, a v10.4.11 client running on a Mac Pro (tower) continues to work fine/as though nothing's changed. It appears as though the only difference is v10.4 client (working) vs. v10.5 client (not working).
Here is what IS working:
1) Network Home Directories on dedicated drive partition of Mac running OS X Server v10.4.11. AFP, DNS, and Open Directory are all up and running (normally, I think) as shown in Server Admin application.
2) Mac Pro (tower) client running v10.4.11 binds to and authenticates at v10.4.11 server. Any valid user can access their home directory on the server seamlessly when logging in at this v10.4.11 client Mac.
3) That same v10.4.11 client Mac also contains a LOCAL admin user with its home directory on the local hard drive. That LOCAL admin account is used to update software on a per machine basis (and preclude users from adding unauthorized software, needing to use a specific machine, etc.).
Here is what IS NOT working:
4) On a MacBook Pro client running v10.5.8, the LOCAL admin account looses access to the partition containing its local home directory. The drive partition literally disappears. The only "solution" I've been able to find (and it's not truly a solution) is to turn off the Open Directory/LDAP binding (using the Directory Utility application). With binding turned off, the LOCAL admin user has no problem accessing their home directory on the local hard drive partition. Turn binding on again (using Directory Utility application), and the LOCAL admin user can no longer see its local home directory.
Again, binding is necessary to allow regular users to use the v10.5 MacBook Pro with Network Home Directories (as in items 1-3 above). Binding should be turned on for this reason. However, with binding on, the LOCAL admin user cannot manage the computer because the local partition containing the admin home directory disappears/is inaccessible. Turn binding off, and the partition containing the admin home directory reappears.
Perhaps there's something in the sever logs that will help. I don't really know how to read these, so if your help involves the logs, please refer to them explicitly (e.g., "in Server Admin, go to Open Directory->Logs->LDAP log" or similar).
Any help greatly appreceated.

Nope. Never used sso_util.
I try to use Apple's GUI server management tools unless absolutely necessary/at the end of my rope (i.e., last step before re-install etc.). I figure there's just too many things going on under the hood: using the command line may fix one setting, but not re-configure the two or three others that Apple NEEDS in order to have the whole thing working in harmony. Unless you really know what's going on with all the configuration files, it's best to let the GUI manage the settings.
In my particular circumstance, I've now got ALL Leopard clients, one Leopard v10.5 server, and one Tiger v10.4 server. Everything is working fine now, but it was not a simple matter getting the Tiger v10.4 server re-integrated into the otherwise ALL Leopard environment. OD/Kerberos is on the Leopard v10.5 server. Home directories are still on the Tiger v10.4 server.
Two keys to getting THIS/MY set-up working:
1) Tiger v10.4 server needs to have Open Directory set to "Connected to a Directory System" and has to be joined to the Kerberos realm that was set-up on the Leopard v10.5 server (use Server Admin to do all of this).
2) Sharepoint on Tiger v10.4 server has to have SOME, but NOT ALL checkboxes for guest access enables/checked. See:
http://discussions.apple.com/message.jspa?messageID=10903468#10903468
Number 2 immediately above is contrary to what Apple manual for User Management reads, but this is what worked for me/my set up, after pulling my hair out following the manual's instructions to the letter and not getting the thing to work!

How to turn off Open Directory in OS X Server 10.8.2

I am configuring a MacPro with ML Server 10.8.2 for internal-only use. I have DNS working on it (with the annoyance that it goes out of its way to break wildcard host names, and it doesn't know how to properly create the zone files to allow a secondary DNS server to do reverse-name-lookups properly). I have only 2 users (admin and Time Machine), Time Machine is working for client Macs using the Time Machine user account, and File Sharing is working (using either account), sharing a RAID of internal drives an a pair of USB-attached external drives.
I briefly turned on Open Directory, just to see if I wanted or needed to go that route. I entered an Open Directory admin (diradmin) with a password. Looked around the options and decided I did NOT need to use Open Directory just to get the Time Machine stuff working, and I was right.
However, now the Server App shows Open Directory is "On." When I go to that tab, I get a message stating that there was an error reading the settings file for Open Directory services. I click it "Off" but it refuses to turn off. When I come back to the tab, I get a pop-up window with a message about an error reading the settings and the Off/On switch moves back to "On" and the green light never goes off next to Open Directory in the list of services.
I've rebooted the machine and after the reboot, sometimes, it appears as if I can add/delete/modify Users and Groups. Other times, after the reboot, the +/- buttons are greyed out and I cannot add/edit/modify Users and Groups. I have not yet tried to add/delete/modify users yet because I'm leery of trusting the server with this error message.
Can anyone help me to remove anything and everything related to Open Directory so that it is "off" as if I never ever turned it on? Or any suggestions on how to fix this short of a reinstall?
Can I download and install the Server app on a differnt machine and then just copy the Server app over to this machine? Will that zero out the Open Directory stuf that I'm trying to get rid of?
Thanks in advance.

I think I solved my problem by running the following command:
sudo slapconfig -destroyldapserver diradmin
diradmin is the name of the Open Directory admin account I created.
The Open Directory Service now appears "off" and no longer had the green dot next to it in the list of services.
Obviously, NOT a good solution to someone who was actively using Open Directory as this appears to have deleted all the data associated with Open Directory.
Users and Groups now allow me to add/delete/modify.
Sad to see an Apple product have such issues.

Open Directory is not providing a secure connection

I've been setting up Yosemite Server, but I haven't been able to get a second Mac to join onto the Open Directory service. When clicking Join… in Accounts Preferences on the client machine, and entering the address, it asks me whether I want to trust the server's certificates, which I do; and then, in a second dialog, it says "This server does not provide a secure (SSL) connection. Do you want to continue?"
My question, simply, is how do I confirm that my server is providing a secure Open Directory connection? If it's not, how do I enable it, and if it is, how do I convince my client to use it?
Background:
After doing the initial setup, I turned on Open Directory before noticing that the host name was not correct—I had not changed it from "Xxx.local". So I changed it to the correct domain as pointed to by an external DNS server. It mentioned that I'd have to reconfigure a number of services, Open Directory among them. I turned Open Directory off, then on, and confirmed in the Certificates section that all services were using the newly-generated certificate with the correct domain name. I turned on Profile Manager, and added a test network user, and an encrypted-only (SMB3) share for its home folder. For good measure, I turned on the Websites service.
At several points along this process, I tried to get the client to join the server's Open Directory, each and every time with the same message that the server does not provide a secure connection. I removed the applicable certificates on the client and tried again, just to be sure it wasn't using an outdated version of them—to no avail. The error is exactly the same whether I use the global .com hostname, the .local hostname, the global IP, or the local 10.0.1.x IP.
The server is running Mac OS X 10.10.1, and the client MBP is on 10.10.
The client is currently on the local network, but I aim to use Portable Home Directories and sync from other locations, so an unsecured OD connection is obviously unacceptable.
Any advice would be dearly appreciated!

First, follow the instructions in this support article to configure the clients to use the server's certificate to bind via LDAPS. The common name in the certificate must match both the server's hostname and its domain name, as resolved by the clients. You will get nowhere if those conditions aren't met.

Possible to convert ordinary accounts to Open Directory accounts?

This might be a naive question. But I need to set up accounts for users on this Mac Pro configured with Leopard Server and they may need to be Open Directory accounts, i.e. we may decide to create portable accounts for the whole cluster and have them hosted on this server. I won't know for sure until we have fully discussed the intended uses of the machine, which could take some time. So I am wondering if I can just give users ordinary accounts using System Preferences and then convert them at a later date to Open Directory accounts. I tried to do this with the first account I created for myself on the system and found that the name spaces of the two kinds of accounts conflict, and it's especially hard/dangerous to change a short name (is this really true??)
It would be confusing for users and a headache for me if everyone has two distinct and unrelated accounts. Thanks in advance for any help.

Hi Liz
+I do get a warning if I launch Server Preferences: it says "Server Preferences can't be used with advanced configurations of Mac OS X Server." Doesn't that confirm that I chose Advanced?+
I guess it does?
I'm thinking you might be getting System Preferences and Server Preferences confused? Your original post was about converting ordinary accounts to Open Directory ones? Provided you've configured the Server as an Open Directory Master with all that that entails then you can install a clean OS on your clients. Provided the DHCP Server is handing out the correct information then after the OS has been installed and at the point the Setup Assistant asks you to create the initial account you should be given a choice to either create one locally or use one that is from Open Directory. If you choose the latter option then a generic local admin account gets created anyway. This is how its supposed to work. However you could forego all of this and simply create a secure local admin account. Join the client to the ODM using the well established method. The same result is achieved.
If you had chosen Standard instead of Advanced a lot of the auto-discovery bit comes into play. To be honest I don't really know although judging by the documentation and what some have posted here this is what happens.
You might find this useful?
http://discussions.apple.com/message.jspa?messageID=8940512#8940512
Tony

Is Open Directory required for Webmail??

Anyone know if I need to enable Open Directory (Tiger Server) in order to use webmail successfully? Currently I am trying to get it going with all users on the local directory but it's not working. Thanks for any help. Rob

Hi
Is Open Directory required for WebMail?
No.
The Web Service needs to be enabled. For that to work effectively DNS needs to be configured and running. Its not absolutely necessary but its better if it is. Obviously the Mail Service needs to be running as well as users having Mail enabled for them in WorkGroup Manager. Obviously you need to enable IMAP for desired users. Either POP and IMAP or IMAP only.
In the Web Service enable the WebMail option. Server Admin > Web > Settings > Sites. You need to enable the WebDAV Module as well. Its in the Modules section. That should be it.
If you want external access open port 16080 and allow public/external requests to the private/internal IP address of your mail server. Create an appropriate firewall rule if your router requires it.
Tony

TS4363 exchange account configuration option is gone for apple mail 6.0

why are there no account options. I have an exchange account that automatically configures to pop and is terrible., pop needs to simply drift into the history books and leave the email world to imap and echange and everyother email protocol that is read on all devices... I can use and have configured an account from a previous install that functions fine but fail bucket on setup of a new one:(

Okay - I fixed it. Here's what I did.
- Deleted the entire mail folder inside my Preferences folder. ~/Library/<userfolder>
- Kept the files in the trash just in case, but didn't need them
- Rebooted
- Opened the System Preferences
- Selected "Mail, Contacts & Calendars"
- Verified the previous account was gone
- Clicked Create
- Created a new account and then opened Mail
- Voila! Email
Note - if you trash the mail folder inside Preferences, it will delete any local emails. All my email is IMAP and I never store anything locally, so everything syched right back when the account was recreated.
Good luck. Hope this helps.

Configure DNS on Snow Leopard for private NAT with Open Directory

I am needing to set up DNS on Snow Leopard server 10.6.4 for use with Snow Leopard clients only. On the server, I have two IPs, one public connections outside the network, and one private within the NAT range. DNS was not originally set up on the server, but Open Directory was (sort of). I've demoted the server from OD master to stand alone, but still can't get this to work.
This server is only for setting up and using Open Directory + NetInstall services inside the network. In effect, it isn't serving web pages and isn't registered with our upstream DNS. What I am assigned to do is get Open Directory to set up user profiles and network shares and home directories. So, what I need is this -
a basic DNS config I can do in Server Admin that will set up DNS to resolve to the local server NAT IP for Open Directory purposes;
and provide DNS for outside the OS X server for the specified Snow Leopard clients.
DHCP is running (but the clients were configured with static IPs in the NAT range). This serves as the DHCP server for the entire network (Windows + Mac clients that aren't in the static NAT range).

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

Do I need Open Directory for multiple email addresses for Calendar users?

Hey all,
I have a single mac mini which I use simply as a calendar server for +/- 20 users. One day I might use Profile Manager to manage their iOS devices too. On the initial installation, we enabled Open Directory, although I'm not sure that it's required, and we have no plans re using it to manage network logins etc aside from existing calendaring.
I'm working through a migration from a Lion Server.app install to Mavericks, and due to some data corruption issues, we'll probably just rebuild the server and reimport the users calendars.
On my existing Lion Server installation, I can still use workgroup manager to assign multiple email addresses to calendar users, so that when a user invites another user to a calendar event using any of their email addresses (we have several variations), the invitation still gets pushed to the correct calendar user.
On Mavericks, without installing Open Directory, it seems I can't do this (I've downloaded Workgroup Manager for Mavericks, but it obviously can't connect to a local open directory). If Open Directory is optional, I'd rather not install it, to avoid overhead and complexity, but I still need a way to manage these multiple email addresses (aliases doesn't cut it).
Any ideas / suggestions?
Thanks,
D

For Calendar server to send actual email invitations to an attendee, two things must happen:
First, you need to configure Server.app > Calendar > Enable invitations by email. Enabling that will bring up a wizard dialog that will step you through the IMAP and SMTP account settings. The default values in that wizard will tell Calendar server to use the local Mail server (which you then would have to configure to use the appropriate SMTP relay, etc.). Or you can change the wizard settings to refer to an external IMAP and SMTP server. It is wise to use a dedicated IMAP account for Calendar server's use -- don't go using someone's personal IMAP account because there might be some "undesirable interactions", let's say. If you need help configuring this for, say, a Gmail account, I can help with that.
Second, the email address for the attendee must *not* be known to Calendar server, i.e. it should *not* be in the Directory. As you probably found out, if Calendar server sees that the attendee has an email address that is in the Directory, the attendee is considered to be "local" and the invitation will be delivered directly to the attendee's calendar client. If you simply leave those other email variations out of the Directory, Calendar server will consider that attendee "remote" and will send an actual email with a special attachment that calendar clients can understand.
Hope that helps.

Open Directory Configuration Question

I've got a Mac-Mini based server running Mountain Lion (10.8.3) and Server.app (2.2.1). The server was migrated from Lion some weeks ago, the Server works OK, but seeing odd CPU usage and fairly frequent non-specific error reports which suggests that there are still a few odd gremlins lurking around that I'm trying to track down. So I'm trying to find things that appear odd. I've found one such in the reported configuration for Open Directory.
The server is configured to be an Open Directory master, and is the only Open Directory server we have. The panel for Open Directory in Server.app lists the single entry as follows:
* www.2gc.org (master)
* 10.0.1.2, 10.211.55.2, 10.37.129.2
The first IP address is the IP address of the server on our LAN. I have no idea what the second and third IP addresses are - they do not appear to have anything to do with any network we have configured. They are from the "private" address space - so I'm guessing they are non-functional since we don't have a network using either with these IP ranges within them - but they must have come from somewhere.
It is also not clear where / how these entries are set within ML.
It may be that this is all perfectly normal, or maybe symptomatic of something that can be cleaned up.
Would value any thoughts.
Thanks in advance.

Hi Simon
Thanks for the thoughts. There are no other servers on the network - this is an isolated computer parked on a fixed IP with no downstream LAN - the 10.0.1.2 address is the one assigned it by the router that connects it to the outside world - but no other devices are connected to the sub-net the machine sits on: all services are provided through the fixed IP to machines accessing it directly from internet via FQDN.
All of which makes the presence of the other two IPs curious, and apparently unnecessary.
Good housekeeping suggests they could be removed - but unclear how these entries are set. But in the interim good to know that the presence of these IPs is probalby harmless.

Do I need to configure Open Directory before I configure mail?

Similar Messages

Maybe you are looking for