If I start outlook 2013 and use rpc over https it seems i.e, if I run outlook 2010 from a 2012 Terminal server inside the network I get the issue. When clients try to send emails they get stuck in the outbox with no errors either in, outlook, the client computer, or on the exchange server.įor me it seems to occur on clients that are inside the network, connecting from out on the intenet appears ok. I have moved a couple of test accounts to Exchange 2013. In Outlook 2010 you can also use Namespace.SendAndReceive method.I have started encountering this issue as well "emails stuck in outbox", while setting up a new exchange 2013 server in my exchange 2007 enviornment. In this case you can start a sync using the the Namespace.SyncObjects collection.: set NS = Application.GetNamespace("MAPI")
EMAILS GETTING STUCK IN OUTBOX OUTLOOK 2013 CODE
Note that the code above assumes that there is an active Explorer this will not be the case if you start Outlook programmatically (and it was not previously started by a user) and do not display any folders. Note that in Outlook 2003 that button is now a dropdown, the real Send/Receive is a subitem of the button: Set Btn = (1, 7095) Uncheck "Use cached mode" in the Exchange Server properties to force online mode - that will ensure that messages are delivered immediately.Īs a last resort, you can simulate clicking "Send/Receive" button in Outlook after sending a message: MailItem.Send If you are using Outlook 2003 or higher with Exchange in a cached mode, it will exhibit the same problem. Note however that Outlook 2002/2003 (online) with an Exchange Server or Outlook 2000 C/W in any configuration are fine. There is however one problem if you are using Outlook 2002 or newer with a PST file and POP3/SMTP transport provider or Outlook 2000 installed in the Internet Only Mode: there is no way to flush the queues using Extended MAPI. Set Utils = CreateObject("Redemption.MAPIUtils") To flush the message queues, create an instance of Redemption.MAPIUtils object and call its DeliverNow method (similar to Session.DeliverNow in CDO) after calling SafeMailItem.Send: MailItem.Send If you however are using a POP3/SMTP transport and a PST file as a message store, step #2 is required. If you are using an Exchange Server, step #2 is not required since Exchange Message Store is tightly bound with the Exchange Transport provider.
Message submission is a two step process in Extended MAPI:
When I send a message using Redemption, it simply stays in the Drafts folder Let me know if you need more information. If there is a need to do code changes, is it possible keeping the redemption.dll version v 4.5 (as per the requirement) What could be the reason, is there need to do code changes or is it some setting changes related to Outlook 2013?Īny kind of help would be very useful.
Scenario 2: Now in Win 7 machine using the developer version redemption.dll v 5.14 too the mail get stuck in Outbox. So when i keep outlook open and run the function the mails get delivered. When i open Outlook 2013 the mails get delivered.
But what i noticed is the mails are stuck in Outbox. Scenario 1: In Win 7 machine using the redemption.dll v 4.5.0.812 when i run the application, the report delivery function runs without errors. For the mail delivery part it uses Redemption.dll Basically its a VBA Access application which will send reports to users. Currently i am in a process of migrating applications to new version, i am facing a problem in the application.
0 kommentar(er)
