Are you using SPF?
http://www.openspf.org/SPF
Main Topics
Browse All TopicsOur Ip address is 196.219.160.195 and some sites refuse to accept email sent from our users specially
AOL we get this report
Delivery has failed to these recipients or distribution lists:
fathiB@aol.com
Microsoft Exchange has been trying to deliver this message without success and has stopped trying. Please try sending this message again, or provide the following diagnostic text to your system administrator.
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: exch-cas.lotusgroup.com
fathiB@aol.com
#550 4.4.7 QUEUE.Expired; message expired ##
Original message headers:
Received: from exch-mbx.lotusgroup.com ([00.00.00.00]) by
exch-cas.lotusgroup.com ([00.00.00.00]) with mapi; Mon, 26 May 2008 13:59:56
+0200
From: <@lotusgroup.com>
Date: Mon, 26 May 2008 13:59:55 +0200
Subject: FW: you will love these cars....
Thread-Topic: you will love these cars....
Thread-Index: Aci+bsWL4jkf8LG/RJKNjeesaz
Message-ID: <6F3DCBBF2AF573449A5F474BE
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/mixed;
boundary="_002_6F3DCBBF2AF
MIME-Version: 1.0
I checked
Checking Realtime Blackhole Lists
Email Server: 196.219.160.195
196.219.160.195 mail1.lotusgroup.com : a2000.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : above.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : abuse.rfc-ignorant.org : ok
196.219.160.195 mail1.lotusgroup.com : affinity.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : argentina.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : bellsouth.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : blackholes.brainerd.net : ok
196.219.160.195 mail1.lotusgroup.com : blackhole.securitysage.com
196.219.160.195 mail1.lotusgroup.com : blackholes.uceb.org : ok
196.219.160.195 mail1.lotusgroup.com : blacklist.spambag.org : ok
196.219.160.195 mail1.lotusgroup.com : bl.deadbeef.com : ok
196.219.160.195 mail1.lotusgroup.com : bl.spamcop.net : ok
196.219.160.195 mail1.lotusgroup.com : brazil.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : broadwing.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : bulk.rhs.mailpolice.com : ok
196.219.160.195 mail1.lotusgroup.com : burst.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : cbl.abuseat.org : ok
196.219.160.195 mail1.lotusgroup.com : charter.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : china.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : cn-kr.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : comcast.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : covad.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : cw.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : cybercon.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : dnsbl.antispam.or.id : ok
196.219.160.195 mail1.lotusgroup.com : dnsbl.njabl.org : ok
196.219.160.195 mail1.lotusgroup.com : dnsbl.sorbs.net : ok
196.219.160.195 mail1.lotusgroup.com : dsn.rfc-ignorant.org : ok
196.219.160.195 mail1.lotusgroup.com : eli.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : epoch.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : he.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : hongkong.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : inflow.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : infolink.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : interbusiness.blackholes.u
196.219.160.195 mail1.lotusgroup.com : internap.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : japan.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : korea.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : korea.services.net : ok
196.219.160.195 mail1.lotusgroup.com : l1.spews.dnsbl.sorbs.net : ok
196.219.160.195 mail1.lotusgroup.com : l2.spews.dnsbl.sorbs.net : ok
196.219.160.195 mail1.lotusgroup.com : lauderdale.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : level3.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : list.dsbl.org : ok
196.219.160.195 mail1.lotusgroup.com : malaysia.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : maxim.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : mexico.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : multihop.dsbl.org : ok
196.219.160.195 mail1.lotusgroup.com : nigeria.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : no-more-funn.moensted.dk : ok
196.219.160.195 mail1.lotusgroup.com : olm.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : pajo.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : ph.rbl.cluecentral.net : ok
196.219.160.195 mail1.lotusgroup.com : porn.rhs.mailpolice.com : ok
196.219.160.195 mail1.lotusgroup.com : postmaster.rfc-ignorant.or
196.219.160.195 mail1.lotusgroup.com : psbl.surriel.com : ok
196.219.160.195 mail1.lotusgroup.com : query.bondedsender.org : ok
196.219.160.195 mail1.lotusgroup.com : qwest.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : rackspace.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : relays.bl.kundenserver.de : ok
196.219.160.195 mail1.lotusgroup.com : relays.nether.net : ok
196.219.160.195 mail1.lotusgroup.com : rogers.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : rr.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : russia.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : satos.rbl.cluecentral.net : ok
196.219.160.195 mail1.lotusgroup.com : sbl.spamhaus.org : ok
196.219.160.195 mail1.lotusgroup.com : singapore.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : spamguard.leadmon.net : ok
196.219.160.195 mail1.lotusgroup.com : spam.wytnij.to : ok
196.219.160.195 mail1.lotusgroup.com : taiwan.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : telstra.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : thailand.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : tr.countries.nerd.dk : ok
196.219.160.195 mail1.lotusgroup.com : turkey.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : unconfirmed.dsbl.org : ok
196.219.160.195 mail1.lotusgroup.com : unsure.nether.net : ok
196.219.160.195 mail1.lotusgroup.com : verio.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : wanadoo-fr.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : whois.rfc-ignorant.org : ok
196.219.160.195 mail1.lotusgroup.com : xo.blackholes.us : ok
196.219.160.195 mail1.lotusgroup.com : yipes.blackholes.us : ok
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Are you using SPF?
http://www.openspf.org/SPF
I got this rejection as well if this report helps
Delivery has failed to these recipients or distribution lists:
Alaa Orfi 9D'! 91AI (ala@alexcountryclub.com)
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: mail362c25.carrierzone.com
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: exch-cas.lotusgroup.com
ala@alexcountryclub.com
mail362c25.carrierzone.com
Original message headers:
Received: from exch-mbx.lotusgroup.com ([192.168.0.17]) by
exch-cas.lotusgroup.com ([192.168.0.16]) with mapi; Thu, 29 May 2008 00:43:53
+0200
From: Amr Abouel Seoud <chairman@lotusgroup.com>
Date: Thu, 29 May 2008 00:43:52 +0200
Subject: McClellan says in new book that White House used propaganda to sell
war
Thread-Topic: McClellan says in new book that White House used propaganda to
sell war
Thread-Index: AcjBC+u41OnLdoYwSKyFEQcP9p
Message-ID: <6F3DCBBF2AF573449A5F474BE
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related;
boundary="_015_6F3DCBBF2AF
type="multipart/alternativ
MIME-Version: 1.0
196.219.160.195 comes back as mail1.lotusgroup.com because it's our external name
and our exchange server (machine Name) is exch-cas.lotusgroup.com
and as you know we can use more than one server name and mx record maped on one server
ex: mail.yahoo.com it's one server but they have more than mx record such as
yahoo.com MX preference = 1, mail exchanger = d.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = e.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = f.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = g.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = a.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = b.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = c.mx.mail.yahoo.com
Hi,
You need to separate this out a bit, but kind4me has exactly the right answer a few posts ago.
MX Records are used for Inbound mail, they have no impact on Outbound mail. What you have here is a name mismatch on the system processing Outbound mail.
For Exchange 2007 the name used to send mail is set on the Send Connector under Organisation Configuration, and depending slightly on your setup, can be under the Hub Transport or Edge Transport.
The name used *must* match the Reverse Lookup entry you have. That is, a server sending out on 196.219.160.195 must identify itself as mail1.lotusgroup.com or mail will bounce after failing that particular check. According to the messages above your mail server is identifying itself as "exch-cas.lotusgroup.com".
The solution, therefore, it to simply change the name used on the Send Connector.
HTH
Chris
I changed the Name of FQDN connector will provide in response to HELO or EHLO (in the Send Connector)under general to mail1.lotusgroup.com and still i got this rejected mail report
Delivery has failed to these recipients or distribution lists:
Alaa Orfi 9D'! 91AI (ala@alexcountryclub.com)
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: mail364c25.carrierzone.com
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: exch-cas.lotusgroup.com
ala@alexcountryclub.com
mail364c25.carrierzone.com
Original message headers:
Received: from exch-mbx.lotusgroup.com ([192.168.0.17]) by
exch-cas.lotusgroup.com ([192.168.0.16]) with mapi; Thu, 29 May 2008 13:05:48
+0200
From: Amr Abouel Seoud <chairman@lotusgroup.com>
To:
"=?windows-1256?Q?Alaa_Orf
=?windows-1256?Q?.com)?=" <ala@alexcountryclub.com>
Disposition-Notification-T
Return-Receipt-To: <chairman@lotusgroup.com>
Date: Thu, 29 May 2008 13:05:47 +0200
Subject: urgent please cal me when u get this email
Thread-Topic: urgent please cal me when u get this email
Thread-Index: AcjBc5WZJ1ApF/pTQX6FFO4qiR
Message-ID: <6F3DCBBF2AF573449A5F474BE
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related;
boundary="_004_6F3DCBBF2AF
type="multipart/alternativ
MIME-Version: 1.0
before changing the send connector name i sent email to my account at yahoo and this si the Full header
X-Apparently-To: amorty999@yahoo.com via 68.142.207.91; Sun, 25 May 2008 14:16:24 -0700
X-YahooFilteredBulk: 196.219.160.195
X-Originating-IP: [196.219.160.195]
Return-Path: <chairman@lotusgroup.com>
Authentication-Results: mta430.mail.re4.yahoo.com from=lotusgroup.com; domainkeys=neutral (no sig)
Received: from 196.219.160.195 (EHLO exch-cas.lotusgroup.com) (196.219.160.195) by mta430.mail.re4.yahoo.com with SMTP; Sun, 25 May 2008 14:16:24 -0700
Received: from exch-mbx.lotusgroup.com ([192.168.0.17]) by exch-cas.lotusgroup.com ([192.168.0.16]) with mapi; Mon, 26 May 2008 00:16:12 +0200
After changing the Send connector name to mail1.lotusgroup.com and made a restart to exchange
this is the Text Full header
X-Apparently-To: amorty999@yahoo.com via 68.142.207.89; Thu, 29 May 2008 03:23:20 -0700
X-YahooFilteredBulk: 196.219.160.195
X-Originating-IP: [196.219.160.195]
Return-Path: <chairman@lotusgroup.com>
Authentication-Results: mta188.mail.re3.yahoo.com from=lotusgroup.com; domainkeys=neutral (no sig)
Received: from 196.219.160.195 (EHLO mail1.lotusgroup.com) (196.219.160.195) by mta188.mail.re3.yahoo.com with SMTP; Thu, 29 May 2008 03:23:19 -0700
Received: from exch-mbx.lotusgroup.com ([192.168.0.17]) by exch-cas.lotusgroup.com ([192.168.0.16]) with mapi; Thu, 29 May 2008 13:21:46 +0200
U can read that the recieved has change in the First Line from : 196.219.160.195 (EHLO exch-cas.lotusgroup.com) to (EHLO mail1.lotusgroup.com)
and still i recieved this error report
Delivery has failed to these recipients or distribution lists:
Alaa Orfi 9D'! 91AI (ala@alexcountryclub.com)
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
The following organization rejected your message: mail365c25.carrierzone.com
_____
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: exch-cas.lotusgroup.com
ala@alexcountryclub.com
mail365c25.carrierzone.com
Original message headers:
Received: from exch-mbx.lotusgroup.com ([192.168.0.17]) by
exch-cas.lotusgroup.com ([192.168.0.16]) with mapi; Thu, 29 May 2008 13:30:12
+0200
From: Amr Abouel Seoud <chairman@lotusgroup.com>
To: Fathi Bakoush <fathiB@aol.com>
CC:
"=?windows-1256?Q?Alaa_Orf
=?windows-1256?Q?.com)?=" <ala@alexcountryclub.com>
Date: Thu, 29 May 2008 13:30:11 +0200
Subject: test please call me now
Thread-Topic: test please call me now
Thread-Index: AcjBdv4GOjxTIszuT4i3o9kdxr
Message-ID: <6F3DCBBF2AF573449A5F474BE
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related;
boundary="_004_6F3DCBBF2AF
type="multipart/alternativ
MIME-Version: 1.0
You've done pretty much all you can to ensure mail is sent out correctly.
You'll have to contact the recipient by other means and have them contact Carrier Zone (http://carrierzone.com/in
Carrier Zone's site contains no useful information at all on why things might be blocked.
You should find you can deliver to AOL and such correctly now at least.
Chris
I hope it is true that i can deliver to AOL but i got this error delayed message lests wait and c what happens
Delivery is delayed to these recipients or distribution lists:
Fathi Bakoush
Subject: test
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 5/31/2008 1:13:34 PM (GMT+02:00) Cairo. Microsoft Exchange will notify you if the message can't be delivered by that time.
_____
Sent by Microsoft Exchange Server 2007
You should see that in the Queue on Exchange if it's not managed to go through. It should have an Error Message (if any) listed there. Most likely is RFC Compliance if it's to AOL, worth checking that really is the case though.
If it is AOL have you made any changes to DNS records recently? AOL and the like perform a lot of extra DNS caching that can really try your patience after fixing an issue.
Chris
yes chris as i said in first describing my problem we changed our MX record and ISP lately that was about one month ago at the begining most sites like yahoo and hotmail and gmail rejected our mail since the DNS did not match on all sites however that problem disappeared after a couple of days when our NEW DNS was rplicated through out the internet however only those to mails AOL and alexcountryclb.com reject our mail still
Yeah I saw that bit, I just wondered about more recent changes. AOL cache for a few days to a week extra which really doesn't help when trying to troubleshoot these kind of things.
AlexCountryClub is a complete unknown, I've never encountered that (Carrier Zone) anti-spam provider before, and they have a really shoddy website providing no information or contact detail at all. That means it will have to be sorted out by the administrators for AlexCountryClub.
Perhaps we should go over the DNS / Server configuration again just to check? I'm pretty sure it's correct now from what you've said.
Chris
Business Accounts
Answer for Membership
by: kind4mePosted on 2008-05-28 at 13:09:04ID: 21663878
AOL uses reverse DNS lookup. If your exchange server (or firewall ) is not reporting the same IP as your MX record AOL will place it into the Spam folder or reject it.