[rt-devel] I'm a slacker (Announcing enhanced-mailgate)

[Jesse]

You've all probably noticed that the frequency of RT cvs commits
and version releases has slowed over the past 5-6 days.  For this, I'm
truly sorry.  Y'all just aren't reporting enough bugs (And yeah, there
are a few things that need fixing still, but they're relatively minor.
none are showstoppers).  

I've spent my days twiddling my thumbs and gazing out the window.
Well, to be totally honest, I've spent my days twiddling my thumbs and gazing
out the window and I've spent my nights putting together a little something
for a client that forms the basis of the NEW AND IMPROVED  enhanced-mailgate.

What, might you ask, is 'enhanced' in this context? Well, the new mail 
gateway sports the ability to define attributes of tickets on create
with RT-<foo>:  pseudo headers.  But that's not all, you can use the same
headers to update existing tickets by email.  Now, I can hear some of you 
thinking "But, email's so insecure"...which is why the enhanced mail gateway
will only perform these actions on tickets if the actor sends their command
messages with an openpgp-compatible signature that's trusted by the RT 
mailgate's local Gnu Privacy Guard install. 

You should keep in mind that this tool was written for a client and _is not_
currently part of RT proper.  It is likely that it will be rolled into a 
future release of RT...but for now, this is NOT freely supported software.
I'm really just not up to dealing with helping folks make this run in their 
environments. I've really just got to concentrate on paying contracts and 
getting 2.0.0 out there. 

        jesse



-- 
jesse reed vincent -- root at eruditorum.org -- jesse at fsck.com 
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

autoconf is your friend until it mysteriously stops working, at which 
point it is a snarling wolverine attached to your genitals by its teeth
 (that said, it's better than most of the alternatives)  -- Nathan Mehl
-------------- next part --------------
$header%
enhanced-mailgate is freely redistributable under the terms of Version 2 of the GNU GPL.
This product was written by Jesse Vincent <jesse at fsck.com> and works with RT 2.0, but is
not part of the RT distribution and IS NOT A FREELY SUPPORTED PRODUCT.  Patches are, of course,
appreciated.




enhanced-mailgate will take pseudo-headers in the message body to set parameters on 
new or existing tickets.

All pseudo-headers are prefixed with RT- and can be used to set parameters on 
new or existing tickets.

pseduo-headers are only searched for in the first chunk of the message body
and must come before any other content. They must appear one to a line.

The operations in pseudo-headers operate on the most recent rt-ticket: header.

If you turn on the $PermitReplayAttacks flag in enhanced-mailgate, RT will treat
the [tag #<int>] in the message's subject as an initial RT-Ticket: header.
This leaves you open to the possibility of a hostile user applying your updates
to another ticket.

If neither of these is given, a new ticket is created (like usual) and the 
commands operate on that new ticket.

requestor [+|-]<emailaddress>
cc [+|-]<emailaddress>
admincc [+|-]<emailaddress>
	For watcher operations, the operator defaults to +

subject <string>
owner <rt-user>
due <date>
starts <date>
started <date>
resolved <date>
status <status>
final-priority <int>
priority <int>
queue <queue id>
<keywordselect> [+|-]<keyword>
	For keyword selects, the operator defaults to +	


The following features aren't yet implemented in extended-mailgate

	time-worked [+|=]<int>
	time-left [+|-|=]<int>

		For time operations, the operator defaults to =

	<depends-on|member-of|refers-to|merge-into> <tid>


KNOWN ISSUES:

	It corrupts the pgp signed messages it sends back to you with your error message.
	It won't properly verify your signature if you pgp-sign a multipart message
	It won't deal with non-pgp-mime signatures