Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Jake Colman <colman@ppllc.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Problems with gnus-registry
Date: Wed, 06 Feb 2008 08:21:52 -0600	[thread overview]
Message-ID: <868x1yp3lr.fsf@lifelogs.com> (raw)
In-Reply-To: <76y79zkpnx.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Tue, 05 Feb 2008 17:24:18 -0500")

On Tue, 05 Feb 2008 17:24:18 -0500 Jake Colman <colman@ppllc.com> wrote: 

Jake> So with a gcc, when the backend causes the sent article to spool to the
Jake> gcc-ed folder, the registry will register that article.  This will work for
Jake> sent emails as well since it is the gcc that will make the registry see it.
Jake> Is this all correct?

Yes, that's how it's supposed to work.

TZ> You can set your archive group to be ignored, see
TZ> gnus-registry-ignored-groups.

Jake> My archive group is defined through the following code:

Jake>   (setq gnus-message-archive-group
Jake>         '((concat "nnimap+hamilton:Archive/" 
Jake>                   (format-time-string "%Y-%m" (current-time)))))

Jake> How can I set gnus-registry-ignored-groups so that I don't have my replies
Jake> registered to the archive (in the absence of any overriding gcc of
Jake> course).

Sorry, I gave you the wrong variable name.  This is the right one with
the default value:

(setq gnus-registry-unfollowed-groups 
 '("delayed$" "drafts$" "queue$" "INBOX$"))

It means "any group ending with one of these words" ($ at the end means
"the string must end here", so "INBOX.hello" won't match the last one
for example).

So, depending on whether you want to keep the default, you can add
"Archive/" to the list (so anything with that word in it not be followed
for splitting).

If you have other groups with "Archive/" in the name, the regular
expression can be more precise to allow only the one above.  I would
keep things simple if possible.

TZ> - subject and sender tracking is experimental and works OK for me, but
TZ> you may discover bugs

TZ> - multiple matches for a subject or a sender will disqualify the match,
TZ> to avoid ambiguous results

Jake> How can I test if that is what's going on?

Jake> It is pretty clear that some of my emails are coming in without the standard
Jake> headers that the registry is looking for.  But one would think that sender
Jake> and subject would always be found!  I'd love to help shake this out for you
Jake> that I can get more of my emails handled by the registry.

The sender and the subject are in the registry as extra data, e.g.

("<47A802B8.6080400@gna.org>" ((mtime 18344 55485 405961) (sender . "\"Suraj N. Kurapati\" <snk@gna.org>") (subject . "[wmii] [ANN] Rumai 2.0.0")) "nnimap+blockstar.com:INBOX.ion")

This entry says:

message ID is first entry

extra data:
 mtime is creation/update date
 sender and subject are as shown

group name is any string after the message ID

So to see if a subject matches multiple groups, you need to:

1) enter a group with a message you're interested in, to make sure it's
in the registry.  Note the message ID, subject, and sender.

2) (after saving to make sure the file contains the latest data)

"grep subject ~/.gnus.registry.eld | grep YOUR_SUBJECT_HERE"

Same as above for the sender.  If multiple entries match, none will be
returned.  If no entries match, we'll need to do more debugging on why
that's happened; grep the registry file for the message ID as well, and
I'll need to see that message.

I will write functions to do the above directly through the registry to
make debugging easier, but for the time being stick with grep.

Ted




  reply	other threads:[~2008-02-06 14:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:21 Jake Colman
2008-02-01 20:57 ` Ted Zlatanov
2008-02-04 13:38   ` Jake Colman
2008-02-04 21:03     ` Ted Zlatanov
     [not found]       ` <76y7a0nyo3.fsf@dev-d01.ppllc.com>
     [not found]         ` <86lk60uwwq.fsf@lifelogs.com>
     [not found]           ` <764pconmz4.fsf@dev-d01.ppllc.com>
2008-02-05 15:15             ` Ted Zlatanov
2008-02-05 21:51               ` Jake Colman
2008-02-05 22:15                 ` Ted Zlatanov
2008-02-05 22:24                   ` Jake Colman
2008-02-06 14:21                     ` Ted Zlatanov [this message]
2008-02-06 16:54                       ` Jake Colman
2008-02-06 17:31                         ` Ted Zlatanov
2008-02-07 15:42                           ` Jake Colman
2008-02-06 20:05                       ` Reiner Steib
2008-02-07 15:43                         ` Ted Zlatanov
2008-02-07 17:29                           ` Reiner Steib
2008-02-08 11:58                             ` David
2008-02-14 17:51                               ` Ted Zlatanov
2008-02-28 15:01                                 ` Ted Zlatanov
2008-02-28 15:53                                   ` David
2008-02-14 17:45                             ` Ted Zlatanov
2008-02-28 15:03                               ` Ted Zlatanov

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=868x1yp3lr.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=colman@ppllc.com \
    --cc=ding@gnus.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).