On 05-Sep-2001 CLEMENT Francis wrote:
> Hello, Davide
>
> In processing 'external' command in mailproc.tab files, the @@TMPFILE and
> @@FILE variables create a 'no' standard message file.
>
> But most of the available packages/tools/... on the net that are designed to
> run with others mta (sendmail/qmail/...) assume to find the standard message
> file format (same format as xmail saves in the mailbox).
>
> So if anyone wants to use a 'standard' message file processing tool (like
> ecartis-listar / majordomo/ filters/...) he have to create a front end
> 'conversion' program to process the xmail @@TMPFILE/@@FILE format and send
> to the real tool a 'correctly' formatted message file.
> It need more 'process' time ...
>
> I think that it will be a good new feature to have xmail generate 'standard'
> mail files for 'external' like commands (not only in mailproc.tab but also
> in filters .tab files, ...) to simplify interface with existing tools.
>
> Two suggestions to enable this in xmail :
> - First one is to patch xmail to generate 'standard' mail files then
> options @@TMPFILE or @@FILE are used. Current tools writed for xmail will
> need to be 'rewritten' to handle new file format.
> - Second option is to add two new @@ args (eg : @@TMPSTDMSG and @@STDMSG)
> that will tell xmail to create 'standard' messages files.
>
> (The second option have my preferrence)
>
> What do you think ?
The correct thing to do would be to split the actual message in two files :
1) the raw message file
2) an info/header file
Has someone ever asked why the presence of the /info directory inside the queue tree ?
This will be done but it's not an easy fix coz there're a lot of places to be patched.
So, for now We've to create the raw message file by hand.
Question :
What is the better place to put such code ?
Do We've 1) to patch a server code or 2) to code a little front/back end ?
My answer is 2) 24 hours/day - seven days/week
- Davide
