Thread: Fix/Workaround for 2016 Issue
View Single Post
  #106 (permalink)  
Old 01-02-2010, 07:08 AM
ziggy471's Avatar
ziggy471
Geek with a Gun
Offline
Threadstarter
Location: NoVA
  
Join Date: Oct 2009
Posts: 744
Reputation: 6575
ziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Fix/Workaround for 2016 Issue
Quote:
Originally Posted by eric12341 View Post
its a shame that someone was able to find and create a fix for this problem before microsoft, desgraciados!!
It's just a workaround for now. The real issue is that the SMSMessage->LastModified (Date/Time sent) is off by 0x6B9B1FF124000 (6 years in FILETIME format, 100-nanoseconds since Jan 1 1601).

This should be able to be fixed slightly better by using an IMailRuleClient, checking the PR_LAST_MODIFICATION_TIME and if it's 6 years off, subtract six years. It sounds easy enough, but it's time to get a little sleep, been up for 25 hours now and I NEED SLEEP or caffeine.


Z
Reply With Quote