Subj : this results in "z:n/n.p@ " - this is not OK
To   : August Abolins
From : mark lewis
Date : Sun Mar 31 2019 13:35:54

 On 2019 Mar 30 22:40:50, you wrote to me:

 ML>> it is also a design flaw... it should raise a huge red error
 ML>> indication when there is no domain listed OR (keep reading)...

 AA> Sadly, that is indeed what was overlooked.

yup...

 ML>> it should NOT put the @ unless there is a domain specified... so still
 ML>> a design  flaw nonetheless...

 AA> Martin discovered that the @ is hardcoded, and does not clear out when the
 AA> domain field is empty.

right, that's the flaw...

 AA> So, any gibberish in the domain field will suffice to prevent a
 AA> session from failing on strict systems looking for something in the
 AA> @domain part.

it could also prevent positive connections since the domain would be wrong...
1:2/3@fidonet is not the same as 1:2/3@fubarnet ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
.... What we need is a Pizza Door and a Beer Door
---
 * Origin:  (1:3634/12.73)

.