The immediate basics of opening and closing issues are currently coded and need no real command knowledge, other requests will have command based interface where the first line of the message or subject line identifies the user's intent. Planning a forum alias scheme for proper placement of issues within forums and once in place will make this more useable in its current form, only places issues in Top Forum in the meantime.
Parses mail from standard in as it's intended to tie into an alias, procmail, smartlist environment commonly used at W3C. Capable of sending email responses using any mail server, protocol, user account, etc. allowed and specified to application server in it's properties file for configuring any outbound mail from application run on the server this is being run on. Assumes a specified mail alias, from email application properties, or in the absense of a speciifed alias assumes the one it received the mail as responding address. Mail originating from system, not a direct response, will use email to come from database in existing and expected forms.***note to self: what to do if received as cc or bcc? use transfer header in place of to or a naming convention
Command with needed environment variables and starts java process. This uses the same application server environment, but unfortunately doesn't take advantage of persistence and class loading from the command prompt as the servlet based/initiated (including irc bot) application at present - plan to address this as mentioned in architecture discussionPlanned email features.