SMTP Configuration
Configure your own SMTP server to send emails from your domain.
Default SMTP
By default, Glambot Studio uses its own SMTP server. Configuring a custom SMTP is optional and recommended only if you want to:
- Send from your own domain (@your-company.com)
- Have full control over deliverability
- Manage your own sending limits
Why Configure Your SMTP?
| Advantage | Description |
|---|---|
| Custom Domain | Send from your own email address |
| Better Deliverability | DKIM/SPF configuration to avoid spam |
| Full Control | Manage your quotas and sending limits |
| Traceability | Track sends from your SMTP provider |
Access Configuration
SMTP configuration is done at the Organization level:
- Click on your name in the top right
- Select "Organizations"
- Navigate to the "SMTP Settings" section
Create an SMTP Configuration
Required Information
| Field | Description | Example |
|---|---|---|
| Name | Configuration identifier | "Gmail Pro" |
| SMTP Server | Server address | smtp.gmail.com |
| Port | Connection port | 587 |
| Username | Login identifier | your-email@domain.com |
| Password | Password or application key | *** |
| TLS | Connection security | Enabled |
| Sender Email | Sending address | noreply@your-domain.com |
Procedure
- In organization settings, "SMTP" section
- Click "Add SMTP Configuration"
- Fill in the information
- Click "Save"
- Test the configuration
Common Configurations
Gmail / Google Workspace
Server: smtp.gmail.com
Port: 587 (TLS) or 465 (SSL)
Authentication: Required
TLS: Enabled
For Gmail, you must create an "application password" in Google security settings. Do not use your regular password.
Outlook / Office 365
Server: smtp.office365.com
Port: 587
TLS: Enabled
Authentication: Required
SendGrid
Server: smtp.sendgrid.net
Port: 587
Username: apikey
Password: your-sendgrid-api-key
Mailgun
Server: smtp.mailgun.org
Port: 587
Username: postmaster@your-domain.mailgun.org
Password: your-mailgun-password
Amazon SES
Server: email-smtp.{region}.amazonaws.com
Port: 587
Username: your-access-key
Password: your-secret-key
Understanding DKIM and SPF
Email authentication is crucial for ensuring your emails reach recipients' inboxes rather than spam folders.
What is SPF (Sender Policy Framework)?
SPF is a DNS record that specifies which mail servers are authorized to send emails on behalf of your domain.
How it works:
- You publish an SPF record in your domain's DNS
- When an email is received, the recipient's mail server checks the SPF record
- If the sending server is listed in the SPF record, the email passes authentication
- If not, the email may be marked as spam or rejected
Example SPF record:
v=spf1 include:_spf.glambot-studio.app ~all
This means: "Emails from my domain can be sent by servers specified in _spf.glambot-studio.app"
What is DKIM (DomainKeys Identified Mail)?
DKIM adds a digital signature to your emails that proves they were sent by your domain and haven't been tampered with.
How it works:
- Your mail server signs outgoing emails with a private key
- You publish the corresponding public key in your DNS
- Recipient servers verify the signature using your public key
- If the signature is valid, the email is authenticated
Benefits:
- Proves email authenticity
- Prevents email tampering
- Improves sender reputation
- Reduces spam false positives
Why You Need Both
| Authentication | Purpose | Protects Against |
|---|---|---|
| SPF | Verifies sender server | Unauthorized servers sending as your domain |
| DKIM | Verifies message integrity | Email content modification in transit |
| Combined | Maximum deliverability | Spam filters, phishing, spoofing |
Always configure both SPF and DKIM for optimal email deliverability. Major email providers (Gmail, Outlook, Yahoo) strongly recommend both.
Configure DKIM and SPF
To improve your email deliverability, configure DKIM and SPF.
Automatic DKIM Generation
Glambot Studio can automatically generate your DKIM records:
- In SMTP configuration, "DKIM" section
- Click "Generate DKIM Records"
- Copy the generated DNS records
DNS Records to Add
Add these records to your DNS hosting provider:
DKIM Record:
Type: TXT
Name: glambot._domainkey
Value: v=DKIM1; k=rsa; p=[generated public key]
SPF Record:
Type: TXT
Name: @
Value: v=spf1 include:_spf.glambot-studio.app ~all
Glambot Studio provides an integrated generator to automatically create your DKIM and SPF records.
Verification
After adding DNS records (propagation delay: 24-48 hours):
- Return to SMTP configuration
- Click "Verify DKIM/SPF"
- The system automatically validates your records
Test Configuration
Before using your configuration in production:
- Click "Test Configuration"
- Enter a test email address
- Verify receipt of the test email
- Check that it doesn't arrive in spam
Troubleshooting
Unable to Connect to SMTP Server
Verify:
- Server address and port are correct
- Username and password are valid
- TLS is enabled if required by the server
- Your provider allows SMTP connections
Emails Sent But Not Received
Verify:
- Email is not in spam folder
- Sender address is authorized by your provider
- DKIM/SPF records are correctly configured
Emails Going to Spam
Common causes:
- DKIM/SPF not configured or invalid
- Sender domain not verified
- Content triggering spam filters
- Low domain reputation
Solutions:
- Configure DKIM and SPF
- Use mail-tester.com to diagnose
- Avoid spam trigger words
- "Warm up" your domain with gradual volume increases
DKIM/SPF Verification Failed
- Wait 24-48h for DNS propagation
- Verify with MXToolbox
- Ensure you copied records exactly (no extra spaces)
- Contact your DNS hosting provider if the problem persists
Best Practices
Security
- Use application passwords, not your main passwords
- Always enable TLS for encryption
- Limit access to SMTP configurations
Deliverability
- Configure DKIM and SPF from the start
- Test regularly with mail-tester.com
- Monitor bounce rates
- Maintain a good sender reputation
Management
- Clearly name your SMTP configurations
- Document access and configurations
- Have a backup configuration