>which version of the api are you using?

Using the current release of 2001-01-25 so it is possible that this has
already been fixed.

Reply via email to