Closed
Bug 261705
Opened 20 years ago
Closed 19 years ago
MAPI failure MAPIFindNext (Mozilla 1.6, 1.7 & Netscape 7 )
Categories
(MailNews Core :: Simple MAPI, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: kxroberto, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 I don't get managed to read the inbox(es) of Mozilla with MAPIFindNext. Played with lots of parameter variations, profile-names, NULLs, and all. MAPILogon (and MAPISendMail work but MAPIFindNext always returns 2 (MAPI_E_FAILURE). (besides: when using Netscapes DLL MAPISendMail opens Mozillas Editor & Profile) I tried with Netscape 4.72 (nsmapi.dll) and OutlookExpress (MSOE.dll): MAPIFindNext works correct as intended! Robert ############# Python 2.3 ############## def SyncInbox(self,cbMsg=None): from ctypes import c_ulong,c_char_p import win32com.mapi.mapi as wmapi mapi=ctypes.WinDLL(r"c:/Programme/mozilla.org/mozilla/mozMapi32.dll") print "MapiDllVersion", mapi.GetMapiDllVersion() #---- shandle=" " profile="" pwd="" mapi.MAPILogon.argtypes = [c_ulong, c_char_p, c_char_p, c_ulong, c_ulong, c_char_p] ret = mapi.MAPILogon( 0, #ULONG ulUIParam, profile, #LPTSTR lpszProfileName, pwd, #LPTSTR lpszPassword, 0, #FLAGS flFlags, 0, #ULONG ulReserved, shandle ) h = struct.unpack("i",shandle)[0] print "MAPILogon",ret,"H:[%s]"%h #----- msgid=" "*513 MAPI_LONG_MSGID = 0x00004000 MAPI_UNREAD_ONLY = 0x00000020 mapi.MAPIFindNext.argtypes = [c_ulong, c_ulong, c_char_p, c_char_p, c_ulong, c_ulong, c_char_p] ret = mapi.MAPIFindNext( h, #LHANDLE lhSession, 0, #ULONG ulUIParam, None, #0, #LPTSTR lpszMessageType, "NULL", #None, #LPTSTR lpszSeedMessageID, MAPI_LONG_MSGID|MAPI_UNREAD_ONLY, #FLAGS flFlags, 0, #ULONG ulReserved, msgid, #LPTSTR lpszMessageID ) print "MAPIFindNext",ret,len(msgid), "[%s]"%msgid[:10] return ret,msgid ########### output: >>> MapiDllVersion 94 MAPILogon 2 H:[538976288] MAPIFindNext 2 513 [ ] >>> Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•20 years ago
|
||
Robert: Why have you filed this bug when you already found bug 250757 before? Isn't this bug just a duplicate of bug 250757?
Updated•20 years ago
|
Product: MailNews → Core
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•