Udo Rader wrote: > I've installed a pretty strict antispam ruleset for our exim4 MTA which > among other things expects real RFC822 compliance. > > The mails from bugzilla at qa.mandrakesoft.com fail here: > > -----CUT----- > 2003-08-03 13:54:14 19jHRG-00053j-II H=office.mandrakesoft.com > (qa.mandrakesoft.com) [195.68.114.34] F=<[EMAIL PROTECTED]> rejected > after DATA: missing or malformed local part (expected word or "<"): > failing address in "From" header is: [some.body] > <[EMAIL PROTECTED]> > -----CUT----- > > Easy to woraround on my side, but it might be a good idea to make the > mails RFC822 compatible.
This is a late reply, but then it seemed important to you. The field that Bugzilla sends is valid according to the RFC. The bracketed name has been surrounded by quotes, which marks it as a "quoted-string" syntax rule. This datatype can contain 'any CHAR excepting <">, "\" & CR, and including linear-white-space' (quoting the RFC). Ergo, brackets are valid within this context. You may need to check your ruleset for compliance. Hope this helps. - John
