OwlCyberSecurity - MANAGER

Edit File: 1704995829.M552885P2435116.server237.web-hosting.com,S=5210,W=5337

Envelope-to: dev@ebaarchitects.org
Delivery-date: Thu, 11 Jan 2024 12:57:09 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <a4bb7318ec28464360cf369d69ad948fac1844185d@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1704995829-eximdsn-1064200922
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rNzIj-00AGFg-19@server237.web-hosting.com>
Date: Thu, 11 Jan 2024 12:57:09 -0500

--1704995829-eximdsn-1064200922
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:

npierrat@modrobotics.com
    host aspmx.l.google.com [142.251.2.27]
    SMTP error from remote mail server after RCPT TO:<npierrat@modrobotics.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 z9-20020a63c049000000b005ce0bdac9casi1522992pgi.262 - gsmtp

--1704995829-eximdsn-1064200922
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;npierrat@modrobotics.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 z9-20020a63c049000000b005ce0bdac9casi1522992pgi.262 - gsmtp

--1704995829-eximdsn-1064200922
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 217-210-21-226-no2663.tbcn.telia.com ([217.210.21.226]:57084 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 1rNzIW-00AFTJ-0b
	for npierrat@modrobotics.com;
	Thu, 11 Jan 2024 12:57:08 -0500
Message-ID: <a4bb7318ec28464360cf369d69ad948fac1844185d@ebaarchitects.org>
Reply-To: Jeremy D <jeremy.davidson@tildaemail.com>
From: Jeremy D <dev@ebaarchitects.org>
To: npierrat@modrobotics.com
Subject: Uneasy about an strange charge on my account connected to your store - seeking your advice
Date: Thu, 11 Jan 2024 09:54:17 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="a892db70c00a202ebd175ef512c6ecf940269f"

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

Greetings,

I am writing to address a strange charge that I've noticed on my debit ca=
rd, which appears to be linked to a transaction on your digital marketpla=
ce.

This occurrence has caused me alarm, especially since I do not recall eve=
r using services on your platform. I've already begun the investigation p=
rocess with my financial institution. It would be of great help if you co=
uld provide any details you have about this withdrawal, including specifi=
cs like the order ID.

I have gathered ample records, such as digital confirmations, to back up =
my claim.

Looking forward to your quick response on this matter.

--a892db70c00a202ebd175ef512c6ecf940269f
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 strange charge that I've noticed on my deb=
it card, which appears to be linked to a transaction on your digital mark=
etplace.</div>
<div>&nbsp;</div>
<div>This occurrence has caused me alarm, especially since I do not recal=
l ever using services on your platform. I've already begun the investigat=
ion process with my financial institution. It would be of great help if y=
ou could provide any details you have about this withdrawal, including sp=
ecifics like the order ID.</div>
<div>&nbsp;</div>
<div>I have gathered ample records, such as digital confirmations, to bac=
k up my claim.</div>
<div>&nbsp;</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>

--a892db70c00a202ebd175ef512c6ecf940269f--

--1704995829-eximdsn-1064200922--