indra@amdcad.AMD.COM (Indra Singhal) (02/09/90)
I tried what Dave suggested about adding [nosave] as part of the text of the message to prevent it from being appended to the =sent file. It did not work. Ofcourse, there was one difference, this particular mail was going out to an addressee who had an exclusive folder, that is where the outgoing message got appended in spite of the [nosave]. The [nosave] was on a line by itself. I am running PatchLevel 15. clues? -- iNDRA | indra@amdcad.AMD.COM (Indra Singhal) (408) 749-5445 | {ames decwrl apple pyramid sun uunet}!amdcad!indra | MS 167; Box 3453; Sunnyvale, CA 94088
silvert@cs.dal.ca (Bill Silvert) (02/12/90)
In article <29101@amdcad.AMD.COM> indra@amdcad.AMD.COM (Indra Singhal) writes: >I tried what Dave suggested about adding [nosave] as part of the text of >the message to prevent it from being appended to the =sent file. It did >not work. I hear a lot of complaints about this not working. The correct syntax is that there must be a space, i.e. [no save]. It might be worth expanding the ELM syntax not to be so picky, given the number of problems this causes. -- Bill Silvert, Habitat Ecology Division. Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2 UUCP: ...!{uunet,watmath}!dalcs!biomel!bill Internet: bill%biomel@cs.dal.CA BITNET: bill%biomel%dalcs@dalac
taylor@limbo.Intuitive.Com (Dave Taylor) (02/13/90)
In article <1990Feb12.140134.22356@cs.dal.ca> bill@biomel.UUCP writes: > In article <29101@amdcad.AMD.COM> indra@amdcad.AMD.COM (Indra Singhal) writes: >> I tried what Dave suggested about adding [nosave] as part of the text of >> the message to prevent it from being appended to the =sent file. It did >> not work. > > I hear a lot of complaints about this not working. The correct syntax > is that there must be a space, i.e. [no save]. It might be worth > expanding the ELM syntax not to be so picky, given the number of > problems this causes. A curious change: Check out my source to version 2.01 gamma: in "savecopy.c", about 160 lines into the file: if (strncmp(buffer, DONT_SAVE, strlen(DONT_SAVE)) == 0 || strncmp(buffer, DONT_SAVE2, strlen(DONT_SAVE2)) == 0) { /* second test added due to an imcompatability between the documentation and the software! (Thanks Bill!) */ fclose(message); fclose(save); chown(savename, userid, groupid); return(TRUE); } where, in "defs.h", DONT_SAVE and DONT_SAVE2 are defined as: #define DONT_SAVE "[no save]" #define DONT_SAVE2 "[nosave]" As you can see, it used to like either of 'em. Any scoop on why someone would have changed that?? -- Dave Taylor Intuitive Systems Mountain View, California taylor@limbo.intuitive.com or {uunet!}{decwrl,apple}!limbo!taylor
syd@DSI.COM (Syd Weinstein) (02/13/90)
taylor@limbo.Intuitive.Com (Dave Taylor) writes: :In article <1990Feb12.140134.22356@cs.dal.ca> bill@biomel.UUCP writes: :> In article <29101@amdcad.AMD.COM> indra@amdcad.AMD.COM (Indra Singhal) writes: :>> I tried what Dave suggested about adding [nosave] as part of the text of :>> the message to prevent it from being appended to the =sent file. It did :>> not work. :> :> I hear a lot of complaints about this not working. The correct syntax :> is that there must be a space, i.e. [no save]. :A curious change: Check out my source to version 2.01 gamma: :in "savecopy.c", about 160 lines into the file: : if (strncmp(buffer, DONT_SAVE, strlen(DONT_SAVE)) == 0 || : strncmp(buffer, DONT_SAVE2, strlen(DONT_SAVE2)) == 0) { :where, in "defs.h", DONT_SAVE and DONT_SAVE2 are defined as: :#define DONT_SAVE "[no save]" :#define DONT_SAVE2 "[nosave]" :As you can see, it used to like either of 'em. Any scoop on why :someone would have changed that?? It didn't change, its still that way. Although the routine is now mailmsg2.c instead of savecopy.c, due to combining a common function. Both should still work. -- ===================================================================== Sydney S. Weinstein, CDP, CCP Elm Coordinator Datacomp Systems, Inc. Voice: (215) 947-9900 syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235