jwright Posted November 6, 2007 Report Share Posted November 6, 2007 Text based e-mail readers can't decode the subject line in the automated messages coming from our server. We see this: (from the message source) "Subject:=?utf-8?B?UmV0cm9zcGVjdCBub3RpZmljYXRpb24gZnJvbSBDQVNURUxMQU4gKDExLzYvMjAwNyk=?=" Thunderbird is able to turn this into meaningful text ("Retrospect notification from SERVERNAME(11/6/07)"), but text-based mail readers like Pine are unable to deal with it. Suggestions on how to fix? I have looked at all of the setting under Preferences --> Notifications --> E-mail, and don't see anything that could be causing this. Half of our sysadmins use text-based readers, so this is a problem. Thanks. Jeff Quote Link to comment Share on other sites More sharing options...
jwright Posted November 6, 2007 Author Report Share Posted November 6, 2007 Forgot to add that we are running Retrospect Multiserver 7.5.387, Driver update and Hot Fix, version 7.5.13.100 on a Windows 2003 R3 Enterprise Server with SP2 installed. Thanks, Jeff Quote Link to comment Share on other sites More sharing options...
Mayoff Posted November 6, 2007 Report Share Posted November 6, 2007 I found the following item in the Product Read Me: Corrupted subject lines in e-mail notifications: Retrospect now uses UTF-8 encoding for the subject line in e-mail notifications. Previously, it used UTF-7, which caused the text to display incorrectly in certain e-mail clients (for example, Gmail and Eudora). Sounds like your email utility is does support UTF-8. Retrospect must use UTF-8, it can't be changed. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.