james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hontvari Jozsef" <hontva...@solware.com>
Subject Re: Processor naming thoughts?
Date Mon, 14 Apr 2003 17:34:53 GMT
"I've made changes here, for example,
to separate out error, spam, and relay-denied mail."

I cannot agree more. I have setup James several times, and the current
default configuration file is always disappointing, it lacks the most
obvious things, like separation of bounce messages and meaningful
notification messages.

I add that using the postmaster address as a default sender in the config
file is a really bad idea. This is a warm invitation for viruses. Actually
the sender should be default (at least in the config file) to
MAILER-DAEMON@... with null address. I guess the null address would require
a change in the notification mailet too, not only in the configuration.


----- Original Message -----
From: "Noel J. Bergman" <noel@devtech.com>
To: "James Developers List" <james-dev@jakarta.apache.org>
Sent: Monday, April 14, 2003 7:13 PM
Subject: RE: Processor naming thoughts?


> Serge,
>
> I agree with the idea of renaming setState to something else.  But I am
not
> quite convinced that renaming processor to queue will have any beneficial
> impact.  The first thing that I think we could do is demonstrate better
use
> of processors within the stock config.  I've made changes here, for
example,
> to separate out error, spam, and relay-denied mail.  We could further
factor
> out, within reason, the mail process to give people a better example of
how
> to use processors.  As it is, we pretty much have just root, transport,
> error and spam.
>
> The tradeoff is that the current architecture is optimized for fewer
> processors.  LinearProcessor is pretty tight, but there is overhead going
> through the spooler.  However, I think that we can address that issue, and
> the benefit of better understanding for the majority of users outweighs
the
> optimization needs that more expert users can achieve.
>
> --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org


Mime
View raw message