> Michael Holzt wrote:
> >>>Server SMTP systems SHOULD NOT reject messages based on perceived
> That's SHOULD NOT and not MUST NOT.
You should check RFC2119 what the phrase "SHOULD NOT" means exactly
in an internet standard:
| 4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that
| there may exist valid reasons in particular circumstances when the
| particular behavior is acceptable or even useful, but the full
| implications should be understood and the case carefully weighed
| before implementing any behavior described with this label.
It is general consensus that "SHOULD NOT" has to be interpreted as "You
must be nuts to do that, think not only twice but at least ten times
about it, and be sure that you know all bad outcomes out of this. Please
do not do it."
As there is no valid technical reason for rejecting such messages, we
should not implement such a blocking in the core code. Add it as an
optional plugin and leave it to the user to implement it, or not. We
can not "carefully weight the case" for the users implementing qpsmtpd.
> How about this: in the core, we block zero size messages and in a plugin
> block messages without DATE and FROM/SENDER?
Sorry: -1 for the core part. +1 for the plugin idea.
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
