This is not a valid test, and here is why.
Your test is using telnet, to a specific IP 10.1.0.11. This server is an internal mail server, not mxlogic, which likely has an internal mx record, note that you are not using dns or an application that would look up such records for this test, so I cannot validate if you have a proper record or not. Also this is not the IP that postfix is getting to send your email to, as it is presently receiving external IPs for mxlogic.
Secondly, the email address you are sending to in the test is at a separate domain, which if I recall, was the original domain that you were sending to that was working, and again likely has an internal mx record that nagios\postfix can route to. You can try sending to the amsterdamhospitality.com email from this same server, if you can than it really only strengthens my suggestion of a proper internal only mx record for this domain that points to your mail server.
So we again are back to the two options of creating an internal only mx record on your internal dns server(s), or white-listing on mxlogic.
The proper route, in my honest opinion, is to create an internal mail record, that points postfix to the internal mail server for this domain. Please note that this is not something that anyone outside of your company would ever have access to, as it should only be done on an internal dns server, not on something like godaddy, network solutions, or any other global dns management provider. This likely has been done long ago for finance36.com, and would just need to be replicated for amsterdamhospitality.com. I honestly would like to know what the other admins opposition to this is, it provides no security risks that are not already on your network, it does not provide external systems or entities information on your internal network, it only provides a proper path for any systems that route mail internally to directly talk with your mail server via the internal network instead of being forced to send data via clear text over the internet, which is a very bad idea especially for nagios alerts.
Here is an excellent example of what I feel should be done in your network, provided it is largely an M$ managed environment.
Some commands that you might run to test my theories of internal records(please put the results of these commands in your post):
Code: Select all
nslookup --querytype=MX mail-ahgserver.ahghotels.local
nslookup --querytype=MX ahghotels.local
nslookup --querytype=MX finance36.com
nslookup --querytype=MX mail.cronow.com
nslookup --querytype=MX cronow.com
nslookup --querytype=MX amsterdamhospitality.com
nslookup mail-ahgserver.ahghotels.local
nslookup ahghotels.local
nslookup finance36.com
nslookup mail.cronow.com
nslookup cronow.com
nslookup amsterdamhospitality.com
The second option is dealing with mxlogic, which I can only provide slight help to, however
this page seems to point out what you likely need to do.