On the client, you can use an agent triggered “before new mail arrives” or “after new mail arrives”.
On the server, you need to get to know Domino quite a bit. There’s no easy way to trap mail routing, since the Domino Router seems to use some non-published API’s to do its magic - see Notes/Domino API Toolkit user’s guide database, documents “Agents” and “Extension Manager” for some guidance.
BTW: Did you check the market? Looking at tools like Darren Crocker’s excellent no.Spam.domino (http://www.drcc.com), Mark Ramos’ spamJam (http://www.granite-software.com) and various other commercial offerings in that area, what do you want to achieve? If it’s not a personal learning you’re hoping to get out of this, I’d question the allocation of resources to a problem that has been mastered and solved.
Subject: RE: or just configure the server to use the blacklist filter
I’ve been working on a similar process. And as one of the other posters indicated, I will add the code to the client to look out for my e-mails and share it with co-workers. So far, I have a function to remove the odd characters from a string… ie: v@i@a… becomes via… My next step is to keep a list of words that I dont want to see in my emails and when that are found do not allow the email to be saved to my mail database.
modules are called add-in’s in the domino/notes world. download the 6.x API Toolkit and check the help for the following EM functions. oh, you can only write these in C, not C++, you can use a C++ IDE but the code must be C (last time i looked anyways)
EM_SMTPCONNECT - processing an inbound smtp connection
EM_SMTPMESSAGEACCEPT - processing an accepted smtp message
EM_NSFNOTEUPDATEMAILBOX - processing any message placed into any mailbox type database (from database properties, not template based)
these three EMs cover everything you need to build a domino server spam add-in
you would use different API EMs for client side processing, they are there I just never used them so don’t know what they are called.