Thank you for the tip Thomas.

I did not think of going the policy route. I will dust off my Pascal routinges and set to work. Because all of the messages come from the same source and should be similarly structured, it should be a relatively straightforward operation.

An appeal for help from the community..

In one of our offices we have a multifunction machine that acts as copier, scanner, fax etc. Received faxes are set to be emailed to a special email alias that is assigned to the person tasked to distribute the messages to the intended recipients. FYI, the server was running the latest Mercury32 and all clients run PMail. The mail sent by the device does not have a valid date. We have raised this with the suppliers who have submitted an error report to the manufacturers, but I am not holding my breath. My best hope is that a software solution on the server may be possible.

====

<scan><scan><bfaxin>====</bfaxin>@treverton.co.za&gt;</scan>@samsung&gt;</scan>@samsung>

<scan><scan><bfaxin></bfaxin></scan></scan>

As can be seen from the above extract, the message is sent without any timestamp. Thus, theses received faxes are VERY hard to keep track of.

Does anyone have any ideas on how to craft a script to be called by Mercury that could add a time- and date-stamp on messages from a particular origin?

First prize (but probably asking too much) would be to be able to take the Fax Job : Received info, together with the information on the line that follows that one and make that the Subject line of the email message.@treverton.co.za>@samsung>@samsung>

<scan><scan><bfaxin>Any ideas would be appreciated.. </bfaxin></scan></scan>

@treverton.co.za>@samsung>@samsung>

> An appeal for help from the community.. In one of our offices we have
> a multifunction machine that acts as copier, scanner, fax etc.
> Received faxes are set to be emailed to a special email alias that is
> assigned to the person tasked to distribute the messages to the
> intended recipients. FYI, the server was running the latest Mercury32
> and all clients run PMail. The mail sent by the device does not have a
> valid date. We have raised this with the suppliers who have submitted
> an error report to the manufacturers, but I am not holding my breath.
> My best hope is that a software solution on the server may be
> possible.

What you really need is to convert the date on the received line to a Date: string via a policy.  A policy can pass the message body to a program that parses the Received: line after the ";" to get the date string and convert it to Date:  5 Aug 2009 12:28:54 +0200 and then paste this in the headers so it looks like this.  This can be done is most any program language and I'd do it in QB45 because that's the easiest for me.  ;-)  I'm sure that there are many other coders that can do this more efficiently that I can.  

Return-path: <scan@samsung>
Received: from SEC0015990663BF (172.24.128.103) by server.treverton.co.za
 (Mercury/32 v4.71) with ESMTP ID MG003572; 5 Aug 2009 12:28:54 +0200
From:<scan@samsung>
Message-Id: <313490.0006@t37>
To: <bfaxin@treverton.co.za>
Subject:=?utf-8?B?RmF4IEZvcndhcmQgZnJvbSBhIFNhbXN1bmcgTUZQ?=
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="----=_NextPart_4ce0_5ea8_1134.7d39"
Content-features: (& (& (dpi=300) (dpi-xyratio=[300/300])) (image-coding=MH))
Date:  5 Aug 2009 12:28:54 +0200


>
> ====
>
> Return-path: <scan@samsung>
> Received: from SEC0015990663BF (172.24.128.103) by server.treverton.co.za
>  (Mercury/32 v4.71) with ESMTP ID MG003572; 5 Aug 2009 12:28:54 +0200
> From:<scan@samsung>
> Message-Id: <313490.0006@t37>
> To: <bfaxin@treverton.co.za>
> Subject:=?utf-8?B?RmF4IEZvcndhcmQgZnJvbSBhIFNhbXN1bmcgTUZQ?=
> MIME-Version: 1.0
> Content-Type: MULTIPART/MIXED; BOUNDARY="----=_NextPart_4ce0_5ea8_1134.7d39"
> Content-features: (& (& (dpi=300) (dpi-xyratio=[300/300])) (image-coding=MH))
>
> ------=_NextPart_4ce0_5ea8_1134.7d39
> Content-Type: TEXT/PLAIN; charset=UTF-8
>
> Please open the attached document. It contains a copy of a Transmitted/Received Fax. For more information on Samsung products and solutions, please visit http://www.samsungprinter.com.
> Fax Job : Receive
>           0116052429
>
> ------=_NextPart_4ce0_5ea8_1134.7d39
> Content-Type: image/tiff
> Content-Transfer-Encoding: BASE64
> Content-Disposition: attachment; filename="Trevert_051225_001.tif"
> ====
>
> As can be seen from the above extract, the message is sent without any
> timestamp. Thus, theses received faxes are VERY hard to keep track of.
> Does anyone have any ideas on how to craft a script to be called by
> Mercury that could add a time- and date-stamp on messages from a
> particular origin? First prize (but probably asking too much) would be
> to be able to take the Fax Job : Received info, together with the
> information on the line that follows that one and make that the
> Subject line of the email message.
>
> Any ideas would be appreciated..
>
>