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

Skylos skylos at gmail.com
Tue Mar 2 20:07:52 PST 2010

Heh, I think he meant to *receive* email with his application, not send it.
  "we want to automate the process of receiving updates from users via


On Tue, Mar 2, 2010 at 6:47 PM, Meryll Larkin <alwanza at yahoo.com> wrote:

> Maybe I'm assuming too much again....  If the Web app and Database are
> hosted by the same ISP, the ISP usually provides information about how the
> Database can be accessed inside a script (at least provides you with your
> account details - username password, the name/address of database and which
> modules are available to reach it).
> If the Web app and Database are not hosted with the same ISP, I could
> understand you might need to parse the email if the ports you need to
> communicate directly with the database aren't open between Web app server
> and DB server.
> Meryll
> _____________________________________________________________
> 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/

"If only I could get rid of hunger by rubbing my belly" - Diogenes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/spug-list/attachments/20100302/b5c52e4b/attachment.html>

More information about the spug-list mailing list