Overview / SendGrid Setup
SendGrid Setup
Provider-specific setup for running Virtual Mailer through SendGrid SMTP with authenticated sender identity, safer throttling, and production-ready validation.
When to Use SendGrid SMTP
SendGrid SMTP is appropriate when you want a managed sending provider instead of sending through a mailbox server, local Outlook profile, or internal relay. It is often the simplest path for authenticated, scalable SMTP delivery in Virtual Mailer.
Managed Delivery
SendGrid handles the outbound mail infrastructure while Virtual Mailer handles campaign creation and execution.
API-Key Authentication
You authenticate with an API key rather than a normal mailbox password.
Domain-Based Sending
Best results come from authenticating your own sending domain instead of relying on generic sender identity.
Why Users Commonly Choose SendGrid
- SendGrid provides managed outbound infrastructure instead of relying on a local mailbox server.
- It is often easier to scale and control than sending through a single user mailbox.
- It works well with Virtual Mailer when you want SMTP delivery backed by a provider-oriented reputation and authentication workflow.
Before You Configure the Account
- An active SendGrid account.
- Access to your domain's DNS records.
- A sender address that belongs to the domain you plan to authenticate.
- Permission to create and store an SMTP-capable API key.
- Access to Virtual Mailer's Mail Accounts module.
Create a SendGrid API Key
- In SendGrid, open
Settings > API Keys. - Create a key with the permissions needed for sending mail.
- Use a scoped key instead of a broad all-access key whenever practical.
- Copy the key immediately and store it securely. SendGrid generally will not show the full key again after creation.
Authenticate Your Sending Domain
- Open
Settings > Sender Authenticationin SendGrid. - Authenticate the domain you want recipients to see in the From address.
- Publish the DNS records SendGrid provides.
- Wait for verification to complete before relying on the account for larger sends.
Choose the domain carefully. The domain used in your From address should be the same one supported by your authentication and reputation strategy.
Configure the Mail Account in Virtual Mailer
| Field | Recommended Value | Notes |
|---|---|---|
| Send Method | SendGrid SMTP | Select the SendGrid-specific route in the Mail Account editor. |
| SMTP Server | smtp.sendgrid.net |
When SendGrid SMTP is selected, Virtual Mailer shows this field and forces it to the correct SendGrid hostname. |
| Port | 587 |
When SendGrid SMTP is selected, Virtual Mailer shows this field and forces it to the standard SendGrid submission port. |
| Encryption | TLS | When SendGrid SMTP is selected, Virtual Mailer shows the encryption field and forces it to TLS. |
| SendGrid Email | Your verified sender email address | When SendGrid SMTP is selected, the editor renames the User Name field to SendGrid Email. This must match the sender email configuration you use in SendGrid. |
| SendGrid Name | Your verified sender display name | This field becomes visible only in SendGrid SMTP mode. It must match the sender-name configuration you use in SendGrid. |
| API Key | Your SendGrid API key | When SendGrid SMTP is selected, the Password field is relabeled to API Key. Paste the API key exactly as issued. |
Important SendGrid-Specific Notes
- Virtual Mailer does not use the old generic SMTP pattern for the SendGrid UI.
- When SendGrid SMTP is selected, the combo-change behavior renames the editable fields to SendGrid Email, SendGrid Name, and API Key.
- The API key belongs in the API Key field, which is the relabeled password field.
- The SendGrid Email and SendGrid Name fields must align with the sender identity configured in SendGrid.
- Virtual Mailer requires all three values for SendGrid mode: SendGrid Email, SendGrid Name, and API Key.
- Your From address should use a domain that has already been authenticated in SendGrid.
- If domain authentication is incomplete, delivery may technically work while inbox placement suffers.
What the Editor Changes Automatically in SendGrid Mode
- SMTP Server: shown and locked to
smtp.sendgrid.net. - Port: shown and locked to
587. - Encryption: shown and locked to TLS.
- Requires Authentication: hidden because SendGrid mode assumes authenticated relay.
- User Name label: changed to SendGrid Email.
- Sender Name field: made visible and relabeled to SendGrid Name.
- Password label: changed to API Key.
Apply Safe Initial Send Pacing
Even with a managed provider, you should not assume unlimited safe volume on day one.
- Start conservatively, for example
25 messages per sessionand10 secondsbetween sessions. - Increase only after you see healthy delivery behavior.
- Warm new sender domains and new campaign streams gradually.
- Avoid sending your largest list first.
Test the Account Before Production Use
- Save the Mail Account.
- Use
Testin the Mail Account editor to confirm SMTP connection and authentication. - Send a real test message to one or more inboxes you control.
- Confirm the From name, From address, and overall rendering look correct.
- Check whether the message lands in inbox, promotions, or spam.
- If tracking is enabled, validate unsubscribe and open-tracking behavior as part of the same test cycle.
Common SendGrid Problems and Fixes
| Problem | Likely Cause | What to Check |
|---|---|---|
| Authentication failed | Wrong SendGrid email, sender name, or API key | Confirm that the Virtual Mailer fields match the SendGrid sender configuration and that the API key is entered in the relabeled API Key field. |
| Messages send but show poor inbox placement | Domain authentication incomplete or reputation still warming | Verify authenticated domain status, sender alignment, content quality, and sending pace. |
| Recipients see branding mismatch | From domain is not aligned with authenticated domain | Check the visible sender address and the domain authenticated in SendGrid. |
| High throttling or unstable results | Sending volume increased too quickly | Lower batch size, increase wait time, and resume growth more gradually. |
| Tracking works inconsistently | Tracking configuration is separate from SendGrid SMTP routing | Review the hosted tracking setup in Tracking and Unsubscribe. |
Recommended Production Checklist
- Create a dedicated SendGrid API key for the sending workflow.
- Authenticate the exact sending domain you intend to use.
- Configure the Mail Account with SendGrid SMTP and validate the credentials.
- Start with conservative throttling.
- Send a real mailbox test and confirm sender identity alignment.
- Validate unsubscribe and tracking behavior before the first public campaign.
- Scale volume gradually after results remain stable.
SendGrid Questions Users Often Ask
Why does SendGrid use an API key instead of a normal password?
SendGrid treats SMTP authentication as an application-level integration model. The API key acts as the credential for relay access, which is why Virtual Mailer relabels the password field to API Key in SendGrid mode.
Why might recipients see “via sendgrid.net”?
This usually points to sender-identity or domain-authentication alignment issues. Authenticating your sending domain and using a matching From address reduces that visible provider-brand artifact.
Do I need SendGrid link branding?
It is not required for Virtual Mailer to send mail through SendGrid SMTP, but consistent branded links and authenticated domains usually support stronger trust and deliverability outcomes.
Next Steps
- Use Mail Accounts to create and tune the sending profile.
- Use Deliverability and Compliance before larger sends.
- Use Tracking and Unsubscribe if you also want hosted open tracking and unsubscribe processing.