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... -- char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
