On Wed, Dec 15, 2010 at 10:51:13AM -0500, Wietse Venema wrote:
> Spacelee:
> > hi everything, I met a problem recently because we need to add a new
> > function to our product.
> > the problem is for each valid incoming email, we need to call a script to
> > insert it to different databases, someo
Spacelee:
> hi everything, I met a problem recently because we need to add a new
> function to our product.
> the problem is for each valid incoming email, we need to call a script to
> insert it to different databases, someone said I could add this to the
> /etc/aliases, like : b...@example.org: "
On 15/12/2010, at 7:00 PM, Victor Duchovni wrote:
> On Wed, Dec 15, 2010 at 05:36:19PM +1100, James Gray wrote:
>
>> At the risk of being blacklisted on this rather "robust" forum,
>> when I've needed a DB backend for mail I've invariably ended up
>> with a product designed for that purpose. Th
On Wed, Dec 15, 2010 at 05:36:19PM +1100, James Gray wrote:
> At the risk of being blacklisted on this rather "robust" forum,
> when I've needed a DB backend for mail I've invariably ended up
> with a product designed for that purpose. The idea of piping or
> scripting may seem desirable at first
On 15/12/2010, at 2:21 PM, Spacelee wrote:
> hi everything, I met a problem recently because we need to add a new function
> to our product.
> the problem is for each valid incoming email, we need to call a script to
> insert it to different databases, someone said I could add this to the
> /e
hi everything, I met a problem recently because we need to add a new
function to our product.
the problem is for each valid incoming email, we need to call a script to
insert it to different databases, someone said I could add this to the
/etc/aliases, like : b...@example.org: "|/tmp/somescripts.sh
