Can not deliver the message I sent?

Alanhardisty is right and you can check this by yourself here: http://www.mxtoolbox.com/ (enter your domain there (zamilofshore.com). The solution should start with registering the domain name for your exchange server and setting up the mx and a records correctly to point to your email server. Alternatively you may use a hosted email solution where you can download the emails to your exchange server by pop3 collection. This will help you deliver emails to servers that check to see if the domain name of the sender is valid which must be the case here...

sorry its zamiloffshore.com

Mr Ioannis_Avgeros:

220 zamiloffshore.com [ESMTP Server] service ready;ESMTP Server; 09/29/09 13:23:46
 Not an open relay.
 0 seconds - Good on Connection time
 0.983 seconds - Good on Transaction time
 OK - 212.93.195.116 resolves to mail.zamil-om.com
 Warning - Reverse DNS does not match SMTP Banner

HELO please-read-policy.mxtoolbox.com
250 zamiloffshore.com [250 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 <supertool@mxtoolbox.com> Sender OK [250 ms]
RCPT TO: <test@example.com>
550 domain of forward path is not allowed - [250 ms]
QUIT
221 [ESMTP Server] service closing transmission channel [234 ms]

                                              

1:
2:
3:
4:
5:
6:
7:
8:

Okay - a few problems here:

1. Your Reverse DNS is set to mail.zamil-om.com and should be mail.zamiloffshore.com 
2. Your FQDN is zamiloffshore.com and should be mail.zamiloffshore.com 
3. Your SPF (Sender Policy Framework record) only allows mail to be sent from IPs 212.93.192.34 & 212.93.192.37 - as long as you are sending from one of these IPs you will be fine - I suspect this is not the case as your mailserver is on IP 212.93.195.116 

So to rectify - please do the following:

1. Call your ISP and get them to change your Reverse DNS name to mail.zamiloffshore.com 
2. Change the FQDN on your mail server under Exchange System Manager> Servers> Protocols> SMTP> SMTP Virtual Server Properties> Delivery Tab> Advanced button 
3. Change your SPF record to match the IP address that you are sending out mail from. 

Mr alanhardisty
I wont to inform you that we have another Email ( zamil-om.com)
please see the attachment

Okay - thanks for letting me know.

In that case, please do the following:

1. Change the FQDN on your mail server under Exchange System Manager> Servers> Protocols> SMTP> SMTP Virtual Server Properties> Delivery Tab> Advanced button to mail.zamiloffshore.com 
2. It looks like you have just changed your SPF record, so as long as that is now correct, things should be fine.  

I also have an FAQ document on my website about this particular problem which may be worth a read:

http://www.it-eye.co.uk/faqs/readQuestion.php?qid=2

My ISP Replay to me

zamiloffshore.com
Server:  st-exchange.awalnet.com
Address:  212.93.196.9
 
Non-authoritative answer:
zamiloffshore.com      nameserver = ns1.awalnet.net.sa
zamiloffshore.com      nameserver = ns2.awalnet.net.sa
zamiloffshore.com
        primary name server = ns1.awalnet.net.sa
        responsible mail addr = hostmaster.ns1.awalnet.net.sa
        serial  = 2009012801
        refresh = 43200 (12 hours)
        retry  = 7200 (2 hours)
        expire  = 2419200 (28 days)
        default TTL = 21600 (6 hours)
zamiloffshore.com      MX preference = 10, mail exchanger = mail.zamiloffshore
com
zamiloffshore.com      text =
 
        "v=spf1 ip4:212.93.192.34 ip4:212.93.192.37 mx include:awalnet.net.sa ~
ll"
 
ns1.awalnet.net.sa      internet address = 212.93.192.4
ns2.awalnet.net.sa      internet address = 212.93.192.5
mail.zamiloffshore.com  internet address = 212.93.195.116 

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:

your....

so what I should do ?

:(

My ISP says

[[

it seems that the cause of the problem is in the "tts-consult.com" email server. I suggest that you send them the problem and they should look into their email servers and see why are your emails being rejected.

also, I checked if your email server is being black listed but it is currently not (please ignore UCPROTECT 3) it is meaningless.

]]