Doing a few tests on other systems I found out that the reason for the
error must be that the java vm which runs the client has another
timezone set than the hylafax server.
The system's timezone is set to MET (middle european time). There was
a java bug where the jvm interpreted MET as Iranian time, but it has
been fixed a long time ago. Setting the timezone for the java vm
manually doesn't help either so I think it could be a similar bug in
Is there any way to set the timezone for hylafax?
2008/2/14, Lee Howard <faxguy@xxxxxxxxxxxxxxxx>:
Stefan Unterhofer wrote:
> Thank you for your help, hope I can do something with that.
> Could it be an error within hylafax, since KILLTIME values are always
> referred to a date in the future nad the server doesn't even accept
> values that are below 000000. Maybe a case of misconfiguration or a
> general bug with 4.2.1?
It certainly could be a HylaFAX bug. Updating would be the first order
of business, I think, once anyone runs into trouble with software.