Search the Community

Showing results for tags 'amazon aws'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Community Calendar

Found 1 result

  1. I understand that sometimes reports are sent to /dev/null because the abuse@ address has requested they not be sent any longer, but is that not an abdication of their responsibilities? For a hosting company in particular, keeping on top of which systems are sending spam is vital to ensuring the security of their network, since spam most often originates from compromised servers. The abuse@ person should not be permitted to hide from the reports. Is this the reason gets /dev/nulled or is it some other reason? And when a network provider has decided to neglect it's obligation to police it's own infrastructure, does that reflect negatively on their reputation?