Well, you'll keep your, I'll keep mine, I even thought I should go to jail. Joking ;)
Apart the fact that the 2 mtas I've mentioned serve more than 1/3 of the internet, where did you see that rfc 821 says "the destination should reject if not properly encoded"? If it's required it must be clearly stated. Read point 6.3 Compensating for Irregularities from rfc 2821 (821 is outdated), in particular: - Correction of addresses to proper FQDN format .... and if you are interested in some clamorous rfc violations read this: http://cr.yp.to/smtp/request.html At last, I agree that 451 might be changed, in this case to something else (5xx), but why not accept it, and correct it, if it can be done? Ciao Dario -----Messaggio originale----- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] conto di CLEMENT Francis Inviato: luned́ 29 novembre 2004 18.29 A: '[EMAIL PROTECTED]' Oggetto: [xmail] Re: smtp error I agree and don't agree ;-) I agree to 'unusual' situation for a telnet session : Explicitly saying 'syntax error' is effectivly not 'mandatory' but help troubleshooting I don't agree to "it doesn't say the destination should reject if not properly encoded" : Returning a 5xx error for this situation is 'recommanded' (if not = required ? .....), saying 'permanent error' not 'temporary error' (as with a 4xx = code)... And if rfc says 'mail' syntax IS (not should be) 'MAIL FROM : <emailaddress>' how incorrect syntax can be 'temporary' and/or accepted = ? Just another point of view ;-) Francis > -----Message d'origine----- > De : Dario [mailto:[EMAIL PROTECTED] > Envoy=E9 : lundi 29 novembre 2004 11:50 > =C0 : [EMAIL PROTECTED] > Objet : [xmail] R: Re: R: Re: smtp error >=20 >=20 > I think you are taking this <error> to seriously. > Remember that this is an "unusual" situation, > telnet is not a mua or an mta, so error codes > are only interpreted by your eyes, and not for > what they are there, the software. > Ok, in this case it could have a text a bit more > clear for you to read, but that's all. > On the other hand the rfc says that the sender > must properly encode the envelope <>, but it > doesn't say the destination should reject if > not properly encoded. It's just a point of > view, not a violation. >=20 >=20 - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
