...
The example below illustrates this SPF information in the header of an email from a fictive institution mosamuseum:
| Expand |
|---|
| title | Détails techniques... |
|---|
|
| Info |
|---|
| Date: Wed, 26 Jun 2019 15:49:40 -0500 (CDT)
From: Mosa Museum <xxx@mosamuseum.com>
Received: from mail.mosamuseum.com ([192.28.148.112])
by mailgw1.xxx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2019 22:49:42 +0200
...
Received-SPF: Pass (mailgw1.xxx.com: domain of
postmaster@mosamuseum.com designates 192.28.148.112 as
permitted sender) identity=xxx; client-ip=192.28.148.112;
receiver=mailgw1.xxx.com;
envelope-from="307-QLA-991.0.109448.0.0.25078.9.15158552-23-364@mail.mosamuseum.com";
x-sender="postmaster@mosamuseum.com";
x-conformance=sidf_compatible; x-record-type="v=spf1";
x-record-text="v=spf1 a -all"
Subject: Here is a message from SecuTix infrastructure, with a SPF record authorized by mosamuseum.com
... |
|
In this example, the SPF record which is authorized to sent emails on behalf of mosamuseum.com is:
...