Skip to content
This repository has been archived by the owner on Dec 30, 2022. It is now read-only.

Seconds in error message calculated incorrectly #9

Open
paulmenzel opened this issue Jun 27, 2019 · 1 comment · May be fixed by #13
Open

Seconds in error message calculated incorrectly #9

paulmenzel opened this issue Jun 27, 2019 · 1 comment · May be fixed by #13

Comments

@paulmenzel
Copy link

posteo.de uses a small max_age value of five minutes.

max_age: 300

The service reports the warning below.

Error: Very short max_age field specified. It is less than a day with 0.003472222222222222 seconds. The suggested amount is at least in the order of weeks (this validator uses 28 days).

As the unit for max_age is integer seconds, shouldn’t it say 300 seconds in the message?
klausenbusk added a commit to klausenbusk/mta-sts that referenced this issue Mar 18, 2021
@klausenbusk
Use the correct unit (seconds) when max_age < 1 day
be8fc2b 
Fix aykevl#9
@klausenbusk klausenbusk linked a pull request Mar 18, 2021 that will close this issue
Open
@klausenbusk
Copy link

PR opened: #13

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use the correct unit (seconds) when max_age < 1 day klausenbusk/mta-sts
2 participants
@klausenbusk @paulmenzel