[Last-Call] Re: [Emailcore] Re: Re: SMTP threat models, SECDIR Review of draft-ietf-emailcore-rfc5321bis-31

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 3 Nov 2024, Paul Wouters wrote:

On Nov 3, 2024, at 09:54, John R. Levine <johnl@xxxxxxxx> wrote:

Skipping over the question of whether anyone actually uses TURN or ETRN,

For the record, i manaually do use telnet to port with ETRN when my home has been offline and I brought it back and I want to tickle my MX to deliver its stash over to my home SMTP server 😀

Could I use “ssh root@mx sendmail -q”, if this got removed. Yes I could)[*]

My point was that SMTP is sender-push, and TURN or ETRN only speed up the pushing. They don't request specific data like http does.

In any event, TURN is only mentioned in an appendix about deprecated features, and ETRN, since it is an optional extension defined in RFC 1985, is only mentioned in passing where it notes that if you get mail from a host, you can treat that like an implict ETRN and send mail queued in the other direction. I don't see any reason to change either of those.

R's,
John

--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux