Solved

Relay mail using SBS2003/Exchange 2003 to Office 365

Posted on 2011-09-13
5
1,600 Views
Last Modified: 2012-05-12
Hi,

Got a little issue.
My Company switched to Office 365 recently.
Now i want (need) our local sbs2003 server to relay mail for some things (UPS, backup status, scan to mail) to the office 365 smtp server.
I configured the default SMTP virtual server on sbs2003 to use a smarthost (podxxxxxx.outlook.com). using TLS and TCP port 587.
I also created a routing group that forwards all mail to the same podxxxxxxx.outlook.com. (tried with an adres space of * and with individual domains).  Also configurred outbound security and enabled TLS.

When i try a test mail i get no error. It's never received either.
The exchange message tracking says the mail is routed and queued for remote delivery.

Anyone who has a clue what i'm missing/doing wrong?
Any help appreciated.
0
Comment
Question by:JHagman
  • 3
  • 2
5 Comments
 
LVL 12

Expert Comment

by:marcustech
ID: 36535048
check in the Queue under Exchange --> <Server name> --> Queues and see if the message is stuck there - if it is, click on it to see more details at the bottom. Also check %systemroot%\logfiles\SMTPSVC1 for related errors.
0
 

Author Comment

by:JHagman
ID: 36535145
Queue says it can't connect to remote smtp (the podxxxx.outlook.com) so there must be something wrong with the settings (i asume).
The queue error on the smtp connector: The remote server did not respond to a connection attempt.


The logfile shows no errors.

So it's either my config for authentication or the podxxxxx is rejecting connections.

0
 
LVL 12

Accepted Solution

by:
marcustech earned 250 total points
ID: 36535157
Check if podxxxx.outlook.com is accepting connections on port 587 ("telnet podxxxx.outlook.xom 587" from command line) - you won't actually be able to test smtp but can at least see if the server accepts the connection. If it accepts the connection (screen will go blank) then there's probably something up with your authentication settings, if not there's either a port blocked by a firewall somewhere or the server name is wrong.
0
 

Author Closing Comment

by:JHagman
ID: 37070579
Since it's still not working here, i'll close the question.
We found another "workaround".
0
 
LVL 12

Expert Comment

by:marcustech
ID: 37073418
If it's still not working and you would like it to work, rather than closing the question you could respond and let us know what the result of your telnet test is.  Then we can advise further troubleshooting steps and hopefully resolve your issue.  Thanks for accepting the answer though.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

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.
Adoption of Microsoft’s Enterprise Mobility and Security solution and Office 365 will re-order the File Sync and Share market Microsoft has stated that its Enterprise Mobility + Security (EMS) is the fastest growing product in the history of the …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …

816 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

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now