Closed Bug 108275 Opened 23 years ago Closed 20 years ago

Enabling the rest of simple MAPI ( 8 interfaces) in mail.

Categories

(MailNews Core :: Simple MAPI, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: tiantian, Assigned: Bienvenu)

References

Details

(Keywords: meta)

Attachments

(6 files)

With the eMojo release, we've completed the implementation of 4 interfaces for
simple MAPI:    

1. MAPILogon - Establishes a session with Messenger
2. MAPILogoff - Ends a session with Messenger 
3. MAPISendMail - Send a mail message through Messenger
4. MAPISendDocuments - Sends a mail message through Messenger.

For the next release, we'll work on the remaining 6 interfaces:

5. MAPIFreeBuffer - Frees any memory allocated by Messenger
6. MAPIFindNext - lists information about a message meeting certain criteria
7. MAPIReadMail - Reads a specific message
8. MAPISaveMail - saves a message into the message store
9. MAPIDeleteMail - deletes a message
10. MAPIAddress - Addresses a messag
11. MAPIDetails - displays a dialog box containing the details of a selected
address list entry.
12. MAPIResolveName - resolving friendly names with email names.

This is a meta bug.
Keywords: meta
Priority: -- → P1
Summary: Enabling the rest of simple MAPI in mail. → Enabling the rest of simple MAPI ( 6 interfaces) in mail.
Target Milestone: --- → mozilla1.0
It says "remaining 6" when there are 8 remaining, right?
Changed summary to 8 interfaces. Thx to Kevin for spotting the typo.
Summary: Enabling the rest of simple MAPI ( 6 interfaces) in mail. → Enabling the rest of simple MAPI ( 8 interfaces) in mail.
reassigning to rdayal
Assignee: tiantian → rdayal
Blocks: 102231
Keywords: nsbeta1+
We will wait for this.
Status: NEW → ASSIGNED
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla1.0 → Future
Propose we remove this as a dependency for Bug 102231, since this is nsbeta1-
and no longer targetted for the next release.
No longer blocks: 102231
Priority: P1 → --
removed jhooker from cc: list
*** Bug 173713 has been marked as a duplicate of this bug. ***
QA Contact: trix → yulian
QA Contact: yulian → stephend
taking
Assignee: rdayal → bienvenu
Status: ASSIGNED → NEW
Attached patch work in progressSplinter Review
work in progress for implementing some of the other interfaces, especially the
ones that are used for palm sync of mail
David, I think you may find this interesting (though it's not as helpful as one
would want):
http://www.eudora.com/developers/mapi.html#HowDoesEudoraSupportMapi

Some linkage:
http://www.dimastr.com/outspy/resources.htm
Attached patch proposed fixSplinter Review
this enables the basic functionality, and works with the eudora mail mapi
conduit...
Attachment #146797 - Flags: superreview?(mscott)
Attachment #146797 - Flags: superreview?(mscott) → superreview+
fixed, palm sync of e-mail via mapi 0 should work now...if you have a mapi conduit.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Good to read that somebody is working on this. Many thanks to David.
Just one question: Does your code probably fix Bug #221673, too? 

Achim
Attached patch follow on fixesSplinter Review
this fixes mapi send (if you've set the correct hidden pref), and attempts to
fix the errors that have been reported...
Attachment #147084 - Flags: superreview?(mscott)
Attachment #147084 - Flags: superreview?(mscott) → superreview+
In order for blind send to work, you need to set the hidden pref
"mapi.blind-send.enabled" to true.
Keywords: helpwanted, nsbeta1-
this patch adds PRLogging, and replaces the LPSTR's with LPTSTR - I believe the
rpc struct marshalling was unhappy about our giving it LPTSTRs that sometimes
had an odd number of bytes, and weren't double null terminated. Since we're
really just giving it ascii data, define the interfaces as such.
Attachment #147333 - Flags: superreview?(mscott)
Attachment #147333 - Flags: superreview?(mscott) → superreview+
ok, tomorrow's nightly thunderbird and seamonkey builds should have the latest
fix in them - I'm hopeful that these will work for people that have been having
the Read Mail error from the Eudora Conduit.
Attachment #147428 - Flags: superreview?(mscott)
Attachment #147428 - Flags: superreview?(mscott) → superreview+
Attachment #147550 - Flags: superreview?(mscott)
Attachment #147550 - Flags: superreview?(mscott) → superreview+
*** Bug 145189 has been marked as a duplicate of this bug. ***
Latest seamonkey 2004051608 reports the following in a warning popup when a
hotsync of new message from palm is attempted:

Send Message Error

Sending of message failed.
No recipients were specified. Please enter a recipient or newsgroup in the
addressing area.


Corresponding hotsync log reports the following ("Test palm!" is the subject):


HotSync operation started 05/16/04 21:38:32
-- Mail
   - Could not send the following e-mail to the E-Mail application:
	To: pearsondave@hotmail.com, Test palm!
OK Mail with 1 message(s)
I've had the problem before when testing with David, so it's a known issue.

So far, no known work around.  Though since the last round of patches, it no
longer freezes everything (that was a real pain).  So improvment has been made.
I seem to be having problems again.  This may be user error and may be a bug. 
Here is what I did.  I retrieved E-mail on my desktop.  I synced this E-mail to
my Visor to Eudora Internet Suite using the Eudora conduit.  All went according
to expectations.  I read some of the E-mail on my Visor during the day and
deleted a few messages including emptying the Trash folder on the Visor, while
my desktop was collecting new E-mail.  I synced my Visor again at the end of the
day.  I had expected the messages I had read to show as read on my desktop, the
messages I had deleted to disappear, and new messages collected while I was away
to sync to my Visor.  None of this happened.  I am using the 5/21 Nightly.
I seem to be back to ahving this problem again after installing TB 0.7.

-- Eudora
   - Failed while trying to retrieve the next message from the Desktop Mail System.
Why is this still listed as "RESOLVED / FIXED" when it does not work?
Perhaps the best questiosn to ask is 'Is this supposed to work in 0.7?'  I know
it worked in the 0.6 Trunk builds, but did 0.7 fork before or after the fix was
checked in?
(In reply to comment #26)
> Perhaps the best questiosn to ask is 'Is this supposed to work in 0.7?'  I know
> it worked in the 0.6 Trunk builds, but did 0.7 fork before or after the fix was
> checked in?
> 

I had the opportunity last night to try out the latest nightly, replacing 0.7.2.
 With the trunk nightly E-mail sync again works.  My guess is that the patch did
not make it into the 0.7 release code base.

The tradeoff is that none of my extensions seem to work with the nightly.  I'll
take E-mail sync over extensions for the moment.
*** Bug 230262 has been marked as a duplicate of this bug. ***
*** Bug 251228 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
*** Bug 227394 has been marked as a duplicate of this bug. ***
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: