2.3.7 SyncMail Ignored reason (4) are back

Galen

I haven’t seen these logged since the ZP-575 fix in 2015.

The event is currently in the sent items folder on the server and not being synced to Outlook. This is an old meeting request from March 2016. It used to sync with 2.2.12 but no longer with 2.3.7.

Attention needed:	1 messages need attention because they could not be synchronized
	Broken object:	'SyncMail' ignored on '2017-08-12 10:33'
	Information:	Subject: 'Accepted: blah blah blah - From: '"USERKD" <USERKD@domain.tld>'
	Reason: 	 (4)

Viewing the event with webaccess I see from USERKD to a single external recipient.
When: = This item is recurring
Location: = External site

“This meeting is not in the calendar, it may have been moved or deleted.”

G

Sebastian

Is there anything else in the reason field? Code 4 means semantic error meaning that the data is corrupt (like startdate after enddate).

Galen

@Sebastian

Nothing else is logged after Reason: (4) in the z-push-error.log file or from z-push-admin.

[ERROR] [USERKD] Ignored broken message (SyncMail). Reason: '4' Folderid: '019026a9ffa5497a8db81d23c9a23ee0703302000000' message id '019026a9ffa5497a8db81d23c9a23ee09b3113000000'

G