Which aspect of EPP are you submitting for?
Endpoint Protector Server
What is a one sentence summary of your feature request?
Support SendGrid SMTP Authentication
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Endpoint Protector currently validates the SMTP username as an email address.
This prevents direct use of Twilio SendGrid.
SendGrid requires the SMTP username to be the literal value “apikey”, with the password set to a SendGrid API key.
Endpoint Protector rejects this configuration because apikey is not a valid email address.
The SMTP username field should therefore allow the value apikey when SendGrid is being used.
Alternatively, Endpoint Protector could add a specific SendGrid SMTP option that applies the correct authentication method.
This would allow Endpoint Protector to send email directly through SendGrid without requiring additional infrastructure or an alternative mail service.
How do you currently solve the challenges you have by not having this feature?
Our current workaround is to use Microsoft 365 OAuth for SMTP.
While this works, it requires a dedicated Microsoft 365 account, ongoing account lifecycle management and monitoring, and Conditional Access exclusions or exceptions to ensure Endpoint Protector can continue to authenticate.
We would prefer to use SendGrid for application-generated email, as it is designed specifically for this purpose and avoids the dependency on a Microsoft 365 user account.
Supporting SendGrid’s required SMTP authentication would allow us to simplify our email configuration while reducing the operational overhead associated with the current workaround.
