3 Feb 2011 04:29
Re: Consensus Result on Issue #1 - Parameter on MAIL
Troy Starr <eai <at> troystarr.net>
2011-02-03 03:29:50 GMT
2011-02-03 03:29:50 GMT
Hi John - > If the envelope or message being sent requires the > capabilities of these EAI extensions, the client MUST > supply the UTF8SMTPbis parameter with the MAIL command. > > If the client is aware that the envelope or message > being sent does not require any of the EAI extension > capabilities, it SHOULD NOT supply the UTF8SMTPbis > parameter with the MAIL command. This specification > does not require that the client inspect the message or > otherwise go to extraordinary lengths to assure itself > whether these EAI capabilities are required for the > particular message. However, in mixed or transitional > environments in which EAI is not completely deployed, > more precision on the part of the client (sender) may > prevent unnecessary message rejections. I agree with the MUST in the first paragraph and the SHOULD NOT in the second paragraph. In the first sentence of the second paragraph, I don't think we want "or" since you would only omit the UTF8SMTPbis parameter if neither the envelope nor the message required EAI capabilities. So I would use a neither/nor combination, or just switch the "or" to "and" to make it clear that both conditions must be satisfied to omit the UTF8SMTPbis parameter. I'm a little iffy about "This specification does not require that the client inspect the message or otherwise go to extraordinary lengths to assure itself whether these EAI capabilities are required for the particular message." This sentence might suggest that I don't need to be sure that this is an EAI message, and therefore I don't need to add the UTF8SMTPbis parameter to the MAIL command. Even though we had the MUST in the first paragraph, I think this could create some ambiguity. I think we could make this clearer by stating that the client isn't required to verify that this isn't an EAI message. Something along the lines of: This specification does not require that the client inspect the message or otherwise go to extraordinary lengths to assure itself that EAI capabilities are not required for the particular message. - Troy Starr
RSS Feed