asked on

SBS 2011 Internal Application Sending E-Mail To Internal Exchange Server

I have looked and this has been discussed in a different light but not specifically this way and the answers have not worked for me. I have several internal applications that I would like to have to send email updates/failures on processes that occur in the background. Some of the applications have not issues and others repeatedly fail with "authentication" issues or unspecified reasons. I see not reason why this should occur and was wondering if anyone had experience in general with applications like this and what the problem is and is it something I can set or is it not designed to work this way from the vendor. For the most part I can use my smart host and send that way but it should work and doesn't and I would like to know why.

Korbus

Are these various applications configured seperately? If so, it could be simply an error in the configuration (un/pw) of those apps with problems.

Are the email apps that fail AND succeed all running on the same machine?

Are they all tring to connect to the same email account?

To know weather or not your apps SHOULD be able to do what you want, we would need more details about them.

mohrk

ASKER

Generally speaking they run on client, server and can also be devices. Both SBS connectors are listening on port 25 but that is the default I think.

Specifically. Symantec endpoint manager runs on same machine as exchange. No credentials, userid and password, domain/userid password. All on port 25. All unspecified error.

Next Acronis True Image 2014 premium. Is run from client, might as well repeat all of the above. Oh and add in TLS for this one SEPM only supports SSL for encryption.

Next Cradlepoint MBR1200B router. Encryption capable unclear as to what protocol it would use. Can use user id password. Various ports. All above tried with failures.

I am trying to think of successes bu the only thing that comes to mind is the internal reports that SBS sends out and internal email.

Thanks

mohrk

ASKER

You had more questions about the account. Yes they are generally connecting to my non-admin account. And they are configured separately as you might be able to tell already.

ASKER CERTIFIED SOLUTION

Korbus

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mohrk

ASKER

OK, SEPM problem resolved. servername - no, FQDN no, localhost yes. No auth not even "real" from address. Hmmm. This is on the exchange server itself.

From a client, from bogus address or real address - 503 5.7.1 client was not authenticated. The overwhelming response from google is enable anonymous on the default receive connector. Do I really want to do that? If so why then why do these apps have the ability to have userid and password? If it is merely to allow access to an offsite server then why can't mine be configured this way? i.e. why can't I set up a client on my network to securely connect to my exchange server?

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mohrk

ASKER

Thanks guys! Both problems resolved and expeditiously. Everything requires a from address despite some apps suggesting it was "optional" or advanced but a bogus address worked so??

I have port 25 mapped and filtered to certain sub-nets and port is 53 locked down to specific public DNS addresses so the router required the IP address of the server and an allow rule on port 25. This combination worked anyway.