tickets #115676
openFwd: Mail delivery failed: returning message to sender
0%
Description
Hi postmaster
Why I can't reply since month on the factory mailing list?
What I do wrong?
Regards
Ulf
---------- Weitergeleitete Nachricht ----------
Betreff: Mail delivery failed: returning message to sender
Datum: Dienstag, 23. August 2022, 22:53:56 CEST
Von: GMX Mailer Daemon mailer-daemon@gmx.net
An: ub22@gmx.net
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 failed:
factory@lists.opensuse.org:
SMTP error from remote server for TEXT command, host: mx2.opensuse.org
(195.135.221.158) reason: 550 5.7.1 Spam identified (9.2/5.0)
--- The header of the original message is following. ---
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net;
s=badeba3b8450; t=1661288034;
bh=AP61kP/fuYGgR3eOp5L1GqeonXAtIy7CaN6KDzB6yNI=;
h=X-UI-Sender-Class:From:To:Subject:Date:In-Reply-To:References;
b=GnaReKjIne1/zfWyACyyh6/+lbPZ38RQJTbanpE+mYetnMXjZyBqUYhFDdHYpzImq
41nttReecXcqYnbNmdDC7koTUc30g/JPEKtk7wikfV4qBaaGSzbuiDgY2sj8ZTzpFP
uIhnrABfPge1wJa3ZeP568GA6gf6ofCCMDbfGE5A=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from peterle.localnet ([89.245.43.5]) by mail.gmx.net (mrgmx005
[212.227.17.190]) with ESMTPSA (Nemesis) id 1MOREi-1ooHMq01QE-00Pz48 for
factory@lists.opensuse.org; Tue, 23 Aug 2022 22:53:54 +0200
From: Ulf ub22@gmx.net
To: factory@lists.opensuse.org
Subject: Re: New Tumbleweed snapshot 20220821 released!
Date: Tue, 23 Aug 2022 22:53:52 +0200
Message-ID: 2934464.yNNZy2ov5i@peterle
X-Face: (za#x/JykRsk![2*[4cetv"OhhfrEDR5R8L}=;QJB
$$+?SspoN7QwezKdtQ'$vD[(?|{v8t+AD6]g@Ov9Hw0;\OX>dOd9[wF&VR5G9yu9>}SqS5"qjj2!FI)De.xE']?pP\8Kr?;58];oWi-cS=Mtt4eMI&(3Y}2n-/9
Ur,U1a3Zh9S^oQq-_]4.{uGqm5|]Fo&X(q%/7Hi8O$gF[S6kl<P}fxTk4L,gU"]uRgBa~s
'WXA*>(4_C,geES
SOiO7#Ex5"#tKgnmiN&WBCW|Q&F-mg92xlX)nA#%
In-Reply-To:
166125986557.24828.10622981276222291262@mailman3.infra.opensuse.org
References: 166116610076.28280.7153368692275901812@localhost
166125986557.24828.10622981276222291262@mailman3.infra.opensuse.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K1:ODHwJLeAoNQd+Kstcw9iFAufgeS+WUdQoM6ZKg7cUYkJyAQ7Xza
qtRA8zi49r8kDuNgZW2aL0Zk4OXDRX4wOQFH4V5VeU/IiHugeDPL+1qzKOhj9T5jSWpFq9Y
Eqlm7BWkbo+oDa0H95zbGPS4yEteqSxgSB3HRJhFNTGO0qSuv4jlNRbhKjF4xCwH1gHmD5q
Cjo9jKOr1gkX0ZcDHVuug==
X-Spam-Flag: NO
X-UI-Out-Filterresults: notjunk:1;V03:K0:LT5gAvhChO8=:jO1dRAX/GwHFKi3Ckh8HRo
7CpFwXRlZ6L4SoSIMf6K2k+QJEBZqXlTZdwt6T8wGQOOqvVFkTjD1rnkZsTcPIqkf3cYrfK5M
UxV5ROApfkmNW7oMcIW4mOw1Ftl3r0tZldxugeIEsROEWTHQGwcOSVkTD5GbAzf4WCnV+YvoK
mXhb/Vy6dv4lV1138Xs4uAJqWieSFfhT17+NirPO1VzEMYzgit21tX8yk97WqwM23SZTZ7EYP
7ZuGKfStLCXC/mr3lLgadF7G0Dv4MqK0U6xqy4FahkwyOqJt3K3GK7P6F+cY53GD9pd1rjNd6
YnVUqVuXYXmbJWZBfVjyKRJGspxe4kO0Q86L7JurT1U34/Hvw3P6LvzTBy4CsZrWURHp/LmTr
JuKEeaXk5HRhjr3NufNSn4GTJKOSjSNvum+G/u6AmwMR4veVEEFveMSP7XkhN/YD0VgE5YV+3
DqjSdXbkTenAOLUve38ErmbK7JC1PL7EDaV7NRllNW7A83wQ7pDhBlQoGNjRuAdEhPiWpiMUn
BiEZRE9QTtMh+uyEZLpCwcBWzO5GUWdQOIMk5akZdWoZZyVJEWYAlws08XpvjopnbZDYJG/Gk
ZNORtc/1kCg+Q82EGDXF2RSjPwfXbaErfK0R6qRP88iHZjH/RBCD57pxfz8WFA5tAcbdzkBE9
1Q9NPm338ixdY44JMLmj0Cn2akb0/RqnA/B3hErTbJ5wCVWlPC93QGHBLTZp3DimrN9wPls6M
3+5rggDNlXzaSqWAjv76Xws2LA7rMKelybrPy04pONLrGiIIQ0VciL/AHSH+I14L18rF99Gop
aMNlIDbIeuAqEj21N5akHvV+RJaOXi0OxrqSMkCy/AtrPGsnQn6snsBMEsTZtSlfbkt3rZexK
NN/0uZnsdOaW6y/kqa+nDBL0CW5ChxKqfd0YxvtUNfvGJlzixub8XqupUstj81RrGBEvPyt1k
xUkS+xWyFPMlkd+PHE/KvYc7genjFdMtUenjdOIbnMG4lc7O7lIg68HHbuwhQE0897sF8OuPa
gtftAeEJglWHjLCc1zL/vCKNrxH7GnzFWDFskZZE8vnHFmtKlYvQd94Lm5gz2BVcRToHJv1G5
lPiZtXRutbrWU5Y+8cS3pgMj0YEOF7bfBex
Files
| Screenshot_20220828_141126.png (61.4 KB) Screenshot_20220828_141126.png | See email I would answer -red arrow |
Updated by cboltz over 1 year ago
- Category set to Mailing lists
- Status changed from New to Feedback
The reason is most likely (without checking the logs)
Subject: Re: New Tumbleweed snapshot 20220821 released!
You might have noticed that the snapshot announcement says that you shouldn't reply to it - and thanks to several cases where people ignored this and replied with a fullquote, such replies are now blocked. Unfortunately we can't give a detailed reject message, so you'll only see "Spam identified".
My guess is that you should be able to reply to a mail on factory if it has a different subject. Please test (once you have something relevant to say) and report back ;-)
Updated by pjessen over 1 year ago
- Private changed from Yes to No
cboltz wrote:
The reason is most likely (without checking the logs)
Subject: Re: New Tumbleweed snapshot 20220821 released!
Yes, that is the reason. (also without checking any logs).
You might have noticed that the snapshot announcement says that you shouldn't reply to it - and thanks to several cases where people ignored this and replied with a fullquote, such replies are now blocked. Unfortunately we can't give a detailed reject message, so you'll only see "Spam identified".
Yeah, that is unfortunate, but because we scan mails without queueing them, we are unable to change them, and e.g. append the scan result.
My guess is that you should be able to reply to a mail on factory if it has a different subject.
Absolutely.
Updated by pjessen over 1 year ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
I think we can close this as resolved.
Updated by ub22@gmx.net over 1 year ago
pjessen wrote:
I think we can close this as resolved.
What is the clear action about this?
From my point of view, it's not OK.
- Not each simple user will be able to file a bug properly
- In case of critical issues (like in my case the topic that a System will be damaged after an update) can't be shared fast. No standard user is able to look continuous on critical bugs at Bugzilla! (see my bug report https://bugzilla.opensuse.org/show_bug.cgi?id=1202840)
- In case you block the reply, than at least the feedback mail should have a clear statement (what is the issue, and what are possible ways to give a clear feedback to a snapshot) If it isn't possible by technical reasons to have it marked as span, at least in the disclaimer should be a remark, that it can be a reason out of the answer of an automatic snapshot report!
- Why some people can reply on this emails and other not (I would answer on the email from "t neo" (see red arrow in the screenshot) and not on the main automatic email itself!
Thanks
Ulf
Updated by pjessen over 1 year ago
- Status changed from Resolved to New
- % Done changed from 100 to 0
ub22@gmx.net wrote:
pjessen wrote:
I think we can close this as resolved.
What is the clear action about this?
I'm sorry, I thought Christian explained it quite well: "do not reply to the Tumbleweed snapshot announcement without changing the subject". We were waiting for your feedback for a couple of days, but it seemed reasonable to close without it.
From my point of view, it's not OK.
Okay. From my point of view, there is nothing for us to do. The procedure of rejecting such replies has been in place since Feb2021.
- In case you block the reply, than at least the feedback mail should have a clear statement (what is the issue, and what are possible ways to give a clear feedback to a snapshot)
As I explained, that is unfortunately not possible, due to the way that filter was implemented. I agree it is less than optimal, but I don't think anyone is going to re-work our entire mail setup just to fix this. (mailman does have some filters too, but they are not sufficiently flexible).
- Why some people can reply on this emails and other not (I would answer on the email from "t neo" (see red arrow in the screenshot) and not on the main automatic email itself!
Generally, nobody except Dimstar is able to send a mail with a subject containing "New Tumbleweed snapshot [0-9]+ released" to the factory list. However, in this case it looks like "t neo" used the Hyperkitty interface to send a reply, and those are sent directly to the lists.
Updated by ub22@gmx.net over 1 year ago
pjessen wrote:
ub22@gmx.net wrote:
pjessen wrote:
I think we can close this as resolved.
What is the clear action about this?
I'm sorry, I thought Christian explained it quite well: "do not reply to the Tumbleweed snapshot announcement without changing the subject". We were waiting for your feedback for a couple of days, but it seemed reasonable to close without it.
OK - not good but I need to accept it :-(
- In case you block the reply, than at least the feedback mail should have a clear statement (what is the issue, and what are possible ways to give a clear feedback to a snapshot)
As I explained, that is unfortunately not possible, due to the way that filter was implemented. I agree it is less than optimal, but I don't think anyone is going to re-work our entire mail setup just to fix this. (mailman does have some filters too, but they are not sufficiently flexible).
That I don't understand. If you put a section in the "SPAM reply text" (hard coded), that in case of reply to a "New Tumbleweed snapshot [0-9]+ released" message it will also happen?
(Means - to edit the SPAM reply text in your Maillist program)
Updated by crameleon about 1 year ago
- Status changed from New to Feedback
- Assignee set to pjessen
Updated by pjessen about 1 year ago
ub22@gmx.net wrote:
That I don't understand. If you put a section in the "SPAM reply text" (hard coded), that in case of reply to a "New Tumbleweed snapshot [0-9]+ released" message it will also happen?
(Means - to edit the SPAM reply text in your Maillist program)
We are using SpamAssassin, invoked over spampd. Where exactly are you proposing I put this? The mailing list manager (mailman3) is not involved.