Bill Michell wrote:
Rodrigo Severo writes:
I tried to rewrite a message using a modified version of the
perlfilter to see what would happen and, surprise! It worked. But Mr.
Sam told me that it was just good luck. I'm not sure why.
This almost certainly has something to do with support either for
messages which are not pure 7-bit ASCII, or for MIME-encoded messages.
While it is pretty easy to rewrite ordinary test messages, anything that
has to cope with extended character sets or MIME has got its job cut out.
AFAIU, you mean that the "new" message I write might not to be right.
Well, if this is the only concearn, I think there is nothing to be
worried about. If someone decides to rewrite a message, it his job to
guarantee that the new message is right. In my case, Amavisd-new is
going to rewrite the message, and, AFAIK, Amavisd-new knows how to
rewrite a message ;)
James Baker believes the problem is that Courier keeps some kind of map
of the message (MIME parts, headers, etc) in memory and so any rewrite
might break this map.
Mr. Sam, could you please enlighten us?
Why can't a global filter rewrite a message?
If you could also point where in the code the problem resides it will
certainly get easier to find a solution.
TIA,
21 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: More concerni...
