Wow!
You must not know much about networking or programming if you do not know how to ask the OS to tell you the address/port associated with the "other end" of a TCP connection. Obviously you know who is sending the message since they are in bidirectional communication with you at the time you are receiving the message, and you need to know where to send the "carry on James" prompts to get them to send more data... Therefore you always know who submitted a message. -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: Michael Thomas [mailto:m...@fresheez.com] On Behalf Of Michael >Thomas >Sent: Monday, 8 July, 2019 18:58 >To: Keith Medcalf; nanog@nanog.org >Subject: Re: SHAKEN/STIR Robocall Summit - July 11 2019 at FCC > > >On 7/8/19 5:54 PM, Keith Medcalf wrote: >> On Monday, 8 July, 2019 18:08, Michael Thomas <m...@mtcc.com> >wrote: >> >>> when we did DKIM back in the day, almost nobody was requiring SMTP >>> auth which meant the providers could say "blame me" via the DKIM >>> signature, >but couldn't really take much action since they didn't >>> know who has doing it. >> This is because DKIM was a solution to a problem that did not >exist. You always know the identity of the MTA sending you a >message, there never was a need for DKIM. It was a solution to a >problem that does not and did not nor will ever exist. >> >> >::eyeroll:: pray tell, how do you "always" know the identity of the >MTA >sending you a message? > > >Mike
