From: "Sebastian P. Luque" <spluque@gmail.com>
Subject: Re: where do messages from daemons go?
Date: Fri, 01 Dec 2006 12:28:28 -0600 [thread overview]
Message-ID: <877ixbh3n7.fsf@patagonia.sebmags.homelinux.org> (raw)
In-Reply-To: <g69k61b1o9v.fsf@lifelogs.com>
On Fri, 01 Dec 2006 18:09:32 +0000,
Ted Zlatanov <tzz@lifelogs.com> wrote:
[...]
> 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.
Thanks. I'll probably abandon using this demon and just let fetchmail
collect the mail in /var/mail/myuser until I retrieve it manually with 'g'
into gnus.
Could somebody please suggest how to recover the "lost" incoming messages
that ended up in /home/sluque/News/sent/mail/misc ? Thanks again.
--
Seb
prev parent reply other threads:[~2006-12-01 18:28 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
2006-12-01 18:28 ` Sebastian P. Luque [this message]
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=877ixbh3n7.fsf@patagonia.sebmags.homelinux.org \
--to=spluque@gmail.com \
/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).