OwlCyberSecurity - MANAGER
Edit File: 1708644715.M633390P1331129.server237.web-hosting.com,S=4724,W=4845
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id wKSiJWvZ12W5TxQA7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 22 Feb 2024 18:31:55 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 22 Feb 2024 18:31:55 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rdIXj-0064pe-1L for dev@ebaarchitects.org; Thu, 22 Feb 2024 18:31:55 -0500 X-Failed-Recipients: info@kaufen-ver-kaufen.de Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <22c68f24fe6f454b48e2ab00e703293fb01c37@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1708644715-eximdsn-1220717394 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rdIXj-0064pe-1L@server237.web-hosting.com> Date: Thu, 22 Feb 2024 18:31:55 -0500 --1708644715-eximdsn-1220717394 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@kaufen-ver-kaufen.de host mx01.ionos.de [217.72.192.67] SMTP error from remote mail server after RCPT TO:<info@kaufen-ver-kaufen.de>: 550 Requested action not taken: mailbox unavailable --1708644715-eximdsn-1220717394 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;info@kaufen-ver-kaufen.de Status: 5.0.0 Remote-MTA: dns; mx01.ionos.de Diagnostic-Code: smtp; 550 Requested action not taken: mailbox unavailable --1708644715-eximdsn-1220717394 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from 61-220-20-106.hinet-ip.hinet.net ([61.220.20.106]:37027 helo=62.204.41.113) 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 1rdIXM-0063tN-2d for info@kaufen-ver-kaufen.de; Thu, 22 Feb 2024 18:31:52 -0500 Message-ID: <22c68f24fe6f454b48e2ab00e703293fb01c37@ebaarchitects.org> Reply-To: Arthur Walter <arthur.w@achansee.com> From: Arthur Walter <dev@ebaarchitects.org> To: info@kaufen-ver-kaufen.de Subject: Uneasy about an unusual charge on my card connected to your platform - need your guidance Date: Thu, 22 Feb 2024 15:28:48 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="08632a815bcae0eeed470ea542a68c9a825b02" --08632a815bcae0eeed470ea542a68c9a825b02 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I am reaching out to express my confusion and concern regarding an strang= e debit I noticed on my e-wallet linked to a transaction on your online m= arketplace. This occurrence is disturbing to me as I have no prior engagements with y= our platform. To address this, I have already initiated the process of di= sputing this billing with my financial institution. Any information you c= ould provide, particularly the purchase number, would be immensely helpfu= l. I am equipped with sufficient proofs, such as transaction histories, to s= upport my claim. Your quick response is eagerly awaited. --08632a815bcae0eeed470ea542a68c9a825b02 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> </div> <div align=3Dleft><font size=3D2 face=3DArial>I am reaching out to expres= s my confusion and concern regarding an strange debit I noticed on my e-w= allet linked to a transaction on your online marketplace.</font></div> <div> </div> <div align=3Dleft><font size=3D2 face=3DArial>This occurrence is disturbi= ng to me as I have no prior engagements with your platform. To address th= is, I have already initiated the process of disputing this billing with m= y financial institution. Any information you could provide, particularly = the purchase number, would be immensely helpful.</font></div> <div> </div> <div align=3Dleft><font size=3D2 face=3DArial>I am equipped with sufficie= nt proofs, such as transaction histories, to support my claim.</font></di= v> <div> </div> <div align=3Dleft><font size=3D2 face=3DArial>Your quick response is eage= rly awaited.</font></div></body></html> --08632a815bcae0eeed470ea542a68c9a825b02-- --1708644715-eximdsn-1220717394--