tookawhile
IS-IT--Management
We out source our email, and we are in the process of changing provider, but have hit upon the following snag.
We use BackExec and this has the ability to email job reports and the such like, this works fine with our current provider. The BackExec email client has no provision (that I'm aware of) to set a password, you can only set the sender name, sender address and port number, SMTP mail server. Our current email provider (even though they do not support open relay) somehow managed to allow this to work for us. When testing our email with the proposed new provider it fails authentication as no password is sent with the BackExec email client.
I was wondering if Server2003 can be configured as a very simple relay(?) forwarder(?) to send the email on to the new provider? If so how do I go about it?
I basically what the app to send a message to an internal email server, which then in turns, forwards onwards to our provider using a username and password.
We use BackExec and this has the ability to email job reports and the such like, this works fine with our current provider. The BackExec email client has no provision (that I'm aware of) to set a password, you can only set the sender name, sender address and port number, SMTP mail server. Our current email provider (even though they do not support open relay) somehow managed to allow this to work for us. When testing our email with the proposed new provider it fails authentication as no password is sent with the BackExec email client.
I was wondering if Server2003 can be configured as a very simple relay(?) forwarder(?) to send the email on to the new provider? If so how do I go about it?
I basically what the app to send a message to an internal email server, which then in turns, forwards onwards to our provider using a username and password.