Quote:
|
Originally Posted by drogers I installed zimbra without a hitch, pretty much.
however, due to the current network admins setup here, the DNS is still not working for the site inside our local network. At my house, i tried going to http://curley.quirkservice.com and got a "forbidden" error message. |
Hrm. If you log into the actual box Zimbra is running on, and use the links browser, does it work (as much as links can), or do you get the same forbidden message?
Quote:
|
Originally Posted by drogers Here is what i have so far:
- curley.quirkservice.com is what i installed zimbra with
- the dns is configured to send the correct traffic to the correct box (i think)
- i have the mx record for quirkservice.com pointing to the zimbra machine
is that all it takes for mail going to quirkservice.com to be sent to the zimbra machine? |
Yup. All this can just be done in DNS. As you said, the MX record for your domain should point to the Zimbra server... which should be the same IP as mail.quickservice.com.
Quote:
|
Originally Posted by drogers do i need to add quirkservice.com as a server in the zimbra admin settings? |
Believe it or not, this is a trick question.
Yes, ultimatly... to be capable of receiving mail for quickservice.com, you have to add that domain into Zimbra.
Or, put another way... for every domain you wish to receive mail for, you need to add that domain into Zimbra, using the admin interface.
Now, during your install, it asked you what domain would be the default. It defaults to hostname.domainname.com.
There's an unfortunate bug in the current version that prevents you from adding domainname.com to the list of hosts you receive email for, when there's any subdomain of that domain already in there. So, if "hostname.domainname.com" exists in Zimbra, you can't add "domainname.com". You *can* add other subdomains, such as "mail.domainname.com".
The Zimbra folks are hot on the case though, and said they have that problem fixed for the next release.
Quote:
|
Originally Posted by drogers is it possible to set up a virtual domain to have the ebay.quirkservice.com subdomain exist on the same server? |
Are you referring to a virtual domain that's not running Zimbra? You can do this, but not through Zimbra. You'd need to add something like Apache into the mix.
What I did is run Apache on port 80, to server a basic website. On that site, I included an "Email Login" link that hands the browser off to Zimbra, which runs on another port.
You could do something similar to host other domains on that same server. To run Apache on port 80, you have to tell Zimbra to stop handling port 80 requests. You can do that by editing "/opt/zimbra/bin/zmiptables", and you'll see the following around line 34:
80 => 7070, # HTTP
Just comment that line out (putting a # at the front of the line), and restart Zimbra (/etc/init.d/zimbra restart).
Now you can start up Apache on port 80. Anytime you want a user to reach Zimbra, you'd just redirect them to port 7070. I personally did that with the following virtual host lines in my /etc/httpd/conf/httpd.conf:
Code:
<VirtualHost *:80>
# Servername is the domain name you want users to type into their
# browser in order to connect to Zimbra
ServerName mail.mydomain.com
# Pass every request off to Zimbra
RewriteEngine On
RewriteRule ^(.*)$ http://127.0.0.1:7070$1 [P]
RewriteRule ^proxy:.* - [F]
# On the way back, rewrite headers containing this domain name and port,
# effectively hiding the port from the user
ProxyPassReverse / http://mail.mydomain.com:7070/
ProxyPreserveHost On
</VirtualHost>
That makes it so that anytime someone connects to "mail.mydomain.com", it hands the request off to Zimbra on port 7070. Otherwise, it's assumed that there's another virtualhost defined that would handle the request (the first virtual host defined is the default, I believe).
The neat thing about the above setup is that the browser never sees the fact that there's another server running on port 7070, Apache using mod_rewrite and mod_proxy to hide it. This does assume those two modules are available, but that's the default in RedHat.
Have a good one,
-Eric