MSGID: 2:250/1.1 516e9d05
CHRS: IBMPC 2
TZUTC: 0000
REPLY: 2:221/1.58 50b75989
Hello August!
On 26.03.19 at 11:10:56, August Abolins wrote to Martin Foster:
AA> On 26.03.19, you wrote to August Abolins:
AA>>> ..and therefore, every Uplink and/or System has to be a 4D Boss(?)
MF>> Ummmmm? :-)
AA> Nevermind. Apparently I don't know what I was talking about! :(
:-)
MF>> The problem here is that the "@" preceeding the domain is hard-coded. If
MF>> the user doesn't specify a domain, WinPoint's mailer will transmit
MF>> ":/.@", which is an invalid address.
AA> Hmmm.. Methinks that 5D is a good thing. Isn't 5D supposed to be an
AA> improvement?
Hmmmmm, not sure how to answer that :-))
AA> The Extra/Options/Uplinks:FidostyleUplinks seems to be the item intended
AA> for the part after the @. Maybe it is also a way to differentiate from
AA> othernets?
Yes, that's its exact purpose and maybe this is one of the reasons why WinPoint
can't handle my hybrid setup?
MF>> After further testing, I've discovered that it depends on which mailer
MF>> the remote system is using. I can reproduce this problem on two systems,
MF>> both of which are using binkD. I've tried it on a third system, which is
MF>> using mbcico(MBSE) and I had no problems with the session.
AA> Sounds like WinPoint needs a compatibility list, or a warning that it is
AA> a truly 5D system.
I'm not so sure about a compatibility list but I'd already planned on adding a
warning about this somewhere in my revised Guide that I'm working on.
Regards,
Martin
--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:250/1.1)
SEEN-BY: 15/2 57/0 123/1970 153/250 154/10 203/0 221/0 226/17 229/107
SEEN-BY: 229/354 426 1014 240/5832 249/206 317 400 267/800 280/464
SEEN-BY: 280/5003 292/624 854 310/31 317/2 3 322/757 342/200 393/68
SEEN-BY: 396/45 423/120 712/848 770/0 1 10 100 330 340 772/0 1 500
SEEN-BY: 2452/250
PATH: 250/1 261/38 3634/12 153/757 250 770/1 280/464 229/426
|
