Dave, I am honestly trying to keep focus with addressing CVS to see how we
can make it work for our package. If it was something we can test today,
it would be done. Feedback is the only way I can see if I understand it
1) I don't see how TLS applies. I don't think it is even relevant. TLS
protects (addressed) secured transmission. I believe you documented TLS is
not useful or reliable. Here.
2) I do see a conflict with SASL (ESMTP AUTH). I think for maximum
compatibility CVS *may* best apply until SASL is known (established or not)
by the client.
3) How do I best merge or not, a bad reputation status against a CVS
Please confirm, correct me or fill me on the about.
#2 and #3 are related. Here's how:
I have 20,000 user accounts. To route mail, they have to use SASL.
We have not received any complaints of any of our users abusing others (and
expect it from the professional group), but if we did, what does that mean?
Can CVS help?
I add a CVS record and I registered with MAPS new CVS compliant
This will not stop the abuse of any specific individual user.
Am I to believe that I need to make sure all our users are CVS ready too?
Even so, it seems to me that I am still stuck of directly addressing user
abuse issues on a personal basis.
Also, another system may be using RBL and quite maybe CVS. They see we have
abusive users and even with our CVS certification, they decided to use RBL
to block us.
Or, is this now a administrative policy issue where a complaint is sent to
accreditation agent to get my status remove or suspended?
These are real possible issues and scenarios.
Hector Santos, Santronics Software, Inc.