From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: where do messages from daemons go?
Date: Fri, 01 Dec 2006 15:59:58 +0000 [thread overview]
Message-ID: <g69bqmn38u9.fsf@lifelogs.com> (raw)
In-Reply-To: <87odqnbput.fsf@patagonia.sebmags.homelinux.org> (Sebastian P. Luque's message of "Fri\, 01 Dec 2006 09\:25\:14 -0600")
On 1 Dec 2006, spluque@gmail.com wrote:
> I had activated a daemon to collect mail for some time by including this
> in ~/.gnus.el:
>
>
> (gnus-demon-add-handler 'gnus-demon-scan-mail 720 nil)
>
>
> and could verify that messages were being collected, as a short notice was
> appearing briefly in the minibuffer and can see the corresponding files
> with names like "Incoming160267qk" being created. However, the messages
> do not appear in any of my groups, although a "%" appears next to the
> groups were they should be. Entering those groups in any way doesn't show
> the new messages. These messages do not seem to go to the bogus group
> neither. Can somebody please point out what might be going on? Thanks in
> advance.
So M-g on a % group doesn't change the article counts?
Check the *Messages* buffer, there may be some information there.
Looks to me like gnus-demon-scan-mail in gnus-demon.el doesn't do
anything unusual:
(defun gnus-demon-scan-mail ()
(save-window-excursion
(let ((servers gnus-opened-servers)
server
(nnmail-fetched-sources (list t)))
(while (setq server (car (pop servers)))
(and (gnus-check-backend-function 'request-scan (car server))
(or (gnus-server-opened server)
(gnus-open-server server))
(gnus-request-scan nil server))))))
Ted
next prev parent reply other threads:[~2006-12-01 15:59 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 [this message]
2006-12-01 17:15 ` Sebastian P. Luque
2006-12-01 18:09 ` Ted Zlatanov
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=g69bqmn38u9.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).