Jump to content

Search the Community

Showing results for tags 'bug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Discussions & Observations
    • Announcements
    • Start Here - before you make your first Post
    • How to use .... Instructions, Tutorials
    • Going to make your first post here?
    • SpamCop Reporting Help
    • SpamCop Blocklist Help
    • SpamCop Email System & Accounts
    • Mailhost Configuration of your Reporting Account
    • New Feature Request
    • SpamCop Lounge
    • Geek/Tech Things
    • Suggested Tools and Applications
    • Testing
    • FAQ Under Construction

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. I've been getting more spam that is tailored to circumvent SpamCop. The latest one has two 'exploits' ... one is a limitation of SC (that shouldn't exist); the other is a new 'bug'. Three key areas that impede SC reporting: Bug: eMail subject line that causes the email body to not be processed. How / do you want me to report this? (As it has header info; I don't want to post it in a public forum) It's been raised before, and I'll raise it again: The hard limitation of links needs to be re-though and re-designed. This same message as #1; they had over 900 lines of "https://products.office.com/en-us/products..." which were obviously intended to circumvent SC reporting. Suggested fix (for each item .. If number exceed): Remove duplicates; as duplicate email's checked and are not set; not counting duplicates would be a big first step. Remove known URL's that a) don't accept reports or b) known "red herring" URL's (microsoft.com as an example) If max is still exceed .. report only the first "n" - or - allow me to choose which "n" should be reported; with them all disabled Rethink the max char limited. Another circumvention technique is to add a substantial amount of html / formatting / white space at the top of the body. When SC truncates (at max chars); the URL's are below that line; and they don't get reported. Suggested fix: Pre-process email to ignore/strip/remove non-visible HTML/white space before truncate and/or search for URL's before truncate. I realize that a great deal of this is "the way it's always been". The spammers are getting around that; and SC needs to be updated to handle the new tactics.
  2. Hi all, I have submitted a piece of spam via e-mail, but when I go to the report page, there is no submit button. To replicate; go to the report page: https://www.spamcop.net/sc?id=z6415792879z94369335a4f925bdc059acc19898c79dz I've tried with Chromium and Firefox on Debian. Rasmus
  3. https://www.spamcop.net/sc?id=z6373673157zfcf5d8744ed20927f013c0ab2388921ez The bottom 'Received:' header has "from cubecube..home (unknown...". When submitted (above link) it aborts parsing the header. When I changed that Received: line to 'cube.cube.home' it parses the header just fine. There must be a bug in the parsing code that causes it to sh** the bed on bad hostnames.
×