Two linux boxes on Lan, one with Zimra, but having Port Issues

[sanchiro]

Originally Posted by mmorse

so your mail (pt 25) is set to go to scott...and there's no mention of you running zimbra on different web ports-nor a mention of 7071 open to david...
Why don't you give us a little more detail on your setup...
You really need to examine your DNS if you plan to use this for incoming mail...

Not sure what detail you are after. Moreover, I don't recall anything in the documentation, about forwarding port 7071 to one's zimbra machine, but after your post, I forwarded port 7071 to my zimbra box's IP address, and VOILA. Suddenly, I can browse the zimbra box, at least from my LAN. I still have to test access from home, when I get there.

Now, I am trying to learn how to set up email accounts for others in Zimbra..and then how to set up access, so that they can access their new zimbra accounts.

Scott

[mmorse]

Originally Posted by sanchiro

I forwarded port 7071 to my zimbra box's IP address, and VOILA. Suddenly, I can browse the zimbra box, at least from my LAN.

Good to hear -7071 is the admin console...so if your trying to access it obviously you need have it pointing at the correct box
List of ports:
Firewall Configuration - ZimbraWiki (just the standard section for you)

Also check to be sure your isp doesn't block pt 25 or that you have to send outgoing mail through one of their relays.

[sanchiro]

Originally Posted by mmorse

Good to hear -7071 is the admin console...so if your trying to access it obviously you need have it pointing at the correct box
List of ports:
Firewall Configuration - ZimbraWiki (just the standard section for you)

Also check to be sure your isp doesn't block pt 25 or that you have to send outgoing mail through one of their relays.

At this point I have two issues. One is finally setting up DNS correctly so that my primary machine 'scott' will get mail destined for it, but then pass along email destined for Zimbra management on 'david'. At that point I assume email and other tasks with Zimbra will then work.

Why doesn't the zimbra .install.sh routine notice or complain about port 7071, during installation? I realize now that 7071 must be forwarded to the machine running Zimbra, else it will not work, but I don't recall any error during installation, or specific reference advising me to forward that particular port.

The other issue, is about setting up for individual users, to access their Zimbra email. What URL would a user load, to log on and access their data?

[sanchiro]

I guess I have tapped out any further help on this...but am hoping someone can help me over this last hurdle.

Suggestions?

[mmorse]

no problem - sorry, quite a large folder of threads for me to reply to...

Originally Posted by sanchiro

At this point I have two issues. One is finally setting up DNS correctly so that my primary machine 'scott' will get mail destined for it, but then pass along email destined for Zimbra management on 'david'. At that point I assume email and other tasks with Zimbra will then work.

What mail solution & operating system is running on scott?

Why doesn't the zimbra .install.sh routine notice or complain about port 7071, during installation? I realize now that 7071 must be forwarded to the machine running Zimbra, else it will not work, but I don't recall any error during installation, or specific reference advising me to forward that particular port.

And their shouldn't be. The install script does check to see if anything else is running on port 7071 (on david) - it can't possibly mess with access through other machines and routers etc.

The other issue, is about setting up for individual users, to access their Zimbra email. What URL would a user load, to log on and access their data?

From your home lan connect to http://david'sip to see the web client. (eventually your goal from the outside is to get dns and routing set up properly so you can just go to http(s)://someaddress.domain.com)

Ports 22, 25, 80 and 110 at least, are routed to 'scott'
6881, 7025, 995, 993, 443 and 389 are forwarded/routed to 'david'

So your running another web server on scott?

You can :
a)Change the web client port on david to something else
zmprov ms server.domain.com zimbraMailPort 81
zmprov stop/start
set up port forwarding to david on that port

b)Access over https -as you said 443 is fowarded to david
zmtlsctl mode (http, https, mixed, both -mixed changes http to https for login only)
zmprov stop/start

[sanchiro]

Originally Posted by mmorse

no problem - sorry, quite a large folder of threads for me to reply to...


What mail solution & operating system is running on scott?

'scott' is running Mailman version 2.1.9, with several lists managed and active. OS is debian 3.1.

And their shouldn't be. The install script does check to see if anything else is running on port 7071 (on david) - it can't possibly mess with access through other machines and routers etc.

From your home lan connect to http://david'sip to see the web client. (eventually your goal from the outside is to get dns and routing set up properly so you can just go to http(s)://someaddress.domain.com)

So your running another web server on scott?

I have Apache 2 running a simple web site for my office. It's not really active, but I also run another application 'ClearHealth', an office management solution for managing patient data, accounts, scheduling, etc. I'd really prefer having Apache allowed to continue running on 'scott' to run this web application.

You can :
a)Change the web client port on david to something else
zmprov ms server.domain.com zimbraMailPort 81
zmprov stop/start
set up port forwarding to david on that port

b)Access over https -as you said 443 is fowarded to david
zmtlsctl mode (http, https, mixed, both -mixed changes http to https for login only)
zmprov stop/start

So, you are saying that zmprov will allow more direct management of Zimbra's ports, i.e., allowing me to override the initial demand made by Zimbra's installation script that it be given exclusive access to ports 25 and 110, for email, as an example?

I'll get busy reading about zmprov and zmtlsctl tools to see how they can help me configure my system.

Any other suggestions?

Scott

[phoenix]

Originally Posted by sanchiro

So, you are saying that zmprov will allow more direct management of Zimbra's ports, i.e., allowing me to override the initial demand made by Zimbra's installation script that it be given exclusive access to ports 25 and 110, for email, as an example?

Zimbra is an MTA and requires exclusive access to port 25 it also provides POP server and requires exclusive access to port 110 (and all the other ports it uses). You can't 'share' those ports with anything else, if that's what you're thinking of doing.

[sanchiro]

Originally Posted by phoenix

Zimbra is an MTA and requires exclusive access to port 25 it also provides POP server and requires exclusive access to port 110 (and all the other ports it uses). You can't 'share' those ports with anything else, if that's what you're thinking of doing.

I am thinking it shouldn't be this much fun to get Zimbra set up and running!

What was that sage advice from Rodney King...can't Zimbra and other servers just get along? I guess not.

[phoenix]

Originally Posted by sanchiro

I am thinking it shouldn't be this much fun to get Zimbra set up and running!

What was that sage advice from Rodney King...can't Zimbra and other servers just get along? I guess not.

Of course Zimbra and other MTAs can get along, just not on the same port. That would be no different whichever MTA you installed - most software requires exclusive access to any port it uses.