topic Re: Incoming email is bounced - Reopened in Email

Incoming email is reported bounced

inkyfingers — Tue, 22 Nov 2022 21:46:58 GMT

I have been sent a report from the owners of @e.email that mail to me at my plusnet email address is being returned to them but I am not being notified.

I also have an email address with them (myself@e.email) email from this address gets though to my plusnet email address fine.

A machine sent "reset password link" never arrives. Machine sent notifications never arrive.

I do not seem to see the way to open a support ticket -- perhaps I'm looking in the wrong place ?

TIA for any help.

Re: Incoming email is reported bounced

inkyfingers — Sat, 26 Nov 2022 11:29:08 GMT

I have been in touch with the other email service provider and given them a secondary email address.

Meanwhile it looks as if Plusnet has allowed 5 machine sent emails through since the day after my original post.

Incoming email is bounced - Reopened

inkyfingers — Sat, 08 Apr 2023 07:35:42 GMT

Really this should be dealt with by means of a Support ticket, but I do not seem to see the way to open a such ticket.

When I try to send email from my mobile to my email address @plusnet the email is being bounced by Plusnet without informing me.

This is an example bounced email

Return-Path: <xx_myself@e.email> Received: from authenticated-user (mail3.ecloud.global [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail3.ecloud.global (Postfix) with ESMTPSA id 9B0F7883182 for <xx_myself@xx_myusername.plus.com>; Thu, 6 Apr 2023 00:57:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=e.email; s=mail3; t=1680742663; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RBYoYMhjYNSSWrjRCb42M9ys0qNUZRKlT5IkT+LWCyU=; b=2XgJWMKlR8/T/4PZmEeixB6VJuFSDcUSkyy88Uh0RMj81rIBBfaA0r9Ne8xn8A8emiruzG CHFHwTgfiJms3R+WaCIUnYyM3uM/MJR31StI68z6bAN0aOY3HGm/1JIdsKfNAg0p2YYNQv 2nW3QSXZ683hz8ATOnTtoZX6mxkX3jE= Date: Thu, 06 Apr 2023 01:57:39 +0100 From: xx_myself@e.email To: My Own Name <xx_myself@xx_myusername.plus.com> Subject: Repo T Message-ID: <78B432F5-8186-47B5-AE83-FAAAE924E4CC@e.email> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----4VFDO32MEEMEJ6YWCLU2VRBJF1NY7A Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=e.email; s=mail3; t=1680742663; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RBYoYMhjYNSSWrjRCb42M9ys0qNUZRKlT5IkT+LWCyU=; b=di5LNfldH3EDQd9656NQuJOqb7vxvHyEipWn/dc2azvMcA6PaceDwexzt2TIp814kWvVww eE0WkhljDBry39D7MsbPYFUPQuNkp2TegSN3IPEcYMz6VMHTU1ePEeez1Wr19fbcVn5vy6 CD4DyktUu0BaBXImxCGcF41oCaRb3UM= ARC-Seal: i=1; s=mail3; d=e.email; t=1680742663; a=rsa-sha256; cv=none; b=kjCmAzdMU7OsPJ7gc6VTUn5/90JNyroKSyIt43sRK4YhmYprzYyV/nea5DW+1Bkpy04Npq U1suQuN1wU3TdvWKF1v+PmUR1H+r7/XGhI1S5amLUubsz0DsJ1esW2FGL6DNzLgd/Qk7Bz s3dWaX1+3MGXC4y6KbSl/oLoXlQNPZo= ARC-Authentication-Results: i=1; mail3.ecloud.global; auth=pass smtp.mailfrom=xx_myself@e.email ------4VFDO32MEEMEJ6YWCLU2VRBJF1NY7A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable https:*//gitlab=2Ee=2Efoundation/e/os/android/-/tree/v1-t -- Sent from /e/ Mail=2E ------4VFDO32MEEMEJ6YWCLU2VRBJF1NY7A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><body><div dir=3D"auto">https:*//gitlab=2Ee=2Efoundati= on/e/os/android/-/tree/v1-t</div><div dir=3D"auto">-- Sent from /e/ Mail=2E= </div></body></html> ------4VFDO32MEEMEJ6YWCLU2VRBJF1NY7A--

This issue has escalated from the situation reported in this post where the email was reported bounced while now as shown above, I have evidence that the email is bounced.

https://community.plus.net/t5/Email/Incoming-email-is-reported-bounced/td-p/1898928

Re: Incoming email is bounced - Reopened

Baldrick1 — Sat, 08 Apr 2023 10:14:51 GMT

Moderators Note

This post has been released from the automatic spam filter.

Re: Incoming email is bounced - Reopened

Townman — Sat, 08 Apr 2023 11:37:56 GMT

Is that the SENT email headers or the non-delivery report email headers?

I cannot see anything therein referring to Plusnet's mail servers.

Re: Incoming email is bounced - Reopened

inkyfingers — Sat, 08 Apr 2023 14:04:51 GMT

Thanks for your reply @Townman

The "delivery failure" message was in two parts, I spent time redacting one part without considering the other, which read

Reporting-MTA: dns; mail3.ecloud.global X-Postfix-Queue-ID: 9B0F7883182 X-Postfix-Sender: rfc822; xx_myself@e.email Arrival-Date: Thu, 6 Apr 2023 00:57:42 +0000 (UTC) Final-Recipient: rfc822; xx_myself@xx_myusername.plus.com Original-Recipient: rfc822;xx_myself@xx_myusername.plus.com Action: failed Status: 5.0.0 Remote-MTA: dns; mx.avasin.plus.net Diagnostic-Code: smtp; 552 Spam Message Rejected

Re: Incoming email is bounced - Reopened

Townman — Sat, 08 Apr 2023 19:21:26 GMT

Are there any X-Headers?

Re: Incoming email is bounced - Reopened

inkyfingers — Sun, 09 Apr 2023 11:51:42 GMT

Hi @Townman, I do not think that there are any X- headers, I do not see them.