Fwd: How must a mail interface behave?

Resending, just to bring some info (I must confess I don't even know
where do I have the prototype I mention in my own email... :'(


---------- Forwarded message ----------
From: Jorge Uriarte Aretxaga <[email protected]>
Date: Wed, Mar 21, 2007 at 12:59 AM
Subject: Re: How must a mail interface behave?
To: [email protected]

As I was trying to say...

I've started playing with a mail interface for Scarab. What I'd like is:
* Allow easy reporting of issues
* Allow adding comments to issues (I'd ideally just answer to a
notification to get it done).

I've got a prototype technical implementation in two hours with SubethaSMTP
Now, I'd like to get some feedback on how to define the "protocol"
between the user and Scarab.

Playing with the smtp implementation, is easy to parse the recipiento
to decide what's the intention of the user, so I'd like to know if
someone out there knows of a good schema to follow.

My own wanderings:

New issues sent to [email protected] (Example:
[email protected])
Maybe the issuetype should be the decision-maker, so:
    [type]@[module].[scarabserver] ([email protected])

 Another option:
    [type].[module]@myscarabserver

Comments and changes could be sent to the real issue:
 [issue]@module.myscarabserver
    or even
 [issue]@myscarabserver

 The text would simply be added as a comment, and we can handle
attachments if desired.
 Attributes would need need some kind of parsing, and a simple markup
to be defined.
 Also, I intend to answer with a preformatted confirmation mail, where
the user can fix the previous errors before the issue being modified.

 One thing I'm wondering; how should authentication behave? Maybe just
relaying in some predefined servers to be allowed to connect?

I know it's fuzzy, sorry. I did not intend to release this so soon,
Anyone out there with experience in this area can shed some light?

Regards,

_
Jorge





-- 
Jorge Uriarte Aretxaga
http://www.gailen.es
http://www.linkedin.com/in/jorgeuriarte