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 |
I'm attempting to send mail with a DDIF attachment to a remote ALL-IN-1 X.400 Mail server. I'm a complete novice with ALL-IN-1, so bear with me if the questions are very basic. I have A1MAIL running on a VMS system, with display set back to a workstation, and I've started up the session with /int=decw. There are 2 apparent problems. The first is that there are 2 attachments instead of just 1 (the DDIF). The first attachment contains the following error message: Delivery/Receipt Notification received by: ALL-IN-1 MAIL V1.1-C Report 1. Actual Recipient: (FINNERTY) Message NOT DELIVERED, reason is: Unable to transfer. Diagnostic: Unrecognized recipient name. Failure report generated at: Reporting Node: RECALL Subject-Message Message Transfer ID: 3525091002101992/A00515/RECALL Subject-Message User Agent Content ID: 116A12891800 Subject-Message is attached. How do I diagnose "Unable to transfer." ? The second problem is that the DDIF does not display. What I get is: This message type cannot currently be displayed. What do I need to do to be able to display DDIF attachments? /Jim
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1553.1 | Wrong conf? | SCOTTC::MARSHALL | Do you feel lucky? | Fri Oct 02 1992 16:55 | 19 |
Hi, >> How do I diagnose "Unable to transfer." ? You look at the lines above and below it! Actual Recipient: (FINNERTY) Diagnostic: Unrecognized recipient name. Put simply, there is no user FINNERTY at the receiving end. This could either be because the mail has gone to the right node, and there is no-one there with that name, or the routing is wrong and it has gone to the wrong node, hence there is even less chance of finding a user with the right name! However, as you're talking about Teamlinks and DEC MailWorks (or whatever it's called this week :-) you might get better answers asking in the conferences dedicated to those products; topic 4 should contain pointers. Scott | |||||
1553.2 | Pointers | AIMTEC::WICKS_A | It wasn't supposed to end this way | Fri Oct 02 1992 17:24 | 3 |
TeamLinks is at ABBOTT::WINDOWS_OFFICE DEC MAILworks is at KOALA::X400MAIL |