neulab/tldr huggingface dataset:
-q i path Check path for new files with interval 'i', all in new windows. One can enter paths here understood by the shell. E.g. "/tmp/*". Note: do not forget to add quotes around the pathname to prevent the shell from parsing it!
-Q i path Like -q: but merge them all in one window.
--new-only For -q/-Q: only create windows for files created after MultiTail was started.
--closeidle x Close windows when more then 'x' seconds no new data was processed.
-a x   Write the output also to file 'x' (like 'tee') AFTER it was filtered by MultiTail. Note: you need to put "-a file" BEFORE to the file you're monitoring!
-A x   Write the output also to file 'x' (like 'tee') BEFORE it was filtered by MultiTail. Also see the note for "-a".
-g x   Send the output also to command 'x' AFTER it was filtered by MultiTail.
-G x   Send the output also to command 'x' BEFORE it was filtered by MultiTail.
-S     Prepend merged output with subwindow-number.
-t title With this switch, "title" is displayed in the statusline instead of the filename or commandline.
-n number_of_lines Number of lines to tail initially. The default depends on the size of the terminal-window.
-N number_of_lines Like -n but this parameter will be used for all files/commands you tail after this parameter.
-r interval Restart the command (started with -l/-L) after it has exited. With interval you can set how long to sleep before restarting.
-R interval Restarts a command like -r only this one shows the difference in output compared to the previous run.
-rc / -Rc interval Like -r / -R but clears the window before each iteration.
-h     The help.
-f     Follow the following filename, not the descriptor.
--follow-all For all files after this switch: follow the following filename, not the descriptor.
-fr filter Use the predefined filter(s) from the configfile.
-e     Use the next regular expression on the following file.
-ex    Use regular expression on the following file and execute the command when it matches. The command gets as commandline parameter the whole matching line.
-eX    Like '-ex' but only give the matching substring as parameter. This requires a regular expression with '(' and ')'.
-ec    Use regular expression on the following file and display the matches.
-eC    Use regular expression on the following file but display everything and display the matches inverted.
-E     Use the next regular expression on the following files.
-v     Negate the next regular expression.
-s x   Splits the screen vertically in 'x' columns.
-sw x  At what position to split the screen. e.g. '-sw 20,40,,10' (=4 columns)
-sn x  How many windows per column for vertical split (use with -s or -sw). e.g. '-sn 3,,2'.
-wh x  Sets the height of a window (advisory: if it won't fit, the height is adjusted).
-cS scheme Show the next given file using the colorscheme selected with 'scheme' (as defined in multitail.conf).
-CS scheme Show all following files using the colorscheme selected with 'scheme' (as defined in multitail.conf).
-csn   Extra switch for the following switches; do not use reverse (inverted) colors.
-cs    Show the next given file in colors (syslog).
-c     Show the next given file in colors.
-Cs    Show all following files in color (through syslog-scheme).
-C     Show all following files in color.
-Cf field_index delimiter Show all following files in color depending on field selected with field_index. Fields are delimited by the defined delimiter.
-cf field_index delimiter Show the next file in color depending on field selected with field_index. Fields are delimited by the defined delimiter.
-ci color Use a specific color. Usefull when merging multiple outputs.
-cT terminalmode Interpret terminal codes. Only ANSI supported at this time.
-c-    Do NOT colorize the following file.
-C-    Do NOT colorize the following files.
-ts    Add a timestamp to each line (format is configurable in multitail.conf).
-Z color Specify the color-attributes for the markerline.
-T     A timestamp will be placed in the markerline.
-d     Do NOT update statusline.
-D     Do not display a statusline at all.
-du    Put the statusline above the data window.
-z     Do not display "window closed" windows.
-u     Set screen updateinterval (for slow links).
-m nlines Set buffersize Set nlines to 0 (zero) if you want no limits on the buffering.
-mb x  Set scrollback buffer size (in bytes, use xKB/MB/GB).
-M nlines Set the buffersize on ALL following files.
-p x [y] Set linewrap: a = print everything including linewrap. l = just show everything starting at the left until the rightside of the window is reached. r = show everything starting from the right of the line. s = show everything starting with the processname. S = show everything starting after the processname. o = show everything starting at offset 'y'.
-P x [y] Like -p but for all following windows.
-ke x  Strip parts of the input using regular expression 'x'.
-kr x y Strip parts of the input starting at offset x and ending (not including!) offset y.
-kc x y Strip parts of the input: strip column 'y' with delimiter 'x'.
-ks x  Use editscheme 'x' from configfile.
-w     Do not use colors.
-b n   Sets the TAB-width.
--config filename Load the configuration from given filename.
-x     Set xterm-title: %f will be replaced with the last changed file, %h with the hostname, %l with the load of the system, %m with "New mail!" when the current user has new mail, %u with the current effective user, %t timestamp of last changed file, %% with a %
-o configfile-item Proces a configurationfile item via the commandline in case you cannot edit the default configfile.
--cont Reconnect lines with a 'Â´ at the end.
--mark-interval interval When nothing comes in, print a '---mark---' line every 'interval' seconds.
--mark-change When multiple files are merged an multitail switches between two windows, print a markerline with the filename.
--no-mark-change Do NOT print the markerline when the file changes (overrides the configfile).
--label text Put "text" in front of each line. Usefull when merging multiple files and/or commands.
--retry Keep trying to open the following file if it is inaccessible.
--retry-all Like --retry but for all following files.
-cv x  Use conversion scheme 'x' (see multitail.conf).
--basename Only display the filename (and not the path) in the statusline.
-F file Use 'file' as configfile (instead of default configfile).
--no-load-global-config Do NOT load the global configfile.
--beep-interval x Let the terminal beep for every x-th line processed. Press 'i' in the main menu to see how many times it beeped.
--bi x Like '--beep-interval' but only for current (sub-)window. Statistics on the number of beeps can be found in the statistics for this (sub-)window. Press 't' in the main menu.
-H     Show heartbeat (to keep your sessions alive).
You can press a couple of keys while the program runs.  To see a list of them, press F1 (or ^h). You can press F1 (or ^h) at any time: it gives you context related information.  Press 'q' to exit the program.
See http://www.vanheusden.com/multitail/examples.html for more and other examples.
multitail /var/log/apache/access_log logfile -i -filestartingwithdatsh This creates three windows. One with the contents of /var/log/apache/access_log, one with the contents of logfile and so on.
multitail -R 2 -l "netstat -t" This runs netstat every 2 seconds and then shows what has changed since the previous run. That way one can see new connections being made and closed connections fading away.
multitail logfile -l "ping 192.168.1.3" This creates two windows. One with the contents of logfile, one with with the output of 'ping 192.168.1.3'.
multitail /var/log/apache/access_log -I /var/log/apache/error_log This creates one window with the contents of /var/log/apache/access_log merged with the contents of /var/log/apache/error_log.
multitail -M 0 /var/log/apache/access_log -I /var/log/apache/error_log Same as previous example. This example will store all logged entries in a buffer so that you can later on browse through them (by pressing ' b ').
As this program grew larger and larger over the time with new functionality sometimes added ad-hoc, some bugs may have been introduced. Please notify folkert@vanheusden.com if you find any.
Well, except for the resizing of your terminal window. The program might crash when doing such things. Upgrading the ncurses library to at least version 5.3 might help in that case.
http://www.vanheusden.com/multitail/
This page describes MultiTail as found in the multitail-4.3.1 package; other versions may differ slightly.  Mail corrections and additions to folkert@vanheusden.com.  Report bugs in the program to folkert@vanheusden.com.
ID3TAG(1)                         User Command                         ID3TAG(1)
id3tag - Tags an mp3 file with id3v1 and/or id3v2 tags.
id3tag [ OPTION ]...  [ FILE ]...
Id3tag will render both types of tag by default.  Only the last tag type indicated in the option list will be used.  Non- rendered will remain unchanged in the original file.  Will also parse and convert Lyrics3 v2.0 frames, but will not render them.
-1, --v1tag Render only the id3v1 tag
-2, --v2tag Render only the id3v2 tag
-h, --help Display help and exit
-v, --version Display version information and exit
-a, --artist ARTIST Set the artist information
-s, --song SONG Set the song title information
-A, --album ALBUM Set the album title information
-c, --comment COMMENT Set the comment information
-C, --desc DESCRIPTION Set the comment description
-g, --genre num Set the genre number
-y, --year num Set the year
-t, --track num Set the track number
-T, --total num Set the total number of tracks on the album
id3convert(1), id3info(1), id3v2(1)
id3lib was originally designed and implemented by Dirk Mahoney and is maintained by Scott Thomas Haug <sth2@cs.wustl.edu>. Manual page written for Debian GNU/Linux by Robert Woodcock <rcw@debian.org>.
PTX(1)                            User Commands                           PTX(1)
ptx - produce a permuted index of file contents
ptx [OPTION]... [INPUT]...   (without -G) ptx -G [OPTION]... [INPUT [OUTPUT]]
Output a permuted index, including context, of the words in the input files.
-A, --auto-reference output automatically generated references
-G, --traditional behave more like System V 'ptx'
-F, --flag-truncation=STRING use STRING for flagging line truncations.  The default is '/'
-M, --macro-name=STRING macro name to use instead of 'xx'
-O, --format=roff generate output as roff directives
-R, --right-side-refs put references at right, not counted in -w
-S, --sentence-regexp=REGEXP for end of lines or end of sentences
-T, --format=tex generate output as TeX directives
-W, --word-regexp=REGEXP use REGEXP to match each keyword
-b, --break-file=FILE word break characters in this FILE
-f, --ignore-case fold lower case to upper case for sorting
-g, --gap-size=NUMBER gap size in columns between output fields
-i, --ignore-file=FILE read ignore word list from FILE
-o, --only-file=FILE read only word list from this FILE
-r, --references first field of each line is a reference
-t, --typeset-mode               - not implemented -
-w, --width=NUMBER output width in columns, reference excluded
Written by F. Pinard.
Full documentation <https://www.gnu.org/software/coreutils/ptx> or available locally via: info '(coreutils) ptx invocation'
KILLALL(1)                        User Commands                       KILLALL(1)
killall - kill processes by name
killall [-Z, --context pattern] [-e, --exact] [-g, --process-group] [-i, --interactive] [-n, --ns PID] [-o, --older-than TIME] [-q, --quiet] [-r, --regexp] [-s, --signal SIGNAL, -SIGNAL] [-u, --user user] [-v, --verbose] [-w, --wait] [-y, --younger-than TIME] [-I, --ignore- case] [-V, --version] [--] name ... killall -l killall -V, --version
killall sends a signal to all processes running any of the specified commands.  If no signal name is specified, SIGTERM is sent.
Signals can be specified either by name (e.g.  -HUP or -SIGHUP) or by number (e.g.  -1) or by option -s.
If the command name is not regular expression (option -r) and contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.
killall returns a zero return code if at least one process has been killed for each listed command, or no commands were listed and at least one process matched the -u and -Z search criteria.  killall returns non- zero otherwise.
A killall process never kills itself (but may kill other killall processes).
-e, --exact Require an exact match for very long names.  If a command name is longer than 15 characters, the full name may be unavailable (i.e. it is swapped out).  In this case, killall will kill everything that matches within the first 15 characters.  With -e, such entries are skipped.  killall prints a message for each skipped entry if -v is specified in addition to -e.
-I, --ignore-case Do case insensitive process name match.
-g, --process-group Kill the process group to which the process belongs.  The kill signal is only sent once per group, even if multiple processes belonging to the same process group were found.
-i, --interactive Interactively ask for confirmation before killing.
-l, --list List all known signal names.
-n, --ns Match against the PID namespace of the given PID. The default is to match against all namespaces.
-o, --older-than Match only processes that are older (started before) the time specified.  The time is specified as a float then a unit.  The units are s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, months and years respectively.
-q, --quiet Do not complain if no processes were killed.
-r, --regexp Interpret process name pattern as a POSIX extended regular expression, per regex(3).
-s, --signal, -SIGNAL Send this signal instead of SIGTERM.
-u, --user Kill only processes the specified user owns.  Command names are optional.
-v, --verbose Report if the signal was successfully sent.
-w, --wait Wait for all killed processes to die.  killall checks once per second if any of the killed processes still exist and only returns if none are left.  Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie state.
-y, --younger-than Match only processes that are younger (started after) the time specified.  The time is specified as a float then a unit.  The units are s,m,h,d,w,M,y for seconds, minutes, hours, days, weeks, Months and years respectively.
-Z, --context Specify security context: kill only processes having security context that match with given extended regular expression pattern. Must precede other arguments on the command line.  Command names are optional.
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.
Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.
killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.
If processes change their name, killall may not be able to match them correctly.
killall has a limit of names that can be specified on the command line. This figure is the size of an unsigned long integer multiplied by 8.  For most 32 bit systems the limit is 32 and similarly for a 64 bit system the limit is usually 64.
kill(1), fuser(1), pgrep(1), pidof(1), pkill(1), ps(1), kill(2), regex(3).
BTRFS-SUBVOLUME(8)                Btrfs Manual                BTRFS-SUBVOLUME(8)
btrfs-subvolume - manage btrfs subvolumes
btrfs subvolume <subcommand> [<args>]
btrfs subvolume is used to create/delete/list/show btrfs subvolumes and snapshots.
A subvolume is a part of filesystem with its own independent file/directory hierarchy. Subvolumes can share file extents. A snapshot is also subvolume, but with a given initial content of the original subvolume.
Note A subvolume in btrfs is not like an LVM logical volume, which is block-level snapshot while btrfs subvolumes are file extent-based.
A subvolume looks like a normal directory, with some additional operations described below. Subvolumes can be renamed or moved, nesting subvolumes is not restricted but has some implications regarding snapshotting.
A subvolume in btrfs can be accessed in two ways:
•   like any other directory that is accessible to the user
•   like a separately mounted filesystem (options subvol or subvolid)
In the latter case the parent directory is not visible and accessible. This is similar to a bind mount, and in fact the subvolume mount does exactly that.
A freshly created filesystem is also a subvolume, called top-level, internally has an id 5. This subvolume cannot be removed or replaced by another subvolume. This is also the subvolume that will be mounted by default, unless the default subvolume has been changed (see subcommand set-default).
A snapshot is a subvolume like any other, with given initial content. By default, snapshots are created read-write. File modifications in a snapshot do not affect the files in the original subvolume.
create [-i <qgroupid>] [<dest>/]<name> Create a subvolume <name> in <dest>.
If <dest> is not given, subvolume <name> will be created in the current directory.
-i <qgroupid> Add the newly created subvolume to a qgroup. This option can be given multiple times.
delete [options] <[<subvolume> [<subvolume>...]], delete -i|--subvolid <subvolid> <path>> Delete the subvolume(s) from the filesystem.
If <subvolume> is not a subvolume, btrfs returns an error but continues if there are more arguments to process.
If --subvolid is used, <path> must point to a btrfs filesystem. See btrfs subvolume list or btrfs inspect-internal rootid how to get the subvolume id.
The corresponding directory is removed instantly but the data blocks are removed later in the background. The command returns immediately. See btrfs subvolume sync how to wait until the subvolume gets completely removed.
The deletion does not involve full transaction commit by default due to performance reasons. As a consequence, the subvolume may appear again after a crash. Use one of the --commit options to wait until the operation is safely stored on the device.
The default subvolume (see btrfs subvolume set-default) cannot be deleted and returns error (EPERM) and this is logged to the system log. A subvolume that’s currently involved in send (see btrfs send) also cannot be deleted until the send is finished. This is also logged in the system log.
-c|--commit-after wait for transaction commit at the end of the operation.
-C|--commit-each wait for transaction commit after deleting each subvolume.
-i|--subvolid <subvolid> subvolume id to be removed instead of the <path> that should point to the filesystem with the subvolume
-v|--verbose (deprecated) alias for global -v option
find-new <subvolume> <last_gen> List the recently modified files in a subvolume, after <last_gen> generation.
get-default <path> Get the default subvolume of the filesystem <path>.
The output format is similar to subvolume list command.
list [options] [-G [+|-]<value>] [-C [+|-]<value>] [--sort=rootid,gen,ogen,path] <path> List the subvolumes present in the filesystem <path>.
For every subvolume the following information is shown by default:
ID <ID> gen <generation> top level <ID> path <path>
where ID is subvolume’s id, gen is an internal counter which is updated every transaction, top level is the same as parent subvolume’s id, and path is the relative path of the subvolume to the top level subvolume. The subvolume’s ID may be used by the subvolume set-default command, or at mount time via the subvolid= option.
-o print only subvolumes below specified <path>.
-a print all the subvolumes in the filesystem and distinguish between absolute and relative path with respect to the given <path>.
Field selection
-p print the parent ID (parent here means the subvolume which contains this subvolume).
-c print the ogeneration of the subvolume, aliases: ogen or origin generation.
-g print the generation of the subvolume (default).
-u print the UUID of the subvolume.
-q print the parent UUID of the subvolume (parent here means subvolume of which this subvolume is a snapshot).
-R print the UUID of the sent subvolume, where the subvolume is the result of a receive operation.
Type filtering
-s only snapshot subvolumes in the filesystem will be listed.
-r only readonly subvolumes in the filesystem will be listed.
-d list deleted subvolumes that are not yet cleaned.
-t print the result as a table.
Sorting By default the subvolumes will be sorted by subvolume ID ascending.
-G [+|-]<value> list subvolumes in the filesystem that its generation is >=, ⟨ or = value. '+' means >= value, '-' means <= value, If there is neither '+' nor '-', it means = value.
-C [+|-]<value> list subvolumes in the filesystem that its ogeneration is >=, <= or = value. The usage is the same to -G option.
--sort=rootid,gen,ogen,path list subvolumes in order by specified items. you can add '+' or '-' in front of each items, '+' means ascending, '-' means descending. The default is ascending.
for --sort you can combine some items together by ',', just like --sort=+ogen,-gen,path,rootid.
set-default [<subvolume>|<id> <path>] Set the default subvolume for the (mounted) filesystem.
Set the default subvolume for the (mounted) filesystem at <path>. This will hide the top-level subvolume (i.e. the one mounted with subvol=/ or subvolid=5). Takes action on next mount.
There are two ways how to specify the subvolume, by <id> or by the <subvolume> path. The id can be obtained from btrfs subvolume list, btrfs subvolume show or btrfs inspect-internal rootid.
show [options] <path> Show more information about a subvolume (UUIDs, generations, times, flags, related snapshots).
/mnt/btrfs/subvolume Name:                   subvolume UUID:                   5e076a14-4e42-254d-ac8e-55bebea982d1 Parent UUID:            - Received UUID:          - Creation time:          2018-01-01 12:34:56 +0000 Subvolume ID:           79 Generation:             2844 Gen at creation:        2844 Parent ID:              5 Top level ID:           5 Flags:                  - Snapshot(s):
-r|--rootid <ID> show details about subvolume with root <ID>, looked up in <path>
-u|--uuid UUID show details about subvolume with the given <UUID>, looked up in <path>
snapshot [-r] [-i <qgroupid>] <source> <dest>|[<dest>/]<name> Create a snapshot of the subvolume <source> with the name <name> in the <dest> directory.
If only <dest> is given, the subvolume will be named the basename of <source>. If <source> is not a subvolume, btrfs returns an error.
-r Make the new snapshot read only.
sync <path> [subvolid...] Wait until given subvolume(s) are completely removed from the filesystem after deletion. If no subvolume id is given, wait until all current deletion requests are completed, but do not wait for subvolumes deleted in the meantime.
-s <N> sleep N seconds between checks (default: 1)
The subvolume flag currently implemented is the ro property. Read-write subvolumes have that set to false, snapshots as true. In addition to that, a plain snapshot will also have last change generation and creation generation equal.
Read-only snapshots are building blocks fo incremental send (see btrfs-send(8)) and the whole use case relies on unmodified snapshots where the relative changes are generated from. Thus, changing the subvolume flags from read-only to read-write will break the assumptions and may lead to unexpected changes in the resulting incremental stream.
A snapshot that was created by send/receive will be read-only, with different last change generation, read-only and with set received_uuid which identifies the subvolume on the filesystem that produced the stream. The usecase relies on matching data on both sides. Changing the subvolume to read-write after it has been received requires to reset the received_uuid. As this is a notable change and could potentially break the incremental send use case, performing it by btrfs property set requires force if that is really desired by user.
Note The safety checks have been implemented in 5.14.2, any subvolumes previously received (with a valid received_uuid) and read-write status may exist and could still lead to problems with send/receive. You can use btrfs subvolume show to identify them. Flipping the flags to read-only and back to read-write will reset the received_uuid manually. There may exist a convenience tool in the future.
Example 1. Deleting a subvolume
If we want to delete a subvolume called foo from a btrfs volume mounted at /mnt/bar we could run the following:
btrfs subvolume delete /mnt/bar/foo
btrfs subvolume returns a zero exit status if it succeeds. A non-zero value is returned in case of failure.
mkfs.btrfs(8), mount(8), btrfs-quota(8), btrfs-qgroup(8), btrfs-send(8)
gh-config - Manage configuration for gh
gh config <command> [flags]
Display or change configuration settings for gh.
Current respected settings: - git_protocol: the protocol to use for git clone and push operations (default: "https") - editor: the text editor program to use for authoring text - prompt: toggle interactive prompting in the terminal (default: "enabled") - pager: the terminal pager program to send standard output to - http_unix_socket: the path to a unix socket through which to make HTTP connection - browser: the web browser to use for opening URLs
gh(1), gh-config-get(1), gh-config-list(1), gh-config-set(1)
SPFQUERY(1)            User Contributed Perl Documentation           SPFQUERY(1)
spfquery - checks if an IP address is an SPF-authorized SMTP sender for a domain
spfquery --mail-from|-m|--sender|-s email-address|domain --helo|-h hostname --ip|-i ip-address [OPTIONS]
spfquery --helo|-h hostname --ip|-i ip-address [OPTIONS]
spfquery --file|-f filename|- [OPTIONS]
spfquery --version|-V
spfquery --help
spfquery performs Sender Policy Framework (SPF) authorization checks based on the command-line arguments or data given in a file or on standard input.  For information on SPF see <http://www.openspf.org>.
The --mail-from form checks if the given ip-address is an authorized SMTP sender for the given envelope sender domain or email-address and "HELO" hostname (so-called "MAIL FROM" check).  If a domain is given, "postmaster" will be substituted for the localpart.
The --helo form checks if the given ip-address is an authorized SMTP sender for the given "HELO" hostname (so-called "HELO" check).
The --file form reads "ip-address sender-address helo-hostname" tuples from the file with the specified filename, or from standard input if filename is -.
The --version form prints version information of spfquery.  The --help form prints usage information for spfquery.
The --mail-from, --helo, and --file forms optionally take any of the following additional OPTIONS:
--debug Print out debug information.
--default-explanation string Use the specified string as the default explanation if the SPF record does not specify an explanation string itself.
--guess spf-terms Use spf-terms as a default record if no SPF record is found.  This is a non-standard feature.
--keep-comments --no-keep-comments Do (not) print any comments found when reading from a file or from standard input.
--local spf-terms Process spf-terms as local policy before resorting to a default result (the implicit or explicit "all" mechanism at the end of the domain's SPF record).  For example, this could be used for white- listing one's secondary MXes: "mx:mydomain.example.org".
--max-lookup-count n Perform a maximum of n SPF record lookups.  Defaults to 10.
--name hostname Use hostname as the hostname of the local system instead of auto- detecting it.
--override domain=spf-record --fallback domain=spf-record Set overrides and fallbacks.  Each option can be specified multiple times.  For example: "--override example.org='v=spf1 -all' --override '*.example.net'='v=spf1 a mx -all' --fallback example.com='v=spf1 -all'".  This is a non-standard feature.
--rcpt-to email-addresses Automatically allow the secondary MXes of the comma-separated list of email-addresses.
--sanitize --no-sanitize Do (not) sanitize the output by condensing consecutive white-space into a single space and replacing non-printable characters with question marks.  Enabled by default.
--trusted --no-trusted Do (not) perform "trusted-forwarder.org" accreditation checking. Disabled by default.  This is a non-standard feature.
pass      The specified IP address is an authorized mailer for the sender domain/address.
fail      The specified IP address is not an authorized mailer for the sender domain/address.
softfail  The specified IP address is not an authorized mailer for the sender domain/address, however the domain is still in the process of transitioning to SPF.
neutral   The sender domain makes no assertion about the status of the IP address.
unknown   The sender domain has a syntax error in its SPF record.
error     A temporary DNS error occurred while resolving the sender policy.  Try again later.
none      There is no SPF record for the sender domain.
0   pass
1   fail
2   softfail
3   neutral
4   unknown
5   error
6   none
spfquery -i 11.22.33.44 -m user@example.com -h spammer.example.net spfquery -f test_data echo "127.0.0.1 user@example.com helohost.example.com" | spfquery -f -
Mail::SPF::Query, spfd
This version of spfquery was written by Wayne Schlitt <wayne@midwestcs.com>.
This man-page was written by Julian Mehnle <julian@mehnle.net>, based on a man-page written by S. Zachariah Sprackett for an older version of spfquery.