Norman Maurer wrote:
Søren Hilmer schrieb:
+1 (but with a shorter note where it applies as suggested by Stefano)
So any suggestion about how the "shorter version" should be lookin ?
Guillermo suggested this:
<!-- WARNING: This is Non-RFC compliant (default value: false) -->
<!-- see also: http://james.apache.org/code-standards.html -->
Here is the original content
---
Certain features allow Apache James to handle mail which has been
constructed or sent in a manner not in compliance with the standards
which James implements.
The feature documented here permits James to handle messages which do
not comply with the following standards which James claims to implement:
RFC XXXX para Y.Y
This feature has been disabled by default because James developers
intend that James itself fully complies with the relevant published
standards in the form in which it is distributed.
The James project's policy is to encourage the developers of other email
software to comply with published standards. It is only by all parties
conforming to published standards that interoperability can be
guaranteed, this is a fundamental charateristic of the internet.
You are free to enable this feature which has been developed for your
benefit as carefully as any of James' other features.
-----
I think it is important to give a reference to the RFC(s) and the
paragraph(s) related to the optional preference, so user could
investigate more on this but we can't reproduce 20 lines of comment for
every of this preference or our config.xml will become totally useless soon.
So I would give freedom to use the preferred formula based on the
specific context, but I would *require* at least a "WARNING" and a
reference to the Non-compliance and the link to the code-standard page.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
