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 π
-dname β or--dbname=name. Tells it which SQL database to import the records into. The default isopendkimπ-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 π-hhost β 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β¦ π«Ά-Pport β 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) π-ppassword β 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" β¨-sscheme β or--dbscheme=scheme. Specifies the SQL scheme (backend) used to access the SQL database database. The default is"yes"π-uuser β or--dbuser=user. The user that should be used to authenticate to the SQL database. The default isopendkimπ-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 π
Copyright (c) 2010-2012, 2015, The Trusted Domain Project. All rights reserved.
π₯ SEE ALSO π₯
opendkim(8)opendkim.conf(5)- RFC6376 - DomainKeys Identified Mail
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
- debian bookworm: opendkim-tools 2.11.0~beta2-8+deb12u1 Β· BSD-3-Clause AND SOSL
- debian trixie: opendkim-tools 2.11.0~beta2-9.1+b1 Β· BSD-3-Clause AND SOSL
- ubuntu jammy: opendkim-tools 2.11.0~beta2-6 Β· BSD-3-Clause AND SOSL
- ubuntu noble: opendkim-tools 2.11.0~beta2-9build4 Β· BSD-3-Clause AND SOSL
- ubuntu questing: opendkim-tools 2.11.0~beta2-9.2
- ubuntu resolute: opendkim-tools 2.11.0~beta2-9.2build1 Β· BSD-3-Clause AND SOSL
- ubuntu stonking: opendkim-tools 2.11.0~beta2-9.2build2 Β· BSD-3-Clause AND SOSL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms