Serge Knystautas wrote: > > Not really. The best you can do is have James grab emails using > fetchmail (or receiving them directly), running them through the > filters and adding whatever headers you want that your Outlook client > can then use to put into the appropriate folders.
"Not really". What do this apply to? If this is a response to... > Of course there are many other ways to handle this within James. ...then what was meant was that within James, the spam processor can be configured to do many different things with the messages other than the example described, including silently trashing it (not a recommendation), seeding the Bayesian filter and so forth. Or am I "not really" understanding you? -- Steve > -- > Serge Knystautas > Lokitech >> software . strategy . design >> http://www.lokitech.com > p. 301.656.5501 > e. [EMAIL PROTECTED] > > On 10/7/05, Steve Brewin <[EMAIL PROTECTED]> wrote: > > Gaurav Handa wrote: > > > I am trying to make the current James mail server to act as a > > > Email filter > > > fetching mails from the pop server and doing a check to > > > verify that the > > > incoming mail is a spam or not. I need to then move the mail > > > to a specified > > > folder in Outlook. > > <snipped> > > > > The way I have done this in the past is to have the James' > mailets that > > detect spam such as SenderInFakeDomain and InSpammerBlacklist pass > > processing to the spam processor, which includes... > > <mailet match="All" class="NotifyPostmaster"> > > <sender>unaltered</sender> > > <prefix xml:space="preserve">[SPAM] </prefix> > > <inline>heads</inline> > > <attachment>message</attachment> > > <passThrough>false</passThrough> > > </mailet> > > The <prefix/> stanza adds "[SPAM] " to the header so its > easy for an Outlook > > filter or a plug-in such as SpamBayes - http://spambayes.sourceforge.net/ to > detect it. By making the original message an <attachment/> the potential > viral load is not exposed to the mail client. Either an Outlook filter or > SpamBayes can move the mail to a given folder. > > Of course there are many other ways to handle this within James. It depends > on your specific needs. > > -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
