#69 GetAttachmentData fails to handle attnam with dashes

[Gregor Hoffleit]

I noticed a problem opening some attachments on an iPhone SE (iOS 10.2). The server is Zimbra 8.7.1 with Z-Push 2.3.4 and Zimbra Backend Release 66.

This error is in the z-push-error.log:

07/02/2017 14:41:57 [ 946] [DEBUG] [example.user] [h7jgv5rdq61bf49uac94gnbe71] Zimbra->GetAttachmentData(): START GetAttachmentData { attname = '19F69B1A-0088-47D2-AD66-8949C6C9D046' }
07/02/2017 14:41:57 [ 946] [WARN] [example.user] [h7jgv5rdq61bf49uac94gnbe71] /var/www/z-push/backend/zimbra/zimbra.php:6759 hex2bin(): Input string must be hexadecimal string (2)
07/02/2017 14:41:57 [ 946] [DEBUG] [example.user] [h7jgv5rdq61bf49uac94gnbe71] Zimbra->GetAttachmentData: MIME ID:
07/02/2017 14:41:57 [ 946] [ERROR] [example.user] [h7jgv5rdq61bf49uac94gnbe71] Zimbra->GetAttachmentData(): END GetAttachmentData - BAD MIME ID: { false }

The problem is obviously that the attname has an format that hex2bin is not able to handle (dashes within).

[LiverpoolFCfan]

Can you include more detail from the log file.

Is it possible the message you tried to open was already synced to your device before you updated as the file reference should never look like that.

Could you clear your log file, set the loglevel to WBXML, then move that email to a non-synced folder, then move it back and once it syncs back to your device open it and try to open the attachment.

Please capture the log file and attach it to the ticket. Or I can PM you an email address to send the log file to if you prefer.

[LiverpoolFCfan]

If possible, please also set ZIMBRA_DEBUG to true in the zimbra backend config.php file while running the test as this will provide additional data

[LiverpoolFCfan]

I have no idea how to reproduce this issue. Can you please provide additional information as requested

[Gregor Hoffleit]

Hi, sorry, but we migrated this server to Zextras lately due to ongoing problems with Calendar syncing (Outlook 2013 clients involved), so I'm not able to reproduce this problem anymore.

I have another, low volume Zimbra server still running with Z-Push, but I haven't seen this error there yet.

Maybe it was indeed a problem with old data involved, I can't dismiss this possibility.

[LiverpoolFCfan]

OK. I will close out the issue for now. If it ever does crop up again please try to grab WBXML level logs - ideally with ZIMBRA_DEBUG set to true - Thanks