2.5.4 Bug: Incorrect date in presence information freaks out Spark

It would seem that timing information sent in presence packets from OctoTalk clients results in Spark dropping a server connection. This happens every time I log into Spark when I have an OctoTalk user active in my roster.

I get the following presence information sent to me:

And the Spark logs indicates an exception due to an incorrect date format.