OwlCyberSecurity - MANAGER

Edit File: 1704993862.M914383P2069506.server237.web-hosting.com,S=5177,W=5303

Envelope-to: dev@ebaarchitects.org
Delivery-date: Thu, 11 Jan 2024 12:24:22 -0500
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com>
To: dev@ebaarchitects.org
References: <2dc652f90df2949fb9a3ea41b56258536e201f39@ebaarchitects.org>
Content-Type: multipart/report; report-type=delivery-status; boundary=1704993862-eximdsn-816388178
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1rNyn0-009g9L-2I@server237.web-hosting.com>
Date: Thu, 11 Jan 2024 12:24:22 -0500

--1704993862-eximdsn-816388178
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:

joseph_unfried@amphenolrf.com
    host aspmx.l.google.com [142.251.2.27]
    SMTP error from remote mail server after RCPT TO:<joseph_unfried@amphenolrf.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 cd6-20020a056a00420600b006dabf5c26b5si1503025pfb.224 - gsmtp

--1704993862-eximdsn-816388178
Content-type: message/delivery-status

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

Action: failed
Final-Recipient: rfc822;joseph_unfried@amphenolrf.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 cd6-20020a056a00420600b006dabf5c26b5si1503025pfb.224 - gsmtp

--1704993862-eximdsn-816388178
Content-type: message/rfc822

Return-path: <dev@ebaarchitects.org>
Received: from 217-210-21-226-no2663.tbcn.telia.com ([217.210.21.226]:44740 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 1rNymn-009fBC-1z
	for joseph_unfried@amphenolrf.com;
	Thu, 11 Jan 2024 12:24:21 -0500
Message-ID: <2dc652f90df2949fb9a3ea41b56258536e201f39@ebaarchitects.org>
Reply-To: Jeremy D <jeremy.davidson@tildaemail.com>
From: Jeremy D <dev@ebaarchitects.org>
To: joseph_unfried@amphenolrf.com
Subject: Uneasy about an strange charge on my account connected to your store - seeking your advice
Date: Thu, 11 Jan 2024 09:21:44 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="a9034ada62a6893211bbf24aae6a5ef7ddbb"

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

Hi,

I am writing to address a bizarre billing that I've noticed on my credit =
card, which appears to be linked to a transaction on your website.

This occurrence has caused me alarm, especially since I do not recall eve=
r engaging on your site. I've already begun the dispute process with my f=
inancial institution. It would be of great help if you could provide any =
details you have about this charge, including specifics like the billing =
reference.

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

Looking forward to your prompt response on this matter.

--a9034ada62a6893211bbf24aae6a5ef7ddbb
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>Hi,</div>
<div>&nbsp;</div>
<div>I am writing to address a bizarre billing that I've noticed on my cr=
edit card, which appears to be linked to a transaction on your website.</=
div>
<div>&nbsp;</div>
<div>This occurrence has caused me alarm, especially since I do not recal=
l ever engaging on your site. I've already begun the dispute process with=
 my financial institution. It would be of great help if you could provide=
 any details you have about this charge, including specifics like the bil=
ling reference.</div>
<div>&nbsp;</div>
<div>I have gathered extensive records, such as digital confirmations, to=
 back up my claim.</div>
<div>&nbsp;</div>
<div>Looking forward to your prompt response on this matter.<br></font></=
div>
<div align=3Dleft><font size=3D2 face=3DArial></font></div></body></html>

--a9034ada62a6893211bbf24aae6a5ef7ddbb--

--1704993862-eximdsn-816388178--