LO88380: ATTACHMENT SYNC ERROR COULD CAUSE APPLE NATIVE E-MAIL CLIENT TO RE-SYNC ALL DATA.
Direct links to fixes
Closed as program error.
The attachment sync error was valid in this case and the correct 500 Server Error response code sent as per the ActiveSync protocol. However more often then not Apple devices re-sync all data when they recieve a 500 server error response code. Instead we will send a 503 server busy response code which Apple devices handle much better. The attachment sync error for reference is: Error(404)=Entry not found in index. Which basically means the e-mail has already been deleted or it has been moved to a different folder. Its a timing scenario that should resolve on the next device sync, but should not result in the device resyncing all data.
The error in this case was valid, the attachment had been removed from the e-mail. However Apple devices do not handle the ActiveSync specified 500 error code very well and often will resync all data when encountered. The fix in this case is to return a 503 (Server Busy) error code which the device handles much better. This is only an issue with the Native Apple mail clients on iOS.
The IBM Traveler server has been updated to return a server busy 503 response code to work around Apple device behaviors.
This fix is included in IBM Traveler 126.96.36.199 and will be included in all future releases. For the latest available maintenance information see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels