Gmail Shows a Question Mark Next to Your Name: What It Means and the Fix

When Gmail cannot confirm that a message really came from the domain in the From address, it replaces the sender's avatar with a question mark and adds "Gmail could not verify that it actually came from" the domain. It is not a spam verdict, but it is one step away from one, and since 2024 the same missing records cause outright rejection for many senders. The fix is two DNS records, and you can confirm it from the recipient's side in under a minute.

Quick answer

Add an SPF record and a DKIM record for the domain, so at least one of them passes and aligns with the From address. Gmail shows the question mark only when neither SPF nor DKIM authenticates the message. Once the records are live, new messages show your initial or photo instead. A DMARC record is the next step, and it is required for any logo to appear.

What Gmail is checking

• SPF: does the server that handed Gmail the message appear in the From domain's SPF record? Pass requires the record to list your provider's servers.
• DKIM: does the message carry a valid signature whose public key is published in your domain's DNS? Pass requires the provider to sign with a key you published.
• Alignment: does the domain that passed match the domain in the From header? A pass for a different domain (the provider's, for example) does not count.

Fix it

1. Open the OquMail dashboard, choose your domain and copy the SPF and DKIM records shown there. Add them at your DNS host: SPF as a TXT records (short text lines in DNS used for email security) on the root, DKIM as a TXT record at the selector name ending in ._domainkey.
2. Add the DMARC record as well while you are there. It starts with v=DMARC1 and goes on a TXT records (short text lines in DNS used for email security) at _dmarc. With p=none it changes nothing yet but turns on reports.
3. Click Verify in the dashboard, then send a message from the domain to a Gmail address.
4. In Gmail, open the message, click the three dots and choose Show original. The summary at the top should read SPF: PASS, DKIM: PASS and DMARC: PASS, each with your domain next to it.
5. The question mark disappears on messages sent after the records went live; it stays on old messages.

Still showing a question mark?

• The message was sent from a mail app configured with another provider's SMTP server, so SPF fails. Use mail.oqumail.com on port 587 as the outgoing server.
• A website or tool sends "from" your address through its own servers. Either add that sender to SPF and get it to sign with your DKIM key, or send those messages through the API instead.
• Two SPF records exist on the domain. Receivers treat that as no record. Merge them; see more than one SPF record.
• The DKIM record was pasted with a line break or with the domain appended to the host. The DKIM guide shows how the host and value should look.

Getting a logo instead of an initial

A photo appears only for senders Gmail knows, such as Google accounts. For a company logo on any domain, Gmail supports BIMI: a DMARC policy at quarantine or reject, an SVG logo published in DNS, and a Verified Mark Certificate from a certificate authority, which costs money and requires a registered trademark. Most small businesses stop at the initial, which looks perfectly normal.

Common questions

Is the question mark the same as the red padlock?

No. The open red padlock means the message was not encrypted in transit (no TLS). OquMail delivers over TLS wherever the receiver supports it, so that icon should not appear on your mail.

Does it affect delivery?

Unauthenticated mail is far more likely to be filtered, and Gmail rejects it outright from many senders with a 550 5.7.26. Fixing the records removes both problems at once.

Want to see how your own domain is set up? Use the free SPF checker and DMARC checker: they run in your browser and store nothing.