Michael Carmack writes:
==
Meanwhile, there is more output from thecourierfilter start trace
==
[EMAIL PROTECTED] strace -vfp 1565
Process 1565 attached
Now, try attaching strace to the root perlfilter after you start
everything, but before you run courierfilter stop.
Therein lies the problem: Whenever I strace it, whether it's before or
after the courierfilter stop, it never fails to stop. So I cannot catch
anything misbehaving via strace.
Michael Carmack writes:
Now, try attaching strace to the root perlfilter after you start
everything, but before you run courierfilter stop.
Therein lies the problem: Whenever I strace it, whether it's before or
after the courierfilter stop, it never fails to stop. So I cannot catch
Olivier Sannier wrote:
Gordon Messmer wrote:
Olivier Sannier wrote:
Gordon Messmer wrote:
You can get third-party software to do that. Once such solution is
pythonfilter, which I wrote:
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/
Sam,
I'd like to feed back that I just wasted about three hours trying to figure
out why I was getting 550 User unknown errors from my Courier server
when submitting messages for a (newly created) local user who has 4 dashes
in their name. This 3 dashes limit isn't documented anywhere but in
Julian Mehnle writes:
Sam,
I'd like to feed back that I just wasted about three hours trying to figure
out why I was getting 550 User unknown errors from my Courier server
when submitting messages for a (newly created) local user who has 4 dashes
in their name. This 3 dashes limit isn't
