<div>
<div class="content wysiwyg-content">
I've migrated our office from Exchange 2003 to Google Apps/Gmail. However, I have a few Xerox machines that I'd like to enable Scan to Email functionality on. The xerox machines don't seem to support SSL/TLS, so it's impossible to have them talk directly to Gmail's servers.<br />
<br />
Our exchange server is still running - How do I properly configure SMTP Connectors or the 'default SMTP virtual server' to be able to forward the email onto Gmail's SMTP servers?<br />
<br />
I've set the default SMTP virtual server to deliver with Outbound security using TLS and my Gmail credentials, with &quot;smtp.gmail.com&quot; as my fully-qualified host name under 'advanced delivery'<br />
<br />
I've also created an SMTP connector set to forward all mail through the smart host: 'smtp.gmail.com', set my gmail credentials under 'advanced', and the address space of '*.mydomain.com'<br />
<br />
At this point scans from my domain to external email addresses are sent correctly, but scans to a user on my domain, &nbsp;user@mydomain.com are not sent to gmail, and end up in the users exchange account, where they won't be seen.<br />

</div>
</div>


I've migrated our office from Exchange 2003 to Google Apps/Gmail. However, I have a few Xerox machines that I'd like to enable Scan to Email functionality on. The xerox machines don't seem to support SSL/TLS, so it's impossible to have them talk directly to Gmail's servers.

Our exchange server is still running - How do I properly configure SMTP Connectors or the 'default SMTP virtual server' to be able to forward the email onto Gmail's SMTP servers?

I've set the default SMTP virtual server to deliver with Outbound security using TLS and my Gmail credentials, with "smtp.gmail.com" as my fully-qualified host name under 'advanced delivery'

I've also created an SMTP connector set to forward all mail through the smart host: 'smtp.gmail.com', set my gmail credentials under 'advanced', and the address space of '*.mydomain.com'

At this point scans from my domain to external email addresses are sent correctly, but scans to a user on my domain,  user@mydomain.com are not sent to gmail, and end up in the users exchange account, where they won't be seen.


Connect Exchange SMTP to Gmail

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.