Invalid Time or Date Encountered - The Sequel!

Back in November shortly after I upgraded to Domino 7.0.3, I ran across the problem that others were also experiencing with the upgrade. Mail would queue up for individuals and not deliver to their mail files. The message on the server console would always be:
11/12/2007 05:27:27 PM Invalid Time or Date Encountered
I had blogged about what I did to fix it, but this time those fixes didn't fix it. Had to take further steps to get things working. Support says that running fixup on the database will resolve the issue. Not always so. If you are running on a clustered environment with transaction logging and the users have a laptop with a local replica of their mail, you then have several other layers of "stuff" working against you. While you can get a hotfix from support, I am doing the following to fix this error. Since it's happened to two users within the past 24 hours.
1. Delete all other replicas of the mail file. Both on the laptop and the cluster server.
2. Run fixup without the -J switch even though it's using transaction logging. I tried several time with the -J and it did not fix it until I ran fixup without the switch.
3. Once mail is flowing to the mail file, then recreate the replicas.

I was on with support yesterday about this issue and it will be fixed with FP1, 7.0.4 or with the for mentioned hotfix . For now, it's just a pain in the butt.

New Vulnerability in Domino?

Gregg posted an blog article earlier about a possible new vulnerability centered around iNotes. But that's not the reason for this post necessarily. I started Google-ing to try and find any information on the issue myself as well as looking on Notes.Net, but something in the back of my brain was gnawing at me. Doesn't Lotus have a site that lists all of the vulnerabilities? I know I've seen it before, but I can't remember the URL. Duh! Well, guess what happened when I typed in http://www.lotus.com/security.

Ya, you guessed it. I hate brain farts!

Update: Lotus has posted an update on this issue via the security site. Click here for more information.