Questions, answered.

Yes. MailLogic receives messages sent to addresses on your domain and forwards them to the destination address you choose. You can continue reading incoming mail in your current inbox without moving to a new email provider or creating a separate mailbox.

Receiving and sending are separate. You can use MailLogic for forwarding only, or add a MailLogic sending option when you need one.

Yes. “Send mail as” is a free Gmail feature and does not require Google Workspace or another paid Google plan. You can configure it with your MailLogic SMTP credentials to send from your custom-domain address. MailLogic SMTP itself requires a paid MailLogic plan.

Google has announced that third-party SMTP support for “Send mail as” will end in January 2027 and may restrict new configurations before then. This change does not affect incoming mail forwarded by MailLogic to a Gmail address. See Google's announcement.

No. MailLogic is an email routing and sending service, not a general-purpose mailbox. Incoming mail is forwarded to the inbox you choose.

Outgoing mail can be sent from the MailLogic dashboard, through Batch Send or an API where available, or from a compatible email client or application using MailLogic SMTP.

MailLogic Replies provides a conversation view for supported MailLogic sends, but it does not replace your main inbox.

Yes. You can add a subdomain such as mail.example.com to MailLogic without moving example.com.

Your root domain can keep using Google Workspace, Microsoft 365, another email provider, or no email service at all. MailLogic treats the subdomain as its own domain for sending and forwarding.

MailLogic also recognizes when the domain you add is a subdomain and adjusts the DNS setup instructions accordingly.

Yes. Multiple services can be authorized to send email for the same domain.

MailLogic can be added to your existing sending setup by updating your SPF record and adding MailLogic DKIM records. Your existing mailbox provider can continue working as before, while MailLogic adds SMTP, API, and Batch Send capacity.

Receiving works differently. Incoming mail is routed according to the domain’s MX records. The MX server with the lowest preference value is tried first, while higher-value records normally serve as fallback destinations.

Because of that, MX records are not a way to have two independent mailbox providers receive the same incoming mail in parallel. For each domain or subdomain, one receiving setup normally owns the inbound mail flow.

You can create personal addresses using your first name, last name, or full name, as well as role-based addresses such as admin@, support@, hello@ or press@. Each address can forward to an inbox you already use, so you can create professional addresses for different people or functions without setting up separate mailboxes.

When someone emails an address you've created, MailLogic receives it on your domain and relays it to your chosen destination inbox. The message keeps the original visible sender and recipient information.

Yes. Catch-all forwarding sends mail for otherwise unconfigured addresses on your domain to an inbox you choose. You can turn it on or off without deleting any email addresses you've configured individually.

Yes. Every plan includes forwarding with no fixed monthly volume limit, subject to fair use. The plan's limit applies only to the number of named email addresses you create and manage individually, not to the number of messages forwarded, including messages received through catch-all.

The Free plan includes up to five forwarding-only named addresses. The SMTP plan keeps the five-address limit and enables sending for each one. Starter and Founder raise the limit to 15 or 50 sending-enabled addresses. These address limits are separate from forwarding volume, which has no fixed monthly limit and is subject to fair use. See pricing for details.

Yes. Every paid plan includes Send Email in the dashboard. Choose an active sending address, add up to 100 recipients across To, Cc, and Bcc, write plain-text or HTML content, preview the message, and attach up to 25 MB of files. Send Email is best when everyone should receive the same message.

Yes, Gmail's third-party “Send mail as” feature can connect to MailLogic SMTP, but Google has announced that the feature will end in January 2027 and may restrict new configurations before then. An alternative is to use MailLogic Send Email in dashboard, or use your MailLogic SMTP credentials with another compatible email client or application. While Google's decision impacts SMTP capability from Gmail, forwarding incoming mail to Gmail is unaffected.

Yes. If an application lets you enter an outgoing mail server, port, username, and password, you can generally use your MailLogic SMTP credentials to send email from your domain.

This includes email clients as well as websites, business applications, monitoring tools, and other software that supports custom SMTP settings. You do not need to send from the MailLogic dashboard—the application connects to MailLogic using the SMTP credentials for your email address, and MailLogic handles the delivery.

Each SMTP-enabled MailLogic address has its own credentials.

• Use Send Email for one message with the same content for every recipient.
• Use Batch Send for separate, personalized transactional messages created from CSV rows and template variables.
• Use authenticated SMTP when an email client or application should send through MailLogic.
• Use the Send API for programmatic transactional email, or the Batch Send API for asynchronous personalized batches.

Send Email, Batch Send, and SMTP are included on every paid plan. The Send API and Batch Send API are included on Starter and Founder.

Yes. On Starter and Founder, your app or website can send transactional messages through the Send API using a domain API key. The Batch Send API accepts up to 500 separate personalized messages on Starter and 2,000 on Founder, asynchronously. Standard Send API requests do not create MailLogic Replies conversations. See the Send API page for a quick curl and Python example.

Each recipient uses one SMTP credit. Automatic top-up is off by default. You can buy additional credits from Billing at any time or opt in to automatic top-ups with your saved card. Send Email, Send API, and Batch Send reserve the complete sendable recipient set and do not partially send when credits are short. A waiting Batch Send can resume after a manual purchase within its 24-hour retention window. Purchased credits are used FIFO after the monthly allowance and roll over on the same plan. Forwarding is never affected by your SMTP credit balance.

MailLogic verifies SPF, DKIM, and DMARC and signs outgoing messages so receiving systems can authenticate your domain. That is an important foundation, but it cannot guarantee inbox placement. Recipient engagement, sending history, message content, complaint rates, list quality, and each receiving provider's policies also affect placement.

Batch Send creates separate, personalized emails from a single template and a CSV recipient list. Each batch supports up to 100 recipients on SMTP, 500 on Starter, and 2,000 on Founder. Your CSV must include each recipient’s email address and can include additional fields—such as name, amount, or company—to use as variables in the subject or message body. Add variables to your template using placeholders such as {{name}} or {{amount}}, and MailLogic automatically replaces them with the corresponding values for each recipient. Before sending, MailLogic validates the CSV and lets you preview each rendered email.

Each sendable row uses one SMTP credit. Previously suppressed recipients are shown during validation, skipped, and not charged. Attachments are not supported in Batch Send. Dashboard Batch Send is included on every paid plan; Batch Send API access is included on Starter and Founder.

MailLogic Replies is an in-dashboard conversation view for supported MailLogic sends. Users can receive response from recipients in dashboard and reply directly. MailLogic Replies works with emails sent from dashboard Batch Send, API Batch Send. and a one-to-one dashboard Send Email when you explicitly select MailLogic Replies under Reply-To.

Ordinary Send API and authenticated SMTP sends do not create Replies conversations. Replies is not a general inbox. Reply subjects and bodies are kept for the bounded retention period shown in the dashboard and then purged. Attachment contents are not stored; the conversation only notes that attachments were present.

• Submitted: MailLogic accepted the message for outbound processing.
• Accepted by destination or Sent: the recipient's mail server accepted it. This does not guarantee inbox placement.
• Deferred: the destination temporarily refused it and the mail server is retrying.
• Pending: MailLogic does not have a conclusive destination result yet.
• Bounced: the destination returned a permanent rejection.
• Failed: submission or delivery failed, or retries expired.
• Unknown: MailLogic could not confirm whether submission succeeded.
• Suppressed: MailLogic skipped the recipient before submission because of qualifying earlier failures.

For Batch Send, a completed progress count means dispatch has finished; use the outcome counts or Logs to check the later SMTP result for each recipient.

MailLogic suppresses recipients after qualifying permanent or repeated final delivery failures, helping prevent repeated sends to addresses that are unlikely to accept mail. The protection applies across the workspace to dashboard Send Email, Send API, Batch Send, and MailLogic Replies.

Batch Send, Send API and MailLogic Replies skip suppressed recipients, and skipped recipients do not use credits. Review the reason for last failure under Log → Suppressed recipients, where you can restore an suppressed address when it is safe to try again. Additionally, dashboard Send Email has a real-time function that warns you and allows a deliberate override while you are sending.

To receive email, you add the MailLogic MX records. To send, you also add SPF, DKIM, and DMARC records for authentication. You don't have to work these out yourself — MailLogic generates the exact records and you paste them at your DNS provider. The domain setup page explains each one in plain language.

Yes. MailLogic works with any registrar or DNS provider where you can add records — the records are standard MX, TXT, and CNAME entries. Add them wherever your domain's DNS is managed and MailLogic will detect them.

Adding the records takes a few minutes. After that, DNS changes propagate — usually quickly, occasionally up to a few hours depending on your provider. MailLogic re-checks automatically and marks each record as verified, so you'll see when your domain is ready.

MailLogic won't leave you guessing. Each record shows a live status, and any that's missing or incorrect is flagged with unverified state instead of a green dot. Fix or re-paste that record and MailLogic re-verifies it. Until DNS records are correctly in place, mail to your domain won't be forwarded, or SMTP won't be enabled — which is why the status view matters.

First confirm your MX record shows green dots in MailLogic dashboard and that the address exists and points to the correct destination inbox. If DNS only recently changed, give it a little time to propagate. Search the destination inbox and check Spam, filters, and blocked-address settings. Also check that the sender was not blocked in MailLogic. On paid plans, use Logs to confirm whether MailLogic received and forwarded the message.

Yes. Block Email stops incoming mail from a specific sender address or an entire sender domain before it reaches your forwarded inbox. This is separate from recipient suppression, which protects outbound application sends after qualifying delivery failures. Recent forwarding and SMTP activity are available in Logs, including forwarding results, destination-server acceptance, deferrals, bounces, failures, and suppression.