RFC 2505:Anti-Spam Recommendations for SMTP MTAs
RFC-Ref

attack


Click on the red underlined text to get to the source

... might result in problems for the DNS server itself to cope with the load. This itself can result in a denial of service attack against the DNS server just by sending email ...
... DNS, forged DNS responses can be used to mount denial of service attacks. For example, if a site is known to implement a FQDN validity ...
... check on addresses in SMTP "MAIL From:" commands, an attacker may be able to use negative DNS responses to effectively block ...
... verifies that incoming responses correspond to outstanding queries, to minimize the risk for such attacks. ...


... It should be noted that by logging more events, especially denied email, one opens the possibility for denial of service attacks, for example by filling logs by having a very large amount of "RCPT To:" commands. An implementation that implements increased logging ...
... commands. An implementation that implements increased logging according to this description must be aware of the fact that the size of the logfiles increases, especially during attacks. ...
... the ability to block a certain user or a certain domain is quite helpful while an attack has just been discovered and is ongoing. ...
... If we are under a spam attack it may help us considerably just being able to slow down the incoming mail rate for that particular user/host ...
... MTA will re-run its mail queue, which may be quite costly and open for Denial of Service attacks. Therefore, the MTA SHOULD control who is is allowed to issue the ETRN ...


... methods described in this document will, because of that, increase the risk of a denial of service attack against the support system by sending spam to a site. Logging facilities must for example be able to handle ...



Google
Web
RFC-Ref