K
Kristy
Hi
I use Outlook Redemption (3.3.0.315) to automatically send and print
HTML emails with an attachment list.
I seem to be having a problem with the messages remaining in the
Drafts Folder. I have read plenty of posts about this and most concur
that this is not an issue within an exchange environment... however I
am having the issue with Exchange 2003, Outlook XP SP2.
The items are marked to send in the Drafts folder so if Send/Receive
or update (f5) is used then the items go as expected, unfortunatley
this is not good enough for my customer as they want it to go
immediately with no further thought :-(
Also the item once in drafts is 'blocked' by Outlook so it cannot be
deleted, moved or anything!
Should I try using utils.delivernow or send keys to simulate a send
receive (which I am going to try in the short term as this customer is
really giving me grief), I feel that I shouldn't have to so this and
am possibly just covering up a bigger issue?
Code sample below is just like this...
'Call PrintInvoice
With sItem
.Save
.Recipients.ResolveAll
.Send
End With
Is there anything obvious you can see?
BTW... On my development pc's (Exchange 2000 and Outlook XP) it works
as expected.
Thanks K
I use Outlook Redemption (3.3.0.315) to automatically send and print
HTML emails with an attachment list.
I seem to be having a problem with the messages remaining in the
Drafts Folder. I have read plenty of posts about this and most concur
that this is not an issue within an exchange environment... however I
am having the issue with Exchange 2003, Outlook XP SP2.
The items are marked to send in the Drafts folder so if Send/Receive
or update (f5) is used then the items go as expected, unfortunatley
this is not good enough for my customer as they want it to go
immediately with no further thought :-(
Also the item once in drafts is 'blocked' by Outlook so it cannot be
deleted, moved or anything!
Should I try using utils.delivernow or send keys to simulate a send
receive (which I am going to try in the short term as this customer is
really giving me grief), I feel that I shouldn't have to so this and
am possibly just covering up a bigger issue?
Code sample below is just like this...
'Call PrintInvoice
With sItem
.Save
.Recipients.ResolveAll
.Send
End With
Is there anything obvious you can see?
BTW... On my development pc's (Exchange 2000 and Outlook XP) it works
as expected.
Thanks K