On Fri, 10 Sep 2021 12:57:59 -0700 L A Walsh wrote: [snip] You missed the one address that is useful admin@opensuse.org

On 2021/09/11 01:00, Per Jessen wrote:

Dave Howorth wrote:

...

On Fri, 10 Sep 2021 12:57:59 -0700 L A Walsh wrote: [snip] You missed the one address that is useful admin@opensuse.org

Not entirely, as I got this back in 1 response: Your mail to 'admin-auto@lists.opensuse.org' with the subject Fwd: Returned mail: see transcript for details Is being held until the list moderator can review it for approval. === I tried postmaster and I think that caused it to goto admin-auto, so I didn't know the list-specific address I did try the general, postmaster, which seemed to trigger the routing you say is useful.

I take it there was an implicit question of why the posting got identified as spam?

---- Well, sorta,

The reason being - please don't reply to Tumbleweed snapshot announcements _without_ changing the subject.

---- Why? [...**!!!***] it was in reference to the announcement, though...

It is unfortunately not so easy to get that message back to the poster.

=== it was NOT specifically to the person who's script was running. It's more of a general question to the list asking why are there 4 date-times associated with a release that are all different from each other. Two might be the same but for timezone, not sure, but 3 were definitely different. After trying to send that a few times, I was getting a bit peeved and wondering how a list that had never marked any of my posts as spam suddenly seemed to be marking most of them as spam. **!!!***--Wait, are you saying that because my topic pertained to the release announcement and, I logically used a subject responding to the release announcement, that having a correct subject for the topic in this case, caused the spam flag? That's horrible! It wasn't spam, and it was proper use of the subject. If that user doesn't want responses to that mail, that's fine, they can route any messages received on their machine to 'trash', but the message to the list was to the list, not them. If you check the original email, their email wasn't included as one of the addressee's because it wasn't something about their email that I necessarily thought was pertinent to them -- I only sent it to the list because that's where I wanted it to go. Usually, if I responding to a person's email, and I am responding to what they said (on a list), I will send a copy to both the list and to them with the intent that I was sending it to the list for possible comment, but was also responding specifically to something they said, so according to internet convention and general politeness, I also addressed the response to them as well. Now that is a courtesy that they can control by adding a "reply-to" field that excludes them, or by adding a filter on their end. It isn't something a list or ISP should mangle as it violates normal email RFC's and standards. Google, w/gmail and its other products demonstrates a penchant for violating such standards and will auto-delete duplicate emails that might go to a user. That causes me no end of problems as some emails goto the list, and some goto me, with the effect that any conversation isn't kept together, with following an email chain jumping back and forth between multiple folders on my machine: -- "Record (Sent)", the list-folder, and my "domain" folder. Even though people who send responses to me and the list, properly, end up w/their response to the list not appearing in my list box, but usually in my 'Domain' box as that gets sent directly to me and doesn't go through the list reflector and gets here first. Anyway -- auto-spamming based on a logical and useful subject seems very likely to catch normal users by surprise and doesn't seem to be very user-friendly?

L A Walsh wrote:

On 2021/09/11 01:00, Per Jessen wrote:

...

The reason being - please don't reply to Tumbleweed snapshot announcements _without_ changing the subject.

---

Why? [...**!!!***] it was in reference to the announcement, though...

It is the agreed-upon "netiquette" on the factory list.

**!!!***--Wait, are you saying that because my topic pertained to the release announcement and, I logically used a subject responding to the release announcement, that having a correct subject for the topic in this case, caused the spam flag?

Any posting with subject matching "New Tumbleweed snapshot [0-9]+ released" will be refused, which we do by identifying it is as spam, yes.

That's horrible! It wasn't spam, and it was proper use of the subject.

It is probably best to take this up on the factory list. -- Per Jessen, Zürich (17.1°C) Member, openSUSE Heroes.