Re: [Assp-user] ASSP Header

[Micheal Espinola Jr]

Aaron Allen wrote: The problem is that someone sending mail to our organization looks at the MX record and sees cacweb, so they initiate a connection to cacweb.  But instead of cacweb answering (since it is acting as a transparent proxy), the server cacexch answers and identifies itself as cacexch.  Perhaps this is just more of a perceived problem, but it seems that if I am connecting to a mail server I should receive the response I was expecting.  Since I receive a response other than the expected response, it would Its purely a perceived problem.  :-)   Here is what I do:  Configure your MTA to respond with mail.domain.tld as its identity. Configure your MX/A record point to mail.domain.tld - still using the appropriate IP to connect properly to cacweb. Ultimately, doing what I do can be good or bad.  Its good because its clean, and no one knows your internal server names.  Its bad in complex environments (server load balancing, clusters, farms, etc), because you have eliminated the uniqueness of the server's response which may lead to troubleshooting difficulties. make me think there might be something weird going on.  At the very least, I wonder if this conforms to the RFC or not. There is no RFC that addresses different MX and identity responses.  As long as the responses are accurate, there is no perceived issue.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user