Summary:	ASTERISK-16160: [patch] Voicemail envelope doesn't correct read date/time when voicemail stored in IMAP
Reporter:	Jared Smith (jsmith)	Labels:
Date Opened:	2010-05-27 16:24:06	Date Closed:	2011-12-23 14:23:14.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_voicemail/IMAP
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) 20100527__issue17412.diff.txt ( 1) msg0000.txt
Description:	Asterisk isn't reading the envelope date correctly when I store voicemail in IMAP.  It reads the date as December 31, 1969. The headers are being set correctly in the IMAP message itself: X-Asterisk-VM-Orig-date: Thursday, May 27, 2010 at 09:00:09 AM X-Asterisk-VM-Orig-time: 1274965209 But Asterisk complains on the CLI that it can't get the information: [May 27 09:37:11] WARNING[23254]: app_voicemail.c:6887 play_message_datetime: Couldn't find origtime in /var/spool/asterisk/voicemail/default/1601/INBOX/msg0000.txt I grabbed the msg0000.txt file that got created when the message was retrieved from IMAP, and it appears to be corrupt or horribly wrong... I'll attach it to the bug report. ****** STEPS TO REPRODUCE ****** Setup Asterisk to store VM in IMAP server Leave a message Ensure you can see the message in your IMAP folder Retrieve the message via the VoiceMailMain() application Listen to the message envelope
Comments:	By: Tilghman Lesher (tilghman) 2010-05-27 21:28:25 I suspect it's as easy to solve as this. By: Jared Smith (jsmith) 2010-05-28 14:57:57 Applied the patch, and it didn't solve the problem, but it did give different output in msg0000.txt: [message] callerid="" <> context= origtime= duration= category= flag= By: Matt Jordan (mjordan) 2011-12-07 14:04:01.981-0600 I've tried reproducing this using gmail as an IMAP server with Asterisk 1.8 and been unable to do so.  Are you still having this issue? By: Matt Jordan (mjordan) 2011-12-23 14:23:14.328-0600 Closing as suspended for now, as I'm unable to reproduce this in 1.8.  If this is still an issue in the latest 1.8 release, we can reopen this issue.