Hi all,
A good deal of you are noticing that Halibot is simply not taking to
your queries and a couple have sent in your error reports and
experiences.
I am running my own mail server and have done a little investigating
of my own. The mail to any Halibot address is still waiting in my
server's queue for immediate delivery end-to-end to halibot.com's
primary mail exchanger host as referenced by the DNS MX record:
hostess.halibot.com (66.13.235.76). I have routed the mail through
three international servers with varying TLD suffixes, and the
general result is that a connection to this host has not been
possible to establish. Attempting manually to connect reveals a live
machine but no open port 25. This is unusual even for machines which
refuse connections from specific IP addresses.
It is fairly possible to conclude at this stage that most people will
not be using Halibot in the near future unless someone contacts an
outside network administrator, since my server has tried for 72 hours
at 4 hour intervals to make this connection. If anyone believes
otherwise, or has had recent successes, please let me know.
Sabahattin
--
Thought for the day:
Bagpipes (n): an octopus wearing a kilt.
Latest PGP Public key? Click:
<mailto:[EMAIL PROTECTED]>
and send that message as is.
Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
E-mail or MSN Messenger: <[EMAIL PROTECTED]>
~~~~~~~~~~~~~~~ ACCMAIL Info (automatically generated) ~~~~~~~~~~~~~~
To UNSUBscribe: Send UNSUBSCRIBE ACCMAIL to [EMAIL PROTECTED]
To get the ACCMAIL FAQ: Send e-mail to "[EMAIL PROTECTED]"
and enter only this line in the BODY of the note:
send usenet/news.answers/internet-services/access-via-email
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
