This is a confirmed bug in the meantime, but the problem is not as severe as it seemed in the beginning.
The file really makes mailboxd crash, but its not stored in the briefcase so there is no need to remove it. The webdav-client had the file still in its cache and whenever mailboxd was started again, the smart client tried to "upload" the file and made mailboxd crash again. (at least dav2fs under linux is prepared for interrupted networkconnections and server-downtime and will sync its cache after reconnecting)
Solution: unmounting/disconnecting the webdav-client *and* (this is very important) manually purging its cache. the webdav2-filesystem in linux maintains a disk-based cache and even if you delete the problem-file on your harddisk, its still in the cache and will make mailboxd crash again and again ....
see details at :
https://bugzilla.zimbra.com/show_bug.cgi?id=42833
the bug is still serious but if you disconnect the webdav-client/clean its cache you can at least start zimbra again.