mscott and cc: phil, warren? Much of our non-static/global data needs to be partitioned by window, not reachable by other windows except through statics/globals. Therefore we're starting the hunt with statics and globals. Please have a look at the file(s) below to see if we can improve reentrantcy across the code base by making modifications to: network/protocol/imap4/imap4pvt.h: char fOnlineSubDirSeparator; // not static anymore - one delimiter for each URL we run. network/protocol/imap4/imap4pvt.h: static int64 fgTimeStampOfNonPipelinedList; network/protocol/imap4/imap4pvt.h: static PRMonitor *gCachedHostInfoMonitor; network/protocol/imap4/imap4pvt.h: static TIMAPHostInfo *fHostInfoList; network/protocol/imap4/imap4pvt.h: static TNavigatorImapConnection* network/protocol/imap4/imap4pvt.h: static PRMonitor *fFindingMailboxesMonitor; network/protocol/imap4/imap4pvt.h: static PRMonitor *fUpgradeToSubscriptionMonitor; network/protocol/imap4/imap4pvt.h: static XP_Bool fHaveWeEverCheckedForSubscriptionUpgrade; network/protocol/imap4/imap4pvt.h: static MSG_BIFF_STATE fCurrentBiffState; network/protocol/imap4/imap4pvt.h: static XPPtrArray *connectionList; network/protocol/imap4/imap4pvt.h: static PRMonitor *fgDataSafeMonitor; network/protocol/imap4/imap4pvt.h: static int fgInboxUsageCount;

RX tasks aren't going to make M3. close the reentrantcy tracking tasks if this specific area has been looked at and doesn't seem to be a problem. Otherwise each of these areas still need some looking at.

Pushing off of M4. We don't have imap for M4 anyway (it wasn't scheduled for M4). We are taking this into consideration for our design of imap.

the imap code now in 5.0 no longer uses any of the global / static data listed below.

so, how can I verify this? do I just use an imap and see if it works? Or is this more code-level verification? If it is code level, then Chris -- you'll need to verify it as you are the reporter.

since this is a low level fix, marking verified