From: "chapelhill.xyz" <[email protected]>
To: [email protected]
Subject: I need your help
Date: Sun, 8 Sep 2024 06:52:22 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
[-- Attachment #1: Type: text/plain, Size: 3043 bytes --]
Spam detection software, running on the system "server-vie001.gnuweeb.org",
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
@@CONTACT_ADDRESS@@ for details.
Content preview: Greeting, I have access to very vital information that can
be used to move huge amounts of money. If it was possible for me to do it
alone I would not have bothered contacting you. Ultimately I need you to
play an important role in the completion of this business transaction.
Content analysis details: (7.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.9 URIBL_ABUSE_SURBL Contains an URL listed in the ABUSE SURBL
blocklist
[URIs: chapelhill.xyz]
3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS
[51.178.18.124 listed in zen.spamhaus.org]
0.1 URIBL_CSS_A Contains URL's A record listed in the Spamhaus CSS
blocklist
[URIs: chapelhill.xyz]
0.1 URIBL_CSS Contains an URL's NS IP listed in the Spamhaus CSS
blocklist
[URIs: chapelhill.xyz]
2.5 URIBL_DBL_SPAM Contains a spam URL listed in the Spamhaus DBL
blocklist
[URIs: chapelhill.xyz]
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 PDS_OTHER_BAD_TLD Untrustworthy TLDs
[URI: chapelhill.xyz (xyz)]
0.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
valid
-3.0 RCVD_IN_VALIDITY_CERTIFIED RBL: Sender in Validity Certification
- Contact [email protected]
[Excessive Number of Queries | <https://knowledge.validity.com/hc/en-us/articles/20961730681243>]
-2.0 RCVD_IN_VALIDITY_SAFE RBL: Sender in Validity Safe - Contact
[email protected]
1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL,
https://senderscore.org/blocklistlookup/
[51.178.18.124 listed in bl.score.senderscore.com]
1.0 FROM_SUSPICIOUS_NTLD_FP From abused NTLD
1.0 FROM_SUSPICIOUS_NTLD From abused NTLD
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.
[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 2516 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 322 bytes --]
Greeting,
I have access to very vital information that can be used to
move huge amounts of money.
If it was possible for me to do it alone I would not
have bothered contacting you. Ultimately I need you to play an
important role in the completion of this business transaction.
Regards,
Mr Alexander Bulyanda
[-- Attachment #2.1.2: Type: text/html, Size: 582 bytes --]
reply other threads:[~2024-09-08 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0ade973cfd230905693c8a21c1f5dfd7c4671b@chapelhill.xyz \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox