> From: Keith Moore <[EMAIL PROTECTED]> > ... > (email errors are usually detected by the sender of a message, since > that's who gets the bounced message. but the party who has responsibility > for fixing the error is usually not on the sender's end of things) > ... It may be irrelevant, and my personal sample size is trivially tiny. ... In recent months very little email I've sent was bounced due to DNS errors and only a little more has been delayed. My logs say the delivery of much more from others to me was delayed or failed because the sender's domain did not resolve for hours or ever. (familiar anti-spam hack, with my guesses used to distinguish spam from legitimate mail suffering from bad sender DNS) Vernon Schryver [EMAIL PROTECTED]
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Tim Salo
- Re: draft-ietf-nat-protocol-complications-02.txt Jon Crowcroft
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt Steven M. Bellovin
- Re: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- RE: draft-ietf-nat-protocol-complications-02.txt BookIII, Robert
- RE: draft-ietf-nat-protocol-complications-02.txt Vernon Schryver
- Re: draft-ietf-nat-protocol-complications-02.txt J. Noel Chiappa
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke
- RE: draft-ietf-nat-protocol-complications-02.txt Bob Braden