On Mon, 2022-09-12 at 07:40 +0000, David Lex wrote:
Best Gaming Laptop:
[...]
What does this have to do with Fedora?
poc
On 9/12/22 03:42, Patrick O'Callaghan wrote:
On Mon, 2022-09-12 at 07:40 +0000, David Lex wrote:
Best Gaming Laptop:
[...]
What does this have to do with Fedora?
It's spam.
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
^^^
On Mon, Sep 12, 2022 at 09:02:25AM -0700, Samuel Sieb wrote:
On 9/12/22 03:42, Patrick O'Callaghan wrote:
On Mon, 2022-09-12 at 07:40 +0000, David Lex wrote:
Best Gaming Laptop:
[...]
What does this have to do with Fedora?
It's spam.
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
^^^
Yep.
It's already been removed from archives and the user banned.
kevin
On Mon, 2022-09-12 at 14:31 -0700, Kevin Fenzi wrote:
On Mon, Sep 12, 2022 at 09:02:25AM -0700, Samuel Sieb wrote:
On 9/12/22 03:42, Patrick O'Callaghan wrote:
On Mon, 2022-09-12 at 07:40 +0000, David Lex wrote:
Best Gaming Laptop:
[...]
What does this have to do with Fedora?
It's spam.
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
^^^
Yep.
It's already been removed from archives and the user banned.
Thanks. I do wish the spam reporting were a little easier. There's quite a lot to fill in manually on that bug page, including a reliable reference to the offending message. Could this not be automated in the footer link, e.g. by including the Message-ID?
On Tue, 2022-09-13 at 11:54 +0100, Patrick O'Callaghan wrote:
Could this not be automated in the footer link, e.g. by including the Message-ID?
Technically you could automate it in a variety of ways. e.g. Each message through the list gets a "report me" link added to it with a their unique ID in the link. Or, you forward an entire message (headers and all) to an automatic assessor.
However, you would need some double-checks to stop miscreants deliberately abusing the system by falsely reporting normal messages. The simplest one being that a certain number of people would have to report the same post to get past a threshold.
On Tue, 2022-09-13 at 20:59 +0930, Tim via users wrote:
On Tue, 2022-09-13 at 11:54 +0100, Patrick O'Callaghan wrote:
Could this not be automated in the footer link, e.g. by including the Message-ID?
Technically you could automate it in a variety of ways. e.g. Each message through the list gets a "report me" link added to it with a their unique ID in the link. Or, you forward an entire message (headers and all) to an automatic assessor.
However, you would need some double-checks to stop miscreants deliberately abusing the system by falsely reporting normal messages. The simplest one being that a certain number of people would have to report the same post to get past a threshold.
Yes, that would make sense. And presumably some sort of check against list membership.
poc
On Tue, Sep 13, 2022 at 12:52:45PM +0100, Patrick O'Callaghan wrote:
On Tue, 2022-09-13 at 20:59 +0930, Tim via users wrote:
On Tue, 2022-09-13 at 11:54 +0100, Patrick O'Callaghan wrote:
Could this not be automated in the footer link, e.g. by including the Message-ID?
Technically you could automate it in a variety of ways. e.g. Each message through the list gets a "report me" link added to it with a their unique ID in the link. Or, you forward an entire message (headers and all) to an automatic assessor.
However, you would need some double-checks to stop miscreants deliberately abusing the system by falsely reporting normal messages. The simplest one being that a certain number of people would have to report the same post to get past a threshold.
Yes, that would make sense. And presumably some sort of check against list membership.
Every post has a Archived-At: header that provides a link to that exact message in the archives. That can be provided to identify the message.
kevin
On Tue, 2022-09-13 at 07:47 -0700, Kevin Fenzi wrote:
On Tue, Sep 13, 2022 at 12:52:45PM +0100, Patrick O'Callaghan wrote:
On Tue, 2022-09-13 at 20:59 +0930, Tim via users wrote:
On Tue, 2022-09-13 at 11:54 +0100, Patrick O'Callaghan wrote:
Could this not be automated in the footer link, e.g. by including the Message-ID?
Technically you could automate it in a variety of ways. e.g. Each message through the list gets a "report me" link added to it with a their unique ID in the link. Or, you forward an entire message (headers and all) to an automatic assessor.
However, you would need some double-checks to stop miscreants deliberately abusing the system by falsely reporting normal messages. The simplest one being that a certain number of people would have to report the same post to get past a threshold.
Yes, that would make sense. And presumably some sort of check against list membership.
Every post has a Archived-At: header that provides a link to that exact message in the archives. That can be provided to identify the message.
That's helpful.
poc
On Tue, 2022-09-13 at 07:47 -0700, Kevin Fenzi wrote:
Every post has a Archived-At: header that provides a link to that exact message in the archives. That can be provided to identify the message.
Though headers aren't so easily viewed on some systems. You typically get your choice of about four (to/from/date/subject) or all of them (and that can be a lot). If people read on mobile devices, they may not get any choice about it.
If I click on that header in Evolution (as you'd expect to be able to with a HTTP address) I get a 503 error from a web server. I still get a 503 error if I strip it back to: https://lists.fedoraproject.org/
The point me and Patrick were commenting on was making it easier to report spam. Not a different way of difficulty. With the current system, the issue reporting link at the bottom of an email, I have to create a Fedora account before I even know what procedure I'm going to have to go through. At that stage I abort with a "not yet another account I have to create, I'm already drowning in passwords".
On Wed, Sep 14, 2022 at 10:21:09AM +0930, Tim via users wrote:
On Tue, 2022-09-13 at 07:47 -0700, Kevin Fenzi wrote:
Every post has a Archived-At: header that provides a link to that exact message in the archives. That can be provided to identify the message.
Though headers aren't so easily viewed on some systems. You typically get your choice of about four (to/from/date/subject) or all of them (and that can be a lot). If people read on mobile devices, they may not get any choice about it.
If I click on that header in Evolution (as you'd expect to be able to with a HTTP address) I get a 503 error from a web server. I still get a 503 error if I strip it back to: https://lists.fedoraproject.org/
Thats because it was down. ;)
Please try again now. The vpn cert on the mail server had expired, been renewed, but not yet pushed out to it.
The point me and Patrick were commenting on was making it easier to report spam. Not a different way of difficulty. With the current system, the issue reporting link at the bottom of an email, I have to create a Fedora account before I even know what procedure I'm going to have to go through. At that stage I abort with a "not yet another account I have to create, I'm already drowning in passwords".
Sure, I can see that, but... if you can't easily report it, just ignore it? Either I or some other admin will see it and take care of it, or someone else will report it. I don't think we have a problem of unreported spam. At least not currently.
kevin
Tim:
If I click on that header in Evolution (as you'd expect to be able to with a HTTP address) I get a 503 error from a web server. I still get a 503 error if I strip it back to: https://lists.fedoraproject.org/
Kevin Fenzi:
Thats because it was down. ;)
Please try again now. The vpn cert on the mail server had expired, been renewed, but not yet pushed out to it.
Yes, it works now.
-
Kevin Fenzi -
Patrick O'Callaghan -
Samuel Sieb -
Tim