gnus-summary-mail-forward - included headers

gnus-summary-mail-forward - included headers

[Thomas Hungenberg]

Hello!

I'm using PGnus 0.95 and I wonder if it is possible to set the
header-lines which should be included when doing a
"gnus-summary-mail-forward" of a news article in any variable.
I don't like header-lines like "Lines:" to be included in the
forwarded message.


      - Thomas

-- 
Thomas Hungenberg -- Student of Applied Computer Science
Private homepage: http://home.pages.de/~th/ -- ICQ-UIN: #3294439
PGP encrypted mail welcome! -- PGP-Public-Key on my homepage!

Re: gnus-summary-mail-forward - included headers

[Matt Pharr]

Dan Christensen <jdc@jhu.edu> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> > 
> > > Trimming the headers by hand is a pain, and would be better if
> > > automated, as it was before.
> > 
> > I've now added message-ignored-forward-headers.
> 
> I don't see this in the source or in the documentation, although
> I do see a Changelog entry.  What's up?

Actually, it's "message-forward-ignored-headers"

-matt
-- 
Matt Pharr                                   mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>

Re: gnus-summary-mail-forward - included headers

[Dan Christensen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> 
> > Trimming the headers by hand is a pain, and would be better if
> > automated, as it was before.
> 
> I've now added message-ignored-forward-headers.

I don't see this in the source or in the documentation, although
I do see a Changelog entry.  What's up?

Dan

-- 
Dan Christensen
jdc@math.jhu.edu

Re: gnus-summary-mail-forward - included headers

[Lars Magne Ingebrigtsen]

François Pinard <pinard@iro.umontreal.ca> writes:

> I did not resend `fp-mml.el' to this group, as it did not change in a
> while, but just ask if you want to peek at it.  Or maybe I should just
> put it somewhere for people to `wget'?

Please do post it again -- I think I must have missed it the first
time around.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: gnus-summary-mail-forward - included headers

[Hrvoje Niksic]

François Pinard <pinard@iro.umontreal.ca> writes:

> I did not resend `fp-mml.el' to this group, as it did not change in
> a while, but just ask if you want to peek at it.  Or maybe I should
> just put it somewhere for people to `wget'?

Please do.  I'd like to try it under XEmacs.

I added the support for indirect buffers to XEmacs, but they've never
been tested extensively because I know of no application that actually
uses them.  I'd love to see one.

Re: gnus-summary-mail-forward - included headers

[Kai Großjohann]

François Pinard <pinard@iro.umontreal.ca> writes:

> [...]  Or maybe I should just put it somewhere for people to `wget'?

Yes, please.  I always wanted to try it, but I was swamped...

kai
-- 
Life is hard and then you die.

Re: gnus-summary-mail-forward - included headers

[François Pinard]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > On a related note, what's the best way to narrow to the current part
> > after inserting a message/rfc822?

> I've now added a keystroke for doing this to the MML keymap, but I
> haven't written the command.  :-)

By the way, in my little `fp-mml.el' exercise, I have a function for that:

(defun fp-mml-edit-current-part ()
  "Setup an indirect buffer to edit the MML part containing point."

I did not resend `fp-mml.el' to this group, as it did not change in a
while, but just ask if you want to peek at it.  Or maybe I should just
put it somewhere for people to `wget'?

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard

Re: gnus-summary-mail-forward - included headers

[Lars Magne Ingebrigtsen]

Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:

> Trimming the headers by hand is a pain, and would be better if
> automated, as it was before.

I've now added message-ignored-forward-headers.

> On a related note, what's the best way to narrow to the current part
> after inserting a message/rfc822?

I've now added a keystroke for doing this to the MML keymap, but I
haven't written the command.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: gnus-summary-mail-forward - included headers

[Toby Speight]

Kai> Kai Großjohann <URL:mailto:Kai.Grossjohann@CS.Uni-Dortmund.DE>

0> In article <vafemg18mi1.fsf@lucy.cs.uni-dortmund.de>, Kai wrote:

Kai> Jim Davidson <jim.davidson@liberate.com> writes:

>> In PGnus, this has been modified.  The argument has been renamed to
>> not-used, and is ignored.  All the headers are included in the
>> forward message.  I much preferred the former behavior.

Kai> Well, pgnus now does MIME forwards.  And that means that the
Kai> remote client is explicitly told that the attachment is an RFC822
Kai> message.  And presumably a mail reader is capable of displaying
Kai> mail messages in a meaningful way (including hiding some headers,
Kai> if so desired).

For me, that isn't the issue.  I'd prefer the default not to include
stuff like "Path", "X-Gnus-Mail-Source" and "Xref" (call me paranoid,
if you like) and I think that the likes of "X-From-Line", "X-From_",
"Envelope-to" and "Delivery-date" (added by the mail delivery agent)
and probably also "Received" are a waste of space, except if you are
debugging message delivery problems.

Trimming the headers by hand is a pain, and would be better if
automated, as it was before.


On a related note, what's the best way to narrow to the current part
after inserting a message/rfc822?  I have the following to submit
articles to alt.humor.best-of-usenet:

(defun gnus-summary-forward-to-abhou nil
  (interactive)
  (let ((message-mode-hook '(my-message-mode-hook)))
    (gnus-summary-post-forward)
    (message-goto-newsgroups)
    (insert "alt.humor.best-of-usenet")
    (and (search-forward mail-header-separator nil t)
         (let ((start (point-marker))
               (end (copy-marker (point-max) t)))
           (message-strip-pgp-sig start end)
           (message-strip-sigfile start end)
           (nuke-trailing-blanks-in-region start end)))
    (set (make-local-variable 'gnus-check-before-posting)
         '(control-chars multiple-headers))
    (set (make-local-variable 'message-syntax-checks)
         '((long-lines . disabled)))))

(defun message-strip-sigfile (start end)
  (interactive "*r")
  (goto-char end)
  ;; first remove trailing blank lines
  (skip-syntax-backward "-")
  (let ((sig-end (point))
        (sig-start (re-search-backward "\n-- *\n" start t)))
    (when (and sig-start
               (<= (count-lines sig-start sig-end) 6) ; 4-line sigblock + "\n-- \n" (2 lines)
               (y-or-n-p "Strip signature? "))
      (undo-boundary)
      (delete-region sig-start end))))


(defun message-strip-pgp-sig (start end)
  (interactive "*r")
  (goto-char start)
  (while (re-search-forward "^---*BEGIN PGP \\([A-Z ]*\\)--*\n+" end t)
        (cond ((string= "SIGNATURE" (match-string 1))
               (let ((sig-start (match-beginning 0))
                     (sig-end (or (search-forward "\n-----END PGP SIGNATURE-----" end t) end)))
                 (delete-region sig-start sig-end)))
              ((string= "SIGNED MESSAGE" (match-string 1))
               (let ((header-start (match-beginning 0))
                     (header-end (match-end 0))
                     (signed-region-end (or (search-forward "\n--" end t) end)))
                 (goto-char header-end)
                 (while (search-forward "\n- " signed-region-end t)
                   (replace-match "\n"))
                 (delete-region header-start header-end)))
              (t
               (delete-region (match-beginning 0) (match-end 0))))))

(defun nuke-trailing-blanks-in-buffer nil
  (interactive "*")
  (nuke-trailing-blanks-in-region (point-min) (point-max)))
(defun nuke-trailing-blanks-in-region (start end)
  (interactive "*r")
  (save-excursion
    (goto-char start)
    (while (re-search-forward "[ \t]+$" end t)
      (replace-match "" t t))))


but of course, message-strip-sigfile tears off the part's end-tag.

Re: gnus-summary-mail-forward - included headers

[Kai Großjohann]

Jim Davidson <jim.davidson@liberate.com> writes:

> In PGnus, this has been modified.  The argument has been renamed to
> not-used, and is ignored.  All the headers are included in the
> forward message.  I much preferred the former behavior.

Well, pgnus now does MIME forwards.  And that means that the remote
client is explicitly told that the attachment is an RFC822 message.
And presumably a mail reader is capable of displaying mail messages in
a meaningful way (including hiding some headers, if so desired).

We know that very few mailers are really *good* programs and grok MIME
the way MIME was meant to be grokked.  But one can dream...

kai
-- 
I like BOTH kinds of music.

gnus-summary-mail-forward - included headers

[Jim Davidson]

Thomas Hungenberg <th@demonium.de> writes:

> I'm using PGnus 0.95 and I wonder if it is possible to set the
> header-lines which should be included when doing a
> "gnus-summary-mail-forward" of a news article in any variable.
> I don't like header-lines like "Lines:" to be included in the
> forwarded message.

I agree.  In the released version of Gnus, the function
gnus-summary-mail-forward takes a first argument, full-headers, which
indicates whether to forward all the headers.

In PGnus, this has been modified.  The argument has been renamed to not-used,
and is ignored.  All the headers are included in the forward message.  I much
preferred the former behavior.

-Jim