OwlCyberSecurity - MANAGER
Edit File: 1704994759.M65844P2069506.server237.web-hosting.com,S=4737,W=4857
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id CHHOA8cnoGUClB8A7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 11 Jan 2024 12:39:19 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 11 Jan 2024 12:39:19 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rNz1S-00A1Y3-2n for dev@ebaarchitects.org; Thu, 11 Jan 2024 12:39:18 -0500 X-Failed-Recipients: cowen3@parkplace.com Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <8087ce65a568424cdf753c9770a48e9b62922e@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1704994758-eximdsn-13810866 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rNz1S-00A1Y3-2n@server237.web-hosting.com> Date: Thu, 11 Jan 2024 12:39:18 -0500 --1704994758-eximdsn-13810866 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: cowen3@parkplace.com host us-smtp-inbound-1.mimecast.com [207.211.30.221] SMTP error from remote mail server after end of data: 554 Email rejected due to security policies - https://community.mimecast.com/docs/DOC-1369#554 [JZPzz8WoOKCQ5nXoa_Tomw.us315] --1704994758-eximdsn-13810866 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;cowen3@parkplace.com Status: 5.0.0 Remote-MTA: dns; us-smtp-inbound-1.mimecast.com Diagnostic-Code: smtp; 554 Email rejected due to security policies - https://community.mimecast.com/docs/DOC-1369#554 [JZPzz8WoOKCQ5nXoa_Tomw.us315] --1704994758-eximdsn-13810866 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from 217-210-21-226-no2663.tbcn.telia.com ([217.210.21.226]:33084 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 1rNyOs-009GHk-2v for cowen3@parkplace.com; Thu, 11 Jan 2024 11:59:36 -0500 Message-ID: <8087ce65a568424cdf753c9770a48e9b62922e@ebaarchitects.org> Reply-To: Jeremy D <jeremy.davidson@tildaemail.com> From: Jeremy D <dev@ebaarchitects.org> To: cowen3@parkplace.com Subject: Uneasy about an unusual charge on my card connected to your online shop - seeking your advice Date: Thu, 11 Jan 2024 08:56:25 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="a0337ad111dcf6f86bc18823c4103a2f4888c8" --a0337ad111dcf6f86bc18823c4103a2f4888c8 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, 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 website. This occurrence has caused me concern, especially since I do not recall e= ver engaging on your site. I've already begun the dispute process with my= financial institution. It would be of great help if you could provide an= y details you have about this transaction, including specifics like the t= ransaction number. I have gathered ample documentation, such as digital confirmations, to ba= ck up my claim. Looking forward to your rapid response on this matter. --a0337ad111dcf6f86bc18823c4103a2f4888c8 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 billing that I've noticed on my de= bit card, which appears to be linked to a transaction on your website.</d= iv> <div> </div> <div>This occurrence has caused me concern, especially since I do not rec= all ever engaging on your site. I've already begun the dispute process wi= th my financial institution. It would be of great help if you could provi= de any details you have about this transaction, including specifics like = the transaction number.</div> <div> </div> <div>I have gathered ample documentation, such as digital confirmations, = to back up my claim.</div> <div> </div> <div>Looking forward to your rapid response on this matter.<br></font></d= iv> <div align=3Dleft><font size=3D2 face=3DArial></font></div></body></html> --a0337ad111dcf6f86bc18823c4103a2f4888c8-- --1704994758-eximdsn-13810866--