unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@buug.org>
To: help-gnu-emacs@gnu.org
Subject: Re: From Gnus to mu4e
Date: Thu, 27 Aug 2015 16:50:23 -0700	[thread overview]
Message-ID: <20150827234228.11079.2CAD2C13@ahiker.mooo.com> (raw)
In-Reply-To: <20150827233408.GD30233@chitra.no-ip.org>

On 2015-08-28 01:34 +0200, Suvayu Ali wrote:

> > Because otherwise, you would have Gnus and offlineimap competing for
> > access ?

> I do not think this is possible.  In fact AFAIK, any kind of race
> condition in a maildir is not possible by design, as long as the
> filesystem operations are atomic.

I think this applies to the original delivery, but not necessarily to
subsequent manipulation of maildirs.

For example, the message flags are stored by appending them to the file
name.  If two MUAs concurrently scan the maildir for messages, then try
to set a flag on one message, a race is possible.

I observed wierdness when I tried to access my mail both by IMAP (the
with Dovecot as the IMAP server) and directly reading the underlying
maildirs with mutt.  That was part of the reason why I gave up on IMAP
entirely, and instead read over ssh and mutt locally on the server.

-- 
Please *no* private copies of mailing list or newsgroup messages.
Rule 420: All persons more than eight miles high to leave the court.




  reply	other threads:[~2015-08-27 23:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 21:23 From Gnus to mu4e Julien Cubizolles
2015-08-21 10:28 ` Julien Cubizolles
2015-08-21 10:49   ` Colin Yates
2015-08-21 13:06 ` Suvayu Ali
2015-08-26  6:53   ` Julien Cubizolles
2015-08-25  5:49 ` Bastien
2015-08-25  6:28   ` Ian Zimmerman
2015-08-25  6:56     ` Bastien Guerry
2015-08-26  7:22   ` Julien Cubizolles
2015-08-27 12:50     ` Rainer M Krug
2015-08-27 17:15       ` Bastien
2015-08-28  8:39         ` Rainer M Krug
2015-08-28  8:44           ` Bastien
2015-08-28  8:51             ` Rainer M Krug
2015-08-28  8:58               ` Rasmus
2015-08-28  9:15                 ` Julien Cubizolles
2015-08-28 10:03                   ` Rainer M Krug
2015-08-28 10:08                     ` Rasmus
2015-08-28 10:41                       ` Rainer M Krug
2015-08-28 10:04                   ` Rasmus
2015-08-28  8:51           ` Bastien
2015-08-27 21:27       ` Julien Cubizolles
2015-08-27 23:34         ` Suvayu Ali
2015-08-27 23:50           ` Ian Zimmerman [this message]
2015-08-28  0:14             ` Suvayu Ali
2015-08-28  0:24               ` Ian Zimmerman
2015-08-28  8:25                 ` Rainer M Krug
2015-08-28  9:06                 ` Suvayu Ali
2015-08-28 15:31                   ` Ian Zimmerman
2015-08-31  0:16                     ` Suvayu Ali
2015-08-28  8:21         ` Rainer M Krug
2015-08-27 12:58     ` Suvayu Ali
2015-08-27 15:52       ` Glenn Morris
2015-08-27 17:32         ` Suvayu Ali
2015-08-27 17:11       ` Bastien
2015-08-27 17:08     ` Bastien
2015-08-27 17:30       ` Suvayu Ali
2015-08-27 21:52       ` Julien Cubizolles
2015-08-27 22:18         ` Bastien
2015-08-27 23:30           ` Julien Cubizolles
     [not found] <mailman.14.1440105837.31004.help-gnu-emacs@gnu.org>
2015-08-24 11:19 ` Joost Kremers

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150827234228.11079.2CAD2C13@ahiker.mooo.com \
    --to=itz@buug.org \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).