#12599 SpamAssassin Spams List "trans-fr"
Closed: Insufficient data by kevin. Opened by harmful-breeze.

Describe what you would like us to do:

The Fedora mailer daemon spams trans-fr@lists.fedoraproject.org [1] by sending Successful Mail Delivery Reports [2] with the "delivery via spamassassin: delivered via spamassassin service" message.

When do you need this to be done by? (YYYY/MM/DD)

It's not a major annoyance, but I'd say ASAP?

Thanks in advance :)


[1] https://lists.fedoraproject.org/archives/list/trans-fr@lists.fedoraproject.org/
[2] https://lists.fedoraproject.org/archives/list/trans-fr@lists.fedoraproject.org/thread/A5XSPYWZ5UJBLZUUZKUJNOHBTEJDIFGH/


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

Can you forward one of the emails with full headers to kevin at fedoraproject.org?

In the mean time I have set the list to discard posts from mailer-daemon@fedoraproject.org, so no more should show up

Any news here? Are you still seeing this?

As there is no response from reporter, I'm closing the issue as fixed. @harmful-breeze feel free to re-open if the issue is still happening.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

@zlopez I did actually send one of the emails I received (with headers) to @kevin after his reminder, and received a new one fairly recently

Metadata Update from @harmful-breeze:
- Issue status updated to: Open (was: Closed)

Sorry, I didn't saw any activity on the ticket for 7 days, so I assumed it's fixed.

So... looked at this a bit today.

Some more questions for you: Did you get any of these emails directly? ie, as list-owner, etc... or are all of them just posted to the list?

I see you are allowing .@fedoraproject.org to bypass the subscriber check and post to the list.
Is it ok to drop that? That would prevent these from actually going to the list.

That said, these are DSN's (delivery status notifications). So, the client is setting that... we should likely drop them all in postfix config.
I can look at doing that if the above doesn't solve things for you.

If you have more info, please feel free to re-open this...

Metadata Update from @kevin:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

Metadata