Consider the following ticket file as an example:
smtp://foo:bar@* smtp://bar:firstname.lastname@example.org *://baz:qux@* *://quux:email@example.com
Now, running mailutils wicket smtp://firstname.lastname@example.org will show:
which means that this URL matches the line 2 in your .mu-tickets file. The wicket command does not show the actual matching line to avoid revealing eventual security-sensitive information. You can instruct it to do so using the --verbose (-v) option:
$ mailutils wicket -v smtp://email@example.com smtp://firstname.lastname@example.org: /home/user/.mu-tickets:2: smtp://bar:***@gnu.org
As you see, even in that case the tool hides the actual password part by replacing it with three asteriscs. If you are working in a secure environment, you can tell mailutils wicket to show passwords as well, by giving the -v option twice.
A counterpart of --verbose is the --quite (-q) option, which instructs wicket to suppress any output, excepting error messages. This can be used in scripts, which analyze the mailutils exit code to alter the control flow.
The mailutils wicket tool exits with code 0 if all URLs were matched and with code 1 if some of them were not matched in the ticket file. If an error occurred, the code 2 is returned.