> If the error message about too many recipients occurs in the
> SMTP-connection you should be able to code the RemoteDelivery
> to handle it
If the server is behaving correctly, section 4.5.3.1 of RFC 2821 should
apply. JavaMail conforms to that RFC, so he should be able to turn partial
sending
Noel J. Bergman wrote:
OK. If I want to work around this it seems I have to build something
that sits in front of James to accept new messages, sort by domain
and slowly dispatch emails with similar domains
That would not be helpful. See
http://wiki.apache.org/james/JamesV3/HighVolume for so
> OK. If I want to work around this it seems I have to build something
> that sits in front of James to accept new messages, sort by domain
> and slowly dispatch emails with similar domains
That would not be helpful. See
http://wiki.apache.org/james/JamesV3/HighVolume for some discussion on
chang
On March 8, 2004 1:39 pm, Noel J. Bergman wrote:
> > It seems there is a bug in James in that it batches too
> > many recipients to a particular domain and that domain's
> > SMTP server responds with:
>
> Not a bug. A limitation regarding an anti-spam measure taken by the remote
> server.
>
> Ther
> Where does james determine whether to batch a bunch of emails?
> Is it in the RemoteDelivery mailet?
It just processes whatever is attached to the mail object.
--- Noel
P.S. Please turn off HTML e-mail
-
To unsubscri
On March 9, 2004 8:49 pm, Bosco So wrote:
> Where does james determine whether to batch a bunch of emails? Is it in
> the RemoteDelivery mailet?
>
> How does james do this batching? Does it look at the outbound queue to
> determine whether a bunch of messages should go to the same domain?
I assume
It seems there is a bug in James in that it batches too
many recipients to a particular domain and that domain's
SMTP server responds with:
Not a bug. A limitation regarding an anti-spam measure taken by the remote
server.
There is no setting for this, although there are pl
> It seems there is a bug in James in that it batches too
> many recipients to a particular domain and that domain's
> SMTP server responds with:
Not a bug. A limitation regarding an anti-spam measure taken by the remote
server.
There is no setting for this, although there are plans to support i
Hello,
I'm sending out notice to my ScheduleWorld clients that a new release is
available. (It's not spam as they agreed to receive these notifications)
It seems there is a bug in James in that it batches too many recipients to a
particular domain and that domain's SMTP server responds with:
R
