tickets #151076
closedFwd: Mail delivery failed: returning message to sender
50%
Description
Hey Gents,
why are my mails classified as Spam?
Cheers
Axel
Files
Updated by crameleon about 1 year ago
- Category set to Mailing lists
- Assignee set to pjessen
- Private changed from Yes to No
Updated by pjessen about 1 year ago
Hi Axel,
exactly who is classifying your mails as spam?
Updated by DocB about 1 year 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
Updated by pjessen about 1 year 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 :-)
Updated by pjessen about 1 year 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?
Updated by DocB about 1 year ago
- File New Tumbleweed snapshot 20231113 released!.mbox New Tumbleweed snapshot 20231113 released!.mbox added
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)
Updated by pjessen about 1 year 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.
Updated by DocB about 1 year 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?
Updated by pjessen about 1 year 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.
Updated by crameleon 6 months ago
- Status changed from In Progress to Closed
Closing as it is working as intended (spam classification by subject), solution is to adjust the subject slightly. I cannot track what email with the restricted subject was replied to that did not get caught, if you find it, please let us know which one as to investigate further.