From: John Owens <jowens@ece.ucdavis.edu>
Cc: John Owens <jowens@ucdavis.edu>, ding@gnus.org
Subject: Re: SpamAssassin support added
Date: Thu, 22 Jan 2004 14:22:01 -0800 [thread overview]
Message-ID: <16400.19721.691000.236190@ece.ucdavis.edu> (raw)
In-Reply-To: <4nbrovu9db.fsf@collins.bwh.harvard.edu>
Ted Zlatanov writes:
On Wed, 21 Jan 2004, jowens@ucdavis.edu wrote:
> I second this - I reach inside the SpamAssassin-wrapped message to
> pull out the original message and then send it to spamcop and
> uce@ftc.gov. Spamcop, at least, is happy with a message from me; the
> contents of the message are simply the whole spam message including
> headers.
I think you want something like the Gmane support in spam-report.el.
I'll take a look.
I don't use the SA wrapping myself, so I haven't had this problem.
Maybe it should be automatically detected by the spam-report function
and the message should be unwrapped before sending to an address.
I think it's a fairly common situation that people don't have control
over what happens upstream - mine get wrapped by another mail server
that I don't have access to and then forwarded to me.
I think I actually prefer the wrapping, since then I get the virgin
message without any SpamAssassin-applied additional headers. Thus if
spam-report.el unwrapped it for me and could send it along, that would
be ideal.
JDO
next prev parent reply other threads:[~2004-01-22 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 1:04 Ted Zlatanov
2004-01-21 12:00 ` Steinar Bang
2004-01-21 15:05 ` Ted Zlatanov
2004-01-21 20:12 ` Steinar Bang
2004-01-21 23:20 ` John Owens
2004-01-22 18:27 ` Ted Zlatanov
2004-01-22 22:22 ` John Owens [this message]
2004-01-23 21:01 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16400.19721.691000.236190@ece.ucdavis.edu \
--to=jowens@ece.ucdavis.edu \
--cc=ding@gnus.org \
--cc=jowens@ucdavis.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).