OwlCyberSecurity - MANAGER
Edit File: 1704400113.M480356P3751712.server237.web-hosting.com,S=4707,W=4827
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id sASEHPEUl2UgPzkA7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 04 Jan 2024 15:28:33 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 04 Jan 2024 15:28:33 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rLUKP-00Fpih-0t for dev@ebaarchitects.org; Thu, 04 Jan 2024 15:28:33 -0500 X-Failed-Recipients: cheri.torres@dish.com Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <248cf7d024e0c100238c953eca0e30dbf84c3f0020@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704400113-eximdsn-1688965636 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rLUKP-00Fpih-0t@server237.web-hosting.com> Date: Thu, 04 Jan 2024 15:28:33 -0500 --1704400113-eximdsn-1688965636 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: cheri.torres@dish.com host us-smtp-inbound-2.mimecast.com [205.139.110.242] SMTP error from remote mail server after RCPT TO:<cheri.torres@dish.com>: 550 Invalid Recipient - https://community.mimecast.com/docs/DOC-1369#550 [t2f8bnz3OlSBxoL-MwBsXQ.us680] --1704400113-eximdsn-1688965636 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;cheri.torres@dish.com Status: 5.0.0 Remote-MTA: dns; us-smtp-inbound-2.mimecast.com Diagnostic-Code: smtp; 550 Invalid Recipient - https://community.mimecast.com/docs/DOC-1369#550 [t2f8bnz3OlSBxoL-MwBsXQ.us680] --1704400113-eximdsn-1688965636 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from [84.15.212.88] (port=55344 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 1rLU2t-00FZUM-11 for cheri.torres@dish.com; Thu, 04 Jan 2024 15:10:34 -0500 Message-ID: <248cf7d024e0c100238c953eca0e30dbf84c3f0020@ebaarchitects.org> Reply-To: michael <michael.thornton@primank.com> From: michael <dev@ebaarchitects.org> To: cheri.torres@dish.com Subject: Uneasy about an strange charge on my bank statement connected to your website - could you assist Date: Thu, 4 Jan 2024 12:07:59 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="03a9e0407eba95ceed470eb1a561555154be" --03a9e0407eba95ceed470eb1a561555154be Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I am writing to address a bizarre charge that I've noticed on my credit c= ard, which appears to be linked to a transaction on your website. This occurrence has caused me unease, especially since I do not recall ev= er shopping on your service. I've already begun the investigation process= with my financial institution. It would be of great help if you could pr= ovide any details you have about this transaction, including specifics li= ke the billing reference. I have gathered extensive documentation, such as credit card logs, to bac= k up my claim. Looking forward to your speedy response on this matter. --03a9e0407eba95ceed470eb1a561555154be 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>Hi,</div> <div> </div> <div>I am writing to address a bizarre charge that I've noticed on my cre= dit card, which appears to be linked to a transaction on your website.</d= iv> <div> </div> <div>This occurrence has caused me unease, especially since I do not reca= ll ever shopping on your service. I've already begun the investigation pr= ocess with my financial institution. It would be of great help if you cou= ld provide any details you have about this transaction, including specifi= cs like the billing reference.</div> <div> </div> <div>I have gathered extensive documentation, such as credit card logs, t= o back up my claim.</div> <div> </div> <div>Looking forward to your speedy response on this matter.<br></font></= div> <div align=3Dleft><font size=3D2 face=3DArial></font></div></body></html> --03a9e0407eba95ceed470eb1a561555154be-- --1704400113-eximdsn-1688965636--