Split action handling into plugin classes

This allows mail plugins to define their own actions that they handle,
and dispatches handling an action to the first plugin that declares it
can handle it.  Using this, the handling of correspond and comment, as
well as the "unsafe" actions take and resolve, are moved out into their
own plugins.

As part of this, ParseCcAddressesFromHead, which was only called during
ticket creation, is inlined and placed in _HandleCreate in the new
RT::Interface::Email::Action::Defaults plugin, which is always enabled.

The $UnsafeEmailCommands configuration is now accomplished by adding
Action::Take and/or Action::Resolve to @MailPlugins.

1 files changed, 9 insertions, 9 deletions

diff --git a/bin/rt-mailgate.in b/bin/rt-mailgate.in
index 9b0b8d4601..8498243a59 100644
--- a/bin/rt-mailgate.in
+++ b/bin/rt-mailgate.in
@@ -329,15 +329,15 @@ Usual invocation (from MTA):
 
 =item C<--action>
 
-Specifies what happens to email sent to this alias.  The avaliable
-basic actions are: C<correspond>, C<comment>.
-
-
-If you've set the RT configuration variable B<< C<UnsafeEmailCommands> >>,
-C<take> and C<resolve> are also available.  You can execute two or more
-actions on a single message using a C<-> separated list.  RT will execute
-the actions in the listed order.  For example you can use C<take-comment>,
-C<correspond-resolve> or C<take-comment-resolve> as actions.
+Specifies what happens to email sent to this alias.  The avaliable basic
+actions are: C<correspond>, C<comment>.  Additional actions, such as
+C<take> or C<resolve>, may be available depending on your local
+C<@MailPlugins> configuration.
+
+You can execute two or more actions on a single message using a C<->
+separated list.  RT will execute the actions in the listed order.  For
+example you can use C<take-comment>, C<correspond-resolve> or
+C<take-comment-resolve> as actions.
 
 Note that C<take> and C<resolve> actions ignore message text if used
 alone.  Include a  C<comment> or C<correspond> action if you want RT