#1467 Spamcop plug-in broken


Hi, this is the admin of spamcop.

I recently ran into a problem with a squirrelmail user
who was submitting spam reports without really knowing
what he was doing - he was a moderator of a list serve,
and was reporting the approval requests as spam,
thinking he was reporting the attached messages as spam.

I haven't used SM myself, so I don't have first hand
information on this, but I took a look at the spamcop
plugin source. It looks like the plugin uses spamcop's
"quick" reporting (an intentionally undocumented
feature), and the user involved confirmed it. That
should not be allowed - only users who know what they
are doing should be using quick reporting, not random
SM lusers.

As a result of this, and the realization that SM had
"quick" reporting built in, I removed that feature from
spamcop except by explicit authorization.

So this quick reporting plugin is now broken. Using
spamcop with the regular confirmation-required
submission format is still OK, but better yet would a
user-configurable submission address. That way, users
who were authorized to do so could use the quick
reporting while others who aren't aware of the feature
wouldn't be using it without realizing the implications.

Feel free to contact me at the email address below if
you have questions about this policy change.





  • Tomas Kuliavas

    Tomas Kuliavas - 2003-11-12
    • assigned_to: nobody --> tokul
  • Tomas Kuliavas

    Tomas Kuliavas - 2003-11-24
    • status: open --> closed-fixed
  • Tomas Kuliavas

    Tomas Kuliavas - 2003-11-24

    Logged In: YES

    quick reporting feature is disabled in 1.5.0cvs and 1.4.3cvs.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks