Right, but practically speaking if James cannot support sending to major email vendors it can't really be considered a useable mailing list manager, as far as I am concerned. I mean, I simply cannot use James if a significant portion of my users will be left in the cold...
A common approach I've seen is for the list manager to detect when a recipient list is getting to long, and break it up into smaller chunks that can be sent separately. Cheers -- Peter T. Brown Founding Partner Headless Hunter, Inc. [EMAIL PROTECTED] "Rewarding you for who you know." http://www.headlesshunter.com/ > From: "Noel J. Bergman" <[EMAIL PROTECTED]> > Reply-To: James Users List <[email protected]> > Date: Wed, 15 Jun 2005 09:01:30 -0400 > To: James Users List <[email protected]>, Andrew Hayden > <[EMAIL PROTECTED]> > Subject: RE: Connection timed out and Too many recipients > > Andrew Hayden wrote: > >> this is an issue with hotmail, yahoo, etc's spam-prevention >> techniques. They tend to set very low limits on the number of >> recipients that a message can be sent to at once > > Which is, by the way, an RFC violation. I appreciate why they do it, but > their limits are well below those mandated by RFC 2821: > > The minimum total number of recipients that must be buffered is > 100 recipients. Rejection of messages (for excessive recipients) > with fewer than 100 RCPT commands is a violation of this > specification. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
