If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Exchange 2003 has issues receiving from external domain.
Hello,
I am having sporadic issues with my Exchange 2003 mail server running on Windows SBS 2003. Every so often I will get an email from one of our clients that has the domain of zahav.net.il, which is based in Israel and I am based in the US, and they state that they received a non delivery report when sending to my domain with error code 4.4.7.
This is only sporadic, and sometimes I do indeed receive emails from them, and other times not. I am running Exchange 2003 version 6.5 SP2. This is really one of the only domains I seem to be experiencing issues when receiving. I have gone through my local mail queues and cannot find a single instance of the failed message. It's like it doesn't even hit my Exchange server. At first I was thinking that this is an issue with their mail server, but I have been made aware that the 4.4.7 errors seem to be related to the "receiving" server and not the "sending" server. I have checked to make sure my domain is not blacklisted, which it is not, and I also have the correct PTR record set on my domain.
Any help with this is greatly appreciated as I am at a stand still on what to test and troubleshoot any further. Thank you.
I am having sporadic issues with my Exchange 2003 mail server running on Windows SBS 2003. Every so often I will get an email from one of our clients that has the domain of zahav.net.il, which is based in Israel and I am based in the US, and they state that they received a non delivery report when sending to my domain with error code 4.4.7.
This is only sporadic, and sometimes I do indeed receive emails from them, and other times not. I am running Exchange 2003 version 6.5 SP2. This is really one of the only domains I seem to be experiencing issues when receiving. I have gone through my local mail queues and cannot find a single instance of the failed message. It's like it doesn't even hit my Exchange server. At first I was thinking that this is an issue with their mail server, but I have been made aware that the 4.4.7 errors seem to be related to the "receiving" server and not the "sending" server. I have checked to make sure my domain is not blacklisted, which it is not, and I also have the correct PTR record set on my domain.
Any help with this is greatly appreciated as I am at a stand still on what to test and troubleshoot any further. Thank you.
Who is Participating?
This is very good information and makes complete sense. Before I contact them to relay information as to what could be wrong on their sending servers end, is there anything else I could try to troubleshoot on my end to test this issue further. I just want to exhaust all my troubleshooting steps before pointing the blame back at their server.
Do you have any Anti-Spam software installed or a 3rd party filtering your mail before it reaches your server or an Anti-Spam device such as a Barracuda appliance?
Do you use the Intelligent Message Filtering on your server in the absence of any 3rd party / software / appliance?
Do you use the Intelligent Message Filtering on your server in the absence of any 3rd party / software / appliance?
I use a Red Hat Linux appliance with Symantec Mail Security for SMTP installed for filtering. I have already tracked and compared my logs with it and my Exchange server and they are identical, so I believe I can safely rule out my Red Hat appliance as a cause wouldn't you say?
Most mail-flow issues lies squarely at the sending server (not all - but most).
Based on their config which I have pointed out - your server is probably just looking at their configuration and rejecting them because they are not configured correctly - and whose fault it that?
Based on their config which I have pointed out - your server is probably just looking at their configuration and rejecting them because they are not configured correctly - and whose fault it that?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Either way - on the surface so far, it looks like they are to blame for their lack of email delivery and they need to sort their end out!
Their 2 MX records are:
100 mx-bk.inter.net.il. [TTL=120] IP=80.179.55.150 [TTL=120] [IL]
10 mx.inter.net.il. [TTL=120] IP=80.179.55.150 [TTL=120] [IL]
Both names point to the same IP Address which is a complete waste of time!!!!
Problem:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mx-bk.inter.net.il claims to be host mtain23.012.net.il [but that host is at 80.179.55.143 (may be cached), not 80.179.55.150]. <br />mx.inter.net.il claims to be host mtain20.012.net.il [but that host is at 80.179.55.134 (may be cached), not 80.179.55.150]. <br />
Plus their SPF record looks wrong and doesn't include their sending server, assuming they send AND receive on the same IP - which they might not!
v=spf1 ip4:192.114.186.0/24 ip4:213.8.233.0/24 ip4:213.8.234.0/24 ip4:213.8.235.0/24 ?all"