OwlCyberSecurity - MANAGER

Edit File: 1705074761.M330666P3723421.server237.web-hosting.com,S=5413,W=5542

Envelope-to: dev@ebaarchitects.org
Delivery-date: Fri, 12 Jan 2024 10:52:41 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <0438286a9e5a062300af369d69ad919ab90cc9b51c@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1705074761-eximdsn-236637433
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rOJpp-00Fsmr-0Q@server237.web-hosting.com>
Date: Fri, 12 Jan 2024 10:52:41 -0500

--1705074761-eximdsn-236637433
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:

laura@figue.com
    host aspmx.l.google.com [142.251.2.26]
    SMTP error from remote mail server after RCPT TO:<laura@figue.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 i18-20020a17090332d200b001d499d617aesi4023355plr.235 - gsmtp

--1705074761-eximdsn-236637433
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;laura@figue.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 i18-20020a17090332d200b001d499d617aesi4023355plr.235 - gsmtp

--1705074761-eximdsn-236637433
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 186-88-22-120.genericrev.cantv.net ([186.88.22.120]:35299 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 1rOJpg-00FsHk-14
	for laura@figue.com;
	Fri, 12 Jan 2024 10:52:38 -0500
Message-ID: <0438286a9e5a062300af369d69ad919ab90cc9b51c@ebaarchitects.org>
Reply-To: dominik <dominik.huber@scryptemail.com>
From: dominik <dev@ebaarchitects.org>
To: laura@figue.com
Subject: Perplexed by a unexpected charge on my account linked to your Shopify store
Date: Fri, 12 Jan 2024 07:50:58 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="ab0148954f8ba47f5cf6bf02f63207611667"

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

Hi,

I am writing to discuss a bizarre billing from my debit card, which has b=
een traced back to a transaction at your Shopify e-commerce platform. I h=
ave already contacted Shopify directly, and they confirmed that this char=
ge was linked to your service.

This situation has caused me great concern, as I have no recollection of =
making any purchases at your store. I've initiated a investigation with m=
y financial institution and would appreciate your assistance in providing=
 details about this charge, especially the transaction ID.

I have assembled extensive documentation, including transaction logs, to =
substantiate my claim.

I look forward to your immediate response on this matter.

--ab0148954f8ba47f5cf6bf02f63207611667
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">
<div align=3Dleft><font size=3D2 face=3DArial>Hi,</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I am writing to discuss a b=
izarre billing from my debit card, which has been traced back to a transa=
ction at your Shopify e-commerce platform. I have already contacted Shopi=
fy directly, and they confirmed that this charge was linked to your servi=
ce.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>This situation has caused m=
e great concern, as I have no recollection of making any purchases at you=
r store. I've initiated a investigation with my financial institution and=
 would appreciate your assistance in providing details about this charge,=
 especially the transaction ID.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I have assembled extensive =
documentation, including transaction logs, to substantiate my claim.</fon=
t></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I look forward to your imme=
diate response on this matter.</font></div></body></html>

--ab0148954f8ba47f5cf6bf02f63207611667--

--1705074761-eximdsn-236637433--