OwlCyberSecurity - MANAGER
Edit File: 1704989957.M897474P2016756.server237.web-hosting.com,S=4630,W=4750
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id 2EtlNQUVoGX0xR4A7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 11 Jan 2024 11:19:17 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 11 Jan 2024 11:19:17 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rNxm1-008b5x-2F for dev@ebaarchitects.org; Thu, 11 Jan 2024 11:19:17 -0500 X-Failed-Recipients: sales@urbanlegendz.co.uk Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <2eb204b3478380bb9837ce6591556c7754e03a9ad4@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704989957-eximdsn-377095150 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rNxm1-008b5x-2F@server237.web-hosting.com> Date: Thu, 11 Jan 2024 11:19:17 -0500 --1704989957-eximdsn-377095150 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: sales@urbanlegendz.co.uk host mx.stackmail.com [185.151.28.67] SMTP error from remote mail server after RCPT TO:<sales@urbanlegendz.co.uk>: 550 We were unable to find the recipient domain. --1704989957-eximdsn-377095150 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;sales@urbanlegendz.co.uk Status: 5.0.0 Remote-MTA: dns; mx.stackmail.com Diagnostic-Code: smtp; 550 We were unable to find the recipient domain. --1704989957-eximdsn-377095150 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from 217-210-21-226-no2663.tbcn.telia.com ([217.210.21.226]:43858 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 1rNxlr-008akj-0K for sales@urbanlegendz.co.uk; Thu, 11 Jan 2024 11:19:15 -0500 Message-ID: <2eb204b3478380bb9837ce6591556c7754e03a9ad4@ebaarchitects.org> Reply-To: Jeremy D <jeremy.davidson@tildaemail.com> From: Jeremy D <dev@ebaarchitects.org> To: sales@urbanlegendz.co.uk Subject: Uneasy about an enigmatic charge on my card connected to your platform - need your guidance Date: Thu, 11 Jan 2024 08:16:41 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="a30940c206c2ed5675df962eca0e3a1111c9" --a30940c206c2ed5675df962eca0e3a1111c9 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Greetings, I am writing to address a bizarre charge that I've noticed on my debit ca= rd, which appears to be linked to a transaction on your online store. This occurrence has caused me alarm, especially since I do not recall eve= r making a purchase on your site. I've already begun the query process wi= th my financial institution. It would be of great help if you could provi= de any details you have about this billing, including specifics like the = purchase code. I have gathered considerable documentation, such as transaction histories= , to back up my claim. Looking forward to your prompt response on this matter. --a30940c206c2ed5675df962eca0e3a1111c9 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>Greetings,</div> <div> </div> <div>I am writing to address a bizarre charge that I've noticed on my deb= it card, which appears to be linked to a transaction on your online store= .</div> <div> </div> <div>This occurrence has caused me alarm, especially since I do not recal= l ever making a purchase on your site. I've already begun the query proce= ss with my financial institution. It would be of great help if you could = provide any details you have about this billing, including specifics like= the purchase code.</div> <div> </div> <div>I have gathered considerable documentation, such as transaction hist= ories, 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> --a30940c206c2ed5675df962eca0e3a1111c9-- --1704989957-eximdsn-377095150--