AuthRelay is a new service under active development and testing. It is provided for evaluation on an “as is” and “as available” basis. It is not yet a production service.
Separate beta service — no guarantee or SLA
AuthRelay is a separate beta service and is not part of the main AuthSMTP service or your AuthSMTP contract. Any guarantees or service-level agreements (SLAs) applicable to the main AuthSMTP service do not extend to AuthRelay. We provide no service guarantee or SLA for AuthRelay during beta, including for availability, reliability or email delivery. Your existing AuthSMTP contract remains unchanged.
Availability and changes
The beta may contain faults, become unavailable, change or be withdrawn without notice. No service-level commitment or guarantee of uninterrupted operation is provided for the beta. Do not rely on it as the sole route for business-critical email, monitoring alerts or other essential communications.
Connection hostnames
AuthRelay must only be accessed using the hostnames supplied by us. Do not configure your email system to connect using an IP address instead. Direct IP connections are unsupported and may fail TLS certificate verification. IP addresses may change at any time without notice; always use the supplied hostname so your system can resolve the current address through DNS.
Email delivery
Successful connection or acceptance by an upstream SMTP server does not guarantee delivery to the recipient. Failures, delays and uncertain sending outcomes may occur. A retry after a connection failure can result in a duplicate message. Keep an alternative sending route and verify delivery independently.
Security and compliance
The initial TLS bridge terminates the client’s TLS connection and creates a separate encrypted connection. Credentials and message content pass through the bridge in memory; the bridge does not maintain a customer-password database or a local mail queue.
TLS 1.3 support, or successful connection from a FIPS-enabled client, does not mean that AuthRelay or the complete email delivery path is FIPS validated or meets a particular regulatory requirement. You are responsible for assessing suitability for your security and compliance requirements before use.
Account requirements and acceptable use
An appropriate AuthSMTP account is required. Existing account restrictions, sending limits and authentication requirements continue to apply. Use of your underlying AuthSMTP account remains subject to the applicable AuthSMTP Terms of Service and Acceptable Usage Policy.
Information and responsibility
Information on this website may be incomplete or contain errors and may change as the service develops. You should assess the risks of beta use and maintain suitable alternatives. Nothing in this disclaimer excludes or limits rights or liabilities that cannot lawfully be excluded or limited.
If you have questions about testing or suitability, please contact AuthSMTP.
Last updated: 15 September 2026
Back to AuthRelay