The qpopper list archive ending on 23 Oct 2001
Topics covered in this issue include:
1. Re: getting qpopper to run initially on RH7.1
Randall Gellens <randy at qualcomm dot com>
Mon, 15 Oct 2001 14:00:12 -0700
2. Re: QPOPPER3 and QPOPPER4
Randall Gellens <randy at qualcomm dot com>
Mon, 15 Oct 2001 13:57:53 -0700
3. RE: QPOPPER3 and QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Mon, 15 Oct 2001 15:45:30 -0600
4. RE: QPOPPER3 and QPOPPER4
Randall Gellens <randy at qualcomm dot com>
Mon, 15 Oct 2001 15:06:55 -0700
5. Re: QPOPPER3 and QPOPPER4
Clifton Royston <cliftonr at lava dot net>
Mon, 15 Oct 2001 12:20:08 -1000
6. RE: QPOPPER3 and QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Mon, 15 Oct 2001 16:20:55 -0600
7. Re: QPOPPER3 and QPOPPER4
Randall Gellens <randy at qualcomm dot com>
Mon, 15 Oct 2001 15:32:17 -0700
8. RE: QPOPPER3 and QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Mon, 15 Oct 2001 17:23:16 -0600
9. Re: QPOPPER3 and QPOPPER4
Clifton Royston <cliftonr at lava dot net>
Mon, 15 Oct 2001 16:01:28 -1000
10. RE: QPOPPER3 and QPOPPER4
Chip Old <fold at bcpl dot net>
Mon, 15 Oct 2001 23:28:47 -0400 (EDT)
11. Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
John Hardly <jhon at iav.ac dot ma>
Tue, 16 Oct 2001 11:55:39 +0000
12. RE: trying to get qpopper working under RH7.1
Stephen Bopple <steve at bopple dot org>
Tue, 16 Oct 2001 10:24:09 -0400
13. QPOPPER3 & QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Tue, 16 Oct 2001 08:43:39 -0600
14. Re: Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
"Kenneth Porter" <shiva at well dot com>
Tue, 16 Oct 2001 10:25:41 -0700
15. RE: trying to get qpopper working under RH7.1
"Kenneth Porter" <shiva at well dot com>
Tue, 16 Oct 2001 10:31:19 -0700
16. Group Bulletins Problem
Sheryl Bruggy <sbruggy at scu.edu dot au>
Wed, 17 Oct 2001 14:40:56 +1000 (EST)
17. Re: Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
John Hardly <jhon at iav.ac dot ma>
Wed, 17 Oct 2001 13:28:31 +0000
18. RE: QPOPPER3 and QPOPPER4
MEISNER <rmeisner at meridia dot org>
Wed, 17 Oct 2001 09:54:08 -0400 (EDT)
19. RE: QPOPPER3 and QPOPPER4
MEISNER <rmeisner at meridia dot org>
Wed, 17 Oct 2001 12:04:24 -0400 (EDT)
20. RE: QPOPPER3 and QPOPPER4
Saxon Jones <SaxonJ at interbaun dot net>
Wed, 17 Oct 2001 10:14:30 -0600
21. RE: QPOPPER3 and QPOPPER4
Gregory Hicks <ghicks at cadence dot com>
Wed, 17 Oct 2001 09:19:42 -0700 (PDT)
22. RE: QPOPPER3 and QPOPPER4
Gustavo Viscaino <g_viscaino at yahoo dot com>
Wed, 17 Oct 2001 09:58:09 -0700 (PDT)
23. RE: QPOPPER3 and QPOPPER4
MEISNER <rmeisner at meridia dot org>
Wed, 17 Oct 2001 13:28:55 -0400 (EDT)
24. RE: QPOPPER3 and QPOPPER4
MEISNER <rmeisner at meridia dot org>
Wed, 17 Oct 2001 13:31:28 -0400 (EDT)
25. RE: QPOPPER3 and QPOPPER4
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Oct 2001 09:41:51 -0700
26. RE: QPOPPER3 and QPOPPER4
Gregory Hicks <ghicks at cadence dot com>
Wed, 17 Oct 2001 10:28:33 -0700 (PDT)
27. RE: QPOPPER3 and QPOPPER4
Chip Old <fold at bcpl dot net>
Wed, 17 Oct 2001 14:33:39 -0400 (EDT)
28. RE: QPOPPER3 and QPOPPER4
Gustavo Viscaino <g_viscaino at yahoo dot com>
Wed, 17 Oct 2001 11:18:55 -0700 (PDT)
29. Re: QPOPPER3 and QPOPPER4
Steven Champeon <schampeo at hesketh dot com>
Wed, 17 Oct 2001 16:39:07 -0400
30. RE: QPOPPER3 and QPOPPER4
Chip Old <fold at bcpl dot net>
Wed, 17 Oct 2001 16:18:12 -0400 (EDT)
31. Problem with the Qpopper 4.03 with open SSL enabled
"Mei-hwa Huang" <mhuang at uta dot edu>
Wed, 17 Oct 2001 16:08:55 -0500
32. Unable to open Bulletin database
Mike <mfahey at enter dot net>
Wed, 17 Oct 2001 18:52:59 -0400 (EDT)
33. Re: QPOPPER3 and QPOPPER4
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Oct 2001 18:04:27 -0700
34. Re: Unable to open Bulletin database
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Oct 2001 18:07:32 -0700
35. Re: Group Bulletins Problem
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Oct 2001 18:01:19 -0700
36. FreeBSD home dir mail
"Matthew Koch" <mattkoch at genevaonline dot com>
Thu, 18 Oct 2001 08:30:33 -0500
37. Re: Unable to open Bulletin database
Mike <mfahey at enter dot net>
Thu, 18 Oct 2001 14:23:15 -0400 (EDT)
38. Re: FreeBSD home dir mail
Clifton Royston <cliftonr at lava dot net>
Thu, 18 Oct 2001 10:28:24 -1000
39. Re: Problem with the Qpopper 4.03 with open SSL enabled
"Kenneth Porter" <shiva at well dot com>
Thu, 18 Oct 2001 13:30:26 -0700
40. setting up RH7.1 rpm
"Adrian Bolzan" <Adrian.Bolzan at aot.com dot au>
Fri, 19 Oct 2001 09:51:09 +1000
41. Re: setting up RH7.1 rpm
"Adrian Bolzan" <Adrian.Bolzan at aot.com dot au>
Fri, 19 Oct 2001 11:10:11 +1000
42. Limit qpopper to SSL?
Kim Scarborough <lists at jinx.unknown dot nu>
Tue, 23 Oct 2001 11:01:08 -0500 (CDT)
43. Re: Limit qpopper to SSL?
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 23 Oct 2001 18:59:46 +0000
44. Re: Limit qpopper to SSL?
Kim Scarborough <lists at jinx.unknown dot nu>
Tue, 23 Oct 2001 12:15:17 -0500 (CDT)
45. folder internal data
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 23 Oct 2001 19:30:46 +0000
46. Re: Limit qpopper to SSL?
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Tue, 23 Oct 2001 19:46:40 +0000
47. Re: Limit qpopper to SSL?
Kim Scarborough <lists at jinx.unknown dot nu>
Tue, 23 Oct 2001 13:05:58 -0500 (CDT)
48. Re: folder internal data
Clifton Royston <cliftonr at lava dot net>
Tue, 23 Oct 2001 08:09:57 -1000
49. Re: folder internal data
Kim Scarborough <lists at jinx.unknown dot nu>
Tue, 23 Oct 2001 13:03:20 -0500 (CDT)
50. Re: folder internal data
Gregory Hicks <ghicks at cadence dot com>
Tue, 23 Oct 2001 12:50:37 -0700 (PDT)
Date: Mon, 15 Oct 2001 14:00:12 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: getting qpopper to run initially on RH7.1
At 2:47 PM -0400 10/15/01, Stephen Bopple wrote:
>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?
Since you specified standalone mode, you need to run qpopper. (You
probably also want this to be done in an rc file at system boot).
Also, there is usually no need for '--enable-specialauth', since the
configure script is generally able to figure out if shadow passwords
are in use.
--
Date: Mon, 15 Oct 2001 13:57:53 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: QPOPPER3 and QPOPPER4
At 12:50 PM -0600 10/15/01, Saxon Jones wrote:
>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.
I can't see why having both versions running would cause any
problems, especially corrupted mailboxes. (Running a newer version
on an alternate port is a common way to try out an update before
committing to it.)
If you are going to pick one version, I'd suggest 4 instead of 3.
If you're pretty sure that the mailbox corruption happens as a result
of running both, can you try and get a debug trace of it happening?
--
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: RE: QPOPPER3 and QPOPPER4
Date: Mon, 15 Oct 2001 15:45:30 -0600
Thanks for the reply... The mailbox corruption was happening when we run
our web mail service on QPOPPER4, our regular mail users weren't having a
problem. Right now we've moved our web mail back to QPOPPER3 and so I don't
expect to be able to get any debug info in the near future.
________________________
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
-----Original Message-----
From: Randall Gellens [mailto:randy at qualcomm dot com]
Sent: Monday, October 15, 2001 2:58 PM
To: Saxon Jones; QPopper Mailing List
Subject: Re: QPOPPER3 and QPOPPER4
At 12:50 PM -0600 10/15/01, Saxon Jones wrote:
>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.
I can't see why having both versions running would cause any
problems, especially corrupted mailboxes. (Running a newer version
on an alternate port is a common way to try out an update before
committing to it.)
If you are going to pick one version, I'd suggest 4 instead of 3.
If you're pretty sure that the mailbox corruption happens as a result
of running both, can you try and get a debug trace of it happening?
--
Date: Mon, 15 Oct 2001 15:06:55 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: RE: QPOPPER3 and QPOPPER4
At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
>The mailbox corruption was happening when we run
>our web mail service on QPOPPER4, our regular mail users weren't having a
>problem. Right now we've moved our web mail back to QPOPPER3 and so I don't
>expect to be able to get any debug info in the near future.
I don't see why you'd get corruption using Qpopper version 4 but not
3 as long as the web mail service is using POP (or even i it's going
at the spools directly). Could there be other differences, such as
different lock methods?
--
Date: Mon, 15 Oct 2001 12:20:08 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: QPOPPER3 and QPOPPER4
On Mon, Oct 15, 2001 at 03:45:30PM -0600, Saxon Jones wrote:
> Thanks for the reply... The mailbox corruption was happening when we run
> our web mail service on QPOPPER4, our regular mail users weren't having a
> problem. Right now we've moved our web mail back to QPOPPER3 and so I don't
> expect to be able to get any debug info in the near future.
Are your webmail users accessing it via an IMAP daemon?
If so, was qpopper4 running in server mode, and is qpopper3 *not*
running in server mode?
I asked some questions a while back about whether qpopper server mode
was compatible with running an IMAP daemon, and didn't get an answer.
We haven't tested that out here yet, but I'm starting to suspect that
it may not be. The current qpopper assumption that it can unlock the
spool during the POP session then relock it and update it in place may
simply be faulty if IMAP is involved.
I'd like to get this one sorted out soon, since we are about to
implement webmail here too.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: RE: QPOPPER3 and QPOPPER4
Date: Mon, 15 Oct 2001 16:20:55 -0600
There are, in fact, different lock methods between our QPOPPER3
(.username.pop) and QPOPPER4 (/Mail/db/pop-lockedout) setups. But the
corruption happened most noticeably when all users were using QPOPPER4.
Since we don't have a whole lot of web mail users, we didn't notice it in
our initial tests when we had only web mail users using QPOPPER4, and
regulars on QPOPPER3.
________________________
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
-----Original Message-----
From: Randall Gellens [mailto:randy at qualcomm dot com]
Sent: Monday, October 15, 2001 4:07 PM
To: Saxon Jones; QPopper Mailing List
Subject: RE: QPOPPER3 and QPOPPER4
At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
>The mailbox corruption was happening when we run
>our web mail service on QPOPPER4, our regular mail users weren't having a
>problem. Right now we've moved our web mail back to QPOPPER3 and so I
don't
>expect to be able to get any debug info in the near future.
I don't see why you'd get corruption using Qpopper version 4 but not
3 as long as the web mail service is using POP (or even i it's going
at the spools directly). Could there be other differences, such as
different lock methods?
--
Date: Mon, 15 Oct 2001 15:32:17 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: QPOPPER3 and QPOPPER4
At 12:20 PM -1000 10/15/01, Clifton Royston wrote:
> I asked some questions a while back about whether qpopper server mode
>was compatible with running an IMAP daemon, and didn't get an answer.
Server mode assumes that the spool is only accessed by Qpopper and a
local delivery agent (which only appends to it). If any other
process accesses the spool, server mode must not be used. So, IMAP
access is incompatible with server mode.
There was a suggestion some months ago to have an option in Qpopper
to keep the spool locked for the duration of the session. That would
permit other processes which may access the spool (such as an IMAP
daemon) to run with Qpopper.
--
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: RE: QPOPPER3 and QPOPPER4
Date: Mon, 15 Oct 2001 17:23:16 -0600
There is no IMAP at my location. Server mode is enabled, though I don't
know why that would affect anything.
________________________
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
-----Original Message-----
From: Clifton Royston [mailto:cliftonr at lava dot net]
Sent: Monday, October 15, 2001 4:20 PM
To: Saxon Jones
Cc: 'Randall Gellens'; QPopper Mailing List
Subject: Re: QPOPPER3 and QPOPPER4
On Mon, Oct 15, 2001 at 03:45:30PM -0600, Saxon Jones wrote:
> Thanks for the reply... The mailbox corruption was happening when we run
> our web mail service on QPOPPER4, our regular mail users weren't having a
> problem. Right now we've moved our web mail back to QPOPPER3 and so I
don't
> expect to be able to get any debug info in the near future.
Are your webmail users accessing it via an IMAP daemon?
If so, was qpopper4 running in server mode, and is qpopper3 *not*
running in server mode?
I asked some questions a while back about whether qpopper server mode
was compatible with running an IMAP daemon, and didn't get an answer.
We haven't tested that out here yet, but I'm starting to suspect that
it may not be. The current qpopper assumption that it can unlock the
spool during the POP session then relock it and update it in place may
simply be faulty if IMAP is involved.
I'd like to get this one sorted out soon, since we are about to
implement webmail here too.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Mon, 15 Oct 2001 16:01:28 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: QPOPPER3 and QPOPPER4
On Mon, Oct 15, 2001 at 05:23:16PM -0600, Saxon Jones wrote:
> There is no IMAP at my location. Server mode is enabled, though I don't
> know why that would affect anything.
Parenthetical: What type of webmail package are you running, then?
Nearly all the ones I've looked at (Twig, Imp, Silkymail, Squirrelmail)
use IMAP as their interface to the mailspool.
However, if you're using a different locking mechanism between qpopper3
and qpopper4 as you mentioned, and qpopper4 has the problems, then it's
almost certain that qpopper3 has the right locking mechanism (i.e. same
as the rest of your mail software) and qpopper4 is using a different
locking method than the rest of your mail software.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Mon, 15 Oct 2001 23:28:47 -0400 (EDT)
From: Chip Old <fold at bcpl dot net>
Subject: RE: QPOPPER3 and QPOPPER4
On Mon, 15 Oct 2001, Saxon Jones wrote:
> But the corruption happened most noticeably when all users were using
> QPOPPER4. Since we don't have a whole lot of web mail users, we didn't
> notice it in our initial tests when we had only web mail users using
> QPOPPER4, and regulars on QPOPPER3.
What webmail application do you use? About 2000 of our customers use
WebMail from Infinite Technologies with QPopper 4.0.3 without any
problems, in addition to another 6000 or so customers using a wide variety
of Mac and PC based POP3 clients. The only differences between our setup
and what you've described of yours: We don't run QPopper in server mode
(but I don't see why that should matter as long as your mail spool is
accessed only by QPopper and your local MDA), and we use the standard
.user.pop temp files and user.lock.
--
Chip Old (Francis E. Old) E-Mail: fold at bcpl dot net
Manager, BCPL Network Services Phone: 410-887-6180
Manager, BCPL.NET Internet Services FAX: 410-887-2091
320 York Road
Towson, MD 21204 USA
Date: Tue, 16 Oct 2001 11:55:39 +0000
From: John Hardly <jhon at iav.ac dot ma>
Subject: Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
Hi All,
I want to compile qpopper 4.0.3 with the following options:
./configure --enable-debugging --enable-apop --enable-auto-delete
--enable-log-facility=LOG_LOCAL5 --enable-log-login
--enable-nonauth-file=/usr/local/etc/pop-exclude --enable-popuid=pop
--enable-specialauth --enable-timing --with-openssl=/usr/local/openssl
Here are my two questions:
1-
Willing to compile Qpopper 4.0.3 on RH 6.2 to support TLS/SSL (using the Opessl),
"make" exits with the following message:
------------------
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX maillock.c -o
maillock.o
gcc -c -I.. -I. -I.. -I../popper \
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX logit.c -o
logit.o
gcc -c -I.. -I. -I.. -I../popper \
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX snprintf.c -o
snprintf.o
gcc -c -I.. -I. -I.. -I../popper \
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX string_util.c
-o string_util.o
gcc -c -I.. -I. -I.. -I../popper \
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX check_group.c
-o check_group.o
gcc -c -I.. -I. -I.. -I../popper \
-g -O2 -idirafter /usr/local/include -DHAVE_CONFIG_H -DLINUX -DUNIX utils.c -o
utils.o
make[2]: *** Warning: Clock skew detected. Your build may be incomplete.
make[2]: Leaving directory `/home/john/qpopper/qpopper4.0.3/common'
gcc pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o pop_init.o
pop_last.o pop_list.o pop_log.o pop_lower.o pop_msg.o pop_parse.o pop_pass.o pop_quit.o
pop_rset.o pop_send.o pop_stat.o pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o popper.o
pop_bull.o xtnd_xlst.o pop_uidl.o mktemp.o pop_rpop.o pop_apop.o md5.o pop_auth.o
pop_pope.o pop_extend.o scram.o hmac.o base64.o pop_util.o get_sub_opt.o msg_ptr.o
drac.o pop_config.o pop_tls.o pop_tls_openssl.o pop_tls_sslplus.o sslplus_utils.o main.o
pop_cache.o genpath.o -o popper ../mmangle/libmangle.a \
-I../common ../common/libcommon.a \
-lresolv -lgdbm -lcrypt -L/usr/local/openssl/lib -lssl -lcrypto
/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':
dso_dlfcn.o(.text+0x99): undefined reference to `dlopen'
dso_dlfcn.o(.text+0xa8): undefined reference to `dlopen'
dso_dlfcn.o(.text+0xfd): undefined reference to `dlclose'
/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_var':
dso_dlfcn.o(.text+0x1a3): undefined reference to `dlsym'
/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func':
dso_dlfcn.o(.text+0x253): undefined reference to `dlsym'
/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload':
dso_dlfcn.o(.text+0x332): undefined reference to `dlclose'
collect2: ld returned 1 exit status
make[1]: *** [popper] Error 1
make[1]: Leaving directory `/home/john/qpopper/qpopper4.0.3/popper'
make: *** [popper_server] Error 2
-------------------------------
I'm using Openssl 0.9.6b ,include and lib files resides on the /usr/local/openssl directory.
Can anyone tells what's going wrong with make here?
2-
When I compile Qpopper (4.0.3) to log to a different log file (using the
--enable-log-facility=LOG_LOCAL5),
it STILL logs to the /var/log/messages !!!
How to prevent this ? i.e: I only want qpopper to log to the file I specified with the LOG_LOCAL5
NOT logging
to two log files.
./John.
--
John Hardly
E-mail : john (at) iav (dot) ac (dot) ma
From: Stephen Bopple <steve at bopple dot org>
Subject: RE: trying to get qpopper working under RH7.1
Date: Tue, 16 Oct 2001 10:24:09 -0400
I got qpopper working on the RH7.1 box
I wasn't aware until I ran 'ipchains -L' that someone had setup a
firewalling script on the webhosting box. I added two rules to permit
syn tcp requests over ports 110 and 143. For giggles I also deleted
and reinstalled qpopper with the 'enable-standalone' and 'enable-
debugging' flags for configuration.
Finally I added this to rc.local
/usr/local/sbin/popper 63.90.248.133:110 -S
and rebooted. I just sent some email and grabbed it from the webserver
using Eudora, no problems.
Steve Bopple
steve at bopple dot org
www.bopple.org
www.linuxhaiku.com
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: QPOPPER3 & QPOPPER4
Date: Tue, 16 Oct 2001 08:43:39 -0600
Thanks for all of your responses. I'm going to try QPOPPER4 again with the
same locking scheme as QPOPPER3 was using, and see what that does.
________________________
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: "Kenneth Porter" <shiva at well dot com>
Date: Tue, 16 Oct 2001 10:25:41 -0700
Subject: Re: Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
On Tue, 16 Oct 2001 11:55:39 +0000, John Hardly wrote:
>/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':
>dso_dlfcn.o(.text+0x99): undefined reference to `dlopen'
>dso_dlfcn.o(.text+0xfd): undefined reference to `dlclose'
>dso_dlfcn.o(.text+0x1a3): undefined reference to `dlsym'
You're missing some library that provides dlopen, dlclose, and dlsym.
I'd guess those are part of the dynamic loader stuff, perhaps part of
libtool.
> When I compile Qpopper (4.0.3) to log to a different log file (using the
>--enable-log-facility=LOG_LOCAL5),
>it STILL logs to the /var/log/messages !!!
> How to prevent this ? i.e: I only want qpopper to log to the file I specified with the LOG_LOCAL5
>NOT logging
>to two log files.
That's a syslog issue. Read the man page for syslog.conf. You probably
need to add local5.none to the line that selects items to log to
/var/log/messages.
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: "Kenneth Porter" <shiva at well dot com>
Date: Tue, 16 Oct 2001 10:31:19 -0700
Subject: RE: trying to get qpopper working under RH7.1
On Tue, 16 Oct 2001 10:24:09 -0400, Stephen Bopple wrote:
>I got qpopper working on the RH7.1 box
>
>I wasn't aware until I ran 'ipchains -L' that someone had setup a
>firewalling script on the webhosting box.
Yep, Red Hat started providing a default firewall rule set with 7.x, to
protect newbies from just connecting a wide-open, very powerful box to
the Internet. Before that, it was too easy to shoot yourself and all
your neighbors in the foot. (Script kiddies LOVE to get control of
Linux zombies because they're such powerful systems to launch attacks
from. They'll share their Windoze zombies but they jealously guard
their Linux "acquisitions".)
I'd recommend installing the Logwatch package or some similar
log-monitoring system, so you'll get frequent reports of what's probing
your firewall. Logwatch is a package of Perl scripts that runs from a
nightly cron job, filters your logs of routine uninteresting stuff,
agregates what's left, and mails it to an admin for analysis. I think
you'll find it on the Red Hat PowerTools CD.
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: Wed, 17 Oct 2001 14:40:56 +1000 (EST)
From: Sheryl Bruggy <sbruggy at scu.edu dot au>
Subject: Group Bulletins Problem
I have recently changed our Qpopper program to enable Group Bulletins.
We have used the standard bulletin board system for some time and it is
a great help in reducing the number of emails being sent out at one
time, as we have a large number of accounts. We also have our staff and
students distributed over a number of campuses and I thought it would be
nice to have a bulletin board set up for each campus as well as the
central system.
However, the group bulletins are not working.
Those groups with only a few entries work fine, but most of our groups
have several thousand entries (split into multiple lines with the same
gid). I have seen some discussion in the past about the limits to the
number of users in a group being set by the sys/limits.h file and the
getgrent(3) and associated functions which are used by this program. It
appears that the getgrid function only returns the FIRST group in the
database with that gid. So, I am assuming that if your name is not in
the first line in /etc/group, you will not get the bulletin.
I have tried setting the primary group (in /etc/passwd) as suggested in
the pop_bull.c program. But that doesnt work either.
Has anyone else had the same problem?
BTW: We are using Tru64 Unix (4.0F) and Qpopper 3.12
Regards
Sheryl Bruggy
Systems/Network Administrator - Unix
._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
Date: Wed, 17 Oct 2001 13:28:31 +0000
From: John Hardly <jhon at iav.ac dot ma>
Subject: Re: Qpopper 4.0.3 + RedHat 6.2 (TLS/SSL)
Tyanks kenneth.
> >/usr/local/openssl/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':
> >dso_dlfcn.o(.text+0x99): undefined reference to `dlopen'
> >dso_dlfcn.o(.text+0xfd): undefined reference to `dlclose'
> >dso_dlfcn.o(.text+0x1a3): undefined reference to `dlsym'
>
> You're missing some library that provides dlopen, dlclose, and dlsym.
> I'd guess those are part of the dynamic loader stuff, perhaps part of
> libtool.
Great, It works now. I installed autoconf , automake and libtools rpms ; recompiled
the openssl. finally I compiled qpopper 4.0.3 without any problem.
Thanks.
> > When I compile Qpopper (4.0.3) to log to a different log file (using the
> >--enable-log-facility=LOG_LOCAL5),
> >it STILL logs to the /var/log/messages !!!
> > How to prevent this ? i.e: I only want qpopper to log to the file I specified with the LOG_LOCAL5
> >NOT logging
> >to two log files.
>
> That's a syslog issue. Read the man page for syslog.conf. You probably
> need to add local5.none to the line that selects items to log to
> /var/log/messages.
Adding the line to syslog.conf resolved my problem :-)
> 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.]
--
John Hardly
E-mail : john (at) iav (dot) ac (dot) ma
Date: Wed, 17 Oct 2001 09:54:08 -0400 (EDT)
From: MEISNER <rmeisner at meridia dot org>
Subject: RE: QPOPPER3 and QPOPPER4
Hi,
I am new to this newslisting. I have received this exact email from you
at least 50 times in the last several days. I'm wondering if you would
look to see if you could remove it from your queue files.
Thank you very much,
Robin Wells-Meisner
Sr. Systems Analyst
Cleveland Clinic
rmeisner at meridia dot org
On Mon, 15 Oct 2001, Saxon Jones wrote:
> There are, in fact, different lock methods between our QPOPPER3
> (.username.pop) and QPOPPER4 (/Mail/db/pop-lockedout) setups. But the
> corruption happened most noticeably when all users were using QPOPPER4.
> Since we don't have a whole lot of web mail users, we didn't notice it in
> our initial tests when we had only web mail users using QPOPPER4, and
> regulars on QPOPPER3.
>
> ________________________
> 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
>
> -----Original Message-----
> From: Randall Gellens [mailto:randy at qualcomm dot com]
> Sent: Monday, October 15, 2001 4:07 PM
> To: Saxon Jones; QPopper Mailing List
> Subject: RE: QPOPPER3 and QPOPPER4
>
> At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> >The mailbox corruption was happening when we run
> >our web mail service on QPOPPER4, our regular mail users weren't having a
> >problem. Right now we've moved our web mail back to QPOPPER3 and so I
> don't
> >expect to be able to get any debug info in the near future.
>
> I don't see why you'd get corruption using Qpopper version 4 but not
> 3 as long as the web mail service is using POP (or even i it's going
> at the spools directly). Could there be other differences, such as
> different lock methods?
> --
>
Date: Wed, 17 Oct 2001 12:04:24 -0400 (EDT)
From: MEISNER <rmeisner at meridia dot org>
Subject: RE: QPOPPER3 and QPOPPER4
Since I have already deleted the 50 or so of this message, I have, in the
last couple hours, received this message again, twice. Could you please
check with your email admin to see if they can halt it from sending
THANK YOU
On Mon, 15 Oct 2001, Saxon Jones wrote:
> There are, in fact, different lock methods between our QPOPPER3
> (.username.pop) and QPOPPER4 (/Mail/db/pop-lockedout) setups. But the
> corruption happened most noticeably when all users were using QPOPPER4.
> Since we don't have a whole lot of web mail users, we didn't notice it in
> our initial tests when we had only web mail users using QPOPPER4, and
> regulars on QPOPPER3.
>
> ________________________
> 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
>
> -----Original Message-----
> From: Randall Gellens [mailto:randy at qualcomm dot com]
> Sent: Monday, October 15, 2001 4:07 PM
> To: Saxon Jones; QPopper Mailing List
> Subject: RE: QPOPPER3 and QPOPPER4
>
> At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> >The mailbox corruption was happening when we run
> >our web mail service on QPOPPER4, our regular mail users weren't having a
> >problem. Right now we've moved our web mail back to QPOPPER3 and so I
> don't
> >expect to be able to get any debug info in the near future.
>
> I don't see why you'd get corruption using Qpopper version 4 but not
> 3 as long as the web mail service is using POP (or even i it's going
> at the spools directly). Could there be other differences, such as
> different lock methods?
> --
>
From: Saxon Jones <SaxonJ at interbaun dot net>
Subject: RE: QPOPPER3 and QPOPPER4
Date: Wed, 17 Oct 2001 10:14:30 -0600
Correct me if I'm wrong, but if there was a problem would it not be on your
end? If it was a problem with the mailing list, I'd see it coming into my
mailbox too, and I don't. If it was a problem with me, it would either
affect the entire mailing list (and therefore show up in my mailbox as
well), or only be affecting Randall.
In any case, I can confirm there's no email in my mail server's queue
destined for meridia.org.
________________________
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
-----Original Message-----
From: MEISNER [mailto:rmeisner at meridia dot org]
Sent: Wednesday, October 17, 2001 10:04 AM
To: Saxon Jones
Cc: 'Randall Gellens'; QPopper Mailing List
Subject: RE: QPOPPER3 and QPOPPER4
Since I have already deleted the 50 or so of this message, I have, in the
last couple hours, received this message again, twice. Could you please
check with your email admin to see if they can halt it from sending
THANK YOU
On Mon, 15 Oct 2001, Saxon Jones wrote:
> There are, in fact, different lock methods between our QPOPPER3
> (.username.pop) and QPOPPER4 (/Mail/db/pop-lockedout) setups. But the
> corruption happened most noticeably when all users were using QPOPPER4.
> Since we don't have a whole lot of web mail users, we didn't notice it in
> our initial tests when we had only web mail users using QPOPPER4, and
> regulars on QPOPPER3.
>
> ________________________
> 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
>
> -----Original Message-----
> From: Randall Gellens [mailto:randy at qualcomm dot com]
> Sent: Monday, October 15, 2001 4:07 PM
> To: Saxon Jones; QPopper Mailing List
> Subject: RE: QPOPPER3 and QPOPPER4
>
> At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> >The mailbox corruption was happening when we run
> >our web mail service on QPOPPER4, our regular mail users weren't having a
> >problem. Right now we've moved our web mail back to QPOPPER3 and so I
> don't
> >expect to be able to get any debug info in the near future.
>
> I don't see why you'd get corruption using Qpopper version 4 but not
> 3 as long as the web mail service is using POP (or even i it's going
> at the spools directly). Could there be other differences, such as
> different lock methods?
> --
>
Date: Wed, 17 Oct 2001 09:19:42 -0700 (PDT)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: RE: QPOPPER3 and QPOPPER4
> Date: Wed, 17 Oct 2001 12:04:24 -0400 (EDT)
> From: MEISNER <rmeisner at meridia dot org>
> To: Saxon Jones <SaxonJ at interbaun dot net>
> cc: "'Randall Gellens'" <randy at qualcomm dot com>, QPopper Mailing List
<qpopper at lists.pensive dot org>
> Subject: RE: QPOPPER3 and QPOPPER4
>
> Since I have already deleted the 50 or so of this message, I have, in
the
> last couple hours, received this message again, twice. Could you
please
> check with your email admin to see if they can halt it from sending
>
> THANK YOU
I'll bet the message shows up each time you check mail and your desktop
machine was checking mail all night long...
Although I have no connection w/Qualcomm and Randy, I'll throw my own
$0.02 worth in here.
Each instance of this type of behaviour I have seen in the past (w/over
8,000 users and I'm one of three Postmasters - we get *ALL* the mail
problems) is caused by a corrupted mail spool or inbox.
The message shows up each time you check your mail spool - no matter how
frequently - and cannot be deleted.
The fix is to lock your mail spool (usually with a "touch user.lock"
file) and then try and find the offending message. If you can, fix it
up or delete the entire message (from the line beginning "^From ..." to
the next "^From ..." (^ means 'anchor at beginning of line. Also note
the SPACE after the word From...)
If this doesn't fix it, check your "Inbox" (Netscape), "Inbox.mbx"
(Eudora)... You could try rebuilding the index files for these
.Inbox.summary (Netscape)
Inbox.toc (Eudora)
Just some thoughts on where to look... I could be wrong - and have been
wrong in the past - but your description sounds like...
Regards,
Gregory Hicks
Postmaster, Cadence.COM
---------------------------------------------------------------------
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
"I worry about my child and the Internet all the time, even though
she's too young to have logged on yet. Here's what I worry about. I
worry that 10 or 15 years from now, she will come to me and say 'Daddy,
where were you when they took freedom of the press away from the
Internet?'" --from the Cryptography list
Date: Wed, 17 Oct 2001 09:58:09 -0700 (PDT)
From: Gustavo Viscaino <g_viscaino at yahoo dot com>
Subject: RE: QPOPPER3 and QPOPPER4
I'm not getting duplicate messages either.
Gustavo Viscaino
--- Saxon Jones <SaxonJ at interbaun dot net> wrote:
> Correct me if I'm wrong, but if there was a problem
> would it not be on your
> end? If it was a problem with the mailing list, I'd
> see it coming into my
> mailbox too, and I don't. If it was a problem with
> me, it would either
> affect the entire mailing list (and therefore show
> up in my mailbox as
> well), or only be affecting Randall.
>
> In any case, I can confirm there's no email in my
> mail server's queue
> destined for meridia.org.
>
> ________________________
> 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
>
> -----Original Message-----
> From: MEISNER [mailto:rmeisner at meridia dot org]
> Sent: Wednesday, October 17, 2001 10:04 AM
> To: Saxon Jones
> Cc: 'Randall Gellens'; QPopper Mailing List
> Subject: RE: QPOPPER3 and QPOPPER4
>
> Since I have already deleted the 50 or so of this
> message, I have, in the
> last couple hours, received this message again,
> twice. Could you please
> check with your email admin to see if they can halt
> it from sending
>
> THANK YOU
>
>
> On Mon, 15 Oct 2001, Saxon Jones wrote:
>
> > There are, in fact, different lock methods between
> our QPOPPER3
> > (.username.pop) and QPOPPER4
> (/Mail/db/pop-lockedout) setups. But the
> > corruption happened most noticeably when all users
> were using QPOPPER4.
> > Since we don't have a whole lot of web mail users,
> we didn't notice it in
> > our initial tests when we had only web mail users
> using QPOPPER4, and
> > regulars on QPOPPER3.
> >
> > ________________________
> > 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
> >
> > -----Original Message-----
> > From: Randall Gellens [mailto:randy at qualcomm dot com]
> > Sent: Monday, October 15, 2001 4:07 PM
> > To: Saxon Jones; QPopper Mailing List
> > Subject: RE: QPOPPER3 and QPOPPER4
> >
> > At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> > >The mailbox corruption was happening when we run
> > >our web mail service on QPOPPER4, our regular
> mail users weren't having a
> > >problem. Right now we've moved our web mail back
> to QPOPPER3 and so I
> > don't
> > >expect to be able to get any debug info in the
> near future.
> >
> > I don't see why you'd get corruption using Qpopper
> version 4 but not
> > 3 as long as the web mail service is using POP (or
> even i it's going
> > at the spools directly). Could there be other
> differences, such as
> > different lock methods?
> > --
> >
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Date: Wed, 17 Oct 2001 13:28:55 -0400 (EDT)
From: MEISNER <rmeisner at meridia dot org>
Subject: RE: QPOPPER3 and QPOPPER4
Actually, no, I have been traveling around different hospitals so,
no "desktop". I have been reading all my mail via a PINE session.
I wish I knew what this was. Later on, given "spare time" I'll look
at your solution.
Thanks!
Robin
On Wed, 17 Oct 2001, Gregory Hicks wrote:
>
> > Date: Wed, 17 Oct 2001 12:04:24 -0400 (EDT)
> > From: MEISNER <rmeisner at meridia dot org>
> > To: Saxon Jones <SaxonJ at interbaun dot net>
> > cc: "'Randall Gellens'" <randy at qualcomm dot com>, QPopper Mailing List
> <qpopper at lists.pensive dot org>
> > Subject: RE: QPOPPER3 and QPOPPER4
> >
> > Since I have already deleted the 50 or so of this message, I have, in
> the
> > last couple hours, received this message again, twice. Could you
> please
> > check with your email admin to see if they can halt it from sending
> >
> > THANK YOU
>
> I'll bet the message shows up each time you check mail and your desktop
> machine was checking mail all night long...
>
> Although I have no connection w/Qualcomm and Randy, I'll throw my own
> $0.02 worth in here.
>
> Each instance of this type of behaviour I have seen in the past (w/over
> 8,000 users and I'm one of three Postmasters - we get *ALL* the mail
> problems) is caused by a corrupted mail spool or inbox.
>
> The message shows up each time you check your mail spool - no matter how
> frequently - and cannot be deleted.
>
> The fix is to lock your mail spool (usually with a "touch user.lock"
> file) and then try and find the offending message. If you can, fix it
> up or delete the entire message (from the line beginning "^From ..." to
> the next "^From ..." (^ means 'anchor at beginning of line. Also note
> the SPACE after the word From...)
>
> If this doesn't fix it, check your "Inbox" (Netscape), "Inbox.mbx"
> (Eudora)... You could try rebuilding the index files for these
>
> .Inbox.summary (Netscape)
> Inbox.toc (Eudora)
>
> Just some thoughts on where to look... I could be wrong - and have been
> wrong in the past - but your description sounds like...
>
> Regards,
> Gregory Hicks
> Postmaster, Cadence.COM
> ---------------------------------------------------------------------
> 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
>
> "I worry about my child and the Internet all the time, even though
> she's too young to have logged on yet. Here's what I worry about. I
> worry that 10 or 15 years from now, she will come to me and say 'Daddy,
> where were you when they took freedom of the press away from the
> Internet?'" --from the Cryptography list
>
>
Date: Wed, 17 Oct 2001 13:31:28 -0400 (EDT)
From: MEISNER <rmeisner at meridia dot org>
Subject: RE: QPOPPER3 and QPOPPER4
Thanks for all the helpful friendly messages.
My apologies to you/your list
Robin
On Wed, 17 Oct 2001, Gustavo Viscaino wrote:
> I'm not getting duplicate messages either.
>
> Gustavo Viscaino
>
> --- Saxon Jones <SaxonJ at interbaun dot net> wrote:
> > Correct me if I'm wrong, but if there was a problem
> > would it not be on your
> > end? If it was a problem with the mailing list, I'd
> > see it coming into my
> > mailbox too, and I don't. If it was a problem with
> > me, it would either
> > affect the entire mailing list (and therefore show
> > up in my mailbox as
> > well), or only be affecting Randall.
> >
> > In any case, I can confirm there's no email in my
> > mail server's queue
> > destined for meridia.org.
> >
> > ________________________
> > 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
> >
> > -----Original Message-----
> > From: MEISNER [mailto:rmeisner at meridia dot org]
> > Sent: Wednesday, October 17, 2001 10:04 AM
> > To: Saxon Jones
> > Cc: 'Randall Gellens'; QPopper Mailing List
> > Subject: RE: QPOPPER3 and QPOPPER4
> >
> > Since I have already deleted the 50 or so of this
> > message, I have, in the
> > last couple hours, received this message again,
> > twice. Could you please
> > check with your email admin to see if they can halt
> > it from sending
> >
> > THANK YOU
> >
> >
> > On Mon, 15 Oct 2001, Saxon Jones wrote:
> >
> > > There are, in fact, different lock methods between
> > our QPOPPER3
> > > (.username.pop) and QPOPPER4
> > (/Mail/db/pop-lockedout) setups. But the
> > > corruption happened most noticeably when all users
> > were using QPOPPER4.
> > > Since we don't have a whole lot of web mail users,
> > we didn't notice it in
> > > our initial tests when we had only web mail users
> > using QPOPPER4, and
> > > regulars on QPOPPER3.
> > >
> > > ________________________
> > > 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
> > >
> > > -----Original Message-----
> > > From: Randall Gellens [mailto:randy at qualcomm dot com]
> > > Sent: Monday, October 15, 2001 4:07 PM
> > > To: Saxon Jones; QPopper Mailing List
> > > Subject: RE: QPOPPER3 and QPOPPER4
> > >
> > > At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> > > >The mailbox corruption was happening when we run
> > > >our web mail service on QPOPPER4, our regular
> > mail users weren't having a
> > > >problem. Right now we've moved our web mail back
> > to QPOPPER3 and so I
> > > don't
> > > >expect to be able to get any debug info in the
> > near future.
> > >
> > > I don't see why you'd get corruption using Qpopper
> > version 4 but not
> > > 3 as long as the web mail service is using POP (or
> > even i it's going
> > > at the spools directly). Could there be other
> > differences, such as
> > > different lock methods?
> > > --
> > >
>
>
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
>
Date: Wed, 17 Oct 2001 09:41:51 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: RE: QPOPPER3 and QPOPPER4
At 9:54 AM -0400 10/17/01, MEISNER wrote:
> Hi,
> I am new to this newslisting. I have received this exact email from you
> at least 50 times in the last several days. I'm wondering if you would
> look to see if you could remove it from your queue files.
It's very hard to tell anything without seeing the full headers of
the email. Please forward a copy, being sure to include the full set
of headers, especially all 'Received' headers, to
<listmaster at lists.pensive dot org>. There is no need to send this to
the list itself, just to the listmaster.
Also, be sure that the messages are in fact duplicates and not merely
replies in a long thread.
Date: Wed, 17 Oct 2001 10:28:33 -0700 (PDT)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: RE: QPOPPER3 and QPOPPER4
> Date: Wed, 17 Oct 2001 13:28:55 -0400 (EDT)
> From: MEISNER <rmeisner at meridia dot org>
>
> Actually, no, I have been traveling around different hospitals so,
> no "desktop". I have been reading all my mail via a PINE session.
> I wish I knew what this was. Later on, given "spare time" I'll look
> at your solution.
The last thing I would check - if you can and have the access to do so
- is to check the sendmail logs for your mail server. It may be a
problem with the sending mailserver (perhaps an upstream from
meridia.org) or receiving sendmail such that sendmail is not properly
recognizing the end of message, times out, and the sending server is
requeing the message...
However, if this were the case, I'd expect that ALL messages would be
duplicated...
Still something to check.
Regards,
Gregory Hicks
> Thanks!
> Robin
>
>
> On Wed, 17 Oct 2001, Gregory Hicks wrote:
>
> >
> > > Date: Wed, 17 Oct 2001 12:04:24 -0400 (EDT)
> > > From: MEISNER <rmeisner at meridia dot org>
> > >
> > > Since I have already deleted the 50 or so of this message, I have,
in
> > the
> > > last couple hours, received this message again, twice. Could you
> > please
> > > check with your email admin to see if they can halt it from
sending
> > >
> > > THANK YOU
> >
> > I'll bet the message shows up each time you check mail and your
desktop
> > machine was checking mail all night long...
> >
> > Although I have no connection w/Qualcomm and Randy, I'll throw my
own
> > $0.02 worth in here.
> >
> > Each instance of this type of behaviour I have seen in the past
(w/over
> > 8,000 users and I'm one of three Postmasters - we get *ALL* the mail
> > problems) is caused by a corrupted mail spool or inbox.
> >
> > The message shows up each time you check your mail spool - no matter
how
> > frequently - and cannot be deleted.
> >
> > The fix is to lock your mail spool (usually with a "touch user.lock"
> > file) and then try and find the offending message. If you can, fix
it
> > up or delete the entire message (from the line beginning "^From ..."
to
> > the next "^From ..." (^ means 'anchor at beginning of line. Also
note
> > the SPACE after the word From...)
> >
> > If this doesn't fix it, check your "Inbox" (Netscape), "Inbox.mbx"
> > (Eudora)... You could try rebuilding the index files for these
> >
> > .Inbox.summary (Netscape)
> > Inbox.toc (Eudora)
> >
> > Just some thoughts on where to look... I could be wrong - and have
been
> > wrong in the past - but your description sounds like...
> >
> > Regards,
> > Gregory Hicks
> > Postmaster, Cadence.COM
> >
---------------------------------------------------------------------
> > 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
> >
> > "I worry about my child and the Internet all the time, even though
> > she's too young to have logged on yet. Here's what I worry about.
I
> > worry that 10 or 15 years from now, she will come to me and say
'Daddy,
> > where were you when they took freedom of the press away from the
> > Internet?'" --from the Cryptography list
> >
> >
>
---------------------------------------------------------------------
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
"I worry about my child and the Internet all the time, even though
she's too young to have logged on yet. Here's what I worry about. I
worry that 10 or 15 years from now, she will come to me and say 'Daddy,
where were you when they took freedom of the press away from the
Internet?'" --from the Cryptography list
Date: Wed, 17 Oct 2001 14:33:39 -0400 (EDT)
From: Chip Old <fold at bcpl dot net>
Subject: RE: QPOPPER3 and QPOPPER4
If either the original sender's mail server or the list's mail server
(turing.pensive.org) was resending the same message over and over, then we
all would have received multiple copies. I haven't, and I haven't seen
complaints from anyone else. Check the queue on your own mail server.
Also check to make sure your POP3 client isn't just downloading the same
message over and over from your mail spool file on your mail server. If
so, either your POP3 client or the POP3 server is misbehaving, or your
mail spool file is corrupted.
On Wed, 17 Oct 2001, MEISNER wrote:
> Since I have already deleted the 50 or so of this message, I have, in the
> last couple hours, received this message again, twice. Could you please
> check with your email admin to see if they can halt it from sending
>
> THANK YOU
--
Chip Old (Francis E. Old) E-Mail: fold at bcpl dot net
Manager, BCPL Network Services Phone: 410-887-6180
Manager, BCPL.NET Internet Services FAX: 410-887-2091
320 York Road
Towson, MD 21204 USA
Date: Wed, 17 Oct 2001 11:18:55 -0700 (PDT)
From: Gustavo Viscaino <g_viscaino at yahoo dot com>
Subject: RE: QPOPPER3 and QPOPPER4
You said you use Pine, right? Pine might be doing Bad
Things© to your lock files, for example. Specially if
it's being executed on the same machine where your POP
server runs.
Just a thought,
Gustavo Viscaino
--- MEISNER <rmeisner at meridia dot org> wrote:
> Since I have already deleted the 50 or so of this
> message, I have, in the
> last couple hours, received this message again,
> twice. Could you please
> check with your email admin to see if they can halt
> it from sending
>
> THANK YOU
>
>
> On Mon, 15 Oct 2001, Saxon Jones wrote:
>
> > There are, in fact, different lock methods between
> our QPOPPER3
> > (.username.pop) and QPOPPER4
> (/Mail/db/pop-lockedout) setups. But the
> > corruption happened most noticeably when all users
> were using QPOPPER4.
> > Since we don't have a whole lot of web mail users,
> we didn't notice it in
> > our initial tests when we had only web mail users
> using QPOPPER4, and
> > regulars on QPOPPER3.
> >
> > ________________________
> > 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
> >
> > -----Original Message-----
> > From: Randall Gellens [mailto:randy at qualcomm dot com]
> > Sent: Monday, October 15, 2001 4:07 PM
> > To: Saxon Jones; QPopper Mailing List
> > Subject: RE: QPOPPER3 and QPOPPER4
> >
> > At 3:45 PM -0600 10/15/01, Saxon Jones wrote:
> > >The mailbox corruption was happening when we run
> > >our web mail service on QPOPPER4, our regular
> mail users weren't having a
> > >problem. Right now we've moved our web mail back
> to QPOPPER3 and so I
> > don't
> > >expect to be able to get any debug info in the
> near future.
> >
> > I don't see why you'd get corruption using Qpopper
> version 4 but not
> > 3 as long as the web mail service is using POP (or
> even i it's going
> > at the spools directly). Could there be other
> differences, such as
> > different lock methods?
> > --
> >
>
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Date: Wed, 17 Oct 2001 16:39:07 -0400
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: QPOPPER3 and QPOPPER4
on Wed, Oct 17, 2001 at 02:33:39PM -0400, Chip Old wrote:
> If either the original sender's mail server or the list's mail server
> (turing.pensive.org) was resending the same message over and over, then we
> all would have received multiple copies. I haven't, and I haven't seen
> complaints from anyone else. Check the queue on your own mail server.
I don't know whether it's a hiccup in the network or what, but I've
had several complaints from folks on mailing lists I've run that I've
been sending them multiple copies lately, as well as having many
multiple copies sent /to/ my server.
From what I've been able to determine, in almost every case the
network latency has been so bad or the connection quality so
intermittent that the remote server sends the message, it is accepted
on my end, and then the connection drops before I can acknowledge
receipt to the remote server. They assume I didn't get it, and attempt
to resend.
It seems to be happening in a lot of places - I've seen it with
verizon, att, digex, and others over the past couple of weeks. Anyway.
Now, to go from one off topic to another - is there any movement on
the "qpopper-announce" front? I want to stay up to date on qpopper,
but not if it means having to wade through all of these completely
offtopic posts and jaunts into basic SMTP vs. POP education... ;)
Steve
--
hesketh.com/inc. v: (919) 834-2552 f: (919) 834-2554 w: http://hesketh.com
Date: Wed, 17 Oct 2001 16:18:12 -0400 (EDT)
From: Chip Old <fold at bcpl dot net>
Subject: RE: QPOPPER3 and QPOPPER4
Not unless both Pine and a POP3 client are trying to access his mail spool
file at the same time. Based on what he said, that's unlikely.
On Wed, 17 Oct 2001, Gustavo Viscaino wrote:
> You said you use Pine, right? Pine might be doing Bad Things© to your
> lock files, for example. Specially if it's being executed on the same
> machine where your POP server runs.
--
Chip Old (Francis E. Old) E-Mail: fold at bcpl dot net
Manager, BCPL Network Services Phone: 410-887-6180
Manager, BCPL.NET Internet Services FAX: 410-887-2091
320 York Road
Towson, MD 21204 USA
From: "Mei-hwa Huang" <mhuang at uta dot edu>
Subject: Problem with the Qpopper 4.03 with open SSL enabled
Date: Wed, 17 Oct 2001 16:08:55 -0500
Hi,
I download openssl package from Sunfreeware web site and install the
package into my Sun Sparc Solaris 7 server.
After configuring the Qpopper 4.0.3 with --with-openssl option and following
the procedures of 'How do I use TLS/SSL with Qpopper' from qpopper FAQ, I am
able to start testing the qpopper with openssl. However, when I type telnet
myserver.domain 110 command to test if the qpopper is running ok no not, I
get the 'ld.so.1:qpopper: fatal: libssl.so.0.9.6: open failed : No Such file
or directory' error message. I check the existence of libssl.so.0.9.6 and
find it is under /usr/local/ssl/lib directory.
Any help on this problem will be greatly appreciated.
Mei-hwa Huang
Computer Network Coordinator
Automation & Robotics Research Institute
University of Texas at Arlington
Tel: 817-272-5906
E-mail: mhuang at uta dot edu
Date: Wed, 17 Oct 2001 18:52:59 -0400 (EDT)
From: Mike <mfahey at enter dot net>
Subject: Unable to open Bulletin database
Hello, Im trying to transfer the file /var/spool/bulls/bulldb
to another system running the same version of linux and qpopper.
However, if you telnet to 110 you get the following error.
-ERR [SYS/TEMP] Unable to open Bulletin database; contact your
administrator
error message from syslog is as follows.
popper[12852]: mike at localhost.localdomain (127.0.0.1): -ERR
[SYS/TEMP] Unable to open Bulletin database; contact your administrator
I can't understand why you simply can't move this file to a different
machine for it to work. I also tried to use db_dump and db_load to create
the database file on the new machine. But I still get the same error
message. I have found no information regarding this on the net, I looked
at the qpopper guide, web site, but have found nothing. If someone's
mail server would happen to go down and they reinstalled the os's and
tried to restore the bulletins information it won't work.
How does one transfer bulletin information from one server to another.
Do you just explain to everyone why they are getting old bulletins?
I simply don't understand why it can't open the database file. I even
looked at the source but it didnt help me to much since I am not a C
programmer. Does anyone have any suggestions? Thanks in advance for
your time.
Date: Wed, 17 Oct 2001 18:04:27 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: QPOPPER3 and QPOPPER4
At 4:39 PM -0400 10/17/01, Steven Champeon wrote:
>Now, to go from one off topic to another - is there any movement on
>the "qpopper-announce" front? I want to stay up to date on qpopper,
>but not if it means having to wade through all of these completely
>offtopic posts and jaunts into basic SMTP vs. POP education... ;)
Announcements of new Qpopper versions are sent to both lists.
--
Date: Wed, 17 Oct 2001 18:07:32 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Unable to open Bulletin database
At 6:52 PM -0400 10/17/01, Mike wrote:
>Hello, Im trying to transfer the file /var/spool/bulls/bulldb
>to another system running the same version of linux and qpopper.
Make sure the file has the same owner and permissions, and that both
the new Qpopper is configured to use the same file name and owner as
the old.
Try enabling debug tracing, which will give more information.
--
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-path>'.
4. Send inetd (or xinetd) a HUP signal.
(Steps 3 and 4 are only needed if you use inetd (or xinetd). In
standalone mode, you can add '-d' or '-t <tracefile-path>' to the
command line directly.)
(In either standalone or inetd mode, if you use a configuration file
you can add 'set debug' or 'set tracefile = <tracefile>' to either a
global or user-specific configuration file instead of steps 3 and 4.)
This causes detailed tracing to be written to the syslog or to the
file specified as 'tracefile'.
Date: Wed, 17 Oct 2001 18:01:19 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Group Bulletins Problem
At 2:40 PM +1000 10/17/01, Sheryl Bruggy wrote:
> I have tried setting the primary group (in /etc/passwd) as suggested in
> the pop_bull.c program. But that doesnt work either.
>
> Has anyone else had the same problem?
>
> BTW: We are using Tru64 Unix (4.0F) and Qpopper 3.12
I'd suggest trying Qpopper 4.0.3. Certainly the primary group should work!
--
From: "Matthew Koch" <mattkoch at genevaonline dot com>
Subject: FreeBSD home dir mail
Date: Thu, 18 Oct 2001 08:30:33 -0500
Has anyone ever confirmed a problem when enabling
home-dir-mail on FreeBSD systems? I have a FreeBSD
system that uses home-dir-mail for quotas and would
love to go to Qpopper 4, but I get an error message
about the users home dir being too long. Has this
been addressed? Will it be fixed a (near) future
release? I commented out the strlen check and everything
works fine, but I'd like to know why its happening.
Matthew Koch
System Administrator
Geneva On-Line Inc.
Date: Thu, 18 Oct 2001 14:23:15 -0400 (EDT)
From: Mike <mfahey at enter dot net>
Subject: Re: Unable to open Bulletin database
Hello, Thank you for your timely response.
I was able to get this working. I was tried to move it to
freebsd and needed to pass it the use-gdbm= option in
order for it to work. It seems linux was using the gdbm
while freebsd was using bsd dbm. Thanks again.
> At 6:52 PM -0400 10/17/01, Mike wrote:
> >Hello, Im trying to transfer the file /var/spool/bulls/bulldb
> >to another system running the same version of linux and qpopper.
>
> Make sure the file has the same owner and permissions, and that both
> the new Qpopper is configured to use the same file name and owner as
> the old.
>
> Try enabling debug tracing, which will give more information.
>
>
--
With best regards,
Mike Fahey - Systems Administration
********************************************************************
ENTER.NET - "The Road to the Internet Starts Here!" (tm)
(610) 437-2221 * http://www.enter.net/ * email:support at enter dot net
********************************************************************
Date: Thu, 18 Oct 2001 10:28:24 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: FreeBSD home dir mail
On Thu, Oct 18, 2001 at 08:30:33AM -0500, Matthew Koch wrote:
> Has anyone ever confirmed a problem when enabling
> home-dir-mail on FreeBSD systems? I have a FreeBSD
> system that uses home-dir-mail for quotas and would
> love to go to Qpopper 4, but I get an error message
> about the users home dir being too long. Has this
> been addressed? Will it be fixed a (near) future
> release? I commented out the strlen check and everything
> works fine, but I'd like to know why its happening.
There was an apparently FreeBSD-specific bug in this discussed on the
list a few months ago, and there was a workaround for it which did not
require a code change, but I don't remember what that was. May have
involved setting some parameter on the command line instead of via
compile-time? Finding it will probably require you to dig through the
archives.
It certainly would be good to get it fixed.
-- 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, 18 Oct 2001 13:30:26 -0700
Subject: Re: Problem with the Qpopper 4.03 with open SSL enabled
On Wed, 17 Oct 2001 16:08:55 -0500, Mei-hwa Huang wrote:
>However, when I type telnet
>myserver.domain 110 command to test if the qpopper is running ok no not, I
>get the 'ld.so.1:qpopper: fatal: libssl.so.0.9.6: open failed : No Such file
>or directory' error message. I check the existence of libssl.so.0.9.6 and
>find it is under /usr/local/ssl/lib directory.
Sounds like a problem with the dynamic loader. I'm not familiar with
how Solaris does it, but with Linux you need to run a command to
identify the availability of shared libraries (the names are written to
a file in /etc). Alternatively, you can define an environment variable
before running a program to tell it additional paths to search for
shared libraries (including the current directory).
I've used the latter mechanism to run game servers as a regular user
without installing their .so's to a system directory. (The idea was to
avoid giving the game executable system priviliges, to protect the
underlying system.)
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: "Adrian Bolzan" <Adrian.Bolzan at aot.com dot au>
Date: Fri, 19 Oct 2001 09:51:09 +1000
Subject: setting up RH7.1 rpm
Hi,
I am new to the list and qpopper.
I have a redHat 7.1 box running postfix.
I installed the RPM version of qpopper 4.0.1 but cannot get it to start.
the install made the "/etc/xinetd/pop3" file but as there is no inetd.conf file I
am not sure how to get qpopper started at boot time.
Any help would be appreciated.
Adrian
From: "Adrian Bolzan" <Adrian.Bolzan at aot.com dot au>
Date: Fri, 19 Oct 2001 11:10:11 +1000
Subject: Re: setting up RH7.1 rpm
Hi,
sorry. i plead pressures of the moment.
xinetd was not installed by default on redHat 7.1, or at least not on mine...
qpopper is working now.
cheers,
adrian
On 19 Oct 01, at 9:51, Adrian Bolzan wrote:
> Hi,
>
> I am new to the list and qpopper.
>
> I have a redHat 7.1 box running postfix.
> I installed the RPM version of qpopper 4.0.1 but cannot get it to
> start.
>
> the install made the "/etc/xinetd/pop3" file but as there is no
> inetd.conf file I am not sure how to get qpopper started at boot time.
>
> Any help would be appreciated.
>
> Adrian
>
Date: Tue, 23 Oct 2001 11:01:08 -0500 (CDT)
From: Kim Scarborough <lists at jinx.unknown dot nu>
Subject: Limit qpopper to SSL?
I looked through the doocumentation for the newest qpopper, but I couldn't
see a way to set it to *only* allow SSL connections. Is there a good way
of doing this? The only thing I could see is to set it to use the
alternate port for SSL and then block access to 110 from a firewall, but
that's an ugly way of doing it.
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 23 Oct 2001 18:59:46 +0000
Subject: Re: Limit qpopper to SSL?
I would use the clear-text-password option with "ssl" or "tsl".
(described on page 31 of the QPopper User-Guide)
- oliver
> I looked through the doocumentation for the newest qpopper, but I couldn't
> see a way to set it to *only* allow SSL connections. Is there a good way
> of doing this? The only thing I could see is to set it to use the
> alternate port for SSL and then block access to 110 from a firewall, but
> that's an ugly way of doing it.
Date: Tue, 23 Oct 2001 12:15:17 -0500 (CDT)
From: Kim Scarborough <lists at jinx.unknown dot nu>
Subject: Re: Limit qpopper to SSL?
> I would use the clear-text-password option with "ssl" or "tsl".
> (described on page 31 of the QPopper User-Guide)
Hmm... I like that idea better. However, since I have tls-support set to
alternate-port, that means I'll still have a port open on 110 that can't
do anything.
If I set the main port to 995, change tls-support to stls, and set the
clear-text-password to ssl, would that work? Or would the negotiation
process for SSL that normally takes place on port 110 break other
SSL-aware pop clients when they hit port 995 looking for a non-negotiable
pop3s connection? I guess I could just try it, but I won't be in front of
the box until tonight.
What's really needed here is a "alternate-port-only" value for the
tls-support option.
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 23 Oct 2001 19:30:46 +0000
Subject: folder internal data
Sorry for (maybe) asking an FAQ.
(I didn't found something usefull about this...)
I'am using QPopper 4.03
Some of my pop-users receive messages like this one:
> > Message-ID: <md5:4F90BE61A3AE922C0A2095A160B3D796>
> Date: Thu, 18 Oct 2001 17:19:56 +0200 (MET DST)
> From: Mail System Internal Data <MAILER-DAEMON at mailserv.fh-giessen dot de>
> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
> X-IMAP: 1003418133 0000000006
> X-Mozilla-Status2: 00000000
>
> This text is part of the internal format of your mail folder, and is not
> a real message. It is created automatically by the mail system software.
> If deleted, important folder data will be lost, and it will be re-created
> with the data reset to initial values.
I belief that QPopper stores these kind of messages for internal use.
But why it delivers those messages to some of my pop-users.
And why he stores those messages (seemingly) only for some pop-users.
(It never appears into my privat Mailbox and I'am using POP3 too (kmail/linux))
I entertain suspicion that it have something to do with there Mail-Clients,
but I'dont know something specific.
How can I prevent that messages like this one above will be send to my pop-users ?
- oliver
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Date: Tue, 23 Oct 2001 19:46:40 +0000
Subject: Re: Limit qpopper to SSL?
I hope I understand you right ...
You will need two daemons.
One for waiting on port 110 for normal SSL conection
and one waiting on port 995 for (old style) alternate-port connections.
Independent from this it should be possible to set the clear-text-password
option for both daemons.
I don't know whether you have to use "ssl" or "tsl" (for the clear-text-password option).
I suppose that you shouldn't use "tsl" for the alternate port, cause the corresponding
clients can't control this.
- oliver
Nachricht vom Dienstag 23 Oktober 2001 17:15:
> > I would use the clear-text-password option with "ssl" or "tsl".
> > (described on page 31 of the QPopper User-Guide)
>
> Hmm... I like that idea better. However, since I have tls-support set to
> alternate-port, that means I'll still have a port open on 110 that can't
> do anything.
>
> If I set the main port to 995, change tls-support to stls, and set the
> clear-text-password to ssl, would that work? Or would the negotiation
> process for SSL that normally takes place on port 110 break other
> SSL-aware pop clients when they hit port 995 looking for a non-negotiable
> pop3s connection? I guess I could just try it, but I won't be in front of
> the box until tonight.
>
> What's really needed here is a "alternate-port-only" value for the
> tls-support option.
--
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, 23 Oct 2001 13:05:58 -0500 (CDT)
From: Kim Scarborough <lists at jinx.unknown dot nu>
Subject: Re: Limit qpopper to SSL?
No, what I want is just one qpopper, running pop3s on port 995, period. No
110 at all, clear or SSL.
On Tue, 23 Oct 2001, Oliver Egginger wrote:
> I hope I understand you right ...
>
> You will need two daemons.
> One for waiting on port 110 for normal SSL conection
> and one waiting on port 995 for (old style) alternate-port connections.
> Independent from this it should be possible to set the clear-text-password
> option for both daemons.
> I don't know whether you have to use "ssl" or "tsl" (for the clear-text-password option).
> I suppose that you shouldn't use "tsl" for the alternate port, cause the corresponding
> clients can't control this.
>
>
> - oliver
>
>
>
> Nachricht vom Dienstag 23 Oktober 2001 17:15:
> > > I would use the clear-text-password option with "ssl" or "tsl".
> > > (described on page 31 of the QPopper User-Guide)
> >
> > Hmm... I like that idea better. However, since I have tls-support set to
> > alternate-port, that means I'll still have a port open on 110 that can't
> > do anything.
> >
> > If I set the main port to 995, change tls-support to stls, and set the
> > clear-text-password to ssl, would that work? Or would the negotiation
> > process for SSL that normally takes place on port 110 break other
> > SSL-aware pop clients when they hit port 995 looking for a non-negotiable
> > pop3s connection? I guess I could just try it, but I won't be in front of
> > the box until tonight.
> >
> > What's really needed here is a "alternate-port-only" value for the
> > tls-support option.
>
> --
> 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, 23 Oct 2001 08:09:57 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: folder internal data
On Tue, Oct 23, 2001 at 07:30:46PM +0000, Oliver Egginger wrote:
> Sorry for (maybe) asking an FAQ.
> (I didn't found something usefull about this...)
>
> I'am using QPopper 4.03
> Some of my pop-users receive messages like this one:
>
> > > Message-ID: <md5:4F90BE61A3AE922C0A2095A160B3D796>
> > Date: Thu, 18 Oct 2001 17:19:56 +0200 (MET DST)
> > From: Mail System Internal Data <MAILER-DAEMON at mailserv.fh-giessen dot de>
> > Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
> > X-IMAP: 1003418133 0000000006
> > X-Mozilla-Status2: 00000000
> >
> > This text is part of the internal format of your mail folder, and is not
> > a real message. It is created automatically by the mail system software.
> > If deleted, important folder data will be lost, and it will be re-created
> > with the data reset to initial values.
>
>
> I belief that QPopper stores these kind of messages for internal use.
No, it's created by uw-imapd and/or Pine - the University of
Washington's (uw) mail software packages. (Note the "X-IMAP" flag in
there.) It's an annoyance. Much of their software is an annoyance
IMHO, starting with their history of poor coding practices leading to
chronic security problems. (My personal bias, at any rate.)
> But why it delivers those messages to some of my pop-users.
> And why he stores those messages (seemingly) only for some pop-users.
> (It never appears into my privat Mailbox and I'am using POP3 too (kmail/linux))
> I entertain suspicion that it have something to do with there Mail-Clients,
> but I'dont know something specific.
>
> How can I prevent that messages like this one above will be send to my pop-users ?
I believe qpopper has an option to suppress it. Alternatively, you can
also alter the options on Pine, at least, to avoid storing it in the
first place. I don't recall about their imapd.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Tue, 23 Oct 2001 13:03:20 -0500 (CDT)
From: Kim Scarborough <lists at jinx.unknown dot nu>
Subject: Re: folder internal data
> I'am using QPopper 4.03
> Some of my pop-users receive messages like this one:
That's actually a Pine thing. Pine 4.x generates those messages, but you
can only see them when using other mailers, or popping your box. Two ways
to fix it:
1) Set the option "quell-internal-folder-msg" to yes in your site-wide
pine.conf; or
2) recompile qpopper with the --enable-uw-kludge in the configure.
Date: Tue, 23 Oct 2001 12:50:37 -0700 (PDT)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: Re: folder internal data
I think the option is something like "--enable-uw-kludge". This will stop the
message from appearing to the POP clients.
Alternatively, your users could use a MUA (mail user agent) that supports IMAP
from their Desktop and laptop (away client)...
Or they could just use a POP client for both.
Regards,
Gregory Hicks
> Date: Tue, 23 Oct 2001 08:09:57 -1000
> From: Clifton Royston <cliftonr at lava dot net>
> On Tue, Oct 23, 2001 at 07:30:46PM +0000, Oliver Egginger wrote:
> > Sorry for (maybe) asking an FAQ.
> > (I didn't found something usefull about this...)
> >
> > I'am using QPopper 4.03
> > Some of my pop-users receive messages like this one:
> >
> > > Date: Thu, 18 Oct 2001 17:19:56 +0200 (MET DST)
> > > From: Mail System Internal Data <MAILER-DAEMON at mailserv.fh-giessen dot de>
> > >
> > > This text is part of the internal format of your mail folder, and is not
> > > a real message. It is created automatically by the mail system software.
> > > If deleted, important folder data will be lost, and it will be re-created
> > > with the data reset to initial values.
> >
> >
> > I belief that QPopper stores these kind of messages for internal use.
>
> No, it's created by uw-imapd and/or Pine - the University of
> Washington's (uw) mail software packages. (Note the "X-IMAP" flag in
> there.) It's an annoyance. Much of their software is an annoyance
> IMHO, starting with their history of poor coding practices leading to
> chronic security problems. (My personal bias, at any rate.)
>
> > But why it delivers those messages to some of my pop-users.
> > And why he stores those messages (seemingly) only for some pop-users.
> > (It never appears into my privat Mailbox and I'am using POP3 too
(kmail/linux))
> > I entertain suspicion that it have something to do with there Mail-Clients,
> > but I'dont know something specific.
> >
> > How can I prevent that messages like this one above will be send to my
pop-users ?
>
> I believe qpopper has an option to suppress it. Alternatively, you can
> also alter the options on Pine, at least, to avoid storing it in the
> first place. I don't recall about their imapd.
> -- Clifton
>
> --
> Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
---------------------------------------------------------------------
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
"I worry about my child and the Internet all the time, even though
she's too young to have logged on yet. Here's what I worry about. I
worry that 10 or 15 years from now, she will come to me and say 'Daddy,
where were you when they took freedom of the press away from the
Internet?'" --from the Cryptography list
Last updated on 23 Oct 2001 by Pensive Mailing List Admin