[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 | 
3196.0. "Return address invalid, A1 is missing (MAIL)" by EVOAI2::DAN_M (Maya DAN) Thu Aug 26 1993 10:06
Thank you to help to answer to the following question from a partner via Digital 
Partner Network (Node CSONET::)
best regards
Maya
                   <<< DUA1:[NOTES$LIBRARY]AI1_TECH.NOTE;1 >>>
                       -< ALL-IN-1 CSO Technical Forum >-
================================================================================
Note 109.0       Return address invalid , A1 is missing  (MAIL)       No replies
ISVNET::JFMEZEI "Jean-Francois Mezei (JF)"           39 lines  24-AUG-1993 22:46
--------------------------------------------------------------------------------
    This is either a bug, or my system's config seems to have gone awyre
    :-)
    
    On ALL-IN-1 3.0 (no patches):
    
    On Message Router 3.2S-220:
    
    
    Create message from JFMEZEI in ALL-IN-1, 
    	TO: JFMEZEI@A1@MYNODE
    
    This message should loop back, and it does.
    
    However, the broadcast ALL-IN-1 sends to my terminal is 
    "New ALL-IN-1 mail from JFMEZEI@A1"
    
    When I read the message, the author is:
    	Jean-Fran�ois Mezei   (JFMEZEI@MYNODE)
    
    when it should really be (JFMEZEI@A1@MYNODE)
    
    If I send the same message with a CC to my VMSMAIL (through MRGATE),
    the sender's address is correct (MYNODE::MRGATE::"A1::JFMEZEI")
    
    Of course, when the reply address is "USERNAME@NODE" instead of 
    "USERNAME@A1@NODE", it makes it impossible to reply to the message
    since Message Router will generate a non delivery notification from
    attempting to deliver to the "USERNAME" user agent.
    
    (unless, of course, all your usernames are defined in MRMAN with
    /REPLACES, something the manual suggests we do NOT do, but something
    which a certain large computer firm does a LOT :-)
    
    Question:
    		Is this a known problem that the A1 gets dropped from 
    			the return address , or could it be the way
    			that system is configured ? I never noticed that
    			before and wonder if something happened when
    			the system rebooted.
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 3196.1 | check the area logical | FORTY2::ASH | Mail Interchange Group, Reading | Thu Aug 26 1993 13:26 | 6 | 
|  | The address is usually formed from the logical name OA$MTI_AREA. This should 
be set to "A1@MYNODE[@AREA]". It looks as if it may be missing the A1.
Another possibility is DDS$AREA (or similar).
g
 | 
| 3196.2 | refreshing GASH's memory | AIMTEC::WICKS_A | U.S.A 2 England 0 - I was there! | Mon Aug 30 1993 05:57 | 8 | 
|  |     Maya,
    
    Grahame means of course the symbol OA$DDS_AREA_ROUTE though I don't
    remember it doing this before.
    
    Regards,
    
    Andrew.D.Wicks
 | 
| 3196.3 | FYI - always from PARTNERnet | EVOAI2::DAN_M | Maya DAN | Thu Sep 16 1993 13:12 | 38 | 
|  | 
                   <<< DUA1:[NOTES$LIBRARY]AI1_TECH.NOTE;1 >>>
                       -< ALL-IN-1 CSO Technical Forum >-
================================================================================
Note 109.4       Return address invalid , A1 is missing  (MAIL)           4 of 4
ISVNET::JFMEZEI "Jean-Francois Mezei (JF)"           22 lines   1-SEP-1993 19:18
                      -< I think it is solved (for now) >-
--------------------------------------------------------------------------------
    I hate it what that happens !!!!!
    
    We had a thunderstorm yesterday.
    
    Remember my problem of adressing myself@a1@mynode and the message
    coming back with a sender of myself@mynode ?
    
    Well, it is gone now....
    
    I had tried many things but to no avail. The one thing that I did
    change was to add an MHS User identifier to the DDS UA record for
    OA$mynode$ALLIN1
    
    Initially, it didn't change anything. But I guess that when the vax was
    rebooted, the DDS change really went into effect and it seems to work
    now.
    
    When I installed A1 from scratch (3.0), the DDS entry for teh ALLIN1 UA
    was not created and I had to create it manually. Doing a trace in
    OAMTIMAIL.COM (SET_TRACE), I realised that the dataset UAPASSWRD is
    supposed to keep track of that stuff. I'll have to check up on the
    documentation to see exactly which portion of A1 handles this.
 |