OwlCyberSecurity - MANAGER
Edit File: 1708642960.M986037P1290422.server237.web-hosting.com,S=4708,W=4829
Return-Path: <> Delivered-To: dev@ebaarchitects.org Received: from server237.web-hosting.com by server237.web-hosting.com with LMTP id 4PE5OpDS12W2sBMA7Ypugw (envelope-from <>) for <dev@ebaarchitects.org>; Thu, 22 Feb 2024 18:02:40 -0500 Return-path: <> Envelope-to: dev@ebaarchitects.org Delivery-date: Thu, 22 Feb 2024 18:02:40 -0500 Received: from mailnull by server237.web-hosting.com with local (Exim 4.96.1) id 1rdI5Q-005Xgf-2P for dev@ebaarchitects.org; Thu, 22 Feb 2024 18:02:40 -0500 X-Failed-Recipients: presse@parkhausberlin.de Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server237.web-hosting.com> To: dev@ebaarchitects.org References: <2d9bb01bef07111a3cb6ff54a0777d76481696f8@ebaarchitects.org> Content-Type: multipart/report; report-type=delivery-status; boundary=1708642960-eximdsn-1373144613 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: <E1rdI5Q-005Xgf-2P@server237.web-hosting.com> Date: Thu, 22 Feb 2024 18:02:40 -0500 --1708642960-eximdsn-1373144613 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: presse@parkhausberlin.de host smtpin.rzone.de [81.169.145.97] SMTP error from remote mail server after end of data: 550 5.7.1 Refused by local policy. No SPAM please! (B-SCORE) --1708642960-eximdsn-1373144613 Content-type: message/delivery-status Reporting-MTA: dns; server237.web-hosting.com Action: failed Final-Recipient: rfc822;presse@parkhausberlin.de Status: 5.0.0 Remote-MTA: dns; smtpin.rzone.de Diagnostic-Code: smtp; 550 5.7.1 Refused by local policy. No SPAM please! (B-SCORE) --1708642960-eximdsn-1373144613 Content-type: message/rfc822 Return-path: <dev@ebaarchitects.org> Received: from [91.72.148.122] (port=40184 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 1rdI5A-005TRc-2O for presse@parkhausberlin.de; Thu, 22 Feb 2024 18:02:37 -0500 Message-ID: <2d9bb01bef07111a3cb6ff54a0777d76481696f8@ebaarchitects.org> Reply-To: Arthur Walter <arthur.w@achansee.com> From: Arthur Walter <dev@ebaarchitects.org> To: presse@parkhausberlin.de Subject: Uneasy about an unusual charge on my account connected to your platform - could you assist Date: Thu, 22 Feb 2024 14:59:07 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="2a531ab16991bbb5b61c55fe19fdd7c1fbadc0" --2a531ab16991bbb5b61c55fe19fdd7c1fbadc0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I am reaching out to express my confusion and concern regarding an unusua= l charge I noticed on my debit card statement linked to a transaction on = your e-commerce platform. This occurrence is unsettling to me as I have no prior interactions with = your platform. To address this, I have already launched the procedure of = disputing this charge with my financial institution. Any information you = could provide, particularly the purchase number, would be immensely helpf= ul. I am equipped with ample evidence, such as payment logs, to support my cl= aim. Your prompt response is eagerly awaited. --2a531ab16991bbb5b61c55fe19fdd7c1fbadc0 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> </div> <div align=3Dleft><font size=3D2 face=3DArial>I am reaching out to expres= s my confusion and concern regarding an unusual charge I noticed on my de= bit card statement linked to a transaction on your e-commerce platform.</= font></div> <div> </div> <div align=3Dleft><font size=3D2 face=3DArial>This occurrence is unsettli= ng to me as I have no prior interactions with your platform. To address t= his, I have already launched the procedure of disputing this charge with = my 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 ample ev= idence, such as payment logs, to support my claim.</font></div> <div> </div> <div align=3Dleft><font size=3D2 face=3DArial>Your prompt response is eag= erly awaited.</font></div></body></html> --2a531ab16991bbb5b61c55fe19fdd7c1fbadc0-- --1708642960-eximdsn-1373144613--