<div dir="ltr">Since action is required (or at least documented as such) it seems that<br> --action correspond --extension action<br>should default to an action of correspond for messages without an extension.<br>Thusly <a href="mailto:rt@example.com">rt@example.com</a> an <a href="mailto:rt%2Bcorrespond@example.com">rt+correspond@example.com</a> are equivalent,<br>
whereas <a href="mailto:rt%2Bcomment@example.com">rt+comment@example.com</a> is not.<br><br>The simple patch below (3.8.0) simply falls back to the value supplied on the<br>command-line if EXTENSION is undef. This should work for queue and action,<br>
and ticket will simply remain null; though a warning may be raised about<br>undefined value.<br><br>--- /opt/rt3/bin/rt-mailgate~ 2008-08-02 10:58:26.000000000 -0400<br>
+++ /opt/rt3/bin/rt-mailgate 2008-08-11 14:30:24.000000000 -0400<br>@@ -89,7 +89,7 @@<br> };<br> <br> if ( ($opts{'extension'} || '') =~ /^(?:action|queue|ticket)$/i ) {<br>- $args{ lc $opts{'extension'} } = $ENV{'EXTENSION'};<br>
+ $args{ lc $opts{'extension'} } = $ENV{'EXTENSION'} || $opts{$opts{'extension'}};<br> } elsif ( $opts{'extension'} && $ENV{'EXTENSION'} ) {<br> print STDERR "Value of the --extension argument is not action, queue or ticket"<br>
.", but environment variable EXTENSION is also defined. The former is ignored.\n";<br><br>-- <br>Cambridge Energy Alliance: Save money & the planet<br>
</div>