At 12:16 pm +0100 2004/05/20, Ron McKeating wrote:
[...]
>2004-05-19 00:01:14 F=<Elviragbp@???> RCPT
><d.gillingwater@???>: Bad HELO: ggyxnij (unqualified-helo)
>
>Is the Elviragbp@??? connecting to our server and asking to send
it is not Elviragbp@??? connecting to your server, it is
12.218.115.74 connecting, as you can see below
>mail to <d.gillingwater@???> and we accept that though we log the
>unqualified domain in the helo, then
have your logs a little less detailed and you will not even see that line...
>2004-05-19 00:01:14 H=12-218-115-74.client.mchsi.com (ggyxnij)
>[12.218.115.74] sender verify fail for <Elviragbp@???>: all
>relevant MX records point to non-existent hosts or (invalidly) to IP
>addresses
>
>This is checking that z45rcv.com is valid (which it isn't as a dig
>lookup gives
>
>;; ANSWER SECTION:
>z45rcv.com. 1152 IN MX 10 218.106.116.147.
>
>and I assume from the log entry that this should be a hostname not an ip
>address. So it does not matter whether mchsi.com is valid or not just
>the senders domain.
of course. It is sender verify after all, not connecting server PTR verify...
>Why did the header change from HELO: ggyxnij in the first log entry to
>H=12-218-115-74.client.mchsi.com (ggyxnij), why is this helo bad?
what header are you talking about? Nothing has changed. The string
after the H= is the PTR (reverse DNS) for the incoming IP, the string
in parenthesis is the HELO argument.
>2004-05-19 00:01:14 H=12-218-115-74.client.mchsi.com (ggyxnij)
>[12.218.115.74] F=<Elviragbp@???> rejected RCPT
><d.gillingwater@???>: Sender verify failed
>
>Then we reject the message. Is this correct, I just want to be sure I
>have understood it properly.
of course it is correct, it is exim doing it after all!
Giuliano
