Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: spam mails using image/gif in multipart/alternative
Date: Fri, 09 Dec 2005 21:29:26 +0900	[thread overview]
Message-ID: <b4mhd9io3mh.fsf@jpl.org> (raw)
In-Reply-To: <v9zmnave9s.fsf@marauder.physik.uni-ulm.de>

>>>>> In <v9zmnave9s.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:

> I've used the following up to now:

> (setq
>  mm-discouraged-alternatives
>  '("text/html" "text/richtext" "text/enriched" "multipart/related")
>  mm-automatic-display (remove "text/html" mm-automatic-display)
>  gnus-buttonized-mime-types '(".*/signed"))

> I newer saw legitimate preferred image/.* parts in
> multipart/alternative, but I hesitate to make such change based on my
> usage only.  If everyone agrees with this, we could change the
> default.  (Only in the trunk or in v5-10 too?  Is it a bug that Gnus
> displays image/* spam?)  Opinions?

I don't know how a multipart/alternative mail of which the second
part is an image is useful (they are often pictures of pills ;-).
There might be mailers which display both of two parts.  (Gnus
may have to do so if content types of two parts are different,
e.g., one is text/*, the other is image/*.)

At any rate, I think making it default to (image/.*) is commonly
useful because most of such mails are spam and it is not worth
seeing such images.

>> My setting is:
>>
>> (setq gnus-buttonized-mime-types
>>       '("multipart/alternative" "multipart/signed")
>>       mm-discouraged-alternatives
>>       '("image/.+"))

> Interesting idea!  It allows to pick the alternative (text, html, gif)
> an displays the plain/text at first:

> ,----
>| 1.  (*) multipart/alternative  ( ) image/gif
>|
>| 2.  (*) text/plain          ( ) text/html
> `----

> Could you please add this suggestion as an example to the manual?

I'll do it next week.

> (Maybe we write "/.*" instead of "/.+" as in other places; the
> difference might confuse newbies.  Or we could change everything to
> "/.+" which is slightly more exact.)

I'll also use `.*' since the differences aren't significant.



  reply	other threads:[~2005-12-09 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 21:14 Reiner Steib
2005-12-08 22:39 ` Katsumi Yamaoka
2005-12-09  8:57   ` Reiner Steib
2005-12-09 12:29     ` Katsumi Yamaoka [this message]
2005-12-16 12:24       ` Katsumi Yamaoka
2005-12-19  7:42         ` Katsumi Yamaoka
2005-12-15 15:25   ` multipart/alternative in gnus-buttonized-mime-types (was: spam mails using image/gif in multipart/alternative) Reiner Steib
2005-12-15 23:12     ` multipart/alternative in gnus-buttonized-mime-types Katsumi Yamaoka
2005-12-16 11:58       ` Katsumi Yamaoka

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=b4mhd9io3mh.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    /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).