abaxter@PIKES.DENVER.COLORADO.EDU (Alan Baxter) (02/07/90)
I can't receive fixes-1 from xstuff@expo.lcs.mit.edu because it is larger than 50000 bytes, i.e. 63113 bytes. The mailer at ncar has a message size limit of 50000 bytes. Could fixes-1 be broken up into two files, each of which is smaller than 50000 bytes? How about a policy of making sure that none of the mail archiver's files are greater than 50K? I know the instructions for the archiver say to not ask for multiple files totaling more than 100K bytes, but it seems that 50K would be a more reasonable limit - at least ncar's mailer thinks so. I've noticed that an attempt was made to keep the R3 fixes smaller than 50K, although I never got fixes 5 and 6 because they were slightly larger than 50K. In fact the instructions for getting the R3 fixes explicitly say the following: Although xstuff will handle requests for multiple fixes in one message (e.g. send fixes 3 4), you shouldn't ask for more than 50Kbytes at a time. Is there anyone else with this problem, or does ncar have the only mailer with this restriction :-). Alan Baxter (303)444-0094 VEXCEL Corporation abaxter@pikes.denver.colorado.edu 2477 55th St. Boulder, CO 80301
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (02/07/90)
Could fixes-1 be broken up into two files, each of which is smaller than
50000 bytes?
I'll send you pieces directly.
How about a policy of making sure that none of the mail
archiver's files are greater than 50K?
The inanity we have to put up with is constantly amazing.bob@MorningStar.Com (Bob Sutterfield) (02/08/90)
In article <9002070208.AA16319@pikes.Denver.Colorado.EDU> abaxter@PIKES.DENVER.COLORADO.EDU (Alan Baxter) writes:
I can't receive fixes-1 from xstuff@expo.lcs.mit.edu because it is
larger than 50000 bytes, i.e. 63113 bytes. The mailer at ncar has
a message size limit of 50000 bytes.
You could always get it via FTP or UUCP instead.