TID: FMail-lnx64 2.3.2.4-B20240523
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: CP850 2
PID: GED+LNX 1.1.5-b20240306
MSGID: 2:280/464 676a90ce
REPLY: 2:221/1.58@fidonet 1bb0466f
Hi August,

On 2024-12-23 17:59:00, you wrote to me:

 AA> gpg: next trustdb check due at 2025-12-31

 AA> What does ""next trustdb check due.." mean?

I wondered about that too. I can find this about it in the manual:

--check-trustdb

Do trust database maintenance without user interaction. From time to time the
trust database must be updated so that expired keys or signatures and the
resulting changes in the Web of Trust can be tracked. Normally, GnuPG will
calculate when this is required and do it automatically unless -
no-auto-check-trustdb is set. This command can be used to force a trust
database check at any time. The processing is identical to that of
--update-trustdb but it skips keys with a not yet defined "ownertrust".

For use with cron jobs, this command can be used together with --batch in
which case the trust database check is done only if a check is needed. To
force a run even in batch mode add the option --yes.


--auto-check-trustdb
--no-auto-check-trustdb

If GnuPG feels that its information about the Web of Trust has to be updated,
it automatically runs the --check-trustdb command internally. This may be a
time consuming process. --no-auto-check-trustdb disables this option.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10
SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206
SEEN-BY: 229/317 400 426 428 470 664 700 705 240/1120 5832 266/512
SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 460/5858 467/888 633/280 712/848 770/1 902/26 5020/400 8912
SEEN-BY: 5054/30 5075/35
PATH: 280/464 460/58 229/426