Specifications

sigmadue - IEC 61131-3 Function Block Library
172
In addition to the above described errors, it is possible to get the ones complaining
the RFC5321 standard:
221 <domain> Service closing transmission channel
251 User not local; will forward to <forward-path>
252 Cannot VRFY user
421 <domain> Service not available, closing transmission channel (This may
be a reply to any command if the service knows it must shut down)
432 A password transition is needed
450 Requested mail action not taken: mailbox unavailable (e.g. mailbox busy or
temporarily blocked for policy reasons)
451 Requested action aborted: local error in processing
452 Requested action not taken: insufficient system storage
454 Temporary authentication failure
455 Server unable to accommodate parameters
500 Syntax error, command unrecognized (this may include errors such as
command line too long)
501 Syntax error in parameters or arguments
502 Command not implemented
503 Bad sequence of commands
504 Command parameter not implemented
530 Authentication required
534 Authentication mechanism is too weak. This response to the AUTH com-
mand indicates that the selected authentication mechanism is weaker than
server policy permits for that user
535 server rejects the authentication data
538 Encryption required for requested authentication mechanism
550 Requested action not taken: mailbox unavailable (e.g. mailbox not found,
no access, or command rejected for policy reasons)
551 User not local; please try <forward-path>
552 Requested mail action aborted: exceeded storage allocation
553 Requested action not taken: mailbox name not allowed (e.g. mailbox syn-
tax incorrect)
554 Transaction failed (Or, in the case of a connection-opening response, "No
SMTP service here")
555 MAIL FROM/RCPT TO parameters not recognized or not implemented
Note:In some situations, the e-mail message cannot be delivered to the receiver due to
destination server problems. Usually, at this point, the server sends a warining
message to advise of the problems. Because the Sigma CPU handles only
outgoing messages, it is impossible to know the result of the delivery.