Novell Cool Solutions

Running More Than One MTA on the Same Server



By:

November 26, 2008 4:35 pm

Reads:4,915

Comments:3

Score:Unrated

Print/PDF

Here’s something I stumbled on while writing my GW8 Upgrade Guide:

The new GroupWise 8 MTA opens a SOAP connection (for administrative purposes) on port 7161. If you intend to run more than one MTA on any particular server, you must set a unique SOAP port for the additional MTAs. This cannot be done in ConsoleOne, but must be configured in your MTA startup file. The default port is 7161. For each additional MTA you should set an alternative port.

For example:

  • NetWare/Windows: /soapport-7162
  • Linux: — soapport 7162

This is undocumented as far as I can tell.

Caledonia Network Consulting:

http://www.caledonia.net/

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

3

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

3 Comments

  1. By:Anonymous

    it’s documented for the POA but yeah it should really also be documented for the MTA. Thanks!

  2. By:Anonymous

    I wonder which Dutch admirer showed you this one … :-)

  3. By:paulgear

    I always try to avoid making modifications to the startup file. It’s a bad idea, in my opinion, because then NDS and the file say different things, and you have to know to go looking in the startup file (because it overrides NDS) when the behaviour you expect based on the NDS config is not happening.

    My solution is this: Always allocate a separate IP for every MTA, POA, and gateway in your GroupWise system. You can configure the IP binding in ConsoleOne, so there’s no need to edit the startup file, and you can easily move the IP between servers if you need to migrate for some reason. Planning even a small GroupWise system in a rigorous way like this is a great way to ensure easy upgradability in the future.

Comment

RSS