OwlCyberSecurity - MANAGER
Edit File: 1704973588.M363984P933003.server237.web-hosting.com,S=4589,W=4710
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id 6OSVFRTVn2WLPA4A7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 11 Jan 2024 06:46:28 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 11 Jan 2024 06:46:28 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rNtW0-00405p-0X for dev@ebaarchitects.org; Thu, 11 Jan 2024 06:46:28 -0500 X-Failed-Recipients: sales@big4cycle.com Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <af8ffd56a2594b40660c45ee1acc161d209db371@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704973588-eximdsn-1435759223 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rNtW0-00405p-0X@server237.web-hosting.com> Date: Thu, 11 Jan 2024 06:46:28 -0500 --1704973588-eximdsn-1435759223 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@big4cycle.com host mail.bluetie.com [71.19.237.153] SMTP error from remote mail server after RCPT TO:<sales@big4cycle.com>: 550 5.1.1 Mail Refused - Address <sales@big4cycle.com> Recipient Unknown --1704973588-eximdsn-1435759223 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;sales@big4cycle.com Status: 5.0.0 Remote-MTA: dns; mail.bluetie.com Diagnostic-Code: smtp; 550 5.1.1 Mail Refused - Address <sales@big4cycle.com> Recipient Unknown --1704973588-eximdsn-1435759223 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from [180.129.59.16] (port=39913 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 1rNtVg-003yT3-19 for sales@big4cycle.com; Thu, 11 Jan 2024 06:46:21 -0500 Message-ID: <af8ffd56a2594b40660c45ee1acc161d209db371@ebaarchitects.org> Reply-To: robert <robert.m@tildaemail.com> From: robert <dev@ebaarchitects.org> To: sales@big4cycle.com Subject: Uneasy about an enigmatic charge on my account connected to your store - need your guidance Date: Thu, 11 Jan 2024 03:43:02 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="a9034ade12d6f93211bbf24b4f8bbf89d7fd" --a9034ade12d6f93211bbf24b4f8bbf89d7fd Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I am writing to address a strange debit that I've noticed on my bank acco= unt, which appears to be linked to a transaction on your digital marketpl= ace. This occurrence has caused me unease, especially since I do not recall ev= er engaging on your store. I've already begun the investigation process w= ith my financial institution. It would be of great help if you could prov= ide any details you have about this billing, including specifics like the= purchase code. I have gathered ample records, such as transaction histories, to back up = my claim. Looking forward to your quick response on this matter. --a9034ade12d6f93211bbf24b4f8bbf89d7fd 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 strange debit that I've noticed on my bank= account, which appears to be linked to a transaction on your digital mar= ketplace.</div> <div> </div> <div>This occurrence has caused me unease, especially since I do not reca= ll ever engaging on your store. I've already begun the investigation proc= ess with my financial institution. It would be of great help if you could= provide any details you have about this billing, including specifics lik= e the purchase code.</div> <div> </div> <div>I have gathered ample records, such as transaction histories, to bac= k up my claim.</div> <div> </div> <div>Looking forward to your quick response on this matter.<br></font></d= iv> <div align=3Dleft><font size=3D2 face=3DArial></font></div></body></html> --a9034ade12d6f93211bbf24b4f8bbf89d7fd-- --1704973588-eximdsn-1435759223--