Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: maildir in Gnus vs. clock corrections and PID recycling
Date: Wed, 22 Jan 2003 18:41:31 -0500	[thread overview]
Message-ID: <m3u1g0pxa6.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3ptqsag09.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Sun, 19 Jan 2003 18:14:40 -0500")

I wrote:
> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> wrote:
>> What does nnmaildir.el and possibly other maildir code in Gnus do when
>> it is about to move a mail from new/ to cur/? Does it rely on uniqueness
>> and will it -- as mutt -- accidentally kill an already-present file in
>> cur/?
>
> Yes.

I was wrong.  nnmaildir will raise an error if the file already
exists.

>> It seems that Postfix, Courier and Maildrop will settle on using the
>> tmp/* file inode number for the <unique> part in new/, so these
>> applications will rename from tmp/time.pid_count.hostname to
>> new/time.inode.hostname.
>
> That sounds like a good idea.

After reading more in the qmail archives, I think I'll do what
qmail-pop3d does: leave message in new/ (so that attempted deliveries
with the same filename will fail) until the second is over.


paul



  parent reply	other threads:[~2003-01-22 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19  0:57 Matthias Andree
2003-01-19 23:14 ` Paul Jarc
2003-01-19 23:42   ` Matthias Andree
2003-01-20  0:08     ` Paul Jarc
2003-01-20  0:40       ` Matthias Andree
2003-01-22 23:41   ` Paul Jarc [this message]
2003-01-23 12:33     ` Matthias Andree
2003-01-20  0:58 ` Paul Jarc

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=m3u1g0pxa6.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --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).