Conference iosg::all-in-1_v30

3256.0. "Time Offset problems between DMW's and ALL-IN-1 IOS" by BUSHIE::SETHI () Fri Sep 10 1993 02:42

    Hi All,
    
    I have benn discusiing the issues of Time offset's in the DEC MAILworks
    conference ABBOT::MAILWORKS-VMS, see topic titled "Time Offset problems
    between DMW's and ALL-IN-1 IOS", note 92.
    
    I am cross-posting the .0 note in this note and you will find it below. 
    We have tried all the combinations to get the time offset correct and
    have had limited success.  In the enclosed note you will see the
    combinations we tried we missed one and that was:
    
            MR       -1000
            X4MAN    +1000
            ALL-IN-1 -1000
    
    Diane was in the DMW's conference spotted that combination and still no
    luck.  It looks like we have a problem with the Delivery Notification
    reports.
    
    Any comments pointers would be great.
    
    Regards,
    
    Sunil
    
    Note 92.0      Time Offset problems between DMW's and ALL-IN-1 IOS 
    
    Hi All,
    
    A customer has version 1.2 of DMW's installed, TeamLinks Mail for
    MS-Windows and Message Router 3.2.  The problem we are having is
    with the Time Off-set.  The nature of the problem is as follows:
    
    1. Sending mail from ALL-IN-1 IOS 3.0-1 to DMW's
    2. Message Router has the time set to GMT
    3. When the a show header is done there is a difference in date
       posted and delivered by 10 hours
    4. The time off-set is changed to +10 (Australia is 10 hours ahead
       on the East Coast compared to GMT).
    5. This solves to some extent the difference in date posted and
       delivered however the Non-delivery notification is now 10 hours
       out (-10 hours)
    
    The customer has sent me the results of trying to get the Time
    Offset right, please find enclosed the results below:
    
    Test results of changing MAILworks and Message Router offset times in an 
    effort to have correct posted/delivered times in MAILworks headers.
    Basically, I changed the offset as times as follows with the
    results listed in the table below. The changes to Message
    Router and MAILworks are listed in + or - hours,
    
    Posted/delivered yes/no would indicate whether or not the times in the 
    message header have the same or similar times (ie, not 10 hours different),
    and whether or not Postmaster delivery failure notice was the correct time
    or not.
    
                                         Mailworks    ALL-IN-1
                  Message   Mailworks    Posted/      Postmaster
                  Router                 Delivered    Delivery Notice
    
                  -10:00     10:00       No           No
                  -10:00    +10:00       Yes          No
                   00:00    +10:00       Yes          No
                  +10:00    +10:00       Yes          No
                  -10:00     00:00       No           Yes
                   00:00     00:00       No           Yes
    
    The above tests were done prior to installing DEC MAILworks V1.2. The 
    following tests were done with V1.2 installed.
    
                  Message    Mailworks   ALL-IN-1   Mailworks    ALL-IN-1
                  Router                            Posted/      Postmaster
                                                    Delivered    Del Notice.
    
                  -10:00     -10:00      -10:00     No           No
                  -10:00      00:00       00:00     No           Yes
                  -10:00     +10:00       00:00     Yes          No
                  -10:00     +10:00      +10:00     Yes          NO
    
    All tests were done by sending an EM to an ALL-IN-1 account, a normal 
    MAILworks account, and a non-existant MAILworks account.
    
    The result we are looking is correct times with both
    MAILworks posted/delivered and ALL-IN-1 Postmaster Delivery
    failure notice having a result of YES.

Hi Sunil,

I think the MAIlworks conference narrowed this one down to: set both IOS and 
X4MAN to +10, and set MR to -10. Then the only failure is in the ALL-IN-1 
non-delivery report - yes?

I suspect this is caused because the report is generated in code and it 
will just pull in the current local time into the text of the message. As you 
know, non-deliveries are just ordinary messages. Perhaps you could customise 
the report to add in the timezone identifier e.g. BST? (I have a vague memory 
that the report text is taken from the message file - probably not any more!)

This problem should be solved when ALL-IN-1 generates proper delivery reports 
- then the text of the report will be generated on the receiving system, and 
will be able to apply the same logic as that used for the other times on the 
messages.

grahame

    Hi Grahame,
    
    Thanks for your input I guess it's more of a case of making people
    aware of the potential problem.  The customer didn't seem too happy
    about it all but I guess they will have to accept it for the time
    being.
    
    Regards,
    
    Sunil