On Thursday 24 January 2008 16:38:49 Craig White wrote: > On Thu, 2008-01-24 at 16:30 +0000, Anne Wilson wrote: > > this is what I was responding to... > > > > > # telnet localhost 110 > > > > .. > > > > # telnet localhost 143 > > > > .. > > > > > > Both these produce ''Temporary failure in name resolution'. > > so it seemed obvious that at some point, you had a defective /etc/hosts > because if dovecot were not running, that wouldn't be the message. For > example, this is what happens when I do this from a CentOS 5 server that > isn't running POP3/IMAP server... > > # telnet localhost 110 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > telnet: Unable to connect to remote host: Connection refused > > # telnet localhost 143 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > telnet: Unable to connect to remote host: Connection refused > You know how difficult it is to try to remember the exact sequence of events, once it's over, but yes - I got that as well, a little later. Right now I can't remember what happened in between. Meanwhile, although dovecot is now running, all is not well. I posted the details to the dovecot list, where I was told that 1.0.rc15 is old, and I should upgrade to 1.0.10, the latest stable release. I'm doing yum updates, so I presume that if this package is available for CentOS I would have to look for a 'testing' repository. Any advice there? Anne
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
