• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

RE: Problem sending a message

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> RE: Problem sending a message Page: <<   < prev  1 [2]
Login
Message << Older Topic   Newer Topic >>
RE: Problem sending a message - 26.Feb.2007 9:37:44 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Remember earlier in this thread when I had you use NSLOOKUP?  You responded:

quote:

When typing Set type=MX followed by problem.com it returned our server details along with:

Non authoritive answer:
problem.com MX preference = 10 mail ecxhanger = relay.name.co.uk
problem.com MX preference = 20 mail ecxhanger = relay2.name.co.uk

relay.name.co.uk   internet address = 12.12.12.12
relay.name.co.uk   internet address = 34.34.34.34
relay.name.co.uk   internet address = 56.56.56.56
relay.name.co.uk   internet address = 78.78.78.78


You obviously substituted false addresses for the actual ones (which is fine for the purposes of this public forum).

What you should be typing is something like:
telnet 12.12.12.12 25
where the actual address you enter is what was displayed in the NSLOOKUP results. You can also type:
telnet relay.name.co.uk 25
Keeping in mind you should first test with the address with the smallest preference number (because that's what a messaging system would do).

< Message edited by uemurad -- 26.Feb.2007 10:01:09 AM >


_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 21
RE: Problem sending a message - 26.Feb.2007 2:53:22 PM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
I typed in telnet for the MX ip and MX name given at home - both gave me the same error (554 check your SMTP server settings) which im sure are set to my ISP via Outlook.

I then RDP into my work server/workstation which came back with the original error with problem.com cannot relay......

So should i try to get the other MX records and try again (it only displayed 2 out of 4)? or would i get the same issue? If so according to that website i cant do this within my doman as it will get false results. Should i remove a PC off the domain and try again? or would that too be pointless?

Thanks

(in reply to uemurad)
Post #: 22
RE: Problem sending a message - 26.Feb.2007 4:34:29 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
From this same home PC, can you telnet onto your own Exchange server?  It could be either your PC or your home ISP is blocking access to port 25.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 23
RE: Problem sending a message - 28.Feb.2007 10:04:28 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
quote:

ORIGINAL: uemurad

From this same home PC, can you telnet onto your own Exchange server?  It could be either your PC or your home ISP is blocking access to port 25.


Yes your right i went to canyouseeme.org and it states it cant see port 25. So is there a way around this?

(in reply to uemurad)
Post #: 24
RE: Problem sending a message - 28.Feb.2007 10:09:43 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
If you are using a 3rd-party firewall and/or are running the WinXP firewall at home, then try disabling it as a test (just long enough to attempt to telnet to your server).  If that doesn't help, contact your ISP to see if they are blocking.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 25
RE: Problem sending a message - 28.Feb.2007 1:43:42 PM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
Tried disabling the FW etc and same result. My ISP are blocking it so no home user can run a web server and will not alter that. Is there a way to change SMTP port from 25 to another open port??

(in reply to uemurad)
Post #: 26
RE: Problem sending a message - 28.Feb.2007 1:55:16 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Since the receiving side has to be listening on the same port, this is probably not an option.

Since all of this was just to test whether the receiving server was the issue, can you perform the telnet test from your Exchange server instead?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 27
RE: Problem sending a message - 28.Feb.2007 2:41:26 PM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
Yes i should be able to do that for tomorrow. Do i perform the exact test that i couldnt from home but on the exchange server? if so according to that website that would give incorrect results????

(in reply to uemurad)
Post #: 28
RE: Problem sending a message - 28.Feb.2007 4:04:31 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Yes.  The reason you want to do this on your Exchange server is to simulate the message being sent out.  If you can manually create/deliver a message from your server to the outside system, then you'll know it's not a communication issue, nor the other system's issue.

If you can establish the telnet session and get part way through the manual SMTP commands then get error codes back, then that's the part you can troubleshoot.

If the manual creation succeeds completely, then the problem is on your side.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 29
RE: Problem sending a message - 1.Mar.2007 10:00:36 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
I did the test from our exchange server. I used open relay.name.co.uk instead of the IP add as this time when i did a test via telnet it was fine. Anyway i got to stage 10 when i received:

553 You are trying to use me [server.name.messagecentre
553-.com] as a relay, but i have not been configured to let
553-you [1.2.3.4 - our IP] to do this. Please
553-visit sitname.com/support for more details
553-about this error message and instructions to resolve
553 this issue. (#5.7.1)

Speaking to one of their guys i have the following headers

Received: from name.problem.com ([192.168.2.1]) by n4000 with ESMTP
       (1.40.112.12/16.2) id AA207198868; Fri, 2 Feb 2007 12:21:08 GMT
Return-Path: <us@ourdomain.co.uk>
Received: from mail.messagecentre.com (mail.messagecentre.com) by name.problem.com  (Clearswift SMTPRS 5.2.5) with SMTP id <T7d8ecc2e24ac1002019e4@name.problem.com> for <test@problem.com>;  Fri, 2 Feb 2007 12:17:37 +0000
X-Viruschecked: Checked
X-Env-Sender: Us@ourDomain.co.uk
X-Msg-Ref: server-9.tower-17.messagecentre.com!1170418465864!29498064!1
X-Starscan-Version: 5.5.10.7.1; banners=-,-,problem.com
X-Originating-Ip: [12.12.12.12]
X-Spamreason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
Received: (qmail 16513 invoked from network); 2 Feb 2007 12:21:04 -0000
Received: from c2bthomr11.btconnect.com (HELO cname.ExternalSender.com)
(12.12.12.12)
by server.Name.messagecentre.com with SMTP; 2 Feb 2007 12:21:04 -0000
Received: from server.OurDomain.local (mail.OurDomain.co.uk [34.34.34.34] (may be forged))
       by name.Forwarder.com
       with ESMTP id CKL7254582;
       Fri, 2 Feb 2007 11:32:10 GMT

It seems our domain possibly thinks it being forged or something??

(in reply to uemurad)
Post #: 30
RE: Problem sending a message - 1.Mar.2007 10:14:15 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Just to confirm, when you performed the telnet test:
1.  The mail from address was a valid address in your domain
2.  The rcpt to address was a valid address in the recipient's domain

More specifically, the domain names listed were yours and theirs respectively? 

As an example, if you attempted to telnet to my server, listing yourself as sender and a Yahoo address as the recipient, my server would reject the message because you were attempting to use my server as an improper relay.  If you were to send the same message directly to Yahoo, or if the recipient address was a domain name I accept, it would work.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 31
RE: Problem sending a message - 1.Mar.2007 10:50:20 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
In answer to your questions:

1.Yes but see below for a definate example of what i did
2. It was my address form our domain as step 10 on that web says address@yourDomain so for example:

Problem.com is their domain and OurDomain is our domain

i typed open relay.problem.co.uk
- It gave me a message 220 TheirServerName.messagecentre.com
ehlo problem.com
- received 250 TheirServerName.messagecentre.com
- 250 piplelining
- 250 8bitmime
mail from: me@personalEXTERNALEmail.com
- 250 OK
rcpt to:me@ourDomain.co.uk
 
Then i got the error message which i posted above (Note above i used my external email then my work email which is on an Exchange server)

(in reply to uemurad)
Post #: 32
RE: Problem sending a message - 1.Mar.2007 11:06:44 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
quote:

rcpt to:me@ourDomain.co.uk

This tells the server you are connecting to (problem.com) that you are trying to send a message to an address they don't process.  This is relaying and should be denied.  This will work if you are connecting to your own server, but not to theirs and not to mine.  It should instead read something like:

rcpt to:their.guy@problem.com


_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 33
RE: Problem sending a message - 1.Mar.2007 11:21:31 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
Ok when i changed that to their.guy@problem .com it went staright through without any problems. The last line read (before i entered quit):

250 OK 5487797964 qp 26975 theirServer.messagecentre.com!5487794567!65456465!1

Sounds like we have the problem at our end?

(in reply to uemurad)
Post #: 34
RE: Problem sending a message - 1.Mar.2007 11:33:32 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Try one more time to send the message from Outlook.  What you are looking for now is to make sure that Exchange is getting the same DNS information you got by manually looking it up, and opening the communication to the proper server on their side.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 35
RE: Problem sending a message - 1.Mar.2007 11:39:59 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
To confirm - I send an email from outloook -

1. Do i use our domain email or external?
2. Who do i send the email to if to problem.com do i need to ask them to send me back the headers?
3. Do i check the DNS information by doing one of the previous tests or via headers?

(in reply to uemurad)
Post #: 36
RE: Problem sending a message - 1.Mar.2007 10:49:18 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
I'm going to cram a big IF-THEN into this message to cut down on some of the back-and-forth. 

Send a message from Outlook to a valid address at the problem domain.  Ask for a reply.  If you get one, everything is good.  If you don't, test DNS from your Exchange server using NSLOOKUP, the SET TYPE=MX command and the name of the problem domain.  Don't use the SERVER command because this time we're checking to see what your Exchange server is getting for a DNS response.  Verify whether or not it matches the FQDN you used for the successful Telnet test.  If it matches, check Message Tracking again looking for the Outlook message you just sent.  If it doesn't match, you need to track down why the DNS server Exchange is contacting has old information. 

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to EssCee)
Post #: 37
RE: Problem sending a message - 5.Mar.2007 6:14:47 AM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
Hopefully i have the correct info here.
Sent a message via outlook received no reply when sent of Friday but Monday morning i have the following received:
Your message did not reach some or all of the intended recipients.
      Subject: Test Message
     Sent: 02/03/2007 09:51

The following recipient(s) could not be reached:
      user@problem.com on 04/03/2007 10:05
           Could not deliver the message in the time limit specified.  Please retry or contact your administrator.
           <server.ourDomain.local #4.4.7>

Comparing nslookup and DNS with this line from the telnet test
250 OK 54456754 qp 24565 theirServer.messagecentre.com!5487794567!65456465!1
i dont have any of the above info listed when i did the nslookup test. I only have
quote:


problem.com MX preference = 10 mail ecxhanger = relay.name.co.uk
problem.com MX preference = 20 mail ecxhanger = relay2.name.co.uk
relay.name.co.uk   internet address = 12.12.12.12
relay.name.co.uk   internet address = 34.34.34.34
relay.name.co.uk   internet address = 56.56.56.56
relay.name.co.uk   internet address = 78.78.78.78

So not sure if this is what your after?? I then went to www.dnsstuff.com and did a whois to see if that brings anything different it returned back with:
quote:


Unfortunately, this domain is registered through Network Solutions, who does not support
WHOIS lookups from DNSStuff.com because of the volume of hits from us.
If you don't like this policy, please send an E-mail to whoisquery@networksolutions.com
or call 1-888-642-9675 and let them know it you don't like it.  Alternatively, you can
file a complaint with Internic.
If this is your domain, please consider using a registrar who values the services we provide.
If you have changed registrars, you can click here to update our cache...Redirecting you in 15 seconds...

Finally i looked in the message centre and it has the same results as my very first post which were
quote:


Message Transfered to name1.domain.com through SMTP
SMTP: Started Outbound transfer of message
Message Transfered to name2.domain.com through SMTP
SMTP: Started Outbound transfer of message
Message Transfered to name3.domain.com through SMTP
SMTP: Started Outbound transfer of message
Message Transfered to name4.domain.com through SMTP
SMTP: Started Outbound transfer of message

This is repeated again and again for a few hours, and name1 is changed to a different name during that period.
Thanks

(in reply to uemurad)
Post #: 38
RE: Problem sending a message - 13.Mar.2007 1:10:03 PM   
EssCee

 

Posts: 154
Joined: 7.Sep.2006
Status: offline
I also noticed if anyone in the firm sends a message to this problem domain the message also hangs in Queues.......any idea about that?

(in reply to EssCee)
Post #: 39

Page:   <<   < prev  1 [2] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> RE: Problem sending a message Page: <<   < prev  1 [2]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter