Simple Mail Transfer Protocol
Mail per Telnet schreiben
Man benötigt nicht unbedingt ein Mail-Programm, um eine Mail bei einem SMTP-Server abzuliefern. Das Mailprogramm ist in der Regel einfach bequemer ;-). Man kann seine Mail auch per Telnet an den zuständigen Mailserver schicken:
$ telnet mail.example.com 25 EHLO fqdn.example.com MAIL FROM: <john@example.com> RCPT TO: <doe@example.com> DATA From: <john@example.com> To: <doe@example.com> Subject: Beispiel Test . QUIT
Delivery Status Notification (DSN)
Ausführliche Informationen gibt es in RFC 3463, aus dem diese Informationen entnommen sind. Dies hier soll nur eine kleine Übersicht sein - keine HTML-Version des RFC.
Status Code Structure
status-code = class "." subject "." detail class = "2"/"4"/"5" subject = 1*3digit detail = 1*3digit
Class
- 2.x.x - Success
- Success specifies that the DSN is reporting a positive delivery action. Detail sub-codes may provide notification of transformations required for delivery.
- 4.x.x - Persistent Transient Failure
- A persistent transient failure is one in which the message as sent is valid, but persistence of some temporary condition has caused abandonment or delay of attempts to send the message. If this code accompanies a delivery failure report, sending in the future may be successful.
- 5.x.x - Permanent Failure
- A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery.
Collected Status Codes
Other or Undefined Status
- x.0.0 Other undefined Status
Address Status
- x.1.0 Other address status
- x.1.1 Bad destination mailbox address
- x.1.2 Bad destination system address
- x.1.3 Bad destination mailbox address syntax
- x.1.4 Destination mailbox address ambiguous
- x.1.5 Destination mailbox address valid
- x.1.6 Mailbox has moved
- x.1.7 Bad sender's mailbox address syntax
- x.1.8 Bad sender's system address
Mailbox Status
- x.2.0 Other or undefined mailbox status
- x.2.1 Mailbox disabled, not accepting messages
- x.2.2 Mailbox full
- x.2.3 Message length exceeds administrative limit.
- x.2.4 Mailing list expansion problem
Mail system status
- x.3.0 Other or undefined mail system status
- x.3.1 Mail system full
- x.3.2 System not accepting network messages
- x.3.3 System not capable of selected features
- x.3.4 Message too big for system
Network and Routing Status
- x.4.0 Other or undefined network or routing status
- x.4.1 No answer from host
- x.4.2 Bad connection
- x.4.3 Routing server failure
- x.4.4 Unable to route
- x.4.5 Network congestion
- x.4.6 Routing loop detected
- x.4.7 Delivery time expired
Mail Delivery Protocol Status
- x.5.0 Other or undefined protocol status
- x.5.1 Invalid command
- x.5.2 Syntax error
- x.5.3 Too many recipients
- x.5.4 Invalid command arguments
- x.5.5 Wrong protocol version
Message Content or Message Media Status
- x.6.0 Other or undefined media error
- x.6.1 Media not supported
- x.6.2 Conversion required and prohibited
- x.6.3 Conversion required but not supported
- x.6.4 Conversion with loss performed
- x.6.5 Conversion failed
Security or Policy Status
- x.7.0 Other or undefined security status
- x.7.1 Delivery not authorized, message refused
- x.7.2 Mailing list expansion prohibited
- x.7.3 Security conversion required but not possible
- x.7.4 Security features not supported
- x.7.5 Cryptographic failure
- x.7.6 Cryptographic algorithm not supported
- x.7.7 Message integrity failure