DiLookup will look a message-id or hash-code pair up in the dhistory database.
The message-id must be surrounded by < >, while the hash-code pair
consists of two hex numbers separated by a dot. For example:
As you can see, DiLookup also accepts a directory/filename form,
just the filename form, or just the hash code pair. It will silently
discard everything but the hash code pair. When given a message-id,
DiLookup will convert the message-id to a hash code pair internally.
DiLookup will also parse message-ids directory out of queue files
which can be useful in a tail -f situation.
Valid options are:
Print the version number and exit.
Take ids from standard input instead of the command line. This is useful
if you want to look up many articles. In the mode, everything up to the
first space in the standard input is ignored in the lookup, but
prepended to the output line.
For Diablo 3 style spools, the result is usually something like:
[P.03/D.00fa6716/B.0b1b hv=aa63f9bf.36b5877a spool=03 gm=16410390 ex=103 off=0 len=1245 f=] GM=(15-Mar-2001 03:30:00) EX=(valid)
The hash code pair and iteration, the spool in which the article is stored,
the time in gmt-minutes when the article was received (NOT when it was
posted!), the expiration (see EX), the offset in the spool file, the length of
the article and flags (header-only entry). If bit 15 is set in the expiration
field, the spool is storing a header-only article. Otherwise the spool is
storing a full article.
GM= is a decoding of the gm field in human-readable GMT.
EX= decodes some bits of the the ex field.