| moz.build |
|
1058 |
| nsIMsgFilter.idl |
some filters are "temporary". For example, the filters we create when the user
filters return receipts to the Sent folder.
we don't show temporary filters in the UI
and we don't write them to disk.
|
4305 |
| nsIMsgFilterCustomAction.idl |
describes a custom action added to a message filter
|
3157 |
| nsIMsgFilterHitNotify.idl |
|
1228 |
| nsIMsgFilterList.idl |
Turn filter logging on or off. Turning logging off will close any
currently-open open logfile.
|
4967 |
| nsIMsgFilterPlugin.idl |
This interface is still very much under development, and is not yet stable.
|
13807 |
| nsIMsgFilterService.idl |
Apply filters to a specific list of messages in a folder.
@param aFilterType The type of filter to match against
@param aMsgHdrList The list of message headers (nsIMsgDBHdr objects)
@param aFolder The folder the messages belong to
@param aMsgWindow A UI window for attaching progress/dialogs
@param aCallback A listener that gets notified of any filtering error
|
3621 |
| nsIMsgOperationListener.idl |
Called when the operation stops (possibly with errors)
@param aStatus Success or failure of the operation
|
659 |
| nsIMsgSearchAdapter.idl |
Clear the saved scope reference. This is used when deleting scope, which is not
reference counted in nsMsgSearchSession
|
1408 |
| nsIMsgSearchCustomTerm.idl |
describes a custom term added to a message search or filter
|
2523 |
| nsIMsgSearchNotify.idl |
until we can encode searches with a URI, this will be an
out-of-bound way to connect a set of search terms to a datasource
|
953 |
| nsIMsgSearchScopeTerm.idl |
|
713 |
| nsIMsgSearchSession.idl |
add a search term to the search session
@param attrib search attribute (e.g. nsMsgSearchAttrib::Subject)
@param op search operator (e.g. nsMsgSearchOp::Contains)
@param value search value (e.g. "Dogbert", see nsIMsgSearchValue)
@param BooleanAND set to true if associated boolean operator is AND
@param customString if attrib > nsMsgSearchAttrib::OtherHeader,
a user defined arbitrary header
if attrib == nsMsgSearchAttrib::Custom, the custom id
otherwise ignored
|
4814 |
| nsIMsgSearchTerm.idl |
Not to be confused with arbitraryHeader, which is a header in the
rfc822 message. This is a property of the nsIMsgDBHdr, and may have
nothing to do the message headers, e.g., gloda-id.
value.str will be compared with nsIMsgHdr::GetProperty(hdrProperty).
|
5572 |
| nsIMsgSearchValidityManager.idl |
Given a search attribute (which is an internal numerical id), return
the string name that you can use as a key to look up the localized
string in the search-attributes.properties file.
@param aSearchAttribute attribute type from interface nsMsgSearchAttrib
@return localization-friendly string representation
of the attribute
|
1104 |
| nsIMsgSearchValidityTable.idl |
|
1445 |
| nsIMsgSearchValue.idl |
junkPercent is set by the message filter plugin, and is approximately
proportional to the probability that a message is junk.
(range 0-100, 100 is junk)
|
1265 |
| nsIMsgTraitService.idl |
This interface provides management of traits that are used to categorize
messages. A trait is some characteristic of a message, such as being "junk"
or "personal", that may be discoverable by analysis of the message.
Traits are described by a universal identifier "id" as a string, as well
as a local integer identifier "index". One purpose of this service is to
provide the mapping between those forms.
Recommended (but not required) format for id:
"extensionName@example.org#traitName"
|
6004 |
| nsMsgBodyHandler.h |
|
3491 |
| nsMsgFilterCore.idl |
these longs are all actually of type nsMsgFilterTypeType |
2246 |
| nsMsgResultElement.h |
|
1350 |
| nsMsgSearchAdapter.h |
linked list of criteria terms |
9255 |
| nsMsgSearchBoolExpression.h |
CBoolExpression --> encapsulates one or more search terms by internally
representing the search terms and their boolean operators as a binary
expression tree. Each node in the tree consists of either
(1) a boolean operator and two nsMsgSearchBoolExpressions or
(2) if the node is a leaf node then it contains a search term.
With each search term that is part of the expression we may also keep
a character string. The character
string is used to store the IMAP/NNTP encoding of the search term. This
makes generating a search encoding (for online) easier.
For IMAP/NNTP: nsMsgSearchBoolExpression has/assumes knowledge about how
AND and OR search terms are combined according to IMAP4 and NNTP protocol.
That is the only piece of IMAP/NNTP knowledge it is aware of.
Order of Evaluation: Okay, the way in which the boolean expression tree
is put together directly effects the order of evaluation. We currently
support left to right evaluation.
Supporting other order of evaluations involves adding new internal add
term methods.
|
4574 |
| nsMsgSearchCore.idl |
Definitions of search attribute types. The numerical order
from here will also be used to determine the order that the
attributes display in the filter editor.
|
8509 |
| nsMsgSearchScopeTerm.h |
|
1298 |
| nsMsgSearchTerm.h |
Switch a string to lower case, except for special database rows
that are not headers, but could be headers
@param aValue the string to switch
|
3256 |