If you need to do manual debugging daily then you are not engaged in debugging, you have a protocol that depends on manual intervention.
That is an architectural defect.
I understand your pain, what I don't understand is why you tolerate it or my business model for mitigating your problem. I have no qualms about telling people that their 'requirement' to run infrastructure obsolete twenty years is not a requirement I recognize.
The bar for justifying MUST requirements should be very high. They certainly should not become a mechanism for people to defer the cost of upgrading their infrastructure onto the rest of us.
"Running a relay" is not a properly stated requirement. What is this relay for? If it is for gating X.400 or DECNET mail then my response would be more or less 'not only do I reject your requirement, I would if it were legal and expeditious to do so personally go to the system in question and reprogram it with a very large axe'. The privacy concerns for running different types of gateway/relay/mailing list are all very different. Simply stating they are essential does not persuade me.
Every time a message passes through a relay it is because either the sender has configured their mail to do that or the receiver has configured their mail to do use it. So the privacy concerns are very different for those hops to the concerns that arise when the sender hands a message over to the receiver.
The reason the privacy concerns come up is that the relay has no idea what role it is forwarding the message under, whether it is acting for the sender or the receiver.
On Sun, Mar 30, 2014 at 7:52 PM, Randy Bush <randy@xxxxxxx> wrote:
the day was weird enough already without my having to agree with an
entire, typically long, jck posting :)
the truth is, i have not used received: headers to authenticate/debug
[0] since yesterday. but it's not yet 09:00, so there is still time
today.
randy
---
[0] - from an ops pov, loop detection, lists subscribing to eachother,
and all that stuff is debugging.
Website: http://hallambaker.com/