The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
 / 
App-WHMCSUtils-0.012
River stage one • 1 direct dependent • 1 total dependent
++
/ whmcs-send-verification-emails

NAME

whmcs-send-verification-emails - Send verification emails for clients who have not had their email verified

VERSION

This document describes version 0.012 of whmcs-send-verification-emails (from Perl distribution App-WHMCSUtils), released on 2021-11-30.

SYNOPSIS

Usage:

% whmcs-send-verification-emails [--action=str] [--admin-password=str] [--admin-username=str] [--config-path=path|-c|--no-config|-C] [--config-profile=profile|-P] [--db-host=str] [--db-name=str] [--db-pass=str] [--db-port=net::port] [--db-user=str] [--debug|--log-level=level|--quiet|--trace|--verbose] [--dry-run|-n] [--format=name|--json] [--hook-set-sender-email=any] [--include-active|--exclude-active] [--include-client-ids-from=filename] [(--include-client-ids=uint)+] [--include-inactive|--exclude-inactive] [--limit=uint] [--mech-user-agent=str] [--(no)naked-res] [--no-env] [--page-result[=program]|--view-result[=program]] [--random|--no-random|--norandom] [--url=url] [--hook-set-sender-email-json=json] [--include-client-ids-json=json] [--url-json=json] [--list-clients]

DESCRIPTION

WHMCS does not yet provide an API for this, so we do this via a headless browser.

OPTIONS

* marks required options.

Main options

--action=s

Default value:

 "send-verification-emails"

Valid values:

 ["list-clients","send-verification-emails"]

The default action is to send verification emails. You can also just list the clients who haven't got their email verified yet.

--admin-password=s*
--admin-username=s*
--db-host=s

Default value:

 "localhost"
--db-name=s*
--db-pass=s
--db-port=s

Default value:

 3306
--db-user=s
--hook-set-sender-email-json=s

Hook to set sender email for every email (JSON-encoded).

See --hook-set-sender-email.

--hook-set-sender-email=s

Hook to set sender email for every email.

Hook will receive these arguments:

    ($client_rec, $orig_sender_email)

`$client_rec` is a hash containing client record fields, e.g. `id`, `email`, `firstname`, `lastname`, etc. `$orig_sender_email` is the original sender email setting (`Email` setting in the configuration table).

Hook is expected to return the sender email.

--include-client-ids-from=s
--limit=s

Only process this many clients then stop.

--list-clients

Shortcut for --action=list-clients.

See --action.

--mech-user-agent=s
--no-random
--url-json=s

See --url.

--url=s*

It should be without `/admin` part, e.g.:

    https://client.mycompany.com/

Configuration options

--config-path=s, -c

Set path to configuration file.

--config-profile=s, -P

Set configuration profile to use.

--no-config, -C

Do not use any configuration file.

Environment options

--no-env

Do not read environment for default options.

Filtering options

--exclude-active
--include-client-ids-json=s

See --include-client-ids.

--include-client-ids=s@

Can be specified multiple times.

--include-inactive

Whether to include inactive clients.

Logging options

--debug

Shortcut for --log-level=debug.

--log-level=s

Set log level.

--quiet

Shortcut for --log-level=error.

--trace

Shortcut for --log-level=trace.

--verbose

Shortcut for --log-level=info.

Output options

--format=s

Choose output format, e.g. json, text.

Default value:

 undef
--json

Set output format to json.

--naked-res

When outputing as JSON, strip result envelope.

Default value:

 0

By default, when outputing as JSON, the full enveloped result is returned, e.g.:

    [200,"OK",[1,2,3],{"func.extra"=>4}]

The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:

    [1,2,3]
--page-result

Filter output through a pager.

--view-result

View output using a viewer.

Other options

--dry-run, -n

Run in simulation mode (also via DRY_RUN=1).

--help, -h, -?

Display help message and exit.

--version, -v

Display program's version and exit.

COMPLETION

This script has shell tab completion capability with support for several shells.

bash

To activate bash completion for this script, put:

 complete -C whmcs-send-verification-emails whmcs-send-verification-emails

in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is recommended, however, that you install modules using cpanm-shcompgen which can activate shell completion for scripts immediately.

tcsh

To activate tcsh completion for this script, put:

 complete whmcs-send-verification-emails 'p/*/`whmcs-send-verification-emails`/'

in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is also recommended to install shcompgen (see above).

other shells

For fish and zsh, install shcompgen as described above.

CONFIGURATION FILE

This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.

By default, these names are searched for configuration filenames (can be changed using --config-path): ~/.config/whmcsutils.conf, ~/whmcsutils.conf, or /etc/whmcsutils.conf.

All found files will be read and merged.

To disable searching for configuration files, pass --no-config.

You can put multiple profiles in a single file by using section names like [profile=SOMENAME] or [SOMESECTION profile=SOMENAME]. Those sections will only be read if you specify the matching --config-profile SOMENAME.

You can also put configuration for multiple programs inside a single file, and use filter program=NAME in section names, e.g. [program=NAME ...] or [SOMESECTION program=NAME]. The section will then only be used when the reading program matches.

You can also filter a section by environment variable using the filter env=CONDITION in section names. For example if you only want a section to be read if a certain environment variable is true: [env=SOMEVAR ...] or [SOMESECTION env=SOMEVAR ...]. If you only want a section to be read when the value of an environment variable equals some string: [env=HOSTNAME=blink ...] or [SOMESECTION env=HOSTNAME=blink ...]. If you only want a section to be read when the value of an environment variable does not equal some string: [env=HOSTNAME!=blink ...] or [SOMESECTION env=HOSTNAME!=blink ...]. If you only want a section to be read when the value of an environment variable includes some string: [env=HOSTNAME*=server ...] or [SOMESECTION env=HOSTNAME*=server ...]. If you only want a section to be read when the value of an environment variable does not include some string: [env=HOSTNAME!*=server ...] or [SOMESECTION env=HOSTNAME!*=server ...]. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.

To load and configure plugins, you can use either the -plugins parameter (e.g. -plugins=DumpArgs or -plugins=DumpArgs@before_validate_args), or use the [plugin=NAME ...] sections, for example:

 [plugin=DumpArgs]
 -event=before_validate_args
 -prio=99
 
 [plugin=Foo]
 -event=after_validate_args
 arg1=val1
 arg2=val2

which is equivalent to setting -plugins=-DumpArgs@before_validate_args@99,-Foo@after_validate_args,arg1,val1,arg2,val2.

List of available configuration parameters:

 action (see --action)
 admin_password (see --admin-password)
 admin_username (see --admin-username)
 db_host (see --db-host)
 db_name (see --db-name)
 db_pass (see --db-pass)
 db_port (see --db-port)
 db_user (see --db-user)
 format (see --format)
 hook_set_sender_email (see --hook-set-sender-email)
 include_active (see --exclude-active)
 include_client_ids (see --include-client-ids)
 include_client_ids_from (see --include-client-ids-from)
 include_inactive (see --include-inactive)
 limit (see --limit)
 log_level (see --log-level)
 mech_user_agent (see --mech-user-agent)
 naked_res (see --naked-res)
 random (see --no-random)
 url (see --url)

ENVIRONMENT

WHMCS_SEND_VERIFICATION_EMAILS_OPT => str

Specify additional command-line options.

FILES

~/.config/whmcsutils.conf

~/whmcsutils.conf

/etc/whmcsutils.conf

HOMEPAGE

Please visit the project's homepage at https://metacpan.org/release/App-WHMCSUtils.

SOURCE

Source repository is at https://github.com/perlancar/perl-App-WHMCSUtils.

AUTHOR

perlancar <perlancar@cpan.org>

CONTRIBUTING

To contribute, you can send patches by email/via RT, or send pull requests on GitHub.

Most of the time, you don't need to build the distribution yourself. You can simply modify the code, then test via:

 % prove -l

If you want to build the distribution (e.g. to try to install it locally on your system), you can install Dist::Zilla, Dist::Zilla::PluginBundle::Author::PERLANCAR, and sometimes one or two other Dist::Zilla plugin and/or Pod::Weaver::Plugin. Any additional steps required beyond that are considered a bug and can be reported to me.

COPYRIGHT AND LICENSE

This software is copyright (c) 2021, 2019, 2018, 2017 by perlancar <perlancar@cpan.org>.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

BUGS

Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-WHMCSUtils

When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.