2 réponses
Salut,
T'as un message d'erreur ?
tu fais quoi exactement ? tu ouvres une sessions dos et pis tu lances la commande et c'est là que ça plante ?
T'as un message d'erreur ?
tu fais quoi exactement ? tu ouvres une sessions dos et pis tu lances la commande et c'est là que ça plante ?
Salut,
Lorsque tu lances ta commande as tu le temps de lire le retour de la commande ou ça plante aussitôt ?
sinon je viens de me faire la RFC 2487, il y a un passage qui me fait penser à ton blème .
Processing After the STARTTLS Command
After the TLS handshake has been completed, both parties MUST
immediately decide whether or not to continue based on the
authentication and privacy achieved. The SMTP client and server may
decide to move ahead even if the TLS negotiation ended with no
authentication and/or no privacy because most SMTP services are
performed with no authentication and no privacy, but some SMTP
clients or servers may want to continue only if a particular level of
authentication and/or privacy was achieved.
If the SMTP client decides that the level of authentication or
privacy is not high enough for it to continue, it SHOULD issue an
SMTP QUIT command immediately after the TLS negotiation is complete. If the SMTP server decides that the level of authentication or
privacy is not high enough for it to continue, it SHOULD reply to
every SMTP command from the client (other than a QUIT command) with
the 554 reply code (with a possible text string such as "Command
refused due to lack of security").
Lorsque tu lances ta commande as tu le temps de lire le retour de la commande ou ça plante aussitôt ?
sinon je viens de me faire la RFC 2487, il y a un passage qui me fait penser à ton blème .
Processing After the STARTTLS Command
After the TLS handshake has been completed, both parties MUST
immediately decide whether or not to continue based on the
authentication and privacy achieved. The SMTP client and server may
decide to move ahead even if the TLS negotiation ended with no
authentication and/or no privacy because most SMTP services are
performed with no authentication and no privacy, but some SMTP
clients or servers may want to continue only if a particular level of
authentication and/or privacy was achieved.
If the SMTP client decides that the level of authentication or
privacy is not high enough for it to continue, it SHOULD issue an
SMTP QUIT command immediately after the TLS negotiation is complete. If the SMTP server decides that the level of authentication or
privacy is not high enough for it to continue, it SHOULD reply to
every SMTP command from the client (other than a QUIT command) with
the 554 reply code (with a possible text string such as "Command
refused due to lack of security").
voilà exatement ce ke je fè.
d'abor j'ouvre le dos
je tape telnet.
o smtp.gmail.com 25
é jè la reponse 220 du serveur
je lance EHLO gmail puis il me repond avec 250
et le lance STARTTLS. il repond mè ne me laisse pas assez de temp pour lancer le MAIL FROM.
je ne sais pas comment dépasser cette étape