Page 4 of 4 FirstFirst ... 234
Results 31 to 38 of 38

Thread: HOWTO: install freepops

  1. #31
    Join Date
    Feb 2008
    Beans
    34

    Re: HOWTO: install freepops

    I would like to bump this thread.

    I've tried everything here and still cannot get freepops to work.

  2. #32
    Join Date
    Mar 2006
    Location
    Derby, uk
    Beans
    79
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: HOWTO: install freepops

    me to - this is a rubbish howto!

  3. #33
    Join Date
    Mar 2007
    Location
    New York City
    Beans
    108
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: HOWTO: install freepops

    same here... I am getting similar errors, sigh

    After typing: sudo freepopsd -p 2000 -b 127.0.0.1

    I receive the error: Unable to bind on 127.0.0.1:2000

    Does this have to do wit firewall permissions, firestarter, etc?

  4. #34
    Join Date
    May 2008
    Beans
    5

    Re: HOWTO: install freepops

    I am a newbee for Ubuntu but I have used Freepops for all my web mail for quite some time on Windows and here is how I got it working on Ubuntu.

    Search Freepops in Synaptic package manager and select to install freepops and freepops-updater-fltk

    After this do

    sudo apt-get install build-essential

    and that will install all the needed stuff.

    Now update all lua packages to the latest using

    sudo freepops-updater-fltk

    And now you can start the service using

    sudo freepopsd -p 110 -b 127.0.0.1 &
    (I used it for port 110 - you can use 2000 as in default setting)

    Now all my hotmail, yahoo, AOL and Gmail are working great. I use port 110 because I use a shared Thunderbird profile between my Windows and Ubuntu and in wondows I have been using port 110 as that seems to be the port my Virus scanner scans.

    Hope this will help someone.

    D.

  5. #35
    Join Date
    Jun 2008
    Beans
    2

    Re: HOWTO: install freepops

    After typing: sudo freepopsd -p 2000 -b 127.0.0.1

    I receive the error: Unable to bind on 127.0.0.1:2000

    Can someone help us with these???

  6. #36
    Join Date
    Jun 2008
    Beans
    2

    Re: HOWTO: install freepops

    Quote Originally Posted by ucro1263 View Post
    After typing: sudo freepopsd -p 2000 -b 127.0.0.1

    I receive the error: Unable to bind on 127.0.0.1:2000

    Can someone help us with these???

    OK, solved my above question myself!!!

    Here's what i did:
    PHP Code:
    sudo gedit /etc/default/freepops 
    in my file it contained the next data:
    PHP Code:
    #####################################
    # configuration file for freepopsd.
    #                                    
    # man freepopsd for more info.     
    DAEMON="/usr/bin/freepopsd"
    DAEMON_OPTS=" -n -s nobody.nogroup"
    PIDFILE="/var/run/freepops.pid"
    CHROOTED_DAEMON_OPTS=" -n -s nobody.nogroup" 
    i changed tha last line to look like this:
    PHP Code:
    #####################################
    # configuration file for freepopsd.
    #                                    
    # man freepopsd for more info.     
    DAEMON="/usr/bin/freepopsd"
    DAEMON_OPTS=" -n -s nobody.nogroup"
    PIDFILE="/var/run/freepops.pid"
    [COLOR="Red"]CHROOTED_DAEMON_OPTS=" -p 2000 -b 127.0.0.1 -n -s nobody.nogroup"[/COLOR
    save, close, and to the next instruction in the howTo.

  7. #37
    Join Date
    Jun 2009
    Beans
    9

    Re: HOWTO: install freepops

    To: Those who have gotten Freepops to work when guarddog is disabled, but not otherwise. There are two possible glitch points:

    (1) The connection between your mail client and the freepops demon (freepopsd). I have set mine up using 127.0.0.1 (localhost) port 2000, and I recommend other messages here to troubleshoot that part (In my installation, no adjustments were necessary in guarddog to enable a connection to localhost port 2000).

    (2) The connection between the freepops demon and the email server (in the INTERNET zone).
    The general factor to consider is that, while Freepops is categorized as a means to access "http mail," it may actually use other protocols (than "http" or "https") to retrieve your mail. Here's some info. which may help.

    I use freepops for yahoo mail, and did some troubleshooting using a log of blocked traffic (I used firestarter for this (?!)). My block occurred on Port 143.

    As it turns out, the current Freepops "lua" (access script) uses IMAP protocol to access yahoo mail (Freepops may also use this method for other services). In guarddog, the corresponding selection is "Internet/Protocol/Imap" (You can verify this by entering "143" in the "Port Reference" Tab). Click to make the checkmark appear, then click "Apply."

    I was able to download my yahoo mail after doing this. Unfortunately, there is a bug in the current [5/17/10] "yahoo.lua" file--keeps downloading the same messages ad infinitum--and I will have to install the update from the freepops bulletin board manually (http://freepops.diludovico.it). The fix was published by a bulletin board participant and hasn't yet been added to the freepops update repository.

    Now I will uninstall firestarter . If you would like to avoid the hassle, you can read the kernel log and get the "blocked packets" information directly (I was too much of a novice to identify this). Here's the corresponding log entry (/var/log/kern.log):
    May 17 07:49:17 [machine-name] kernel: [10167.520079] DROPPED IN= OUT=eth0 SRC=192.168.0.198 DST=98.136.131.29 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=42835 DF PROTO=TCP SPT=4517 DPT=143 SEQ=508079533 ACK=0 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101040201030307)

    Apparently "DPT" means "destination port." "SRC" would be your local machine's network address.

    Good Luck!
    Cam
    Last edited by yateendra; May 17th, 2010 at 07:09 PM. Reason: Deleted unnecessary instructions to create guarddog entry enabling localhost:2000

  8. #38
    Join Date
    Oct 2006
    Beans
    158

    Re: HOWTO: install freepops

    Make sure the following in /etc/defaults/freepops is changed


    DAEMON_OPTS=" -p 2000 -n -s nobody.nogroup"

    This makes the localhost error go a way even with a firewall.

Page 4 of 4 FirstFirst ... 234

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •