SPUG: standard way for a web app to handle incoming email?

Phil Mitchell phil at 2people.org
Tue Mar 2 22:36:43 PST 2010

You are all awesome! Thank you for all this kind attention -- I apologize
for posting and then running off to a late meeting.

It looks like the combination of fetchmail and procmail is exactly what I
was needing (and good to know about other options, like Net::SMTP, too ...)

It's kind of an interesting challenge - we want to make it as frictionless
as possible for govt agencies to respond to the hazard report emails that we
send out from Bikewise. So we're going to be implementing a very simple
"form" that gets submitted simply by replying to the email.

If anyone's done something similar and has pearls of wisdom, I'd welcome any
tips ..

Thanks again!


On Tue, Mar 2, 2010 at 4:38 PM, Phil Mitchell <phil at 2people.org> wrote:

> For my perl/catalyst web app, Bikewise.org, we want to automate the process
> of receiving updates from users via email. IOW, user sends email to
> update at bikewise.org and we parse the contents and update the database
> accordingly.
> As I sat down to think this through, I realized I have no idea how this is
> done. The app is hosted on a virtual server, and relies on a separate mail
> server that's run by my hosting provider. Do I need access to the raw mail
> files on the server? Is there a standard way to set this up?
> --
> Bikewise: http://www.bikewise.org
> _____________________________________________________________
> Seattle Perl Users Group Mailing List
>     POST TO: spug-list at pm.org
> SUBSCRIPTION: http://mail.pm.org/mailman/listinfo/spug-list
>    MEETINGS: 3rd Tuesdays
>    WEB PAGE: http://seattleperl.org/

Bikewise: http://www.bikewise.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/spug-list/attachments/20100302/bf235b4f/attachment-0001.html>

More information about the spug-list mailing list