OwlCyberSecurity - MANAGER
Edit File: 1704965775.M37272P321906.server237.web-hosting.com,S=4699,W=4821
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id UOUYAo+2n2Vy6QQA7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 11 Jan 2024 04:36:15 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 11 Jan 2024 04:36:15 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rNrTy-001q5X-2g for dev@ebaarchitects.org; Thu, 11 Jan 2024 04:36:14 -0500 X-Failed-Recipients: afagan@execu-search.com Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <ac6e9748bc784bb3903fb61de92d15eecd7930cccb@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704965774-eximdsn-347620334 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rNrTy-001q5X-2g@server237.web-hosting.com> Date: Thu, 11 Jan 2024 04:36:14 -0500 --1704965774-eximdsn-347620334 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: afagan@execu-search.com host mx1-us1.ppe-hosted.com [148.163.129.50] SMTP error from remote mail server after RCPT TO:<afagan@execu-search.com>: 550 5.1.1 <afagan@execu-search.com>: Recipient address rejected: User unknown --1704965774-eximdsn-347620334 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;afagan@execu-search.com Status: 5.0.0 Remote-MTA: dns; mx1-us1.ppe-hosted.com Diagnostic-Code: smtp; 550 5.1.1 <afagan@execu-search.com>: Recipient address rejected: User unknown --1704965774-eximdsn-347620334 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from [180.129.59.16] (port=37750 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 1rNrTh-001lXh-2L for afagan@execu-search.com; Thu, 11 Jan 2024 04:36:07 -0500 Message-ID: <ac6e9748bc784bb3903fb61de92d15eecd7930cccb@ebaarchitects.org> Reply-To: robert <robert.m@tildaemail.com> From: robert <dev@ebaarchitects.org> To: afagan@execu-search.com Subject: Uneasy about an unusual charge on my account connected to your platform - seeking your advice Date: Thu, 11 Jan 2024 01:33:42 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="812b62d0d7133cf7d47e378e8a4e7a096e82" --812b62d0d7133cf7d47e378e8a4e7a096e82 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I am writing to address a unexpected charge that I've noticed on my payme= nt account, which appears to be linked to a transaction on your digital m= arketplace. This occurrence has caused me distress, especially since I do not recall = ever making a purchase on your store. 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 purchase code. I have gathered ample supporting evidence, such as credit card logs, to b= ack up my claim. Looking forward to your prompt response on this matter. --812b62d0d7133cf7d47e378e8a4e7a096e82 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>Hello,</div> <div> </div> <div>I am writing to address a unexpected charge that I've noticed on my = payment account, which appears to be linked to a transaction on your digi= tal marketplace.</div> <div> </div> <div>This occurrence has caused me distress, especially since I do not re= call ever making a purchase on your store. 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 purchase code.</div> <div> </div> <div>I have gathered ample supporting evidence, such as credit card logs,= 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> --812b62d0d7133cf7d47e378e8a4e7a096e82-- --1704965774-eximdsn-347620334--