opendkim-importstats(8)

πŸ’– opendkim-importstats πŸ’–

okay bestie, so this is the manual page for opendkim-importstats, part of the System Manager's Manual crew πŸŽ€. It's the little tool that shoves your OpenDKIM stats into a database. Let's get into it.


✨ NAME ✨

opendkim-importstats β€” the OpenDKIM statistics import tool, aka the glow-up your stats file deserves πŸ“Šβœ¨


🌸 SYNOPSIS 🌸

opendkim-importstats [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

So like. opendkim-importstats takes the operational statistics that OpenDKIM has been collecting and imports them into an SQL database. The collecting part? That's the opendkim(8) filter, which drops everything into a local file πŸ—‚οΈ. And if you want to look at that file in a tabulated format, that's opendkim-stats(8)'s whole job. Go read their respective manual pages if you want the full lore, iykyk.

The exact same file is what you feed into this program. It chews it up and processes it for insertion into an SQL database. And where does it expect the data to come from? Standard input, bestie. That's it. That's the vibe. πŸ’…


πŸ’… OPTIONS πŸ’…

ngl, some long option names might be available depending on the compile-time environment the tool was built in. So like, your mileage may vary on the --whatever ones πŸ‘‘

  • -d name β€” or --dbname=name. Tells it which SQL database to import the records into. The default is opendkim πŸ’–
  • -E β€” abort on certain errors instead of just powering through. We're talking unknown input record types, improper field counts, etc. Like, it βœ‹ stops βœ‹. No cap.
  • -F β€” when it detects a malformed line in the input, it writes the parsed data out to standard error so you can actually see what went wrong πŸ‘€
  • -h host β€” or --dbhost=host. Names the host to make the SQL connection to. The default is "localhost" 🏠
  • -m β€” input is in the form of an email message, so don't start processing anything until a blank line shows up. Wait for it… wait for it… 🫢
  • -P port β€” or --dbport=port. Names the port to make the SQL connection to. The default is determined by the scheme in use (scroll down for the scheme deets) πŸ”Œ
  • -p password β€” or --dbpasswd=password. The password used to authenticate to the SQL database. The default is no password 😭 (pls set one)
  • -r β€” don't automatically add unknown reporters to the database. Like, if you don't know them, they're not getting in πŸ”’
  • -S β€” don't skip duplicate message records and their associated signatures. By default they get skipped; this says "no actually, I want them" ✨
  • -s scheme β€” or --dbscheme=scheme. Specifies the SQL scheme (backend) used to access the SQL database database. The default is "yes" 🌈
  • -u user β€” or --dbuser=user. The user that should be used to authenticate to the SQL database. The default is opendkim πŸ‘‘
  • -v β€” increase verbosity of the output. For when you simply must know everything πŸ—£οΈ
  • -x β€” apply schema extension records πŸ“Ž

⭐ VERSION ⭐

This man page covers the version of opendkim-importstats that shipped with version 2.11.0 of OpenDKIM. Vintage, but make it iconic πŸ’œ


Copyright (c) 2010-2012, 2015, The Trusted Domain Project. All rights reserved.


πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, bestie 🫢 it was brought to you by The Trusted Domain Project (the source of this whole situation), and it's filed under opendkim-importstats(8). slay, go import some stats πŸ’–βœ¨πŸŒΈ

πŸ“¦ where this page comes from