| components.conf |
|
5822 |
| moz.build |
|
1024 |
| nsLocalMailFolder.cpp |
|
128834 |
| nsLocalMailFolder.h |
Interface for representing Local Mail folders.
|
11357 |
| nsLocalUndoTxn.cpp |
|
13705 |
| nsLocalUndoTxn.h |
|
2110 |
| nsLocalUtils.cpp |
|
6798 |
| nsLocalUtils.h |
|
1076 |
| nsMailboxProtocol.cpp |
the output_buffer_size must be larger than the largest possible line
2000 seems good for news
jwz: I increased this to 4k since it must be big enough to hold the
entire button-bar HTML, and with the new "mailto" format, that can
contain arbitrarily long header fields like "references".
fortezza: proxy auth is huge, buffer increased to 8k (sigh).
|
19938 |
| nsMailboxProtocol.h |
should we pause for the next read |
3893 |
| nsMailboxServer.cpp |
|
484 |
| nsMailboxServer.h |
|
495 |
| nsMailboxService.cpp |
only used by open attachment... |
19516 |
| nsMailboxService.h |
only used by open attachment |
2024 |
| nsMailboxUrl.cpp |
|
14791 |
| nsMailboxUrl.h |
|
3437 |
| nsMsgBrkMBoxStore.cpp |
Class for handling Berkeley Mailbox stores.
|
58938 |
| nsMsgBrkMBoxStore.h |
Class for handling Berkeley Mailbox stores.
|
1741 |
| nsMsgFileHdr.cpp |
|
11367 |
| nsMsgFileHdr.h |
This mail-related class is a stub. You can help mailnews by expanding it. |
943 |
| nsMsgLocalStoreUtils.cpp |
Attempt to update X-Mozilla-Status and X-Mozilla-Status2 headers with
new message flags by rewriting them in place.
|
12743 |
| nsMsgLocalStoreUtils.h |
Utility Class for handling local mail stores. Berkeley Mailbox
and MailDir stores inherit from this class to share some code.
|
1133 |
| nsMsgMaildirStore.cpp |
Class for handling Maildir stores.
|
46960 |
| nsMsgMaildirStore.h |
Class for handling Maildir stores.
|
1119 |
| nsNoIncomingServer.cpp |
|
5680 |
| nsNoIncomingServer.h |
get some implementation from nsMsgIncomingServer |
1222 |
| nsNoneService.cpp |
|
3935 |
| nsNoneService.h |
nsNoneService_h___ |
653 |
| nsParseMailbox.cpp |
the following macros actually implement addref, release and query interface
for our component. |
86033 |
| nsParseMailbox.h |
Used for the various things that parse RFC822 headers...
|
9680 |
| nsPop3Sink.cpp |
for logging to Error Console |
26357 |
| nsPop3Sink.h |
|
1904 |
| nsPop3URL.cpp |
|
6629 |
| nsPop3URL.h |
Pop3 specific event sinks |
1158 |
| nsRssIncomingServer.cpp |
|
8128 |
| nsRssIncomingServer.h |
__nsRssIncomingServer_h |
1607 |
| nsRssService.cpp |
|
3289 |
| nsRssService.h |
nsRssService_h___ |
564 |
| Pop3Channel.sys.mjs |
A channel to interact with POP3 server.
@implements {nsIChannel}
@implements {nsIRequest}
|
2256 |
| Pop3Client.sys.mjs |
A structure to represent a response received from the server. A response can
be a single status line of a multi-line data block.
@typedef {object} Pop3Response
@property {boolean} success - True for a positive status indicator, "+OK", or
for an authorization challenge respone "+".
@property {string} status - This is the status indicator. Will be either
"+OK", "-ERR" or, for server authorization challenges, "+".
@property {string} statusText - The optional text following the status
indicator.
@property {string} data - The segment of a multi-line or a single line data
response with status and statustext not present - the useful response data.
A single char to represent a uidl status, possible values are:
- 'k'=KEEP,
- 'd'=DELETE
- 'b'=TOO_BIG
- 'f'=FETCH_BODY
@typedef {string} UidlStatus
|
55327 |
| Pop3IncomingServer.sys.mjs |
@implements {nsIPop3IncomingServer}
@implements {nsILocalMailIncomingServer}
@implements {nsIMsgIncomingServer}
@implements {nsISupportsWeakReference}
|
11613 |
| Pop3ProtocolHandler.sys.mjs |
@implements {nsIProtocolHandler}
|
1084 |
| Pop3ProtocolInfo.sys.mjs |
@implements {nsIMsgProtocolInfo}
|
1196 |
| Pop3Service.sys.mjs |
@implements {nsIPop3Service}
|
2016 |
| StoreIndexer.cpp |
|
9926 |
| StoreIndexer.h |
StoreIndexer iterates through all the messages in a folder's local
msgStore, building (or rebuilding) the message database.
Future improvements:
StoreIndexer should be decoupled from the folder. It should just take an
nsIMsgPluggableStore to scan and a nsIMsgDatabase to populate, and that's
it.
Any folder-specific stuff (folder locking etc) should be handled higher
up, by the calling code and its callback functions.
NOTE: deriving from nsIStoreScanListener is _purely_ an implementation
detail, and should not be considered part of the public interface!
|
3323 |