I've checked if it is really an open relay - and i'm already listed on najsbl.org because of that wrong behavior.
I was not the one that build Zimbra on that client, but I'm the one that must solve that problem - lol
-- RELAY TEST --
Mail relay testing
Connecting to ***.***.***.*** for relay test...
<<< 220 smtp.mydomain.com.br ESMTP Postfix
>>> HELO antispam-ufrj.pads.ufrj.br
<<< 250 smtp.mydomain.com.br
Relay test 1
>>> RSET
<<< 250 2.0.0 Ok
>>> MAIL FROM:<spamtest@antispam-ufrj.pads.ufrj.br>
<<< 250 2.1.0 Ok
>>> RCPT TO:<relaytest@antispam-ufrj.pads.ufrj.br>
<<< 250 2.1.5 Ok
>>> QUIT
<<< 221 2.0.0 Bye
Relay test result
Ops!!! Host appeared to accept a message relay!
-- EOF --
I know that Zimbra doesn't behave it self as and open relay - All I'm saying is that something must be making Zimbra to act as one. Maybe a miss configuration - or as I'm in doubt: Every e-mail that came from World Wide Web is hitting my MTA with internal IP from firewall. I think it was supposed to sustain the valid IP, as it is been forwarded - right?
Sooo - if everything came from firewall hitting my MTA in 25 smtp port - it is on my trusted network, right?
How to solve that without changing my client's entire hack putting a freaking DMZ (Where it had to be at the first place - i know.. don't shoot me.

)
I'm already listed in some blacklist's as an open relay.
----------------------------
Note:. The other freak sys admin have installed Gentoo Linux, than putt Zimbra into a chroot dir with Debian 4.
Plz - Don't ask me why.

-----------------------------
i'm just trying to fix that to WORK, just in time to my new blade server came in and them EVERYTHING it will be normally (re)installed as it's recommended by all nice people at ZIMBRA's. lol again.
- I look to the network design again, and I've stopped a moment just to cry alone in the bathroom.. ow my... -