Provided by: spamassassin_4.0.0-7ubuntu1_all bug

NAME

       Mail::SpamAssassin::Plugin::SpamCop - perform SpamCop reporting of messages

SYNOPSIS

         loadplugin     Mail::SpamAssassin::Plugin::SpamCop

DESCRIPTION

       SpamCop is a service for reporting spam.  SpamCop determines the origin of unwanted email
       and reports it to the relevant Internet service providers.  By reporting spam, you have a
       positive impact on the problem.  Reporting unsolicited email also helps feed spam
       filtering systems, including, but not limited to, the SpamCop blocklist used in
       SpamAssassin as a DNSBL.

       Note that spam reports sent by this plugin to SpamCop each include the entire spam
       message.

       See https://www.spamcop.net/ for more information about SpamCop.

USER OPTIONS

       spamcop_from_address user@example.com   (default: none)
           This address is used during manual reports to SpamCop as the From: address.  You can
           use your normal email address.  If this is not set, a guess will be used as the From:
           address in SpamCop reports.

       spamcop_to_address user@example.com   (default: generic reporting address)
           Your customized SpamCop report submission address.  You need to obtain this address by
           registering at "https://www.spamcop.net/".  If this is not set, SpamCop reports will
           go to a generic reporting address for SpamAssassin users and your reports will
           probably have less weight in the SpamCop system.

       spamcop_max_report_size   (default: 50)
           Messages larger than this size (in kilobytes) will be truncated in report messages
           sent to SpamCop.  The default setting is the maximum size that SpamCop will accept at
           the time of release.

       spamcop_relayhost server:port  (default: direct connection to SpamCop)
           Direct connection to SpamCop servers (port 587) is used for report submission by
           default.  If this is undesirable or blocked by local firewall policies, you can
           specify a local SMTP relayhost to forward reports.  Relayhost should be configured to
           not scan the report, for example by using a separate submission port.  SSL or
           authentication is not supported.