[SOLVED] Send To -> Mail Recipient does nothing

[XpL0d3r]

Hi all,

Having an issue here with a domain user / computer.

Windows 7 Ent x64 SP1, Office 2013

The user used to be able to right-click a file on his Desktop, navigate to Send To, and select Mail Recipient. The file would automatically attach to a blank email for Outlook.

Now, when the user does this, absolutely nothing happens.

Steps taken so far:
Classic reboot
Gpupdate
It works when I login as a different standard user or administrative user on the same computer
Recreated outlook OST file, issue still persists
Renamed Mapi32.DLL to Mapi32.OLD, so that when Outlook is re-launched it created a new copy of this file. Issue still persists
Ensured Outlook is set as the default email program and that MAILTO and Send mail commands are associated with Outlook.
Checked Event Viewer, and noticed these events every time I tried to send:
"MAPISendMail: Failed to submit message. Attachments to the message exceeded the size limit set by your Administrator."

We have default limits in place; I tried sending a 1KB text file and still got the error above. Did a little searching and someone recommended the fix as stated in the answer on the link HERE which mentioned editing the registry. I did this, issue still persists.

At this point I'm kind of at a stand still. The user can work around it by opening a blank email and then dragging the files in, or using the attach button. Unfortunately he's a user that frequently uses the Send To option, so I'd like to get this resolved.

Any ideas or anything else anyone can think of?

Thanks!
--Shaun

 

[Digerati]

Not all versions of Office include Outlook so Outlook is often purchased separately, and may not be same version as other Office apps. So, are you sure it is Outlook 2013?

In Outlook, under Help, try selecting Office Diagnostics to see if that helps.

 

[XpL0d3r]

We use Office Professional Plus. I'm 100% certain it's office 2013 as I stated.

Diagnostics were useless.

 

[Digerati]

For sure, Office Pro includes Outlook. Not sure I've heard of Pro "Plus", but I doubt that matters here.

Diagnostics were useless.

Well, it was worth a try.

Wow. I see your frustration. I see lots of folks complaining, but no fix. Well, one guy said he "downloaded the fix" but didn't bother to say what it was, and never returned, the butthead. Pardon me.
Hmmm, not sure it fits, but might be worth a try: FIX: "Send to Mail Recipient" function fails when you try to send a note or signature through Windows Journal if a 32-bit version of Outlook is installed on a 64-bit version of Windows 7 or of Windows Server 2008 R2

 

[XpL0d3r]

For sure, Office Pro includes Outlook. Not sure I've heard of Pro "Plus", but I doubt that matters here.

Diagnostics were useless.

Well, it was worth a try.

Wow. I see your frustration. I see lots of folks complaining, but no fix. Well, one guy said he "downloaded the fix" but didn't bother to say what it was, and never returned, the butthead. Pardon me.
Hmmm, not sure it fits, but might be worth a try: FIX: "Send to Mail Recipient" function fails when you try to send a note or signature through Windows Journal if a 32-bit version of Outlook is installed on a 64-bit version of Windows 7 or of Windows Server 2008 R2

It's mainly for a business environment. Only used with volume licensing. Office Professional Plus 2013 ? business software

I will definitely give that hotfix a try though and report back. It is 32-bit Office on a 64-bit system, so it won't hurt to try. Thanks!

 

[Digerati]

Keep us posted.

 

[Koza Nozdri]

Меню пуск - shell:sendto
Там должно быть присутствие: Адресат

Если проблема сохранится - потребуется работа с ассоциацией.

 

[Digerati]

Hi Koza Nozdri and Welcome. Please note this is an English speaking forum so please post your comments in English. I have used Bing to translate your post as follows, but not sure it is what you wanted to say.

On the start menu - - shell:sendto

There must be a presence of: the Addressee

If the problem persists-the need to work with the Association

 

[Koza Nozdri]

Please note, this is an English speaking forum, so please leave your comments in English.

Yes, thank you. I badly know English that will enable you to avoid problems of translation will try knockoutjs START menu - run - shell: SendTo to check the file destination , if the object is present, it will be necessary to work with associations of files and some registry edits

 

[XpL0d3r]

I actually believe we've identified this as an issue with our LiquidFiles plugin. (Send Large Files — Fast, Easy, Secure and Affordable | LiquidFiles)

It's now affecting a handful of people at our company. We use LiquidFiles as a way to prevent emails with large attachments. There was a recent update for it right before this issue occurred. Only strange thing is that it's affecting select people, not everyone. I'll keep this updated, but at the moment our network admin is working with the LiquidFiles support team to resolve this.

Thanks

 

[Koza Nozdri]

good!

 

[XpL0d3r]

Confirmed fixed with the new version of the LiquidFiles plugin. It was basically an issue with the plugin not creating an XML file when it should have. That file is read by the plugin which tells LiquidFiles when to "kick in" or not. Essentially any attachments over 5MB (our limit) automatically use LiquidFiles rather than actually attaching in Outlook. LiquidFiles uploads the file to our server and sends a link to the recipient to download the file rather than attaching it.

Without that XML file, 0MB is assumed. Outlook reads that as unlimited, but LiquidFiles would actually read it as 0. The file wouldn't attach since any file > 0b.

There was a workaround for this by creating the XML file.

Now the question is, why wasn't the XML file created in the first place? Everyone has LiquidFiles installed on their machine.

As it turns out, while it's installed on everyone's machine, it needs to be "triggered" to configure properly. That is, attach something in Outlook like normal that's above the 5MB limit, which will trigger the use of LiquidFiles rather than just attaching in Outlook. This is why the issue was sporadic throughout our office; users who had never triggered it had no XML file.

All good now!