Package talx.model.filters

Provides message filter classes.

See:
Description

Interface Summary

ReceiverFilter	Represents a filter in the incoming filter stack.
ReceiverFilterListener	Contract for listeners to the incoming filter stack.
SenderFilter	Represents a filter in the outgoing filter stack.
SenderFilterListener	Contract for listeners to the outgoing filter stack.

Class Summary

CommandFilter	Searches incoming messages for test commands and game moves.
InboxCountMonitor	Keeps the outbox at or below a given size.
InboxDateMonitor	Removes old messages from the inbox.
MultiRecipientFilter	Filters messages that was sent to too many recipients.
NoTextFilter	Filters messages that contain no text.
OutboxCountMonitor	Keeps the outbox at or below a given size.
OutboxDateMonitor	Removes old messages from the outbox.
ReceiverFilterAdapter	Adapter class for objects in the incoming filter stack.
RemoteReceiver	Gets messages from an IMAP or POP3 store and passes them into the incoming filter stack.
RemoteSender	Sends messages from the outgoing filter stack to an SMTPServer.
SenderFilterAdapter	Adapter class for objects in the outgoing filter stack.
SpyFilter	Searches incoming messages for test commands and game moves.
TrashDateMonitor	Removes old messages from the trash.

Package talx.model.filters Description

Provides message filter classes. This package contains the classes that comprise the incoming and outgoing filter stacks. The incoming filter stack is comprised of receiver filters and the outgoing filter statck is comprised of sender filters. Each filter receives either a good message through newMailArrived or sendingMail, or a bad message as FilterActivated. The filter must decide to rebroadcast the message as either good or bad. The general contract is that filters should not move a message from bad status to good status. They may move messages from good to bad, or produce other side-effects, however. Typically, a filter will simply extend one of the adapter classes and only provide a filterMessage method.