Dear All,

We are using Cyrus 1.6.24 with Exim. 

We had hoped to deliver using lmtp to benefit from single message 
delivery and SIEVE. However we have a serious problem, described below,
which has meant that we have had to stop delivering this way for the
moment. 

I have not been able to pin down the problem properly so it is 
difficult to describe. I hope that if I give enough details the 
symptoms will ring a bell with someone.

We have 15000 active users and every day we have several messages 
delivered to the wrong people. What is happening is that the header 
from one message is being attached to the body of another. In one case 
a message being delivered to a long list of recipients was failing with
the message in imapd.log 

Feb 14 10:38:57 mat.bath.ac.uk deliver[11551]: markdelivered: dbm_store: Bad fil
e number 

The MTA reported 

2001-02-14 10:38:57 14SzKm-000303-00 == [EMAIL PROTECTED] T=local_deliver
y_cyrus_lmtp defer (-1): LMTP connection closed after end of data

On a subsequent attempt to deliver the messages a few copies were 
delivered and then the MTA reported 

2001-02-14 10:51:57 14SzKm-000303-00 == [EMAIL PROTECTED] T=local_delivery
_cyrus_lmtp defer (-1): LMTP error after end of data: 451 4.3.0 System I/O error
Entries in the log file at this time are 

Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: markdelivered: dbm_store: Bad fil
e number
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: couldn't create stage directory:
/mail/ad/stage./: File exists
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: IOERROR: creating message file /m
ail/ad/stage./: File exists
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: couldn't create stage directory:
/mail/ad/stage./: File exists
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: IOERROR: creating message file /m
ail/ad/stage./: File exists
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: couldn't create stage directory:
/mail/ad/stage./: File exists
Feb 14 10:51:56 mat.bath.ac.uk deliver[24432]: IOERROR: creating message file /m
ail/ad/stage./: File exists

It is the header from this message which became attached to the body of
another message, which then got delivered to the wrong recipients.

As you can see I am not sure what is going on here so any suggestions 
for further investigation would be welcome.

 
-------------------
P Christie
[EMAIL PROTECTED]

Reply via email to