Ticket #1304102 (new Feature Requests: None)

Opened 3 years ago

Last modified 7 months ago

Report Spam to a mailaddress

Reported by: roundcube Owned by: nobody
Priority: 3 Milestone: later
Component: Other Version: None
Severity: critical Keywords:
Cc:

Description (last modified by thomasb) (diff)

Add a configurable e-mail address where users can send
spam reports with a single click.

Attachments

spamreport_1.0.tgz (11.9 kB) - added by wik 7 months ago.
Patch for spam reporting
spamreport-1.1.tgz (12.4 kB) - added by wik 7 months ago.

Change History

  Changed 3 years ago by rpoulton

Logged In: YES 
user_id=19991

It is important to be able to submit both false positives
and misses. Maybe if there was a configurable way to check
for certain headers in a message, you could then add a
'spam' or 'not spam' button accordingly. In many spam
systems these will require slightly different handling.

  Changed 2 years ago by nobody

Logged In: NO 

Spamassassin provides a good interface, feeding the mail to
spamc o spamassassin works, if report is needed spamassassin -r
eliastorres@gmail.com

  Changed 2 years ago by stratus@…

It won't be good implement this feature thinking that the webmail will be in the same server as the domain MX, so i would like to recommend:

User POV:

- "report as spam" option visible without click the message, like gmail.

- "report as not spam" option visible only when reading a message and if there's a ham option configured (see below).

Admin POV:

- The admin should be able to configure "spam_command", "spam_mail", "ham_command" and "ham_mail" options. {spam,ham}_command will cover the case where the MX and webmail services are in the same server. {spam,ham}_mail will be email address and cover the other scenario. It's up to admin use both if he wants to.

My 2 cents.

  Changed 2 years ago by thomasb

  • owner changed from roundcube to nobody
  • status changed from assigned to new
  • description modified (diff)
  • milestone deleted

  Changed 2 years ago by beni

I think it is important to let the admin decide wether he wants such buttons or not. If nothing is configured, no "default" should be invoked.

My spamassasin learns automatically every day from the users SPAM directory. This way, the user only needs to sort out mails. He moves false positives out of the SPAM folder or he drops missed spams from the inbox to the SPAM folder. This way spam learning is simple, user intuitive and no button is needed :)

  Changed 22 months ago by eorellan

i guess the best way to intercept the spam and ham is create a new colum, like yahoo beta webmail.

there's exist a new column in each mail then if you click the fire, sends the selected mail to spam without open the mail, at the same time, in spam folder exist the same column to select the spam as a good mail (not spam = ham), then automatic moves to inbox the mail and excludes from spam folder.

What do you think about this ?

  Changed 17 months ago by radiantmatrix

I'd like to throw a "vote" in for this feature, with some additional comments about desired behavior.

When a spam message arrives, I'd like to see the 'report spam' link to have one of two behaviors:

* Sends copy of message (with all original headers) to the administrator, using an email address configured globally (e.g. in one of the (config).inc.php files). This option is good for organizations that want to have users report to an internal group. Nice-to-have would be a header in that message set (e.g. 'X-SpamReport?: yes').

* Sends copy of message (with all original headers), to an address configured by the end user (e.g. a SpamCop? reporting address). This option is great for individual users (like me), and would be a boon for any web host that would like to use RoundCube as their standard webmail offering.

Ideally, the admin should be able to configure the behavior:

  1. No spam-reporting capabilities
  2. Report spam only to system-wide reporting address
  3. Report spam to user-supplied address
    1. Send to system-wide address if user doesn't supply one
    2. Always send to system-wide address as well
    3. No system-wide address, no spam reporting if no user address supplied

Hope this is helpful -- I'm willing to participate in developing and testing this feature, though my dev. exp is in Perl and Python, not PHP.

  Changed 12 months ago by beni

Like said above - dont forget the option of just moving the mail into another (configurable) folder. Together with the email options this would be very flexible.

Spam tagging is NOT the job of the MUA and should be the responsibility of the mail server. The MUAs job is just to give feedback back to the mail server, so he may decide better in the future. However, a direct feed to a command like said above is a good option on systems where the mailserver and mail classifier sits on the same machine.

  Changed 8 months ago by seansan

  • summary changed from Report Spam to Report Spam to a mailaddress
  • milestone set to later

Review later, sound like a plugin

Changed 7 months ago by wik

Patch for spam reporting

follow-up: ↓ 11   Changed 7 months ago by wik

I have just attached a patch against the most recent SVN tree which adds support for forwarding spam/ham to a specified email address to train the site's bayes filter (e.g., spamassassin + procmail.

This feature can be enabled with the main.inc.php, otherwise it is hidden from the user. There are possible icons to go with this, but feel free to change them.

Changed 7 months ago by wik

in reply to: ↑ 10   Changed 7 months ago by wik

Replying to wik: Fixed a UI problem where reported messages were removed from the list and required a refresh to restore.

Note: See TracTickets for help on using tickets.