Re: C'est pas si simple l'email.

que le mail a été accepté par le serveur. Libre ensuite à lui d'en faire ce qu'il veut.

Il y a un protocole, et des codes retours. Si on peut dialoguer sur internet, c'est justement parce que les serveurs ne font pas ce qu'ils veulent mais respectent les protocoles. On a tendance à râler ici lorsqu'un site affiche ie6 only, ou utilise des hack immondes et ne passe que sous certains navigateur, c'est a peut près le même genre de problème.

Lorsqu'il ne veut pas s'occuper d'un courrier suspect, il peut très bien dire j'en veut pas. Là il faut oui oui, ok, pas de problème avant de le jeter.

Tiens cadeau la RFC

4.2.1. Reply Code Severities and Theory
 The three digits of the reply each have a special significance. The
 first digit denotes whether the response is good, bad, or incomplete.
 An unsophisticated SMTP client, or one that receives an unexpected
 code, will be able to determine its next action (proceed as planned,
 redo, retrench, etc.) by examining this first digit. An SMTP client
 that wants to know approximately what kind of error occurred (e.g.,
 mail system error, command syntax error) may examine the second
 digit. The third digit and any supplemental information that may be
 present is reserved for the finest gradation of information.
 There are four values for the first digit of the reply code:
 2yz Positive Completion reply
 The requested action has been successfully completed. A new
 request may be initiated.
 3yz Positive Intermediate reply
 The command has been accepted, but the requested action is being
 held in abeyance, pending receipt of further information. The
 SMTP client should send another command specifying this
 information. This reply is used in command sequence groups (i.e.,
 in DATA).
 4yz Transient Negative Completion reply
 The command was not accepted, and the requested action did not
 occur. However, the error condition is temporary, and the action
 may be requested again. The sender should return to the beginning
 of the command sequence (if any). It is difficult to assign a
 meaning to "transient" when two different sites (receiver- and
 sender-SMTP agents) must agree on the interpretation. Each reply
 in this category might have a different time value, but the SMTP
 client SHOULD try again. A rule of thumb to determine whether a
 reply fits into the 4yz or the 5yz category (see below) is that
 replies are 4yz if they can be successful if repeated without any
 change in command form or in properties of the sender or receiver
 (that is, the command is repeated identically and the receiver
 does not put up a new implementation).
 5yz Permanent Negative Completion reply
 The command was not accepted and the requested action did not
 occur. The SMTP client SHOULD NOT repeat the exact request (in
 the same sequence). Even some "permanent" error conditions can be
 corrected, so the human user may want to direct the SMTP client to
 reinitiate the command sequence by direct action at some point in
 the future (e.g., after the spelling has been changed, or the user
 has altered the account status).

Lorsqu'il répond 2, il indique clairement que c'est fait, et requested action c'est pas 'fout le dans /dev/null'

Il ne faut pas décorner les boeufs avant d'avoir semé le vent