Mail digest and MIME headers

Mail digest and MIME headers

[Per Abrahamsen]

Why does "gnus-uu-digest-mail-forward" insert 

        MIME-Version: 1.0
        Content-Type: text/plain; charset=us-ascii

in each digested message?  This is the default content type, so there
should be no reason to insert the headers.

Re: Mail digest and MIME headers

[ShengHuo ZHU]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Why does "gnus-uu-digest-mail-forward" insert 
> 
>         MIME-Version: 1.0
>         Content-Type: text/plain; charset=us-ascii
> 
> in each digested message?  This is the default content type, so there
> should be no reason to insert the headers.

Fixed.

ShengHuo

-- 
(setq gnus-posting-styles '((".*" (signature-file "~/.signature"))))

Re: Mail digest and MIME headers

[Per Abrahamsen]

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 
> > Why does "gnus-uu-digest-mail-forward" insert 
> > 
> >         MIME-Version: 1.0
> >         Content-Type: text/plain; charset=us-ascii
> > 
> > in each digested message?  This is the default content type, so there
> > should be no reason to insert the headers.
> 
> Fixed.

Thanks, but does it has to add the MIME-version header?  When there is
no other MIME headers?

I also found a problem with the first "Topics" entry, there is an
empty line before the "Subject: " header which makes it part of the
body, instead of part of the header.  This patch fixes that:

2001-02-06  Per Abrahamsen  <abraham@dina.kvl.dk>

	* gnus-uu.el (gnus-uu-save-article): Make the topics summary a
	message/rfc822.

Index: gnus-uu.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-uu.el,v
retrieving revision 6.2
diff -c -r6.2 gnus-uu.el
*** gnus-uu.el	2000/12/28 17:44:20	6.2
--- gnus-uu.el	2001/02/06 22:35:10
***************
*** 886,892 ****
  	      (when (and message-forward-as-mime gnus-uu-digest-buffer)
  		;; The default part in multipart/digest is message/rfc822.
  		;; Subject is a fake head.
! 		(insert "

[-- Attachment #2: Type: text/plain, Size: 317 bytes --]

\nSubject: Topics\n\n"))
  	      (insert "Topics:\n")))
  	(when (not (eq in-state 'end))
  	  (setq state (list 'middle))))
--- 886,892 ----
  	      (when (and message-forward-as-mime gnus-uu-digest-buffer)
  		;; The default part in multipart/digest is message/rfc822.
  		;; Subject is a fake head.
! 		(insert "

[-- Attachment #3: Type: message/rfc822, Size: 144 bytes --]

Re: Mail digest and MIME headers

[Russ Allbery]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Thanks, but does it has to add the MIME-version header?  When there is
> no other MIME headers?

It's not strictly necessary, but it does say to other MUAs that you're
guaranteeing that they can assume all of the standard defaults for the
other MIME parameters, whereas if you leave off MIME-Version you're saying
that the message may not comply with MIME and could be in an unknown
character set.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

Re: Mail digest and MIME headers

[Per Abrahamsen]

Russ Allbery <rra@stanford.edu> writes:

> It's not strictly necessary, but it does say to other MUAs that you're
> guaranteeing that they can assume all of the standard defaults for the
> other MIME parameters, whereas if you leave off MIME-Version you're saying
> that the message may not comply with MIME and could be in an unknown
> character set.

Does this reasoning apply to nested messages, such as messages within
MIME digests?  

For a top-level message, I agree it is a good tradeoff, because
unknown headers are hidden by most agents, even those that are not
MIME aware.

Re: Mail digest and MIME headers

[Russ Allbery]

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Russ Allbery <rra@stanford.edu> writes:

>> It's not strictly necessary, but it does say to other MUAs that you're
>> guaranteeing that they can assume all of the standard defaults for the
>> other MIME parameters, whereas if you leave off MIME-Version you're
>> saying that the message may not comply with MIME and could be in an
>> unknown character set.

> Does this reasoning apply to nested messages, such as messages within
> MIME digests?  

I'm fairly sure not.  Good point.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

Re: Mail digest and MIME headers

[ShengHuo ZHU]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > Per Abrahamsen <abraham@dina.kvl.dk> writes:
> > 
> > > Why does "gnus-uu-digest-mail-forward" insert 
> > > 
> > >         MIME-Version: 1.0
> > >         Content-Type: text/plain; charset=us-ascii
> > > 
> > > in each digested message?  This is the default content type, so there
> > > should be no reason to insert the headers.
> > 
> > Fixed.
> 
> Thanks, but does it has to add the MIME-version header?  When there is
> no other MIME headers?
> 
> I also found a problem with the first "Topics" entry, there is an
> empty line before the "Subject: " header which makes it part of the
> body, instead of part of the header.  This patch fixes that:
> 
> 2001-02-06  Per Abrahamsen  <abraham@dina.kvl.dk>
> 
> 	* gnus-uu.el (gnus-uu-save-article): Make the topics summary a
> 	message/rfc822.

This patch is munged because of the mml tags.  Could you resent the
patch as an attachment?

ShengHuo

-- 
(setq gnus-posting-styles '((".*" (signature-file "~/.signature"))))

Re: Mail digest and MIME headers

[Per Abrahamsen]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> This patch is munged because of the mml tags.  Could you resent the
> patch as an attachment?

I just committed it, hope that is ok.