OwlCyberSecurity - MANAGER

Edit File: 1704995093.M658103P2400133.server237.web-hosting.com,S=5183,W=5310

Envelope-to: dev@ebaarchitects.org
Delivery-date: Thu, 11 Jan 2024 12:44:53 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <80a6ef44f09db7b92a80c96285517b6ea3d9e6@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1704995093-eximdsn-21751714
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rNz6r-00A6CE-1T@server237.web-hosting.com>
Date: Thu, 11 Jan 2024 12:44:53 -0500

--1704995093-eximdsn-21751714
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:

help@jeweljk.com
    host aspmx.l.google.com [142.251.2.27]
    SMTP error from remote mail server after RCPT TO:<help@jeweljk.com>:
    550-5.1.1 The email account that you tried to reach does not exist. Please try
    550-5.1.1 double-checking the recipient's email address for typos or
    550-5.1.1 unnecessary spaces. For more information, go to
    550 5.1.1  https://support.google.com/mail/?p=NoSuchUser cn8-20020a056a020a8800b005cde3cc04c5si1558621pgb.821 - gsmtp

--1704995093-eximdsn-21751714
Content-type: message/delivery-status

Reporting-MTA: dns; server237.web-hosting.com

Action: failed
Final-Recipient: rfc822;help@jeweljk.com
Status: 5.0.0
Remote-MTA: dns; aspmx.l.google.com
Diagnostic-Code: smtp; 550-5.1.1 The email account that you tried to reach does not exist. Please try
 550-5.1.1 double-checking the recipient's email address for typos or
 550-5.1.1 unnecessary spaces. For more information, go to
 550 5.1.1  https://support.google.com/mail/?p=NoSuchUser cn8-20020a056a020a8800b005cde3cc04c5si1558621pgb.821 - gsmtp

--1704995093-eximdsn-21751714
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 217-210-21-226-no2663.tbcn.telia.com ([217.210.21.226]:51552 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 1rNz6b-00A51o-1s
	for help@jeweljk.com;
	Thu, 11 Jan 2024 12:44:52 -0500
Message-ID: <80a6ef44f09db7b92a80c96285517b6ea3d9e6@ebaarchitects.org>
Reply-To: Jeremy D <jeremy.davidson@tildaemail.com>
From: Jeremy D <dev@ebaarchitects.org>
To: help@jeweljk.com
Subject: Uneasy about an enigmatic charge on my account connected to your website - need your guidance
Date: Thu, 11 Jan 2024 09:41:53 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="02bff65de984aea03399d07b9c4862775bb97a"

--02bff65de984aea03399d07b9c4862775bb97a
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Greetings,

I am writing to address a bizarre withdrawal that I've noticed on my cred=
it card, which appears to be linked to a transaction on your digital mark=
etplace.

This occurrence has caused me unease, especially since I do not recall ev=
er shopping on your service. I've already begun the query 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 b=
illing reference.

I have gathered extensive supporting evidence, such as digital confirmati=
ons, to back up my claim.

Looking forward to your rapid response on this matter.

--02bff65de984aea03399d07b9c4862775bb97a
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>&nbsp;</div>
<div>I am writing to address a bizarre withdrawal that I've noticed on my=
 credit card, which appears to be linked to a transaction on your digital=
 marketplace.</div>
<div>&nbsp;</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 query 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 billing reference.</div>
<div>&nbsp;</div>
<div>I have gathered extensive supporting evidence, such as digital confi=
rmations, to back up my claim.</div>
<div>&nbsp;</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>

--02bff65de984aea03399d07b9c4862775bb97a--

--1704995093-eximdsn-21751714--