It's all about the answers!

Ask a question

Setting up RTC - SMTP connection in a complex and secured infrastructure


Dan Sevcenco (5021723) | asked Oct 15 '13, 7:51 a.m.
I am having a problem setting up the connectivity to the SMTP server due to the specifics of the deployment architecture. Here are the details:

1. The server is an IBM pSeries with AIX OS
2. In fact we have several servers, each having a number of LPARs and the deployment architecture is active - standby
3. The servers are clustered for high availability
4. Because of clustering, the servers have multiple IP addresses, some being attached to physical network adapters, some being virtualized by vio.
5. When connecting to the SMTP server, the source IP is 172.20.66.114
6. The SMTP server is seeing that the connection is coming from IP 172.20.66.40, which is an IP that is related to the hardware clustering functionality.
7. Because of this mismatch, the SMTP server reports that is not able to perform relaying for the receiver e-mail address.

Question : Is there any way in RTC / JTS to configure which IP address to use when binding to a socket in order to open the connection to the SMTP server? Obviously, I want to be able to open the connection from the IP address that the SMTP server is seeing so that the process of sending the e-mail works as expected.

Nota bene : I tried the functionality of sending an e-mail through the same SMTP server from another RTC deployment which is mapped on a system that is not clustered and it worked like a charm. So the problem with the 1st RTC deployment seems to be environment configuration related.

Thank you!

One answer



permanent link
Kevin Ramer (4.4k6166186) | answered Oct 18 '13, 4:20 p.m.
Well, I don't have clustering but do have AIX LPAR with many IP bound to one NIC(*).  Users can connect to RTC using hostnames for the various IP that are bound by the RTC/RQM tomcat.   However, we occasionally get inquiry where users have been notified that their LDAP authentication has been failing 100s of times, but the reported IP is always the main IP on the interface.   While this is not identical to your situation it has some similarities.  You might have to extend the SMTP host acceptable IP list to include that whole subnet (assuming you have that authority).  Or use an intermediate SMTP that is acceptable to the desired SMTP host.


(*)
en0: flags=1e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
        inet 91.142.60.73 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.192 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.175 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.166 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.115 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.152 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.109 netmask 0xffffff00 broadcast 91.142.60.255
        inet 91.142.60.213 netmask 0xffffff00 broadcast 91.142.60.255

Your answer


Register or to post your answer.