• [^] # Re: C'est pas si simple l'email.

    Posté par . En réponse au journal Les emails par Neuf.... Évalué à 3. Dernière modification le 16 mai 2012 à 20:27.

    _Si le transfert est OK, il répond OK, point barre. Et avec un spam, ben c'est OK (le transfert).

    Vous voulez faire faire à SMTP autre chose que du transfert…_

    Nous on s'en fout, mais la RFC est assez claire :

    The relay server may accept or reject the task of relaying the mail in the same
     way it accepts or rejects mail for a local user. If it accepts the
     task, it then becomes an SMTP client, establishes a transmission
     channel to the next SMTP server specified in the DNS (according to
     the rules in section 5), and sends it the mail. If it declines to
     relay mail to a particular address for policy reasons, a 550 response
     SHOULD be returned.
     When the receiver-SMTP accepts a piece of mail (by sending a "250 OK"
     message in response to DATA), it is accepting responsibility for
     delivering or relaying the message. It must take this responsibility
     seriously. It MUST NOT lose the message for frivolous reasons, such
     as because the host later crashes or because of a predictable
     resource shortage.
     If there is a delivery failure after acceptance of a message, the
     receiver-SMTP MUST formulate and mail a notification message. This
     notification MUST be sent using a null ("<>") reverse path in the
     envelope. The recipient of this notification MUST be the address
     from the envelope return path (or the Return-Path: line). However,
     if this address is null ("<>"), the receiver-SMTP MUST NOT send a
     notification. Obviously, nothing in this section can or should
     prohibit local decisions (i.e., as part of the same system
     environment as the receiver-SMTP) to log or otherwise transmit
     information about null address events locally if that is desired. If
     the address is an explicit source route, it MUST be stripped down to
     its final hop.
    
    

    Donc le mail tu l'aimes ou tu l'aimes pas, mais si tu l'aimes pas tu DOIS faire beurk.

    De même si un relais et/ou un backup MX accepte le mail et n'arrive pas à le transmetre au bout de quelques jours, il DOIT avertir l'utilisateur qu'il laisse tomber si le reply to: existe.

    Donc bloquer le spam oui, mais pas n'importe comment.