Conference iosg::all-in-1

    Hi, Graham.
    
       My customer is running ALL-IN-1 V3.0A
    
    
    Best regards,
    Mascot.

(and while we're waiting...)

V3.0A - so ALL-IN-1 is still using the MR V1 interface i.e. MR translates the 
delivery report information into a text message - I don't know exactly how 
this works.

This also assumes that the report isn't already in text - it may have been 
generated by an ALL-IN-1 V3.0A system.

But I'm still not sure exactly what you want to achieve. The most common 
reason for a non-delivery report is that the originator typed in the wrong 
address. So you'll get an NDR which says something like NO SUCH USER. Is this 
the one you want to change? What do you want to change this to?

You only rarely get reports of network problems - though you might get 
"ALL-IN-1 was unable to send your message . . ." ones - are these ones the 
problem?

In any case, just replacing all reports with "remote node is unreachable" is 
only going to confuse everyone. As a support person, I rely on these reports 
to try and work out where the problems lie.

Can you try and explain exactly which reports are causing a problem, and 
exactly what the customer wants to change?

grahame

But I'm still not sure exactly what you want to achieve. The most common 
reason for a non-delivery report is that the originator typed in the wrong 
address. So you'll get an NDR which says something like NO SUCH USER. Is this 
the one you want to change? What do you want to change this to?


ANS : Because my customer is a banking environment, his end users does not
      have computer knowledges. When his end users send a mail to other 
      people and the mail is undelivered due to "node" unreachable or
      or no receipent problem, it will have a return message to his end 
      users. His end users will not know what is the content. Therefore,
      my customer ask that whether it can modify the undelivered reply mail
      so that his end users know what it means. I do not know what is the
      mechanism non-delivery report generation. Can we simplified the 
      report before his end users to receive the mail.

      I don't know what it means NDR.

      Any advice should be appreciated
          
 
    

Hi Mascot,

	NDR = Non-Delivery Report

The simple answer to your question is yes, I think it is possible. But it will 
involve several stages, because the reports are generated in different ways by 
different pieces of software. For instance (and I hope someone is checking all 
of this!)

 - if the report is generated by ALL-IN-1 V3.0 or earlier, it is a text 
message. This text is built up from entries in the ALL-IN-1 message files. I 
would guess that you could only change the meaning of these messages - you 
cannot add more or remove any

 - if the report is generated by Message Router (or by ALL-IN-1 V3.1 or 
later, or by an X.400 MTA such as Mailbus 400), it uses numbers to represent
the text. The text reports are then generated by the Message Router on your
system - I don't know exactly how this is done, but perhaps there are template
files which you can change. 

grahame

I should add that when you upgrade your ALL-IN-1 system from V3.0A, then 
ALL-IN-1 (and not MR) converts the NDR numbers into text. I think this is done 
by template (.BLP) files in ALL-IN-1.

grahame

    I find some  similiar files that mentioned in 2523.6 and 2523.7.
    These files are named MAILSNDF2.BLP, MAILSNDF3.BLP and MAILUNBF.BLP 
    on directory oa$disk:[allin1.blp_english], but my customer does not have
    these files. Are they customerization file ? If it is a trailor made
    files. How can I do that ?
    
    
    
    

    These files are certainly in the V3.1, V3.2 and V4.0 kits, but perhaps
    they weren't in V3.0 if that's what your customer is running. V3.0 is
    so old that I don't have those files easily accessible anymore.

    The files were also in the V3.0 kit.
    
    Martin  (who knows where the V3.0 kits are hidden).
    

The best solution to this problem is to upgrade to V3.1 or V3.2 and customise
the boilerplate files that are used to generate the end-user messages.  You can
also customise the message symbols that are merged into these boilerplates.

You can then trivially make a non-delivery message that looks something like:

    Your message could not be delivered to: smith@a1@rdgeng@reo
    Because there is no such user on the mail network
or:
    Your message could not be delivered to: albert einstein@zko
    Because the recipient's system could not be reached

which is I assume what you want.  However, note that by doing this simplication
and making these generalisations you will be losing information that may be
relevant to the system manager in tracing the problem.

Note also this will only work for notifications that arrive at your system as
proper encoded notifications.  If, for example, you're using MRGATE, you will be
unable to change any non-delivery notifications it sends back to you.  The same
will be true of NDNs received from older (V3.0) ALL-IN-1 systems still in your
network.

The default information and messages that ALL-IN-1 displays closely follows the
X.400 standard - most of the message texts come directly from that standard. 
Admittedly they're not the most friendly messages, but that's standards
conformance for you...

Scott

    Thanks for all to give a lot of suggestion to me.