InnerWeb
Skip to main content

System mail flagged as spoofing: a case from a client's mailbox

Invitations and login codes ended up in quarantine because the client's mail system treated them as an attempt to impersonate its own company. The cause was not in the DNS configuration, but in what the system wrote in the display name of the sender. We describe the symptoms, the diagnosis and the change that solved the problem.

34 chars
limit for first name and company in the sender name
Source: karta
6
languages of the message footer
Source: karta

Symptom: invitations that do not arrive

After the installation went live, users reported that they were not receiving invitations or codes. The mail administrator found them in quarantine with a spoofing label. The messages came from an external domain, and the display name carried the client's company name. For a mail filter this is a classic pattern: a sender from a foreign domain presents itself as the organization of the recipient.

The problem hit the most sensitive messages: system invitations and second-factor codes. Without them an employee could not create an account or log in, so the IT department received reports on the first day the system was used.

Diagnosis: not DNS, but the sender name

The first reflex is to check the SPF, DKIM and DMARC records. In this case they were correct and needed no change. The shared sending address of the system sits in the vendor's domain, and the records of that domain stay unchanged. Only the display name of the sender and the Reply-To address were changing.

The difference between an address and a display name is the key point here. The mail filter compares what the user sees in the From field with the domain of the actual sender. When the name suggests the recipient's company and the domain is foreign, the anti-spoofing rule fires, even if domain authentication passes without objection.

What was changed and what stayed the same

What was changed and what stayed the sameChart: three DNS records unchanged and two header fields changed0123elementsDNS records unchanged (SPF,DKIM, DMARC)DNS records unchanged (SPF, DKIM, DMARC): 3 elements3Fields changed (sender name,Reply-To)Fields changed (sender name, Reply-To): 2 elements2
Source: Component card: description of the mail sender identity

Solution: the name shows who generated the message

The change means that the sender name tells the truth about where the message came from. The person who triggered the sending appears under their own first name, surname and company, followed by a note that the message went through the system. Messages without a person, such as password reset, MFA code and password change confirmation, are signed as a system message. First name and company are shortened to 34 characters so that the name fits the From field on a phone.

The Reply-To address is set to the person's address only when the message has an actor and that actor has an address. System messages have no Reply-To, so a reply does not reach a random person. The footer of every message contains a sentence about the two domains with the address of the instance host and appears in 6 languages, and the invitation has a line at the top naming the person who invited.

What the mail administrator did

On the client's side two steps were enough: releasing the messages from quarantine and adding the system's sending domain to the list of trusted senders in line with company policy. There was no need to change DNS records in the client's domain, because the sender remains the vendor's domain.

  • Release the messages from quarantine for the first users.
  • Add the system's sending domain to trusted senders according to the adopted policy.
  • Send a test message of each kind: invitation, password reset, MFA code.
  • Check the headers of the test: SPF, DKIM and DMARC results and the Reply-To field.

Conclusions for the mail administrator

When system messages land in quarantine with a spoofing label, first compare the display name with the sender's domain, and only then open the DNS records. Many reports are closed by this comparison alone.

Test invitations and login codes before inviting the first group of employees. One test of each kind of message takes a few minutes and saves a day of reports to the IT department.

Video

Frequently asked questions

Does the client have to change DNS records?

Not in the case described. The sender is the vendor's domain, and SPF, DKIM and DMARC did not need changes. The display name and Reply-To changed.

Why do MFA codes have no Reply-To address?

Because they have no actor. Reply-To is set only for messages triggered by a person who has an e-mail address.

How do I check that the problem is gone?

Send a test invitation, a password reset and an MFA code, and in the headers check the result of domain authentication and the From field.

Let's test the mail before inviting users

We will send test messages of every kind and, together with the mail administrator, check the headers before the first group receives invitations.

Let's talk