You have 3 PTR records set up currently:
Code:
10.100.177.205.hcjbc.org. IN PTR bcldap.hcjbc.org
10.100.177.200.hcjbc.org. IN PTR bcmailbox.hcjbc.org
10.100.177.210.hcjbc.org. IN PTR bcmta.hcjbc.org
The problem with them is that every application when looking up a PTR record for aaa.bbb.ccc.ddd will query the DNS server for "ddd.ccc.bbb.aaa.in-addr.arpa." but the PTR records you have setup only provide information for 10.100.177.200.hcjbc, so these records will never be used and are pointless. You should create the zone in-addr.arpa. similar to what I posted so that you have valid PTR records as a mail server needs them, and most other applications expect it.
(Also if you actually test those queries you are missing the "." at the end so it really returns "bcmta.hcjbc.org.hcjbc.org.", but since it will never get queried it doesn't really matter 
)
Another thing which I forgot to mention last time is that MX records are supposed to have the FQDN of the server, not it's IP address. This is why it is showing "10.100.177.200.hcjbc.org." as your mail server. You entered in 10.100.177.200, and bind properly saw there was no terminating "." on there so it added the origin of "hcjbc.org.".
Since you have it split up I believe the MX record should be pointing to the MTA, so
Code:
hcjbc.org. 380000 IN MX 10 bcmta.hcjbc.org.