<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10">
</HEAD>
<BODY>
I'm emailing the list to get ideas on how spambayes could be used in a mass email hosting setup, as an ISP would have. There wound/t be much trouble in setting up seperate sb databases per email account using existing methods already found in sb code, such as the mysql/sql option. Filtering can occur on the smtp recieve side, placing a header to be filtered by the client (or subject line). This is the easy part.<BR>
<BR>
The hard part is the training. I'll assume it's generally accepted that for spambayes to be effective, training must be done on a per account basis. One man's spam is another man's ham after all. So we need a training interface to handle a mass hosting setup that is per account.<BR>
<BR>
It gets worse though. IMAP folders could help here, but an ISP does not want users saving mail on the server. Also, support needs to be low, so I'm not sure expecting users to view source and cut and paste into a web app will be the answer either.<BR>
<BR>
Most email client support some form of 'forward as redirect', in which the message is sent again with a new envlope. The brainstorming here has gone down the road of some type of email account that does training, i.e. a <A HREF="mailto:ham@isp.com">ham@isp.com</A> and a <A HREF="mailto:spam@isp.com.">spam@isp.com.</A> the smtp server for these accounts would require authencation to prevent real spammers from using them, and also to tie the sender to an account and database for training. Using the forward as redirect, the user trains his database. I'm also thinking it would also be possible to detect if the user did not forward as a redirect, but instead did a normal forward, because there would be no recieved headers, and there would also be no spambayes headers, so we could reject the message for training and prevent the user from incorrectly training his account.<BR>
<BR>
We would want a basic online application for the user to tune his spambayes preferences, but again this isn't much to do and is really just working with exiting code and interfaces. I think if spambayes had a solution for the mail server in a mass hosting, it would get alot of use by ISPs who constantly hear spam complaints from users. Current commercial options are too costly and don't provide the results spambayes can. Current open source server solutons also don't compare with spambayes in results.<BR>
<BR>
I'm interested in hearing back thoughts, and open to other interface ideas. I'm ready to start coding away on the solution, but I want to be sure in the solution before I start =).<BR>
<BR>
Mike<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<FONT COLOR="#999999">__________________________________ </FONT><BR>
<BR>
<A HREF="mailto:michael.neel@mediapulse.com"><FONT COLOR="#000000" SIZE="2"><B><U>michael.neel</B></FONT></A><A HREF="mailto:michael.neel@mediapulse.com"><FONT COLOR="#808080" SIZE="2">@mediapulse.com</U></A><BR>
vice president of information systems<BR>
865.675.4455 x30<BR>
800.380.4514</FONT><BR>
<BR>
<A HREF="http://www.mediapulse.com/"><FONT COLOR="#a51c1e" SIZE="2"><U>www.mediapulse.com</U></FONT></A><BR>
<FONT COLOR="#999999">__________________________________</FONT>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>