Changing summary mode "to" field

Changing summary mode "to" field

[Han Pilmeyer]

Hi,

I remember from my "before Gnus" days that I used a mailer that would
say something like "To:<to-address>" instead of showing the mail was
from me (in cases where the mail originated from me). This was very
usefull specially in mail archives where everything now just shows that
it's "from me", something I knew already.

Does anyone know if Gnus can be customized to do something similar in
summary mode?

Cheers.
-- 
Han Pilmeyer, han@uto.dec.com, Phone: +31 30 2832671, FAX: +31 30 2832686
Digital Equipment B.V., Europalaan 44, 3526 KS Utrecht, The Netherlands
|         Answers are the easy part, questions raise the doubt   -JB          |
All opinions are those of the author, not of Digital Equipment!

Re: Changing summary mode "to" field

[Kai Grossjohann]

>>>>> Han Pilmeyer writes:

  Han> I remember from my "before Gnus" days that I used a mailer that
  Han> would say something like "To:<to-address>" instead of showing
  Han> the mail was from me (in cases where the mail originated from
  Han> me). [...]

This is difficult to do in Gnus because the from address is stored in
the overview data and thus the summary buffer can be generated from
the overview data alone.  Would one do something like this, one would
have to read all the articles or extend the overview format.

AFAIK.

kai
-- 
I wonder why nobody don't like me,
or is it de fact dat I'm ugly? -- Harry Belafonte

Re: Changing summary mode "to" field

[Sten Drescher]

>>>>> Kai Grossjohann writes:

>>>>> Han Pilmeyer writes:
Han> I remember from my "before Gnus" days that I used a mailer that
Han> would say something like "To:<to-address>" instead of showing the
Han> mail was from me (in cases where the mail originated from
Han> me). [...]

KG> This is difficult to do in Gnus because the from address is stored
KG> in the overview data and thus the summary buffer can be generated
KG> from the overview data alone.  Would one do something like this,
KG> one would have to read all the articles or extend the overview
KG> format.

	I'd suggest extending/modifying the overview format slightly.
When the From: header of the article matches a regexp (say,
"*stend*@*(tivoli.com|texas.net)*"), instead of storing the From:
information store the To: header, including "To:", in the address
field of the overview data for the article.  Since this departs from
the standard overview format, make it selectable (perhaps
nnmail-store-to-address, defaulting to nil, with the regexp being
nnmail-store-to-address-regexp?).

-- 
+----------------------  Tivoli Customer Support  ----------------------+
|   Sten Drescher                     Tivoli Systems, Inc               |
|   email: sten.drescher@tivoli.com   9442 Capital of Texas Hwy North   |
|   phone: (512) 794-9070             Arboretum Plaza One, Suite 500    |
|   fax  : (512) 345-2784             Austin, Texas 78759               |
+-----------------------------------------------------------------------+

Re: Changing summary mode "to" field

[Per Abrahamsen]

>>>>> "SD" == Sten Drescher <sten.drescher@tivoli.com> writes:

SD> 	I'd suggest extending/modifying the overview format slightly.

The overview format already allows you to store arbitrary headers.
I'd suggest simply storing the To header as well as the (mandatory)
>From header.  

Perhaps there should be a variable controlling which headers are
stored, say 

(defcustom nnml-extra-nov-headers '("xref")
   "List of optional header fields to store in the NOV files."
   :type '(repeat string)
   :group 'gnus-mail)

Obviously we'd need primitives to extract the optional headers, and
add support for them at reasonable places like scoring and the summary
line format.

If you are on friendly terms with the news administrator, maybe he
will add newsgroups to the nov format file.  Then you can
(efficiently) increase the score of Gnus users, and decrease the score
of MS News users.

Re: Changing summary mode "to" field

[Lars Balker Rasmussen]

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> If you are on friendly terms with the news administrator, maybe he
> will add newsgroups to the nov format file.  Then you can
> (efficiently) increase the score of Gnus users, and decrease the score
> of MS News users.

YM X-Newsreader, HTH?
-- 
Lars Balker Rasmussen                   <URL:http://www.daimi.aau.dk/~gnort/>

Re: Changing summary mode "to" field

[Karl Kleinpaste]

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> (defcustom nnml-extra-nov-headers '("xref")
>    "List of optional header fields to store in the NOV files."
>    :type '(repeat string)
>    :group 'gnus-mail)

> Obviously we'd need primitives to extract the optional headers, and
> add support for them at reasonable places like scoring and the summary
> line format.

I'm doing exactly that for the sake of (particularly) Keywords:
headers, with generalization to others.  My reason for doing this is
to get small bits of body content into news servers' overview files
(in Keywords:), so as to be scorable, in the hope of improving
conversation-tracking beyond what you get with References: ties (which
may hold things together too long) and Subject: (which doesn't change
nearly often enough in busy groups).  I've got some heuristics for
auto-generation of the keywords themselves, plus a Gnus interface hook
to make it work.  What I will be doing this week or next is writing
these primitives, to get the info back from the server, and to score
on them.

(I exchanged a note or two with Lars about this a couple weeks ago.)

> If you are on friendly terms with the news administrator, maybe he
> will add newsgroups to the nov format file.

No, that won't help in the general case right now, at least under INN.
Your news system will start complaining:

Nov 12 15:07:20 pocari-sweat innd: SERVER bad_schema unknown header "Keywords"

It seems that INN is excessively picky about what shows up in
overview.fmt.  As it happens, because I'm doing this work, I've sent a
patch for inn1.5b2 to the maintainer to take care of this, and he has
agreed that it will apear in inn1.5final, possibly generalized so as
not to be so picky in the 1st place.

(This message will have a Keywords: header present using my new module
messkeyw.el.  It's a very simple-minded but useful algorithm that does
little more than count words and take the highest occurrences.)

Re: Changing summary mode "to" field

[Lars Magne Ingebrigtsen]

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

> Obviously we'd need primitives to extract the optional headers, and
> add support for them at reasonable places like scoring and the summary
> line format.

The trick is adding stuff like this without making things go slower
for people who don't want it.  I'm making headway, though -- things
may (or may not) be happening soonish.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen