Closed Bug 500577 Opened 16 years ago Closed 16 years ago

Cannot send email from external software, MAPI?

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 499958

People

(Reporter: ebturner, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Build Identifier: 2.0.0.22 Running Windows XP. Using Pitney Bowes Shipstream software which uses MAPI (i think thats the proper term) to send shipping numbers via email. The postal service software uses standard MAPI calls to use your email client to send emails on its behalf. (Being Outlook, Thunderbird, etc.) Thunderbird did an automatic update from 2.0.0.21 to 2.0.0.22 and the emails no longer send from the external program. Tried a fresh install and it did the same thing. The external program which uses your email client to process and send an email would not work. I can send emails manually, so its not an incorrect email/POP setting. I switched to Outlook via the Internet Explorer settings and it worked via Outlook (yuck). Switched back to Thunderbird and nothing sends, nor any record of it being sent (sent folder empty). I found my old version 2.0.0.21 and installed over the 2.0.0.22 and things are back to NORMAL. I can only assume that something in the new version is not working 100% with MAPI. Reproducible: Always Steps to Reproduce: 1. Upgrade to Thunderbird 2.0.0.22 2. Use an external program to send an email (via MAPI) 3. Check sent folder and no email was sent. Also no email received (test send to self just to make sure) 4. Reinstall the old version 2.0.0.21 and try again...IT WORKS FINE. It really seems to be a problem in the MAPI handling in the new version. Did something change?
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.