Posts Tagged ‘Mac OS X’

Configuring MassTransit Server to listen on ports less than 1024 on Mac OS X using xinetd

Tuesday, November 11th, 2008


This article explains how to configure MassTransit to listen on ports less than 1024 on Mac OS X without running as root using the xinetd utility. Most commonly, this configuration is necessary to allow MassTransit to listen on the standard FTP ports (20 and 21) or the standard TCP/IP Secure port (443) without running as root. These configuration options also allow MassTransit to listen with TCP/IP on port 80.

Note that the Xinetd utility is not available on Mac OS 10.5 Leopard. For information on how to listen on ports below 1024 on 10.5 or later, please consult the following KB article:

Consult the sections below to:
– Configure FTP port redirection using xinetd
– Configure TCP/IP and TCP/IP Secure port redirection using xinetd

Note that to use this configuration to listen on the default FTP ports without running as root, you will need to use MassTransit 4.5.1×22 or later.

1. xinetd can only re-direct from well known ports (TCP/IP – 80, TCP/IP Secure – 443, FTP – 21).
2. When configuring multihomed setups for FTP, the users must use “localhost” as the IP for port redirection.


Configuration steps are described in the ‘Using Xinetd’ PDF linked at the bottom of the page. You will also need to download and unzip the provided script (also linked below) to assist you with configuration.

Related Document:

Related Script:

Upgrading MySQL from 4.x to 5.0 – Mac OS X

Monday, September 10th, 2007


MassTransit 5.1 introduces support for MySQL versions 5.0 and greater, which allows for faster performance, better management, enhanced data integrity, improved security and additional replication services. MySQL 5 is the default database for MassTransit 5.1 and later. Group Logic recommends that customers using previous versions upgrade to take full advantage of these added capabilities.


Please see the attached document for information on updating MySQL to version 5.0 for use with your MassTransit installation on Mac OS X.

Related Document:

MassTransit is compatible with Mac OS X 10.4 “Tiger”

Friday, November 4th, 2005


MassTransit servers and web clients are now compatible with Mac OS 10.4 and Mac OS 10.4 Server. Customers will need to hotfix their installations to take advantage of this compatibility on MassTransit Enterprise. There are some caveats that customers should be aware of.


MassTransit 4.5.1×57 and later have been certified as compatible with Mac OS 10.4 and Mac OS 10.4 servers. In order to run on Tiger, please download the latest hotfix for your MassTransit server and web clients from the hotfix web page.

Please be aware that the first time you restart a machine running MassTransit (server or client) on Mac OS 10.4, you may receive a warning dialog that states the following: “An item in the Startup Items folder (“/Library/StartupItems/mtstacktuner”) does not have the proper security settings.” This warning appears because the specified file was installed by MassTransit with non-standard permissions. Click the “Fix” button to repair the permissions on the file. MassTransit will function correctly with either set of permissions.

Please review the following questions to determine if you need to take any other steps to get MassTransit running under Tiger.

1. Do you need MassTransit to listen on ports below 1024 (for FTP or firewall purposes)?
If so, you can use a tool called Xinetd to avoid the need to run as root. Please consult the Using Xinetd knowledge base article for the specifics of how to configure Xinetd. There is a new version of the Xinetd script for Mac OS 10.4.

2. Are you upgrading an existing MassTransit Enterprise server with an active web configuration?
If you are currently running on Mac OS 10.2 or Mac OS 10.3 and have a web configuration for MassTransit, you will need to back up your existing httpd.conf file before upgrading to Mac OS 10.4 and restore this backup after installation. Please contact Group Logic technical support if you need assistance in backing up or restoring your web configuration.

Does MassTransit Support Mac OS X?

Friday, October 29th, 2004


Yes, all MassTransit product types run natively on Mac OS X as of version 4.2 to version 6.0.


The following describes Mac OS X compatibility for other recent versions:

MassTransit Web Client
MassTransit Web Client versions 5.1 and later run natively on Mac OS X. (They are also compatible with Mac OS 9 and Windows).

MassTransit Servers in Compatibility Mode
Group Logic recommends that customers using Mac OS X upgrade to MassTransit 5.1 or later. However, MassTransit 4.1.2 works with Mac OS X in “compatibility mode”. This includes MassTransit Application Clients, Satellite, Professional, and Enterprise Servers. For MassTransit Professional and Enterprise Servers, existing users who have ADB-based hardware keys need to side-grade to a USB-based hardware key. Contact Group Logic Technical Support for more information. Please note that MassTransit Servers 6.1 and later are not supported on Mac OS X.

How does MassTransit handle permissions on Mac OS X?

Wednesday, December 3rd, 2003


How does MassTransit handle permissions on Mac OS X?


Mac OS X uses Unix-style file and folder permissions. Read, write, and execute permissions can be enabled and disabled independently for the owner of the file, the group owner of the file, and for all users.

By default, files on Mac OS X are created so that only the owner of the file has read and write permissions; for all other users the file will be read-only. In the same way, folders on Mac OS X are created so that they are writable only by the owner; other users can view the directory content, but cannot add to or modify the folder.

In order to allow files to be picked up by a variety of users, all files and folders received by MassTransit have their permissions set to be readable and writable by any user. All mailbox folders created by MassTransit are also readable and writable by all users.

Files dropped in the To Send mailboxes for MassTransit must have their permissions set such that the user MassTransit is running under has read and write access to the new files. If MassTransit does not have read and write access, it may not be able to successfully transfer the files. Sharing the User Mailboxes folder using AFP with inherited permissions will ensure that all uploaded files can be properly transferred by MassTransit. The MassTransit installer offers the option to configure this share point automatically when MassTransit is installed.

If you wish to configure more restrictive permissions, you can alter the permissions on the user mailboxes to be more restrictive using the permissions section of Get Info in the Finder or using the chmod command at the terminal. In making these changes, be careful to ensure that the user MassTransit is running under still has read and write permissions to all user mailboxes so files can be transferred properly.

How can MassTransit be configured to support inbound FTP connections for file transfers?

Monday, June 9th, 2003


How can MassTransit be configured to support inbound FTP connections for file transfers?


MassTransit servers for Macintosh platforms support inbound connections via FTP. In order to support this, the following procedure is required:

1. Click the “Configuration” button from the MassTransit Navigation bar.

2. Click on the “Incoming Calls” tab, located in the upper-left hand corner of the Configuration window.

3. Click on the “Add” button to create an incoming call method.

4. From the pulldown menu, select “FTP Server” and click “OK”.

5. Make sure that the “Answer incoming calls” option is checked, and click “OK.”

6. Click on the “Save” button in the lower-left corner of the Configuration window in order to register the changes.

MassTransit can be configured to allow individual users to access their own unique, private mailboxes. MassTransit may also be configured to enable “generic” or anonymous logins. Such configurations are controlled via MassTransit’s address book. Presently, there is no FTP Server support for Windows-based platforms.

NOTE: If a firewall is employed within your organization, additional security rules may be required to support inbound FTP connections. Traditionally, the File Transfer protocol requires ports 20, 21 and ports greater than 1024.