Project

General

Profile

Actions
Copy link

tickets #151076

open

Fwd: Mail delivery failed: returning message to sender

Added by docb@opensuse.org 5 months ago. Updated 5 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
pjessen
Category:
Mailing lists
Target version:
-
Start date:
2023-11-19
Due date:
% Done:

50%

Estimated time:

Description

Hey Gents,

why are my mails classified as Spam?

Cheers
Axel

Files

Download all files
signature.asc (833 Bytes) signature.asc docb@opensuse.org, 2023-11-19 21:33
New Tumbleweed snapshot 20231113 released!.mbox (920 Bytes) New Tumbleweed snapshot 20231113 released!.mbox DocB, 2023-12-04 19:17
Actions
Copy link
 #1

Updated by crameleon 5 months ago

  • Category set to Mailing lists
  • Assignee set to pjessen
  • Private changed from Yes to No

Hi @pjessen,

would you take this?

Georg

Actions
Copy link
 #2

Updated by pjessen 5 months ago

Hi Axel,
exactly who is classifying your mails as spam?

Actions
Copy link
 #3

Updated by DocB 5 months ago

Hi Per,
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)

-> looks like the opensuse mail server

Actions
Copy link
 #4

Updated by pjessen 5 months ago

DocB wrote in #note-3:

Hi Per,
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)

-> looks like the opensuse mail server

Yep, it does - that's quite a high score :-)

Actions
Copy link
 #5

Updated by pjessen 5 months ago

pjessen wrote in #note-4:

DocB wrote in #note-3:

Hi Per,
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)

-> looks like the opensuse mail server

Yep, it does - that's quite a high score :-)

On the 19 November, the only mails that scored 9.2 had hits RCVD_IN_BL_SPAMCOP_NET and RCVD_IN_DNSWL_BLOCKED - they don't look like they came from you though.
Can you tell me when (makes it easier to find in the log) you had such a reject, maybe also upload the failed mail?

Actions
Copy link
 #6

Updated by DocB 5 months ago

It was actually 16.11.23 14:03
I attache the original mail (actually, I had some attempts to send, so there should be some more from me around that time)

Actions
Copy link
 #7

Updated by pjessen 5 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

DocB wrote in #note-6:

It was actually 16.11.23 14:03
I attache the original mail (actually, I had some attempts to send, so there should be some more from me around that time)

"New Tumbleweed snapshot 20231113 released!"

That is the problem - replying to the snapshot announcement without changing the subject.

Actions
Copy link
 #8

Updated by DocB 5 months ago

pjessen wrote in #note-7:

"New Tumbleweed snapshot 20231113 released!"

That is the problem - replying to the snapshot announcement without changing the subject.

Well, in fact I replied to a user (who did not change the subject).
So this is classified as spam then?

Actions
Copy link
 #9

Updated by pjessen 5 months ago

DocB wrote in #note-8:

pjessen wrote in #note-7:

"New Tumbleweed snapshot 20231113 released!"

That is the problem - replying to the snapshot announcement without changing the subject.

Well, in fact I replied to a user (who did not change the subject).

Hmm, that posting ought to have been rejected too.

So this is classified as spam then?

At the time, it was the easiest way of rejecting a posting based on the Subject contents. I agree it is not optimal, but even if we now implemented it in mailman, you would be none the wiser.

Actions
Copy link

Also available in: Atom PDF