Mailing-List: contact server-user-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "James Users List" <server-user@james.apache.org>
Received-SPF: pass (nike.apache.org: domain of apache@bago.org designates
 74.125.82.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20cf304345becfd096049a25d73d@google.com>
References: <20cf304345becfd096049a25d73d@google.com>
Date: Tue, 18 Jan 2011 23:09:32 +0100
Message-ID: <AANLkTim2qocEaS7kjEiHMCMCiAq6DU_oVLuQFJrPcUHc@mail.gmail.com>
Subject: Re: SMTP for user->app notification
From: Stefano Bagnara <apache@bago.org>
To: James Users List <server-user@james.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2011/1/18  <cstansbury@gmail.com>:
> I'm the developer of a web-based application and am looking into what it
> would take for me to be able to provide each of my users with their own
> application-specific email address so that they could send email to my site
> that would then reformat the message into something more appropriate (much
> like Posterous allows you to add blog entries via email).
>
> Is this a "use case" that is common for James, and if not, how easy is it to
> hook into the framework system so that I don't have to poll a database
> constantly (but can instead receive email "events" and react accordingly)?

Yes. I have had this very use case solved by writing a custom mailet
that does an HTTP call to the final website after having parsed the
message.
When interacting with a website I prefer to do this "mail to web"
translation instead of embedding james in the application server and
use simple java calls.

At the most extreme you could write a simple mailet that POST the
whole mimemessage AS-IS to a given use and leave all of the logic on
the web side: this is up to you.

Stefano

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org