The qpopper list archive ending on 15 Oct 2001
Topics covered in this issue include:
1. Re: SYS/TEMP: Unable to open Bulletin database
Randall Gellens <randy at qualcomm dot com>
Wed, 3 Oct 2001 14:40:55 -0700
2. RE: SYS/TEMP: Unable to open Bulletin database
"Justin Ainsworth" <jda at sunset dot net>
Wed, 3 Oct 2001 16:49:31 -0700
3. Alternate- and stls-Port seems to be the same.
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Thu, 4 Oct 2001 13:12:37 +0000
4. support for Tru64 Unix 5.1
"Doryce E . Moore" <demoore at ccsalpha3.nrl.navy dot mil>
Thu, 4 Oct 2001 10:49:52 -0400
5. encrypted password
Cecilia Cabrera <ccabrera at scooby.uba dot ar>
Thu, 4 Oct 2001 16:35:48 +0000 (/etc/localtime)
6. Re: encrypted password
Clifton Royston <cliftonr at lava dot net>
Thu, 4 Oct 2001 13:57:39 -1000
7. Re: Alternate- and stls-Port seems to be the same.
"Kenneth Porter" <shiva at well dot com>
Thu, 04 Oct 2001 19:00:03 -0700
8. qpopper 4.0.3
"Sascha Reimann" <reimann at haar-systemberatung dot de>
Fri, 05 Oct 2001 10:55:00 +0200
9. Re: qpopper 4.0.3
"Kenneth Porter" <shiva at well dot com>
Fri, 05 Oct 2001 02:11:14 -0700
10. Re: qpopper 4.0.3
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Fri, 5 Oct 2001 11:11:01 +0000
11. Re: qpopper 4.0.3
"Sascha Reimann" <reimann at haar-systemberatung dot de>
Fri, 05 Oct 2001 11:45:37 +0200
12. Re: Alternate- and stls-Port seems to be the same.
Randall Gellens <randy at qualcomm dot com>
Fri, 5 Oct 2001 10:26:34 -0700
13. Re: support for Tru64 Unix 5.1
Randall Gellens <randy at qualcomm dot com>
Fri, 5 Oct 2001 10:27:58 -0700
14. RE: SYS/TEMP: Unable to open Bulletin database
Randall Gellens <randy at qualcomm dot com>
Fri, 5 Oct 2001 10:24:23 -0700
15. Re: Alternate- and stls-Port seems to be the same.
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Mon, 8 Oct 2001 10:37:48 +0000
16. "alternate-port", "stls" and MS-Outlook
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Mon, 8 Oct 2001 12:29:21 +0000
17. Re: support for Tru64 Unix 5.1
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Mon, 8 Oct 2001 12:50:44 +0000
18. Problem With QPopper
"Matthew Hale" <mhale at semo dot net>
Mon, 8 Oct 2001 13:24:03 -0500
19. Re: "alternate-port", "stls" and MS-Outlook
Randall Gellens <randy at qualcomm dot com>
Mon, 8 Oct 2001 15:19:34 -0700
20. Re: Problem With QPopper
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 9 Oct 2001 14:21:33 +0000
21. Implementing user quotas
Sean Kelly <sean.kelly at the-web-works.co dot uk>
Tue, 09 Oct 2001 14:28:19 +0100
22. Re: Implementing user quotas
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 9 Oct 2001 15:56:23 +0000
23. RE: Implementing user quotas
Sean Kelly <sean.kelly at the-web-works.co dot uk>
Tue, 09 Oct 2001 14:55:16 +0100
24. Re: Implementing user quotas
Butch Kemper <kemper at tstar dot net>
Tue, 09 Oct 2001 08:53:36 -0500
25. Re: "alternate-port", "stls" and MS-Outlook
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 9 Oct 2001 17:56:15 +0000
26. specify user homedir for temp-drop-dir
Ted George <ted at kcnet dot com>
Tue, 09 Oct 2001 11:36:21 -0500
27. Re: "alternate-port", "stls" and MS-Outlook
Gustavo Viscaino <g_viscaino at yahoo dot com>
Tue, 9 Oct 2001 11:02:47 -0700 (PDT)
28. Re: Problem With QPopper
Randall Gellens <randy at qualcomm dot com>
Tue, 9 Oct 2001 12:29:01 -0700
29. Re: Implementing user quotas
Clifton Royston <cliftonr at lava dot net>
Tue, 9 Oct 2001 10:24:06 -1000
30. Re: "alternate-port", "stls" and MS-Outlook
Randall Gellens <randy at qualcomm dot com>
Tue, 9 Oct 2001 16:23:19 -0700
31. what are these lock files
PM WONG <pmwong at power25t.hkbu.edu dot hk>
Wed, 10 Oct 2001 13:53:22 +0800 (HKT)
32. Re: Implementing user quotas
peter.allen at moon-light.co dot uk
Wed, 10 Oct 2001 12:25:29 +0100
33. Implementing user quotas / Expiring Email
Steve Perrault <sperraul at mnsi dot net>
Wed, 10 Oct 2001 08:25:35 -0400
34. Re: Implementing user quotas / Expiring Email
Gregory Hicks <ghicks at cadence dot com>
Wed, 10 Oct 2001 05:47:17 -0700 (PDT)
35. Re: Implementing user quotas
Clifton Royston <cliftonr at lava dot net>
Wed, 10 Oct 2001 08:25:04 -1000
36. Re: Implementing user quotas / Expiring Email
Clifton Royston <cliftonr at lava dot net>
Wed, 10 Oct 2001 08:33:44 -1000
37. Re: Implementing user quotas / Expiring Email
Randall Gellens <randy at qualcomm dot com>
Wed, 10 Oct 2001 11:41:43 -0700
38. Re: what are these lock files
Randall Gellens <randy at qualcomm dot com>
Wed, 10 Oct 2001 11:38:45 -0700
39. Re: Implementing user quotas / Expiring Email
Peter Evans <peter at gol dot com>
Thu, 11 Oct 2001 08:55:12 +0900
40. Re: what are these lock files
PM WONG <pmwong at power25t.hkbu.edu dot hk>
Thu, 11 Oct 2001 09:34:20 +0800 (HKT)
41. Re: Implementing user quotas / Expiring Email
Ted George <ted at kcnet dot com>
Thu, 11 Oct 2001 07:56:18 -0500
42. Re: Implementing user quotas / Expiring Email
"Michael Kolos" <michael at colba dot net>
Thu, 11 Oct 2001 10:52:57 -0400
43. Re: Implementing user quotas / Expiring Email
Randall Gellens <randy at qualcomm dot com>
Thu, 11 Oct 2001 16:59:26 -0700
44. Re: Implementing user quotas / Expiring Email
Clifton Royston <cliftonr at lava dot net>
Thu, 11 Oct 2001 14:42:32 -1000
45. Re: Implementing user quotas / Expiring Email
Randall Gellens <randy at qualcomm dot com>
Thu, 11 Oct 2001 17:53:19 -0700
46. Re: Implementing user quotas / Expiring Email
"Michael Kolos" <michael at colba dot net>
Fri, 12 Oct 2001 14:17:00 -0400
47. Quota Flush / Update Problem.
Syed Hasan Masood <hmasood at super.net dot pk>
Sat, 13 Oct 2001 00:39:34 +0500
48. QPOPPER3 and QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Mon, 15 Oct 2001 12:50:37 -0600
49. getting qpopper to run initially on RH7.1
Stephen Bopple <steve at bopple dot org>
Mon, 15 Oct 2001 14:47:19 -0400
50. Re: getting qpopper to run initially on RH7.1
"Kenneth Porter" <shiva at well dot com>
Mon, 15 Oct 2001 14:01:39 -0700
Date: Wed, 3 Oct 2001 14:40:55 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: SYS/TEMP: Unable to open Bulletin database
At 12:23 PM -0700 10/3/01, Justin Ainsworth wrote:
>Oct 3 11:11:47 diamond /usr/local/sbin/popper[30335]: jda at
>209.142.14.11 (209.142.14.11): -ERR [SYS/TEMP] Unable to open Bulletin
>database; contact your administrator
>
>Occasionally I get this error. It appears to be happening randomly,
>and for no apparent reason.
>
>I am running Qpopper 4.0.3, compiled with the following options:
>
>./configure
> --silent
> --enable-bulletins=/etc/bulletins
> --enable-bulldb=/etc/bulletins
> --enable-temp-drop-dir=/tmp/mspool
> --enable-cache-dir=/tmp/mcache
> --enable-spool-dir=/var/spool/mail
> --with-pam=qpopper
> --enable-trim-domain
> --enable-downcase-user
> --disable-reverse-lookup
> --enable-timeout 0
> --enable-statistics
> --enable-fast-update
> --enable-standalone
> --enable-servermode
> --disable-old-uidl
> --enable-optimizations
> --disable-debugging
> --disable-low-debug
> --enable-log-facility=LOG_LOCAL0
>
>Any help you can give would be very appreciated.
>
> .~.
> /v\
>-- // \\
>JA /( )\
> ^`~`^
> L I N U X
>[-----------------------------------------------------------]
> Justin Ainsworth Systems Administrator &
> PHONE: (530) 879-5660x108 Technical Support Supervisor
> FAX: (530) 879-5676 Sunset Net LLC
> WEB: http://www.sunset.net 1915 Mangrove Ave
> EMAIL: jda at sunset dot net Chico, CA 95926
>[-----------------------------------------------------------]
Most likely it's a contention issue on the bulletin database. The
current architecture requires each session to obtain an exclusive
lock on the bulldb for a short time. With many simultaneous
connections, some won't be able to do so before they time out. This
is discussed in the Administrator's Guide. You can (a) increase the
number of attempts each session makes, (b) turn on 'bulldb-nonfatal'
option, or (c) stop using a database to store the last seen bulletin.
(One long-term solution would be to have a Qpopper bulletin database
process which owns the lock and serves requests by the other Qpopper
processes.)
--
From: "Justin Ainsworth" <jda at sunset dot net>
Subject: RE: SYS/TEMP: Unable to open Bulletin database
Date: Wed, 3 Oct 2001 16:49:31 -0700
> Most likely it's a contention issue on the bulletin database. The
> current architecture requires each session to obtain an exclusive
> lock on the bulldb for a short time. With many simultaneous
> connections, some won't be able to do so before they time out. This
> is discussed in the Administrator's Guide. You can (a) increase the
> number of attempts each session makes, (b) turn on 'bulldb-nonfatal'
> option, or (c) stop using a database to store the last seen bulletin.
Thanks.
Well, (b) should take care of the problem.
What DB format does qpopper use for storing bulletin information? In
the event that I decide to switch away from using the bulldb, I would
like to be able to dump the output so I can update the users .popbull
files. I tried db_dump, but it was the wrong format.
>
> (One long-term solution would be to have a Qpopper bulletin database
> process which owns the lock and serves requests by the other Qpopper
> processes.)
Any possibility of this happening in the near future? :-)
.~.
/v\
-- // \\
JA /( )\
^`~`^
L I N U X
[-----------------------------------------------------------]
Justin Ainsworth Systems Administrator &
PHONE: (530) 879-5660x108 Technical Support Supervisor
FAX: (530) 879-5676 Sunset Net LLC
WEB: http://www.sunset.net 1915 Mangrove Ave
EMAIL: jda at sunset dot net Chico, CA 95926
[-----------------------------------------------------------]
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Thu, 4 Oct 2001 13:12:37 +0000
Subject: Alternate- and stls-Port seems to be the same.
Hello,
I am using Qpopper 4.0.3 (standalone).
I followed the QPopper-Manual guidance and set up a configuration file
for the alternate-port, one for the standard port and another one for common
settings (shown bellow). I don't get both to work.
The reason is that both daemons listen on Port 110, so always one of them
can run, the other can't start.
I thought the alternate-port option would let the daemon listen on port 995 ?
What I'am missing here ?
- oliver
My configuration:
----------------------------------------> File for the Standard Port
# Standardport Port (110) configuration
#
set tracefile = /var/log/popper.log
set tls-support = stls
set config-file = /etc/QPopper/common_popper.conf
<----------------------------------------
----------------------------------------> File for the alternate Port
# Alternate-Port (995) configuration
#
set tracefile = /var/log/alt_popper.log
set tls-support = alternate-port
set config-file = /etc/QPopper/common_popper.conf
<----------------------------------------
----------------------------------------> /etc/QPopper/common_popper.conf
# Some other settings ...
[...]
# Certificate and private key
set tls-server-cert-file = <my certificate>
set tls-private-key-file = <my private key>
<----------------------------------------
Date: Thu, 4 Oct 2001 10:49:52 -0400
From: "Doryce E . Moore" <demoore at ccsalpha3.nrl.navy dot mil>
Subject: support for Tru64 Unix 5.1
I tried to build a generic popper for Tru64 Unix 5.1. The password
that works for a clear-text telnet login will not work for popper. I
tried it with enable-special-auth and without it. I am using
qpopper4.0.3. The configure and make complete without errors.
--
Doryce E. Moore, Center for Computational Science
System Support Group
doryce.moore at nrl.navy dot mil
(202) 767-5853 (office/voice mail)
(202) 404-7402 (fax)
Date: Thu, 4 Oct 2001 16:35:48 +0000 (/etc/localtime)
From: Cecilia Cabrera <ccabrera at scooby.uba dot ar>
Subject: encrypted password
Hi, i've been to modify a Qpopper that isn't using encryption for
it's passwords so that it does. Since it is already running with at least
300 users and from what i've read, i believe the easiest thing to do would
be to run a ./configure --enable-specialauth so it uses /etc/shadows
encrypted passwords (althought this would leave them without mail for a while - as long as it
takes me to figure things out! :) ).
Is this right? Is there a simpler way?
Is there a document that explains things further that you can recommend?
Thanks a lot.
Cecilia.
PS: please have in mind that i'm a newbie at qpopper!
Date: Thu, 4 Oct 2001 13:57:39 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: encrypted password
On Thu, Oct 04, 2001 at 04:35:48PM +0000, Cecilia Cabrera wrote:
> Hi, i've been to modify a Qpopper that isn't using encryption for
> it's passwords so that it does. Since it is already running with at least
> 300 users and from what i've read, i believe the easiest thing to do would
> be to run a ./configure --enable-specialauth so it uses /etc/shadows
> encrypted passwords (althought this would leave them without mail for a while - as long as it
> takes me to figure things out! :) ).
>
> Is this right? Is there a simpler way?
Are you attempting to have it use encrypted passwords "on the disk", in
terms of how the password's stored on the server, or "on the wire", for
network communications with the users?
Shadow password files have to do with the former, how securely the data
is stored on the disk. If your qpopper is working with the users'
normal login passwords now, and if your system has a shadow password
file, then qpopper is already using the shadow password file and you
don't need to reconfigure it for that.
If you're wanting it to use encrypted communication "on the wire", for
the network connections, then that's a totally different question.
Again, it won't involve whether you're using a shadow password file,
and it won't work by having the users log in with the encrypted text
you find inside the password file.
You need to consider several possibilities, which will depend on what
your users' mail programs support. If you only have a few hundred
users, you may have an easier time limiting what programs you use.
Two major alternatives are:
APOP - the session is in the clear (unencrypted), but the user's mail
program follows an alternative authentication protocol which does not
get the password from the user in "cleartext". This uses a separate
password database.
SSL - the entire session between the user's mail program and qpopper is
encrypted using the same protocol used for secure web server
connections; *inside* this encrypted channel, the username and password
change take place just as usual.
TLS is a variation on SSL where the two ends of the protocol (qpopper
and the mail client) can automatically detect whether they can both use
encryption, or make a clear connection if they can't.
> Is there a document that explains things further that you can recommend?
Do read the whole .PDF file included with popper. It has a lot of
useful information there. This is probably the limit of what I can
help you with; I know how this works in theory, but have not set up
either of those in practice.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Kenneth Porter" <shiva at well dot com>
Date: Thu, 04 Oct 2001 19:00:03 -0700
Subject: Re: Alternate- and stls-Port seems to be the same.
On Thu, 4 Oct 2001 13:12:37 +0000, Oliver Egginger wrote:
>I am using Qpopper 4.0.3 (standalone).
>
>I followed the QPopper-Manual guidance and set up a configuration file
>for the alternate-port, one for the standard port and another one for common
>settings (shown bellow). I don't get both to work.
>The reason is that both daemons listen on Port 110, so always one of them
>can run, the other can't start.
>
>I thought the alternate-port option would let the daemon listen on port 995 ?
>What I'am missing here ?
See page 42 in the PDF file, which explains how to start Qpopper in
standalone mode. Step 2 shows how to specify the IP address and port
number.
(I use xinetd, so I specify the ports in my xinetd config files.)
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Date: Fri, 05 Oct 2001 10:55:00 +0200
From: "Sascha Reimann" <reimann at haar-systemberatung dot de>
Subject: qpopper 4.0.3
Hi,
I want to configure a qpopper4.0.3 with pop after smtp function.
I only find a patch for the old version 2.5.3.!
Have anybody an idea where i can find the right patch?
Thanks for help!!!
Sascha
Mit freundlichen Grüßen
Sascha Reimann
Networktechnology / Security
Haar Systemberatung GmbH
Akazienstrasse 13
48432 Rheine
Tel: 05971 17500
Fax: 05971 17503
Mob.: 0170 3231384
www.haar-systemberatung.de
reimann at haar-systemberatung dot de
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 05 Oct 2001 02:11:14 -0700
Subject: Re: qpopper 4.0.3
On Fri, 05 Oct 2001 10:55:00 +0200, Sascha Reimann wrote:
>I want to configure a qpopper4.0.3 with pop after smtp function.
>I only find a patch for the old version 2.5.3.!
>Have anybody an idea where i can find the right patch?
It's called POP-before-SMTP, and it's already built in. Look for the
DRAC feature. (DRAC is a separate package that qpopper can take
advantage of.)
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Fri, 5 Oct 2001 11:11:01 +0000
Subject: Re: qpopper 4.0.3
> I want to configure a qpopper4.0.3 with pop after smtp function.
> I only find a patch for the old version 2.5.3.!
Did you mean smtp after pop ... ?
I suppose.
See the User-Guide
Sides 7, 19 and 22
then have look at
http://mail.cc.umanitoba.ca/drac/
alternativ you can check out the log-messages implementation,
decribed at
http://www.spam.cl.cam.ac.uk/spam/tools/smPbS.html
hope this helps
- oliver
Date: Fri, 05 Oct 2001 11:45:37 +0200
From: "Sascha Reimann" <reimann at haar-systemberatung dot de>
Subject: Re: qpopper 4.0.3
LOL, yes of course, I mean smtp after pop :-)
Thanks for your answers!
Kind regards,
sascha
Mit freundlichen Grüßen
Sascha Reimann
Networktechnology / Security
Haar Systemberatung GmbH
Akazienstrasse 13
48432 Rheine
Tel: 05971 17500
Fax: 05971 17503
Mob.: 0170 3231384
www.haar-systemberatung.de
reimann at haar-systemberatung dot de
Date: Fri, 5 Oct 2001 10:26:34 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Alternate- and stls-Port seems to be the same.
Most likely you aren't setting things up so that Qpopper actually
serves both ports. You do that using whichever method you normally
use to cause Qpopper to service a port. This might be inetd, xinetd,
or if you use standalone mode, an rc file. Whichever method you use,
you'll need two instances of Qpopper, one per port.
Date: Fri, 5 Oct 2001 10:27:58 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: support for Tru64 Unix 5.1
At 10:49 AM -0400 10/4/01, Doryce E . Moore wrote:
> I tried to build a generic popper for Tru64 Unix 5.1. The password
> that works for a clear-text telnet login will not work for popper.
> I tried it with enable-special-auth and without it. I am using
> qpopper4.0.3. The configure and make complete without errors.
> --
> Doryce E. Moore, Center for Computational Science
> System Support Group
> doryce.moore at nrl.navy dot mil
> (202) 767-5853 (office/voice mail)
> (202) 404-7402 (fax)
Try enabling debug tracing and see if you get a more specific error.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you used
'-d') or to the file specified as 'tracefile'.
Date: Fri, 5 Oct 2001 10:24:23 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: RE: SYS/TEMP: Unable to open Bulletin database
At 4:49 PM -0700 10/3/01, Justin Ainsworth wrote:
> What DB format does qpopper use for storing bulletin information?
I'd have to check the code, but offhand I think it just stores a
(key, value) pair with the last bulletin number as the data and the
user name as the key, using whichever database library was selected
at compile time (dbm, ndbm, gdbm).
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Mon, 8 Oct 2001 10:37:48 +0000
Subject: Re: Alternate- and stls-Port seems to be the same.
Yes, I didn't set up Qpopper suitable.
I was thinking, that the alternate-port option will be sufficing,
so that I don't have to define that port explicit.
Maybe it would be helpful to rename this option to make clear that
"alternate-port" and "stls" differ from the used protocol and not from the port,
even if the "alternate-port"-protocol mostly will be used on port 995.
Many thanks for your help !
regards
oliver
Kenneth Porter wrote:
> See page 42 in the PDF file, which explains how to start Qpopper in
> standalone mode. Step 2 shows how to specify the IP address and port
> number.
Randall Gellens wrote:
> Most likely you aren't setting things up so that Qpopper actually
> serves both ports. You do that using whichever method you normally
> use to cause Qpopper to service a port. This might be inetd, xinetd,
> or if you use standalone mode, an rc file. Whichever method you use,
> you'll need two instances of Qpopper, one per port.
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Mon, 8 Oct 2001 12:29:21 +0000
Subject: "alternate-port", "stls" and MS-Outlook
New difficulties (sorry to bore you again),
I try to configure Qpopper to accept SSL-Conections from Microsoft-Clients,
for our Microsoft users.
I am testing with Microsoft-Outlook 2000 (9.0.0.2814).
On the server-side I run both protocols ("stls" ; "alternate-port") successively
on Port 995.
It failed in both cases.
The Error-Message from MS-Outlook isn't very useful.
Therefore I have (consecutively) included the debug-output from the both daemons.
The "alternate-port" debug-output says, that the TLS/SSL handshake
failed - but why ?
The debug output from the "stls" option tells me practically nothing.
(I am no TLS/SSL expert).
:-(
Maybe you'll skim over it ...
regards
- oliver
d e b u g - o u t p u t f o r "a l t e r n a t e - p o r t" o n p o r t 995 :
Oct 8 09:54:13.783 2001 [18935] Trace and Debug destination is file "/var/log/alt_popper.log" [pop_config.c:1108]
Oct 8 09:54:13.783 2001
Oct 8 09:54:13.783 2001 [18935] ...read line 4 (32): set tls-support = alternate-port [pop_config.c:1314]
Oct 8 09:54:13.783 2001
Oct 8 09:54:13.783 2001 [18935] Set tls-support to alternate-port (1) [pop_config.c:1195]
Oct 8 09:54:13.783 2001
Oct 8 09:54:13.783 2001 [18935] ...read line 5 (49): set config-file = /etc/QPopper/common_popper.conf [pop_config.c:1314]
Oct 8 09:54:13.783 2001
Oct 8 09:54:13.783 2001 [18935] Processing config file '/etc/QPopper/common_popper.conf'; CallTime=1 [pop_config.c:1278]
[...]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 31 (68): set tls-server-cert-file = /usr/local/apache/conf/ssl.crt/server.crt [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] Set tls-server-cert-file to "/usr/local/apache/conf/ssl.crt/server.crt" [pop_config.c:1211]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 32 (68): set tls-private-key-file = /usr/local/apache/conf/ssl.key/server.key [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] Set tls-private-key-file to "/usr/local/apache/conf/ssl.key/server.key" [pop_config.c:1211]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 33 (0): [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 34 (0): [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 35 (0): [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] ...read line 36 (0): [pop_config.c:1314]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] Finished processing config file '/etc/QPopper/common_popper.conf'; rslt=1 [pop_config.c:1462]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.784 2001 [18935] Finished processing config file '/etc/QPopper/alt_popper.conf'; rslt=1 [pop_config.c:1462]
Oct 8 09:54:13.784 2001
Oct 8 09:54:13.786 2001 [18935] (v4.0.3) Servicing request from "chaos.dvz.fh-giessen.de" at 212.201.18.85 [pop_init.c:1152]
Oct 8 09:54:13.786 2001
Oct 8 09:54:13.786 2001 [18935] before TLS; tls_support==1 [popper.c:171]
Oct 8 09:54:13.786 2001
Oct 8 09:54:13.787 2001 [18935] ...Initializing OpenSSL library [pop_tls_openssl.c:224]
Oct 8 09:54:13.787 2001
Oct 8 09:54:13.788 2001 [18935] ...have /dev/urandom; skipping PRNG seeding [pop_tls_openssl.c:282]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...setting method to SSLv23_server_method [pop_tls_openssl.c:306]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...allocating OpenSSL context [pop_tls_openssl.c:336]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...setting certificate file /usr/local/apache/conf/ssl.crt/server.crt [pop_tls_openssl.c:346]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...setting private key file /usr/local/apache/conf/ssl.key/server.key [pop_tls_openssl.c:367]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...verifying private key against certificate [pop_tls_openssl.c:381]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...(tls_cipher_list not specified) [pop_tls_openssl.c:408]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...allocating OpenSSL connection [pop_tls_openssl.c:419]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...setting input (0) and output (0) file descriptors [pop_tls_openssl.c:429]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] ...successfully completed OpenSSL initialization [pop_tls_openssl.c:449]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] TLS Init [popper.c:193]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.788 2001 [18935] Attempting OpenSSL handshake [pop_tls_openssl.c:498]
Oct 8 09:54:13.788 2001
Oct 8 09:54:13.789 2001 [18935] tls accept returned 0 [pop_tls_openssl.c:501]
Oct 8 09:54:13.789 2001
Oct 8 09:54:13.789 2001 [18935] SSL_get_error says SSL_ERROR_SYSCALL (5) [pop_tls_openssl.c:507]
Oct 8 09:54:13.789 2001
Oct 8 09:54:13.789 2001 [18935] TLS handshake Error [pop_tls_openssl.c:541]
Oct 8 09:54:13.789 2001
Oct 8 09:54:13.789 2001 [18935] TLS/SSL Handshake failed: -1 [popper.c:204]
Oct 8 09:54:13.789 2001
d e b u g - o u t p u t f o r "s t l s" o n p o r t" 995 :
Oct 8 09:27:49.965 2001 [18705] Trace and Debug destination is file "/var/log/popper.log" [pop_config.c:1108]
Oct 8 09:27:49.965 2001
Oct 8 09:27:49.965 2001 [18705] ...read line 4 (22): set tls-support = stls [pop_config.c:1314]
Oct 8 09:27:49.965 2001
Oct 8 09:27:49.965 2001 [18705] Set tls-support to STLS (2) [pop_config.c:1195]
Oct 8 09:27:49.965 2001
Oct 8 09:27:49.965 2001 [18705] ...read line 5 (49): set config-file = /etc/QPopper/common_popper.conf [pop_config.c:1314]
Oct 8 09:27:49.965 2001
Oct 8 09:27:49.965 2001 [18705] Processing config file '/etc/QPopper/common_popper.conf'; CallTime=1 [pop_config.c:1278]
[...]
Oct 8 09:27:49.966 2001 [18705] ...read line 31 (68): set tls-server-cert-file = /usr/local/apache/conf/ssl.crt/server.crt [pop_config.c:1314]
Oct 8 09:27:49.966 2001
Oct 8 09:27:49.966 2001 [18705] Set tls-server-cert-file to "/usr/local/apache/conf/ssl.crt/server.crt" [pop_config.c:1211]
Oct 8 09:27:49.966 2001
Oct 8 09:27:49.966 2001 [18705] ...read line 32 (68): set tls-private-key-file = /usr/local/apache/conf/ssl.key/server.key [pop_config.c:1314]
Oct 8 09:27:49.966 2001
Oct 8 09:27:49.966 2001 [18705] Set tls-private-key-file to "/usr/local/apache/conf/ssl.key/server.key" [pop_config.c:1211]
Oct 8 09:27:49.966 2001
[...]
Oct 8 09:27:49.966 2001 [18705] Finished processing config file '/etc/QPopper/common_popper.conf'; rslt=1 [pop_config.c:1462]
Oct 8 09:27:49.966 2001
Oct 8 09:27:49.966 2001 [18705] Finished processing config file '/etc/QPopper/tssl_popper.conf'; rslt=1 [pop_config.c:1462]
Oct 8 09:27:49.966 2001
Oct 8 09:27:49.969 2001 [18705] (v4.0.3) Servicing request from "chaos.dvz.fh-giessen.de" at 212.201.18.85 [pop_init.c:1152]
Oct 8 09:27:49.969 2001
Oct 8 09:27:49.969 2001 [18705] before TLS; tls_support==2 [popper.c:171]
Oct 8 09:27:49.969 2001
Oct 8 09:27:49.969 2001 [18705] ...Initializing OpenSSL library [pop_tls_openssl.c:224]
Oct 8 09:27:49.969 2001
Oct 8 09:27:49.970 2001 [18705] ...have /dev/urandom; skipping PRNG seeding [pop_tls_openssl.c:282]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...setting method to SSLv23_server_method [pop_tls_openssl.c:306]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...allocating OpenSSL context [pop_tls_openssl.c:336]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...setting certificate file /usr/local/apache/conf/ssl.crt/server.crt [pop_tls_openssl.c:346]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...setting private key file /usr/local/apache/conf/ssl.key/server.key [pop_tls_openssl.c:367]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...verifying private key against certificate [pop_tls_openssl.c:381]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...(tls_cipher_list not specified) [pop_tls_openssl.c:408]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.970 2001 [18705] ...allocating OpenSSL connection [pop_tls_openssl.c:419]
Oct 8 09:27:49.970 2001
Oct 8 09:27:49.971 2001 [18705] ...setting input (0) and output (0) file descriptors [pop_tls_openssl.c:429]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.971 2001 [18705] ...successfully completed OpenSSL initialization [pop_tls_openssl.c:449]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.971 2001 [18705] TLS Init [popper.c:193]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.971 2001 [18705] (v4.0.3) Intro [popper.c:238]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.971 2001 [18705] +OK Qpopper (version 4.0.3) at david.dvz.fh-giessen.de starting. [popper.c:251]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.971 2001 [18705] Qpopper ready for input from (null) at chaos.dvz.fh-giessen.de [212.201.18.85] [popper.c:283]
Oct 8 09:27:49.971 2001
Oct 8 09:27:49.974 2001 [18705] (null) at chaos.dvz.fh-giessen.de (212.201.18.85): -ERR POP EOF or I/O Error [popper.c:794]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] I/O error flushing output to client at chaos.dvz.fh-giessen.de [212.201.18.85]: Operation not permitted (1) [pop_send.c:685]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] +OK Pop server at david.dvz.fh-giessen.de signing off. [popper.c:351]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] I/O error flushing output to client at chaos.dvz.fh-giessen.de [212.201.18.85]: Operation not permitted (1) [pop_send.c:685]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] pTLS->m_pPOP->tls_started == false [pop_tls_openssl.c:807]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] freeing m_OpenSSLconn [pop_tls_openssl.c:811]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] freeing m_OpenSSLctx [pop_tls_openssl.c:817]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] openssl_shutdown returning 0 [pop_tls_openssl.c:822]
Oct 8 09:27:49.974 2001
Oct 8 09:27:49.974 2001 [18705] (v4.0.3) Ending request from "" at (chaos.dvz.fh-giessen.de) 212.201.18.85 [popper.c:368]
Oct 8 09:27:49.974 2001
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Mon, 8 Oct 2001 12:50:44 +0000
Subject: Re: support for Tru64 Unix 5.1
Maybe you use a different PAM stack for your telnet daemon.
The corresponding files can be found in /etc/pam.d
(Mandrake / RedHat distributions).
I don't know, whether this is true for Tru64.
- oliver
> I tried to build a generic popper for Tru64 Unix 5.1. The password
> that works for a clear-text telnet login will not work for popper. I
> tried it with enable-special-auth and without it. I am using
> qpopper4.0.3. The configure and make complete without errors.
From: "Matthew Hale" <mhale at semo dot net>
Subject: Problem With QPopper
Date: Mon, 8 Oct 2001 13:24:03 -0500
I am using the latest version of QPopper on Debian. This is what error I'm
getting:
There was a problem logging onto your mail server. Your Password was
rejected. Account: 'mail.interace.net', Server: 'mail.interace.net',
Protocol: POP3, Server Response: '-ERR maillock: cannot lock
'/var/mail/interace': 1', Port: 110, Secure(SSL): No, Server Error:
0x800CCC90, Error Number: 0x800CCC92
How do I fix this?!?!?!?!?!?!?
Sincerely,
Matthew Hale
Date: Mon, 8 Oct 2001 15:19:34 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: "alternate-port", "stls" and MS-Outlook
At 12:29 PM +0000 10/8/01, Oliver Egginger wrote:
>The "alternate-port" debug-output says, that the TLS/SSL handshake
>failed - but why ?
I'd suggest trying another client (such as Eudora) and/or turning on
any debug/trace capability in Outlook (I know OE has one). Perhaps
it didn't like the cert.
>The debug output from the "stls" option tells me practically nothing.
It says the connection dropped, probably because the client (Outlook)
can't handle stls (which is unfortunate) and is expecting
alternate-port.
There are two ways of setting up a TLS/SSL connection. The proper
way is with stls, where the server advertises its capabilities and
the client requests TLS. The TLS handshake occurs after the client
requests it (using the stls command).
The other way is alternate-port, where the TLS or SSL handshake
occurs immediately when the connection opens.
--
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 9 Oct 2001 14:21:33 +0000
Subject: Re: Problem With QPopper
Hello,
You asked:
> How do I fix this?!?!?!?!?!?!?
I don't know !
Maybe the file or the directory is set to invalid access rights.
The POP-Daemon (qpopper) needs write access to this file.
But the output says as well, that the password was rejected.
Check your accounting configuration too.
Do you using PAM ?
Consult the log-files (maybe located at /var/log) for more information
(auth.log; syslog and your qpopper log file, if you have one)
Also you should turn the debug-mode of QPopper on!
Randall Gellens wrote:
> Try enabling debug tracing and see if you get a more specific error.
>
> To enable tracing in Qpopper:
>
> 1. Do a 'make clean'
> 2. Re-run ./configure, adding '--enable-debugging'.
> 3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
> 4. Send inetd a HUP signal.
>
> This causes detailed tracing to be written to the syslog (if you used
> '-d') or to the file specified as 'tracefile'.
Step 3 and 4 are only necessary if you start QPopper via inetd.
If you use QPopper in standalone mode you can simply put the line
set debug = true
in your configuration file or you must pass the corresponding command-line
option to the daemon.
- oliver
Date: Tue, 09 Oct 2001 14:28:19 +0100
From: Sean Kelly <sean.kelly at the-web-works.co dot uk>
Subject: Implementing user quotas
Hi there,
After failing to find anything about this subject in the list archives for the past few months I thought I would ask the list.
One of my POP servers has e-mail for various users delivered to and collected from /var/spool/mail/whoever. I have a need to implement maximum mailbox size restrictions on the
various mailboxes. First I looked at my mail server, but that's just the transfer agent and as such I don't think it should deal with quotas.
What methods does Qpopper supply in order to enforce a maximum mailbox size for users on a system?
Thanks in advance,
--
Sean Kelly
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 9 Oct 2001 15:56:23 +0000
Subject: Re: Implementing user quotas
Sorry,
but why (for the wold) a pop-daemon have to deal with mail-quotas ?
What MTA are you using ?
We employ Exim. Exim support Mail-Quotas, and Size-Warn-Messages as well.
I am sure that almost every MTA support things like that.
A Pop-daemon make the boxes smaller or keep the size,
so it would be tricky for a pop-daemon to manage quotas.
hope that helps
- oliver
> Hi there,
>
> After failing to find anything about this subject in the list archives for
> the past few months I thought I would ask the list.
>
> One of my POP servers has e-mail for various users delivered to and
> collected from /var/spool/mail/whoever. I have a need to implement maximum
> mailbox size restrictions on the various mailboxes. First I looked at my
> mail server, but that's just the transfer agent and as such I don't think
> it should deal with quotas.
>
> What methods does Qpopper supply in order to enforce a maximum mailbox
> size for users on a system?
>
> Thanks in advance,
>
> --
> Sean Kelly
--
Oliver Egginger
FH Giessen-Friedberg
DV-Zentrum
Wiesenstrasse 14
35390 Giessen
Tel. +49 641 309-1283
Fax +49 641 309-2908
Mail: Oliver.Egginger at dvz.fh-giessen dot de
****************************************************
Sprechzeiten des DV-Zentrums fuer
E-Mail-Angelegenheiten:
Mo 11:30 - 15:30 Uhr
Di 13:15 - 15:30 Uhr
Do 9:30 - 16:00 Uhr
Fr 9:45 - 11:45 Uhr
****************************************************
Date: Tue, 09 Oct 2001 14:55:16 +0100
From: Sean Kelly <sean.kelly at the-web-works.co dot uk>
Subject: RE: Implementing user quotas
Aarrgh, brain fart - of course it's not qpopper's job. That's why there's nothing in the archives about it.
Sorry all,
--
Sean Kelly
Date: Tue, 09 Oct 2001 08:53:36 -0500
From: Butch Kemper <kemper at tstar dot net>
Subject: Re: Implementing user quotas
Mail size restrictions are not a function of Qpopper.
Implementing such restrictions must be done when the mail messages are
delivered by the Mail Transport Agent to the User's Mail Box.
Qpopper only reads the User's Mail Box and delivers the messages to the
Mail User Agent.
Butch
At 08:28 AM 10/9/01, you wrote:
>Hi there,
>
> After failing to find anything about this subject in the list
> archives for the past few months I thought I would ask the list.
>
> One of my POP servers has e-mail for various users delivered to
> and collected from /var/spool/mail/whoever. I have a need to implement
> maximum mailbox size restrictions on the
>various mailboxes. First I looked at my mail server, but that's just the
>transfer agent and as such I don't think it should deal with quotas.
>
> What methods does Qpopper supply in order to enforce a maximum
> mailbox size for users on a system?
>
> Thanks in advance,
>
>--
>Sean Kelly
TSTAR Internet, Inc | Making the Net Work
Marble Falls, TX | Serving Blanco, Burnet,
830-693-6967 | Llano, and Mason Counties
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 9 Oct 2001 17:56:15 +0000
Subject: Re: "alternate-port", "stls" and MS-Outlook
Hello again,
>
> I'd suggest trying another client (such as Eudora) and/or turning on
> any debug/trace capability in Outlook (I know OE has one). Perhaps
> it didn't like the cert.
>
guessed, thank you very much Randall !
After I installed the Server and CA certificate (selfsigned) proper,
it starts working with Outlook and Eudora.
(there are still one additional step required for Eudora).
But (to make a long story short) there are now some "new" qpopper debug-messages,
I can't really understand.
For Every TLS/SSL connection (this is true for both ports, "alternate" and "stls")
I found the following messages at the end of the tracefile:
Oct 9 12:10:13.521 2001 [24910] SSL_get_error says SSL_ERROR_SYSCALL (5) [pop_tls_openssl.c:766]
Oct 9 12:10:13.521 2001
Oct 9 12:10:13.521 2001 [24910] TLS shutdown Error [pop_tls_openssl.c:789]
Oct 9 12:10:13.521 2001
Oct 9 12:10:13.521 2001 [24910] freeing m_OpenSSLconn [pop_tls_openssl.c:811]
Oct 9 12:10:13.521 2001
Oct 9 12:10:13.521 2001 [24910] freeing m_OpenSSLctx [pop_tls_openssl.c:817]
Oct 9 12:10:13.521 2001
Oct 9 12:10:13.521 2001 [24910] openssl_shutdown returning -1 [pop_tls_openssl.c:822]
Oct 9 12:10:13.521 2001
Oct 9 12:10:13.521 2001 [24910] (v4.0.3) Ending request from "hg6522" at (chaos.dvz.fh-giessen.de) 212.201.18.85 [popper.c:368]
Oct 9 12:10:13.521 2001
What means TLS shutdown error ?
Why it can't close the connection proper ?
Can this cause difficulties in certain circumstances ?
If I only consider the Client-Side, it seems to work perfectly.
I would be deeply grateful if someone could give me a clue
(which me not refer back to the sources).
regards
- oliver
n o t e i n t h e m a r g i n :
The only tick, I can see on the Client-Side, comes from the
"Eudora SSL Connection Information Manager" it says:
***** Unknown certificate chain validation error: Code(3015) *****
***** But ignoring this error because Certificate is trusted *****
I suppose that this message appears, cause I am unable to install the
CA Certificate for Eudora (but this is no QPopper subject).
Outlook shows no messages at all (excepting the E-Mails :-} ... ),
but I did't discover the "trace-capability" of Outlook as yet ...
Date: Tue, 09 Oct 2001 11:36:21 -0500
From: Ted George <ted at kcnet dot com>
Subject: specify user homedir for temp-drop-dir
hello,
is there a way to set the temp-drop-dir location to the user's home
directory. the mail spool can be set to the home dir with
--enable-home-dir-mail, but the .pop file still gets created in
/var/spool/mail, or any other directory that you can specify with the
./configure. not sure how to use the homedir here since $HOME is root's
home dir
thanks
Date: Tue, 9 Oct 2001 11:02:47 -0700 (PDT)
From: Gustavo Viscaino <g_viscaino at yahoo dot com>
Subject: Re: "alternate-port", "stls" and MS-Outlook
Hello,
> but I did't discover the "trace-capability" of
> Outlook as yet ...
In Outlook Express: Tools, Options, Maintenance (it
might be called something else; I'm not using the
English version of Windows; anyway, it's the tab
beside "Connection"). Down below, there's a checkbox
to create a logfile for all mail actions. The only
problem is that I don't remember the filename neither
its location... it's buried somewhere in the
"x:\windows\application data\whatever\...\microsoft
outlook" mess (I don't have Windows here right now,
sorry ;-)). I don't know whether MS Outlook supports
this, though.
Good luck,
Gustavo Viscaino
__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
Date: Tue, 9 Oct 2001 12:29:01 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Problem With QPopper
At 1:24 PM -0500 10/8/01, Matthew Hale wrote:
>I am using the latest version of QPopper on Debian. This is what error I'm
>getting:
>
>There was a problem logging onto your mail server. Your Password was
>rejected. Account: 'mail.interace.net', Server: 'mail.interace.net',
>Protocol: POP3, Server Response: '-ERR maillock: cannot lock
>'/var/mail/interace': 1', Port: 110, Secure(SSL): No, Server Error:
>0x800CCC90, Error Number: 0x800CCC92
>
>How do I fix this?!?!?!?!?!?!?
>
>
> Sincerely,
> Matthew Hale
I'd suggest turning on debug tracing to see if you get any more
details in the log.
--
--
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you used
'-d') or to the file specified as 'tracefile'.
Date: Tue, 9 Oct 2001 10:24:06 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Implementing user quotas
On Tue, Oct 09, 2001 at 02:28:19PM +0100, Sean Kelly wrote:
> Hi there,
>
> After failing to find anything about this subject in the list
> archives for the past few months I thought I would ask the
> list.
>
> One of my POP servers has e-mail for various users delivered to
> and collected from /var/spool/mail/whoever. I have a need to
> implement maximum mailbox size restrictions on the various mailboxes.
> First I looked at my mail server, but that's just the transfer agent
> and as such I don't think it should deal with quotas.
...
When I was reviewing it a month or two ago, I found a surprising
scarcity of web information on setting up mail quotas; you'd think
everyone would want to do it, but there's not much information out
there, at least not that I could find in Google. I wanted to do it via
file-system (kernel-level) quotas, but had to make sure that all
components of the mail system would handle it well.
There actually is one important Qpopper related fact for implementing
mail quotas:
If you implement quotas at the file system level, you want to
configure Qpopper so the temporary pop-drop files are on a different
partition from your mail spools, without user quotas. Otherwise, once
a user hits their quota, they will be unable to pop their mail to
reduce their mailbox below quota.
That aside, quota enforcement is the work of the local mail delivery
agent; that may be either your MTA, or delegated by the MTA to some
other program. We use procmail for local mail delivery, and our
testing showed that it was very quota-aware, and able to communicate
over-quota conditions back to the MTA which invoked it. After a little
tweaking on how our MTA reported these erorrs, I enabled and set user
quotas on our mail spool partition two weeks ago, and have not had any
problems with it so far. If users are near quota, any new mail coming
in which would put them over-quota gets bounced back to the sender
instead of being delivered.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Tue, 9 Oct 2001 16:23:19 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: "alternate-port", "stls" and MS-Outlook
At 5:56 PM +0000 10/9/01, Oliver Egginger wrote:
>What means TLS shutdown error ?
>Why it can't close the connection proper ?
>Can this cause difficulties in certain circumstances ?
This shouldn't cause any problems. Qpopper was trying to close TLS
connections that hadn't been set up. A patch went in to fix this,
but I can't recall offhand if it's in 4.0.3 or not. If not it'll be
in the next release.
--
Date: Wed, 10 Oct 2001 13:53:22 +0800 (HKT)
From: PM WONG <pmwong at power25t.hkbu.edu dot hk>
Subject: what are these lock files
I've found a lot of lock files
(not by the name username.lock) under /var/spool/mail
They are named like:
username.lock.1001301842.37546.hostname
Now though they are 0 size, i wonder if their left over
will affect users doing their popper session?
Why do they exist and can i delete them at anytime (if not
when could i kill them ?)
We run qpopper 4.0.3
Date: Wed, 10 Oct 2001 12:25:29 +0100
From: peter.allen at moon-light.co dot uk
Subject: Re: Implementing user quotas
Hi Clifton
Thanks for your reply which was most informative and set us here thinking.
The main query was did your approach of copying temporary pop-drop files to
a different partition (and back) slow the process down at all ? Currently
our pop-drops reside in the users' home directory the same as their Mailbox
you see.
Best regards
Peter
At 10:24 09/10/01 -1000, Clifton Royston wrote:
>On Tue, Oct 09, 2001 at 02:28:19PM +0100, Sean Kelly wrote:
> > Hi there,
> >
> > After failing to find anything about this subject in the list
> > archives for the past few months I thought I would ask the
> > list.
> >
> > One of my POP servers has e-mail for various users delivered to
> > and collected from /var/spool/mail/whoever. I have a need to
> > implement maximum mailbox size restrictions on the various mailboxes.
> > First I looked at my mail server, but that's just the transfer agent
> > and as such I don't think it should deal with quotas.
>...
>
> When I was reviewing it a month or two ago, I found a surprising
>scarcity of web information on setting up mail quotas; you'd think
>everyone would want to do it, but there's not much information out
>there, at least not that I could find in Google. I wanted to do it via
>file-system (kernel-level) quotas, but had to make sure that all
>components of the mail system would handle it well.
>
> There actually is one important Qpopper related fact for implementing
>mail quotas:
>
> If you implement quotas at the file system level, you want to
>configure Qpopper so the temporary pop-drop files are on a different
>partition from your mail spools, without user quotas. Otherwise, once
>a user hits their quota, they will be unable to pop their mail to
>reduce their mailbox below quota.
>
> That aside, quota enforcement is the work of the local mail delivery
>agent; that may be either your MTA, or delegated by the MTA to some
>other program. We use procmail for local mail delivery, and our
>testing showed that it was very quota-aware, and able to communicate
>over-quota conditions back to the MTA which invoked it. After a little
>tweaking on how our MTA reported these erorrs, I enabled and set user
>quotas on our mail spool partition two weeks ago, and have not had any
>problems with it so far. If users are near quota, any new mail coming
>in which would put them over-quota gets bounced back to the sender
>instead of being delivered.
>
> -- Clifton
>
>--
> Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Wed, 10 Oct 2001 08:25:35 -0400
From: Steve Perrault <sperraul at mnsi dot net>
Subject: Implementing user quotas / Expiring Email
My concern is what occurs when a user is at quota. How does Qpopper make
room to add the X-UIDL lines if the person is already at quota?
Also, has anyone implemented an expire mechanism to Qpopper? As in "delete
all messages older than x days, and delete all read messages older than y
days". Admittedly, it would only affect people who actually CHECK their
email, but it would be cleaner than my Perl code to do the same thing.
- SteveP
> > Hi there,
> >
> > After failing to find anything about this subject in the list
> > archives for the past few months I thought I would ask the
> > list.
> >
> > One of my POP servers has e-mail for various users delivered to
> > and collected from /var/spool/mail/whoever. I have a need to
> > implement maximum mailbox size restrictions on the various mailboxes.
> > First I looked at my mail server, but that's just the transfer agent
> > and as such I don't think it should deal with quotas.
>...
>
>
> When I was reviewing it a month or two ago, I found a surprising
>scarcity of web information on setting up mail quotas; you'd think
>everyone would want to do it, but there's not much information out
>there, at least not that I could find in Google. I wanted to do it via
>file-system (kernel-level) quotas, but had to make sure that all
>components of the mail system would handle it well.
>
> There actually is one important Qpopper related fact for implementing
>mail quotas:
>
>
> If you implement quotas at the file system level, you want to
>configure Qpopper so the temporary pop-drop files are on a different
>partition from your mail spools, without user quotas. Otherwise, once
>a user hits their quota, they will be unable to pop their mail to
>reduce their mailbox below quota.
>
>
> That aside, quota enforcement is the work of the local mail delivery
>agent; that may be either your MTA, or delegated by the MTA to some
>other program. We use procmail for local mail delivery, and our
>testing showed that it was very quota-aware, and able to communicate
>over-quota conditions back to the MTA which invoked it. After a little
>tweaking on how our MTA reported these erorrs, I enabled and set user
>quotas on our mail spool partition two weeks ago, and have not had any
>problems with it so far. If users are near quota, any new mail coming
>in which would put them over-quota gets bounced back to the sender
>instead of being delivered.
>
>
> -- Clifton
Date: Wed, 10 Oct 2001 05:47:17 -0700 (PDT)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: Re: Implementing user quotas / Expiring Email
> Date: Wed, 10 Oct 2001 08:25:35 -0400
> From: Steve Perrault <sperraul at mnsi dot net>
>
> My concern is what occurs when a user is at quota. How does Qpopper
> make room to add the X-UIDL lines if the person is already at quota?
What happens is that qpopper does not have to worry about the quota
since the underlying file system does the worrying. What happens is
that the file does not get modified and written back because the user is
out of space (over quota).
I would submit that this is not a Good Way (tm) to do business.
I submit that users should have a high limit (with notification sent at
the time the user goes over this quota saying something like "you are
over limit. Unless you go below x MB/GB/whatever in (x period of time),
you will be locked out.)
The user should also have a 'no-more-write' limit at say, 2x the high
limit.
And finally, the user have a hard "you shall not exceed this limit"
quota at say, 2.5x high limit:
At "high limit" (soft quota), the user gets a warning message and the
clock starts ticking towards end of grace period.
at 2x high limit - no more writes to disk.
at hard high limit - no more logins until they talk to some systems
person and get their disk area cleaned up.
My thoughts. Your own may vary.
> Also, has anyone implemented an expire mechanism to Qpopper? As in
> "delete all messages older than x days, and delete all read messages
> older than y days". Admittedly, it would only affect people who
> actually CHECK their email, but it would be cleaner than my Perl code
> to do the same thing.
This is most normally a function of the client side MUA.
As for the answer, there was some discussion on this a short while ago
(say a month-6weeks ago). There were several solutions proposed but
nothing emerged as the clear winner. There was 'preenmail' (I was most
interested in this so grabbed a copy) and some others.
Regards,
Gregory Hicks
>
> - SteveP
>
>
> > > Hi there,
> > >
> > > After failing to find anything about this subject in the
list
> > > archives for the past few months I thought I would ask the
> > > list.
> > >
> > > One of my POP servers has e-mail for various users delivered
to
> > > and collected from /var/spool/mail/whoever. I have a need to
> > > implement maximum mailbox size restrictions on the various
mailboxes.
> > > First I looked at my mail server, but that's just the transfer
agent
> > > and as such I don't think it should deal with quotas.
> >...
> >
> >
> > When I was reviewing it a month or two ago, I found a surprising
> >scarcity of web information on setting up mail quotas; you'd think
> >everyone would want to do it, but there's not much information out
> >there, at least not that I could find in Google. I wanted to do it
via
> >file-system (kernel-level) quotas, but had to make sure that all
> >components of the mail system would handle it well.
> >
> > There actually is one important Qpopper related fact for
implementing
> >mail quotas:
> >
> >
> > If you implement quotas at the file system level, you want to
> >configure Qpopper so the temporary pop-drop files are on a different
> >partition from your mail spools, without user quotas. Otherwise,
once
> >a user hits their quota, they will be unable to pop their mail to
> >reduce their mailbox below quota.
> >
> >
> > That aside, quota enforcement is the work of the local mail
delivery
> >agent; that may be either your MTA, or delegated by the MTA to some
> >other program. We use procmail for local mail delivery, and our
> >testing showed that it was very quota-aware, and able to communicate
> >over-quota conditions back to the MTA which invoked it. After a
little
> >tweaking on how our MTA reported these erorrs, I enabled and set user
> >quotas on our mail spool partition two weeks ago, and have not had
any
> >problems with it so far. If users are near quota, any new mail
coming
> >in which would put them over-quota gets bounced back to the sender
> >instead of being delivered.
> >
> >
> > -- Clifton
>
---------------------------------------------------------------------
Gregory Hicks | Principal Systems Engineer
Cadence Design Systems | Direct: 408.576.3609
555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479
San Jose, CA 95134 | Internet: ghicks at cadence dot com
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
Date: Wed, 10 Oct 2001 08:25:04 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Implementing user quotas
On Wed, Oct 10, 2001 at 12:25:29PM +0100, peter.allen at moon-light.co dot uk wrote:
> Thanks for your reply which was most informative and set us here thinking.
>
> The main query was did your approach of copying temporary pop-drop files to
> a different partition (and back) slow the process down at all ? Currently
> our pop-drops reside in the users' home directory the same as their Mailbox
> you see.
To answer your main question: No. I had *expected* that the total
performance would decrease in server-mode, because the "fast-updates"
option is ineffective when the two files are located on different
partitions. In fact the reverse happened - performance went up and
total load on our system went down, substantially.
Eventually I figured out that the performance increase from two other
factors more than compensated for this loss. The throughput when the
spools must be copied is faster because the second partition is on a
different RAID set, and this leads to more parallelized I/O during
large copies (the system can be simultaneously reading one set of disks
while writing the other set), but also it means much less disk head
motion and seek delays, because it does not need to "swing" the heads
from one part of the disk to another to copy a large spool file. (I've
forgotten who, but someone else on this list pointed that out as a key
factor in the performance analysis, thanks!) There's some emails from a
month or so ago discussing this on the list.
Summary: if you can put the temp files on a disk partition located on
a physically separate disk or RAID set from the one where your spools
are stored, your total POP throughput should go up dramatically.
Qpopper is generally disk-bound on most systems.
-- Clifton
> At 10:24 09/10/01 -1000, Clifton Royston wrote:
> > When I was reviewing it a month or two ago, I found a surprising
> >scarcity of web information on setting up mail quotas; you'd think
> >everyone would want to do it, but there's not much information out
> >there, at least not that I could find in Google. I wanted to do it via
> >file-system (kernel-level) quotas, but had to make sure that all
> >components of the mail system would handle it well.
> >
> > There actually is one important Qpopper related fact for implementing
> >mail quotas:
> >
> > If you implement quotas at the file system level, you want to
> >configure Qpopper so the temporary pop-drop files are on a different
> >partition from your mail spools, without user quotas. Otherwise, once
> >a user hits their quota, they will be unable to pop their mail to
> >reduce their mailbox below quota.
> >
> > That aside, quota enforcement is the work of the local mail delivery
> >agent; that may be either your MTA, or delegated by the MTA to some
> >other program. We use procmail for local mail delivery, and our
> >testing showed that it was very quota-aware, and able to communicate
> >over-quota conditions back to the MTA which invoked it. After a little
> >tweaking on how our MTA reported these erorrs, I enabled and set user
> >quotas on our mail spool partition two weeks ago, and have not had any
> >problems with it so far. If users are near quota, any new mail coming
> >in which would put them over-quota gets bounced back to the sender
> >instead of being delivered.
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Wed, 10 Oct 2001 08:33:44 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Implementing user quotas / Expiring Email
On Wed, Oct 10, 2001 at 08:25:35AM -0400, Steve Perrault wrote:
> My concern is what occurs when a user is at quota. How does Qpopper make
> room to add the X-UIDL lines if the person is already at quota?
This would be a problem, though it should only happen if someone is
*exactly* a few bytes short of the hard quota, or if they have been
over the "soft quota" long enough that it has set into stone, and
they're not deleting any mail.
Remember, the X-UIDL additions are only updated back into the main
spool at the end of the session. The POP session should still be able
to complete if they're over quota provided that they deleted enough
messages to get them back under quota. I think. That's one boundary
condition I didn't think to test, I admit.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Wed, 10 Oct 2001 11:41:43 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Implementing user quotas / Expiring Email
At 8:25 AM -0400 10/10/01, Steve Perrault wrote:
>Also, has anyone implemented an expire mechanism to Qpopper?
Qpopper does have an option to delete all read mail. There is a
wish-list item to make it flexible.
--
Date: Wed, 10 Oct 2001 11:38:45 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: what are these lock files
At 1:53 PM +0800 10/10/01, PM WONG wrote:
>I've found a lot of lock files
>(not by the name username.lock) under /var/spool/mail
>They are named like:
>username.lock.1001301842.37546.hostname
>
>Now though they are 0 size, i wonder if their left over
>will affect users doing their popper session?
>Why do they exist and can i delete them at anytime (if not
>when could i kill them ?)
>
>We run qpopper 4.0.3
I don't believe Qpopper ever creates or uses locks of that form.
Perhaps your delivery agent or some other process uses them?
It would be good to track down where they came from, because it's
vital that Qpopper and your delivery agent (and all other processes
which access the spool) use the same locking mechanism. Otherwise
the spools are likely to be corrupted.
--
Date: Thu, 11 Oct 2001 08:55:12 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: Implementing user quotas / Expiring Email
Steve Perrault (sperraul at mnsi dot net) wrote:
> My concern is what occurs when a user is at quota. How does Qpopper make
> room to add the X-UIDL lines if the person is already at quota?
use NOSTATUS, that way X-UIDL are always computed and not stored,
obviating the need for a re-write of the mailbox.
> Also, has anyone implemented an expire mechanism to Qpopper? As in "delete
> all messages older than x days, and delete all read messages older than y
> days". Admittedly, it would only affect people who actually CHECK their
> email, but it would be cleaner than my Perl code to do the same thing.
expiry by an outside program that locks in the same way as
sendmail(postfix/etcetc) would be best, then every day in the
middle of the low period, you'd get a notification like:
%HOUSE-3-EXPIRE, salvaged 23425931 bytes of expired mail. (9%)
--
New Snibbo! Combined Breakfast Cereal and Washing-Up Liquid!
Date: Thu, 11 Oct 2001 09:34:20 +0800 (HKT)
From: PM WONG <pmwong at power25t.hkbu.edu dot hk>
Subject: Re: what are these lock files
On Wed, 10 Oct 2001, Randall Gellens wrote:
> >They are named like:
> >username.lock.1001301842.37546.hostname
> >
> >Now though they are 0 size, i wonder if their left over
> >will affect users doing their popper session?
> I don't believe Qpopper ever creates or uses locks of that form.
> Perhaps your delivery agent or some other process uses them?
>
I guess they might be created by the imapd (the other most common
protocol users on our machine use to read mails)
Wonder if imapd have to create lock files like qpopper does ?
Date: Thu, 11 Oct 2001 07:56:18 -0500
From: Ted George <ted at kcnet dot com>
Subject: Re: Implementing user quotas / Expiring Email
Clifton Royston wrote:
>
> On Wed, Oct 10, 2001 at 08:25:35AM -0400, Steve Perrault wrote:
> > My concern is what occurs when a user is at quota. How does Qpopper make
> > room to add the X-UIDL lines if the person is already at quota?
>
> This would be a problem, though it should only happen if someone is
> *exactly* a few bytes short of the hard quota, or if they have been
> over the "soft quota" long enough that it has set into stone, and
> they're not deleting any mail.
>
this is a big problem. in just a 5 meg spool, there could be 300
messages or more waiting to get the X-UIDL lines, that could be much
more than just a few bytes.
> Remember, the X-UIDL additions are only updated back into the main
> spool at the end of the session. The POP session should still be able
> to complete if they're over quota provided that they deleted enough
> messages to get them back under quota. I think. That's one boundary
> condition I didn't think to test, I admit.
>
the pop session may just die, leaving a 0 byte mail spool and the full
over quota mail spool in the .pop file. now the worst part is that
local mail delivery will continue because it thinks the mailbox is
empty. so you will end up with new mail in the spool in addition to the
overquota mailspool which is still locked up in the .pop file and needs
to be manually put back in the spool. once it gets overquota, any pop
request that is not to just download and delete all message will hang
because of overquota errors.
> -- Clifton
>
> --
> Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Michael Kolos" <michael at colba dot net>
Subject: Re: Implementing user quotas / Expiring Email
Date: Thu, 11 Oct 2001 10:52:57 -0400
It is not such a rare occurance.
I have had this problem for a while - usually we get about one user per week
where I have to restore their mail spool from the .pop file. In my case,
their spool file ends up with a bunch of characters at the beginning, making
it even bigger.
At least we can still recover their mail, but it kind of defeats the purpose
of having the temp directory on a different (non quota) partition.
It would be nice if something could be done - like not putting in any X-UIDL
headers that would bring the spool overquota.
Michael Kolos
Administrateur de Réseaux
Network Administrator
ColbaNet Inc
----- Original Message -----
From: "Clifton Royston" <cliftonr at lava dot net>
To: "Steve Perrault" <sperraul at mnsi dot net>
Cc: "Subscribers of Qpopper" <qpopper at lists.pensive dot org>
Sent: Wednesday, October 10, 2001 2:33 PM
Subject: Re: Implementing user quotas / Expiring Email
> On Wed, Oct 10, 2001 at 08:25:35AM -0400, Steve Perrault wrote:
> > My concern is what occurs when a user is at quota. How does Qpopper
make
> > room to add the X-UIDL lines if the person is already at quota?
>
> This would be a problem, though it should only happen if someone is
> *exactly* a few bytes short of the hard quota, or if they have been
> over the "soft quota" long enough that it has set into stone, and
> they're not deleting any mail.
>
> Remember, the X-UIDL additions are only updated back into the main
> spool at the end of the session. The POP session should still be able
> to complete if they're over quota provided that they deleted enough
> messages to get them back under quota. I think. That's one boundary
> condition I didn't think to test, I admit.
>
> -- Clifton
>
> --
> Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
>
Date: Thu, 11 Oct 2001 16:59:26 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Implementing user quotas / Expiring Email
At 10:52 AM -0400 10/11/01, Michael Kolos wrote:
>It is not such a rare occurance.
>I have had this problem for a while - usually we get about one user per week
>where I have to restore their mail spool from the .pop file.
When Qpopper starts it checks for leftover mail in the temp drop; it
should be necessary to manually move the mail over.
> In my case,
>their spool file ends up with a bunch of characters at the beginning, making
>it even bigger.
That indicates something is wrong. The temp spool should not be
getting corrupted. Are you sure you're using the latest version of
Qpopper? I think there was an early version, perhaps 2.53, that
could create a large temp spool full of junk under some circumstances.
>It would be nice if something could be done - like not putting in any X-UIDL
>headers that would bring the spool overquota.
You mean like the 'no-status' option?
--
Date: Thu, 11 Oct 2001 14:42:32 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Implementing user quotas / Expiring Email
On Thu, Oct 11, 2001 at 04:59:26PM -0700, Randall Gellens wrote:
> At 10:52 AM -0400 10/11/01, Michael Kolos wrote:
> >It is not such a rare occurance.
> >I have had this problem for a while - usually we get about one user per week
> >where I have to restore their mail spool from the .pop file.
>
> When Qpopper starts it checks for leftover mail in the temp drop; it
> should be necessary to manually move the mail over.
^^ "NOT", right?
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Thu, 11 Oct 2001 17:53:19 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Implementing user quotas / Expiring Email
At 4:59 PM -0700 10/11/01, I mistyped:
>When Qpopper starts it checks for leftover mail in the temp drop; it
>should be necessary to manually move the mail over.
Oops. I meant to say it shouldn't be necessary.
--
From: "Michael Kolos" <michael at colba dot net>
Subject: Re: Implementing user quotas / Expiring Email
Date: Fri, 12 Oct 2001 14:17:00 -0400
----- Original Message -----
From: "Randall Gellens" <randy at qualcomm dot com>
To: "Michael Kolos" <michael at colba dot net>; "Clifton Royston"
<cliftonr at lava dot net>
Cc: "Subscribers of Qpopper" <qpopper at lists.pensive dot org>
Sent: Thursday, October 11, 2001 7:59 PM
Subject: Re: Implementing user quotas / Expiring Email
> At 10:52 AM -0400 10/11/01, Michael Kolos wrote:
> >It is not such a rare occurance.
> >I have had this problem for a while - usually we get about one user per
week
> >where I have to restore their mail spool from the .pop file.
>
> When Qpopper starts it checks for leftover mail in the temp drop; it
> should be necessary to manually move the mail over.
>
Of course qpopper can't put the spool back from the temp drop, because the
temp drop is over quota for the user.
> > In my case,
> >their spool file ends up with a bunch of characters at the beginning,
making
> >it even bigger.
>
> That indicates something is wrong. The temp spool should not be
> getting corrupted. Are you sure you're using the latest version of
> Qpopper? I think there was an early version, perhaps 2.53, that
> could create a large temp spool full of junk under some circumstances.
>
It's not the temp spool that's having the problems. That's the copy that's
not on a quota-enabled partition. It's the actual mail-spool that appears
to have this problem.
We are running 4.0.3 in standalone. Users only access the mail via pop, and
procmail delivers incoming mail.
I may have eggagerated the frequency that this happens.
We've got about 10,000 mail boxes and this may happen a few times a month at
most, probably once or twice.
I haven't been able to figure out the source, but this idea of adding the
X-UIDL headers could explain it.
I don't see why the spool file gets corrupted as a result, however, unless
qpopper meets with something weird when it goes overquota.
if I turn on no-status, it basically means that no X-UIDL headers are added,
and how exactly does that affect performance?
Thanks,
Michael
Date: Sat, 13 Oct 2001 00:39:34 +0500
From: Syed Hasan Masood <hmasood at super.net dot pk>
Subject: Quota Flush / Update Problem.
Hi All,
I am experiencing a problem with my user quotas. The situation is that I
have implemented a standard quota of 2 MB for all users, now there is
one user who does not have any mails in his mailbox but the command
"quota userid" is showing a large number os blocks of quota being used.
I have earlier used the command "quotacheck -avug" to fix this problem
and by doing this all the user quotas were flushed and return back to
normal condition, but this time this command is not updating the quota
records. kindly help me as how can i update and flush the quota records
in this scenario for any or all users.
Thanks
Regards
Hasan Masood
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: QPOPPER3 and QPOPPER4
Date: Mon, 15 Oct 2001 12:50:37 -0600
I'm just wondering if there's any possible problem with running both
QPOPPER3 and QPOPPER4 at the same time (but on different ports)? We've been
having some strange behavior, resulting in corrupted mailboxes, and so we
reverted our web-mail to QPOPPER3. While this solved the problem of the
corrupted mailboxes, I'm suspicious that some recent slow-downs of the mail
server have been due to this.
Has anyone experienced anything like this?
Thanks.
________________________
Saxon Jones
Network Administrator,
Interbaun Communications
Suite 200, 18404 Stony Plain Road
Edmonton, AB
T5S 2M8
mailto:netadmin at interbaun dot net
http://www.interbaun.com/
(780) 447-8282, ext. 369
From: Stephen Bopple <steve at bopple dot org>
Subject: getting qpopper to run initially on RH7.1
Date: Mon, 15 Oct 2001 14:47:19 -0400
Hello,
I've never used Qpopper before. I downloaded the 4.0.3-no-test tarball
and installed it on a RH7.1 box. I ran
./configure --enable-standalone enable-specialauth
and did a make install. After editiing /etc/services to make the
change from pop-3 to pop3 I can get popper to run in standalone mode.
However, connections are being refused, and port 110 is open.
I then added:
popper:all
to /etc/hosts.allow (eventhough I'm not using xinetd to launch popper)
but I still cannot get a connection to port 110.
Can anyone help?
Steve
Steve Bopple
steve at bopple dot org
www.bopple.org
www.linuxhaiku.com
From: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 15 Oct 2001 14:01:39 -0700
Subject: Re: getting qpopper to run initially on RH7.1
On Mon, 15 Oct 2001 14:47:19 -0400, Stephen Bopple wrote:
>I've never used Qpopper before. I downloaded the 4.0.3-no-test tarball
>and installed it on a RH7.1 box. I ran
>
>./configure --enable-standalone enable-specialauth
>
>and did a make install. After editiing /etc/services to make the
>change from pop-3 to pop3 I can get popper to run in standalone mode.
>However, connections are being refused, and port 110 is open.
>I then added:
>
>popper:all
>
>to /etc/hosts.allow (eventhough I'm not using xinetd to launch popper)
>but I still cannot get a connection to port 110.
Editing hosts.allow would only affect you if qpopper had linked to
tcpwrappers. I don't think it does that.
The only other thing I can think of is ipchains or netfilter. Check
your system logs to see if there are any firewall violations when you
try to connect.
You can also run tcpdump and lsof to see what your network subsystem is
doing. lsof should show the listen socket. tcpdump should show some
activity when you connect.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Last updated on 15 Oct 2001 by Pensive Mailing List Admin