Off topic here, but users should not be sending messages with 180 recipients.
a) many MTA's will refuse mails with 180 recipients b) cause's a huge overhead making, for instance, mobile receivers very unhappy This, of course, doesn't mean that it should not be possible to send messages to 180 recepients or that the webmail-function should contain bugs that prevent send messages to huge number of receipients. But in any case, let you client know that when sending messages to a large group of people he/she should use the BCC-field or use a mailling-list. Kind regards, Sander Holthaus > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of [EMAIL PROTECTED] > Sent: Monday, June 28, 2004 1:07 PM > To: [EMAIL PROTECTED] > Subject: [courier-users] Maximal length of To: header > > Hello! > > I would like to know why the real maximal length of To: > header is only 5000 characters? > > I found the following conditions in getrcpts function from > courier/submit.C source file, but I don't understand that: > > if (l > headerlimit || l > 5000) > headercnt=0; > > In my opinion the first condition is OK, because headerlimit > is big enough (100000 characters). Unfortunately, the second > condition can make troubles with long To: header. > > Why? One user of my mail system was trying to send message to > about 180 recipient. The length of To: header was greater > than 5000 characters and the webmail showed him the following error: > > 511 Headers specify no receipients. > sendmail: Unable to submit message. > > The appropriate code from getrcpts function gets 5000 > characters chunk of header. If the header is longer, the code > gets next chunk and lost previous. The user showed the error, > because second chunk of header To: didn't contain "To: ". > > I think that first condition (l > headerlimit) is enough and > the code should _add_ all line chunk to line buffer. > > My best regards! > > Pawel Tecza > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor > pitches, unmatched networking opportunities. Visit > www.blackhat.com _______________________________________________ > courier-users mailing list > [EMAIL PROTECTED] > Unsubscribe: > https://lists.sourceforge.net/lists/listinfo/courier-users ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
