Why not have a filter that adds the recipient to a database when the message comes in and then have another program that is running all the time check the database for new entries and then goes to the maildir for the recipient and scan the new message? If the message is spam then remove it from maildir.=20
Probably not the best way to do it, but it separates the load from xmail filters and slowing it down. Bill >---------- >From: Edinilson J. Santos[SMTP:[EMAIL PROTECTED]] >Sent: Saturday, June 29, 2002 5:21 PM >To: "[EMAIL PROTECTED]" >Subject: [xmail] Re: Message steps > > Davide, > >Xmail is very fast, no doubt about this. >The problem is: I'm using the windows version of xmail and using = windows >scripting host to handle filters. >Some filters uses a file definition (to block spam, for example) that >increase every day and is more fast to run a separated process that = loads >allfilters definitions once and stay in memory for future scanning. >Without this, will be imposible to any machine handle and filter = thousands >ofmessages/day without slowing down Xmail (first impact of this could = be >noticed in POP3). > >For this reason, I'm trying to do a script that simple do that job = without >"to confuse" Xmail. > >Please, only send me the steps (something like 1-spammers.tab, >2-mailproc.tab, 3-domain.tab, and so on) of a incoming message. >The beta version of this filter is working today in a domain that = handle +- >5000 messages/day without problems BUT I=B4m afraid if isn't missing = something >around. > >Thank you again! > >Edinilson > > >--------------------------------------------------- >ATINET-Afiliado UOL de Atibaia >Rua Francisco R. Santos, 54 sala 3 >ATIBAIA/SP Cep: 12940-250 >Tel Voz: (0xx11) 4412-0876 >http://www.atinet.com.br > > > >--------- Mensagem Original -------- >De: "Davide Libenzi" <[EMAIL PROTECTED]> >Para: "XMail mailing list" <[EMAIL PROTECTED]> >Assunto: [xmail] Re: Message steps >Data: 29/06/02 19:48 > > > >On Sat, 29 Jun 2002, Edinilson J. Santos wrote: > >> >>Davide, >> >>Could you tell me all steps of a message incoming to xmail? >>We'are developing a filter that will scan messages after they arrive = (to >>avoid xmail "blocks" in certain circumstances) and we need to know = which >>steps we will need to make "in hand" > >XMail does not "block" and actually an high filter load will create a = nice >input auto-limitation. What you're very likely trying to achieve is to >make XMail to work with a mail filter that pretend messages to be = removed >from the spool to be later reinjected. If you will tweak message steps >directly you're very likely to make XMail to misbehave because of file >locks. There are other ways to do that, using a smarter filter for >example, that will tag messages already scanned to distinguish the = already >processed ones. > > > > >- Davide > > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED][1] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED][2] > > > > > > >--- Links --- > 1 mailto:[EMAIL PROTECTED] > 2 mailto:[EMAIL PROTECTED] >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED] > > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
