ent: 10 May 2005 18:53
> To: James Users List
> Subject: Re: Serious bandwidth begin consumed by James
>
>
>
>
> [EMAIL PROTECTED] wrote:
>
> >>I tested by:
> >>
> >>- I had two test servers both setup with james (Sender, Receiver)
> >>-
On 5/11/05, Daniel Perry <[EMAIL PROTECTED]> wrote:
> James recieves data command. Responds accordingly.
> James starts receiving data. Once hit's maximum limit, an exception causes
> james to send a 552 error (immediately).
> Now, this is where i might be missing somthing, but James then seems to
> > If i am right, it should:
> > Notice to size limit has been reached, and stop buffering
> the message.
> > Continue reading the message until . is reached
> Send 552
> > error!
> > Reset state, and continue to accept other messages.
>
> IMHO when the limit is reached, we should either (soft
> > If i am right, it should:
> > Notice to size limit has been reached, and stop buffering
> the message.
> > Continue reading the message until . is reached
> Send 552
> > error!
> > Reset state, and continue to accept other messages.
>
> IMHO when the limit is reached, we should either (soft
On 5/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > IMHO when the limit is reached, we should either (soft fail)
> > listen to everything and ignore the data as you describe
> > above, or (hard fail) kill the connection. Right now what we
> > does not make a lot of sense, since we haven't
> On 5/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > IMHO when the limit is reached, we should either (soft fail)
> > > listen to everything and ignore the data as you describe
> > > above, or (hard fail) kill the connection. Right now what we
> > > does not make a lot of sense, since
Daniel,
I was going to make a change to the code, at the outer level but actually,
I've got a concern. If something ELSE in the server led to OutOfMemory
conditions, we'd start purging the outgoing spool. That would be
catastrophic.
I'll look at the specific case of the bounce message. I belie
(when i get a free minute!)
Daniel.
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: 03 June 2005 22:00
> To: James-Dev Mailing List
> Subject: RE: Serious bandwidth begin consumed by James
>
>
> Daniel,
>
> I was going to mak
Did anyone else ever look into the (serious) issues i highlighted with the
SMTP protocol handler and remote delivery mailet?
1. endless remote delivery retries on an exception when remote delivery
bounces a message (initial problem) - can be delt with using the patch i
supplied, to catch the error
|
| cc:
|
| Subject: [bump]
Daniel,
I did look at the one for RemoteDelivery, and there are a couple of
solutions there, but in general I think you've a point.
Please make sure to do your patches against the current trunk, since we've
been making changes. For example, buffering was recently changed in
SMTPHandler.
Daniel,
I will post today a new nightly build. If you are interested in testing the
new improvements, that'd be great.
> 1. endless remote delivery retries on an exception when remote delivery
> bounces a message
> 2. Error (eg. OutOfMemoryError) at any point in remote delivery causes
> endless
> > 3. Non RFC compliant rejection of messages over size limit,
> and this
> > also screws up the remainder of the SMTP session.
>
> Stefano was working on buffering in SMTP. I don't know and
> haven't looked to see if he got to this one, or if we still
> need a patch.
NO, my patch is only t
13 matches
Mail list logo
