OwlCyberSecurity - MANAGER
Edit File: 1726719917.M674724P1546287.premium69.web-hosting.com,S=9860,W=10134
Return-Path: <postmaster@39f87c2b59.nxcli.io> Delivered-To: contact+spam@homeimportance.com Received: from premium69.web-hosting.com by premium69.web-hosting.com with LMTP id mECMJ62n62YvmBcAQpcCZw (envelope-from <postmaster@39f87c2b59.nxcli.io>) for <contact+spam@homeimportance.com>; Thu, 19 Sep 2024 00:25:17 -0400 Return-path: <postmaster@39f87c2b59.nxcli.io> Envelope-to: contact@homeimportance.com Delivery-date: Thu, 19 Sep 2024 00:25:17 -0400 Received: from cloudhost-65065.us-west-1.nxcli.net ([173.249.144.164]:32094) by premium69.web-hosting.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96.2) (envelope-from <postmaster@39f87c2b59.nxcli.io>) id 1sr8j8-0073wo-35 for contact@homeimportance.com; Thu, 19 Sep 2024 00:25:17 -0400 Received: (qmail 7508 invoked by uid 10200); 19 Sep 2024 04:22:37 +0000 Date: Thu, 19 Sep 2024 04:21:31 +0000 To: contact@homeimportance.com From: MetaMask <support@metamask.io> Message-ID: <b76666de22236bd2fa9480d159e3a1ce@metamask.io> List-Unsubscribe: mailto:bounce709-CS4bpyrKnM4D4cE@metamask.io?subject=list-unsubscribe MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="147316bcc1ef2d590c12c7ffe7da27c83" Content-Transfer-Encoding: 8bit X-Spam-Status: Yes, score=11.3 X-Spam-Score: 113 X-Spam-Bar: +++++++++++ X-Spam-Report: Spam detection software, running on the system "premium69.web-hosting.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 root\@localhost for details. Content preview: Action Required: Set Up Two-Factor Authentication (2FA) body { font-family: 'Arial', sans-serif; margin: 0; padding: 0; background-color: #f4f4f4; } .container { max-width: 650px; margin: 40px auto; padding: 30px; background-color: #ffffff; border-radius: [...] Content analysis details: (11.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: metamask.io] 0.0 URIBL_PH_SURBL Contains an URL listed in the PH SURBL blocklist [URIs: xxrsports.com] 1.9 URIBL_ABUSE_SURBL Contains an URL listed in the ABUSE SURBL blocklist [URIs: xxrsports.com] 0.0 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [173.249.144.164 listed in sa-trusted.bondedsender.org] 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different 0.0 RCVD_IN_VALIDITY_RPBL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [173.249.144.164 listed in bl.score.senderscore.com] 0.0 HTML_IMAGE_ONLY_32 BODY: HTML: images with 2800-3200 bytes of words 0.0 HTML_MESSAGE BODY: HTML included in message 1.7 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/) 2.4 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50% [cf: 100] 3.0 KAM_DMARC_REJECT DKIM has Failed or SPF has failed on the message and the domain has a DMARC reject policy 0.9 URG_BIZ Contains urgent matter 0.0 KAM_DMARC_STATUS Test Rule for DKIM or SPF Failure with Strict Alignment 1.0 KAM_LAZY_DOMAIN_SECURITY Sending domain does not have any anti-forgery methods X-Spam-Flag: YES Subject: ***SPAM*** Urgent: Assistance Required for 2FA Access Issue This is a multi-part message in MIME format. --147316bcc1ef2d590c12c7ffe7da27c83 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Action Required: Set Up Two-Factor Authentication (2FA) body { font-family: 'Arial', sans-serif; margin: 0; padding: 0; background-color: #f4f4f4; } .container { max-width: 650px; margin: 40px auto; padding: 30px; background-color: #ffffff; border-radius: 10px; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1); } h1 { font-size: 22px; color: #333; text-align: center; border-bottom: 2px solid #e0e0e0; padding-bottom: 15px; margin-bottom: 30px; } p { font-size: 16px; color: #555; line-height: 1.8; margin-bottom: 20px; } .signature { margin-top: 40px; } .signature p { margin: 5px 0; } footer { text-align: center; font-size: 13px; color: #999; margin-top: 30px; } .logo { text-align: center; margin-bottom: 20px; } .logo img { max-width: 150px; } Action Required: Set Up Two-Factor Authentication (2FA) Dear MetaMask User, To enhance the security of your MetaMask account, we are requiring all users to enable two-factor authentication (2FA). This additional security step helps protect your account from unauthorized access. If you have not yet set up 2FA, please follow the instructions below to complete the process: 1. Visit the 2FA setup page: MetaMask 2FA Setup 2. Follow the on-screen instructions to enable 2FA on your account. Ensure that you complete this setup by [specific deadline, if applicable]. If you need assistance or encounter any issues, please contact our support team for help. Thank you for your prompt attention to this important security update. MetaMask Support Team Email: support@metamask.io Website: https://metamask.io © 2024 MetaMask Support --147316bcc1ef2d590c12c7ffe7da27c83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Action Required: Set Up Two-Factor Authentication (2FA)</title> <style> body { font-family: 'Arial', sans-serif; margin: 0; padding: 0; background-color: #f4f4f4; } .container { max-width: 650px; margin: 40px auto; padding: 30px; background-color: #ffffff; border-radius: 10px; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1); } h1 { font-size: 22px; color: #333; text-align: center; border-bottom: 2px solid #e0e0e0; padding-bottom: 15px; margin-bottom: 30px; } p { font-size: 16px; color: #555; line-height: 1.8; margin-bottom: 20px; } .signature { margin-top: 40px; } .signature p { margin: 5px 0; } footer { text-align: center; font-size: 13px; color: #999; margin-top: 30px; } .logo { text-align: center; margin-bottom: 20px; } .logo img { max-width: 150px; } </style> </head> <body> <div class="container"> <div class="logo"> <img src="https://theme.zdassets.com/theme_assets/2313093/bad730fb4fa8145bf225c509b343cc23f951c2e9.svg" alt="MetaMask Logo"> </div> <h1>Action Required: Set Up Two-Factor Authentication (2FA)</h1> <p>Dear MetaMask User,</p> <p>To enhance the security of your MetaMask account, we are requiring all users to enable two-factor authentication (2FA). This additional security step helps protect your account from unauthorized access.</p> <p>If you have not yet set up 2FA, please follow the instructions below to complete the process:</p> <p>1. Visit the 2FA setup page: <a href="https://xxrsports.com/" target="_blank">MetaMask 2FA Setup</a></p> <p>2. Follow the on-screen instructions to enable 2FA on your account.</p> <p>Ensure that you complete this setup by [specific deadline, if applicable]. If you need assistance or encounter any issues, please contact our support team for help.</p> <p>Thank you for your prompt attention to this important security update.</p> <div class="signature"> <p>MetaMask Support Team</p> <p>Email: support@metamask.io</p> <p>Website: <a href="https://metamask.io">https://metamask.io</a></p> </div> </div> <footer> © 2024 MetaMask Support </footer> </body> </html> --147316bcc1ef2d590c12c7ffe7da27c83--