Re: ask-2.5.0-1 IOerror

In message <[email protected]>, Marco Paganini writes:
> Hi Erez,
> 
[...]
> > So you might want to check how ask.py behaves when it gets SIGINTR or
> > SIGPIPE, or an error reading from stdin, or an error writing to stdout.
> > This isn't an easy task b/c you have to consider that these errors or
> > signals could arrive at any time in ask.py's run.  Maybe you might setup
> > some sighandlers just to catch these situations, and later on figure out how
> > to gracefully recover from these situations; or block certain signals during
> > critical times.
> 
> The big problem really is that there's no way to "gracefully" recover when
> you're being executed from the .forward file. In the end, you'll have to
> return an error to the MTA, which will then soft or hard fail the delivery.

Right.  But in this case I was hand-feeding accumulated emails into a shell
script that ran spamc|ask|slocal, so there's no need to return an error to
the MTA, only the user who ran the script.

Erez.


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0