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

Andrew Sweger andrew at sweger.net
Tue Mar 2 17:06:18 PST 2010

Oh yeah. I'll second the suggestion for procmail. But I usually let
fetchmail retrieve the messages from the real mail server and then it
hands it off to procmail for intelligent handling. I love procmail. I
haven't touched its recipe file in over a year, totally forgot all the
work it's doing.

(Hey, look! I used "its" and "it's" correctly. Go me.)

On Tue, 2 Mar 2010, C.J. Adams-Collier wrote:

> I've always liked procmail.  Set up a mailbox for the account and have
> your MDA deliver to procmail.  add different procmail rules to fire off
> different scripts based on the content of the subject, To_ field, From
> field, etc.
> http://pm-doc.sourceforge.net/
> Cheers,
> C.J.
> On Tue, 2010-03-02 at 16:38 -0800, Phil Mitchell 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/

Andrew B. Sweger -- The great thing about multitasking is that several
                                things can go wrong at once.

More information about the spug-list mailing list