From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: where do messages from daemons go?
Date: Fri, 01 Dec 2006 18:09:32 +0000 [thread overview]
Message-ID: <g69k61b1o9v.fsf@lifelogs.com> (raw)
In-Reply-To: <87k61bh70w.fsf@patagonia.sebmags.homelinux.org> (Sebastian P. Luque's message of "Fri\, 01 Dec 2006 11\:15\:27 -0600")
On 1 Dec 2006, spluque@gmail.com wrote:
> On Fri, 01 Dec 2006 15:59:58 +0000,
> Ted Zlatanov <tzz@lifelogs.com> wrote:
>
> [...]
>
>> So M-g on a % group doesn't change the article counts?
>
>> Check the *Messages* buffer, there may be some information there.
>
> Thank you Ted. I noticed these lines in that buffer:
>
>
> nnfolder: Reading incoming mail from file... [3 times]
> spam-split: calling the spam-check-bogofilter function [2 times]
> Saving file /home/sluque/News/sent/mail/misc...
> Wrote /home/sluque/News/sent/mail/misc
> nnfolder: Reading incoming mail (2 new)...done
>
>
> I verified that all these messages were getting sent to the
> /home/sluque/News/sent/mail/misc file, but this doesn't explain why the
> groups where they should've gone were being marked "%". I have the
> following to set the different places where messages should go:
>
>
> (setq message-directory "~/News/mail"
> mail-source-directory "~/News/mail"
> ;; how and where to store sent messages
> gnus-message-archive-method
> '(nnfolder "archive"
> (nnfolder-inhibit-expiry t)
> (nnfolder-get-new-mail nil)
> (nnfolder-active-file "~/News/sent/active")
> (nnfolder-directory "~/News/sent/"))
> ;; sort sent mail and news into different groups
> gnus-message-archive-group
> '((if (message-news-p)
> "sent-news"
> (concat "sent-" (format-time-string "%m-%Y"))))
> message-auto-save-directory "~/News/drafts")
>
>
> so I don't understand how those messages ended up as nnfolder. Any
> further ideas most welcome.
I don't know much about this functionality, so I can't answer your
question well. I use IMAP and NNTP mostly, so I haven't had to use
nnfolder delivery options as you do. My guess is that
gnus-request-scan, which is called by gnus-demon-scan-mail directly,
is wrapped by lots of other code when you use `g'
(gnus-group-get-new-news in gnus-group.el). gnus-group-get-new-news
is huge and runs hooks, etc.
Ted
next prev parent reply other threads:[~2006-12-01 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 15:25 Sebastian P. Luque
2006-12-01 15:59 ` Ted Zlatanov
2006-12-01 17:15 ` Sebastian P. Luque
2006-12-01 18:09 ` Ted Zlatanov [this message]
2006-12-01 18:28 ` Sebastian P. Luque
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=g69k61b1o9v.fsf@lifelogs.com \
--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).