The qpopper list archive ending on 13 Dec 1999
Topics covered in this issue include:
1. Re: qpopper on larger systems...
"Jack Barnett" <jbarnett at axil.netmate dot com>
Tue, 7 Dec 1999 07:22:19 -0600
2. Re: Still having problems with .user.pop
"Jack Barnett" <jbarnett at axil.netmate dot com>
Tue, 7 Dec 1999 07:38:36 -0600
3. Re: Duplication of messages in mailbox
Eric Luyten <eluyten at vub.ac dot be>
Tue, 7 Dec 1999 14:48:18 +0100 (MET)
4. Re: Duplication of messages in mailbox
Eric Luyten <eluyten at vub.ac dot be>
Tue, 7 Dec 1999 14:53:23 +0100 (MET)
5. Re: Still having problems with .user.pop
"Lisa Casey" <lisa at jellico dot com>
Tue, 7 Dec 1999 09:18:09 -0500
6. I want use DBM w/ QPOP
"Fabio de Oliveira" <fabio.oliveira at nttb.com dot br>
Tue, 7 Dec 1999 16:28:02 -0200
7. Re: Duplication of messages in mailbox
Theresa M Peter <theresa at email.uc dot edu>
Tue, 07 Dec 1999 13:34:16 -0500
8. Re: Duplication of messages in mailbox
Qpopper Support <qpopper at qualcomm dot com>
Tue, 7 Dec 1999 12:27:36 -0800
9. Eudora accessing qpopper via a firewall of some sort
"Network Admin [JPeterson]" <jay at qtm dot net>
Tue, 7 Dec 1999 17:01:38 -0500
10. Re: Eudora accessing qpopper via a firewall of some sort
Fergal Daly <fergal at esatclear dot ie>
Tue, 07 Dec 1999 23:43:47 +0000
11. Qpopper and DG/UX
"Nick Sancho" <nick at sonicair dot com>
Tue, 7 Dec 1999 22:33:14 -0700
12. logging on linux
=?iso-8859-1?Q?=22Rieger=2CGötz=22?= <G.Rieger at uniorg dot de>
Wed, 8 Dec 1999 11:02:18 +0100
13. SOS,how can I use different directory for user's .popbull
NightHawk <nighthawk at szonline dot net>
Thu, 09 Dec 1999 17:02:57 +0800
14. Use a HOMEMAILDIR database in qpopper3.23
NightHawk <nighthawk at szonline dot net>
Thu, 09 Dec 1999 18:03:26 +0800
15. accounts not receiving bulletins on purpose
"Miss Parker" <miss.parker at dialcom.com dot pl>
Thu, 9 Dec 1999 11:59:56 +0100
16. spool file ownership
webmaster at plucky dot com
Thu, 09 Dec 1999 16:03:24 -0500
17. spool file ownership
webmaster at plucky dot com
Thu, 09 Dec 1999 16:18:23 -0500
18. MIME and qpoper
"YiHua 'Philip' Sheng" <phsan at cs.siu dot edu>
Thu, 9 Dec 1999 17:18:47 -0600
19. Qpopper 3.0b24 available
Qpopper Support <qpopper at qualcomm dot com>
Thu, 09 Dec 1999 18:26:10 -0800
20. The problem of hangup and difficulty in retrieve MIME messages
NightHawk <nighthawk at szonline dot net>
Fri, 10 Dec 1999 10:56:43 +0800
21. The problem of hangup and difficulty in retrieve MIME messages
NightHawk <nighthawk at szonline dot net>
Fri, 10 Dec 1999 13:50:34 +0800
22. The compiled failing of qpopper3.0b24 on solaris7
NightHawk <nighthawk at szonline dot net>
Fri, 10 Dec 1999 14:27:31 +0800
23. Re: Qpopper 3.0b24 available
"Kenneth Porter" <shiva at well dot com>
Fri, 10 Dec 1999 00:43:40 -0800
24. Quick tip for v3 users
Fergal Daly <fergal at esatclear dot ie>
Fri, 10 Dec 1999 12:44:57 +0000
25. bulletin database
"Miss Parker" <miss.parker at dialcom.com dot pl>
Fri, 10 Dec 1999 14:15:10 +0100
26. Re: The problem of hangup and difficulty in retrieve MIME messages
Alan Brown <alan at manawatu.gen dot nz>
Sat, 11 Dec 1999 03:02:51 +1300 (NZDT)
27. Re: The compiled failing of qpopper3.0b24 on solaris7
Mark Schaal <mark at champ.tstonramp dot com>
Fri, 10 Dec 1999 12:14:03 -0800 (PST)
28. BULLDB
Jason Englander <jason at interl dot net>
Fri, 10 Dec 1999 15:41:57 -0600 (CST)
29.
Phil Savoie <Phil.Savoie at learnix dot ca>
Fri, 10 Dec 1999 16:49:25 -0500
30. Qpopper 3.0b25 available
Qpopper Support <qpopper at qualcomm dot com>
Fri, 10 Dec 1999 16:56:49 -0800
31. I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
"Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Fri, 10 Dec 1999 18:08:01 -0800
32. Re: I really wish there were a Qpopper *ANNOUNCE*-only
Qpopper Support <qpopper at qualcomm dot com>
Sat, 11 Dec 1999 18:14:00 -0800
33. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Terje Bless <link at tss dot no>
Sun, 12 Dec 1999 13:20:29 +0100
34. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
Randall Gellens <randy at pensive dot org>
Sun, 12 Dec 1999 12:37:57 -0800
35. authentication timeouts/disconnects
Bret Buchanan--extra email <bret at ulink dot net>
Sun, 12 Dec 1999 17:38:17 -0800
36. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
Michael L Vezie <mlv at pobox dot com>
Sun, 12 Dec 1999 23:27:13 -0500
37. Re: authentication timeouts/disconnects
Randall Gellens <randy at pensive dot org>
Sun, 12 Dec 1999 21:55:13 -0800
38. scram-md5
Kenichi Okada <okada at opaopa dot org>
Mon, 13 Dec 1999 17:25:55 +0900
39. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
Admin Mailing Lists <mlist at intergrafix dot net>
Mon, 13 Dec 1999 09:24:15 -0500 (EST)
40. RE: I really wish there were a Qpopper *ANNOUNCE*-only mailinglist...
"Network Admin [JPeterson]" <jay at qtm dot net>
Mon, 13 Dec 1999 10:51:58 -0500
41. problem with APOP
"Benito Fernandez Garcia" <befernandez at isdefe dot es>
Mon, 13 Dec 1999 17:40:48 +0100
42. Re: problem with APOP
Qpopper Support <qpopper at qualcomm dot com>
Mon, 13 Dec 1999 11:41:21 -0800
43. Compile Errors - version 3.0b24
Bob Johnson <rjohnson at ubcinc dot com>
Mon, 13 Dec 1999 13:14:40 -0800
44. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Dan Harkless <dan-qpopper at dilvish.speed dot net>
Mon, 13 Dec 1999 13:56:49 -0800
45. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Dan Harkless <dan-qpopper at dilvish.speed dot net>
Mon, 13 Dec 1999 13:59:12 -0800
46. Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
"Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Mon, 13 Dec 1999 13:57:51 -0800
47. qpopper faq conributions
hypnose at t-online dot de (guenter wessling)
Tue, 14 Dec 1999 01:45:06 +0100
48. Re: qpopper faq conributions
"Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Mon, 13 Dec 1999 17:01:28 -0800
49. Re: qpopper faq conributions
Leonard Hermens <Leonard.Hermens at rcity dot com>
Mon, 13 Dec 1999 17:26:24 -0800
50. Re: qpopper faq conributions
Qpopper Support <qpopper at qualcomm dot com>
Mon, 13 Dec 1999 17:28:15 -0800
From: "Jack Barnett" <jbarnett at axil.netmate dot com>
Subject: Re: qpopper on larger systems...
Date: Tue, 7 Dec 1999 07:22:19 -0600
Would running qpopper in stand alone mode help any?
I thought that was him (Larry Wall) but wasn't sure.
----- Original Message -----
From: Tomasz Orzechowski <tmo at apk dot net>
To: Jack Barnett <jbarnett at axil.netmate dot com>
Cc: robert rotman <rotman at inode dot at>; Subscribers of Qpopper
<qpopper at lists.pensive dot org>
Sent: Monday, December 06, 1999 3:34 PM
Subject: Re: qpopper on larger systems...
> This might be overkill, his problem is with too many instances of popper
> being spawned from inetd, not (yet, anyhow) from lack of system resources.
>
> There is an option to put into inetd.conf which defines how many instances
> of a given server can be spawned in any given 5 minutes. If he increases
> that appropriately he will see if he needs to redistribute the load, and
> even then there is server-mode and other things like striped metadevices
> he can do before distributing the load between multiple pop frontends.
>
> BTW, your quote is from Larry Wall, of PERL fame :)
> And the motto of the language, as well.
>
> Jack Barnett wrote on Mon, Dec 06, 1999 at 03:00:20PM -0600:i
> > Would there be any way to 'split' your mail servers up? Have like 3-4
mail
> > servers, and 'split' up your users in some logical manner, have say the
> > class of 99 on server x.domain.org and the class of 00 on the
y.domain.org
> > and the class of 01 on z.domain.org.
> >
> > Then if a student from the class of 99 want to download his email, he
would
> > point his pop3 server address to x.domain.org, etc, etc..
> >
> > I bet you could play with Bind and Sendmail and get every mail sent to
> > user at domain.org forwarded to the correct user at x dot domain dot org (or where
ever
> > his mail might live). If you couldn't do it on the DNS and SMTP level
you
> > could always write a quick Perl script that would add the line
> >
> > user at domain.org:user at x dot domain dot org
> >
> > to your /etc/alaises file on the domain.org machine (provided you are
> > running Sendmail). In fact you could add the script to be called on the
> > backend of your add user script for your system..
> >
> > I see 2 problems with this though.
> >
> > 1) you have to get manegment to allocate money for extra hardware (which
can
> > be tough to impossiable depending on where you work :)
> >
> > 2) The sysadmin at the company (probably you) would have to maintain 3-4
> > more times the hardware, 3-4 times more times the software, take 3-4
times
> > longer to do security audits, then there is patch upgrades, etc, etc...
> >
> > This way would and could work, but I am not saying it is the best way...
> >
> > Jack
> >
> > "There is more than one way to do things"
> > -- Larry Way (??)
> >
> >
> > ----- Original Message -----
> > From: robert rotman <rotman at inode dot at>
> > To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
> > Sent: Monday, December 06, 1999 12:59 PM
> > Subject: qpopper on larger systems...
> >
> >
> > > hy all,
> > >
> > > i've installed qpopper3.018 on my server with approx. 20.000
connections
> > > /day.
> > > i've the message "pop3/tcp server failing (looping), service
terminated"
> > > very often and so i installed xinetd.
> > >
> > > now the xinetd blocks this connection an tis message did not apaer any
> > > more.
> > >
> > > but the connection of our users are rejected wicht is not the goal
because
> > > it is planned increase the number of users on this server.
> > >
> > > As i read in the doc's multiple servers which are NFS mounted - are
not
> > > recomanded.
> > >
> > >
> > > so what should i do?
> > >
> > >
> > > robert
> > >
> > >
> > > ---
> > > di. robert rotman inode.graz
> > > phone -> ++43-(0)316 811451 ++43-(0)316 811451 <- fax
> > > rotman at inode.at http://www.graz.inode dot at/
> > > --
> > > this letter was written on recycled bytes used by deleted mail.
> > >
> > >
> > >
>
> --
> Tomasz Orzechowski tmo at apk dot net
> APK.net systems administration team TO630
>
>
From: "Jack Barnett" <jbarnett at axil.netmate dot com>
Subject: Re: Still having problems with .user.pop
Date: Tue, 7 Dec 1999 07:38:36 -0600
Lisa,
That is odd, you /var slice is not even close to being full. It doesn't
look like a problem with qpopper, but some type of permission problem with
your /var/mail directory.
Usually when that happens, it is either wrong permissions on the directory,
to much mail with not enough quota, the disk being mounted wrong(no write
access), or no space left on device. We checked most of those things and I
am not exactly sure what is holding up write permissions on /var/mail...
A normal user should be able to run the command `touch /var/mail/test.file`
without errors, if you could figure out how to get that to work, then
qpopper shouldn't have any more problems either..
I am sorry, but I am not exactly sure why your /var/mail directory doesn't
accept write access. You would probably be best checking with the qpopper
list or any FreeBSD list available to see /why/ a normal user can't write to
the /var/mail directory.
Jack
----- Original Message -----
From: Lisa Casey <lisa at jellico dot com>
To: Jack Barnett <jbarnett at axil.netmate dot com>
Cc: <qpopper at lists.pensive dot org>
Sent: Monday, December 06, 1999 2:49 PM
Subject: Re: Still having problems with .user.pop
> Hi Jack,
>
> I agree, this is peculiar...
>
> >The /var slice is mounted with read / write premissions, that shouldn't
be
> a
> >problem, quota's isn't the problem.
> >
> >The thing that looks strange to me though, is that a normal user should
be
> >able to `touch /var/mail/test.file` since /var/mail should have read and
> >write permissions by /ALL/ the users. Hrm, strange... run the command
> >
> >`df -ak`
> >
> >or if that doesn't work try
> >
> >`df`
>
>
>
> i2000# df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/wd0s1a 39647 26579 9897 73% /
> /dev/wd0s1f 1427527 745677 567648 57% /usr
> /dev/wd0s1e 19815 3398 14832 19% /var
> procfs 4 4 0 100% /proc
>
>
> >
> >Basically what this does, it outputs disk information, what is mounted
> >where, how much is in use, how much is free, etc, etc.
> >
> >It will say something like "avalib" or "free" for free space, go down a
> >little ways and line the "avalib" colums up with the "/var" row and that
> >will show you how much free space is left on the device, if it is %100
> >completely full, ever single byte in use, than that would be causeing the
> >touch error and the pop3 error. I don't think this is the case, but it
is
> >worth checking since this isn't the typical problem :)
>
>
> looks to me like the var slice is only at 19% of capacity, if I am reading
> this right.
>
>
> >
> >Does sending email to your users work fine or do you get an error that is
> >simplair to the pop3 error, like "premission denied" when you send?
>
>
> I can send E-mail to users fine. I sent a test message to my manager and
saw
> the size of his /var/mail/username file increase accordingly. But I can't
> retrieve the mail using Outlook Express with his account info set up, I
get
> the same errors as I do when I try to access my E-mail account on the Free
> BSD box. And according to the error messages on the console, all users are
> getting these errors.
>
>
> >Are you running qpopper from inetd or stand alone?
>
>
> It's run from inetd:
>
> # example entry for the optional pop3 server
> #
> pop3 stream tcp nowait root /usr/local/libexec/popper
> popper
> #
>
> Thanks,
>
> Lisa Casey
>
>
>
>
>
Subject: Re: Duplication of messages in mailbox
Date: Tue, 7 Dec 1999 14:48:18 +0100 (MET)
From: Eric Luyten <eluyten at vub.ac dot be>
> We've found that the mails in our user mailbox are duplicated
> after checking or deleting messages in some occassions. We are
> using qpopper 2.53 (server-mode) in Solaris 2.5.1.
We're running qpopper 2.53 in server mode on Solaris 7 and have
been bitten by the same problem. Quite anoying when *several*
mailboxes go over 100 MB and occupancy of your mail spool goes
way over 90% ...
Have you ever seen 320 concurrent 'popper' instances ? :-\
I reported the problem to Qpopper support when they asked for
reports on instances of spool file corruption.
> Is there any tunnings or methods to avoid this from happening ?
I was hoping the improved I/O error diagnostics of Qpopper3.0
can provide us with more information about what goes wrong.
Eric Luyten, Computing Centre VUB/ULB.
Subject: Re: Duplication of messages in mailbox
Date: Tue, 7 Dec 1999 14:53:23 +0100 (MET)
From: Eric Luyten <eluyten at vub.ac dot be>
> But this is not the qpopper's problem.
We're certainly not ruling that out either.
> That can be:
> 1. sendmail's configuration problem:
> eliminate the local mailer's flag "m" & change "A=mail.local ..."
> to "A=mail ..."
Errrrm... That's the flag allowing the delivery agents to carry out
deliveries to multiple recipients on the local system.
We had two occasions of mailbox duplication today where there was
no (new) message delivery done...
There is, however, *always* a "-ERR /var/mail/poptemp/.xxxx.pop lock
busy! Is another session active? (11)" popper error to be seen in
the logs at around the time of mailbox duplication but not all of
those errors result in a duplication.
Eric Luyten, Computing Centre VUB/ULB.
From: "Lisa Casey" <lisa at jellico dot com>
Subject: Re: Still having problems with .user.pop
Date: Tue, 7 Dec 1999 09:18:09 -0500
Hi Jack,
I fixed it. Thanks for all of your help, I learned a lot from you and you
did point me in the right direction. The problem turned out to be not the
permissions on /var/mail, but the permissions on /var itself
which were:
drwx-----T 20 root wheel 512 May 18 1999 var
I changed these to:
drwxrwxrwt 20 root wheel 512 May 18 1999 var
and popper works. Do you (or anyone) see any problem with leaving the /var
permissions set like this? I do have the sticky bit set...
Lisa
-----Original Message-----
From: Jack Barnett <jbarnett at axil.netmate dot com>
To: Lisa Casey <lisa at jellico dot com>
Cc: qpopper at lists.pensive.org <qpopper at lists dot pensive dot org>
Date: Tuesday, December 07, 1999 8:37 AM
Subject: Re: Still having problems with .user.pop
>
>Lisa,
>
>That is odd, you /var slice is not even close to being full. It doesn't
>look like a problem with qpopper, but some type of permission problem with
>your /var/mail directory.
>
>Usually when that happens, it is either wrong permissions on the directory,
>to much mail with not enough quota, the disk being mounted wrong(no write
>access), or no space left on device. We checked most of those things and I
>am not exactly sure what is holding up write permissions on /var/mail...
>
>A normal user should be able to run the command `touch /var/mail/test.file`
>without errors, if you could figure out how to get that to work, then
>qpopper shouldn't have any more problems either..
>
>I am sorry, but I am not exactly sure why your /var/mail directory doesn't
>accept write access. You would probably be best checking with the qpopper
>list or any FreeBSD list available to see /why/ a normal user can't write
to
>the /var/mail directory.
>
>Jack
>
>
>
>
>----- Original Message -----
>From: Lisa Casey <lisa at jellico dot com>
>To: Jack Barnett <jbarnett at axil.netmate dot com>
>Cc: <qpopper at lists.pensive dot org>
>Sent: Monday, December 06, 1999 2:49 PM
>Subject: Re: Still having problems with .user.pop
>
>
>> Hi Jack,
>>
>> I agree, this is peculiar...
>>
>> >The /var slice is mounted with read / write premissions, that shouldn't
>be
>> a
>> >problem, quota's isn't the problem.
>> >
>> >The thing that looks strange to me though, is that a normal user should
>be
>> >able to `touch /var/mail/test.file` since /var/mail should have read and
>> >write permissions by /ALL/ the users. Hrm, strange... run the command
>> >
>> >`df -ak`
>> >
>> >or if that doesn't work try
>> >
>> >`df`
>>
>>
>>
>> i2000# df
>> Filesystem 1K-blocks Used Avail Capacity Mounted on
>> /dev/wd0s1a 39647 26579 9897 73% /
>> /dev/wd0s1f 1427527 745677 567648 57% /usr
>> /dev/wd0s1e 19815 3398 14832 19% /var
>> procfs 4 4 0 100% /proc
>>
>>
>> >
>> >Basically what this does, it outputs disk information, what is mounted
>> >where, how much is in use, how much is free, etc, etc.
>> >
>> >It will say something like "avalib" or "free" for free space, go down a
>> >little ways and line the "avalib" colums up with the "/var" row and that
>> >will show you how much free space is left on the device, if it is %100
>> >completely full, ever single byte in use, than that would be causeing
the
>> >touch error and the pop3 error. I don't think this is the case, but it
>is
>> >worth checking since this isn't the typical problem :)
>>
>>
>> looks to me like the var slice is only at 19% of capacity, if I am
reading
>> this right.
>>
>>
>> >
>> >Does sending email to your users work fine or do you get an error that
is
>> >simplair to the pop3 error, like "premission denied" when you send?
>>
>>
>> I can send E-mail to users fine. I sent a test message to my manager and
>saw
>> the size of his /var/mail/username file increase accordingly. But I can't
>> retrieve the mail using Outlook Express with his account info set up, I
>get
>> the same errors as I do when I try to access my E-mail account on the
Free
>> BSD box. And according to the error messages on the console, all users
are
>> getting these errors.
>>
>>
>> >Are you running qpopper from inetd or stand alone?
>>
>>
>> It's run from inetd:
>>
>> # example entry for the optional pop3 server
>> #
>> pop3 stream tcp nowait root /usr/local/libexec/popper
>> popper
>> #
>>
>> Thanks,
>>
>> Lisa Casey
>>
>>
>>
>>
>>
>
>
>
From: "Fabio de Oliveira" <fabio.oliveira at nttb.com dot br>
Subject: I want use DBM w/ QPOP
Date: Tue, 7 Dec 1999 16:28:02 -0200
Dear all,
We're running qpopper 2.53 in server mode on Solaris 2.6 and I would like to
use to authentication one DBM file. So I dont want use the etc/passwd file.
If someone use this method, please help me?
I know that is need to change the source code. But i dont know where in
code?
Thank you in advance for any help.
Best Regards,
-------------------------------------------------
Fabio Oliveira
Sao Paulo - Brasil
-------------------------------------------------
Date: Tue, 07 Dec 1999 13:34:16 -0500
From: Theresa M Peter <theresa at email.uc dot edu>
Subject: Re: Duplication of messages in mailbox
I have a hard time believing that the problem is not with Qpopper and with
sendmail or the delivery agent. This is what I have found.
1.) The duplication of messages occurs sporadically, and not always
with the delivery of new mail.
2.) The duplication of messages is usually a handful at a time, and not
the whole mbox, though we have seen that occur.
3.) The "-ERR /var/mail/poptemp/.xxxx.pop lock busy! Is another session
active? (11)" popper error can usually be found in the log files around the
times that message duplication occurs
4.) I haven't seen this occur with any other client besides Eudora Pro.
5.) I did not see any changes in the headers of the messages from the
original messages to the duplicated messages, but Eudora still downloaded
the duplicates. *****What does Eudora look for to decide whether or not it
has already downloaded the message?*****
6.) If you set Eudora to remove messages fom the server after X amount
of days it will skip over those messages that have been duplicated and keep
them on the server. (Manual intervention is required and that isn't
acceptable with 44,000 users, thankfully it is sporadic and far between)
7.) The problem usually occurs when a users mbox ~10 MB
8.) Our sendmail configuration does not have that flag present.
FYI
Server side I am running Solaris 2.6, Sendmail 8.9.2, Qpopper 2.4 and
Procmail 3.10
Client side we are finding that this occurs with users who are running
Eudora Pro 4.x (though I am not going to eliminate any of the the other
clients or versions)
Unfortunately or fortunately, depending on how you want to look at it, I
was experiencing this problem this past weekend and was able to put these
observations together, along with the questions and problems our users
brought to me. I have since cleaned out my mailbox, manually, and cannot
seem to reproduce this phenomenon as we like to call it. I do have a copy
of the mbox file to put into a 'test' account and do more testing on but I
haven't gotten around to that yet.
Any ideas or thoughts on the cause and solution would be greatly appreciated.
Theresa Peter
University of Cincinnati
Bearcat Online Office
At 11:59 AM 12/7/99 +0800, you wrote:
>I have the same problem before.
>But this is not the qpopper's problem.
>That can be:
>1. sendmail's configuration problem:
>eliminate the local mailer's flag "m" & change "A=mail.local ..."
>to "A=mail ..."
>
>2.some version of Pmail donot work fine.(Bug?)Just upgrade the Pmail or
>using other MUA!
>
>Hope this help!
>Gary
>
>> Dear all,
>>
>> We've found that the mails in our user mailbox are duplicated
>> after checking or deleting messages in some occassions. We are
>> using qpopper 2.53 (server-mode) in Solaris 2.5.1. Is there any
>> tunnings or methods to avoid this from happening ?
>>
>> Regards,
>>
>> Tom Sit
>>
>>
>>
>>
>>
Date: Tue, 7 Dec 1999 12:27:36 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Duplication of messages in mailbox
At 1:34 PM -0500 12/7/99, Theresa M Peter wrote:
> I have a hard time believing that the problem is not with Qpopper and with
> sendmail or the delivery agent. This is what I have found.
>
> 1.) The duplication of messages occurs sporadically, and not always
> with the delivery of new mail.
>
> 2.) The duplication of messages is usually a handful at a time, and not
> the whole mbox, though we have seen that occur.
>
> 3.) The "-ERR /var/mail/poptemp/.xxxx.pop lock busy! Is another session
> active? (11)" popper error can usually be found in the log files around the
> times that message duplication occurs
To me, this implies that qpopper died while updating the spool.
Have you tried qpopper3.0? It fixed a number of cases where qpopper
could die and not clean up.
>
> 4.) I haven't seen this occur with any other client besides Eudora Pro.
That's very odd. It would be interesting to get a Eudora Pro log of
a session with a corrupted spool. You can do this by editing the
Eudora.INI file and adding the following lines before or after the
[Settings] section:
[Debug]
LogLevel=127
Then quit and relaunch Eudora.
>
> 5.) I did not see any changes in the headers of the messages from the
> original messages to the duplicated messages, but Eudora still downloaded
> the duplicates. *****What does Eudora look for to decide whether or not it
> has already downloaded the message?*****
Eudora uses the UID to know which messages it has seen.
>
> 6.) If you set Eudora to remove messages fom the server after X amount
> of days it will skip over those messages that have been duplicated and keep
> them on the server. (Manual intervention is required and that isn't
> acceptable with 44,000 users, thankfully it is sporadic and far between)
Perhaps because the duplicated messages appear to be new. If you
tell Eudora to delete the messages, does it? (You can right-click on
the server status and select 'delete from server'.)
>
> 7.) The problem usually occurs when a users mbox ~10 MB
>
> 8.) Our sendmail configuration does not have that flag present.
>
> FYI
>
> Server side I am running Solaris 2.6, Sendmail 8.9.2, Qpopper 2.4 and
> Procmail 3.10
> Client side we are finding that this occurs with users who are running
> Eudora Pro 4.x (though I am not going to eliminate any of the the other
> clients or versions)
I'd suggest upgrading to qpopper 3.0 (or at least 2.53) and the
latest procmail -- reports have linked procmail 3.10 to spool
corruption problems. Qpopper versions below 2.5 are vulnerable to
buffer overflows and should NOT be used.
> Unfortunately or fortunately, depending on how you want to look at it, I
> was experiencing this problem this past weekend and was able to put these
> observations together, along with the questions and problems our users
> brought to me. I have since cleaned out my mailbox, manually, and cannot
> seem to reproduce this phenomenon as we like to call it. I do have a copy
> of the mbox file to put into a 'test' account and do more testing on but I
> haven't gotten around to that yet.
>
From: "Network Admin [JPeterson]" <jay at qtm dot net>
Subject: Eudora accessing qpopper via a firewall of some sort
Date: Tue, 7 Dec 1999 17:01:38 -0500
I have a customer who is accessing our qpopper3.0b23 via some sort of
firewall (wingate I think) and he is hitting the poplog as
"fbattista@fbattista" he cannot change anything in his settings or it wont
work, we broke his ability to do this when we upgraded to the latest beta
from the modified 3.0b that was vulnerable to the overrun rootshell attack..
I had gotten a mod from this mailing list to make qpopper ignore anything
including and after the @ sign if it was in the username, can someone help
me get this mod again so I can apply it to 3.0b23?
Thank You
Date: Tue, 07 Dec 1999 23:43:47 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: Eudora accessing qpopper via a firewall of some sort
At 17:01 07/12/99 -0500, Network Admin [JPeterson] wrote:
>I have a customer who is accessing our qpopper3.0b23 via some sort of
>firewall (wingate I think) and he is hitting the poplog as
>"fbattista@fbattista" he cannot change anything in his settings or it wont
>work, we broke his ability to do this when we upgraded to the latest beta
>from the modified 3.0b that was vulnerable to the overrun rootshell attack..
>I had gotten a mod from this mailing list to make qpopper ignore anything
>including and after the @ sign if it was in the username, can someone help
>me get this mod again so I can apply it to 3.0b23?
have a look at http://www.esatclear.ie/~fergal/qpopper, I just made a quick
patch for you again, I didn't even try to compile it. Also it's a patch
against 3b18 but it should probably work on b23 you can apply it by cd'ing
into the popper src directory and type
patch -p1 < remove_domain.patch
I take no responsibilty for any bad things that happen when you use this!
but it's exactly the same as the last patch,
Fergal
From: "Nick Sancho" <nick at sonicair dot com>
Subject: Qpopper and DG/UX
Date: Tue, 7 Dec 1999 22:33:14 -0700
Has anyone been able to compile qpopper on an m88k DG/UX platform?
Specifically R4.11 MU06?
From: =?iso-8859-1?Q?=22Rieger=2CGötz=22?= <G.Rieger at uniorg dot de>
Subject: logging on linux
Date: Wed, 8 Dec 1999 11:02:18 +0100
hello there,
i am running qpopper 2.53 on a suse linux box. everything works fine, except
that i cant change the logging behaviour.
until now, every pop-request is logged in /var/log/messages and
/var/log/mail. i would like to have the qpopper-logging only in
/var/log/poplog or so because we are running some software which is polling
the popd very often.
in the documentation it says that the default logging on bsd syslog goes to
local0. so i tried this in the syslog.conf, but nothing changed.
can anybody help me with that?
i would be very grateful, because i have already spent hours on that. ;-)
regards,
goetz
Date: Thu, 09 Dec 1999 17:02:57 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: SOS,how can I use different directory for user's .popbull
I am using qpopper3.0b23 on solars7 now!
I am desired to use the bulletin function of qpopper3.0b23,
but my users have a same home directory! I think that if
the user's .popbull file could relocate in another directory(
such as: /var/spool/bulletins/popbull), and use its name as
.username.popbull, etc. But I don't know how to configure my
qpopper server.
I will greatly
appreciate anyone for his good ideas
Best Regard!
Date: Thu, 09 Dec 1999 18:03:26 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: Use a HOMEMAILDIR database in qpopper3.23
I want to class my all users into a different groups( such
group1, gourp2, group3,group4,etc.)!
every groups use a different mail spool,such as:
group1 /var/mail/group1
group2 /var/mail/group2
group3 /var/mail/group3
....
I make a file (such as homemaildir) define the mail spool
directory. In the message spool directoy, the user's mail
spool is same as old format.I does't know how to modify
the qpopper server!
Can anyone give me a patch to modify the qpopper3.0b23?
I wil greatly appreciate his help!
Best regard!
From: "Miss Parker" <miss.parker at dialcom.com dot pl>
Subject: accounts not receiving bulletins on purpose
Date: Thu, 9 Dec 1999 11:59:56 +0100
is this possible to configure qpopper to have list of
special users that won't receive any bulletins
(but the rest of them should)
thanks
-----------
Miss Parker
From: webmaster at plucky dot com
Date: Thu, 09 Dec 1999 16:03:24 -0500
Subject: spool file ownership
I am running qpopper 2.53 in server mode using
/usr/spool/poptemp as my spool location. I am
using quotas to limit user's mailbox size to 5MB.
My problem is that if the user has more than
2.5MB in their mailbox, they receive the Overquota
error when they attempt to pop their mail. Is
there a way to specify one specific owner for
every user's temp mail drop? I'd like to make it
so that the temp files are owned by a user that
I can assign a larger quota to, like the user
poptemp or something like that.
I have to be able to keep all user's quotas at 5MB,
but still allow them to pop and delete their mail
even if their box is full.
Thanks,
Brad
From: webmaster at plucky dot com
Date: Thu, 09 Dec 1999 16:18:23 -0500
Subject: spool file ownership
I am running qpopper 2.53 in server mode using
/usr/spool/poptemp as my spool location. I am
using quotas to limit user's mailbox size to 5MB.
My problem is that if the user has more than
2.5MB in their mailbox, they receive the Overquota
error when they attempt to pop their mail. Is
there a way to specify one specific owner for
every user's temp mail drop? I'd like to make it
so that the temp files are owned by a user that
I can assign a larger quota to, like the user
poptemp or something like that.
I have to be able to keep all user's quotas at 5MB,
but still allow them to pop and delete their mail
even if their box is full.
Thanks,
Brad
From: "YiHua 'Philip' Sheng" <phsan at cs.siu dot edu>
Subject: MIME and qpoper
Date: Thu, 9 Dec 1999 17:18:47 -0600
I am wondering whether POP3 server has relationship with MIME, what version
of MIME is supported by qpopper?
Thanks.
Philip
Date: Thu, 09 Dec 1999 18:26:10 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Qpopper 3.0b24 available
Qpopper 3.0b24 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Changes from 3.0b23 to 3.0b24
-----------------------------
1. Try and ensure SEEK_SET and friends always defined.
2. Condition genpath() and maillock() debugging on -d or -t.
3. Fix SEEK_END not defined on IRIX.
4. Fix make errors on SunOS4.
5. Fix typo (SYS_MAILOCK instead of SYS_MAILLOCK).
6. Fixed crash if message line exceeded 1024 bytes.
7. Problems building on SunOS4.
Date: Fri, 10 Dec 1999 10:56:43 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: The problem of hangup and difficulty in retrieve MIME messages
hello,all
I have been suffering from the problem of hangup
and difficulty in retrieving MIME messages !!!!
When my users retriev their MIME message (attached
binary file), the speed of download message will become
very slow and often hangup ! because of this problem,
I get a lot of complain. I don;t know what's wrong!!!
PLease help me! Any your advice will be greatly
appreciated
Date: Fri, 10 Dec 1999 13:50:34 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: The problem of hangup and difficulty in retrieve MIME messages
hello,all
I am using qpopper3.0b18~3.0b24 on solaris2.6~ solaris7.
My install step as following:
1.configure --enable-servermode --enable-mangle --enable-auto-delete
--enable-specialauth
2.make
the inetd.conf file:
pop3 stream tcp nowait.800 root /usr/lib/popper popper -R -T 240
I have been suffering from the problem of hangup
and difficulty in retrieving MIME messages !!!!
When my users retriev their MIME message (attached
binary file), the speed of download message will become
very slow and often hangup ! because of this problem,
I get a lot of complain. I don;t know what's wrong!!!
PLease help me! Any your advice will be greatly
appreciated
Date: Fri, 10 Dec 1999 14:27:31 +0800
From: NightHawk <nighthawk at szonline dot net>
Subject: The compiled failing of qpopper3.0b24 on solaris7
Hello,all:
when I install qpopper3.0b24 on solaris7 as follow steps,
it always display the following error message!!!! I don't know
what's wrong? the qpopper3.0b20 can be
correctly compiled and installed
The install step:
1. ./configure --enable-servermode --enable-mangle
--enable-auto-delete \
--enable-log-login --enable-specialauth
2. make
The error message:
ar -rlibcommon.a flock.o maillock.o genpath.o logit.o
ar: flock.o not in archive format
ar: bcommon.a taken as mandatory 'posname' with keys 'abi'
*** Error code 1
make: Fatal error: Command failed for target `libcommon.a'
Current working directory /tmp/qpopper3.0b24/common
*** Error code 1
make: Fatal error: Command failed for target `common_library'
Current working directory /qpopper3.0b24/popper
*** Error code 1
make: Fatal error: Command failed for target `popper_server'
Can you help me ?!
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 10 Dec 1999 00:43:40 -0800
Subject: Re: Qpopper 3.0b24 available
On Thu, 09 Dec 1999 18:26:10 -0800, Qpopper Support wrote:
>Qpopper 3.0b24 is available at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
My current RPM spec file works fine with this if you global-replace
"23" with "24". (Don't really need to change the occurrence in the
changelog comment, though. There should be 4 other occurrences that
need to be changed.) I've uploaded the edited copy to
http://www.sewingwitch.com/ken/qpopper2.99.24.spec.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
http://www.215Now.com/
Date: Fri, 10 Dec 1999 12:44:57 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Quick tip for v3 users
Maybe you all knew this, but in case you didn't. qpopper 3 is set to
compile with debugging info built in (I'm talking about the -g switch on
gcc) and this makes the executable about 4 times larger than it needs to be
on my linux machine. I ran
strip popper
to remove the debug symbols, I got an executable that was 100k instead of
400k. I honestly don't know if this will improve performance any, but it
doesn't hurt.
By the way, if any of the folks from qualcomm are reading this, is there
any chance you might run the source files through indent or something like
that for the next release, the formatting seems to be fairly inconsistent,
some lines are indented with tabs, some with spaces and some with a
mixture, thanks,
Fergal
From: "Miss Parker" <miss.parker at dialcom.com dot pl>
Subject: bulletin database
Date: Fri, 10 Dec 1999 14:15:10 +0100
QPopper 3 INSTALL file constains something like:
"[...] A bulletin
database can be used to track the bulletins
instead of the users home directory.
This feature is enabled with -DBULLDB during
compilation. -DBULLDB requires two blank files
including the name of BULLDIR/bulldb.pag and
the creation of BULLDIR/bulldb.dir."
ok, but where should I include the -DBULLDB option
for the succesful compilation?
thanks
-----------
Miss Parker
Date: Sat, 11 Dec 1999 03:02:51 +1300 (NZDT)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: The problem of hangup and difficulty in retrieve MIME messages
MIME has nothing to do with popper, as this is part of the message body.
The usualy casuse of this kind of behaviour is software flow
control/hardware flow control clashes or lousy phone lines causing the
modem to dump the call.
** Lousy phone lines are 99% caused by faulty phones. Unplug
all other devices and see if the problem continues before blaming the
telco.
On Fri, 10 Dec 1999, NightHawk wrote:
> hello,all
> I have been suffering from the problem of hangup
> and difficulty in retrieving MIME messages !!!!
> When my users retriev their MIME message (attached
> binary file), the speed of download message will become
> very slow and often hangup ! because of this problem,
> I get a lot of complain. I don;t know what's wrong!!!
> PLease help me! Any your advice will be greatly
> appreciated
>
>
"It is the responsibility of the private sector to adopt, implement, and
enforce measures to deter and prevent the improper use of unsolicited
commercial electonic mail" - HR3888 Sec 201
From: Mark Schaal <mark at champ.tstonramp dot com>
Subject: Re: The compiled failing of qpopper3.0b24 on solaris7
Date: Fri, 10 Dec 1999 12:14:03 -0800 (PST)
There's a mistake in the common/Makefile.in. You can edit that file
and reconfigure or just the common/Makefile and remove the extra
dollar sign after the AR_FLAG.
libcommon.a: ${OBJS}
ar ${AR_FLAG}$ libcommon.a ${OBJS} ${RANLIB_CMD}
should be
libcommon.a: ${OBJS}
ar ${AR_FLAG} libcommon.a ${OBJS} ${RANLIB_CMD}
Hope that helps,
Mark
>
> Hello,all:
> when I install qpopper3.0b24 on solaris7 as follow steps,
> it always display the following error message!!!! I don't know
> what's wrong? the qpopper3.0b20 can be
> correctly compiled and installed
> The install step:
> 1. ./configure --enable-servermode --enable-mangle
> --enable-auto-delete \
> --enable-log-login --enable-specialauth
> 2. make
> The error message:
>
> ar -rlibcommon.a flock.o maillock.o genpath.o logit.o
> ar: flock.o not in archive format
> ar: bcommon.a taken as mandatory 'posname' with keys 'abi'
> *** Error code 1
> make: Fatal error: Command failed for target `libcommon.a'
> Current working directory /tmp/qpopper3.0b24/common
> *** Error code 1
> make: Fatal error: Command failed for target `common_library'
> Current working directory /qpopper3.0b24/popper
> *** Error code 1
> make: Fatal error: Command failed for target `popper_server'
>
> Can you help me ?!
>
--
Mark J. Schaal Phone: (909) 620-7724
TST On Ramp Fax: (909) 620-8174
System Administrator E-Mail: mark at tstonramp dot com
Date: Fri, 10 Dec 1999 15:41:57 -0600 (CST)
From: Jason Englander <jason at interl dot net>
Subject: BULLDB
I know when you use BULLDB, if they're not in the db, but they do have a
.popbull it will be read into the db. I'd like it greatly in a future
version of popper if it would also remove the old .popbull file.
jm2c,
Jason
--
Jason Englander <jason at interl dot net>
Systems Administrator - InterLink L.C.
Date: Fri, 10 Dec 1999 16:49:25 -0500
From: Phil Savoie <Phil.Savoie at learnix dot ca>
Subject:
Date: Fri, 10 Dec 1999 16:56:49 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Qpopper 3.0b25 available
Qpopper 3.0b25 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Changes from 3.0b24 to 3.0b25
-----------------------------
1. Fix typo in common/Makefile.in
Subject: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
From: "Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Date: Fri, 10 Dec 1999 18:08:01 -0800
Hello. I am in charge of network security where I work, so I make it a
practice to be on the "announce" mailing lists for all the daemons we have
installed.
Unfortunately Qpopper doesn't have a separate "-announce" list, just the
main discussion list. The discussion list is a great resource if you're
having problems with Qpopper, but if you're not, the relatively high traffic
is a bit of a nuisance. I'm only interested in news of new versions and
security exploits discovered in old ones.
I'd like to humbly suggest that Eudora set up a separate list,
qpopper-announce at lists.pensive dot org.
I know the stock answer for any Qpopper suggestions is "sorry, this is free
software -- we can't devote many resources to it", but I don't think setting
up another list, putting a link to it on your web page, and Cc'ing it when
announcing new versions would be that big a burden.
For a popular network daemon with a history of root exploits like Qpopper,
setting up such a list is the Right Thing To Do (TM).
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-qpopper at dilvish.speed dot net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
Date: Sat, 11 Dec 1999 18:14:00 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only
At 6:08 PM -0800 12/10/99, Dan Harkless wrote:
>Hello. I am in charge of network security where I work, so I make it a
>practice to be on the "announce" mailing lists for all the daemons we have
>installed.
>
>Unfortunately Qpopper doesn't have a separate "-announce" list, just the
>main discussion list. The discussion list is a great resource if you're
>having problems with Qpopper, but if you're not, the relatively high traffic
>is a bit of a nuisance. I'm only interested in news of new versions and
>security exploits discovered in old ones.
>
>I'd like to humbly suggest that Eudora set up a separate list,
>qpopper-announce at lists.pensive dot org.
This has actually been on my to-do list for a week or so, now. It
occurred to me that it would be nice to have a very low-traffic list
that people could sign up for to know when new versions are available.
However, this would probably be an official Qualcomm list, so it
would be @qualcomm.com -- the public qpopper discussion list is an
unofficial one, hosted at pensive.org.
Date: Sun, 12 Dec 1999 13:20:29 +0100
From: Terje Bless <link at tss dot no>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
On 11.12.99 at 18:14, Qpopper Support <qpopper at qualcomm dot com> wrote:
>This has actually been on my to-do list for a week or so, now. It
>occurred to me that it would be nice to have a very low-traffic list that
>people could sign up for to know when new versions are available.
Not just new versions, I hope. There are a bunch of other things it would
be usefull to know about. Unofficial patches, "how I fixed foo"-stories,
and security problems spring to mind.
>However, this would probably be an official Qualcomm list, so it would be
>@qualcomm.com -- the public qpopper discussion list is an unofficial one,
>hosted at pensive.org.
Why the distinction? I see no real reason why both lists can't be hosted at
the same place unless there are politics involved here. Hosting both lists
at the same place makes filtering sooo much easier and should make
administration a bit saner.
Date: Sun, 12 Dec 1999 12:37:57 -0800
From: Randall Gellens <randy at pensive dot org>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
> >This has actually been on my to-do list for a week or so, now. It
>>occurred to me that it would be nice to have a very low-traffic list that
>>people could sign up for to know when new versions are available.
>
> Not just new versions, I hope. There are a bunch of other things it would
> be usefull to know about. Unofficial patches, "how I fixed foo"-stories,
> and security problems spring to mind.
I think the point of an announce-only list is *very* low traffic. To
me, that means new versions and security announcements. The list
would be on-way only. Qualcomm announces something. Any discussion
takes place on the public discussion list.
IMHO, patches, experience with "foo" situations, and so forth, are
exactly what the public Qpopper discussion list is for.
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
It is the business of the future to be dangerous.
From: Bret Buchanan--extra email <bret at ulink dot net>
Subject: authentication timeouts/disconnects
Date: Sun, 12 Dec 1999 17:38:17 -0800
okay, heres the problem, whenever I try to authenticate into my pop3 server
(running qpopper 3.0b25 with shadowpasswd, server_mode and bulletin support)
and try and check a user thats not there, or even if the user is there and
fails to authenticate the password it waits like 10 seconds, then closes the
connection saying the password is bad. I looked though the INSTALL file and
couldn't find any thing that would either reduce the time it took to
authenticate or not disconnect me after it fails to authenticate. I was
wondering if any of you knew a way to fix that.
Thanks,
Bret Buchanan
sys admin
Date: Sun, 12 Dec 1999 23:27:13 -0500
From: Michael L Vezie <mlv at pobox dot com>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
At 01:20 PM 12/12/1999 +0100, Terje Bless wrote:
> >This has actually been on my to-do list for a week or so, now. It
> >occurred to me that it would be nice to have a very low-traffic list that
> >people could sign up for to know when new versions are available.
>
>Not just new versions, I hope. There are a bunch of other things it would
>be usefull to know about. Unofficial patches, "how I fixed foo"-stories,
>and security problems spring to mind.
I agree with Randall Gellens; other general information belongs in
this list. I subscribed to this list hoping it was an announce list.
I delete most of the mail I see here, and would much rather just
get important things ("final 3.0 released" (but I'd settle for new
beta announcements!)).
> >However, this would probably be an official Qualcomm list, so it would be
> >@qualcomm.com -- the public qpopper discussion list is an unofficial one,
> >hosted at pensive.org.
>
>Why the distinction? I see no real reason why both lists can't be hosted at
>the same place unless there are politics involved here. Hosting both lists
>at the same place makes filtering sooo much easier and should make
>administration a bit saner.
Nice thing about it being at quallcom.com is that there's no question
regarding the source. If I forwarded mail from this list to someone who
had never heard about it, they might see pensive.org and guess the list
to be unofficial. But if it came from qpopper-announce at qualcomm dot com,
there would be no reason to question the authenticity.
Michael
Date: Sun, 12 Dec 1999 21:55:13 -0800
From: Randall Gellens <randy at pensive dot org>
Subject: Re: authentication timeouts/disconnects
At 5:38 PM -0800 12/12/99, Bret Buchanan--extra email wrote:
> okay, heres the problem, whenever I try to authenticate into my pop3 server
> (running qpopper 3.0b25 with shadowpasswd, server_mode and bulletin support)
> and try and check a user thats not there, or even if the user is there and
> fails to authenticate the password it waits like 10 seconds, then closes the
> connection saying the password is bad. I looked though the INSTALL file and
> couldn't find any thing that would either reduce the time it took to
> authenticate or not disconnect me after it fails to authenticate. I was
> wondering if any of you knew a way to fix that.
That's very deliberate. It makes it take longer for someone doing a
brute-force break-in attempt. There's a define called SLEEP_SECONDS
at the top of pop_pass.c which specifies how long the delay is (ten
seconds).
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
Procedures! Of course, that's what you'd use with a *sophisticated*
machine like this. Procedures. --'Ceaser Smith' in _Hot_Millions_
Date: Mon, 13 Dec 1999 17:25:55 +0900
From: Kenichi Okada <okada at opaopa dot org>
Subject: scram-md5
I test scram-md5.
# scramauth -init
% scramauth
pass
# scramauth -list
username: SCRAM
But I cannot success an authentication.
auth scram-md5 AGtva2FkYQA8c2drOG1vZ***i5zYXNsQHNhbm1hPg==
+ 30M9AOal5+ECAAQAUVBPUEBoYW1hY2hpAK***E/BR9SBGiBPNVsWrQL725KN
AQAAANr6XRC7GK34u***RPP3Kr4=
-ERR Unknown command: "aqaaanr6xrc7gk34u***rpp3kr4=".
Fri Dec 10 01:10:41 1999 [8603] (v3.0b23) Servicing request from "localhost" at ???
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] +OK QPOP (version 3.0b23) at server starting. <8603 dot 944755841@server>
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] Received (61): "auth scram-md5 AGtva2FkYQA8c2drOG1vZ****i5zYXNsQHNhbm1hPg=="
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] SCRAM-MD5 authentication Base64: AGtva2FkYQA8c2drOG1vZ****i5zYXNsQHNhbm1hPg==
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] SCRAM-MD5 "username"
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] Received (30): "AQAAANr6XRC7GK34u***RPP3Kr4="
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] username@localhost: -ERR Unknown command: "aqaaanr6xrc7gk34u***rpp3kr4=".
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] EOF from username at ??? (localhost)
Fri Dec 10 01:10:41 1999
Fri Dec 10 01:10:41 1999 [8603] username@localhost: -ERR POP EOF or I/O error (0)
Why?
Thank you.
--
Kenichi Okada
mailto:okada at opaopa dot org
Date: Mon, 13 Dec 1999 09:24:15 -0500 (EST)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing
> Hello. I am in charge of network security where I work, so I make it a
> practice to be on the "announce" mailing lists for all the daemons we have
> installed.
>
> Unfortunately Qpopper doesn't have a separate "-announce" list, just the
> main discussion list. The discussion list is a great resource if you're
> having problems with Qpopper, but if you're not, the relatively high traffic
> is a bit of a nuisance. I'm only interested in news of new versions and
> security exploits discovered in old ones.
>
while I agree with your suggestion of an announce list, I'd just like to
point out the discussion list is anything but "relatively high traffic"
go subscribe to the linux-kernel list *grin*
-Cygnus
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
admin at intergrafix dot net Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://cygnus.ncohafmuta.com http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
From: "Network Admin [JPeterson]" <jay at qtm dot net>
Subject: RE: I really wish there were a Qpopper *ANNOUNCE*-only mailinglist...
Date: Mon, 13 Dec 1999 10:51:58 -0500
> > Hello. I am in charge of network security where I work, so I make it a
> > practice to be on the "announce" mailing lists for all the
> > daemons we have
> > installed.
> >
> > Unfortunately Qpopper doesn't have a separate "-announce" list, just the
> > main discussion list. The discussion list is a great resource if you're
> > having problems with Qpopper, but if you're not, the relatively
> > high traffic
> > is a bit of a nuisance. I'm only interested in news of new versions and
> > security exploits discovered in old ones.
> >
>
> while I agree with your suggestion of an announce list, I'd just like to
> point out the discussion list is anything but "relatively high traffic"
> go subscribe to the linux-kernel list *grin*
>
> -Cygnus
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Yeah, or the FreeBSD-questions list .. geez.. =) I think that aside from the
Magick IRC services list, this one is the lowest traffic one that I sift
through on a regular basis <grin>
-JPeterson
From: "Benito Fernandez Garcia" <befernandez at isdefe dot es>
Date: Mon, 13 Dec 1999 17:40:48 +0100
Subject: problem with APOP
Hello friends, I' ve just installed qpopper2.53 in RH6.1 and everything go well
except the authenticate method APOP.
I configured qpopper with next compiler definitions
./configure --enable-specialauth --enable-apop=/etc/pop.auth
--with-popuid=pop
Later, with the user root, I set up popauth as ......
-rwsr-xr-x pop root /usr/local/bin/popauth
and typed popauth -init (then the database was initializated)
-rw-------- pop root /etc/pop.auth
Finally, I tried popauth -user <anyuser> and then .....
here is my problem,
First popauth ask me for the new password but at the end, in the screen appear
the next message
"popauth: /etc/pop.auth: unable to open POP authorization DB"
I think that the problem is about rights, therefore i put pop.auth rwxrwxrwx
but this doesn't work.
Anyone can help me?
Thanks a lot in advanced and regards.
Date: Mon, 13 Dec 1999 11:41:21 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: problem with APOP
At 05:40 PM 12/13/99 +0100, Benito Fernandez Garcia wrote:
>First popauth ask me for the new password but at the end, in the screen appear
>the next message
>
> "popauth: /etc/pop.auth: unable to open POP authorization DB"
This is fixed in 3.0; try 3.0b25.
From: Bob Johnson <rjohnson at ubcinc dot com>
Subject: Compile Errors - version 3.0b24
Date: Mon, 13 Dec 1999 13:14:40 -0800
System: IBM RS6000 running AIX 4.1.
Compiler: GNU version 'gcc version 2.95.1 19990816 (release)'
Compile Errors:
1) <====================>
gcc -c -I.. -I.. -I. -I../mmangle -I../common -g -O2 =
-fpcc-struct-return -fstrength-reduce -DHAVE_CONFIG_H -DAIX -DUNIX =
pop_send.c -o pop_send.o
pop_send.c: In function `pop_send':
pop_send.c:259: warning: passing arg 1 of `header_mucker_init' from =
incompatible pointer type
2) <====================>
gcc -c -I.. -I. -I.. -I../popper -g -O2 -fpcc-struct-return =
-fstrength-reduce -DHAVE_CONFIG_H -DAIX -DUNIX mime.c -o mime.o
mime.c: In function `MimeCteB64Process':
mime.c:365: warning: comparison is always false due to limited range of =
data type
3) <====================>
gcc -c -I.. -I. -I.. -I../popper -g -O2 -fpcc-struct-return =
-fstrength-reduce -DHAVE_CONFIG_H -DAIX -DUNIX mangle.c -o mangle.o
mangle.c: In function `MangleMapper':
mangle.c:263: warning: comparison is always false due to limited range =
of data type
Corrections:
1) Haven't figured out yet.
2) Change type for 'B64->shift' to an 'int' from 'char'; line 274 of =
mmangle/mime.h
3) Change operator from '==' to '='; line 263 of mmangle/mangle.c
Question:
Are the changes I've made correct; nothing to worry about or will be =
changed in a latter version?
Information Notes:
a) I have not had a chance to test this yet, but I don't like =
'warnings'.
b) I compiled version 3.0b22 on a 386-Red Hat Linux system. I got =
warning (1), but did not get (2) or (3).
c) I have version 3.0b15 running on an AIX 4.1 machine. The only =
problems I have noted are with 'something' MS Office97 doesn't like =
about some messages. I typically have to delete the message for the =
rest of the mail to be read. The error states you don't have enough =
memory to read the mail, but this is a BS message. If I find out what =
this relates to, I will send a follow up.
From: Dan Harkless <dan-qpopper at dilvish.speed dot net>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Date: Mon, 13 Dec 1999 13:56:49 -0800
Qpopper Support <qpopper at qualcomm dot com> writes:
> >Hello. I am in charge of network security where I work, so I make it a
> >practice to be on the "announce" mailing lists for all the daemons we have
> >installed.
> >
> >Unfortunately Qpopper doesn't have a separate "-announce" list, just the
> >main discussion list. The discussion list is a great resource if you're
> >having problems with Qpopper, but if you're not, the relatively high traffic
> >is a bit of a nuisance. I'm only interested in news of new versions and
> >security exploits discovered in old ones.
> >
> >I'd like to humbly suggest that Eudora set up a separate list,
> >qpopper-announce at lists.pensive dot org.
>
> This has actually been on my to-do list for a week or so, now. It
> occurred to me that it would be nice to have a very low-traffic list
> that people could sign up for to know when new versions are available.
>
> However, this would probably be an official Qualcomm list, so it
> would be @qualcomm.com -- the public qpopper discussion list is an
> unofficial one, hosted at pensive.org.
Great! I only suggested the lists.pensive.org one because I thought it
might be easier to set up, and I didn't want "don't have the resources to
set it up" to be an excuse not to do so (since that's Qualcomm's official
policy on Qpopper).
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-qpopper at dilvish.speed dot net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
From: Dan Harkless <dan-qpopper at dilvish.speed dot net>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Date: Mon, 13 Dec 1999 13:59:12 -0800
Admin Mailing Lists <mlist at intergrafix dot net> writes:
> > Hello. I am in charge of network security where I work, so I make it a
> > practice to be on the "announce" mailing lists for all the daemons we have
> > installed.
> >
> > Unfortunately Qpopper doesn't have a separate "-announce" list, just the
> > main discussion list. The discussion list is a great resource if you're
> > having problems with Qpopper, but if you're not, the relatively high traffic
> > is a bit of a nuisance. I'm only interested in news of new versions and
> > security exploits discovered in old ones.
>
> while I agree with your suggestion of an announce list, I'd just like to
> point out the discussion list is anything but "relatively high traffic"
> go subscribe to the linux-kernel list *grin*
I didn't say it was a "high traffic" list. I said it was a "*relatively*
high traffic" list. Relative to the other lists I'm on, and certainly
relative to an announce-only list, it's high traffic.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-qpopper at dilvish.speed dot net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
From: "Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Subject: Re: I really wish there were a Qpopper *ANNOUNCE*-only mailing list...
Date: Mon, 13 Dec 1999 13:57:51 -0800
Randall Gellens <randy at pensive dot org> writes:
> > >This has actually been on my to-do list for a week or so, now. It
> >>occurred to me that it would be nice to have a very low-traffic list that
> >>people could sign up for to know when new versions are available.
> >
> > Not just new versions, I hope. There are a bunch of other things it would
> > be usefull to know about. Unofficial patches, "how I fixed foo"-stories,
> > and security problems spring to mind.
>
> I think the point of an announce-only list is *very* low traffic. To
> me, that means new versions and security announcements. The list
> would be on-way only. Qualcomm announces something. Any discussion
> takes place on the public discussion list.
>
> IMHO, patches, experience with "foo" situations, and so forth, are
> exactly what the public Qpopper discussion list is for.
I agree 100%.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-qpopper at dilvish.speed dot net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
Date: Tue, 14 Dec 1999 01:45:06 +0100
Subject: qpopper faq conributions
From: hypnose at t-online dot de (guenter wessling)
>Sender: dan at dilvish.speed dot net - wrote:
>Great! I only suggested the lists.pensive.org one because I thought it
might be easier
>to set up, and I didn't want "don't have the resources to set it up" to be
an excuse
>not to do so (since that's Qualcomm's official policy on Qpopper).
>-Dan Harkless-
Dear Dan, hi everyone,
I hear these complaints sometimes - but why ?
qpopper is a great program, running fine, stable, with nice features.
Support with even trivial problems is great. Thank you again, Mr. G.
Development is continued, 30b25 is close-to-incredible.
How long did it take to fix the buffer overflow ? 2 days ?
What do you expect ? 24-hours-0800-hotline ?
I really think that we should appreciate the job done by support here.
Forgive me, but this list should come back to qpopper info.
A little less "announce-list" discussion, and a little more like "I did
this and that, and that way it runs fine" - that would be nice.
Maybe there is need for some additions to the faq ?
For example:
-------------------
Q: If I try popauth with 2.5.3, I get the message "unable to open
authorization database". What happened ?
A: With qpopper 2.5.3 on 386-dld-distrib with 3.0.36 - and maybe on other
systems, add here -, popauth simply does not work as is. That´s it.
If you want APOP, take 30b25. That really works with popauth.
If you don´t need APOP, you can use 2.5.3. Without popauth 2.5.3 works all
right.
Q: When I want bulletins, how do I compile/configure ? Do I have to specify
--enable-bulletins plus modify the Makefile after ./configure ?
A: In the first place, you don not have to worry about the Makefile. Just do
./configure --enable-bulletins=/var/spool/bulls
if you want /var/spool/bulls as bulletin directory.
All necessary changes will be made for you. The generated Makefiles do NOT
have to be changed. Just do "make".
As a result, every user will have a ".popbull"-file in her home directory
(/home/user).
This file contains the number of the last bulletin that has been sent to
this user. Number in this case means the running number of the bulletin:
lets say, 24 bulletins of the form "0001.bull" to "0024.bull" have been
placed before the user enters your system. This new user will then receive
the number of bulletins you specified at "#define NEWBULLCNT" in
"popper.h". Default is "1". So the user will receive the one last bulletin.
And .popbull will contain the number "24".
If NEWBULLCNT is set to "3", the user will receive the three latest
bulletins (22,23,24 in this case). And .popbull will still contain "24".
Of course, the ".popbull"-file is created the first time the user receives
mail.
Q: I had my bulletins running fine. Then, for some reason, the system got
mixed up and now, some users receive bulletins, some don´t. What happened=
?
A: Very often, system administrators change accounts of their users: maybe
UID is changed (for quota reason, f.e.), maybe the user is set up a second
time. This happens.
And it will drive popper crazy - of course.
The easiest way to get bulletins running again for the user is deleting
.popbull in her home directory (/home/user). Next time the user receives
mail, .popbull is re-created, and things should run fine.
If that does not work, you can delete the user, delete the users /home
directory, delete the users mail spool and set the user up completely new
again. THEN qpopper-bulletins will definitely work again - but maybe the
user will shoot you....
To get around this shooting problem, you can create a BULLDB - database
instead of having .popbull - files in every user´s home directory.
This BULLDB database is initiated by a change in the Makefile. With qpopper
2.5.3, just follow the instructions in INSTALL. Add -DBULLDIR.... to the
"defs" line.
With qpopper 30b25, it seems a little more complicated, since there are
more than one Makefiles (Makefile; /popper/Makefile; /common/Makefile...).
It is suggested to change "config.h" BEFORE doing ./configure instead of
changing Makefiles AFTER ./configure.
(((Here should be the modification of config.h; however - I do not know how
and what to change.. :( this is for you all, then...)))
When running popper after all, the BULLDB (in /var/spool/bulls, in our
example) contains a list of the users and the corresponding number of the
user´s latest received bulletin. If then something gets whizzydizzy, just
delete BULLDB (when system is in pause, of course). BULLDB will be
re-created all new, when any user receives mail. You may want to inform the
users that bulletins have been reorganized, and all is fine.
--------------------
Don´t you people think that this kind of contributions would be greatly
appreciated by everyone ? Every time, a problem is solved, we might be able
to put one more question to the faq. Do I ask for too much ?
If I said anything wrong in the above Q/A´s, please correct me.
Thanks for your patience,
Guenter
-- If I seem offensive, please imagine me smiling.
If that does not help, smile yourself --
:) have a nice day - alles Gute - :)
Guenter Wessling (hypnose at t-online dot de)
- Westfalian Society of Hypnosis -
- Westfaelische Gesellschaft fuer Hypnose -
48165 Muenster, Germany
fax: 0049 (0)2501 27273=09
http://home.t-online.de/home/hypnose
From: "Dan Harkless" <dan-qpopper at dilvish.speed dot net>
Subject: Re: qpopper faq conributions
Date: Mon, 13 Dec 1999 17:01:28 -0800
hypnose at t-online dot de (guenter wessling) writes:
> > Great! I only suggested the lists.pensive.org one because I thought it
> > might be easier to set up, and I didn't want "don't have the resources
> > to set it up" to be an excuse not to do so (since that's Qualcomm's
> > official policy on Qpopper).
>
> Dear Dan, hi everyone,
> I hear these complaints sometimes - but why ?
>
> qpopper is a great program, running fine, stable, with nice features.
> Support with even trivial problems is great. Thank you again, Mr. G.
>
> Development is continued, 30b25 is close-to-incredible.
> How long did it take to fix the buffer overflow ? 2 days ?
>
> What do you expect ? 24-hours-0800-hotline ?
>
> I really think that we should appreciate the job done by support here.
Who said I was complaining? I totally understand Qualcomm's position in
having such a policy, and being cognizant of it, I sometimes word
suggestions to avoid a knee-jerk "sorry, no company resources available to
do that". If that wasn't the stated policy of the company, I wouldn't
tip-toe as much when making suggestions.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-qpopper at dilvish.speed dot net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
Date: Mon, 13 Dec 1999 17:26:24 -0800
From: Leonard Hermens <Leonard.Hermens at rcity dot com>
Subject: Re: qpopper faq conributions
> >Sender: dan at dilvish.speed dot net - wrote:
>>Great! I only suggested the lists.pensive.org one because I thought it
>might be easier
>>to set up, and I didn't want "don't have the resources to set it up" to be
>an excuse
>>not to do so (since that's Qualcomm's official policy on Qpopper).
>>-Dan Harkless-
>
>Dear Dan, hi everyone,
>I hear these complaints sometimes - but why ?
It didn't sound like a complaint to me.
-- Leonard
Date: Mon, 13 Dec 1999 17:28:15 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: qpopper faq conributions
At 01:45 AM 12/14/99 +0100, guenter wessling wrote:
>Q: If I try popauth with 2.5.3, I get the message "unable to open
>authorization database". What happened ?
Thanks for your FAQ suggestions. This particular question is in the FAQ,
but when the web site was overhauled the qpopper pages were accidently set
back to an earlier version lacking this question and many other recent
additions. We're working on getting this fixed.
If anyone has suggestions for FAQ additions, documentation clarifications,
patches, etc., please send them to qpopper at qualcomm dot com. It's always
appreciated.