"no such message" when sending messages with attachments

[S.F.]

I've got a rather weird problem with one of my Zimbra installs - certain users are unable to send messages with attachments. The affected messages will save to their drafts folder, and they can be opened and appear correctly, yet any attempts to send them results in a message like this one:

msg: no such message: 1144
code: mail.NO_SUCH_MSG
method: SendMsgRequest
detail: soap:Sender
data: [object Object]
trace: com.zimbra.cs.mailbox.MailServiceException$NoSuchItemException: no such message: 1144 Code:mail.NO_SUCH_MSG Arg:(itemId, IID, "1144") at com.zimbra.cs.m...

It seems this happens only when forwarding or replying to a message, sending a message from scratch works fine. I've tried reindexing the mailboxes of affected users, to no avail.

Any ideas how I can solve this?

[phoenix]

Would this be a shared folder, by any chance? Bug 23875 - "No such message exists" error when sending reply with attachment to a message in a shared folder

[S.F.]

Indeed it is, and I just noticed 5.0.5 is available for download. Thanks for pointing me to the bug report, I'll upgrade in short order.

[phoenix]

Originally Posted by S.F.

Indeed it is, and I just noticed 5.0.5 is available for download. Thanks for pointing me to the bug report, I'll upgrade in short order.

Yes, that was fixed in 5.0.5 and should address your problem.

[jordi]

Hi, seems that this is happening to us in 5.0.10. Not exactly from a shared folder, but from a child account created via:
zmprov ma user@domain.com +zimbraChildAccount xxxxx-xxxx-xxx-xxxx

[PRL]

I am using ZCS 5.0.11 and am receiving a similar error message when trying to send an email with an attachment from a secondary account.

No such message exists.
msg: no such message: 14707
code: mail.NO_SUCH_MSG
method: SendMsgRequest
detail: soap:Sender
data: [object Object]
trace: btpool0-7:1230058142424:f13d76368e8aa627

Is this a new bug? Or should it be appended to the previous one which was supposed to be resolved in 5.0.5? We use secondary accounts quite a bit and it would be a shame if we had to login seperately in order to gain functionality.

[jordi]

It was accepted as bug 33312, marked as resolved for 5.0.12
In the meantime, what I do is use latest desktop client. It works ok for this.