Multiple inbound SMTP host names

[amb1545]

I saw the additional to the admin console that provides the "inbound SMTP host name" field, which is helpful because all of my clients previously used Postini and now use MXlogic. My question is, is there a way to specify multiple inbound SMTP hosts? MXlogic for example provides a domain.com.inbound10.mxlogic.net as well as domain.com.10inbound10.mxlogic.net which are both priority of 10 (per their best practices).

[exyst]

Did you ever get an answer for this? I'm using Red Condor and they have given me four MX records to configure. I configured just the primary one, but don't know if there are implications to this.

In addition, is there a way per domain to configure Zimbra so that mail is only accepted from specific IP addresses/ranges?

Darryl

[Labsy]

Same problem here:
is there a way to enter multiple Inbound SMTP host names? All my domains have at least 2 MX records, which are on separate network - that's what MX proirity is all about, right?

So, if anybody with enough knowledge ansers, here are main question regarding Inbound SMTP host name settings:
1.) How to enter multiple inbound SMTP host names, either via GUI, or manually in some file
2.) If (1) cannot be done, what are the consequences, if mail for this domain is routed via non-entered SMTP host?
3.) Any other workaround for cases, where domain is using external multiple MX records (most probably for spam filtering)?

Thanx!

[morten]

Same problem here. But no answer yet!

Does anybody know how to do this. I have tried to use multiple entries separated by spaces, by comma's, but nothing works.

Is this possible or maybe not required.
Normally you can have multiple MX records and zimbra only checks the first one, as far as I know, so it's maybe not even relevant?

[phoenix]

It's not necessary to have multiple inbound SMTP names. All you need to do is point your MX records to the Zimbra server public IP. You can either point your DNS records for each domain to the server as follows:

Bind DNS records for yourdomain1.com
yourdomain1.com. 7200    IN      MX      10 mail.yourdomain1.com.
mail.yourdomain1.com. 7200 IN    A       x.x.x.x <- your public IP

Bind DNS records for yourdomain2.com
yourdomain2.com. 7200    IN      MX      10 mail.yourdomain2.com.
mail.yourdomain2.com. 7200 IN    A       x.x.x.x <- your public IP

You can also do them like this:

Bind DNS records for yourdomain1.com
yourdomain1.com. 7200    IN      MX      10 mail.yourdomain1.com.
mail.yourdomain1.com. 7200 IN    A       x.x.x.x <- your public IP

Bind DNS records for yourdomain2.com
yourdomain2.com. 7200    IN      MX      10 mail.yourdomain1.com.
mail.yourdomain2.com. 7200 IN    A       x.x.x.x <- your public IP

Note the difference in from the first example for yourdomain2 MX record. Either of those will work.

[morten]

Thanks Bill for your reply,

however, this is a solution to the problem. What you are saying we understand, thats just the required DNS entries if you can directly point your MX records to zimbra.

In our case there is a anti spam service which receives all the mail and verifies this. After verification it is sent to the real smtp server. Therefor the MX records always point to the anti spam server. But we do not just have one such server but, as is very common, at least 2 servers with different priorities.

We can not configure one 'Inbound smtp host name' but not multple addresses.
The question is, how can we add multiple hostnames to 'Inbound smtp host name'. Because this field only accepts one.

[phoenix]

Which version of Zimbra are you using? Could you update your forum profile (so we don't have to keep asking you) with the output of the following:

zmcontrol -v

[morten]

For this installation we are using the following version:

Release 6.0.3_GA_1915.UBUNTU8_64 UBUNTU8_64 FOSS edition

[phoenix]

Sorry for my previous misleading answer. This problem is supposed to be fixed in 6.0.2: Bug 40072 – multi-valued zimbraSmtpHostname not reflected in Admin Console.

[morten]

Now I understand the confusion. This bug is reporting the server-wide configuration. however, I am configuring this on a per-domain setup. This is because not all domains use the same servers.