Forum Discussion
SMTP [port25] VS configuration
It might depend on how you want the SMTP traffic to work.
In my case with an Exchange 2016 server, the "default" SMTP setup caused us to not see the originating client IPs, which is a big deal for us, and since it's not HTTP/S traffic, X-Forwarded-For is of no help. I did get it to work by changing the Type to 'Performance (Layer 4)', and creating a fastL4 Protocol Profile (Client), and setting it to 'Loose Close: Enabled'
Source Address Translation: None
Source Port: Preserve Strict
Hope that helps?
I think in my example, the traffic is "tunneled" through the F5, and the SMTP/TLS settings are all set on the Exchange server itself. So I believe you could use my example fine, if you want to keep the client IPs intact. (which is the main purpose I set it up that way) I guess, give it a try and see if it works?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com