| I think you mean a uuencoded (not uudecoded) file.
UUENCODE turns a binary file into ASCII, which is
then sendable via SMTP. A uudecoded file would be
a binary file.
How are you sending it (using a UCX SMTP sender on
the VMS machine, or through an RMC)? Are you using
NMail?
Have you looked at the headers of the messages
(Message -> Properties, then click on the Headers
tab) to see if there's any difference between the
undecoded messages and the final one?
|
| Thanks for your response
sorry, i did mean uuencoded file as you have rightly mentioned
I am using rmc (us3rmc) and also nm%
i checked up the headers and the route it took was different
in two of the mails (copies of the same mail i should say)
and also the size of the mails received is different each time,
the last copy (the one with the proper attachments ) biggest
the others i am able to see the first line of the uuencoded
message as begin 600 but the end of the message is not
having the "end" line as in any uuencoded message.
we are running ucx 3.2 on use vms 5.5-2 but the SMTP
is not working consistently hence i did not try through
smtp%.
any help would be greatly appreciated
Thanks and regds
jayaram
|
| Well, us3rmc is in Palo Alto in the US. Unfortunately, the only
RMC in AP is JRDMAX in Japan, so right now your messages have to
go to the US and back to get from VMSmail to Exchange.
Usually if the whole message can't be delivered (and that seems
to be the problem here), then the recipient drops the partial
message and the sender tries again. I think we need to know
where the message is being resent to see how it can be fixed.
Can you capture the headers as text and mail them to me?
(MaryEllen Kennedy in Exchange or [email protected]). Don't
forward the messages, as the header information may not make
it through.
|