Windows 10: Outlook send/receive problem

I am running Office 2016 on my desktop Windows PC. Windows recently upgraded itself to version 2004. Since then I have been having intermittent problems with Outlook. When I boot-up, open Outlook, and do a send/receive, it always works perfectly. After being open for some time, it will start to give me 0x8004210A errors for every email account that I have. I think I can still send but the problem seems to be on the receive function, I think. Re-booting the PC fixes the problem. It will also sporadically pop up the window to enter my password, but like I said, it always works when I start up. Ideas?

:)

 

Outlook ceases to send and receive mail the next day

Does your Outlook Version 11 [part of Office 2003] ever send the messages? I've never favored having to click an icon to Send and Receive immediately, just another step in using the program, prefer to have it do the functions when clicking Send for the message.

And it's possible Win10 Version 1803 Build 17134.228 is part of the issue since support for Office 2003 has ended.

I'd try a test where Outlook is closed first before shutting down the computer, after all Outlook won't work when the computer is shut down.

 

Outlook send/receive issue after moving pst files to Drive D

I need some advice, as this issue is driving me pretty crazy and the solutions I've found online so far don't seem to work or have negative downstream consequences.
Win 10 (oem), v.1903
Office 2019 Home and Business (oem)
Internal Drive C: program files (but the oem install has the Documents folder on Drive C too for some reason)
Internal Drive D: data files
Background

1. After activating Outlook 2019, Windows automatically placed each pst file in C:\\Users\Username\Documents\Outlook Files\L: [email protected] Instead, I would like to store each Outlook pst file (have multiple email addresses/pst files) in a Documents folder (or some other folder) on Drive D.
2. To move the original Documents folder from drive C to Drive D I closed Outlook, right-clicked the original Documents folder and used the Properties/Location tab to move it to a new Documents folder I had previously created on drive D. That step seemed to work correctly, and each pst file was now in the new Documents folder on Drive D.
3. After the folder move, I launched Outlook and used the resulting "Outlook can't find" popup to specify a new file path for each pst file. However, while I can see each new file path in Outlook's Account Settings, it throws send and receive error messages (e.g.: "Sending reported error (0x8004010F): Outlook data file cannot be accessed") and won't send or receive for each account. This continues to happen after closing and reopening Outlook.
4. I moved the Documents folder back to where it was on drive C. I tried this several times, using the Outlook error popup to try to remap each email account to the new Documents path on Drive D.

Bottom line is that this Outlook send/receive issue is also preventing me from moving my Documents folder to the D drive where I want it, because when I move it, it messes up Outlook.
Question

• After I move each pst file and specify the new file paths in the Outlook popup, how do I get Outlook to send/receive for those email accounts?

Thank you in advance.

 

How to stop Win 10 with Outlook sending attachments as Winmail.dat

WIN 10 (64 bit) with OUTLOOK 2016 send E-Mails which some recipients are unable to open or read.


The problem most commonly encountered, to judge from many internet pleas for help, is that normal e-mail messages are sent and received satisfactorily but attachments – whatever their file extensions – are sometimes apparently not sent or not openable. There are also reports that some e-mail main texts are apparently not sent or not openable. This note is based specifically on WIN 10(64) plus OUTLOOK 2016, but my extensive reading for a solution has revealed that other WIN / OUTLOOK issue combinations also give rise to the same or similar problem. It may therefore well be possible that the following actions will also be of assistance with these.
The root problem is that OUTLOOK sometimes encodes messages and/or attachments as WINMAIL.dat files and sends these. Many non-MS mail programs can not recognise and/or open these. WINMAIL.dat is a format used in times past for sending Rich Text Format (RTF) messages. I am uncertain why MS persists with this heritage I have found in limited testing that some ISPs seem to receive OUTLOOK attachments OK (because these are sent as their original files with “normal” extensions) whereas another ISP appears to prompt their conversion to WINMAIL.dat and then can not open them. I have, by the way, eliminated any possibility that the problem stems from my receiving computer. My accounts are of the “web based” type and I can open my E-mail boxes by web access direct to the ISP.
My testing (not comprehensive) has shown that when OUTLOOK is used to send attachments to a Gmail.com account they are received OK but when the exact same attachments are sent to a BTInternet.com they are received as WINMAIL.dat encoded files. It is thus doubly unsatisfactory in that one can not rely on the receipt of attachments sometimes, but not always.
Here are the 3 steps I took :- 1.. Modify the registry to inhibit generation of Winmail.dat files. To do this a.. Open program REGEDIT (Windows key plus R) b.. Go to Computer/ HKEY_CURRENT_USER/ SOFTWARE/Microsoft/Office/16.0/Outlook/Preferences c.. Create a new DWORD(32bit) called Disable TNEF
d.. Enter a value of 1 ie.0x00000001 (1) e.. Exit Regedit 2.. Set up OUTLOOK so as NOT to send messages in RTF format. a.. Open OUTLOOK b.. At top left SLCk the blue FILE tab. File page opens.
c.. In list at LHS SLCk OPTIONS. d.. From OPTIONS find and SLCk MAIL. e.. In MAIL option scroll down to COMPOSE MESSAGES f.. Find CHANGE EDITING SETTINGS g.. Select PLAIN TEXT format option in box. (HTML option may also be OK but RICH TEXT FORMAT – RTF – must NOT be selected). h.. Close the MAIL options page(s).
3.. Set up OUTLOOK not to auto-complete addressees and empty the auto complete cache. a.. Open OUTLOOK b.. At top left SLCk the blue FILE tab. File page opens. c.. In list at LHS SLCk OPTIONS. d.. From OPTIONS find and SLCk MAIL. e.. In MAIL option scroll down to COMPOSE MESSAGES
f.. Select SEND MESSAGES section. g. UNCHECK box labelled “Use auto complete list to suggest names when typing To/cc/bcc lines”. h.. Find and SLCk the “Empty auto complete list” i.. SLCk YES in response to “ARE YOU SURE” pop-up box j.. There is no apparent response to step i. k.. Close OUTLOOK mail option page(s). l.. For good measure re-start the PC.

Notes : i.. At step 3e with OUTLOOK 2013 scroll to SENDING MESSAGES section. ii.. In OUTLOOK 2003 and 2007 for procedure section 2 : iia.. Access OPTIONS from the tools menu iib.. Click MAIL FORMAT tab iic.. Click INTERNET FORMAT iid. Under Outlook Rich Text Options click either Convert to HTML format or Convert to Plain Text format. Get rid of any reference to RTF.
iii. This note is written based on Win 10(64bit) plus Outlook 2016. Other OS/Outlook versions may vary in function and detail.
iv.. Some versions of OUTLOOK provide for the message sending format to be varied between addressees in the address book. To check for this each address book entry needs to be examined from its PROPERTIES values. These should be opened and set to HTML or PLAIN TEXT and never RTF (or TNEF). v.. With my problem the solution was achieved after step 3. It appears that the auto-complete cache “remembers” previous settings and hence it needs to be deleted.
vi.. Step 3 was the vital action and was kindly contributed by Caledon Ken at TEN FORUMS I will mark the thread as resolved after further evaluation, but am highly optimistic. .