Link to home
Start Free TrialLog in
Avatar of cwelectric
cwelectric

asked on

How can I allow other applications to send mail through Exchange Server 2007?

I have a couple different scenarios, but am trying to achieve the same result: Sending mail through Exchange Server

Our phone system is a 3Com NBX V3000 VoIP solution. Within the system, there is the ability to do Offsite Notification via email. I have configured all options correctly and actually had it working at one point, but it has since stopped. The only option within the software to be configured for the mail server is "SMTP Domain Name". This issue may or may not be related to Exchange...I have not yet determined that yet. However, it may coincide with the following issue.


My other issue is with an online backup solution which we offer. This backup software has the ability to send emails to clients upon completion of a backup. Within this software, the items which can be filled in for mail are an email account, username, password, and mail server.

I can only get the backup software emails working if the email is sent to a user that also resides on our Exchange server. The software will not send to an external address. The Exchange log reports the following error when trying to send to an address that is not native to Exchange server. All emails work just fine when sending to a user on the same Exchange Server.
     
550 5.7.1 Unable to relay
RSET
250 2.0.0 Resetting


After some research and looking into the logs, I believe the issue lies within the Receive Connector. However, I am a bit unsure why I can send to other Exchange users, but not send outside. The online backup account is no different than any other user account setup within Exchange. In fact, I have actually plugged the onlinebackup account into Outlook and it could send/receive to outside users just fine.


Any ideas? Am I missing something here?
ASKER CERTIFIED SOLUTION
Avatar of Syedm2
Syedm2

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cwelectric
cwelectric

ASKER

I have read that article and complete those steps already. I already had the new Receive Connector created. I can also tell that emails sent by the "onlinebackup" user are being applied to that Receive Connector when I check the logs, but I am still getting the same error.

For what it's worth, I am not seeing ANY log that indicates the 3Com NBX is trying to relay mail using Exchange.
have you done any firewall changes in the past few months?

On the exchange server you can create an email address for an external user for the backup!
and it will relay the message to that person!


Avatar of Nitin Gupta
I have an actual user created withing AD called "onlinebackup". I have actually given that username a mailbox within Exchange server and confirmed the account working by plugging the username/password into a Microsoft Outlook client and sending mail.

These credentials are plugged into the web interface of our backup software in order to send the logs via email.

No firewall changes for at least a month. All mail ports are forwarding properly.
Change the protocol logging level on the relay conenctor to verbose and restart transport service.
The protocol logs will tell wat is the issue.
My receive connector is setup properly (I believe), based on the two articles posted in this thread.

On the "Network" tab, I have the IP addresses of two servers which I want to be able to authenticate.
Under "Authentication", I have "TLS" and "Externally Secured" selected.
Under "Permission Groups", I have simply selected all items.

As I said, I know this receive connector is working, because I can see it being applied within the log files when the backup server attempts to send an email.

Am I missing another setting here? I can post screenshots if necessary.
Verbose logging has been enabled already. That is where I found the error message that I posted when I started this thread, and how I know my receive connector is being applied to the proper mail.
Doesn't look like an exchange issue though
http://msexchangeteam.com/archive/2006/12/28/432013.aspx

That link apparently fixed the issue, it just took me a while to realize it since the backup software delays the sending of emails, for some reason.

Ok great.
so you do not think that I should get a few points as I see that you accepted my link!