Cannot connect to mailserver - (popfile)

[LiNuts]

I have installed popfile, and set up the buckets. I am using kmail to get my e-mails, as per the popfile tutorial, i changed my login to this:

 

Name: linuts

Login: pop.pacnet:linuts

Password:************

Host:127.0.0.1

port:110

 

But i get the error message "could not connect to host 127.0.0.1"

 

Using Mandrake 10.0 official

 

according to the popfile tutorial the port should be 8080, so i tried "127.0.0.1:8080" but got the same error.

 

Cheers

linuts

 

 

Edit: moved from Software by spinynorman

[Steve Scrimpshire]

The port 8080 is for the web interface configuration for Popfile. Point your browser there and you will see (will only work if popfile is actually running):

http://127.0.0.1:8080

 

I had a problem getting popfile to even start when trying to use port 110. Set popfile to use port 1110 and then adjust your settings in Kmail accordingly and all should be well.

[LiNuts]

I tried port 1110, but got the same message, I can reach http://127.0.0.1:8080/ no problems. It is when i go to use Kmail i get the "cannot connect to host 127.0.0.1" error.

 

I checked the /etc/hosts file and there is an entry for 127.0.0.1 localhost there. I have tried using a couple of different Mail programs ( Evolution --- Operas M2 ) but its still the same.

 

I even put an entry in the /etc/hosts.allow file for 127.0.0.1 but that didn't work either.

 

Anyone any idea of what this could be,

 

Cheers

LiNuts

 

edit: when i change the settings back to normal using kmail, it works o.k.

Edited May 9, 2004 by LiNuts

[LiNuts]

O.K. Have found the problem ( i think ) Its the startup script. When i shutdown popfile using the script in /etc/init.d/popfile stop and re-start it /etc/init.d/popfile start, all works o.k.

 

Now perhaps someone with a lot more experience than i have can shed some light as to why the startup script ( i presume its the /etc/rc.d/rc5.d/S65popfile ) script thats stuffing things up.

 

Its going to be a pain to keep having to shutdown and restart popfile.

 

Cheers

linuts

[tyme]

my suggestion would to be to check and see if for some reason the startup script is being run before the network (eth0 and lo) are brought up during boot. but that's just a wild stab :-/

[LiNuts]

Just goes to show what a newbie i am :D I never thought of that, I'll run the "sysv-init" and check,

 

As i am on dial-up, i suppose i'll have to make sure that the startup script /etc/rc.d/rc5.d/S65popfile starts after my network connection script.

 

Cheers

linuts

[LiNuts]

O.K. I couldn't find SysV-init to check whether the popfile scrip is starting before the ip-up script, so i made a quick bash script and made it executable and put it in /etc/ppp/ip-up.d, and it worked :lol:

 

Now when i use my dial-up my script automatically shuts down and restarts popfile. For anyone who wants to use it here it is:

 #!/bin/bash
            #popfile script
            /etc/init.d/popfile stop
            /etc/init.d/popfile start
            echo "popfile is running"

then save the script as a .sh file, then chmod +x to make it executable.

There probably is a better way to do it, but this works for me.

cheers

linuts