Qpopper Monthly Help File

         M O N T H L Y   Q P O P P E R   L I S T   H E L P

Addresses:
----------

Email addresses for this particular list server:

  List server:           qpopper-request <at> lists.pensive.org
  Everyone on the list:  qpopper <at> lists.pensive.org
  Human in charge:       listmaster <at> lists.pensive.org

Virtually,
The List Server Admin <listmaster <at> lists.pensive.org>

getting poppassd on fedora 3 to work?

Re: getting poppassd on fedora 3 to work?

Re: getting poppassd on fedora 3 to work?

qpopper and quotas

I have updated our qpopper patches which modify the locking mechanism to make 
it work with hard filesystem quotas. The new files for 4.08 are here:
http://www.softlab.ece.ntua.gr/~sivann/popper-ntua.tar.gz

The idea is to maintain the spool lock while mail is on the temp file, to 
prevent new mail to be appended to the truncated spool, because the sum of the 
spool and the temp spool can exceed the quota limit. New mail to be delivered 
should wait at the mailqueue for the spool to be unlocked. (The spool gets 
locked while it is being copied to the temp, so the mda has to cope with 
locked spools anyway.).

Developers, why not implementing this as an option.

--

-- 
Spiros  Ioannou
Image, Video and Multimedia Systems Laboratory
National Technical University of Athens
School of Electrical & Computer Engineering
Computer Science Division
Tel: +30-2107722491, +30-6973903808

Re: getting poppassd on fedora 3 to work?

Hi Tim,

>
>  service poppassd
>  {
>  port = 106
>  socket_type = stream
>  protocol = tcp
>  user = root
>  server = /usr/local/bin/poppassd
>  server_args = poppassd
>  wait = no
>  only_from = 127.0.0.1
               ^^^^^^^^^
>  instances = 4
>  disable = no
>  }
>
>  Tim

Your problem is there, most likely. What this line tells xinetd is to
only allow connections from the local host. You should either comment
(or remove) this line out or fix the liste to address to the
address(s) of your internal or DMZ interface(s).

God bless you,

Víctor Rafael Rivarola
--
FANÁTICO
"Por cuanto eres tibio, y no frío ni caliente, te vomitaré de mi boca."
Apocalipsis 3:16

LOCO
"Porque la Palabra de la Cruz es locura para los que se pierden; pero a
los que se salvan, esto es, a nosotros, es poder de Dios."
1 Corintios 1:18

Re: getting poppassd on fedora 3 to work?

On Mon, Nov 21, 2005 at 04:23:29PM -0300, Victor Rafael Rivarola Soerensen (FANATICO y LOCO por Cristo) wrote:
> Hi Tim,
> >  service poppassd
> >  {
> >  port = 106
> >  socket_type = stream
> >  protocol = tcp
> >  user = root
> >  server = /usr/local/bin/poppassd
> >  server_args = poppassd
> >  wait = no
> >  only_from = 127.0.0.1
>                ^^^^^^^^^
> >  instances = 4
> >  disable = no
> >  }
> >
> >  Tim
> 
> Your problem is there, most likely. What this line tells xinetd is to
> only allow connections from the local host. You should either comment
> (or remove) this line out or fix the liste to address to the
> address(s) of your internal or DMZ interface(s).

  No, he pointed out this is intentional, because it is only supposed to
allow connections from the webmail software running on the same box. 

  If there *is* any problem relating to this, it might be that the
webmail software is connecting to a public IP address instead of
localhost.  

  -- Clifton

--

-- 
    Clifton Royston  --  cliftonr <at> iandicomputing.com / cliftonr <at> lava.net
       President  - I and I Computing * http://www.iandicomputing.com/
 Custom programming, network design, systems and network consulting services

Re: getting poppassd on fedora 3 to work?

poppassd experts,
   I can connect by telneting to port 106 from the local host.  However, 
the error I get when using this method is "400 Server busy -- try again 
later".  So I am now thinking that there is some issue with it reading 
passwords from Fedora 3.  I believe Fedora uses shadow passwords so I 
compiled popppassd with the special_auth option.  Regardless, I can't 
change a password.  I might end up moving to a php script if I can't get 
this to work soon.  Any suggestions are very much welcome!
  Tim

At 03:05 PM 11/21/2005, Clifton Royston wrote:
>On Mon, Nov 21, 2005 at 04:23:29PM -0300, Victor Rafael Rivarola Soerensen 
>(FANATICO y LOCO por Cristo) wrote:
> > Hi Tim,
> > >  service poppassd
> > >  {
> > >  port = 106
> > >  socket_type = stream
> > >  protocol = tcp
> > >  user = root
> > >  server = /usr/local/bin/poppassd
> > >  server_args = poppassd
> > >  wait = no
> > >  only_from = 127.0.0.1
> >                ^^^^^^^^^
> > >  instances = 4
> > >  disable = no
> > >  }
> > >
> > >  Tim
> >
> > Your problem is there, most likely. What this line tells xinetd is to
> > only allow connections from the local host. You should either comment
> > (or remove) this line out or fix the liste to address to the
> > address(s) of your internal or DMZ interface(s).
>
>   No, he pointed out this is intentional, because it is only supposed to
>allow connections from the webmail software running on the same box.
>
>   If there *is* any problem relating to this, it might be that the
>webmail software is connecting to a public IP address instead of
>localhost.
>
>   -- Clifton
>
>
>--
>     Clifton Royston  --  cliftonr <at> iandicomputing.com / cliftonr <at> lava.net
>        President  - I and I Computing * http://www.iandicomputing.com/
>  Custom programming, network design, systems and network consulting services

Tim Tyler
Network Engineer - Beloit College
tyler <at> beloit.edu 

Re: getting poppassd on fedora 3 to work?

2005/11/21, Clifton Royston <cliftonr <at> lava.net>:
> On Mon, Nov 21, 2005 at 04:23:29PM -0300, Victor Rafael Rivarola Soerensen (FANATICO y LOCO por Cristo) wrote:
> > Hi Tim,
> > >  service poppassd
> > >  {
> > >  port = 106
> > >  socket_type = stream
> > >  protocol = tcp
> > >  user = root
> > >  server = /usr/local/bin/poppassd
> > >  server_args = poppassd
> > >  wait = no
> > >  only_from = 127.0.0.1
> >                ^^^^^^^^^
> > >  instances = 4
> > >  disable = no
> > >  }
> > >
> > >  Tim
> >
> > Your problem is there, most likely. What this line tells xinetd is to
> > only allow connections from the local host. You should either comment
> > (or remove) this line out or fix the liste to address to the
> > address(s) of your internal or DMZ interface(s).
>
>   No, he pointed out this is intentional, because it is only supposed to
> allow connections from the webmail software running on the same box.

Tim, are your users only connneecting through webmail? The way I
understood you, they where able to connect by webmail and not pops,
hence the problem you where asking aboout. If I read you wronng, I am
sorry.

>
>   If there *is* any problem relating to this, it might be that the
> webmail software is connecting to a public IP address instead of
> localhost.
>
>   -- Clifton

Uhhmm...yes, this could also be the problem I had not thought about.

God bless you all,

Víctor Rafael Rivarola

--
FANÁTICO
"Por cuanto eres tibio, y no frío ni caliente, te vomitaré de mi boca."
Apocalipsis 3:16

LOCO
"Porque la Palabra de la Cruz es locura para los que se pierden; pero a
los que se salvan, esto es, a nosotros, es poder de Dios."
1 Corintios 1:18

Re: getting poppassd on fedora 3 to work?

At 04:53 PM 11/21/2005, Tim Tyler wrote:
>poppassd experts,
>   I can connect by telneting to port 106 from the local 
> host.  However, the error I get when using this method is "400 
> Server busy -- try again later".  So I am now thinking that there 
> is some issue with it reading passwords from Fedora 3.  I believe 
> Fedora uses shadow passwords so I compiled popppassd with the 
> special_auth option.  Regardless, I can't change a password.  I 
> might end up moving to a php script if I can't get this to work 
> soon.  Any suggestions are very much welcome!

If you need a web-based password changing capability for your users, 
take a look at this one:

http://www.unicom.com/sw/web-chpass/

We use that for our users, and it works well.

If you're not using POPPASSD from Eudora or other clients anyway, 
then it's probably not worth messing with.

Dan

>  Tim
>
>At 03:05 PM 11/21/2005, Clifton Royston wrote:
>>On Mon, Nov 21, 2005 at 04:23:29PM -0300, Victor Rafael Rivarola 
>>Soerensen (FANATICO y LOCO por Cristo) wrote:
>> > Hi Tim,
>> > >  service poppassd
>> > >  {
>> > >  port = 106
>> > >  socket_type = stream
>> > >  protocol = tcp
>> > >  user = root
>> > >  server = /usr/local/bin/poppassd
>> > >  server_args = poppassd
>> > >  wait = no
>> > >  only_from = 127.0.0.1
>> >                ^^^^^^^^^
>> > >  instances = 4
>> > >  disable = no
>> > >  }
>> > >
>> > >  Tim
>> >
>> > Your problem is there, most likely. What this line tells xinetd is to
>> > only allow connections from the local host. You should either comment
>> > (or remove) this line out or fix the liste to address to the
>> > address(s) of your internal or DMZ interface(s).
>>
>>   No, he pointed out this is intentional, because it is only supposed to
>>allow connections from the webmail software running on the same box.
>>
>>   If there *is* any problem relating to this, it might be that the
>>webmail software is connecting to a public IP address instead of
>>localhost.
>>
>>   -- Clifton
>>
>>
>>--
>>     Clifton Royston  --  cliftonr <at> iandicomputing.com / cliftonr <at> lava.net
>>        President  - I and I Computing * http://www.iandicomputing.com/
>>  Custom programming, network design, systems and network consulting services
>
>Tim Tyler
>Network Engineer - Beloit College
>tyler <at> beloit.edu