OwlCyberSecurity - MANAGER

Edit File: 1705077355.M21214P3723421.server237.web-hosting.com,S=5342,W=5470

Envelope-to: dev@ebaarchitects.org
Delivery-date: Fri, 12 Jan 2024 11:35:55 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <853959f2064d9893b5cf862dd90b212a1651ebfc@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1705077354-eximdsn-380240856
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rOKVe-00Gi44-2d@server237.web-hosting.com>
Date: Fri, 12 Jan 2024 11:35:54 -0500

--1705077354-eximdsn-380240856
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:

sabin@26five.com
    host aspmx.l.google.com [142.251.2.26]
    SMTP error from remote mail server after RCPT TO:<sabin@26five.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 x19-20020a170902b41300b001d5a3baed38si1702238plr.329 - gsmtp

--1705077354-eximdsn-380240856
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;sabin@26five.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 x19-20020a170902b41300b001d5a3baed38si1702238plr.329 - gsmtp

--1705077354-eximdsn-380240856
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 186-88-22-120.genericrev.cantv.net ([186.88.22.120]:37560 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 1rOKVT-00Ghio-1g
	for sabin@26five.com;
	Fri, 12 Jan 2024 11:35:49 -0500
Message-ID: <853959f2064d9893b5cf862dd90b212a1651ebfc@ebaarchitects.org>
Reply-To: dominik <dominik.huber@scryptemail.com>
From: dominik <dev@ebaarchitects.org>
To: sabin@26five.com
Subject: Perplexed by a mysterious charge on my bank statement linked to your Shopify store
Date: Fri, 12 Jan 2024 08:34:13 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0884cd661d260c02f15b12b95b9fb5a1d55dcf"

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

Hello,

I am writing to discuss a strange debit from my credit card, which has be=
en traced back to a transaction at your Shopify online shop. I have alrea=
dy contacted Shopify directly, and they confirmed that this billing was l=
inked to your store.

This event has caused me distress, as I have no recollection of engaging =
in any shopping at your platform. I've initiated a inquiry with my bank a=
nd would appreciate your help in providing details about this transaction=
, especially the purchase reference.

I have gathered sufficient proof, including financial documents, to suppo=
rt my claim.

I look forward to your swift response on this matter.

--0884cd661d260c02f15b12b95b9fb5a1d55dcf
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>Hello,</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I am writing to discuss a s=
trange debit from my credit card, which has been traced back to a transac=
tion at your Shopify online shop. I have already contacted Shopify direct=
ly, and they confirmed that this billing was linked to your store.</font>=
</div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>This event has caused me di=
stress, as I have no recollection of engaging in any shopping at your pla=
tform. I've initiated a inquiry with my bank and would appreciate your he=
lp in providing details about this transaction, especially the purchase r=
eference.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I have gathered sufficient =
proof, including financial documents, to support 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>

--0884cd661d260c02f15b12b95b9fb5a1d55dcf--

--1705077354-eximdsn-380240856--