REPORT_MAILX.CONF(5)

πŸ“¦
version 2.17.15 Β· 3 versions
, in opensuse-leap 16.0

πŸŽ€ REPORT_MAILX.CONF(5) πŸŽ€

okay bestie, this is the manual page for report_mailx.conf, the config file for libreport. It’s giving β€œsmall file, big main character energy” πŸ’…

πŸ’– NAME πŸ’–

report_mailx.conf β€” configuration file for libreport.

✨ DESCRIPTION ✨

This configuration file specifies which of the work flow definitions are applicable to analyzing problems and send information via email.

All applicable work flows are presented to users in User Interface as possibilities for processing any problems. A particular work flow becomes applicable if its conditions are satisfied.

This configuration file consists from condition lines. Each condition line must start with EVENT=workflow_NAME, where workflow_ is a constant prefix and workflow_NAME is the base name of the path to the reporting work flow configuration file.

The rest of the condition line has the form VAR=VAL, VAR!=VAL, or VAL~=REGEX, where VAR is the name of a problem directory element to be checked (for example, "executable", "package", hostname" etc). A condition can have as many element checks as it needs.

All condition lines in this configuration file are commented out by default. Therefore all applicable work flows from this file are not presented to users in User Interface. To enable this extension, uncomment all condition lines in this configuration file.

⚠️ default vibe check: commented out means not showing up in the UI. Uncomment the condition lines when you want this extension doing its thing πŸ’–

🌸 EXAMPLES 🌸

Condition line:

EVENT=workflow_MailxCCpp analyzer=CCpp

The condition line above expects existence of /usr/share/libreport/workflows/workflow_MailxCCpp.xml.

πŸ¦‹ SEE ALSO πŸ¦‹

report-gtk(1)

πŸ‘‘ AUTHOR πŸ‘‘

  • ABRT team

This page is from LIBREPORT 2.17.15, dated 07/15/2024 β€” mwah, bestie, go uncomment responsibly πŸ’‹βœ¨