"Julian Mehnle" <[EMAIL PROTECTED]> writes:
> Lloyd Zusman [EMAIL PROTECTED] wrote:
>>
>> [ ... ]
>>
>> I just thought of a possible hack to handle this case. What do you
>> folks think of this idea? ...
>>
>> [ ... ]
>
> This is roughly what I'm planning to do in the *second* release of my
> Courier::Filter filter module framework, the *first* release of which I
> will finally release this week. I haven't decided yet what kind of
> modifications to allow (just adding headers, or replacing the whole
> header, or even replacing the whole message), and how to store the
> modification information (separate files, DBM database file, whatever).
> But I, too, think this is the best we can do to work around the
> limitation in the courierfilter interface.
GMTA!
I'm going to start out with just a list of headers to append, in a flat
file. In general, I only want to do minimal processing in courierfilter
modules, with the heavy lifting done in later steps. Therefore, all I
need is a header to trigger each subsequent rule which will do the more
ponderous processing (such as altering the entire message, etc.).
In other words, this will probably be sufficient for my purposes:
Step 1: courierfilter module writes a special header into the file
that's named after the message ID.
Step 2: early in maildrop, that header is appended to the appropriate
message.
Step 3: if desired, later in maildrop, a separate rule looks for that
header and if it matches, does more modification to the message.
Nonetheless, I'll be very interested to try out your second release,
once it comes out.
I'm currently in the process of implementing my own hack. I'll make it
available here when it's done.
Question: given a courier-processed email message that's going through
maildrop, is there a way to determine the full path name of that
message's data or control file under the COURIERTOP/var/msgq or
COURIERTOP/var/msgs tree? If so, I can use the basename of one of
those files as the name of the unique file that I create in the
/var/messageids directory. That would guarantee uniqueness, which
in the general case, the Message-ID header cannot do.
--
Lloyd Zusman
[EMAIL PROTECTED]
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
