Bug 3948 - spamcop submissions don't seem to work
Summary: spamcop submissions don't seem to work
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 3.0.0
Hardware: Other other
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords: triage
Depends on:
Blocks:
 
Reported: 2004-11-02 20:54 UTC by Duncan Findlay
Modified: 2005-07-02 16:53 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Duncan Findlay 2004-11-02 20:54:29 UTC 
Package: spamassassin
Version: 3.0.0-1
Severity: normal

I have set the spamcop_to_address option on user_prefs to my spamcop submission
address,
and am piping messages from mutt to  "spamassassin -r"
Everything seems to happen as it should, except that in almost all cases I
receive an error mail back from spamcop saying "spamcop encountered errors" as
the subject,
and in the body, a message that says Spamcop was unable to find a message in my
mail.
Looking at the message that spamcop returns, it appears the the offending
message is correctly inserted.
I have had spamcop accept a message from spamassassin I believe once, but even
then when I went to complete the web portion of the submission,
I was told there was no data to act on.
It looks as though something about the way spamassassin is formatting the
original message is confusing spamcop.
Comment 1 Bob Menschel 2005-05-24 21:14:42 UTC 
Duncan, a number of spamcop submission issues have been worked on and resolved
since this bug was opened.  Can you verify whether this specific problem still
exists, and at what (hopefully) newer level of SA you're experiencing it?
Comment 2 Bob Menschel 2005-07-02 23:26:40 UTC 
Triage: Closing as invalid since no response. Can reopen if anyone can reproduce
in any current version.
Comment 3 Duncan Findlay 2005-07-03 00:53:49 UTC 
Hmm... this is a Debian bug and I'm not really the one with the problem ...
usually I report these as spamassassin at packages.debian.org. But according to
the URL above, the reporter determined it was not a bug...