09-19-05 11:01 PM
In this case, yes the host named beta generated the HELO command.
If it's not your host, then it's one of the hosts that lies in your path.
Could be your host, could be the ISP, could be the recipient. Any
information in the headers of the message? If it's not your host, then you'd
want to start outside your network with the next hop and follow it until you
find the host.
You can look up the dns records and open your own conversations to the hosts
with a telnet session to TCP 25 (from a windows command line: telnet host 25
will open the session you want.)
Feel free to drop a note offline if you need some additional help with
troubleshooting this. Some more details (some you may not want to share on
a public board) would be needed to help any more than these suggestions.
Al
"MikeR" <NOnf4lSPAM@pobox.com> wrote in message
news:erBsYbRvFHA.1256@TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Inline
>
> Al Mulnick wrote:
> I don't know. The return address on the error e-mail is postmaster@beta. I
> don't know a server or domain named beta.
>
> Who generates the HELO command? Beta?
>
[ Post a follow-up to this message ]
|