ietf
[Top] [All Lists]

Re: SPAM: - Re: Last Call: <draft-ietf-uta-email-tls-certs-05.txt> (Updated TLS Server Identity Check Procedure for Email Related Protocols) to Proposed Standard

2015-11-21 18:24:54
Dear Samir, all,

Speaking as sergeant-at-arms.

I think this topic and the attachment is out of scope for the IETF exploder.

You’re also behaving with attacks to other participants, which can’t be 
tolerated.

Furthermore, I don’t think crossposting to this list for a technical discussion 
is appropriate.

So please don’t keep going on, read RFC3005, and avoid even responding to this 
email, so I don’t need to restrict your posting rights.

Regards,
Jordi









-----Mensaje original-----
De: ietf <ietf-bounces(_at_)ietf(_dot_)org> en nombre de Samir Srivastava 
<samirs(_dot_)lists(_at_)gmail(_dot_)com>
Responder a: <samirs(_dot_)lists(_at_)gmail(_dot_)com>
Fecha: sábado, 21 de noviembre de 2015, 15:12
Para: ComKal Networks <admin(_at_)comkal(_dot_)com(_dot_)au>
CC: IETF discussion list <ietf(_at_)ietf(_dot_)org>
Asunto: Re: SPAM: - Re: Last Call: <draft-ietf-uta-email-tls-certs-05.txt> 
(Updated TLS Server Identity Check Procedure for Email Related Protocols) to 
Proposed Standard

This is not an spam. I am forwading the attachment to you. In which
supreme court of US did not do anything

On Sat, Nov 21, 2015 at 9:05 AM, ComKal Networks 
<admin(_at_)comkal(_dot_)com(_dot_)au> wrote:
On Fri, 20 Nov 2015 18:26:57 -0500 Samir Srivastava wrote:

Sorry I donot have time to change the subject. Can Protocol become

Have the courtesy to at least place SPAM: at the start of
your subject line please.





<Prev in Thread] Current Thread [Next in Thread>