Solved

Small Business Server SMTP connector not delivering mail.

Posted on 2007-12-06
7
390 Views
Last Modified: 2008-02-01
I am having an issue with the Exchange SMTP connector for rogerswirelessdata.com not delivering mail to a client's windows pc phone.The messages are stuck in the server queue and a restart of the SMTP service and the entire server have not resolved the problem. I have verified with Rogers Wireless that I am using the correct information for their server. The perplexing part is that during the initial setup and test, messages were routed correctly and delivered. The failure began to occur about 36 hours after the initial setup was complete. Any ideas on what is causing this issue?
0
Comment
Question by:DrDamnit
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 20420186
Can you telnet to port 25 of their mail server from the Exchange server?

Although the domain rogerswirelessdata.com doesn't appear to have any MX records, so if you are trying to route by DNS then it will probably fail.

Simon.
0
 
LVL 32

Author Comment

by:DrDamnit
ID: 20421502
Thank you. You have pointed me in the right direction. I have spoken to Rogers again and pointed out to them that rogerswirelessdata.com does not have any MX records. I was then provided with: pcs.rogers.com which does have MX records. My question now is; can I correct the address on the server, or do I need to do this on the device itself? If I can do it on the server, what are the steps involved?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 20422860
The fact that you are forwarding email to phones does not matter, as far as Exchange is concerned you are just sending an email to an address.

Have the phone company told you to use a different email address or domain? If so I presume that you are putting email addresses in somewhere for the forwarding to take place. If you are, then you need to update those email addresses as appropriate.

Simon.
0
Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

 
LVL 32

Author Comment

by:DrDamnit
ID: 20423209
The problem is that on the phone, when you setup automatic notifications (push technology stuff) you enter in an email address, which corresponds to sending text messages to the phone. Thus, when a new email is recieved, Exchange sends a text message to the phone telling the phone "hey, check your email," which starts the activesync process.

The question before the court is: can we change that notification email address without having to have the phone in hand (it is 2,000 miles away) and re-running the activesync setup wizard on the phone (Windows Mobile 6) or can I set that email address in active directory / exchange manager somewhere?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 20424592
Push doesn't use the text message method any more if you are using Exchange 2003 SP2. It uses http packets. I didn't even think WM6 supported the old text message method.

I think you may have setup the push technology in the wrong way.

This is my guide to setting up push.
http://www.amset.info/exchange/mobile-setup.asp

I would suggest that you get hold of the Windows Mobile emulator from Microsoft and try it for yourself.

Simon.
0
 
LVL 32

Author Comment

by:DrDamnit
ID: 20426620
Me thinks they don't have direct push. It's old school text message notification.

Here are two reasons why:
http://gogetmyfiles.com/resources/mobile-services.png
http://gogetmyfiles.com/resources/queue.png

The first is the MObile Services Properties screenshot, and the second is an SMTP connector queue that has 21 messages in it because the recieving server needs to be changed (what sparked this whole thread).
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 20426731
That means the server doesn't have Exchange 2003 SP2 installed. I wonder what else it doesn't have. Check whether the server is up to date at all - Windows 2003 SP2, SBS SP1, Exchange 2003 SP2 plus updates that are released after that.

Simon.
0

Featured Post

Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question