Problem with disabling "Add X-Originating IP to messages"

[Mindaugas]

Hello,
some of our customers connects to Zimbra server over POP3 from Outlook.
When they send message to particular domain messages are rejected with this text:
<xxxx@xxx.xx>: host mail.xxx.xx[xxx.xxx.xxx.xxx] said: 554
Service unavailable; Client host [our zimbra server name] blocked using
Barracuda Reputation;
http://bbl.barracudacentral.com/q.cgi?ip=<public customer IP address> (in reply to end of
DATA command)

I realized that problem is with showing "Originating IP address".
I disabled "Add X-Originating IP to messages" in Admin Console, but problem persist. When I send message from Web Console x-Originating IP is not added, but when I send from Outlook it appears again.

I configured Outlook to submit messages over 465 port with enabled SSL encryption - the same problem.

Please help me solve this problem.
Thank You.

[phoenix]

Originally Posted by Mindaugas

Hello,
some of our customers connects to Zimbra server over POP3 from Outlook.
When they send message to particular domain messages are rejected with this text:
<xxxx@xxx.xx>: host mail.xxx.xx[xxx.xxx.xxx.xxx] said: 554
Service unavailable; Client host [our zimbra server name] blocked using
Barracuda Reputation;
http://bbl.barracudacentral.com/q.cgi?ip=<public customer IP address> (in reply to end of
DATA command)

Then you should go to the Barracuda site and get yourself removed from the list (or whitelisted).

Originally Posted by Mindaugas

I configured Outlook to submit messages over 465 port with enabled SSL encryption - the same problem.

Port 587 (requires authentication) is the correct Submission port.

[Mindaugas]

Originally Posted by phoenix

Then you should go to the Barracuda site and get yourself removed from the list (or whitelisted).

Our Zimbra server public IP address is not blacklisted, our customers public IP address is blacklisted which appears as X-Originating IP address.
But anyway I filled tthe removal form.

Originally Posted by phoenix

Port 587 (requires authentication) is the correct Submission port.

I've changed to 587 port. The same behavior.

But main question is is it possible to disable adding of "X-Originating IP address" totally?

[jerryboi]

Configuration > Global Settings > MTA > Messages:
[] Add X-Originating IP to messages

[Mindaugas]

Originally Posted by jerryboi

Configuration > Global Settings > MTA > Messages:
[] Add X-Originating IP to messages

Yes, this option is unchecked. But this option not working when mail is sent over SMTP (Outlook - POP3).

[ewilen]

I know I am coming to this late, but the setting in Zimbra only applies to messages sent via ZCO or ZWC. If you have Outlook sending via SMTP, the X-Originating-IP header won't appear anyway. You'll see exactly the same result if your customer uses Thunderbird or any other POP/SMTP client (or IMAP/SMTP).

The real issue here is that the receiving mail server is looking at the Received: headers and deciding to block the mail because a blacklisted ip address appears somewhere in there. This is a pretty bad practice--generally, you only want to block, if at all, based on the final hop before delivery.