On Sat, 04 Oct 2014, Alexey Vissarionov wrote to mark lewis:
ml> this positional distinction seems to be missed by many and the INA ml> flag is wasted as it doesn't get followed by other flags indicating ml> the capabilities available for the connection it is representing... ml> if the above example does not contain an IP or FQDN in a recognized ml> position before the IBN, then connecting systems will likely be ml> attempting the f.n.z conversion and lookup to find the proper IP or ml> FQDN to connect to for the IBN connection...
AV> The positional distinction means your own mental disability.
this is not an appropraite comment, alexey...
AV> Other people, including most developers, have enough mental AV> abilities to parse the line regardless of flag order.
and they fail to properly parse multiflagged entries...
in the above: 1. the first ITN,IVM apply to the f.n.z.domain.tld converted connection address because there is no FQDN or IP number listed.
2. the first IBN applies only to site1.tld. there is no ITN or IVM there and the f.n.z.domain.tld doesn't handle it at all.
3. the second ITN applies only to site2.tld. there is no IBN or IVM there.
4. the fourth site, site3.tld, handles all three connection types.
intelligent mailers and nodelist using software would have no problem with this... it should also allow for the Xx flags to be listed with each as well as pretty much all other flags... i can easily see the Txy flags being listed with INA flags indicating that sitex.tld is operational at certain times...
the sad thing is that the intelligence that mailer software used to have has been lost...
)\/(ark
If you think it's expensive to hire a professional to do the job, wait until you hire an amateur.
