From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: David Mazieres expires 2015-11-28 PST
<mazieres-evmnkzzavjvnrbsbughkgbywbs@temporary-address.scs.stanford.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: muchsync files renames
Date: Mon, 31 Aug 2015 12:59:43 +0100 [thread overview]
Message-ID: <87k2sbmzww.fsf@freja.aidecoe.name> (raw)
In-Reply-To: <87io7wr50y.fsf@ta.scs.stanford.edu>
[-- Attachment #1: Type: text/plain, Size: 3011 bytes --]
Hi David,
First of all thank you a lot for support. I am Cc'ing ml because the
last paragraph may be useful hint for other users.
David Mazieres writes:
> So to be clear, you are getting tons of lines that start "[SERVER]
> [notmuch]" and contain the string "Ignoring non-mail file"? Is the
> "##...##" literal, or is that an ellipsis?
I have just cut off few directories on the path. :-) All of these files
are invalid spam mail, indeed. I have removed them. One problem less.
> Also, those file names were not generated were not generated by
> muchsync. Any mail file created by muchsync will have a file name of
> the form:
>
> nnn.MnnnPnnnQnRn.machine
> nnn.MnnnPnnnQnRn.machine:2,
Just to makes things clear (once again? :-)), these file names are
generated only on client side. Muchsync is not gonna ever to sync file
names to server, is it?
> When you run "notmuch new" on the server, without muchsync, does it
> take forever and print all these message while scanning non mail
> files?
No. Notmuch doesn't print these messages when I just run "notmuch new"
myself. Anyway there was only around 100 of invalid mail files.
> Okay, this is the interesting part. It appears that 5775 out of your
> 115877 messages have been moved to a different directory on the
> client. I notice that the one message you include above has been
> moved to the Spam maildir.
> Is it possible that A) you have some spam filtering on the client that
> is moving things to the Spam folder,
I have a mailfilter rule which moves mails with "X-Spam-Status: Yes" to
Spam directory, but this happens on delivery before notmuch indexing.
> or B) that one of your two machines is using a case-independent file
> system that is causing confusion between "Spam" and "spam"?
I am testing it on single GNU/Linux host between different users. It is
ext4 fs.
> So... based on all the evidence so fare the culprit seems to be that
> something is moving mail files into your Spam folder on the client.
> If that rings any bells and solves the problem, great. If not, here
> is what we need to do to track it down further.
I have followed you hints to track down the issue. All of these
messages are spam. What I suspect follows.
All of these files have been placed to new/ subdir by maildrop and
during posthook (afew) have been stripped of any tags besides 'spam'
tag, in particular 'unread' tag has been removed, but files still remain
in new/ subdir. So... what had to happen is that during muchsync these
messages have been discovered as already read, so they don't belong to
new/ but must be moved to cur/. And this is what happened on client
side. During next muchsync these changes had to be pushed to server,
i.e. move from new/ to cur/.
So if my assumptions are correct, actually there is no issue! I would
just have to adjust afew filtering to prevent this behaviour.
Thank you,
--
Amadeusz Żołnowski
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 950 bytes --]
next prev parent reply other threads:[~2015-08-31 12:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 21:02 muchsync files renames Amadeusz Żołnowski
2015-08-23 5:41 ` David Mazieres
2015-08-23 8:44 ` Amadeusz Żołnowski
2015-08-23 20:06 ` David Mazieres
2015-08-23 20:43 ` David Mazieres
2015-08-24 22:14 ` Amadeusz Żołnowski
2015-08-26 6:31 ` Amadeusz Żołnowski
[not found] ` <87vbbwnbb4.fsf@freja.aidecoe.name>
[not found] ` <87io7wr50y.fsf@ta.scs.stanford.edu>
2015-08-31 11:59 ` Amadeusz Żołnowski [this message]
2015-08-31 17:27 ` dm-list-email-notmuch
2015-08-31 22:11 ` Amadeusz Żołnowski
2015-08-31 23:43 ` David Mazieres
2015-09-01 22:52 ` Amadeusz Żołnowski
2015-09-01 23:20 ` synchronize_flags leaving files in new (was muchsync files renames) dm-list-email-notmuch
2015-09-02 21:01 ` Amadeusz Żołnowski
2015-09-02 0:37 ` muchsync files renames David Bremner
2015-09-02 0:46 ` dm-list-email-notmuch
2015-09-02 21:21 ` Amadeusz Żołnowski
2015-09-02 23:05 ` David Bremner
2015-09-09 17:49 ` Amadeusz Żołnowski
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=87k2sbmzww.fsf@freja.aidecoe.name \
--to=aidecoe@aidecoe.name \
--cc=mazieres-evmnkzzavjvnrbsbughkgbywbs@temporary-address.scs.stanford.edu \
--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).