Hello August!

On 25.03.19 at 19:32, August Abolins wrote to Martin Foster:

 AA> On 25.03.19, you wrote to August Abolins:

 MF>> Found another one .....

 MF>> - 5D addresses MUST be used, otherwise, WinPoint transmits invalid
 MF>> AKAs to the remote system and the result of that is that the remote
 MF>> system will boot you off.

 AA> Well... it *is* a point program, so.. to me that implies that it
 AA> *expects* to operate as a 5D machine, and communicate with a Boss(es)
 AA> only.   Every message it creates internally will be 5D.

Even though WinPoint's mailer transmits 5D AKA's to the remote system,  
WinPoint's mail processor inserts 4D addresses in the MSGID's.

 AA> ..and therefore, every Uplink and/or System has to be a 4D Boss(?)

Ummmmm? :-)

 AA> However, as I write this, there *is* a Crashmail option at the top of
 AA> this internal editor window.  So, could that imply that it can call/poll
 AA> *any* other open (no session password) system that would accept
 AA> Crashmail?

Yes it does(and can - see the Guide)but it doesn't alter the fact that  
WinPoint's mailer transmits 5D addresses to the remote system.

 AA> If so, then maybe it can do what you would think, but for
 AA> some reason, the config is wrong somewhere?

The problem here is that the "@" preceeding the domain is hard-coded.  
If the user doesn't specify a domain, WinPoint's mailer will transmit  
"<zone>:<net>/<node>.<point>@", which is an invalid address.

After further testing, I've discovered that it depends on which mailer  
the remote system is using. I can reproduce this problem on two  
systems, both of which are using binkD. I've tried it on a third  
system, which is using mbcico(MBSE) and I had no problems with the  
session.

Regards,
Martin

--- OpenXP 5.0.36
 * Origin: Bitz-Box - Bradford - UK (2:310/31.3)