The real problem though is not the actual size of the limit , but the manual interaction that is required and the time delay until rejection. If the list could be changed to automatic rejection this would solve the problem . Sebastian
Am 16.09.2011 19:21, schrieb Thomas Beale: > The 40kb limit was one of the sysadmin rules at UCL, and I happen to > agree with it (obviously, it could have been 50 or 100 or whatever, but > they use 40). I know it is sometimes annoying but it does prevent > massive attachments. Some years ago I was on probably 6 HL7 lists (they > have about 40) and there was not only no limit to size, but continual > cross-posting, with the result that 3Mb attachments were regularly sent, > and received 4 times! I for one don't want to go there again.... i think > today there is always an option for putting up some large file and just > emailing the link to it. > > If people want to up the actual current limit of 40kb to 70, 100 or so, > that is certainly doable, but I am not sure what problem it is solving. > > - thomas > > On 16/09/2011 17:42, Rong Chen wrote: >> Hi all, >> >> I am quite happy with the current infrastructure - mailing lists, >> issue tracking and SVN repositories. One thing I am missing for the >> java project is a build server, something like Apach Continuum that >> can check out the latest code, compile, run all the testcases, and >> publish reports and successful builds somewhere. >> >> Sebastian, It seems we have a manual step in the process of >> rejecting(or allowing) large mail. At least that's the case with the >> java list that I am monitoring. It will be convenient if the mail is >> just bounced automatically if it's too large. Perhaps there is a >> setting somewhere we could use with the current mailing list software. >> >> Cheers, >> Rong
