Top Features of 1st Mail Sender You Should Know

Step-by-Step Guide: Setting Up 1st Mail Sender

Setting up 1st Mail Sender is straightforward — this guide walks you through installation, initial configuration, and verification so you can start sending reliable emails quickly.

What you’ll need

  • An active 1st Mail Sender account (sign-up completed)
  • A working email address to send from
  • Basic access to DNS settings for your sending domain (recommended for best deliverability)

1. Create and verify your account

  1. Sign up with your email and a secure password.
  2. Check your inbox for the verification email and click the verification link.
  3. Sign in to the dashboard.

2. Add your sending identity (email or domain)

  1. In the dashboard, go to “Senders” or “Sending Identities.”
  2. Click “Add Sender” and choose either:
    • Single email address (quick setup), or
    • Domain (recommended — allows sending from any address at that domain).
  3. Enter the email or domain and submit.

3. Verify your sender

  • For a single email: open the verification message sent to that address and click the link.
  • For domain: follow the dashboard instructions to add DNS records (TXT for SPF, TXT/CNAME for DKIM, and possibly an MX or TXT for verification).

4. Configure DNS records (for domain sending)

  1. Open your domain registrar or DNS provider panel.
  2. Add the SPF record provided (TXT). If you already have an SPF record, merge the allowed senders.
  3. Add the DKIM record(s) exactly as shown (TXT or CNAME).
  4. Add any additional verification record the dashboard shows.
  5. Return to 1st Mail Sender and click “Verify” — DNS changes can take from minutes to 48 hours to propagate.

5. Set up sending preferences

  1. Choose a default “From” name and address.
  2. Configure reply-to if different from the sender.
  3. Select sending region or IP options if offered (shared vs. dedicated IP).
  4. Set throttling limits if you plan large sends (messages per minute/hour).

6. Authenticate with SMTP or API

  • To send via SMTP:
    1. Copy SMTP host, port, username, and password from the dashboard.
    2. Add these credentials to your mail client, app, or server.
    3. Choose SSL/TLS or STARTTLS as recommended.
  • To send via API:
    1. Generate an API key in the dashboard.
    2. Store the key securely and add it to your application’s mail library following the provider’s API docs.

7. Test a send

  1. Send a test message to a set of addresses (Gmail, Outlook, and an internal account).
  2. Verify delivery, subject rendering, and that links/images appear correctly.
  3. If any test lands in spam, check SPF/DKIM status and the message content for spammy traits.

8. Monitor deliverability and set feedback handling

  1. Enable bounce and complaint webhooks or SMTP callbacks.
  2. Configure suppression lists and automatic unsubscribe handling.
  3. Regularly review delivery reports, bounce rates, and complaint metrics in the dashboard.

9. Optimize for best results

  • Warm up new IPs gradually by increasing volume over days.
  • Use double opt-in for subscriber lists.
  • Keep lists clean: remove hard bounces and unengaged addresses.
  • Personalize subject lines and content; avoid excessive links and spammy wording.

10. Troubleshooting checklist

  • DNS not verified: re-check records and propagation.
  • Emails marked spam: confirm SPF/DKIM, check content, and monitor sender reputation.
  • High bounce rate: validate list before sending and remove invalid addresses.
  • API/SMTP errors: verify credentials, ports, and firewall rules.

Quick checklist (copyable)

  • Create account and verify email
  • Add sender address or domain
  • Publish SPF and DKIM records
  • Verify domain in dashboard
  • Configure SMTP/API credentials
  • Send tests to multiple providers
  • Enable webhooks for bounces/complaints
  • Monitor metrics and warm IPs if needed

Follow these steps and you’ll have 1st Mail Sender configured for reliable sending and measurable deliverability.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *