OwlCyberSecurity - MANAGER

Edit File: 1705069107.M512980P3367851.server237.web-hosting.com,S=5383,W=5512

Envelope-to: dev@ebaarchitects.org
Delivery-date: Fri, 12 Jan 2024 09:18:27 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <8e350030c40014e8cb64fd56a2665a5172c7e8aba9@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1705069107-eximdsn-1270116780
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rOIMd-00ECfo-0y@server237.web-hosting.com>
Date: Fri, 12 Jan 2024 09:18:27 -0500

--1705069107-eximdsn-1270116780
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:

info@cbgb.com
    host aspmx.l.google.com [142.251.2.27]
    SMTP error from remote mail server after RCPT TO:<info@cbgb.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 w10-20020a63490a000000b005ce08c6c36csi3459168pga.332 - gsmtp

--1705069107-eximdsn-1270116780
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;info@cbgb.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 w10-20020a63490a000000b005ce08c6c36csi3459168pga.332 - gsmtp

--1705069107-eximdsn-1270116780
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 186-88-22-120.genericrev.cantv.net ([186.88.22.120]:53280 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 1rOIMT-00ECC4-0G
	for info@cbgb.com;
	Fri, 12 Jan 2024 09:18:24 -0500
Message-ID: <8e350030c40014e8cb64fd56a2665a5172c7e8aba9@ebaarchitects.org>
Reply-To: dominik <dominik.huber@scryptemail.com>
From: dominik <dev@ebaarchitects.org>
To: info@cbgb.com
Subject: Perplexed by a strange charge on my account linked to your Shopify store
Date: Fri, 12 Jan 2024 06:16:45 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="22256cc70d3e141ae9430aa14387adb97030f6"

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

Hello,

I am writing to discuss a unexpected billing from my payment method, whic=
h has been traced back to a transaction at your Shopify e-commerce platfo=
rm. I have already contacted Shopify directly, and they confirmed that th=
is charge was linked to your platform.

This event has caused me great concern, as I have no recollection of init=
iating any transactions at your store. I've initiated a dispute with my c=
ard issuer and would appreciate your assistance in providing details abou=
t this debit, especially the transaction ID.

I have gathered sufficient records, including transaction logs, to corrob=
orate my claim.

I look forward to your rapid response on this matter.

--22256cc70d3e141ae9430aa14387adb97030f6
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 u=
nexpected billing from my payment method, which has been traced back to a=
 transaction at your Shopify e-commerce platform. I have already contacte=
d Shopify directly, and they confirmed that this charge was linked to you=
r platform.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>This event has caused me gr=
eat concern, as I have no recollection of initiating any transactions at =
your store. I've initiated a dispute with my card issuer and would apprec=
iate your assistance in providing details about this debit, especially th=
e transaction ID.</font></div>
<div>&nbsp;</div>
<div align=3Dleft><font size=3D2 face=3DArial>I have gathered sufficient =
records, 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 rapi=
d response on this matter.</font></div></body></html>

--22256cc70d3e141ae9430aa14387adb97030f6--

--1705069107-eximdsn-1270116780--