| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hi, This is Xposted in the CLI conference. I did some work at customers, mostly dealing with sending mail to and from X.400 MTA's. At one site there was editor integrated. The change in OAET.MAR reflected to a wrong DECBODYpart. (Not decbody7 hex 69) I changed the et_nbs definition to ^X69 the macro TXTFMT in OAET.MAR. Get the new object and inserted in the appropiate library. Linked the whole stuff, but wonder no result ! The message goes out still with the 'old' bodypart. Question : Are the more places where this should be updated ? I think at the DDIF DOTS etc. They're also using the DECBODY7. Is there some special code somewhere which deals with the RMS semantic tag, if there is no sementic tag drop default to the FOREIGN DSAB ? reagrds Rob.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2936.1 | <Nothing ?> | IJSAPL::EISINK | Wed Jun 30 1993 19:33 | 11 | |
Hi,
I always thougt that there are some clever people around in this
notesfile whom are able to think accross the borders of their
imagination.
Soembody around who has some ideas about this, Is this CLI application
using their own code to handle the TEXT DSAB ? I cab't imagine how they
were able to implement this, especialy the fetch routine is capable of
handling these messages
regards
| |||||