On 30.08.2007, at 02:31, David Woodhouse wrote:
> On Wed, 2007-08-29 at 12:08 +0100, David Woodhouse wrote:
>> On Tue, 2007-08-28 at 22:45 +0200, Wolfgang Hennerbichler wrote:
>>>
>>> helo mail.domain.name
>>> MAIL FROM:<"NokiaNiedersch\366neweidewlole"@???>
>>>
>>> The local part of the sender address is obviously "broken",
>>
>> That isn't obvious to me.
>
> Actually, I think you're right, although perhaps not for the
> reasons you
> originally thought.
:)
> So since your example actually seems to have contained the byte 0xF6
> (the \366 is presumably a representation of that, rather than being a
> literal '\' '3' '6' '6', you probably _can_ declare that it's
> obviously
> broken on syntactic grounds.
It really was a umlaut, I just switched to an UTF8-enabled terminal,
and voila:
35h 22K 1IQ5fZ-00085v-Km <> *** frozen ***
"Büchlerqgytc"@???
34h 18K 1IQ6tP-0001X6-WF <> *** frozen ***
"NokiaNiederschöneweidewlole"@???
15h 18K 1IQOqb-0004Rv-98 <> *** frozen ***
"PlenkPlänterwaldmety"@???
> I'm surprised Exim's SMTP syntax checks
> didn't catch that -- unless it really was a backslash and three
> digits?
Those messages are frozen because they have been bounced from the
remote MTA. I'll try to figure out a way to block these sender
adresses. Thanks for your help digging into the RFC's (I should
actually have done that before asking).
> --
> dwmw2
wogri
--
wogri@???
http://www.wogri.com
http://www.einradfilm.at
