On Thu, 2014-08-28 at 23:49 +0200, Karsten Bräckelmann wrote: > On Thu, 2014-08-28 at 16:14 -0500, Chris wrote: > > I'm having an issue with getting SA 3.4.0 when run as spamassassin -D -r > > to report spam to SpamCop. The errors I'm seeing are: > > Ignoring the Perl warnings for now. > > > In my v310.pre file I have: > > > > loadplugin Mail::SpamAssassin::Plugin::SpamCop > > /usr/local/share/perl/5.18.2/Mail/SpamAssassin/Plugin/SpamCop.pm > > It should never be necessary to provide the (optional) filename argument > with stock SA plugins. Even worse, absolute paths will eventually be > harmful. > > > I have set the SpamCop from and to addresses in the SpamCop.pm file: > > The Perl modules are no user-serviceable parts. Do not edit them. > > Moreover, the SpamCop plugin provides the spamcop_(from|to)_address > options to set these in your configuration. See > > http://spamassassin.apache.org/doc/Mail_SpamAssassin_Plugin_SpamCop.html > > > setting => 'cpoll...@example.com', > > setting => 'submit.exam...@spam.spamcop.net', > > Wait... What exactly did you edit? > > The only instances of 'setting' in SpamCop.pm are the ones used to > register SA options. Did you replace the string spamcop_from_address > with your email address? > > I have a gut feeling the Perl warnings will disappear, if you revert any > modifications to the SpamCop.pm Perl module and set the options in your > configuration instead... > >
That was the fix Karsten, thanks very much. Chris -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 17:31:15 up 1 day, 1:13, 4 users, load average: 0.18, 0.36, 0.31 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
