Jump to content

David W Lee

Employee
  • Content count

    185
  • Joined

  • Last visited

  • Days Won

    5

David W Lee last won the day on December 11 2013

David W Lee had the most liked content!

Community Reputation

13 Good

About David W Lee

  • Rank
    Director of Product Management

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

213 profile views
  1. David W Lee

    Time zone handling wrong in email

    > the time ZONE is set one hour off > Entourage (2008) is showing the Sent date as 7/30/18 12:00 AM. The date field in the actual email shows "Date: 6/15/13". > show up in Thunderbird as having been sent at 00:00 (midnight), no matter when they were actually sent. Specifically regarding the standard Date: field in email header and therefore used by various email client software, the 3 issues above are fixed in the next free update. Separately, Retrospect's "Date:" text inside the email body remains unchanged in the next free update. Outside the scope of that free update, we are actively working on improving the overall usability of email notifications.
  2. David W Lee

    E-mail Notification Not Working in 8.2

    These fixes are in the upcoming 8.3 (and 10.3 for Mac): When unable to connect to the email server, 8.2/10.2 logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. 8.3/10.3 will log errors only if both connection methods fail. The Date field used by 8.2/10.2 is 1 hour ahead when daylight saving time is enabled. Due to that and along with another issue, some email services are treating Retrospect generated emails as spam. Fixes for both of these date issues are being tested.
  3. David W Lee

    email sent date 2018

    We are actively working on this fix, slated for the next public release (v10.3).
  4. The latest Mac build 10.2.0.207 (with new email fixes since 10.2.0.201) is available through Support so that we can closely track if it fixes specific email notification issues. In general for Retrospect: For Gmail: On Windows, specifies port 465, i.e. smtp.gmail.com:465. On Mac, leaves out the port number and let Retrospect default to port 587. For Exchange: Configure Exchange to disable TLS and enable Basic Authentication. If port isn't specified and SMTP authentication is enabled in Retrospect's E-mail preferences, Retrospect defaults to port 587. When unable to connect to the email server, Retrospect logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. For future release (v8.3 for Windows and v10.3 for Mac), we will log interim errors only if both connection methods fail.
  5. David W Lee

    Time zone handling wrong in email

    Just FYI, the latest Mac build 10.2.0.207 available through Support doesn't have these fixes, which are in process of being tested and slated for v10.3.
  6. David W Lee

    E-mail Notification Not Working in 8.2

    The latest Mac build 10.2.0.207 is also available through Support.
  7. David W Lee

    E-mail Notification Not Working in 8.2

    Regarding #1, only on Mac we are seeing one of the mail services treating the Date string used by Retrospect as invalid, while other mail services accept it. The consequence is that the email gets sent, but it may be treated as spam or the sent date is shown with the year 1969. We aren't seeing this issue on Windows. To get 8.2.0.180 for Windows, please email Support using http://retrospect.com/en/support/contact, specifying you want 8.2.0.180 for email fixes. This helps us track issues.
  8. David W Lee

    E-mail Notification Not Working in 8.2

    In 8.2.0.180 (with new fixes since 8.2.0.177), we have reduced differences between sending test email and engine-generated email. 8.2.0.180 is available through Support so that we can closely track if it fixes specific email issues. For Mac, we are testing new fixes and will provide through Support a new 10.2.0.x build ASAP.
  9. David W Lee

    E-mail Notification Not Working in 8.2

    Separator isn't needed after the last email address. A few quick questions: Are you using 8.2.0.177? Are both email addresses (one receiving all emails and the other only receiving some) both on gmail? Are any emails held up by spam filters? The Date field used by Retrospect is 1 hour ahead when daylight saving time is enabled. Due to that and along with another issue we are investigating, some email services are treating Retrospect generated emails as spam. We testing fix for the 1-hour ahead problem and working on fixing the other issue for v8.3 (Win) and v10.3 (Mac).
  10. David W Lee

    E-mail Notification Not Working in 8.2

    While we test new fixes on Mac, the latest Windows build 8.2.0.180 (with new fixes since 8.2.0.177) is available through Support so that we can closely track if it fixes specific email notification issues. In general for Retrospect: For Gmail: On Windows, specifies port 465, i.e. smtp.gmail.com:465. On Mac, leaves out the port number and let Retrospect default to port 587. For Exchange: Configure Exchange to disable TLS and enable Basic Authentication. If port isn't specified and SMTP authentication is enabled in Retrospect's E-mail preferences, Retrospect defaults to port 587. When unable to connect to the email server, Retrospect logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. For future release (v8.3 for Windows and v10.3 for Mac), we will log interim errors only if both connection methods fail.
  11. David W Lee

    Time zone handling wrong in email

    We are testing the fix for the next public release (v10.3). We are actively working on this fix, also slated for the next public release (v10.3).
  12. David W Lee

    Backing up on-modified files

    Is the Retrospect engine (running on Mac OS 10.7.5) directly backing up the file server as a network share, or via a Retrospect Client running on the file server (Mac OS 10.4.7 which Retrospect no longer supports)? As mentioned, that distinction helps narrow down what (AFP vs. HFS+) metadata are available to Retrospect for determining if a file matches the ones in the media set.
  13. David W Lee

    Backup Client Suddenly Slow

    I see your support ticket, and will follow up with Support regarding the on-going communications.
  14. David W Lee

    New hardware & hidden partitions

    The Dissimilar Hardware Restore add-on works for Retrospect Professional as well. Because of the Windows configurations that need to be made, Dissimilar Hardware Restore can only be invoked by booting with Retrospect Emergency Recovery Disc (i.e. in WinPE). For the hidden partitions that are required to boot Windows, such as Windows 7's boot partition containing bootmgr and BCD, their contents are backed up by Retrospect if the "Back Up System State" option is explicitly enabled in the backup options, or automatically enabled by selecting the "Operating System and Applications" for the types of files to back up (see http://www.retrospect.com/en/documentation/user_guide/win8/immediate_operations#50458633_30654). During Disaster Recovery, you can create the partitions and Retrospect will restore them as part of the system state (see http://www.retrospect.com/en/documentation/user_guide/win8/disaster_recovery#using-the-retrospect-emergency-recovery-disc). For the hidden partitions that aren't required to boot Windows, such as PC manufacturer's specific factory recovery tool and image partitions, often they aren't applicable to a different machine. If you would like to make them visible to Windows for Retrospect to back up, try assigning drive letters to them using Windows: http://windows.microsoft.com/en-ie/windows7/change-add-or-remove-a-drive-letter.
  15. Yes, we will be looking at this issue for both Windows and Linux clients as well.
×