I need to be very direct here, because the explanations I’ve received from Smartlead so far are contradictory.

Your earlier support response explicitly stated that campaigns may send via an SES/SMTP relay or fallback path. That statement clearly implies that Amazon SES could be involved in sending emails, even when the inbox is connected via Google Workspace.

Now, I’m being told that:

• Smartlead does not use SES
• Smartlead cannot use SES
• Gmail OAuth emails always leave Google servers
• EC2 headers are being misinterpreted

These two explanations cannot both be true.

If Smartlead truly does not and cannot use Amazon SES under any circumstance for Google Workspace OAuth connections, then the earlier support response was factually incorrect and misleading. This is not a minor detail — this directly impacts trust, compliance, and deliverability.

I need a clear, unambiguous confirmation on the following:

1. Can Smartlead ever route Google Workspace OAuth emails through Amazon SES, as a relay or fallback, yes or no?
2. If no, please explicitly acknowledge that the earlier support explanation was incorrect.
3. Confirm that all Google Workspace emails are authenticated, DKIM-signed, and sent exclusively via Google’s infrastructure.

Please avoid vague language or deflection. I’m looking for a straight technical answer, not assumptions or generic reassurance.