nsISpamSettings Interface Reference

import "nsISpamSettings.idl";

Inheritance diagram for nsISpamSettings:

Inheritance graph
[legend]
Collaboration diagram for nsISpamSettings:

Collaboration graph
[legend]

List of all members.

Public Member Functions

void logJunkHit (in nsIMsgDBHdr aMsgHdr, in boolean aMoveMessage)
void logJunkString (in string aLogText)
void clone (in nsISpamSettings aSpamSettings)
void initialize (in nsIMsgIncomingServer aServer)

Public Attributes

attribute long level
 0 for nothing, 100 for highest
attribute boolean moveOnSpam
readonly attribute boolean markAsReadOnSpam
attribute long moveTargetMode
 Most consumers will just use spamFolderURI rather than accessing any of target attributes directly.
const long MOVE_TARGET_MODE_ACCOUNT = 0
const long MOVE_TARGET_MODE_FOLDER = 1
attribute string actionTargetAccount
attribute string actionTargetFolder
readonly attribute string spamFolderURI
 built from moveTargetMode, actionTargetAccount, actionTargetFolder
attribute boolean purge
attribute long purgeInterval
 interval, in days
attribute boolean useWhiteList
attribute string whiteListAbURI
readonly attribute boolean manualMark
 should we do something (move or delete) when the user manually marks a message as junk?
readonly attribute long manualMarkMode
const long MANUAL_MARK_MODE_MOVE = 0
const long MANUAL_MARK_MODE_DELETE = 1
attribute boolean useServerFilter
 integrate with server-side spam detection programs
attribute ACString serverFilterName
readonly attribute nsIFile serverFilterFile
const long TRUST_POSITIVES = 1
const long TRUST_NEGATIVES = 2
attribute long serverFilterTrustFlags
readonly attribute boolean loggingEnabled
attribute nsIOutputStream logStream


Member Function Documentation

void nsISpamSettings::logJunkHit ( in nsIMsgDBHdr  aMsgHdr,
in boolean  aMoveMessage 
)

void nsISpamSettings::logJunkString ( in string  aLogText  ) 

void nsISpamSettings::clone ( in nsISpamSettings  aSpamSettings  ) 

void nsISpamSettings::initialize ( in nsIMsgIncomingServer  aServer  ) 


Member Data Documentation

attribute long nsISpamSettings::level

0 for nothing, 100 for highest

Most consumers will just use spamFolderURI rather than accessing any of target attributes directly.

built from moveTargetMode, actionTargetAccount, actionTargetFolder

interval, in days

should we do something (move or delete) when the user manually marks a message as junk?

readonly attribute long nsISpamSettings::manualMarkMode

integrate with server-side spam detection programs


The documentation for this interface was generated from the following file:

Generated Mozilla by doxygen 1.5.6