Title: | LinkWorks V3.0 Notes Conference |
Notice: | LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues |
Moderator: | tacklr.apd.dec.com::TACK_L m::TACK_L |
Created: | Tue Jun 28 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2269 |
Total number of notes: | 8338 |
Hi, A customer has installed V3.0.8 on OpenVMS and configured the XMPROC.OPT with the line $ XMSENDFLG == "c" in order to have LinkWorks External Mail omitting the X.400 ISO extensions with LinkWorks object information in the message envelope (See Note 1966), and rather have them in a separate IA5 bodypart. This does not seem to work as expected. The envelope extensions are still sent, and no additional bodypart is created. Decoding the messages archived by the MTA indicates this (and the messages are rejected with diag. 14 from the ADMD's MTA). Apart from possible typos in the flag setting, what can be causing this? Is there something I've misunderstood here? Regards, Lars Even.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2090.1 | Check version of XMSEND.EXE | UTROP1::schimmb.uto.dec.com::schimmel_b | Mon Jan 27 1997 10:15 | 31 | |
Lars, As far as I can judge, the update to suppress X.400 ISO extensions was NOT present in LinkWorks 3.0.7 (for OpenVMS) and is present in the LinkWorks 3.0.8 kit (for OpenVMS). o Are you sure that external mail of LinkWorks 3.0.8 is installed ? A method to verify this is to look to the UNIX style SCCSID's in XMSEND.EXE. I just did this for the two different versions (i.e., 3.0.7 and 3.0.8) of XMSEND.EXE after moving the executables to a UNIX system. When you execute the command: what xmsend.exe | fgrep mailsend than 3.0.7 shows mailsend.c 3.13 while 3.0.8 shows mailsend.c 3.14 Of course you need the last one and to my best knowledge, the option XMSENDFLG == "c" does work ! Regards, Berd Schimmel |