Conference virke::mrmemo

.0> The message contains 94 Memo users, 2 System 36 users (via MRS) and 7
.0> Teamlinks users.  I'm not sure if this is the distribution list problem
.0> mentioned elsewhere.

    It probably is the "distribution list problem" since Memo only supports
    75 normal receivers, at least that was the limit a year or so ago when
    I checked (and then there were no plans to change it).

.0> I'm also not sure where the address comes from in the above message as it
    isn't one of mine!

    I guess you are referring to "MEMO SYSTEM THROUGH MRMEMO/GATEWAY"
    This fake recipient is generated by MRMEMO when there's nothing else to
    use. There are some type of error situations where Memo doesn't return
    a complete non-delivery message. When this happens, MRMEMO uses this
    dummy recipient.

.0> I believed that DECmailworks would send to Memo as 94 individual messages.
.0> Is this correct?

    I don't know - probably not, otherwise you would probably get 94 separate
    non-delivery messages!

    Even if there was an individual message for each recipient, the whole
    distribution list would probably be included in every message (with only
    one actionable recipient). Then you're stuck anyway since each non-
    actionable recipient also uses up a slot in the Memo message header.

.0> This works the other way with an identical address list set up in Memo.

    I'm not sure, but I think that distribution lists in Memo are implemented
    in a way that bypasses the 75-recipient limit by sacrificing some
    functionality, such as message correlation. I.e. you won't be able to
    see which recipients have received/read the message.

.0> Is there any solution to this?

    As long as the limitation is in Memo, I'm afraid there's no simple
    solution.

    An idea: You might check the possibility to use Memo's distribution
    lists "backwards". I.e. send a message from DECmailworks to a destination
    address in Memo that actually is a Memo distribution list. If that works,
    it would at least be possible to send to whole groups/departments when
    the predefined Memo distribution lists are sufficient. [My guess though
    is that it doesn't work.]

    Anders

The response from Verimation is that 72 is the limit on a single message.  
There are no plans to change this in V4 of Memo, which is a shame as we're 
installing it in a couple of weeks.

All the lists I need are duplicated on Memo as public distribution lists 
(PUDLs).  Therefore, I decided to try creating a test PUDL called DECDIR to 
see if I could send to it.  Both the Distribution List (VAGUK.DECDIR) and 
me (VAGUK2.MCMICHI) are registered in DDS.  When sending the message I get 
the following:

-----------------------------------------------
Delivery/Receipt Notification received by: DEC MAILworks V1.2

Report 1.
    Actual Recipient: (VAGUK.DECDIR@MEMO@GOLF)
        (*MRMRLP=1)
    Message NOT DELIVERED, reason is: Unable to transfer.
    Diagnostic: Message originator not authorized for use of the gateway.
    Failure report generated at: 

Reporting Node: GOLF

Subject-Message Message Transfer ID:
   9612081717011994/A05445/GOLF/11818C480B00

    Subject-Message User Agent Content ID: 11818C480B00
-----------------------------------------------

This surprises me as I don't have any form of DDS validation turned on and 
all addresses are registered in DDS anyway.

Any ideas?


Ian.

.0> Message NOT DELIVERED, reason is: Unable to transfer.
.0> Diagnostic: Message originator not authorized for use of the gateway.

.0> This surprises me as I don't have any form of DDS validation turned on and 
.0> all addresses are registered in DDS anyway.

.0> Any ideas?

    If DDS validation is disabled, it's not MRMEMO itself that rejects the
    message. It is Memo that sends a status message (non-delivery). The error
    codes in Memo are not identical to the ones used in MR (no surprise) so
    MRMEMO tries to translate Memo's error codes to MR diagnostics.

    There are tables in appendix D of "VAX MAILGATE for MEMO Operator's Manual"
    that describe how error codes are converted between Memo and MR.
    This particular MR error (Message originator not authorized for use of
    the gateway) could come from two different Memo error codes:

	1) Authorization failed
	2) Distribution rejected. Sender DGN is unknown

    If 1) is your problem, there is probably something in Memo that prevents
    external messages from accessing distribution lists. There could be an
    implementation limitation that prevents non-local users from using
    distribution lists or there is some kind of protection on the distribution
    list that must be changed to allow external users. Verimation should know.

    If 2) is your problem, you shouldn't be able to send to *any* Memo address.
    If this is the case, it's something wrong with your sender address. Are
    you using DDS address translation? If you are not, your sender address
    will not be VAGUK2.MCMICHI but something like prefix.user..a1m..a1mnode
    and this will be rejeced by Memo unless "complex name" name addressing is
    configured in Memo. If complex name addressing is not configured, Memo
    only allows the format DGN.DEN in addresses. Can you send a message to a
    "normal" Memo user?
    
    Anders

I fall into category 1.  I'll get our Memo "expert" on-site to have a look. 
 Failing that I'll contact Verimation.



Ian.

The answer from our expert and Vermiation is that it can't be done.  PUDLs 
can't be used by people outside the Memo system.  "Normal" messages can 
only contain up to 72 addressees as their internal file header is of a 
fixed size!

How do Verimation expect big, or even medium companies to use this product?

Can anyone think of any other work arounds?  I *need* a subscribers list 
which contains 400+ Memo users, 170 Teamlinks users and 30 SNADS users.  I 
know I could split this into about 20 lists of 72 people but it's hardly 
acceptable to ask users to send their message 20 times!

I am running MR Memo V2.1-VW which I believe was developed for VW in 
Germany.  They use ALL-IN-1 and Memo systems.  They *must* have run into 
the same problem and found a good work around.  Do you still have any 
contacts with VW (either Digial or VAG) that I could try contacting?

Thanks for you help and I realise that this isn't really your problem.  
However, any advice would be very much appreciated.



Ian.

    
> I am running MR Memo V2.1-VW which I believe was developed for VW in 
> Germany.  They use ALL-IN-1 and Memo systems.  They *must* have run into 
> the same problem and found a good work around.  Do you still have any 
> contacts with VW (either Digial or VAG) that I could try contacting?

    Try HEINZ FISCHER@HAO DTN 863-5197
    
    Don't be too optimistic though.
    
    	cheers,
    
    		Stefan