Tom Allison <[EMAIL PROTECTED]> writes: > The RFC2822 specifies that every header should be in the format of > > tag: string > tag: string > > The problem that found in the original email is that the header was > not seperated by '\n\n', causing his email to fail. > > The problem isn't the Python email, it's the content of the original > email. By all rights, it could be rejected on the grounds that it > isn't compliant with RFC2822 or RFC822. > > To make allowances to accept this as valid email is to accept damaged > goods.
In an ideal world, I'd agree with you, and just punt and say it's up to the SMTP server to reject such non-compliant messages before TMDA even seems them. Certainly, you are encouraged to do this if you are able to. Unfortunately, there are a couple problems with requiring this. First, it's not clear how difficult this is to accomplish (particularly with no-frills MTAs like qmail). More importantly, not all TMDA users have control over their MTA's configuration (for example, when running from an account at their ISP or university). Since TMDA is a user-level app, it must attack the problem at this level, and make some kind of allowance for these situations. I hope to have a resolution to the problem soon. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
