The qpopper list archive ending on 27 Dec 1999


Topics covered in this issue include:

  1. Re: Qpopper 3.0b26 available
       Qpopper Support <qpopper at qualcomm dot com>
       Sat, 18 Dec 1999 10:03:30 -0800
  2. Re: Qpopper 3.0b26 available
       Qpopper Support <qpopper at qualcomm dot com>
       Sat, 18 Dec 1999 10:14:41 -0800
  3. Re: Qpopper 3.0b26 available
       Carrer Yuri <yurj at dns.alfa dot it>
       Sat, 18 Dec 1999 19:39:09 +0100 (MET)
  4. Re: Qpopper 3.0b26 available
       Qpopper Support <qpopper at qualcomm dot com>
       Sat, 18 Dec 1999 11:20:08 -0800
  5. why does qpopper start up three popper deamon every time?
       NightHawk <nighthawk at szonline dot net>
       Mon, 20 Dec 1999 16:32:51 +0800
  6. need qpopper3.0b22
       Benjamin Berger <benjamin.berger at ascom dot ch>
       Mon, 20 Dec 1999 10:00:06 +0100
  7. Grind to a halt
       "Martyn Routley" <martynr at invictanet.co dot uk>
       Mon, 20 Dec 1999 15:28:37 -0000
  8. RE: Grind to a halt
       Steven Fletcher <stevenf at shellnet.co dot uk>
       Mon, 20 Dec 1999 15:51:07 -0000
  9. Re: why does qpopper start up three popper deamon every time?
       Qpopper Support <qpopper at qualcomm dot com>
       Mon, 20 Dec 1999 12:16:03 -0800
 10. Re: Grind to a halt
       Qpopper Support <qpopper at qualcomm dot com>
       Mon, 20 Dec 1999 12:18:27 -0800
 11. Qpopper 3.0b26 available but still no PAM support.  :(
       Jonathan Benson <sysadmin at ocean.com dot au>
       Tue, 21 Dec 1999 11:12:03 +1100
 12. Re: Qpopper 3.0b26 available but still no PAM support.  :(
       Byron Jones <byron at vianet.net dot au>
       Tue, 21 Dec 1999 09:16:21 +0800
 13. Re: Qpopper 3.0b26 available but still no PAM support.  :(
       Qpopper Support <qpopper at qualcomm dot com>
       Mon, 20 Dec 1999 17:56:22 -0800
 14. Re: Qpopper 3.0b26 available but still no PAM support.  :(
       "Igor S. Livshits" <igorl at life.uiuc dot edu>
       Mon, 20 Dec 1999 21:15:34 -0600
 15. Re: Qpopper 3.0b26 available but still no PAM support.  :(
       Carrer Yuri <yurj at dns.alfa dot it>
       Tue, 21 Dec 1999 09:27:12 +0100 (MET)
 16. Michael Nugents mysql patch
       Thomas Egrelius <thomas at egrelius dot nu>
       Tue, 21 Dec 1999 15:31:46 +0100 (MET)
 17. AFS and QPOPPER
       "Thorsten A. Knieling" <knieling at hrz.tu-darmstadt dot de>
       Tue, 21 Dec 1999 16:47:30 +0100 (CET)
 18. Compile Failure with 30.b26
       forrie at forrie dot com (Forrest Aldrich)
       Tue, 21 Dec 1999 09:53:22 -0800
 19. Re: Compile Failure with 30.b26
       Vince Vielhaber <vev at michvhf dot com>
       Tue, 21 Dec 1999 13:15:55 -0500 (EST)
 20. How to ensure sender uses a valid return address?
       "Jonathan C. Detert" <detertj at matc dot edu>
       Tue, 21 Dec 1999 12:53:14 -0600
 21. preventing pop locks
       "Kaley Davis" <kaley at drizzle dot net>
       Tue, 21 Dec 1999 14:05:40 -0800
 22. Re: How to ensure sender uses a valid return address?
       Randall Gellens <randy at qualcomm dot com>
       Tue, 21 Dec 1999 14:46:33 -0800
 23. Re: preventing pop locks
       Qpopper Support <qpopper at qualcomm dot com>
       Tue, 21 Dec 1999 14:49:44 -0800
 24. RE: Michael Nugents mysql patch
       Steven Fletcher <stevenf at shellnet.co dot uk>
       Wed, 22 Dec 1999 11:46:49 -0000
 25. Q on pop_pass.c
       "Mark Anthony J. Mercado" <mark at calamba.laguna dot net>
       Wed, 22 Dec 1999 20:36:40 +0800 (PHT)
 26. Re: Q on pop_pass.c
       Jesus Cea Avion <jcea at argo dot es>
       Wed, 22 Dec 1999 13:44:09 +0100
 27. RE: Q on pop_pass.c
       Steven Fletcher <stevenf at shellnet.co dot uk>
       Wed, 22 Dec 1999 12:52:39 -0000
 28. RE: Michael Nugents mysql patch
       robert rotman <rotman at inode dot at>
       Wed, 22 Dec 1999 14:21:20 +0100 (CET)
 29. RE: Michael Nugents mysql patch
       Alan Brown <alan at manawatu.gen dot nz>
       Thu, 23 Dec 1999 02:31:39 +1300 (NZDT)
 30. RE: Michael Nugents mysql patch
       robert rotman <rotman at inode dot at>
       Wed, 22 Dec 1999 14:44:57 +0100 (CET)
 31. RE: Michael Nugents mysql patch
       Alan Brown <alan at manawatu.gen dot nz>
       Thu, 23 Dec 1999 02:48:52 +1300 (NZDT)
 32. RE: Michael Nugents mysql patch
       Fergal Daly <fergal at esatclear dot ie>
       Wed, 22 Dec 1999 14:24:15 +0000
 33. Re: Q on pop_pass.c
       Michael L Vezie <mlv at pobox dot com>
       Wed, 22 Dec 1999 11:12:09 -0500
 34. RE: Michael Nugents mysql patch
       Steven Fletcher <stevenf at shellnet.co dot uk>
       Wed, 22 Dec 1999 16:14:44 -0000
 35. RE: Michael Nugents mysql patch
       Fergal Daly <fergal at esatclear dot ie>
       Wed, 22 Dec 1999 18:13:20 +0000
 36. dead subscriber?
       Fergal Daly <fergal at esatclear dot ie>
       Wed, 22 Dec 1999 19:15:33 +0000
 37. RE: Michael Nugents mysql patch
       Alan Brown <alan at manawatu.gen dot nz>
       Thu, 23 Dec 1999 13:31:06 +1300 (NZDT)
 38. Mailbox corruption
       Kelly Peterson <KellyP at interbaun dot net>
       Thu, 23 Dec 1999 08:53:50 -0700
 39. Re: Mailbox corruption
       "Kaley Davis" <kaley at drizzle dot net>
       Thu, 23 Dec 1999 11:39:28 -0800
 40. Re: Mailbox corruption
       Qpopper Support <qpopper at qualcomm dot com>
       Thu, 23 Dec 1999 15:42:33 -0800
 41. Mail Modernization Project
       Mike Nugent <mnugent at goamerica dot net>
       Fri, 24 Dec 1999 12:53:44 -0500
 42. Re: dead subscriber?
       Listmaster <listmaster at lists.pensive dot org>
       Sun, 26 Dec 1999 21:33:14 -0800
 43. Password incorrect
       Jason Oakley <illogix at ihug.com dot au>
       Mon, 27 Dec 1999 18:58:52 +1100
 44. Re: Password incorrect
       pestilence <pestilence at netplan dot gr>
       Mon, 27 Dec 1999 10:26:44 +0200
 45. Re: Password incorrect
       Rik Schneider <rik at deranged.schneider dot org>
       Mon, 27 Dec 1999 08:09:30 +0000
 46. Re: Password incorrect
       Jason Oakley <illogix at ihug.com dot au>
       Mon, 27 Dec 1999 19:33:02 +1100
 47. Re: Password incorrect
       Balgansuren <balgaa at publica.ub.mng dot net>
       Mon, 27 Dec 1999 16:49:36 -0800 (GMT)
 48. FYI: Red Hat 5.2/6.1 incompatibility
       "Kenneth Porter" <shiva at well dot com>
       Mon, 27 Dec 1999 01:43:08 -0800
 49. Re: FYI: Red Hat 5.2/6.1 incompatibility
       pestilence <pestilence at netplan dot gr>
       Mon, 27 Dec 1999 12:09:15 +0200
 50. Re: FYI: Red Hat 5.2/6.1 incompatibility
       "Kenneth Porter" <shiva at well dot com>
       Mon, 27 Dec 1999 02:19:29 -0800

Date: Sat, 18 Dec 1999 10:03:30 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0b26 available

At 8:57 PM -0800 12/17/99, Kenneth Porter wrote:

>On Fri, 17 Dec 1999 18:46:22 -0800, Qpopper Support wrote:
>
>>Changes from 3.0b25 to 3.0b26
>
>Excellent news! Looks like this addresses several outstanding concerns.
>
>It now compiles clean on my Red Hat 5.2 box with the extra warnings
>enabled.

I'm glad to hear it.

>
>I'd suggest fixing the Last updated date at the top of the
>Release.Notes.

Note that the Changes file gets updated every beta cycle, while 
Release.Notes gets updated less often.  But thanks for the tip -- 
there are some things that should get copied from Changes to 
Release.Notes.

Date: Sat, 18 Dec 1999 10:14:41 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0b26 available

At 9:20 AM +0100 12/18/99, Carrer Yuri wrote:

>  >   5.  If gcc version 2.7.2.3 is detected, remove -O2 flag.
>
>  Why? :)

It seems the 2.7.2.3 optimizer generates bad code for certain 
constructs used in qpopper, such as:

             if (s->function != NULL) {
                 p.CurrentState = (p.CurrentState != halt) &&
		    (p.CurrentState != error ) ?
		    s->result[(*s->function)(&p)] : p.CurrentState;
             }

So the choices were to either add a kluge to the code (store s in a 
local temporary) or disable the optimizer when gcc 2.7.2.3 is used.

Date: Sat, 18 Dec 1999 19:39:09 +0100 (MET)
From: Carrer Yuri <yurj at dns.alfa dot it>
Subject: Re: Qpopper 3.0b26 available

On Sat, 18 Dec 1999, Qpopper Support wrote:

> At 9:20 AM +0100 12/18/99, Carrer Yuri wrote:
> 
> >  >   5.  If gcc version 2.7.2.3 is detected, remove -O2 flag.
> >
> >  Why? :)
> 
> It seems the 2.7.2.3 optimizer generates bad code for certain 
> constructs used in qpopper, such as:
> 
>              if (s->function != NULL) {
>                  p.CurrentState = (p.CurrentState != halt) &&
> 		    (p.CurrentState != error ) ?
> 		    s->result[(*s->function)(&p)] : p.CurrentState;
>              }
> 
> So the choices were to either add a kluge to the code (store s in a 
> local temporary) or disable the optimizer when gcc 2.7.2.3 is used.

 Thanks. I've reported SEVERAL time that there where some problem with
 my box, a linux libc5 based with gcc 2.7.3. Im glad someone have looked
 at it. So everyone has used qpopper on a Linux box, and compiled it, had
 a bad code in it :)


Date: Sat, 18 Dec 1999 11:20:08 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0b26 available

At 7:39 PM +0100 12/18/99, Carrer Yuri wrote:

>  Thanks. I've reported SEVERAL time that there where some problem with
>  my box, a linux libc5 based with gcc 2.7.3. Im glad someone have looked
>  at it. So everyone has used qpopper on a Linux box, and compiled it, had
>  a bad code in it :)

This was reported to us by Brian McCauley, who did the analysis; he 
deserves the credit.

Note however, that the current check (which is rather a kluge) looks 
for gcc version 2.7.2.3 only; 2.7.3 won't match and hence will have 
the optimizer enabled.  If it, too, (or any other version) generates 
bad code, please report it to us.

Date: Mon, 20 Dec 1999 16:32:51 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: why does qpopper start up three popper deamon every time?

Hello, all
     I have been running qpopper from 2.53 to 3.25 on solaris 2.6 and
solaris 7
since the april.
     I don't know why does inetd start up three popper deamon  every
time when 
I don't use the "-R" parameter in my inetd.conf. such as:
    pop3  stream  tcp  nowait.1800  root  /usr/sbin/popper popper  -T
420
,but when I  use the parameter "-R" in my inetd.conf (as follows:)
    pop3 stream  tcp nowait.1800  root /usr/sbin/popper popper -R -T 420
This thing will not happen! 
      Furthermore, the download speed of message  will become slow and
slow 
when my dailup users retrieve their messages with a binary
attachment(such as
image file or a program),and sometime it will hangup ,and sometime it
will
generate a BOGUS.user* file ( infrequence). But in a LAN , it run very
well. 
I don't know whether the next release  will resolve this problem!

      Thanks in advance!

Date: Mon, 20 Dec 1999 10:00:06 +0100
From: Benjamin Berger <benjamin.berger at ascom dot ch>
Subject: need qpopper3.0b22

hi, out there!

I like to use the mysqlauth-patch (http://www.riverstyx.net/qpopmysql/) for
the qpopper-server.
to use this patch I need a copy of the qpopper3.0b22! ... can you say me
where to get this?

greetz,

Benjamin Berger


From: "Martyn Routley" <martynr at invictanet.co dot uk>
Subject: Grind to a halt
Date: Mon, 20 Dec 1999 15:28:37 -0000

Hi
I use v2.53 on FreeBSD 3.0

Several of our users have a problem where, when they are downloading one or more large messages, the data flow just stops. The
client software then starts to timeout and eventually gives up even though there is a good connection to the mail server and other
traffic (ping traceroute http) etc is ongoing.

Any ideas please?

Martyn
-----------------------------------------------------
InvictaNet - The Internet in Plain English, Guaranteed
http://www.invictanet.co.uk
mailto:info at invictanet.co dot uk
phone: 0870 7402252
fax: +44 (0)1233 334001
------------------------------------------------------


From: Steven Fletcher <stevenf at shellnet.co dot uk>
Subject: RE: Grind to a halt
Date: Mon, 20 Dec 1999 15:51:07 -0000

traceroute to invictanet.co.uk (62.232.18.118), 30 hops max, 40 byte packets
 1  pipex-gw.shellnet.co.uk (194.129.209.1)  2.022 ms  3.103 ms  4.584 ms
 2  man-gw3.pipex.net (158.43.183.3)  12.453 ms  4.832 ms  3.940 ms
 3  fddi0-0-0.cr1.man1.gbb.uk.uu.net (158.43.180.1)  2.679 ms  4.223 ms
17.017 ms
 4  pos6-0-0.cr1.bhx1.gbb.uk.uu.net (158.43.254.158)  24.086 ms  5.178 ms
18.353 ms
 5  pos4-0-0.cr1.rea1.gbb.uk.uu.net (158.43.254.37)  7.976 ms  27.080 ms
15.693 ms
 6  fe1-1-0.cr2.rea1.gbb.uk.uu.net (158.43.254.94)  8.139 ms  9.471 ms
24.786 ms
 7  pos0-2.cr1.lnd4.gbb.uk.uu.net (158.43.254.29)  31.447 ms  9.261 ms
24.900 ms
 8  pos0-0.cr1.lnd8.gbb.uk.uu.net (158.43.254.53)  13.879 ms  11.267 ms
9.992 ms
 9  fe0-0-0.br1.lnd8.gbb.uk.uu.net (158.43.188.69)  16.888 ms  22.063 ms
13.204 ms
10  linx-l1.ukcore.bt.net (195.66.225.10)  12.766 ms  25.926 ms  10.933 ms
11  core1-fe-1-1.telehouse.bt.net (194.74.16.1)  37.728 ms  32.199 ms
23.474 ms
12  core1-pos11-0.ealing.bt.net.65.74.194.in-addr.arpa (194.74.65.26)
12.015 ms  38.401 ms  16.636 ms
13  access1-FE1-1-0.ealing.bt.net (194.72.9.163)  36.306 ms  24.114 ms
15.529 ms
14  194.74.78.93 (194.74.78.93)  30.044 ms  35.172 ms  52.002 ms
15  62.232.126.41 (62.232.126.41)  31.155 ms  27.357 ms  40.727 ms
16  router.ns0.net (62.232.18.65)  2843.606 ms  2655.134 ms  2030.517 ms
<---  !!
17  colossus.invictanet.co.uk (62.232.18.118)  476.972 ms  945.546 ms
1002.919 ms    <---  !!

Are your customers accessing your mailserver from outside of your network? I
doubt that the line being as busy as those response times show them to be
will be able to support mail connections (especially to Win 9x clients) with
much reliability. This would be highlighed with large emails.

Steven Fletcher
stevenf at shellnet.co dot uk

> -----Original Message-----
> From: Martyn Routley [mailto:martynr at invictanet.co dot uk]
> Sent: 20 December 1999 15:29
> To: Subscribers of Qpopper
> Subject: Grind to a halt
>
>
> Hi
> I use v2.53 on FreeBSD 3.0
>
> Several of our users have a problem where, when they are
> downloading one or more large messages, the data flow just stops. The
> client software then starts to timeout and eventually gives
> up even though there is a good connection to the mail server and other
> traffic (ping traceroute http) etc is ongoing.
>
> Any ideas please?
>
> Martyn
> -----------------------------------------------------
> InvictaNet - The Internet in Plain English, Guaranteed
> http://www.invictanet.co.uk
> mailto:info at invictanet.co dot uk
> phone: 0870 7402252
> fax: +44 (0)1233 334001
> ------------------------------------------------------
>
>


Date: Mon, 20 Dec 1999 12:16:03 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: why does qpopper start up three popper deamon every time?

At 04:32 PM 12/20/99 +0800, NightHawk wrote:
>Hello, all
>      I have been running qpopper from 2.53 to 3.25 on solaris 2.6 and
>solaris 7
>since the april.
>      I don't know why does inetd start up three popper deamon  every
>time when
>I don't use the "-R" parameter in my inetd.conf. such as:
>     pop3  stream  tcp  nowait.1800  root  /usr/sbin/popper popper  -T
>420
>,but when I  use the parameter "-R" in my inetd.conf (as follows:)
>     pop3 stream  tcp nowait.1800  root /usr/sbin/popper popper -R -T 420
>This thing will not happen!
>       Furthermore, the download speed of message  will become slow and
>slow
>when my dailup users retrieve their messages with a binary
>attachment(such as
>image file or a program),and sometime it will hangup ,and sometime it
>will
>generate a BOGUS.user* file ( infrequence). But in a LAN , it run very
>well.
>I don't know whether the next release  will resolve this problem!
>
>       Thanks in advance!


Please use 3.0b26 and enable trace debugging by adding '--enable-debugging' 
to the './configure' command (be sure to do a 'make clean' first).  Then 
add '-t tracefile' to the inetd line (and send a HUP signal to 
inetd).  This causes additional trace debugging lines to be written to the 
file specified as 'tracefile'.

If you can reproduce the additional processes being connected when -R is 
not used, please send in 'tracefile'.  It is hard to imagine how -R could 
affect this, so I suspect there is something else going on.

More importantly, the additional trace records in 'tracefile' should help 
diagnose what is going on when users have problems with binary 
attachments.  Please send in 'tracefile' (or enough of it to show the 
sessions with problems).

Send the material to <qpopper at qualcomm dot com>, not to the list.

Thank you for your help.



Date: Mon, 20 Dec 1999 12:18:27 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Grind to a halt

At 03:28 PM 12/20/99 +0000, Martyn Routley wrote:
>Hi
>I use v2.53 on FreeBSD 3.0
>
>Several of our users have a problem where, when they are downloading one 
>or more large messages, the data flow just stops. The
>client software then starts to timeout and eventually gives up even though 
>there is a good connection to the mail server and other
>traffic (ping traceroute http) etc is ongoing.

Please use 3.0b26 and enable trace debugging by adding '--enable-debugging' 
to the './configure' command (be sure to do a 'make clean' first).  Then 
add '-t tracefile' to the inetd line (and send a HUP signal to 
inetd).  This causes additional trace debugging lines to be written to the 
file specified as 'tracefile'.

The additional trace records in 'tracefile' should help diagnose what is 
going on when users have problems with large messages.  Please send in 
'tracefile' (or enough of it to show the sessions with problems).

Send the material to <qpopper at qualcomm dot com>, not to the list.

Thank you for your help.


Date: Tue, 21 Dec 1999 11:12:03 +1100
From: Jonathan Benson <sysadmin at ocean.com dot au>
Subject: Qpopper 3.0b26 available but still no PAM support.  :(

Qpopper Support wrote:

> Qpopper 3.0b26 is available at
> <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
>

PLEASE!  Add PAM support!  :(

I may be one of only a few that wants it but after much fiddling to get
the patch from b18 to work with b25 it is once again broken against
b26.  Looks like I have another hour or so of stuffing about to get it
working again.

Also if you happen to read this and use a system using PAM (wether or
not you use the patch or just end up configuring it for shadowed
passwords) then please reply to the thread to give an indication of how
many are interested (but keep it short so as not to SPAM the list).  If
I am indeed one of only a few people then I can understand the low
priority on adding support for PAM.

I can't see why folks as knowledgeable as the qpopper team can't apply a
patch, check a few odds and ends and then have it as part of the
official distribution?  It's a small amount of code effecting 2 code
files and the config files.

At least then I wouldn't have to try creating a new patch every release
of a new beta.

Sorry, but I just had to whinge.  We are some 8 patch levels on since
German so kindly created this patch and it's yet to make it in to a
current beta.

Oh and while I'm complaining I might as well mention that bulletins
don't work for me (in fact won't even compile without a patch I posted
here back around b18) on a RedHat Linux (6.0) box but I gave up on that
idea when it still didn't work under b25 (I get error messages saying it
can't open/lock, or something like that, the bulletin database on the
odd occasion).

Jon

--
Jonathan Benson
Systems Administrator
Ocean Internet
http://www.ocean.com.au/




Date: Tue, 21 Dec 1999 09:16:21 +0800
From: Byron Jones <byron at vianet.net dot au>
Subject: Re: Qpopper 3.0b26 available but still no PAM support.  :(

>PLEASE!  Add PAM support!  :(

i second that motion.

-- byron jones ----------------------
    systems administrator
    vianet australia
    http://www.vianet.net.au/~byron


Date: Mon, 20 Dec 1999 17:56:22 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0b26 available but still no PAM support.  :(

At 11:12 AM +1100 12/21/99, Jonathan Benson wrote:

>  PLEASE!  Add PAM support!  :(

We have been working on bug fixing before addressing additional 
features.  PAM is the at the top of the list to be added, thanks to 
the patches that were sent in.

>  Oh and while I'm complaining I might as well mention that bulletins
>  don't work for me (in fact won't even compile without a patch I posted
>  here back around b18) on a RedHat Linux (6.0) box but I gave up on that
>  idea when it still didn't work under b25 (I get error messages saying it
>  can't open/lock, or something like that, the bulletin database on the
>  odd occasion).

I'll look into this.  Does the error message occur every time, or 
only on occasion?  What is the exact error message?


Date: Mon, 20 Dec 1999 21:15:34 -0600
From: "Igor S. Livshits" <igorl at life.uiuc dot edu>
Subject: Re: Qpopper 3.0b26 available but still no PAM support.  :(

At 9:16 AM +0800 on 12/21/99, Byron Jones wrote:
>>PLEASE!  Add PAM support!  :(
>
>

I agree -- I cannot justify manually adding these code changes with 
every release, and I am not about to give up PAM.

Thanks, igor


Date: Tue, 21 Dec 1999 09:27:12 +0100 (MET)
From: Carrer Yuri <yurj at dns.alfa dot it>
Subject: Re: Qpopper 3.0b26 available but still no PAM support.  :(

On Tue, 21 Dec 1999, Byron Jones wrote:

> >PLEASE!  Add PAM support!  :(
> 
> i second that motion.
> 

 me too :)



Date: Tue, 21 Dec 1999 15:31:46 +0100 (MET)
From: Thomas Egrelius <thomas at egrelius dot nu>
Subject: Michael Nugents mysql patch

Hi!

I'm trying to use the changes Michael Nugent have done to qpopper, to use
a mysql database for authentication, but with no luck.

I've patched all files with his diffs, and compiled ok. The binary works
just fine, but it is still using /etc/passwd for authentication.

I guess I have to modify the Makefile in some way, and I have tried to do
it but with the same result.

Have anyone else used Michaels patches successfully? I guess so... ;-)
What do I have to do except patching the source files?

/Thomas


Date: Tue, 21 Dec 1999 16:47:30 +0100 (CET)
From: "Thorsten A. Knieling" <knieling at hrz.tu-darmstadt dot de>
Subject: AFS and QPOPPER

Hallo,

has anybody uses qpopper with AFS 3.5 Auth (Kerberos V4). i only need the
authentication, no ticket. Compiling the qpopper 3.0 b 36 with AFS-Libraries
does, but the qpopper hangs at authentication.

Thanks,
 Thorsten

Thorsten A. Knieling
Darmstadt University of Technology
University Computing Center                                 ////
knieling at hrz.tu-darmstadt dot de                               (@ @)
-------------------------------------------------------oOO--(_)--OOo--------

Date: Tue, 21 Dec 1999 09:53:22 -0800
From: forrie at forrie dot com (Forrest Aldrich)
Subject: Compile Failure with 30.b26

This is on FreeBSD-2.2.8:


gcc -c -I.. -I.. -I. -I../mmangle -I../common  -g -freg-struct-return 
-fstrength-reduce -DHAVE_CONFIG_H  -DBSD -DFREEBSD -DUNIX pop_init.c 
-o pop_init.o
In file included from pop_init.c:28:
/usr/include/sys/param.h:45: warning: `BSD' redefined
*Initialization*:1: warning: this is the location of the previous definition
pop_init.c: In function `strdup':
pop_init.c:71: argument `str' doesn't match prototype
/usr/include/string.h:85: prototype declaration
*** Error code 1

Stop.

Note, I also tried removing the -O2, which doesn't have an effect 
here as it's a define.   Fix?



_F

Date: Tue, 21 Dec 1999 13:15:55 -0500 (EST)
From: Vince Vielhaber <vev at michvhf dot com>
Subject: Re: Compile Failure with 30.b26

On Tue, 21 Dec 1999, Forrest Aldrich wrote:

> This is on FreeBSD-2.2.8:
> 
> 
> gcc -c -I.. -I.. -I. -I../mmangle -I../common  -g -freg-struct-return 
> -fstrength-reduce -DHAVE_CONFIG_H  -DBSD -DFREEBSD -DUNIX pop_init.c 
> -o pop_init.o
> In file included from pop_init.c:28:
> /usr/include/sys/param.h:45: warning: `BSD' redefined
> *Initialization*:1: warning: this is the location of the previous definition
> pop_init.c: In function `strdup':
> pop_init.c:71: argument `str' doesn't match prototype
> /usr/include/string.h:85: prototype declaration
> *** Error code 1
> 
> Stop.
> 
> Note, I also tried removing the -O2, which doesn't have an effect 
> here as it's a define.   Fix?

Using the gcc 2.7.2.1 that came with my 2.2.8 I was able to configure
and make without a problem.  Are you using any configure options?  
Different compiler?

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev at michvhf.com    http://www.pop4 dot net
128K ISDN - $24.95/mo or less; 56K Dialup - $17.95/mo or less www.pop4.net
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================




Date: Tue, 21 Dec 1999 12:53:14 -0600
From: "Jonathan C. Detert" <detertj at matc dot edu>
Subject: How to ensure sender uses a valid return address?

Hello Qpopper Users,

My problem is avoiding spam that originates within my organization - my
organization has "computer labs" open to any student.  The problem is that
anyone can send email from a lab pc, using a POP3 client configured to use our
sendmail mailserver as the outgoing mail server, and say they are whoever they
want to be - i.e. they can set their return address to anything they want.

I want a way to ensure that a person can't originate email with a bogus
return-address.

I'm using qpopper v2.52 on solaris with sendmail v8.9.3.

Any ideas?  Thanks.
-- 
Happy Landings,

Jon Detert
Unix System Administrator at Milwaukee Area Technical College
Milwaukee, Wisconsin, USA

Date: Tue, 21 Dec 1999 14:05:40 -0800
Subject: preventing pop locks
From: "Kaley Davis" <kaley at drizzle dot net>

Hi, I'm new to the list, so please forgive me if this is a tediuos FAQ. (I
couldn't find an archive anywhere).

I switched to cucipop from qpoppper-2.53 a few months ago, but switched back
to qpopper-3.0b26 a couple of days ago. I am pretty happy with it,
resource-utilization-wise, but I have one problem. Some users are getting
their inboxes locked up with lingering .userid.pop files.

I had this problem with 2.53, which is why I switched to cucipop, but I am
wondering if I can solve it with the -T flag instead, since it appears to be
a timeout issue. I'm curious what timeout values people have found work
best. So far, I get the problem with -T 60, -T 90 or -T 120. Any guidance on
this issue is greatly appreciated. Thank you!



~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Kaley Davis             kaley at drizzle dot net
Drizzle Internet NW     (206) 447-2702
http://www.drizzle.com  (800) 378-7405


Date: Tue, 21 Dec 1999 14:46:33 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: How to ensure sender uses a valid return address?

At 12:53 PM 12/21/99 -0600, Jonathan C. Detert wrote:
>I want a way to ensure that a person can't originate email with a bogus
>return-address.
>
>I'm using qpopper v2.52 on solaris with sendmail v8.9.3.

This isn't a qpopper issue, but a sendmail one.

I'd suggest trying sendmail 8.10, which I believe supports SMTP AUTH and 
can act as a Message Submission Agent.  What you'd want is to configure 
sendmail to (1) reject anything sent to port 25 from a lab system, and (2) 
require authentication on every submission.  This will force all local 
systems to send mail using the Submit port and also to authenticate 
first.  That way, no matter what the user puts as the From address, you'll 
have their user ID. I haven't played with 8.10 enough to have done this 
myself yet.


Date: Tue, 21 Dec 1999 14:49:44 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: preventing pop locks

At 02:05 PM 12/21/99 -0800, Kaley Davis wrote:

>Some users are getting their inboxes locked up with lingering .userid.pop 
>files.

Please use 3.0b26 and enable trace debugging by adding '--enable-debugging' 
to the './configure' command (be sure to do a 'make clean' first).  Then 
add '-t tracefile' to the inetd line (and send a HUP signal to 
inetd).  This causes additional trace debugging lines to be written to the 
file specified as 'tracefile'.

The additional trace records in 'tracefile' should help diagnose what is 
going on when users have problems with lingering .userid.pop files.  Please 
send in 'tracefile' (or enough of it to show the sessions with problems and 
the prior session for the same userid).

Send the material to <qpopper at qualcomm dot com>, not to the list.

Thank you for your help.



From: Steven Fletcher <stevenf at shellnet.co dot uk>
Subject: RE: Michael Nugents mysql patch
Date: Wed, 22 Dec 1999 11:46:49 -0000

Hiya Thomas;

I have used the patches from http://www.netd.co.za/mysql_mail/ with
success - I haven't tried (even seen) any others yet.

Where are these patches located? I'd be willing to try them out & provide
any assistance that I can.

Steven Fletcher
stevenf at shellnet.co dot uk

> -----Original Message-----
> From: Thomas Egrelius [mailto:thomas at egrelius dot nu]
> Sent: 21 December 1999 14:32
> To: Subscribers of Qpopper
> Subject: Michael Nugents mysql patch
>
>
> Hi!
>
> I'm trying to use the changes Michael Nugent have done to
> qpopper, to use
> a mysql database for authentication, but with no luck.
>
> I've patched all files with his diffs, and compiled ok. The
> binary works
> just fine, but it is still using /etc/passwd for authentication.
>
> I guess I have to modify the Makefile in some way, and I have
> tried to do
> it but with the same result.
>
> Have anyone else used Michaels patches successfully? I guess so... ;-)
> What do I have to do except patching the source files?
>
> /Thomas
>
>


Date: Wed, 22 Dec 1999 20:36:40 +0800 (PHT)
From: "Mark Anthony J. Mercado" <mark at calamba.laguna dot net>
Subject: Q on pop_pass.c

Hello,

I've looked up the 2.53 source and I have a question why do we need to
sleep for sometime before returning a POP_FAILURE?

here is the portion of the code...

    /*  We don't accept connections from users with null passwords */
    /*  Compare the supplied password with the password file entry */
    /*  pw_encrypt() ??                                            */
    if ((pw->pw_passwd == NULL) || (*pw->pw_passwd == '\0') ||
            (strcmp(crypt(p->pop_parm[1], pw->pw_passwd), pw->pw_passwd)
#ifdef HAVE_PW_ENCRYPT
             && strcmp(pw_encrypt(p->pop_parm[1], pw->pw_passwd),
pw->pw_passwd)
#endif
        sleep(SLEEP_SECONDS);
        return (pop_msg(p,POP_FAILURE, pwerrmsg, p->user));
    }


I know it is there for a reason but I do not have any idea. Can somebody
enlighten me on this one?


I'd also like to include the password entered for failed logins in the
log. Is it safe to replace

	return (pop_msg(p,POP_FAILURE, pwerrmsg, p->user));

with this

return (pop_msg(p,POP_FAILURE,
"Incorrect passwd \"%s\" supplied for user \"%s\"", p->pop_parm[1], p->user))



Any help will be greatly appreciated.

-Mark


Date: Wed, 22 Dec 1999 13:44:09 +0100
From: Jesus Cea Avion <jcea at argo dot es>
Subject: Re: Q on pop_pass.c

> I know it is there for a reason but I do not have any idea.

To avoid password guessing. Is not the same to try 100 passwords/second
that a pasword every 3 seconds.

-- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at argo.es http://www.argo dot es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
                                      _/_/    _/_/          _/_/_/_/_/
PGP Key Available at KeyServ   _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz

From: Steven Fletcher <stevenf at shellnet.co dot uk>
Subject: RE: Q on pop_pass.c
Date: Wed, 22 Dec 1999 12:52:39 -0000

Probably to deter people trying to break into accounts. If you get the
password wrong, it'll wait 10 seconds (default) & tell them it's incorrect.
If it's the correct password there could still be a pause of say, 4-5
seconds when the POP3 server is scanning a large maildump file.

It'll basically stop people/programs sending USER/PASS commands constantly
and forcibly breaking into an account.

Steven Fletcher
stevenf at shellnet.co dot uk

> -----Original Message-----
> From: Mark Anthony J. Mercado [mailto:mark at calamba.laguna dot net]
> Sent: 22 December 1999 12:37
> To: Subscribers of Qpopper
> Subject: Q on pop_pass.c
>
>
> Hello,
>
> I've looked up the 2.53 source and I have a question why do we need to
> sleep for sometime before returning a POP_FAILURE?
>
> here is the portion of the code...
>
>     /*  We don't accept connections from users with null passwords */
>     /*  Compare the supplied password with the password file entry */
>     /*  pw_encrypt() ??                                            */
>     if ((pw->pw_passwd == NULL) || (*pw->pw_passwd == '\0') ||
>             (strcmp(crypt(p->pop_parm[1], pw->pw_passwd),
> pw->pw_passwd)
> #ifdef HAVE_PW_ENCRYPT
>              && strcmp(pw_encrypt(p->pop_parm[1], pw->pw_passwd),
> pw->pw_passwd)
> #endif
>         sleep(SLEEP_SECONDS);
>         return (pop_msg(p,POP_FAILURE, pwerrmsg, p->user));
>     }
>
>
> I know it is there for a reason but I do not have any idea.
> Can somebody
> enlighten me on this one?
>
>
> I'd also like to include the password entered for failed logins in the
> log. Is it safe to replace
>
> 	return (pop_msg(p,POP_FAILURE, pwerrmsg, p->user));
>
> with this
>
> return (pop_msg(p,POP_FAILURE,
> "Incorrect passwd \"%s\" supplied for user \"%s\"",
> p->pop_parm[1], p->user))
>
>
>
> Any help will be greatly appreciated.
>
> -Mark
>
>


Date: Wed, 22 Dec 1999 14:21:20 +0100 (CET)
From: robert rotman <rotman at inode dot at>
Subject: RE: Michael Nugents mysql patch

hi,

most mailserver (sendmail, exim...) have build in support for mysql
authentification.
why are the qpopper-mysql patches not integrated in the main sources of
qpopper. these are only a view lines code.

i guess im not the only one who is using the mysql authentification
and spending a lot of hours to adapt the mysql-patches to the new updates
of qpopper.

or are there any other reasons?

robert


Date: Thu, 23 Dec 1999 02:31:39 +1300 (NZDT)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: RE: Michael Nugents mysql patch

On Wed, 22 Dec 1999, robert rotman wrote:

> most mailserver (sendmail, exim...) have build in support for mysql
> authentification.
> why are the qpopper-mysql patches not integrated in the main sources of
> qpopper. these are only a view lines code.
> 
> i guess im not the only one who is using the mysql authentification
> and spending a lot of hours to adapt the mysql-patches to the new updates
> of qpopper.
> 
> or are there any other reasons?

It may sound like a silly question, but has anyone ever put together a
MySQL+sendmail+qpopper howto?

AB


Date: Wed, 22 Dec 1999 14:44:57 +0100 (CET)
From: robert rotman <rotman at inode dot at>
Subject: RE: Michael Nugents mysql patch

On Thu, 23 Dec 1999, Alan Brown wrote:

> On Wed, 22 Dec 1999, robert rotman wrote:
> 
> > most mailserver (sendmail, exim...) have build in support for mysql
> > authentification.
> > why are the qpopper-mysql patches not integrated in the main sources of
> > qpopper. these are only a view lines code.
> > 
> > i guess im not the only one who is using the mysql authentification
> > and spending a lot of hours to adapt the mysql-patches to the new updates
> > of qpopper.
> > 
> > or are there any other reasons?
> 
> It may sound like a silly question, but has anyone ever put together a
> MySQL+sendmail+qpopper howto?
> 

i dont know im using exim but im sure there are also some howto's for
sendmail.
but in my case (exim) the autentification does not affect the the
installation of exim - qpopper in general.
the methode of operating is the same.

but i dont understand. this was not my question.

robert

--
this letter was written on recycled bytes used by deleted mail.



Date: Thu, 23 Dec 1999 02:48:52 +1300 (NZDT)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: RE: Michael Nugents mysql patch

On Wed, 22 Dec 1999, robert rotman wrote:

> i dont know im using exim but im sure there are also some howto's for
> sendmail.

> but i dont understand. this was not my question.

I know. I'm looking to implement mysql queries for both sendmail and
qpopper (among other things).

AB


Date: Wed, 22 Dec 1999 14:24:15 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: RE: Michael Nugents mysql patch

At 11:46 22/12/99 -0000, Steven Fletcher wrote:
>Hiya Thomas;
>
>I have used the patches from http://www.netd.co.za/mysql_mail/ with
>success - I haven't tried (even seen) any others yet.
>
>Where are these patches located? I'd be willing to try them out & provide
>any assistance that I can.

I used the patches you point to above for a few weeks, but they some
deficiencies:
- the patch is quite big (it replaces the whole authentication function)
- it has what I would consider a security flaws: if an account does not
exist it tells the pop client rather than just returning an authentication
failed message; it also logs the plain password in the poplog file
everytime some attempts to connect!
- it doesn't have anything to cope with home directories, which will break
bulletins (unless you ue bull_db) and will break  any system which delivers
into homedirs

it does have the advantage of being configured from a text file in /etc but
I was a bit worried to see that the code that reads the file doesn't
actually check whether it successfully opened the file. This leads to a
core dump if the file isn't there or has bad permissions.

In the end I wrote my own version which just replaces the get_pwnam
function, so everything stays exactly as before, with mysql behaving like a
passwd file. About a week later the "Mail Modernization Project"
http://sendmail.jacked-in.org/ was announced. There is a patch for qpopper,
sendmail and procmail, the qpopper one just replaces get_pwnam (which I
think is the best way to do it.)

I haven't tried it yet, but it all looks promising. The aim is to have all
mail stored in a mysql database (or whatever sql you want) which could be
pretty cool for people running big sites,

Fergal



Date: Wed, 22 Dec 1999 11:12:09 -0500
From: Michael L Vezie <mlv at pobox dot com>
Subject: Re: Q on pop_pass.c

At 08:36 PM 12/22/1999 +0800, Mark Anthony J. Mercado wrote:
>I'd also like to include the password entered for failed logins in the
>log. Is it safe to replace
>
>         return (pop_msg(p,POP_FAILURE, pwerrmsg, p->user));
>
>with this
>
>return (pop_msg(p,POP_FAILURE,
>"Incorrect passwd \"%s\" supplied for user \"%s\"", p->pop_parm[1], p->user))

I wouldn't do that.  Most of the time failed passwords are a simple
matter of a typo.  That would put a cleartext almost-password in
a log file.

Michael


From: Steven Fletcher <stevenf at shellnet.co dot uk>
Subject: RE: Michael Nugents mysql patch
Date: Wed, 22 Dec 1999 16:14:44 -0000

Read your points on this with interest. The database delivery/retrival
support that this set of patches has looks incredibly cool.
Whilst I was more than happy with the performance of the previous set of
patches (indeed it was going to be used in a production ISP at the start of
next year), the DB storage has got to beat flat files any day. :-)

Steven Fletcher
stevenf at shellnet.co dot uk

> In the end I wrote my own version which just replaces the get_pwnam
> function, so everything stays exactly as before, with mysql
> behaving like a
> passwd file. About a week later the "Mail Modernization Project"
> http://sendmail.jacked-in.org/ was announced. There is a
> patch for qpopper,
> sendmail and procmail, the qpopper one just replaces
> get_pwnam (which I
> think is the best way to do it.)
>
> I haven't tried it yet, but it all looks promising. The aim
> is to have all
> mail stored in a mysql database (or whatever sql you want)
> which could be
> pretty cool for people running big sites,
>
> Fergal
>
>
>


Date: Wed, 22 Dec 1999 18:13:20 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: RE: Michael Nugents mysql patch

At 16:14 22/12/99 -0000, Steven Fletcher wrote:
>Read your points on this with interest. The database delivery/retrival
>support that this set of patches has looks incredibly cool.
>Whilst I was more than happy with the performance of the previous set of
>patches (indeed it was going to be used in a production ISP at the start of
>next year), the DB storage has got to beat flat files any day. :-)

I don't think they'll have db storage anywhere near ready by the start of
next year but it could be nice. A simpler approach which allows you to
spread a heavy load over several servers is perdition, a pop/imap proxy
http://www.us.vergenet.net/linux/perdition/

The idea is you have several backend mail servers all running qpopper and
sendmail. Your users are spread across these servers in some fashion. These
machines aren't accessible to the outside world, instead people talk to
your frontend mail servers for mail delivery and collection.

For pop/imap, the client actually talks to perdition, which uses the
supplied username and a database server/file to decide which of the backend
mailservers the account is on, then it simply acts as a tunnel passing data
from the client to the correct backend server.

For smtp, you need to setup sendmail to deliver mail to the correct backend
server for every user, this can be done using rewriting rules or whatever.

There's a paper on that site with benchmarks and details for a few
different backend/frontend server setups, worth reading if you're looking
at a lot of traffic,

Fergal



Date: Wed, 22 Dec 1999 19:15:33 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: dead subscriber?

For the last few weeks (months?) whenever I send mail to this list I get
this from someone, can the list manager remove this guy please, thanks,

Fergal


>Return-Path: <daemon at srv1-for.for.zaz.com dot br>
>Received: from wonka.esatclear.ie (root at wonka.esatclear dot ie [194.145.128.5])
>	by munchkin.esatclear.ie (8.8.7/8.8.7) with ESMTP id SAA01706
>	for <fergal at munchkin.esatclear dot ie>; Wed, 22 Dec 1999 18:17:40 GMT
>Received: from srv1-for.for.zaz.com.br (srv1-for.for.zaz.com.br
[200.239.123.1])
>	by wonka.esatclear.ie (8.9.3/8.9.3) with ESMTP id SAA04635
>	for <fergal at esatclear dot ie>; Wed, 22 Dec 1999 18:15:40 GMT
>Received: (from daemon@localhost)
>	by srv1-for.for.zaz.com.br (8.8.7/8.8.7) id QAA26747
>	for Fergal Daly <fergal at esatclear dot ie>; Wed, 22 Dec 1999 16:19:01 -0200
>Date: Wed, 22 Dec 1999 16:19:01 -0200
>Message-Id: <199912221819.QAA26747 at srv1-for.for.zaz.com dot br>
>From: MAILER-DAEMON <MAILER-DAEMON at zaz.com dot br>
>To: Fergal Daly <fergal at esatclear dot ie>
>Subject: Returned message - mailbox size exceeded
>X-UIDL: opm!!Sa$!!8GC!!Z^@e9
>
>Your message with subject [RE: Michael Nugents mysql patch] was not
delivered to the
>following recipient: [forop0a9].  This recipient's mailbox is full.
>
>Sua mensagem com assunto [RE: Michael Nugents mysql patch] nao foi
entregue ao seguinte
>destinatario: [forop0a9].  A caixa-postal deste destinatario esta' cheia.
>
>


Date: Thu, 23 Dec 1999 13:31:06 +1300 (NZDT)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: RE: Michael Nugents mysql patch

On Wed, 22 Dec 1999, Steven Fletcher wrote:

> Read your points on this with interest. The database delivery/retrival
> support that this set of patches has looks incredibly cool.
> Whilst I was more than happy with the performance of the previous set of
> patches (indeed it was going to be used in a production ISP at the start of
> next year), the DB storage has got to beat flat files any day. :-)

To an extent. 

software.com's Intermail product does this with an Oracle database as
the backend and it's not particularly reliable.

Also, MySQL is optimised for queries, not inserts/deletions. It may not
be the best engine for this kind of task.

AB


From: Kelly Peterson <KellyP at interbaun dot net>
Subject: Mailbox corruption
Date: Thu, 23 Dec 1999 08:53:50 -0700

We're using qpopper version 2.53.  I have noticed that every once in a
while, probably less than one in ten million times, a mailbox will get
corrupted.  The mailboxes get appended to themselves multiple times.  I have
only noticed this with large mail boxes, over 30MB, so far.

Has anyone seen this before?  Is there a fix for it?

Thanks.

Date: Thu, 23 Dec 1999 11:39:28 -0800
Subject: Re: Mailbox corruption
From: "Kaley Davis" <kaley at drizzle dot net>

I've noticed it, too. And more often that one in ten million times. I would
love to know why this happens and how to prevent it.


~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Kaley Davis             kaley at drizzle dot net
Drizzle Internet NW     (206) 447-2702
http://www.drizzle.com  (800) 378-7405


----------
>From: Kelly Peterson <KellyP at interbaun dot net>
>To: qpopper at lists.pensive dot org (Subscribers of Qpopper)
>Subject: Mailbox corruption
>Date: Thu, Dec 23, 1999, 7:53 AM
>

> We're using qpopper version 2.53.  I have noticed that every once in a
> while, probably less than one in ten million times, a mailbox will get
> corrupted.  The mailboxes get appended to themselves multiple times.  I have
> only noticed this with large mail boxes, over 30MB, so far.
>
> Has anyone seen this before?  Is there a fix for it?
>
> Thanks.
> 

Date: Thu, 23 Dec 1999 15:42:33 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Mailbox corruption

This is covered in more detail in the Qpopper FAQ (Frequently Asked 
Questions); see 
<http://www.eudora.com/qpopper/qpop_faq.html#from.lines>.

The short answer is to upgrade to the latest qpopper 3.0beta 
(available at <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>) 
and make sure you do not have procmail 3.10 installed anywhere.


Date: Fri, 24 Dec 1999 12:53:44 -0500
From: Mike Nugent <mnugent at goamerica dot net>
Subject: Mail Modernization Project

	qpopper people:
A few of us has started the "Mail Modernization Project".  The current
focus of the project is to help mail scale up to extrememly large
installations.  As part of the effort, we have patched qpopper to allow
MySQL authentication.  Unfortunatly, you're coding a lot faster than we
are right now :)

Our current patch is for qpopper3.0b23, and I've noticed you're up to
b26 and not even distributing anything under b25 (at least on
ftp.qualcomm.com, is there another preferred frp site?).  I would ask
you to go to our web page and take a look at the patch for consideration
in the main distribution.  It's is fairly small and doesn't add any code
at all unless the user configures the server with --enable-mysqlauth.

The web page is at http://sendmail.jacked-in.org.  Please get back to me
with any coding style differences that are required for the main qpopper
tree.  I can be reached from the webpage or replied to on this email.  I
will also monitor the list as well as I can.

Thanks for a great product.

--
Mike Nugent
MMP Maintainer
mike at illuminatus dot org

Date: Sun, 26 Dec 1999 21:33:14 -0800
From: Listmaster <listmaster at lists.pensive dot org>
Subject: Re: dead subscriber?

At 7:15 PM +0000 12/22/99, Fergal Daly wrote:

>  For the last few weeks (months?) whenever I send mail to this list I get
>  this from someone, can the list manager remove this guy please, thanks,

The problem was that the bounces do not give any clue as to the 
original recipient of the message, nor the route it took.  The 
address in the bounces was not itself subscribed, nor was anyone at 
that host.  The postmaster at that host does not answer email.

The bounces are in direct violation of RFC 821.  They are sent to the 
 From header, instead of the envelope return-path.  They also fail to 
include the original message, which would have trace headers.

So I wrote a program to send special messages to all subscribers 
individually, using unique From and Subject headers.  This revealed 
the culprit, who has been unsubscribed.

Date: Mon, 27 Dec 1999 18:58:52 +1100
From: Jason Oakley <illogix at ihug.com dot au>
Subject: Password incorrect

I have just installed the latest qpopper on a test pc at home, 3.0b26.

If I telnet to the server, I can log in with username/password.
However, if I use the same username and password on the new qpopper, I get 
an error of "Password incorrect".  Yet, if I use the old qpopper that is 
also installed (2.53) I can check mail fine.


Date: Mon, 27 Dec 1999 10:26:44 +0200
From: pestilence <pestilence at netplan dot gr>
Subject: Re: Password incorrect

Check if your system has shadow passwords, if it has recompile qpopper with
shadow support (check the INSTALL file for more options).

Jason Oakley wrote:

> I have just installed the latest qpopper on a test pc at home, 3.0b26.
>
> If I telnet to the server, I can log in with username/password.
> However, if I use the same username and password on the new qpopper, I get
> an error of "Password incorrect".  Yet, if I use the old qpopper that is
> also installed (2.53) I can check mail fine.


Date: Mon, 27 Dec 1999 08:09:30 +0000
From: Rik Schneider <rik at deranged.schneider dot org>
Subject: Re: Password incorrect

Are you using shadowed passwords (/etc/shadow under SysV or linux,
/etc/master.passwd under BSD) if so did you use the  --enable-specialauth
flag when you ran configure.

You may want to look at the FAQ at
http://www.eudora.com/qpopper/qpop_faq.html

Jason Oakley wrote:

> I have just installed the latest qpopper on a test pc at home, 3.0b26.
>
> If I telnet to the server, I can log in with username/password.
> However, if I use the same username and password on the new qpopper, I get
> an error of "Password incorrect".  Yet, if I use the old qpopper that is
> also installed (2.53) I can check mail fine.


Date: Mon, 27 Dec 1999 19:33:02 +1100
From: Jason Oakley <illogix at ihug.com dot au>
Subject: Re: Password incorrect

Thanks to everyone who answered this.. I should learn to read with my eyes 
open.
The reason I didn't is, I have compiled several qpopper versions at work 
where I run Solaris 7 and never have used that switch, yet the server does 
have shadow passwording... strange.

Still, it fixed this problem =:)


At 10:26 27/12/99 +0200, you wrote:
>Check if your system has shadow passwords, if it has recompile qpopper with
>shadow support (check the INSTALL file for more options).
>
>Jason Oakley wrote:
>
> > I have just installed the latest qpopper on a test pc at home, 3.0b26.
> >
> > If I telnet to the server, I can log in with username/password.
> > However, if I use the same username and password on the new qpopper, I get
> > an error of "Password incorrect".  Yet, if I use the old qpopper that is
> > also installed (2.53) I can check mail fine.


Date: Mon, 27 Dec 1999 16:49:36 -0800 (GMT)
From: Balgansuren <balgaa at publica.ub.mng dot net>
Subject: Re: Password incorrect

Hello,

The Qpopper 3.0b26 is normal working on the Solaris 7.

Balgaa

On Mon, 27 Dec 1999, Jason Oakley wrote:

> Thanks to everyone who answered this.. I should learn to read with my eyes 
> open.
> The reason I didn't is, I have compiled several qpopper versions at work 
> where I run Solaris 7 and never have used that switch, yet the server does 
> have shadow passwording... strange.
> 
> Still, it fixed this problem =:)
> 
> 
> At 10:26 27/12/99 +0200, you wrote:
> >Check if your system has shadow passwords, if it has recompile qpopper with
> >shadow support (check the INSTALL file for more options).
> >
> >Jason Oakley wrote:
> >
> > > I have just installed the latest qpopper on a test pc at home, 3.0b26.
> > >
> > > If I telnet to the server, I can log in with username/password.
> > > However, if I use the same username and password on the new qpopper, I get
> > > an error of "Password incorrect".  Yet, if I use the old qpopper that is
> > > also installed (2.53) I can check mail fine.
> 
> 


From: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 27 Dec 1999 01:43:08 -0800
Subject: FYI: Red Hat 5.2/6.1 incompatibility

I just upgraded my system from Red Hat 5.2 to 6.1, and the Qpopper
3.0b26 that I'd recently built stopped working. It would intermittently
refuse a PASS command with "unknown command" and I noticed that it
carried the last character of a 4-letter username into the 4th position
of a subsequent attempt (same connection) with a 3-letter username (ie.
"user abcd" followed by "user xyz" responded with "password required
for xyzd"). I rebuilt the whole thing (bumping the RPM release number)
and "upgraded" to the rebuild and it started working again.

I noted while upgrading the OS that there were several new 5.2
compatibility packages for writing 5.2-compatible programs, so I can
only guess that the C library changed in some way that broke string
handling.

If anyone knows more about this, I'd like to hear about it. I've built
other 3rd party packages besides Qpopper and I'd like to know what
demons are lurking in there.

Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
http://www.215Now.com/



Date: Mon, 27 Dec 1999 12:09:15 +0200
From: pestilence <pestilence at netplan dot gr>
Subject: Re: FYI: Red Hat 5.2/6.1 incompatibility

Lot's have changed since the 5.2 ver of R.H try recompiling qpopper (it
isn't that big) it should work fine after that (at least it works for me).

If you still have problems try rpmfind.net i am sure you will find an rpm
good for your system over there.

Kenneth Porter wrote:

> I just upgraded my system from Red Hat 5.2 to 6.1, and the Qpopper
> 3.0b26 that I'd recently built stopped working. It would intermittently
> refuse a PASS command with "unknown command" and I noticed that it
> carried the last character of a 4-letter username into the 4th position
> of a subsequent attempt (same connection) with a 3-letter username (ie.
> "user abcd" followed by "user xyz" responded with "password required
> for xyzd"). I rebuilt the whole thing (bumping the RPM release number)
> and "upgraded" to the rebuild and it started working again.
>
> I noted while upgrading the OS that there were several new 5.2
> compatibility packages for writing 5.2-compatible programs, so I can
> only guess that the C library changed in some way that broke string
> handling.
>
> If anyone knows more about this, I'd like to hear about it. I've built
> other 3rd party packages besides Qpopper and I'd like to know what
> demons are lurking in there.
>
> Ken
> mailto:shiva at well dot com
> http://www.sewingwitch.com/ken/
> http://www.215Now.com/


From: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 27 Dec 1999 02:19:29 -0800
Subject: Re: FYI: Red Hat 5.2/6.1 incompatibility

On Mon, 27 Dec 1999 12:09:15 +0200, pestilence wrote:

>Lot's have changed since the 5.2 ver of R.H try recompiling qpopper (it
>isn't that big) it should work fine after that (at least it works for me).

That's what I'm saying!

>If you still have problems try rpmfind.net i am sure you will find an rpm
>good for your system over there.

The only RPM's I've seen have been up to 2.53, so I took over the task
of keeping up a package SPEC file for the 3.0 beta. You'll note that
the version listed for 3.0b25 (actually renumbered to 2.99.25 to fit
RPM's model of beta numbering) is my packaging. (The URL is
http://rpmfind.net/linux/RPM/qpopper.html.)

I am currently running 2.99.26-2, which is just b26 rebuilt under RH
6.1.

Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
http://www.215Now.com/