OwlCyberSecurity - MANAGER
Edit File: 1704968633.M882722P587592.server237.web-hosting.com,S=4952,W=5073
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id KH+DNLnBn2VI9wgA7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 11 Jan 2024 05:23:53 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 11 Jan 2024 05:23:53 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rNsE5-002Xvp-2B for dev@ebaarchitects.org; Thu, 11 Jan 2024 05:23:53 -0500 X-Failed-Recipients: gbrierley@tessituranetwork.com Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <20f7be15c9ad87896ac08922c4f0dacf5b593d@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704968633-eximdsn-1467618472 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rNsE5-002Xvp-2B@server237.web-hosting.com> Date: Thu, 11 Jan 2024 05:23:53 -0500 --1704968633-eximdsn-1467618472 Content-type: text/plain; charset=us-ascii This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: gbrierley@tessituranetwork.com host tessituranetwork-com.mail.protection.outlook.com [104.47.66.10] SMTP error from remote mail server after RCPT TO:<gbrierley@tessituranetwork.com>: 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [MW2NAM12FT063.eop-nam12.prod.protection.outlook.com 2024-01-11T10:23:53.559Z 08DC0781194C62EB] --1704968633-eximdsn-1467618472 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;gbrierley@tessituranetwork.com Status: 5.0.0 Remote-MTA: dns; tessituranetwork-com.mail.protection.outlook.com Diagnostic-Code: smtp; 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [MW2NAM12FT063.eop-nam12.prod.protection.outlook.com 2024-01-11T10:23:53.559Z 08DC0781194C62EB] --1704968633-eximdsn-1467618472 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from [180.129.59.16] (port=51291 helo=62.204.41.121) by server237.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.1) (envelope-from <dev@ebaarchitects.org>) id 1rNsDs-002X2U-1u for gbrierley@tessituranetwork.com; Thu, 11 Jan 2024 05:23:52 -0500 Message-ID: <20f7be15c9ad87896ac08922c4f0dacf5b593d@ebaarchitects.org> Reply-To: robert <robert.m@tildaemail.com> From: robert <dev@ebaarchitects.org> To: gbrierley@tessituranetwork.com Subject: Uneasy about an unknown charge on my card connected to your website - appreciate your insight Date: Thu, 11 Jan 2024 02:21:19 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="2a3079d20e6a404ead074ee503371d082ee64e" --2a3079d20e6a404ead074ee503371d082ee64e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Dear, I am writing to address a bizarre billing that I've noticed on my debit c= ard, which appears to be linked to a transaction on your digital marketpl= ace. This occurrence has caused me distress, especially since I do not recall = ever using services on your platform. I've already begun the investigatio= n process with my financial institution. It would be of great help if you= could provide any details you have about this withdrawal, including spec= ifics like the billing reference. I have gathered considerable proofs, such as digital confirmations, to ba= ck up my claim. Looking forward to your prompt response on this matter. --2a3079d20e6a404ead074ee503371d082ee64e Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"> </head> <body bgColor=3D"#ffffff"><font size=3D2 face=3DArial> <div><br>Dear,</div> <div> </div> <div>I am writing to address a bizarre billing that I've noticed on my de= bit card, which appears to be linked to a transaction on your digital mar= ketplace.</div> <div> </div> <div>This occurrence has caused me distress, especially since I do not re= call ever using services on your platform. I've already begun the investi= gation process with my financial institution. It would be of great help i= f you could provide any details you have about this withdrawal, including= specifics like the billing reference.</div> <div> </div> <div>I have gathered considerable proofs, such as digital confirmations, = to back up my claim.</div> <div> </div> <div>Looking forward to your prompt response on this matter.<br></font></= div> <div align=3Dleft><font size=3D2 face=3DArial></font></div></body></html> --2a3079d20e6a404ead074ee503371d082ee64e-- --1704968633-eximdsn-1467618472--