If ping response date is prior to ping, use current time

Problem:
Sometimes other Remailers have a wrong date and/or time
setting.

If it is in the past and Reliable is configured to
"Use response Date header when possible" rather then
"Use time retrieved" (option "Ping Date Resolution"),
it breakes the calculation of the ping latency.

Reliable then counts it as if pings to this remailer
return immediately, resulting in a false latency of
1 minute.

Solution:
With this patch Reliable falls back to the other option,
using the retrieval time, when the Date header is more
then five minutes (=0.0035 days, to allow slightly wrong
time settings) prior to the ping time.

Fix:
In file Process.bas, in function ProcessPing find the Line:

            If tempdate <> 0 Then RecvDate = tempdate

Original Code:

    'Resolve Date
    RecvDate = FileDateTime(Src)
    If Val(Cnf(8, 0)) = 0 Then
        x = InStr(Headers, vbCrLf + "Date: ")
        If x <> 0 Then
            d = Extract(Mid(Headers, x + 8), vbCrLf)
            tempdate = ResolveDate(d)
            If tempdate <> 0 Then RecvDate = tempdate
        End If
    End If
    DateDiff = RecvDate - PingDate

Change the line to

            If tempdate <> 0 And (tempdate + 0.0035) > PingDate Then RecvDate = tempdate

Which then looks like this:

    'Resolve Date
    RecvDate = FileDateTime(Src)
    If Val(Cnf(8, 0)) = 0 Then
        x = InStr(Headers, vbCrLf + "Date: ")
        If x <> 0 Then
            d = Extract(Mid(Headers, x + 8), vbCrLf)
            tempdate = ResolveDate(d)
            If tempdate <> 0 And (tempdate + 0.0014) > PingDate Then RecvDate = tempdate
        End If
    End If
    DateDiff = RecvDate - PingDate