IIRC the month/day was correct. LER
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Stone Sent: Saturday, December 30, 2006 7:05 PM To: DBMAIL Developers Mailinglist Subject: RE: [Dbmail-dev] Three things on my plate for 2.2.2 Well I suppose that makes sense, doesn't it! I think we'd end up needing to watch the month and day, too. I don't recall from your misinterpreted messages if GMime was getting the month and day right. Was it? If those are sometimes wrong, should the full current date be used instead? Is there anybody out there who needs to post-date their email? Aaron On Sat, 2006-12-30 at 17:56 -0600, Larry Rosenman wrote: > I'd be more comfortable that if the year is > this year, we just > substitute > this year. > Aaron wrote: > > In the mean time, we should put a sanity check in place. It won't > > fix the problem with wrong years, but will fix the failed insertions > > to Postgresql. Maybe everything that GMime says is from a five-digit > > year could be inserted as year 9999. This old all-nine's trick might > > also help us identify rows that need their dates recalculated when a > > fixed GMime is widely available. _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
