Re: Single domain rejection

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks for the feedback, please post back your findings as I am always
looking for resolution to any issue posted.

--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner

"gtw" <gtw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D4C8D363-7943-4717-8A12-9C68453C9E21@xxxxxxxxxxxxxxxx
>I contacted the net admin on their end to verify I had the correct server
> information. I did not, but with the new information I was able to telnet
> into the server and get a response. I was not able to ping their server
> though. I have passed this information on to their net admin for
> additional
> followup.
>
> "John Oliver, Jr. [MVP]" wrote:
>
>> Can you simply PING there SMTP Server from your Exchange Server and get a
>> reply? Lets verify first you are at least able to hit their Server from
>> your location. As for dropping your Port 25 connection it really depends
>> on
>> how they have setup their Firewall/Router to block your IP. My guess is
>> that Port 25 traffic is not the only traffic being blocked. They could
>> have ICMP requests disabled so you need to verify they have this enabled
>> before performing a simple ping test. See if they turn on some
>> monitoring
>> on their end to see if they can verify your IP is making a connection on
>> their end. Most Routers/Firewalls will allow for logging inbound
>> connections.
>>
>> --
>> John Oliver, Jr.
>> MCSE, MCT, CCNA, Exchange MVP
>> Microsoft Certified Partner
>>
>> "gtw" <gtw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:57FA8496-7CB3-4AF2-883C-BA120D3415AD@xxxxxxxxxxxxxxxx
>> >I do have another question regarding this. If port 25 is being blocked
>> > wouldn't this not be more wide spread on their end. The other company
>> > is
>> > receiving mail from others just fine. We are the only ones
>> > experiencing
>> > issues getting mail to them. Could we be specifically filtered out at
>> > the
>> > port?
>> >
>> > "gtw" wrote:
>> >
>> >> Thank you for your insight. I tried to tell them this before, but
>> >> apparently
>> >> I told the wrong person. I will try again with a little more
>> >> persistance
>> >> this time. I will post the resolution just FYI once this is resolved.
>> >>
>> >> "John Oliver, Jr. [MVP]" wrote:
>> >>
>> >> > Well, then you are being blocked at their Router, Firewall or
>> >> > Exchange
>> >> > Server. I would call their Admin and tell them your findings.
>> >> >
>> >> > --
>> >> > John Oliver, Jr.
>> >> > MCSE, MCT, CCNA, Exchange MVP
>> >> > Microsoft Certified Partner
>> >> >
>> >> > "gtw" <gtw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> > news:94E1A52C-FCC7-406A-9312-FC4C7E49CFBE@xxxxxxxxxxxxxxxx
>> >> > > no I cannot.
>> >> > >
>> >> > > "John Oliver, Jr. [MVP]" wrote:
>> >> > >
>> >> > >> Can you make a telnet connection on port 25 to their mailserver?
>> >> > >> http://support.microsoft.com/kb/q153119/.
>> >> > >>
>> >> > >> The message rejected portion of the NDR tells me that they are
>> >> > >> filtering
>> >> > >> their mail somehow with Antispam Software, Reverse DNS, etc.
>> >> > >>
>> >> > >> --
>> >> > >> John Oliver, Jr.
>> >> > >> MCSE, MCT, CCNA, Exchange MVP
>> >> > >> Microsoft Certified Partner
>> >> > >>
>> >> > >> "gtw" <gtw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> > >> news:F27BD82D-D129-49BF-AB0C-7FC1B9F20EB7@xxxxxxxxxxxxxxxx
>> >> > >> >I am having an NDR issue. Within the past week we have not been
>> >> > >> >able to
>> >> > >> > email to a domain that we have always been able too, and it is
>> >> > >> > the
>> >> > >> > only
>> >> > >> > domain that this is happening to us with. We have not made
>> >> > >> > any
>> >> > >> > changes
>> >> > >> > on
>> >> > >> > our side, and we have had the net admin from the other domain
>> >> > >> > check to
>> >> > >> > see
>> >> > >> > if
>> >> > >> > there have been any changes on their end, and there have not
>> >> > >> > been
>> >> > >> > any.
>> >> > >> >
>> >> > >> > One NDR indicates: Could not deliver the message in the time
>> >> > >> > limit
>> >> > >> > specified. Please retry or contact your administrator.<"our
>> >> > >> > domain".com
>> >> > >> > #4.4.7>
>> >> > >> >
>> >> > >> > The second NDR indicates: This message was rejected due to the
>> >> > >> > current
>> >> > >> > administrative policy by the destination server. Please retry
>> >> > >> > at
>> >> > >> > a
>> >> > >> > later
>> >> > >> > time. If that fails, contact your system administrator. <"our
>> >> > >> > domain.com
>> >> > >> > #4.3.2>.
>> >> > >> >
>> >> > >> > The other domain receives email from other companies, but not
>> >> > >> > from
>> >> > >> > us.
>> >> > >> > I
>> >> > >> > looked in the Exchange system manager and pulled up some of the
>> >> > >> > offending
>> >> > >> > emails to see what was in there. The following is an excerpt:
>> >> > >> > 7/13/2005 9:27 AM Tracked message history on server "our
>> >> > >> > server"
>> >> > >> > 7/13/2005 9:27 AM SMTP Store Driver: Message Submitted from
>> >> > >> > Store
>> >> > >> > 7/13/2005 9:27 AM SMTP: Message Submitted to Advanced
>> >> > >> > Queuing
>> >> > >> > 7/13/2005 9:27 AM SMTP: Started Message Submission to
>> >> > >> > Advanced
>> >> > >> > Queue
>> >> > >> > 7/13/2005 9:27 AM SMTP: Message Submitted to Categorizer
>> >> > >> > 7/13/2005 9:27 AM SMTP: Started Outbound Transfer of Message
>> >> > >> > 7/13/2005 9:27 AM Message transferred out to
>> >> > >> > namicnav1.namic.org through SMTP
>> >> > >> > 7/13/2005 9:18 AM The log file
>> >> > >> > '\\namicnav1\Tracking.Log\20050713.log'
>> >> > >> > is not available.
>> >> > >> >
>> >> > >> > Eventually...
>> >> > >> > 7/13/2005 11:29 AM SMTP: Non-Delivered Report (NDR)
>> >> > >> > Generated
>> >> > >> >
>> >> > >> > Sorry if this post appears choppy. I have not had any luck
>> >> > >> > looking in
>> >> > >> > the
>> >> > >> > MSKB, so I am turning to you. If you have any idea as to what
>> >> > >> > is
>> >> > >> > going
>> >> > >> > on
>> >> > >> > I
>> >> > >> > would greatly appreciate a little guidance. Thank you.
>> >> > >> >
>> >> > >> > Jason
>> >> > >> >
>> >> > >>
>> >> > >>
>> >> > >>
>> >> >
>> >> >
>> >> >
>>
>>
>>


.

Relevant Pages

  • Re: Single domain rejection
    ... Can you simply PING there SMTP Server from your Exchange Server and get a ... Lets verify first you are at least able to hit their Server from ... As for dropping your Port 25 connection it really depends on ... MCSE, MCT, CCNA, Exchange MVP ...
    (microsoft.public.exchange2000.admin)
  • Re: RPC over HTTP Certificate Issue
    ... Please close port 80 - you don't need this port open (unless you are hosting ... I installed the certificate in trused certificates, ... the server side config seems to be all set and working, ... How to Verify That World Wide Web Publishing Service Is ...
    (microsoft.public.windows.server.sbs)
  • Outlook Express
    ... Please verify that you ... have entered the server name correctly. ... above with two exceptions: Protocol: POP3, Port 110. ...
    (microsoft.public.windowsxp.general)
  • Re: Single domain rejection
    ... I contacted the net admin on their end to verify I had the correct server ... > that Port 25 traffic is not the only traffic being blocked. ...
    (microsoft.public.exchange2000.admin)
  • RE: Some technical errors
    ... If the SMTP server is not running on port 25 TCP it is not a public ... Manager - Computer Assurance Services BDO Chartered Accountants & ...
    (Security-Basics)