Subject: Save Big with Solar

From: "Solar Installers" <[email-masked]>
Date: Thu, 17 Nov 2022 05:25:04 -0800 (PST)

Spam detection software, running on the system "mx1.eskimo.com",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
[email-masked] for details.

Content preview:  Save Big with Solar http://antifungalcare.email/-KTOYJ8vS4WZ1fDp9mWLsOF2xOnedD3pEls0soZh7tZ21UEMuQ
   http://antifungalcare.email/uMRj8CaHcUvXGveP5lv37eScKas_SA_1vV3EysEjUY6JjVNcwA

Content analysis details:   (6.3 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 1.7 URIBL_BLACK            Contains an URL listed in the URIBL blacklist
                            [URIs: antifungalcare.email]
 1.9 URIBL_ABUSE_SURBL      Contains an URL listed in the ABUSE SURBL
                            blocklist
                            [URIs: antifungalcare.email]
-1.0 DMARC_PASS             DMARC check passed
 0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
 0.0 T_SPF_PERMERROR        SPF: test of record failed (permerror)
 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level
                            mail domains are different
 0.0 HTML_FONT_LOW_CONTRAST BODY: HTML font color similar or
                            identical to background
 0.0 PP_MIME_FAKE_ASCII_TEXT BODY: MIME text/plain claims to be ASCII
                             but isn't
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
 1.1 DCC_CHECK              Detected as bulk mail by DCC (dcc-servers.net)
 0.0 FSL_BULK_SIG           Bulk signature with no Unsubscribe
 0.1 DKIM_INVALID           DKIM or DK signature exists, but is not valid
 0.2 FROM_FMBLA_NEWDOM14    From domain was registered in last 7-14 days
 1.8 ADMITS_SPAM            Admits this is an ad
 0.0 KHOP_HELO_FCRDNS       Relay HELO differs from its IP's reverse DNS

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.

Subject: Save Big with Solar
From: "Solar Installers" <[email-masked]>
To: <[email-masked]>
Date: Thu, 17 Nov 2022 05:25:04 -0800 (PST)

Save Big with Solar

http://antifungalcare.email/-KTOYJ8vS4WZ1fDp9mWLsOF2xOnedD3pEls0soZh7tZ21UEMuQ

http://antifungalcare.email/uMRj8CaHcUvXGveP5lv37eScKas_SA_1vV3EysEjUY6JjVNcwA

were aware that this was effectively a suicide mission, but Junayd's threats forced Sawra to comply. Leaving behind a small garrison, Sawra led 12,000 men out of Samarkand and with the help of a local guide managed to reach within a farsakh (roughly 5–6 km or 3.1–3.7 mi) of Junayd's force by crossing over the mountains. There he was confronted by the Türgesh, who, reportedly on the advice of Ghurak, the Sogdian king of Samarkand, set fire to the dry grasslands. Sawra's lieutenants advised a slow infantry advance fronted by a spear-wall (the standard Umayyad anti-cavalry tactic) but Sawra, knowing his troops to be weary and desperate, decided instead to launch a cavalry charge against the Türgesh in the hopes of breaking through with at least part of his force and reaching Junayd. Sawra's troops, "maddened by heat and thirst" in the description of H.A.R. Gibb, charged the Türgesh and broke their front, but the battle soon became a confused affair with both sides hindered by the smoke, dust, and flames. In the end, the Umayyad army lost its cohesion, scattered, and was destroyed piecemeal by the Türgesh cavalry. All but a thousand of Sawra's force perished, including Sawra himself.

Junayd used the diversion to break th