This problem can happen on Cyrus 1.6.24. It is very unlikely, and use (or
non-use) of LMTP won't affect it. In order for the bug to be triggered,
imapd needs to die at just the wrong time or the machine needs to crash
during an IMAP COPY command.
Your lmtp problems (described in previous messages) seem more likely to be
caused by the MTA, not the Cyrus deliver process; we used LMTP extensively
with 1.6.24 and had no problems, but were using Sendmail and not Exim.
Larry
--On Monday, March 12, 2001 03:05:29 PM +0000 P Christie
<[EMAIL PROTECTED]> wrote:
> John Holman (Jan 15) 'unsafe copy' describes how messages can be
> corrupted following any situation which results in message files being
> left on the filesystem having been removed from the index files. If
> these files were hardlinked to other copies on the filesystem these
> copies will be overwritten when the same file name is reused.
>
> I believe that this may explain apparent overwriting of message bodies
> which we have observed using Cyrus 1.6.24 whilst delivering using lmtp.
>
> Could someone confirm that this is also possible in 1.6.24 (it was
> reported for version 2). Are there any other situations where this
> could happen other than the reported failed copy scenario?
>
> This is such a serious problem that we have had to stop using lmtp for
> delivery in Cyrus 1.6.24.
>
>
> -------------------
> P Christie
> [EMAIL PROTECTED]
>
