--------
Hi Paul,

>> suggestions?
>
>Yes, I have one because I don't know where it could be discussed

  Good - I think.

>
>What is to be done (as a whole community) with terribly not conformant
>  software that want to connect to GO-MHS? Or more precisely, would it be
>  possible to have a common attitude with sites/domains using that type
>  of software and really *endangering* the whole GO-MHS?
>
>It concernrs PRMDs (eg. using today MS-MAIL gateways) but also some ADMDs :-(
>
>As we have no direct control on what people buy and use, it is not an easy
>matter. What I suggest is to maintain and publish very widely a
>blacklist of products/providers which will give the name and version
>of the culprits along with a description of the problems.
>  - this would allow customers to check this list prior to buying choices?
>  - this would put a high pressure over the suppliers to fix the
>	problems as soon as possible.
>being unable to solve this type of problem is in my mind a serious X.400
>killer!
>

  Well this is a touchy subject. But how do you approach it with out
getting into any legal problems - my US legal paranoia showing.  I beleave
the GO-MHS coordination service is trying to avoid this problem by
testing new connection requests before they connect. But if the service
moves to a non-coordinated service (i.e. X.500, DNS) this would be 
harder to enforce. The Current SMTP world suffers from simular problems.
  
  At best we may be able to have a list of tested/recommended S/W. To
publish a negative list would invite problems. With ether list, who 
would publish it? And who would like to say they had tested and found the
software usable/unusable?  It would be nice if we did not go down the
the same path as SMTP but it is not clear how we can avoid it.

Tony...