You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Chase Seibert <ch...@bullhorn.com> on 2006/09/27 17:45:44 UTC
update on fast fail?
I'm in the beginning stages of evaluating JAMES. While I agree with some of the points in http://wiki.apache.org/james/NoFastFail, I would still like to persue implementing fast fail under JAMES.
1. Is it still the case that fast fail is not supported for non-existant recipients on domains you host?
2. How do you set up fast fail for relaying attemps? This is alluded to on that wiki entry.
3. Are there any work-arounds used in practice to implement fast fail?
If anyone is interested, the primary reason we want to use fast fail is that we are planning on out sourcing spam filtering to Postini, which recommends that we fast fail non-existant recipients. Personally, I'm also more comfortable with fast fail, as that is what all other servers I have come into contact with do by default.
-Chase
Application Developer
B U L L H O R N
Staffing and Recruiting Software On Demand
The Last Software You'll Ever Need
www.bullhorn.com
Re: update on fast fail?
Posted by Stefano Bagnara <ap...@bago.org>.
Hi Chase,
we started supporting fastfail (that wiki page is really old).
JAMES Server 2.3.0 (currently in RC3) already contains some experimental
interface and mechanism to enable fast fail but it does not include a
fast fail handler to che for the availability of a specific user (you
can write an handler for it).
James Server 2.4.0 (or 3.0, we have still to define the version) will
include official support for similar fastfail filters and James Server
will be extensible using this mechanism.
Stefano
Chase Seibert wrote:
>
> I'm in the beginning stages of evaluating JAMES. While I agree with some of the points in http://wiki.apache.org/james/NoFastFail, I would still like to persue implementing fast fail under JAMES.
>
> 1. Is it still the case that fast fail is not supported for non-existant recipients on domains you host?
> 2. How do you set up fast fail for relaying attemps? This is alluded to on that wiki entry.
> 3. Are there any work-arounds used in practice to implement fast fail?
>
> If anyone is interested, the primary reason we want to use fast fail is that we are planning on out sourcing spam filtering to Postini, which recommends that we fast fail non-existant recipients. Personally, I'm also more comfortable with fast fail, as that is what all other servers I have come into contact with do by default.
>
> -Chase
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: update on fast fail?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I'm in the beginning stages of evaluating JAMES. While I agree with
> some of the points in http://wiki.apache.org/james/NoFastFail, I
> would still like to persue implementing fast fail under JAMES.
We have fast-fail support in JAMES v2.3, and considerable effort is going into enhancing it even more. We all recognize that the SMTP landscape has continued to change, with millions of MS-Windows users contributing to billions of spoofed SPAM messages.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org