Re: 'forking' transactions

2008-01-28 Thread Chris Lewis
Jared Johnson wrote: Peter J. Holzer wrote: That's why I wrote cf_wrapper (it's in the contrib directory), which checks the results for all recipients and returns a temporary error when they don't agree - when the client resends the message, it can "split" them into two groups with consistent re

Re: 'forking' transactions

2008-01-28 Thread Jared Johnson
Peter J. Holzer wrote: That's why I wrote cf_wrapper (it's in the contrib directory), which checks the results for all recipients and returns a temporary error when they don't agree - when the client resends the message, it can "split" them into two groups with consistent responses. Who is "the

prepending to message body

2008-01-28 Thread Jared Johnson
What's the best way to do this? Is there any way to avoid forcing it into spooling to disk? -Jared Johnson Software Developer and Support Engineer Network Management Group, Inc. 620-664-6000 x118 -- Inbound and outbound email scanned for spam and viruses by the DoubleCheck Email Manager: http:

Re: 'forking' transactions

2008-01-28 Thread Chris Lewis
Chris Lewis wrote: Jared Johnson wrote: Peter J. Holzer wrote: That's why I wrote cf_wrapper (it's in the contrib directory), which checks the results for all recipients and returns a temporary error when they don't agree - when the client resends the message, it can "split" them into two group

Re: prepending to message body

2008-01-28 Thread John Peacock
Jared Johnson wrote: > What's the best way to do this? Is there any way to avoid forcing it > into spooling to disk? Please describe what you are trying to do, rather than how you think you need to do it. I can read that question several different ways, each with it's own solution. John

Re: prepending to message body

2008-01-28 Thread Jared Johnson
John Peacock wrote: Please describe what you are trying to do, rather than how you think you need to do it. I can read that question several different ways, each with it's own solution. Thanks for the response, I'll elaborate: I'm reproducing spamassassin's "report_safe" feature (e.g. a m

qpsmtpd-async and dnsbl

2008-01-28 Thread prof . freud
Dear friends, I filed this also under code.google.com/p/smtpd as an 'Issue', but it looked so deserted there. What steps will reproduce the problem? qpsmtpd-async(rev 838) with dnsbl plugin enabled What is the expected output? What do you see instead? 15958 Plugins already loaded 15958 running p