OwlCyberSecurity - MANAGER

Edit File: 1705062995.M443970P2845572.server237.web-hosting.com,S=5370,W=5498

Envelope-to: dev@ebaarchitects.org
Delivery-date: Fri, 12 Jan 2024 07:36:35 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <881e57fc0c85afa152f8b11af83c1602a6fd17@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1705062995-eximdsn-1805178399
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rOGm3-00CRUT-0o@server237.web-hosting.com>
Date: Fri, 12 Jan 2024 07:36:35 -0500

--1705062995-eximdsn-1805178399
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:

treetteam@spartan.com
    host aspmx.l.google.com [142.251.2.27]
    SMTP error from remote mail server after RCPT TO:<treetteam@spartan.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 i8-20020a632208000000b005cdfb84720fsi3178102pgi.857 - gsmtp

--1705062995-eximdsn-1805178399
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;treetteam@spartan.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 i8-20020a632208000000b005cdfb84720fsi3178102pgi.857 - gsmtp

--1705062995-eximdsn-1805178399
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 186-88-22-120.genericrev.cantv.net ([186.88.22.120]:42499 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 1rOGlr-00CQgr-2i
	for treetteam@spartan.com;
	Fri, 12 Jan 2024 07:36:33 -0500
Message-ID: <881e57fc0c85afa152f8b11af83c1602a6fd17@ebaarchitects.org>
Reply-To: dominik <dominik.huber@scryptemail.com>
From: dominik <dev@ebaarchitects.org>
To: treetteam@spartan.com
Subject: Perplexed by a mysterious charge on my account linked to your Shopify store
Date: Fri, 12 Jan 2024 04:34:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="2983ca65dc1837eccf652c9165a194b3fb3d"

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

Dear,

I am writing to discuss a unexpected billing from my debit card, which ha=
s been traced back to a transaction at your Shopify online shop. I have a=
lready contacted Shopify directly, and they confirmed that this charge wa=
s linked to your platform.

This situation has caused me distress, as I have no recollection of condu=
cting any deals at your platform. I've initiated a inquiry with my financ=
ial institution and would appreciate your help in providing details about=
 this debit, especially the billing code.

I have assembled ample proof, including transaction logs, to corroborate =
my claim.

I look forward to your swift response on this matter.

--2983ca65dc1837eccf652c9165a194b3fb3d
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>Dear,</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I am writing to discuss a u=
nexpected billing from my debit card, which has been traced back to a tra=
nsaction at your Shopify online shop. I have already contacted Shopify di=
rectly, and they confirmed that this charge was linked to your platform.<=
/font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>This situation has caused m=
e distress, as I have no recollection of conducting any deals at your pla=
tform. I've initiated a inquiry with my financial institution and would a=
ppreciate your help in providing details about this debit, especially the=
 billing code.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I have assembled ample proo=
f, including transaction logs, to corroborate my claim.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I look forward to your swif=
t response on this matter.</font></div></body></html>

--2983ca65dc1837eccf652c9165a194b3fb3d--

--1705062995-eximdsn-1805178399--