| The reason it isn't working is that ALL-IN-1 detects deferred mail by
looking for mesages that have a "sent" date but not a "posted"
(delivered) date. Unfortunately an MCD'd SENT message keeps its original
sent and posted dates, and the posted date is not cleared when the message
is deferred.
This should be fixed in a future release.
If this is causing the customer big problems then you might like to
look at modifying the EMMDEF form so that it checks for a posted date
(cab$.delivery) and clears it. If you do this you should be aware that
this field can be multivalued, ie some messages can have multiple
posted dates.
Andy
|
|
Andy,
Thanks for the reply. A quick question, is there a way of setting the sent
date of a message to nothing? Thus deferred mail would work correctly!
Regards,
Richard Simpson.
|
| I think I might have typoed in .1 so I'll have another go at getting the field
names right! :)
Basically the date fields work as follows:
cab$.posted is the date and time that the message is posted,
ie when Sent or Deferred
cab$.delivered is the date and time that the message is delivered
(or placed in the queue if it's remote).
cab$.delivery is the deferred delivery date and time.
A deferred message, which has not yet been delivered and therefore _can_ be
canceled, is one which has a .delivery date, but no .delivered date.
The problem is that an MCD'd message already has a .delivered date, so
if it is subsequently deferred it cannot be canceled.
A temporary workaround would be to clear the .delivered field when messages
are deferred. Since the field can be multivalued, a script is required. The
following script seems to work but comes without a guarantee:
get #i = 0
for cab$attributes:delivered do compute #i = #i + 1
.label loop
.if #i eq 0 then .exit
write change cab$ k = oa$curdoc , delivered = ""
compute #i = #i - 1
.goto loop
|