From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gnus-registry question
Date: Wed, 19 Nov 2003 16:06:33 -0500 [thread overview]
Message-ID: <4n7k1wdq5i.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76fzgrnktz.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 14 Nov 2003 08:25:28 -0500")
On Fri, 14 Nov 2003, colman@ppllc.com wrote:
> I did find a situation where it is broken. I have a folder where
> the gcc is set to archive the message into the same folder. I used
> 'C-u a' to send a message using that folder's attributes. I made a
> point of NOT opening that folder again. When I next split my mail
> after I had received a reply the reply message did NOT get filed
> correctly. I then moved the reply message back to my INBOX and
> tried again. This time, too, it was misfiled. I again copied the
> message back to my INBOX. This time, however, I opened up the
> folder where my initial emial was filed and read that email. This
> registered my original with the registry. When I now tried
> splitting, the reply was filed correctly.
Turn up gnus-verbose, and send me the message log when this happens.
I think what you're saying is that a GCC does not automatically send
replies to that message to a folder. I'll see what I can do to fix
that, and I'll try to duplicate the problem, but your message log
will be very helpful regardless.
Thanks
Ted
next prev parent reply other threads:[~2003-11-19 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 21:41 Jake Colman
2003-11-12 22:04 ` Ted Zlatanov
2003-11-14 13:25 ` Jake Colman
2003-11-19 21:06 ` Ted Zlatanov [this message]
2003-11-12 23:07 ` Danny Siu
2003-11-13 15:50 ` Jake Colman
2003-11-13 16:57 ` Ted Zlatanov
2003-11-13 19:13 ` Raymond Scholz
2003-11-13 19:49 ` Danny Siu
2003-11-19 21:01 ` gnus-registry-ignored-groups (was: gnus-registry question) 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=4n7k1wdq5i.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).