WebGee Docsالتوثيق
Email

Report a false positive

Legitimate mail rejected or filtered — what to gather, and what to check first, since most rejections have a cause you can fix.

Legitimate mail is being rejected or filtered. Applies to mail sent from and received by WebGee accounts.

Check these first

Most rejections are not false positives, and these four account for nearly all of them.

SMTP authentication is off. Sending without authenticating adds several points to the spam score on its own — see Fix "550 Please turn on SMTP Authentication".

SPF or DKIM is wrong. A domain that does not authenticate scores worse on every message — see Set your SPF record.

The content triggered it. Subject lines in capitals, shortened links, or a message that is one large image — see Fix "550 This message was classified as SPAM".

The mailbox is compromised and sending spam you did not write — see Fix the 550 5.7.1 [SS] rejection.

If none of those apply

Open a ticket with your support PIN and include:

  • The full bounce message, verbatim as text
  • The message headers — see Get the full headers of an email
  • The sending and receiving addresses
  • When it happened, with a timezone
  • Whether it is every message or occasional

Send these as text, not screenshots. The rejection is traced by matching the message ID against delivery logs, and an image cannot be searched. A ticket with a screenshot of a bounce takes several exchanges to get to the same place.

For inbound mail filtered wrongly

Mail arriving with {Spam?} in the subject was scored as probable spam and delivered anyway — see Spam and virus filtering.

You can filter on that tag in your mail client. If a specific correspondent is consistently tagged, include one of their messages with full headers in your ticket.

On this page