Re: $transaction->body_filename;

2008-09-29 Thread Matt Sergeant
On Mon, 29 Sep 2008, Chris Lewis wrote: Matt told me that the body_filename not showing headers is actually an idiosyncracy of qpsmtpd-async, and behaves more like one would expect under qpsmtpd-forkserver etc. and that he had fixed that. Is that in SVN yet? Yes.

Re: $transaction->body_filename;

2008-09-29 Thread Chris Lewis
Matt told me that the body_filename not showing headers is actually an idiosyncracy of qpsmtpd-async, and behaves more like one would expect under qpsmtpd-forkserver etc. and that he had fixed that. Is that in SVN yet?

Re: $transaction->body_filename;

2008-09-16 Thread Chris Lewis
Matt Sergeant wrote: > On Mon, 15 Sep 2008 17:39:33 -0400, Chris Lewis wrote: >> Matt Sergeant wrote: >>> On Mon, 15 Sep 2008 16:40:24 -0400, Chris Lewis wrote: >>>> According to the documentation, when you call >>>> $transaction->body_filename, you ge

Re: $transaction->body_filename;

2008-09-15 Thread Matt Sergeant
On Mon, 15 Sep 2008 17:35:31 -0700, Ask Bjørn Hansen wrote: > > On Sep 15, 2008, at 13:40, Chris Lewis wrote: > >> According to the documentation, when you call >> $transaction->body_filename, you get a temporary file name that points >> at a file that contain

Re: $transaction->body_filename;

2008-09-15 Thread Ask Bjørn Hansen
On Sep 15, 2008, at 13:40, Chris Lewis wrote: According to the documentation, when you call $transaction->body_filename, you get a temporary file name that points at a file that contains the message. If you examine body_filename, it has no headers. It was made that way first because

Re: $transaction->body_filename;

2008-09-15 Thread Matt Sergeant
On Mon, 15 Sep 2008 19:30:11 -0400, Matt Sergeant wrote: >> Would it be worth considering have a data_filename() call, that does >> exactly the same thing as body_filename, but includes the headers too? >> Then we can fix the clamdscan plugin without breaking anything else. > > I thought about tha

Re: $transaction->body_filename;

2008-09-15 Thread Matt Sergeant
On Mon, 15 Sep 2008 17:39:33 -0400, Chris Lewis wrote: > Matt Sergeant wrote: >> On Mon, 15 Sep 2008 16:40:24 -0400, Chris Lewis wrote: >>> According to the documentation, when you call >>> $transaction->body_filename, you get a temporary file name that points &

Re: $transaction->body_filename;

2008-09-15 Thread Chris Lewis
Matt Sergeant wrote: > On Mon, 15 Sep 2008 16:40:24 -0400, Chris Lewis wrote: >> According to the documentation, when you call >> $transaction->body_filename, you get a temporary file name that points >> at a file that contains the message. If you examine body_filena

Re: $transaction->body_filename;

2008-09-15 Thread Matt Sergeant
On Mon, 15 Sep 2008 16:40:24 -0400, Chris Lewis wrote: > According to the documentation, when you call > $transaction->body_filename, you get a temporary file name that points > at a file that contains the message. If you examine body_filename, it > has no headers. > > The

$transaction->body_filename;

2008-09-15 Thread Chris Lewis
According to the documentation, when you call $transaction->body_filename, you get a temporary file name that points at a file that contains the message. If you examine body_filename, it has no headers. The clamdscan plugin uses body_filename to hand off to clamdscan. Which means that Cla