If only part of a domain's mail (perhaps only a single user's POP account) is being handled by this instance
of James it is important that outgoing mail addressed to this domain that is not intended for James be properly delivered.
To enable this filtering the FetchPOP scheduler adds a header, X-fetchedby, to the fetched message. This header can be checked using
the provided matcher FetchedFrom. This matcher can be used to direct fetched mail to a processor set up
to handle mail fetched from one or more POP3 accounts. The matcher should be used exactly once in the mail
pipeline for each FetchPOP task, as the matcher removes a matching header to prevent outgoing replies or
redirections from looping.
The FetchedFrom matcher is configured with the name of the particular FetchPOP task it is supposed to match. In general,
this matcher will be used to direct mail to a custom processor for further processing. A mailet tag such as the
following
 |  |  |
 |
<mailet match="FetchedFrom=fetchtaskname" class="ToProcessor">
<processor>fetchprocessor</processor>
</mailet>
|  |
 |  |  |
where fetchtaskname is the name of the FetchPOP task being matched and fetchprocessor is the name of the fetched mail
processor can be used to this purpose. The fetched mail processor should contain mailets which will filter
and forward mail to real local or remote users. This can be achieved in the usual fashion as described in the
SpoolManager configuration section and in the out of the box
configuration file.