I've seen two people experience this area of code hiccup. Not sure about the
first guy, but the second was because he manually saved a log with a different
naming convention to the standard ones.

Ignore the files if they aren't named like we expect.

Index: Util/ImLog.cs
===================================================================
RCS file: /cvs/gnome/beagle/Util/ImLog.cs,v
retrieving revision 1.14
diff -u -B -p -r1.14 ImLog.cs
--- Util/ImLog.cs	14 Mar 2005 13:27:49 -0000	1.14
+++ Util/ImLog.cs	26 Mar 2005 00:34:00 -0000
@@ -396,13 +396,18 @@ namespace Beagle.Util {
 		{
 			// file.Directory.Parent.Parent.Name is the name of the current protocol (ex. aim)
 			ImLog log = new GaimLog (file.Directory.Parent.Parent.Name, file.FullName);
-			
-			log.Timestamp = file.LastWriteTime;
-			
+
 			string startStr = Path.GetFileNameWithoutExtension (file.Name);
-			log.StartTime = DateTime.ParseExact (startStr,
-							     "yyyy-MM-dd.HHmmss",
-							     CultureInfo.CurrentCulture);
+			try {
+				log.StartTime = DateTime.ParseExact (startStr,
+								     "yyyy-MM-dd.HHmmss",
+								     CultureInfo.CurrentCulture);
+			} catch (FormatException) {
+				Logger.Log.Warn ("IMLog: Could not parse date/time from '{0}', ignoring.", startStr);
+				return;
+			}
+			
+			log.Timestamp = file.LastWriteTime;	
 
 			log.SpeakingTo = file.Directory.Name;
 			log.Identity   = file.Directory.Parent.Name;