On Mon, 26 Nov 2007, Matic wrote:
> Damn, I thought you were a wizard! :(
> Seriously, i thought it might be some specific system code or whatever.
The execution was successful from a system POV (see the "0" before the
"250"). But your "whatever" was run in your filter, returned 250.
- Davi
Damn, I thought you were a wizard! :(
Seriously, i thought it might be some specific system code or whatever. I
will have to look at how to reproduce this error (exit code) in environmet
when loged in to console.
What exactly does -X- startup option do - beside the obvius "SMTPS - Disable
the ser
On Mon, 26 Nov 2007, Matic wrote:
> Hi,
>
> I have moved the script from mailproc.tab to filters.in.tab to se what
> would be in the filterslog
> and this is it:
>
> .. "in" "" "0" "250" "path to the executabale"
>
> what could cause the 250 exit code?
You ask me?!? That's the
Hi,
I have moved the script from mailproc.tab to filters.in.tab to se what
would be in the filterslog
and this is it:
.. "in" "" "0" "250" "path to the executabale"
what could cause the 250 exit code?
Davide wrote:
The environment used by a shell script running in your log
On Sun, 25 Nov 2007, Matic wrote:
> hi
>
> i have just moved one xmail server from win to linux and everything
> seems to work fine. I just have one glitch with one of the filters in
> mailproc
>
> in mailproc.tab i have
> "mailbox"
> "external" "path to bash script" "@@FILE" (real TABs)
