User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

TB Updated this morning. TB had updated when I got to work and was waiting for me to click the restart button. I clicked the restart and it seemed that the update was fine.

When I tried to send an attachment from Acrobat Reader I had problems.

I believe the issue only started after the update to 60.5.2

Actual results:

I tried sending a pdf from Adobe Acrobat using the send email icon, then selected send as attachment in the right side pane, selected default mail application, then clicked continue.

At first it appeared nothing happened, but then I would receive the email with the attachment in my inbox, but in the recipients area it would show undisclosed.

I have my emails set to bcc to myself so that is why it came back to me, but I didn't have an opportunity to select or enter a recipient, and the send new mail window never opened.

I tried sending the same file by right clicking on it in Windows Explorer and selecting send to-mail recipient. It did the same thing as with Acrobat Reader.

I then read up a little bit to see if someone else had the same issue. I came across an instance, though not the same as mine but similar, it suggested trying to send an email from MS Word to see if it was a MAPI problem. Trying to send from Word got the same result...a bcc email with the attachment, but no verbiage or recipients.

I tried rebooting the computer, but it didn't make a difference. I checked the email settings in Reader and it was set to use the default mail application which I checked and it is Thunderbird.

I looked for solutions on line but couldn't find anything that was the same as my problem.

Expected results:

Normally when I send an attachment by clicking the envelope icon in Acrobat Reader, and select "send as attachment", select "default mail application", and select "continue" it will open up a compose mail window, with the attachment already attached, ready for me to enter recipient info and write any verbiage I want to include with the attachment.

When I right click a file in Windows Explorer and select "Send to"-"Mail Recipient" a new compose mail window opens with the selected file already attached and ready to type a message and enter recipient information.

When I'm in the latest acrobat reader dc and click on the mail function, using default email application, I get from THUNDERBIRD "Another application is attempting to send email using your user profile. Are you sure you want to send email? (checkbox) Warn me whenever other applications try to send email from me. OK or Cancel.

With the checkbox checked:
If I click OK, acrobat says "a specified recipient type is invalid". I was never able to enter a recipient. Never get the compose window.

If I click Cancel - same results.

With the checkbox UNchecked: - SAME result. And now I don't get the Thunderbird message at all.

I appreciate your thoughts mercinf123. But I don't suspect that the problem lies with Acrobat. Te last Acrobat update was 2/22/19. I didn't experience the problem didn't show up until the Thunderbird update 2/27/19. Also, I have the same problem with Windows Explorer and MS Word.

I will send pdf's from Acrobat Reader several times a week, so I think I would have seen it between the time that Reader updated on the 22nd and T-Bird updated on the 27th.

We didn't experience the issue until the Thunderbird update on the 27th. Proved that to my satisfaction when I was alerted from work. I hadn't installed the update on my Thunderbird. Worked fine before the update, and not immediately after. I made no changed to Acrobat. At work, mostly we go directly from a PDF to email, only occasionally from other apps.

Anyone find a solution? We generate PDF's out of our AR/AP/OE/IC system on a regular basis and email them out. Most of the people who do that aren't very computer literate. The pdf pops up and they review, then click on the email button. It worked yesterday, not today. They don't know the file is actually created, stored on the server, and can be retrieved. (It doesn't usually matter if I've shown them before, if it doesn't work the "normal" way, they scream) Thankfully, this morning's call came from someone a bit more computer literate, and I think she's OK for a bit. One of my big "screamers" must be out today. I'm working remotely.

We have the same problem with Thunderbird 60.5.2 on the Windows 2008r2 and Windows 2019.

See bug 1530820 comment #30.