Best email forwarding service with delivery logs and recovery

Quick answer for email forwarding service delivery logs

You want three artifacts when a customer swears they sent mail: the public MX set, the receiving event with timestamp and remote response, and the destination inbox or its spam folder. A forwarder that cannot show the middle artifact leaves you arguing from memory. MailerZ records inbound and outbound hops, stores content for 14 days on Free or 90 days on paid plans, and preserves Header From on the forward. Envelope MAIL FROM may use SRS. It is not IMAP. It is not an archive product. It is not an open relay.

“Best” here means a stack you can test. Google’s people-first content guidance is the evidence style, not a ranking trophy: Creating helpful, reliable, people-first content. A log that says delivered while Gmail hid the message is still a useful log. A product that promises Primary is selling a thing no forwarder owns.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled. Paid plans keep 90-day recovery and add send-as within published limits. Solo is $40 per year. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Capability list: MailerZ features. Failed hops after a clean MX set: delivery recovery.

Cloudflare Email Routing and other inbound routers can move mail without giving you the same stored-hop model. Read Cloudflare — Email Routing documentation if that is the stack you run. ImprovMX is the closest commercial class; compare current plans on their site: ImprovMX — product documentation. Do not migrate because a blog used the word best. Migrate because you can name the artifact you were missing.

The user problem and the decision criteria

Teams shop for delivery logs after a weekend argument. A customer has a sent folder. Gmail is quiet. The old forwarder has a green check or nothing at all. Support guesses leftover MX, a filter, or a lie. Without a destination SMTP response, every guess is equally expensive.

Recovery is the sibling problem. A hop fails at 6 p.m. Friday. Monday the body is gone. A 14-day or 90-day window is not seven-year hold. It is enough to retry or to prove what arrived. If you need a legal archive, keep it in Gmail or buy hosting. Do not buy forwarding logs and then ask for eDiscovery.

A logging forwarder is a poor fit when you need tenant eDiscovery, when you want the vendor to promise inbox placement, or when you will never open the history UI. It is a good fit when a customer dispute must end with a timestamp and a remote code.

Technical mail flow

Logs attach to SMTP conversations. IETF RFC 5321 — Simple Mail Transfer Protocol is the transport. The sender looks up MX, delivers, and is done. Your forwarder then starts a second conversation with Gmail. Email forwarding service delivery logs should record both, or at least the second hop’s response. Inbox tabs are not in that transcript.

What MailerZ records

After verification and an alias match, MailerZ stores required content and metadata, returns 250 to the sender, and forwards. Header From stays the original sender. Delivery history keeps the destination response. If Gmail accepts and files the message in spam, history can still say delivered. That pair is the point of the product, not a contradiction.

Unknown recipients on Free are held. The hold is itself evidence: the local-part was not on the allow-list. Buying logs does not turn catch-all hold into a silent forward. Name the alias or enable paid catch-all forward when you mean it.

What recovery is

The store exists so a failed hop can be inspected or retried during the window. Opening a body for break-glass recovery can create an audit row. That is a control, not a marketing badge. After 14 days on Free or 90 days on paid, the window closes. Gmail remains the archive if the forward succeeded.

Outbound logs matter once you add paid SMTP. Authentication failures, 550 on unauthorized recipients, and plan-limit refusals should appear as SMTP facts, not as “Gmail is broken.” Unhosted or unauthorized send gets 550 / 550 5.7.1. MailerZ is not an open relay.

SPF, DKIM, and DMARC are outbound authorization. IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) are the texts. They do not write your inbound log. They do not place mail in Primary.

Message-ID is the other join key. Gmail’s UI hides it. Raw headers show it. MailerZ history should let you correlate the stored copy with the destination copy without guessing from timestamps. If two probes used the same subject, you will merge events in your head and file a false incident. Unique subjects are not a style preference. They are how a small team avoids lying to itself.

Retry behavior belongs in the runbook. A 4xx from Gmail is not the same as a 5xx. A timeout is not a filter. If you retry from the recovery store, record that you retried. A customer who sends once and a support agent who retries twice can look like three incidents in a sloppy spreadsheet. The log is only as good as the person reading the code, not the color of the badge in the UI.

Step-by-step setup and decision path

This is the email forwarding service delivery logs setup path. Get a matched pair of artifacts before you cut production MX.

1. Write the artifact you are missing

   If you already have Gmail and only lack a hop transcript, you are in this article. If you lack a mailbox, you are shopping for hosting. If you lack Calendar, you are shopping for a suite.

2. Add one domain and verify TXT

   Use the root domain. Publish the unique verification TXT. Receiving stays off until the check passes. Logs for an unverified domain will not exist yet.

3. Create a named alias and verify the destination

   Map hello@ to the Gmail you will search. Complete destination verification. A probe to an unverified destination wastes the first history row.

4. Publish one MX set and delete leftovers

   Copy exact hosts. Remove leftover Google, Microsoft, registrar, or prior forwarder MX. Query two resolvers. History cannot explain mail that never arrived because a second MX stole it. Use the migration planner if you are leaving another vendor.

5. Send a uniquely titled probe from another mailbox

   Open Gmail. Open MailerZ history. Match subject, timestamp, and destination response. Self-send from the same Gmail account can skip the hop and leave an empty log.

6. Practice one recovery while the window is open

   If a test hop fails, use the store inside 14 or 90 days. Do not wait a quarter. Confirm you know where the event lives before a customer is involved.

7. Add paid send-as only if outbound logs are in the acceptance test

   Free has no send-as. Solo and above add SMTP. Send to a second external inbox and read the outbound event. Plan limits: Solo 5/hour and 100/month; Starter 10 and 200; Business 15 and 400; Agency 25 and 800.

Failure modes and proof

Most “logs are useless” reports are leftover MX, a self-send test, or a team that expected history to override Gmail’s spam folder. Separate the cases.

Proof is always a pair: sanitized destination headers and the MailerZ event. Do not send SMTP passwords to support. Do not publish verification tokens. DNS-only tools: troubleshooting.

MailerZ workflow and product boundary

MailerZ is a custom-domain email delivery layer operated by Secuno LLC. Point MX at MailerZ. Mail for a hosted, verified domain can land in Gmail or Outlook. Paid plans add authenticated SMTP. Site: mailerz.net. App: mail.mailerz.net.

Positioning: a focused custom-domain forwarding plus authenticated SMTP option with hop evidence. That is the delivery-logs job. It is not a SIEM and not a mailbox host.

What MailerZ does

• Accept inbound mail for verified domains and configured recipients.
• Preserve Header From on the forward.
• Hold or forward unknown recipients according to plan and settings.
• Store messages 14 days on Free or 90 days on paid plans.
• Record delivery history for inbound and outbound hops.
• Send through authenticated SMTP on paid plans.
• Surface leftover MX as a diagnostic hard stop.

What MailerZ does not do

• Replace Gmail with IMAP or webmail.
• Rewrite header From, Subject, Date, Message-ID, body, or MIME.
• Offer send-as on Free.
• Promise inbox placement, uptime SLAs, or review counts.
• Claim SOC 2, ISO 27001, or HIPAA. Controls: Security.
• Act as an open relay or a campaign sender.
• Keep mail forever. The window closes.

Cost, alternatives, and trade-offs

You pay for the window and the transcript, not for a trophy log. Free is enough to learn whether history matches Gmail. Paid 90-day store is for operators who will actually open a failed hop next month. Solo is $40 per year when send-as and the longer window travel together.

Annual Starter, Business, and Agency billing includes two months free versus monthly. Solo has no monthly option. Alias ceilings: 3 / 15 / 50 / 200 / 500. If you cannot find a history row, raise leftover MX, not the plan, until public DNS is exclusive.

Shared inboxes produce noisy logs if three people forward the same alias into three Gmail accounts and only one of them filters aggressively. The history row will show three destination responses or one, depending on how you configured fan-out. Read the event, not the loudest founder. If only one destination is configured, only one 250 matters. The other two people are looking at a mailbox that was never on the route.

Time zones show up in disputes. A customer in UTC+9 sent at 09:00 their clock. Your history is UTC. Gmail’s sent folder is the customer’s local time. Teach support to compare Message-ID and the unique subject, not the wall clock. The join key you wrote in the probe is the same join key you need in production when the subject is an invoice number.

Agencies watching client domains should not treat history as a status page for the client’s Gmail. You can prove MailerZ accepted and that Gmail’s SMTP said yes. You cannot prove the client’s intern did not file the message. Put that sentence in the retainer. It prevents a refund argument that no log can win.

Break-glass recovery is for failed hops, not for curiosity. If someone opens bodies as a habit, you have an access problem, not a retention problem. Rotate who can open the store. Keep SMTP passwords out of tickets. The audit row exists so that a later reviewer can see the open, not so you can advertise a badge.

FAQ

Key takeaways

• The best email forwarding service with delivery logs records the destination SMTP response.
• A 250 is not Primary. Gmail can still hide the message.
• Recovery is 14 days on Free and 90 days on paid. It is not an archive.
• Header From stays the original sender. Envelope SRS is the allowed rewrite.
• Leftover MX makes history look random. Delete it.
• Test inbound from a different mailbox. Self-send lies.
• No history row means mail never arrived. A 250 plus quiet Gmail means a filter.
• Free has no send-as. Paid SMTP logs outbound refusals.
• MailerZ is not SOC 2, not IMAP, and not a bulk sender.

Conclusion and next action

Buy logs because you need a timestamp and a remote code, not because a comparison table said visibility. Keep Gmail. Publish one MX set. Probe from another mailbox. Match history to the inbox. Use the recovery window while it is open. Add paid send-as only if the From identity must travel.

MailerZ fits that job. It does not fit a legal vault or campaign telemetry. Start on Free if you only need to watch inbound for 14 days. Move to a paid plan when 90-day store or send-as is the acceptance test.

Next action: add one domain, create one alias, send a uniquely titled message from a mailbox that is not the destination, and keep both the history row and the Gmail copy.

Review quarterly, or sooner if MailerZ retention, destination SMTP behavior, or DNS guidance changes. Author: MailerZ editorial, Secuno LLC.