Hi I am back thought I should start a new mail... since i lost track of previous. Anyways, Does Dovecot require courier-authdaemon or whatever it is called to run? When running the following i recieve the following output should I kill inet from 143 or not. aries:/etc/init.d# netstat -ltnp | grep ':143' tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 24715/inetd I am recieving the same response with the dovecot init file: aries:/etc/init.d# /etc/init.d/dovecot aries:/etc/init.d# /etc/init.d/dovecot aries:/etc/init.d# /etc/init.d/dovecot restart aries:/etc/init.d# There is no output possible because of inet? Any Help will be great! Thanks!
aries:/etc/init.d# netstat -ltnp | grep ':143'
aries:/etc/init.d#
Right I found that cyrus was in the inet config uncommented and now I recieve
outputs for dovecot :)
As for SquirrelMail Config test:
Warning: fsockopen(): unable to connect to localhost:143 in
/var/www/mail/src/configtest.php on line 247
ERROR: Error connecting to IMAP server "localhost:143".Server
error: (111)
Connection refused
Right so obiously I need to put dovecot in the inet conf any ideas what to put
in?
Thanks
Mark
Quoting Allen Parker <infowolfe at gmail.com>:
> On 8/14/05, admin at downend.org <admin at downend.org> wrote:
> > Hi I am back thought I should start a new mail... since i lost track
of
> > previous. Anyways,
> >
> > Does Dovecot require courier-authdaemon or whatever it is called to
run?
> > When running the following i recieve the following output should I
kill
> inet
> > from 143 or not.
> >
> > aries:/etc/init.d# netstat -ltnp | grep ':143'
> > tcp 0 0 0.0.0.0:143 0.0.0.0:*
LISTEN
> > 24715/inetd
>
> more than likely, you should check in your distribution's inetd.conf
> (under xinetd, normally /etc/xinetd.d/ is where configurations are
> kept) and remove any reference to an imap server in there since you're
> not launching dovecot from inetd... you should be seeing errors like
> "unable to bind to port" in your syslog coming from dovecot.. (i
> personally don't use inetd for launching things... but to each their
> own)
>
> hope this helps
>
> > I am recieving the same response with the dovecot init file:
> >
> > aries:/etc/init.d# /etc/init.d/dovecot
> > aries:/etc/init.d# /etc/init.d/dovecot
> >
> > aries:/etc/init.d# /etc/init.d/dovecot restart
> > aries:/etc/init.d#
> >
> >
> > There is no output possible because of inet?
> > Any Help will be great!
> > Thanks!
> >
>
>
> --
> ________________________________________
> To avoid being added to my spam filter:
> 1. Utilize list replies unless otherwise requested.
> 2. If you DO send me a personal email, use english.
> 3. HTML isn't cute. It belongs on the web, not in my inbox.
>
Update On the Following: Hey Everyone got some good news and some wierd things... Firstly, netstat -ltnp | grep ':143' -- does not show an output telnet localhost 143 -- Cannot Connect Secondly, I have no firewall installed. Thirdly, If I type "mail" as the user in SSH I can read my mail and I can send mail from other servers... which is strange considering it cannot connect Fourthly, /etc/init.d/dovecot start (Just start) -- Does not show an output. pidof dovecot -- Does not state a process for dovecot Any ideas what I should do... or anyone knows the reason. I checked mail.err and comes up with the following: Aug 14 07:15:04 aries imap-login: Can't load private key file /etc/ssl/private/dovecot.pe.................. and of course because of the above SquirrelMail cannot detect the Dovecot Imap Server. I would appreciate some step to step guidience as it is getting important. I also appreciate the people who have helped me and thank you for not being cocky... or big headed... Once dovecot is running I won't be touching it for a very long time :) Regards, Mark Smith Quoting Allen Parker <infowolfe at gmail.com>:> On 8/14/05, admin at downend.org <admin at downend.org> wrote: > > Hi I am back thought I should start a new mail... since i lost track of > > previous. Anyways, > > > > Does Dovecot require courier-authdaemon or whatever it is called to run? > > When running the following i recieve the following output should I kill > inet > > from 143 or not. > > > > aries:/etc/init.d# netstat -ltnp | grep ':143' > > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > > 24715/inetd > > more than likely, you should check in your distribution's inetd.conf > (under xinetd, normally /etc/xinetd.d/ is where configurations are > kept) and remove any reference to an imap server in there since you're > not launching dovecot from inetd... you should be seeing errors like > "unable to bind to port" in your syslog coming from dovecot.. (i > personally don't use inetd for launching things... but to each their > own) > > hope this helps > > > I am recieving the same response with the dovecot init file: > > > > aries:/etc/init.d# /etc/init.d/dovecot > > aries:/etc/init.d# /etc/init.d/dovecot > > > > aries:/etc/init.d# /etc/init.d/dovecot restart > > aries:/etc/init.d# > > > > > > There is no output possible because of inet? > > Any Help will be great! > > Thanks! > > > > > -- > ________________________________________ > To avoid being added to my spam filter: > 1. Utilize list replies unless otherwise requested. > 2. If you DO send me a personal email, use english. > 3. HTML isn't cute. It belongs on the web, not in my inbox. >