From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: spam-use-pgp-signed?
Date: Wed, 22 Mar 2006 18:07:23 +0100 [thread overview]
Message-ID: <87slpapfw4.fsf@mat.ucm.es> (raw)
In-Reply-To: <4n4q1shp8u.fsf@asimov.bwh.harvard.edu>
>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
Ted> On 15 Feb 2006, oub@mat.ucm.es wrote:
>> May be I am wrong, but I think there is a difference between mailcrypt
>> for pgp and the gnu support for gpg. While the former signs messages
>> inline the letter uses mime. So may be the following cheap trick might
>> do
>> (setq
>> nnimap-split-rule 'nnimap-split-fancy
>> nnimap-split-inbox "INBOX"
>> nnimap-split-fancy
>> `(| ;macro
>> ("Content-Type" "multipart/signed" "SPAM.HAM")))
Ted> Since this is a header, it's a fast check I can do as a spam filter,
Ted> if anyone is interested. Hooking it into the spam.el framework means
Ted> that, basically, the last line above will become
Ted> (setq spam-use-signed-check t) ;; or something like that
I think it would be nice. But there is a however. I just tested the
setting with gnus and mozilla-thunderbird, and 3 smtp server: my
university server, gmail and gmx.net. That is I sent a message to myself which
I signed pgp mime.
- My university server does not not chance the header and the
above setting would work.
- Gmail however produces the following header
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Accept-Language: en-us, en
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:user-agent:x-accept-language:mime-version:t
o:subject:x-enigmail-version:content-type:content-transfer-encoding:sender;
b=UQVmgpAvZMgBNilVC6jL3nU/UK+s/0Q0I4bMqo0fMedsguRm+vGvV1+rAc2djkQSsLsFU/agS
JwEwzSgQ6gA+Uk8g8aiS9lz6d0r5TbnHNOloUC1gC/ig6Dyj7Juze5pjcmBqU9sVYyRWIgAz+2K
LkImPJ1DR+sM5GAbWfIYWHo=
- Gmx even changed the content-type to
Content-type: multipart/mixed; boundary="=-=-="
So I am not sure what is the best strategy. May be to include all of
these headers?
Uwe
prev parent reply other threads:[~2006-03-22 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 20:31 spam-use-pgp-signed? Uwe Brauer
2006-02-13 19:27 ` spam-use-pgp-signed? Ted Zlatanov
2006-02-15 14:35 ` spam-use-pgp-signed? Uwe Brauer
2006-03-20 19:48 ` spam-use-pgp-signed? Ted Zlatanov
2006-03-22 17:07 ` Uwe Brauer [this message]
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=87slpapfw4.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
/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).