From: Tassilo Horn <tassilo@member.fsf.org>
To: notmuch@notmuchmail.org
Subject: Notmuch doesn't index new mails when mail location contains symlinks (was: Notmuch doesn't index new mails)
Date: Mon, 23 Nov 2009 14:55:40 +0100 [thread overview]
Message-ID: <87einpl50j.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87ws1hldmu.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Mon, 23 Nov 2009 11:49:29 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
Hi all,
I've investigated a bit further.
> [notmuch doesn't index new mails although all directories and files
> are readable and writable.]
In my config, I have:
--8<---------------cut here---------------start------------->8---
[database]
path=/home/horn/Mail/Dovecot
--8<---------------cut here---------------end--------------->8---
In that directory, there are two symlinks pointing to the real mail
location in /var/spool/mail:
--8<---------------cut here---------------start------------->8---
[horn@localhost][~/Mail/Dovecot][0][5213]
[:)] % ll
total 0
lrwxrwxrwx 1 horn horn 34 Nov 23 14:49 fastmail -> /var/spool/mail/fastmail/mailboxes
lrwxrwxrwx 1 horn horn 29 Nov 23 14:49 uni -> /var/spool/mail/uni/mailboxes
--8<---------------cut here---------------end--------------->8---
Whenever I delete those symlinks and created them anew, the new mails
get indexed with the next "notmuch new". Of course, I could create a
script that does exactly that, but there should be a better way, right?
Bye,
Tassilo
next prev parent reply other threads:[~2009-11-23 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 10:49 Notmuch doesn't index new mails Tassilo Horn
2009-11-23 13:55 ` Tassilo Horn [this message]
2009-11-23 14:02 ` Notmuch doesn't index new mails when mail location contains symlinks Mikhail Gusarov
2009-11-23 14:43 ` Tassilo Horn
2009-11-23 15:01 ` Tassilo Horn
2009-11-23 15:10 ` Mikhail Gusarov
2009-11-23 15:16 ` Jed Brown
2009-11-23 15:03 ` Jed Brown
2009-11-23 15:11 ` Mikhail Gusarov
2009-11-26 18:34 ` Carl Worth
2009-11-26 18:39 ` Jed Brown
2009-11-26 21:14 ` Carl Worth
2009-11-26 21:22 ` Jed Brown
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87einpl50j.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).