openSUSE admin

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 ;-)

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.

I think we can close this as resolved.

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.

1. Not each simple user will be able to file a bug properly
2. 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)
3. 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!
4. 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

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.

1. 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).

1. 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.