Fred Lindberg writes:
> For a mailing list, I get errors like (the xxx are ascii chars replaced by me):
>
> 1 1.38 207.244.124.137 failed after I sent the message./Remote host said:
>550 Syntax error in 'Cc' header: malformed address: "xxx Mack"
> <[EMAIL PROTECTED]>/
> 1 1.53 212.208.194.252 failed after I sent the message./Remote host said:
>550 Syntax error in 'Cc' header: malformed address: "xxx Mack"
> <[EMAIL PROTECTED]>/
>
> It seems that hosts (mainly running EXIM) are parsing messages and rejecting non
>rfc822-compliant messages. Other message have been rejected because of
> an incorrectly formatted From: header, others because they contain chars > 127 (e.g.
>iso-8859-1 umlauts).
>
> To me this seems brain-dead, but maybe that's a lack of understanding on my part.
>Are there any redeeming features to this type of activity?
Yes. Spam filtering. I think that this is an excellent idea, and I have
implemented it myself, although my RFC822 checking is probably not as
strict as this particular instance.
--
Sam
