cid problems

cid problems

[google]

Hi--

I recently upgraded to No Gnus 0.4 from Debian,
under XEmacs 21.4 patch 17 Jumbo Shrimp,
and cid rendering seems to have stopped working.

It's possible I changed something in .gnus, but I don't think so...

Here's what seems like it might be relavent:

(setq mm-automatic-display
      '(
        "application/pgp-signature"
        "image/gif"
        "image/jpeg"
        "image/png"
        "message/delivery-status"
        "message/rfc822"
        "multipart/related"
        "multipart/mixed"
        "text/enriched"
        "text/html"
        "text/richtext"
                         ))
(setq mm-discouraged-alternatives
      '("text/html"
        "text/richtext"))
(add-to-list 'mm-inlined-types "message/rfc822")
(setq mm-inline-large-images 'T)
(setq mm-inline-text-html-with-images 'T)
(setq mm-w3m-safe-url-regexp 'nil)
(setq mm-text-html-renderer 'w3m)
(setq w3m-default-display-inline-images 'T)
(setq w3m-display-inline-image 'T)


I had to set mm-w3m-safe-url-regexp to nil to make cid's render before
I upgraded. Despite what the manual said, under the previous debian
gnus rev,
if I left it alone, cid's didn't work, and when I flipped it to nil,
they did...

  thanks for any clues...
   --akb

Re: cid problems

[Katsumi Yamaoka]

>>>>> In <1148296300.206613.52570@38g2000cwa.googlegroups.com>
>>>>>	google@mirror.to wrote:

> I recently upgraded to No Gnus 0.4 from Debian,
> under XEmacs 21.4 patch 17 Jumbo Shrimp,
> and cid rendering seems to have stopped working.

> It's possible I changed something in .gnus, but I don't think so...

> Here's what seems like it might be relavent:

Well, I found nothing to stop the cid rendering there.  Actually
I tried Gnus v0.4 and your configuration, and could see images
which have been embedded as cid urls in some html messages.  I
think there may be another cause.  For instance, your XEmacs has
been built with no image libraries, there are no contents
related to a cid tag within a message, etc.

> (setq mm-automatic-display
>       '(
>         "application/pgp-signature"
>         "image/gif"
>         "image/jpeg"
>         "image/png"
>         "message/delivery-status"
>         "message/rfc822"
>         "multipart/related"
>         "multipart/mixed"
>         "text/enriched"
>         "text/html"
>         "text/richtext"
>                          ))

Although there's no problem if you are sure what you do, using
`setq' to set such a list variable might let you overlook some
significant elements that have been added in the new Gnus
release (it is a basic problem that will happen when using `M-x
customize-option' as well, though).  A better way to do that
seems to be the use of `add-to-list' and/or `remove'.

> (setq mm-discouraged-alternatives
>       '("text/html"
>         "text/richtext"))
> (add-to-list 'mm-inlined-types "message/rfc822")
> (setq mm-inline-large-images 'T)
> (setq mm-inline-text-html-with-images 'T)
> (setq mm-w3m-safe-url-regexp 'nil)
> (setq mm-text-html-renderer 'w3m)
> (setq w3m-default-display-inline-images 'T)
> (setq w3m-display-inline-image 'T)

> I had to set mm-w3m-safe-url-regexp to nil to make cid's render before
> I upgraded. Despite what the manual said, under the previous debian
> gnus rev,
> if I left it alone, cid's didn't work, and when I flipped it to nil,
> they did...

I don't think what you are talking about is cid.  As far as I
know, cid tags are used to point contents which are embedded in
messages themselves as MIME parts.  Contents being able to be
displayed by setting `mm-w3m-safe-url-regexp' to nil are
external links, such as http tags.

Re: cid problems

[google]

Thanks for the add-to-list suggestion.

The mm-w3m-safe-url-regexp documentation says that it's default value
contains cid, so I figured it was relavent.

I did figure out the problem; while the cid attachments in fact were
gif's and jpeg's, for some reason when the mime message was created
(not by gnus) they got set to a mime type of shockwave.

  --cheers
  --akb