Danny Angus wrote: > IMHO this.. > > I aspire to program and offer a service, a service which > > eliminates spam by forwarding messages from unknown senders > > only after those senders have posted bond with a > > micropayment. So I need to insert my functionality in the > > midst of the process of forwarding. > > .. should be achieved using mailets and matchers, the best thing to do is to > get your head round their configuration, and the mailet API.
I certainly have been trying to do this. But I find it difficult to understand what I should do, given the documentation as it presently exists. Perhaps part of my weakness is that I have no prior experience administering sendmail, or a similar program, so I can not bring to my attempt to use James any experience telling what I need to do to configure and run such a program. > There shouldn't really be any need for you to greatly understand how james > contains mailets if you understand how to use the container, it should hide > low level mail handling, and mailet instatiation from your specific process > logic. I agree if what you are describing is a goal, toward which the developers and documenters of James should continue to aim, rather than a present reality. But my experience during a few weeks of studying James suggests that this goal has not yet been reached. I've scanned all the readily evident documentation and read much of it (indeed, I've read many parts twice now). But, for instance, this "container" that you say I need to understand seems new to me. Have I overlooked its documentation? Is it a particular class, a package, or the whole of James? Where can I read about it, apart from reading the source code of it? > Check out matcher and mailet code in org.apache.james.transport.mailets, and > mess with ~/james/apps/james/conf/config.xml to see the effect of changing > mailet/matcher & processors to build new flows and behaviour. I think there are people who are good at experimenting with configuration commands and then inducing, from the observed behavior, how the system can be used to their advantage, but unfortunately I don't think I am one of them. Since I am hoping to offer a service, I think I owe my prospective customers an administration whose knowledge of the system is more sturdy than "Duh, it worked before." Also, I'm curious. I want to understand much of the functioning at the level of the Java source. Thank you, Rich Hammer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
