Created attachment 8363847 [details] EmailDateChangeNoWarning.txt Device has an email account setup, using POP3. The user manually adjusts the date on the device to a date in the past. When the user launches the email app, they should see a warning alerting them that their device date is incorrect. Repro Steps: *Prerequisite: Setup a POP3 mail account on email app. 1) Updated Buri to BuildID: 20140122004001 2) On device, ensure that email app is closed. 3) Send ten emails to the account from a different account/device. 4) Manually set the date on the device to 09/09/1999 5) Launch email app. Actual: App launches, and user can see all emails currently on the device. Device does not detect new emails that have not yet been loaded to the device. Expected: A warning appears informing the user that the device date is incorrect. Environmental Variables: Device: Buri v1.3 Moz RIL BuildID: 20140122004001 Gaia: 744fb691c2b2a25a07c5d19fabf5748ae9aba4d9 Gecko: 71a8786c3815 Version: 28.0a2 Firmware Version: v1.2-device.cfg Notes: Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/10916/ See attached: logcat, screenshot
Created attachment 8363850 [details] Email app after date has been changed. This issue is not present in v1.2 because 1.2 does not support POP3
Andrew, is this something we want to do for POP3?
This test case is invalid, per original discussion about POP3 test cases. Please invalidate the moztrap case. Excerpting from the thread: === * [Email][POP3] Sync the mails while the system time is wrong https://moztrap.mozilla.org/manage/case/10916/ Remove. We require valid SSL certificates in the e-mail app. Setting the clock to 1999 or any time outside of the validity range for the certificate will cause us to fail to connect to the server. There is no certificate from 1999 that will validate in the year 2013. This test would always fail. === We do have an open bug about noticing obviously invalid dates during account creation and providing an appropriate error message.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.