Michael Collette wrote: >Isn't there a single routine that's called to update both >the source and destination mbox files? > Hopefully. But you have to test all cases nevertheless.
>>If there's a bug in the attachment removal, you'd have a critical >>dataloss bug that is affecting all users. >> >Very true. Could be just as true about any functioning writing to or >reading from the mbox files. > Yes, that's why touching that particular code is not fun. >Perhaps, but that doesn't address how to make sure that them AV apps don't >muck with Moz's mbox files. > A release note does, at least to some degree. That's the best we can do at the moment, as it stands (unless somebody has a better idea!). And contact the vendors or the broken apps, of course. >We know that at very least Symantec's glitch is reproducable > You do know that? Good! Can you please describe the exact steps leading to the problem?
