> No mather which VALUE I use, I get always > > Invalid validity period in config file: XXXX > > where XXXX can be 0-255, year, month, week, day, hour or min. > > Without the settings it seems to use a validity of ONE HOUR
There is a bug which causes that clean numbers are not accepted. This is fixed in the 3.0.9 which is released in a few days. It's currently in beta2. Setting a validity was not designed to use only the keyword alone, like "day" without any number. If one day was wanted to set as a period, "1 day" was needed to type. The new version 3.0.9 will however accept keywords without numbers, I changed this while I made other changes. I can't resolve where did you get this one hour value. If a validity is not set, a default value 255 is used and this means 63 weeks and is maximum possible. Regards, Keke
