none
Send Connector to Send to Specific Host

    Question

  • Recently, we have installed a fax appliance which has the capability of using T.37 to convert an email to fax. I'm running into an issue with my send connector on our Exchange 2013 environment. The send connector is set up to send to an external smart host as our email is scanned outbound by a cloud service. So the format that the fax server requires is that the email has to be addressed to something like fax=5555551234@fax.domain.org with the "fax=" followed by the fax number followed by '@' and then the host name of the appliance. All of the documentation states that as long as I have a DNS record for the fax host, the Exchange server should simply forward it to the host as specified after the @. However, it seems that the send connector is just sending it along to our cloud spam filter instead of keeping it internal. What would be the best way to have the server recognize that anything sent to @fax.domain.org should go directly to that host name and not send it off to the cloud filter?
    Tuesday, November 24, 2015 9:42 PM

Answers

  • Recently, we have installed a fax appliance which has the capability of using T.37 to convert an email to fax. I'm running into an issue with my send connector on our Exchange 2013 environment. The send connector is set up to send to an external smart host as our email is scanned outbound by a cloud service. So the format that the fax server requires is that the email has to be addressed to something like fax=5555551234@fax.domain.org with the "fax=" followed by the fax number followed by '@' and then the host name of the appliance. All of the documentation states that as long as I have a DNS record for the fax host, the Exchange server should simply forward it to the host as specified after the @. However, it seems that the send connector is just sending it along to our cloud spam filter instead of keeping it internal. What would be the best way to have the server recognize that anything sent to @fax.domain.org should go directly to that host name and not send it off to the cloud filter?

    Create a specific send connector for the FAX messages

    Set  the address space of this send connector to fax.domain.org.

    Set the smarthost on the FAX send connector to the host name that represents the fax providers SMTP gateway


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.


    • Edited by Andy DavidMVP Tuesday, November 24, 2015 10:11 PM
    • Marked as answer by Scott_42 Tuesday, November 24, 2015 10:29 PM
    Tuesday, November 24, 2015 10:11 PM

All replies

  • Recently, we have installed a fax appliance which has the capability of using T.37 to convert an email to fax. I'm running into an issue with my send connector on our Exchange 2013 environment. The send connector is set up to send to an external smart host as our email is scanned outbound by a cloud service. So the format that the fax server requires is that the email has to be addressed to something like fax=5555551234@fax.domain.org with the "fax=" followed by the fax number followed by '@' and then the host name of the appliance. All of the documentation states that as long as I have a DNS record for the fax host, the Exchange server should simply forward it to the host as specified after the @. However, it seems that the send connector is just sending it along to our cloud spam filter instead of keeping it internal. What would be the best way to have the server recognize that anything sent to @fax.domain.org should go directly to that host name and not send it off to the cloud filter?

    Create a specific send connector for the FAX messages

    Set  the address space of this send connector to fax.domain.org.

    Set the smarthost on the FAX send connector to the host name that represents the fax providers SMTP gateway


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.


    • Edited by Andy DavidMVP Tuesday, November 24, 2015 10:11 PM
    • Marked as answer by Scott_42 Tuesday, November 24, 2015 10:29 PM
    Tuesday, November 24, 2015 10:11 PM
  • This seems to have worked. Thank you so much!
    Tuesday, November 24, 2015 10:29 PM