Currently, we're running Zimbra 5.0.13 behind our Ironport setup (AsyncOS 6.5.2)
We're experiencing issues with our ability to correctly use our outgoing content filters while specifying a custom header under Network > Incoming Relays.
Our subscribers send from a mailstore and then through the Ironports. The subscriber's original IP is lost on the Received: from header (replaced with the mailstore's IP address), so we're using a X-Originating-IP custom header that Zimbra injects.
The problem is that the header is not being recognized as its passed from Zimbra. Zimbra passes it like so:
X-Originating-IP: [1.2.3.4]
If I initiate a SMTP conversation from the mailstore to the Ironport manually, and specify the header and omit the brackets, like so:
X-Originating-IP: 1.2.3.4
our remote IP related outgoing content rules then work as expected.
Unfortunately, the rub is that the Ironport won't allow you to specify a custom header such as "X-Originating-IP: [" since no whitespace is allowed and it just wants the header name and not the extraneous characters that it can't seem to parse.
Any suggestions or workarounds would be appreciated...thanks!
