1REPORTER-MAILX(1) LIBREPORT MANUAL REPORTER-MAILX(1)
2
3
4
6 reporter-mailx - Sends contents of a problem directory via email.
7
9 reporter-mailx [-v] -d DIR [-c CONFFILE] [-F FMTFILE]
10
12 The tool reads a problem directory, composes an email message from the
13 directory contents, and uses mailx to send the message to specified
14 recipient.
15
16 Properties of email messages can be specified in a configuration file,
17 and via environment variables.
18
19 Configuration file
20 Configuration file contains entries in a format "Option = Value".
21
22 The options are:
23
24 Subject
25 The subject of the email message.
26
27 EmailFrom
28 The sender of the email message.
29
30 EmailTo
31 The recipient of the email message.
32
33 SendBinaryData
34 Use yes/true/on/1 to attach all binary files from the problem
35 directory to the email. This can cause the emails to be very large.
36
37 Formatting configuration files
38 Lines starting with # are ignored.
39
40 Lines can be continued on the next line using trailing backslash.
41
42 Format:
43
44 "%summary
45 subject format"
46
47 "section
48 element1[,element2]..." The literal text line to be added to email.
49 Can be empty. (Empty lines are NOT ignored!)
50
51 Subject format is a line of text, where %element% is replaced by
52 text element's content, and [[...%element%...]] block is used only if
53 %element% exists. [[...]] blocks can nest.
54
55 Sections can be:
56 - %summary: email subject format string.
57 - %attach: a list of elements to attach.
58 - text, double colon (::) and the list of comma-separated elements.
59
60 Elements can be:
61 - problem directory element names, which get formatted as
62 <element_name>: <contents>
63 or
64 <element_name>:
65 :<contents>
66 :<contents>
67 :<contents>
68 - problem directory element names prefixed by "%bare_",
69 which is formatted as-is, without "<element_name>:" and colons
70 - %oneline, %multiline, %text wildcards, which select all corresponding
71 elements for output or attachment
72 - %binary wildcard, valid only for %attach section, instructs to attach
73 binary elements
74 - problem directory element names prefixed by "-",
75 which excludes given element from all wildcards
76
77 Nonexistent elements are silently ignored.
78 If none of elements exists, the section will not be created.
79
80 Integration with ABRT events
81 reporter-mailx can be used as a reporter, to allow users report
82 problems via email when they decide to do it. This usage is
83 pre-configured in /etc/libreport/events.d/mailx_event.conf:
84
85 EVENT=report_Mailx reporter-mailx
86
87 It can also be used to notify administrator automatically when a
88 problem happens. When this is desired, modify the event configuration
89 file to run the tool on the post-create event:
90
91 EVENT=post-create reporter-mailx
92
94 -d DIR
95 Path to problem directory.
96
97 -c CONFFILE
98 Path to configuration file. When used in ABRT event system, the
99 file contains site-wide configuration. Users can change the values
100 via environment variables.
101
102 -F CONF_FORMAT_FILE Formatting file for an email.
103
105 Environment variables take precedence over values provided in the
106 configuration file.
107
108 Mailx_Subject
109 Subject of the email message.
110
111 Mailx_EmailFrom
112 Sender of the email message.
113
114 Mailx_EmailTo
115 Recipient of the email message. If nor the environment variable nor
116 the corresponding option is defined, the message is send to
117 "root@localhost".
118
119 Mailx_SendBinaryData
120 Use yes/true/on/1 to attach all binary files from the problem
121 directory to the email.
122
124 /usr/share/libreport/conf.d/plugins/mailx.conf
125 Readonly default configuration files.
126
127 /etc/libreport/plugins/mailx.conf
128 Configuration files.
129
131 mailx_event.conf(5), mailx.conf(5), report_mailx.conf(5)
132
134 ยท ABRT team
135
136
137
138LIBREPORT 2.1.11.1 11/13/2018 REPORTER-MAILX(1)