--On 22 June 2007 18:46:01 +1000 Christopher Glanville
<christopher_glanville@???> wrote:
> Connecting to smtp.isp.com [XX.XX.XX.XX]:25 ... connected
> SMTP<< 220-Mycroft.smtp.isp.com ESMTP Sendmail 8.14.0/8.14.0; Fri, 22
> Jun 2007 04:39:57 -0400 (EDT)
> 220-All transactions are logged.
> 220 Only authenticated connections are permitted on this host.
> SMTP>> EHLO localhost
> SMTP<< 250-Mycroft.smtp.isp.com Hello
> dsl-124-150-121-6.vic.smtp.isp.com [XX.XX.XX.XX], pleased to meet you
> 250-ENHANCEDSTATUSCODES
> 250-PIPELINING
You're obfuscating, which is pointless because you're not doing it very
well. Nevertheless, it makes it harder for people to help you. Please don't
do it.
Here, for example, you've tried but failed to mask your IP address. I'll
bet it's 6.121.150.124, no? You've also tried to hide the name of the host
that you're trying to connect to, but you revealed it in an earlier email.
If you must obfuscate domains, please use example.com or similar. RFC2606
reserves some domain names for this purpose. smtp.server.isp.com is a
registered domain, so please don't use it as an example.
Or maybe you actually did insert smtp.isp.com into your config? You
shouldn't, but it was suggested to you when the real server name was also
available.
--
Ian Eiloart
IT Services, University of Sussex
x3148
