-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
On Mon, 2 May 2005, wayne wrote:
1) Treat PermError as "None"
No
Agreed.
2) Treat PermError as "Fail"
No
Agreed.
3) RECOMMEND PermError be rejected via SMTP 5xx responses
Good.
Significantly better than 2), my preferred option.
4) RECOMMEND PermError be temporarily rejected via SMTP 4xx responses
Not as good.
Forbidden by the existing e-mail RFC's IIRC.
Transmission errors that require intervention to clear are
supposed to be flagged by 5xx codes, 4xx codes are reserved
for failures (overloaded server and such) that can clear themselves.
5) On PermError, MAY accept message but send DSN describing error.
If DSN is not accepted, then REJECT as in 3.
Acceptable, and in the spirit of being strict with what is sent, but
relaxed on what is accepted. I wouldn't complain if this were
the consensus position.
- --
Daniel Taylor VP Operations Vocal Laboratories, Inc.
dtaylor(_at_)vocalabs(_dot_)com http://www.vocalabs.com/
(952)941-6580x203
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCd20Q8/QSptFdBtURAlinAJ9WZqBuH8fBaBkYb3c9W5eyD3IHdwCdELJ3
6C8FVq/IRBtNXfgRGgbCkws=
=NdWP
-----END PGP SIGNATURE-----