The qpopper list archive ending on 14 Mar 2002
Topics covered in this issue include:
1. Re: Spool older than cache file error
Gregory Hicks <ghicks at cadence dot com>
Tue, 5 Mar 2002 05:38:10 -0800 (PST)
2. Re: Spool older than cache file error
Eric Luyten <Eric.Luyten at vub.ac dot be>
Tue, 5 Mar 2002 14:41:47 +0100 (MET)
3. Re: Spool older than cache file error
Randall Gellens <randy at qualcomm dot com>
Tue, 5 Mar 2002 12:22:08 -0800
4. Auto-Delete Option
"Habib Abassi" <habassi at telephonyatwork dot com>
Tue, 5 Mar 2002 14:14:09 -0800
5. Could I enable qpopper log in runtime mode without recompiling Qpopper
"Habib Abassi" <habassi at telephonyatwork dot com>
Thu, 7 Mar 2002 16:45:16 -0800
6. Any dependencies between the failure of the disconnect and the enabled option of the qpopper log
"Habib Abassi" <habassi at telephonyatwork dot com>
Thu, 7 Mar 2002 17:08:10 -0800
7. Re: Auto-Delete Option
Randall Gellens <randy at qualcomm dot com>
Thu, 7 Mar 2002 18:20:38 -0800
8. Re: Any dependencies between the failure of the disconnect
Randall Gellens <randy at qualcomm dot com>
Thu, 7 Mar 2002 18:23:02 -0800
9. Outlook porblems with qpopper
"hhh" <hhh at datashopper dot dk>
Fri, 8 Mar 2002 12:30:08 +0100
10. Re: Outlook porblems with qpopper
Kenneth Porter <shiva at well dot com>
08 Mar 2002 13:35:03 -0800
11. Re: Could I enable qpopper log in runtime mode without
Randall Gellens <randy at qualcomm dot com>
Fri, 8 Mar 2002 14:49:44 -0800
12. problem with RedHat 7.2
"Filippo Pizzo" <pizzof at zeronove dot it>
Mon, 11 Mar 2002 08:35:44 +0100
13. Chunky writes and timeouts
"Lisa Casey" <lisa at jellico dot com>
Mon, 11 Mar 2002 12:08:38 -0500
14. RE: Outlook porblems with qpopper
"Bob Castleberry" <castlebb at cuinc dot org>
Mon, 11 Mar 2002 16:24:25 -0600
15. RE: Outlook porblems with qpopper
Alan Brown <alanb at digistar dot com>
Mon, 11 Mar 2002 17:41:34 -0500 (EST)
16. Re: problem with RedHat 7.2
Kenneth Porter <shiva at well dot com>
11 Mar 2002 16:14:19 -0800
17. Re: problem with RedHat 7.2
Alan Brown <alanb at digistar dot com>
Mon, 11 Mar 2002 19:49:07 -0500 (EST)
18. Re: Chunky writes and timeouts
Randall Gellens <randy at qualcomm dot com>
Mon, 11 Mar 2002 17:05:36 -0800
19. Re: problem with RedHat 7.2
Kenneth Porter <shiva at well dot com>
11 Mar 2002 17:13:33 -0800
20. Re: problem with RedHat 7.2
Daniel Senie <dts at senie dot com>
Mon, 11 Mar 2002 20:49:34 -0500
21. Re: problem with RedHat 7.2
Alan Brown <alanb at digistar dot com>
Mon, 11 Mar 2002 21:29:49 -0500 (EST)
22. Re: problem with RedHat 7.2
Daniel Senie <dts at senie dot com>
Mon, 11 Mar 2002 22:48:44 -0500
23. Re: problem with RedHat 7.2
Robert Brandtjen <rob at prometheusmedia dot com>
Mon, 11 Mar 2002 22:33:02 -0600
24. Re: problem with RedHat 7.2
Kenneth Porter <shiva at well dot com>
11 Mar 2002 21:02:04 -0800
25. Re: problem with RedHat 7.2
Robert Brandtjen <rob at prometheusmedia dot com>
Mon, 11 Mar 2002 23:15:41 -0600
26. Re: problem with RedHat 7.2
Alan Brown <alanb at digistar dot com>
Tue, 12 Mar 2002 07:29:52 -0500 (EST)
27. Re: problem with RedHat 7.2
Robert Brandtjen <rob at prometheusmedia dot com>
Tue, 12 Mar 2002 08:50:21 -0600
28. Re: problem with RedHat 7.2
Alan Brown <alanb at digistar dot com>
Tue, 12 Mar 2002 11:46:43 -0500 (EST)
29. RE: Outlook porblems with qpopper
"Bob Castleberry" <castlebb at cuinc dot org>
Tue, 12 Mar 2002 11:27:57 -0600
30. QPopper on SunOS
Rob Lake <rlake at colabnet dot com>
12 Mar 2002 14:27:24 -0330
31. Re: QPopper on SunOS
Kelly Kane <kkane at CHS.CUSD.Claremont dot Edu>
Tue, 12 Mar 2002 10:17:00 -0800
32. Error Compiling "Symbol referencing errors"
Louis Bohm <lbohm at lightbridge dot com>
Tue, 12 Mar 2002 14:10:29 -0500
33. Re: problem with RedHat 7.2
Robert Brandtjen <rob at prometheusmedia dot com>
Tue, 12 Mar 2002 15:53:42 -0600
34. Re: QPopper on SunOS
Randall Gellens <randy at qualcomm dot com>
Tue, 12 Mar 2002 13:59:18 -0800
35. RE: Outlook porblems with qpopper
Kenneth Porter <shiva at well dot com>
12 Mar 2002 14:42:01 -0800
36. RE: Outlook porblems with qpopper
"Bob Castleberry" <castlebb at cuinc dot org>
Wed, 13 Mar 2002 09:04:55 -0600
37. RE: Outlook porblems with qpopper
The Little Prince <thelittleprince at asteroid-b612 dot org>
Wed, 13 Mar 2002 09:02:56 -0800 (PST)
38. RE: Outlook porblems with qpopper
Leonard Hermens <Leonard.Hermens at rcity dot com>
Wed, 13 Mar 2002 10:51:20 -0800
39. RE: Outlook porblems with qpopper
Alan Brown <alanb at digistar dot com>
Wed, 13 Mar 2002 16:04:44 -0500 (EST)
40. Time out errors
Homer Wilson Smith <homer at lightlink dot com>
Wed, 13 Mar 2002 16:51:22 -0500 (EST)
41. RE: Outlook porblems with qpopper (OT)
Kelly Kane <kkane at CHS.CUSD.Claremont dot Edu>
Wed, 13 Mar 2002 14:01:19 -0800
42. RE: Outlook porblems with qpopper (OT)
Randall Gellens <randy at qualcomm dot com>
Wed, 13 Mar 2002 14:45:15 -0800
43. Possible bug in qpopper 4.0.3
Anders Johansson <andjoh at cicada.linux-site dot net>
Wed, 13 Mar 2002 22:54:25 +0100
44. RE: Outlook porblems with qpopper (OT)
The Little Prince <thelittleprince at asteroid-b612 dot org>
Wed, 13 Mar 2002 16:21:25 -0800 (PST)
45. Re: Outlook porblems with qpopper (OT)
Chis Payne <cpayne at pr.uoguelph dot ca>
Wed, 13 Mar 2002 21:58:32 -0500
46. Re: Possible bug in qpopper 4.0.3
Wayne Heming <wheming at hemnet.com dot au>
Thu, 14 Mar 2002 19:03:13 +1100
47. Statistics logging in Qpopper4.0.3
doryce moore <demoore at ccsalpha3.nrl.navy dot mil>
Thu, 14 Mar 2002 13:15:51 -0500
48. Server mode and IMAP/WebMail
"Dan Schaper" <dschaper at midcom dot com>
Thu, 14 Mar 2002 12:24:45 -0800
49. Where are unsubscribe instructions for qpopper mailing list?
Shaun Landau <shaun.landau at rogers dot com>
Thu, 14 Mar 2002 14:59:07 -0600
50. Re: Where are unsubscribe instructions for qpopper mailing
Randall Gellens <randy at qualcomm dot com>
Thu, 14 Mar 2002 16:10:24 -0800
Date: Tue, 5 Mar 2002 05:38:10 -0800 (PST)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: Re: Spool older than cache file error
> Date: Tue, 5 Mar 2002 10:57:12 +0100 (MET)
> From: Eric Luyten <Eric.Luyten at vub.ac dot be>
>
> > At 10:59 AM -0800 3/1/02, Dan Schaper wrote:
> >
> > >I'm seeing this error in my popper logs, is this a configuration
error, or
> > >just a transient self healing error?
> >
> > The error means that Qpopper didn't trust the cache file, because it
[...snip...]
>
> Not necessarily.
> We are also seeing those 'spool older than cache file' messages.
>
> It invariably happens after a new message arrived for a given user AND
> a subsequent succesful POP session, with 'leave messages on server'
set.
Eric:
Dunno if I am reading the logs correctly, but these show this user
checking for mail every two minutes...?
Given the size of the file (23.9MB) and depending on how busy your
server is, isn't this a bit short between checks? I generally tell my
users to set the mail check to intervals of not less than five
minutes... I also show them how to over-ride this setting if they are
expecting an important message, and things seem to work well...
The only errors I've seen have been the "... probe of account..." when
someone truly whacks up their password and we have to reset it for
them...
Regards,
Gregory Hicks
>
> Example : (anonymized)
>
> 10:41:34 popper[9816]: Stats: user 0 0 260 23935643 host ip
> 10:43:36 popper[12048]: Stats: user 0 0 260 23935643 host ip
> 10:45:42 popper[14462]: Stats: user 0 0 261 23954722 host ip
> 10:47:54 popper[16942]: spool older than cache file
/var/mail/u/s/.user.cache
> 10:47:59 popper[16942]: Stats: user 0 0 261 23954734 host ip
>
> It is my guess that the session at 10:45:42 did not succeed at
updating
> the .cache file although no error message to this effect was logged.
>
> The actual check in popper/pop_cache.c seems robust (and simple)
enough.
>
>
> Eric.
---------------------------------------------------------------------
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
"The trouble with doing anything right the first time is that nobody
appreciates how difficult it was."
When a team of dedicated individuals makes a commitment to act as
one... the sky's the limit.
Subject: Re: Spool older than cache file error
Date: Tue, 5 Mar 2002 14:41:47 +0100 (MET)
From: Eric Luyten <Eric.Luyten at vub.ac dot be>
> Eric:
>
> Dunno if I am reading the logs correctly, but these show this user
> checking for mail every two minutes...?
Correct.
> Given the size of the file (23.9MB) and depending on how busy your
> server is, isn't this a bit short between checks?
Not really. All POP requests are properly terminated well before new
messages come in or other POP connections attempts arrive. I checked
that.
I could show you identical behaviour with a 3 MB mailbox and a popping
period of fifteen minutes. Size is not the issue here.
Eric Luyten, Computing Centre VUB/ULB.
Date: Tue, 5 Mar 2002 12:22:08 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Spool older than cache file error
At 10:57 AM +0100 3/5/02, Eric Luyten wrote:
>It invariably happens after a new message arrived for a given user AND
>a subsequent succesful POP session, with 'leave messages on server' set.
Can you reproduce this with debug tracing? Perhaps it is a problem
updating the cache on the previous session, as you suggested. Or
maybe in the case where new mail arrived during a session Qpopper
updates the cache after the spool. It may even be a a case where the
code is working as intended, and the error should really be a debug
trace message instead. (Currently, Qpopper does not use the cache if
new mail arrived, in the interest of robustness. To do so would be a
useful enhancement.)
Subject: Auto-Delete Option
Date: Tue, 5 Mar 2002 14:14:09 -0800
From: "Habib Abassi" <habassi at telephonyatwork dot com>
Hi,
Could any one has an answer for this question
The Auto-Delete option delete automatically the email after using the
retr command even if the disconnect fail (update-on-abort is disabled) ?
Thanks in advance.
Subject: Could I enable qpopper log in runtime mode without recompiling Qpopper
Date: Thu, 7 Mar 2002 16:45:16 -0800
From: "Habib Abassi" <habassi at telephonyatwork dot com>
Hi,
Could I enable qpopper log in runtime mode without recompiling Qpopper?
Thanks in advance.
Subject: Any dependencies between the failure of the disconnect and the enabled option of the qpopper log
Date: Thu, 7 Mar 2002 17:08:10 -0800
From: "Habib Abassi" <habassi at telephonyatwork dot com>
Hi,
I want to know if there's any dependency between the failure of the
disconnect from the server and the enabled option of the qpopper log.
This is my configuration :
Qpopper log option was turned off.
update-on-abort is turned off
Under a load stress of sending and retrieving emails I am receiving a
failure (sometimes) of the disconnect from the server due to timeout
when Qpopper log option is turned on , no more failure ?
My questions are :
1-Why I am receiving disconnect failure only when the qpopper log option
is turned off?
2-Why I am losing all marked emails as deleted from the mailbox however
update-on-abort option is turned off?
Thanks.
Date: Thu, 7 Mar 2002 18:20:38 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Auto-Delete Option
At 2:14 PM -0800 3/5/02, Habib Abassi wrote:
>The Auto-Delete option delete automatically the email after using
>the retr command even if the disconnect fail (update-on-abort is
>disabled) ?
When update-on-abort is false, the session should not enter the
UPDATE state unless the client sends QUIT. Without entering UPDATE,
deleted messages are not removed.
If you're seeing different behavior, it could be a bug. Can you
reproduce it? If so, please get a debug trace.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: Thu, 7 Mar 2002 18:23:02 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Any dependencies between the failure of the disconnect
At 5:08 PM -0800 3/7/02, Habib Abassi wrote:
>1-Why I am receiving disconnect failure only when the qpopper log
>option is turned off?
Things don't break when you're watching them?
Seriously, it might be cause-and-effect or it might be coincidental.
If you can reliably reproduce this, a packet trace might help show
the differences in network activity and timing between the two states.
>2-Why I am losing all marked emails as deleted from the mailbox
>however update-on-abort option is turned off?
Are you certain that the client does not send QUIT?
From: "hhh" <hhh at datashopper dot dk>
Subject: Outlook porblems with qpopper
Date: Fri, 8 Mar 2002 12:30:08 +0100
I'm using qpopper version 4.0.4rc1 on a slackware 8.0 and everyhing is
working great EXCEPT with Microsoft Outlook 2000 and XP.
There is no problem sending from Outlook but receiving works about 3
times out of 10. The error message i'm getting in the message log when
its not working looks like this:
Mar 8 10:35:44 apollon popper[5870]: xxx at 194.19.xx.xx
(194.10.xx.xx): -ERR POP EOF or I/O Error
Mar 8 10:35:44 apollon popper[5870]: Stats: xxx 0 0 2 2162 194.10.xx.xx
194.10.xx.xx
Mar 8 10:35:44 apollon popper[5870]: I/O error flushing output to
client xxx at 194.19.xx.xx [194.10.xx.xx]: Operation not permitted (1)
I tryed the same thing with Eudora, Outlook Express and Pegasus and
those porgrams are all working perfect.
I know it's proberly not a qpopper problem but i'm all out of idears and
the Outlook users are getting very tired of the problem. I tryed 3
different Outlook's 2000, XP and a localized version of XP and i tryed
installing the program updates all with the same result. I'm using the
standard setup with no SLL or any other special features.
Please help me...
Thanks in advance.
Subject: Re: Outlook porblems with qpopper
From: Kenneth Porter <shiva at well dot com>
Date: 08 Mar 2002 13:35:03 -0800
On Fri, 2002-03-08 at 03:30, hhh wrote:
> Mar 8 10:35:44 apollon popper[5870]: xxx at 194.19.xx.xx
> (194.10.xx.xx): -ERR POP EOF or I/O Error
This generally indicates that the client is disconnecting prematurely.
You might want to check timeouts on O2k to see why it might be doing
this. Running a packet sniffer on the client might give you some useful
information.
Date: Fri, 8 Mar 2002 14:49:44 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Could I enable qpopper log in runtime mode without
At 4:45 PM -0800 3/7/02, Habib Abassi wrote:
>Hi,
>
>Could I enable qpopper log in runtime mode without recompiling Qpopper?
>
>Thanks in advance.
If you're talking about debug logging, then you must compile Qpopper
to enable it. Once that's been done you can turn it on and off at
run-time (even per-user).
If you're talking about some other kind of logging, there probably is
a run-time option for it.
See the Administrator's Guide for details.
From: "Filippo Pizzo" <pizzof at zeronove dot it>
Subject: problem with RedHat 7.2
Date: Mon, 11 Mar 2002 08:35:44 +0100
Hi,
if dgt:
rpm -ivh qpopper-4.0.1-1.i386.rpm
get the message:
error: failed dependencies:
dracd is needed by qpopper-4.0.1-1
libcrypto.so.0 is needed by qpopper-4.0.1-1
libssl.so.0 is needed by qpopper-4.0.1-1
why? help me!!!
Thanks, Filippo
From: "Lisa Casey" <lisa at jellico dot com>
Subject: Chunky writes and timeouts
Date: Mon, 11 Mar 2002 12:08:38 -0500
Hi,
Could someone explain to me how chunky writes effect qpopper timeouts? I'm
having a lot of problems with users getting timeouts when they attempt to
pop their mail. The error message I was seeing in /var/log/messages was:
Mar 11 10:00:25 i2000 -s[39039]: (v4.0) Timeout (120 secs) during nw read
from username at IP address
So I changed qpoppers timeout to 600 seconds but now I get a lot of error
messages like:
Mar 11 10:00:25 i2000 -s[39039]: (v4.0) Timeout (600 secs) during nw read
from username at IP address.
Most of our customers use Outlook Express and we have changed the server
timeout in their settings from one to five minutes.
The only other thing I see in the qpopper FAQ that addresses this issue is
the bit about chunky writes, but there's a couple of things I don't
understand.
Since I already have qpopper installed and running can I just run
./configure again to change the chunky writes? Or should I use a
configuration file? I don't quite understand how I should create the
configuration file and just how to tell qpopper to use it.
Any help would be appreciated.
Thanks,
Lisa Casey, Webmaster
Netlink 2000, Inc.
lisa at jellico dot net
From: "Bob Castleberry" <castlebb at cuinc dot org>
Subject: RE: Outlook porblems with qpopper
Date: Mon, 11 Mar 2002 16:24:25 -0600
I've fought with oxp for a while now and was getting timeouts all the
time (still do sometime), I would recommend setting the timeout to 4
min, if it starts getting "can't connect to server" errors just restart
outlook and that tends to fix it (I hate outlook with a passion)
Bob T. Kat
"When everyone's out to get you, paranoia's just good thinking!"
-- WKRP's Dr. Johnny Fever
-----Original Message-----
From: Qpopper-errors at lists.pensive dot org
[mailto:Qpopper-errors at lists.pensive dot org] On Behalf Of hhh
Sent: Friday, March 08, 2002 5:30 AM
To: Subscribers of Qpopper
Subject: Outlook porblems with qpopper
I'm using qpopper version 4.0.4rc1 on a slackware 8.0 and everyhing is
working great EXCEPT with Microsoft Outlook 2000 and XP.
There is no problem sending from Outlook but receiving works about 3
times out of 10. The error message i'm getting in the message log when
its not working looks like this:
Mar 8 10:35:44 apollon popper[5870]: xxx at 194.19.xx.xx
(194.10.xx.xx): -ERR POP EOF or I/O Error
Mar 8 10:35:44 apollon popper[5870]: Stats: xxx 0 0 2 2162 194.10.xx.xx
194.10.xx.xx
Mar 8 10:35:44 apollon popper[5870]: I/O error flushing output to
client xxx at 194.19.xx.xx [194.10.xx.xx]: Operation not permitted (1)
I tryed the same thing with Eudora, Outlook Express and Pegasus and
those porgrams are all working perfect.
I know it's proberly not a qpopper problem but i'm all out of idears and
the Outlook users are getting very tired of the problem. I tryed 3
different Outlook's 2000, XP and a localized version of XP and i tryed
installing the program updates all with the same result. I'm using the
standard setup with no SLL or any other special features.
Please help me...
Thanks in advance.
Date: Mon, 11 Mar 2002 17:41:34 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: RE: Outlook porblems with qpopper
On Mon, 11 Mar 2002, Bob Castleberry wrote:
> I've fought with oxp for a while now and was getting timeouts all the
> time (still do sometime), I would recommend setting the timeout to 4
> min, if it starts getting "can't connect to server" errors just restart
> outlook and that tends to fix it (I hate outlook with a passion)
It's generally a bad idea to hardcode, but how does MS OutHouse react if
you use an IP address instead of the hostname?
AB
Subject: Re: problem with RedHat 7.2
From: Kenneth Porter <shiva at well dot com>
Date: 11 Mar 2002 16:14:19 -0800
On Sun, 2002-03-10 at 23:35, Filippo Pizzo wrote:
> if dgt:
> rpm -ivh qpopper-4.0.1-1.i386.rpm
>
> get the message:
>
> error: failed dependencies:
>
> dracd is needed by qpopper-4.0.1-1
> libcrypto.so.0 is needed by qpopper-4.0.1-1
> libssl.so.0 is needed by qpopper-4.0.1-1
The qpopper RPM is compiled to use SSL and DRAC, so you need to install
the dracd and openssl-devel RPM's. Is the error message not clear? The
hard part is figuring out which package contains required libraries, but
"libssl" should have been a clue.
You can use http://www.rpmfind.net to find packages that contain files.
With .so files, you want to specify the base name and try it without
version numbers (ie. libssl.so without the .0) as the versioned symlinks
are added at package installation time and so aren't "owned" by a
package.
Date: Mon, 11 Mar 2002 19:49:07 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: problem with RedHat 7.2
On 11 Mar 2002, Kenneth Porter wrote:
> The qpopper RPM is compiled to use SSL and DRAC, so you need to install
> the dracd and openssl-devel RPM's. Is the error message not clear? The
> hard part is figuring out which package contains required libraries, but
> "libssl" should have been a clue.
You can also use up2date which is supposed to go get them.
Debian users have apt-get which will also fetch the dependencies.
AB
Date: Mon, 11 Mar 2002 17:05:36 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Chunky writes and timeouts
At 12:08 PM -0500 3/11/02, Lisa Casey wrote:
>Could someone explain to me how chunky writes effect qpopper timeouts?
I don't know that it affects server timeouts, only client timeouts,
but I suppose it might have an effect on server timeouts.
By default, Qpopper 4.x aggregates small writes into one large
packet. This makes TLS/SSL much more efficient, and can be faster in
a normal network.
However, if there is a lot of network congestion or other problems
causing dropped packets between the server and the client, the large
packet may get dropped and need to be resent, possibly several times.
During this period the client receives nothing from the server. If
the client has a very short timeout, it generates an error and closes
the connection.
Turning chunky writes off (or setting it to TLS only) forces Qpopper
to send each network write as its own packet (at least when not under
TLS/SSL). This increases the chances that something will reach the
client before it times out.
It's generally better to fix the network problem, or increase the
client timeout, but if neither of those are practical in a situation,
fiddling with chunky writes can help.
> I'm
>having a lot of problems with users getting timeouts when they attempt to
>pop their mail. The error message I was seeing in /var/log/messages was:
>
>Mar 11 10:00:25 i2000 -s[39039]: (v4.0) Timeout (120 secs) during nw read
>from username at IP address
>
>So I changed qpoppers timeout to 600 seconds but now I get a lot of error
>messages like:
>
>Mar 11 10:00:25 i2000 -s[39039]: (v4.0) Timeout (600 secs) during nw read
>from username at IP address.
This is a server timeout, not a client timeout.
>
>Most of our customers use Outlook Express and we have changed the server
>timeout in their settings from one to five minutes.
Then you probably don't need to mess with chunky writes.
>
>The only other thing I see in the qpopper FAQ that addresses this issue is
>the bit about chunky writes, but there's a couple of things I don't
>understand.
>
>Since I already have qpopper installed and running can I just run
>./configure again to change the chunky writes? Or should I use a
>configuration file? I don't quite understand how I should create the
>configuration file and just how to tell qpopper to use it.
It's a lot easier to use a run-time configuration file than to
recompile Qpopper. Not only do you avoid having to do a 'make
realclean' and rerunning ./configure and make, but you can turn it on
and off, for everyone or just some users.
Just create the file (you can use the sample one in the
distribution), put it somewhere, and then modify the flags passed to
Qpopper when it is launched to point to it. This should all be
covered in the Administrator's Guide.
Subject: Re: problem with RedHat 7.2
From: Kenneth Porter <shiva at well dot com>
Date: 11 Mar 2002 17:13:33 -0800
On Mon, 2002-03-11 at 16:49, Alan Brown wrote:
> On 11 Mar 2002, Kenneth Porter wrote:
>
> > The qpopper RPM is compiled to use SSL and DRAC, so you need to install
> > the dracd and openssl-devel RPM's. Is the error message not clear? The
> > hard part is figuring out which package contains required libraries, but
> > "libssl" should have been a clue.
>
> You can also use up2date which is supposed to go get them.
I think that only works with Red Hat-supplied packages. Qpopper and
dracd are my packages, so up2date wouldn't know about them.
Date: Mon, 11 Mar 2002 20:49:34 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: problem with RedHat 7.2
At 07:49 PM 3/11/02, Alan Brown wrote:
>On 11 Mar 2002, Kenneth Porter wrote:
>
> > The qpopper RPM is compiled to use SSL and DRAC, so you need to install
> > the dracd and openssl-devel RPM's. Is the error message not clear? The
> > hard part is figuring out which package contains required libraries, but
> > "libssl" should have been a clue.
>
>You can also use up2date which is supposed to go get them.
BIG warning here.
DRAC requires portmapper. So if you use up2date to try to load DRAC (and if
the dependencies are properly set up in the drac RPM), you'll get a bunch
of stuff you might not have wanted on your server. This is the one big
danger with up2date.
You also have to pay RedHat $60/year/server for the service (which I do,
and am generally happy with).
I, for one, do NOT EVER run portmapper, NFS, YP or other such stuff on
production servers unless absolutely necessary. I do have an alternate
solution for SMTP-after-POP (which will get merged in to qpopper sometime)
which does not rely on those components.
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Date: Mon, 11 Mar 2002 21:29:49 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: problem with RedHat 7.2
On Mon, 11 Mar 2002, Daniel Senie wrote:
> DRAC requires portmapper. So if you use up2date to try to load DRAC (and if
> the dependencies are properly set up in the drac RPM), you'll get a bunch
> of stuff you might not have wanted on your server. This is the one big
> danger with up2date.
DRAC is a rpc service, so of course it needs portmaper.
> I, for one, do NOT EVER run portmapper, NFS, YP or other such stuff on
> production servers unless absolutely necessary. I do have an alternate
> solution for SMTP-after-POP (which will get merged in to qpopper sometime)
> which does not rely on those components.
Can we _please_ get away from kludges like DRAC and POP-before-SMTP?
They both leave windows of opportunity for a resourceful spammer to get
in.
It has been nearly 2 years since AUTH SMTP came out. It works, it's
secure and it's now widely supported.
Concentrate development on that model T, instead of making better buggy
whips.
I'm going to make a similar statement about pop3:
If you have users who want to leave some mail on the server or access
from multiple locations, they should be using IMAP. That was designed
for this scenario.
I know the reasons for soldiering on with kludge solutions, but it
really is time to stop trying to drive in screws with a mallet.
It may take a bit more time to get a working IMAP server running and to
get AUTH SMTP working, but the reduced support load will pay for itself
shortly afterwards.
AB
Date: Mon, 11 Mar 2002 22:48:44 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: problem with RedHat 7.2
At 09:29 PM 3/11/02, Alan Brown wrote:
>On Mon, 11 Mar 2002, Daniel Senie wrote:
>
> > DRAC requires portmapper. So if you use up2date to try to load DRAC (and if
> > the dependencies are properly set up in the drac RPM), you'll get a bunch
> > of stuff you might not have wanted on your server. This is the one big
> > danger with up2date.
>
>DRAC is a rpc service, so of course it needs portmaper.
>
> > I, for one, do NOT EVER run portmapper, NFS, YP or other such stuff on
> > production servers unless absolutely necessary. I do have an alternate
> > solution for SMTP-after-POP (which will get merged in to qpopper sometime)
> > which does not rely on those components.
>
>
>Can we _please_ get away from kludges like DRAC and POP-before-SMTP?
We have our customers using SMTP AUTH.
>They both leave windows of opportunity for a resourceful spammer to get
>in.
>
>It has been nearly 2 years since AUTH SMTP came out. It works, it's
>secure and it's now widely supported.
>
>Concentrate development on that model T, instead of making better buggy
>whips.
>
>
>I'm going to make a similar statement about pop3:
>
>If you have users who want to leave some mail on the server or access
>from multiple locations, they should be using IMAP. That was designed
>for this scenario.
>
>I know the reasons for soldiering on with kludge solutions, but it
>really is time to stop trying to drive in screws with a mallet.
>
>It may take a bit more time to get a working IMAP server running and to
>get AUTH SMTP working, but the reduced support load will pay for itself
>shortly afterwards.
Well, we allow SMTP-after-POP to reduce our support load. We have some
users who just don't get their stuff set up right no matter what.
As for IMAP, that would also increase support costs. Users have a harder
time understanding it.
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
From: Robert Brandtjen <rob at prometheusmedia dot com>
Subject: Re: problem with RedHat 7.2
Date: Mon, 11 Mar 2002 22:33:02 -0600
On Monday 11 March 2002 09:48 pm, Daniel Senie wrote:
> As for IMAP, that would also increase support costs. Users have a harder
> time understanding it.
I agree with that - most of em can't even get OutLook (yuk) running right.
what IMAP needs is slightly more fool proof set up, meaning it needs a client
which is totally dumbed down so they can't help but get it right.
--
Robert Brandtjen
--------------------------------------
Web Site Creation and Hosting Services
Hostmaster at prometheusmedia dot com
www.prometheusmedia.com
Subject: Re: problem with RedHat 7.2
From: Kenneth Porter <shiva at well dot com>
Date: 11 Mar 2002 21:02:04 -0800
On Mon, 2002-03-11 at 20:33, Robert Brandtjen wrote:
> I agree with that - most of em can't even get OutLook (yuk) running right.
> what IMAP needs is slightly more fool proof set up, meaning it needs a client
> which is totally dumbed down so they can't help but get it right.
But M$ wants to sell you Exchange, so they have no incentive to make
other protocols, esp. open ones, particularly easy to use. Remember
Kerberos, or DNS. M$ introduced incompatibilities to cripple
interoperability.
From: Robert Brandtjen <rob at prometheusmedia dot com>
Subject: Re: problem with RedHat 7.2
Date: Mon, 11 Mar 2002 23:15:41 -0600
On Monday 11 March 2002 11:02 pm, Kenneth Porter wrote:
> But M$ wants to sell you Exchange, so they have no incentive to make
> other protocols, esp. open ones, particularly easy to use. Remember
> Kerberos, or DNS. M$ introduced incompatibilities to cripple
> interoperability.
yeah, I know - but the at least the DNS issue backfired on them repeatedly,
my DNS and BIND book talked brieely about MS incompatibility.
--
Robert Brandtjen
--------------------------------------
Web Site Creation and Hosting Services
Hostmaster at prometheusmedia dot com
www.prometheusmedia.com
Date: Tue, 12 Mar 2002 07:29:52 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: problem with RedHat 7.2
On Mon, 11 Mar 2002, Robert Brandtjen wrote:
> I agree with that - most of em can't even get OutLook (yuk) running right.
> what IMAP needs is slightly more fool proof set up, meaning it needs a client
> which is totally dumbed down so they can't help but get it right.
IMAP worked first time for me at the client end with both OutBreak
Express, KDE Kmail and Ximian Evolution mail.
With 2 minutes work it's fine in pine too.
What major problems are encountered with Outlook vs outlook express when
tryig to run IMAP?
AB
From: Robert Brandtjen <rob at prometheusmedia dot com>
Subject: Re: problem with RedHat 7.2
Date: Tue, 12 Mar 2002 08:50:21 -0600
On Tuesday 12 March 2002 06:29 am, Alan Brown wrote:
> IMAP worked first time for me at the client end with both OutBreak
> Express, KDE Kmail and Ximian Evolution mail.
none for me, I'm referring to the average user.
--
Robert Brandtjen
--------------------------------------
Web Site Creation and Hosting Services
Hostmaster at prometheusmedia dot com
www.prometheusmedia.com
Date: Tue, 12 Mar 2002 11:46:43 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: problem with RedHat 7.2
On Tue, 12 Mar 2002, Robert Brandtjen wrote:
> On Tuesday 12 March 2002 06:29 am, Alan Brown wrote:
> > IMAP worked first time for me at the client end with both OutBreak
> > Express, KDE Kmail and Ximian Evolution mail.
> none for me, I'm referring to the average user.
Well for all the above, if they can't configure IMAP, then they're going
to need hand holding to configure pop3 servers too.
AB
From: "Bob Castleberry" <castlebb at cuinc dot org>
Subject: RE: Outlook porblems with qpopper
Date: Tue, 12 Mar 2002 11:27:57 -0600
"When everyone's out to get you, paranoia's just good thinking!"
-- WKRP's Dr. Johnny Fever
Allan Brown wrote:
> It's generally a bad idea to hardcode, but how does MS OutHouse react
if
> you use an IP address instead of the hostname?
I have all my email clients hardcoded to eliminate dns lookup (anything
to help the process along right), if we ever switch isp connections from
uunet I'll be quitting in a hurry (over a hundred hardcoded outhouse
clients to change, in multiple location), I was having resolution issues
before hardcoding but only with outhouse, everything else works fine,
now that I think about it I hadn't seen any of these issues with
outhouse express (would that be jonny on the spot :) it's kind of
funny, management insists we use this awful software and it's my fault
when it doesn't work right, go figure
Bob T. Kat
Subject: QPopper on SunOS
From: Rob Lake <rlake at colabnet dot com>
Date: 12 Mar 2002 14:27:24 -0330
Hi,
I am attempting to install qpopper 4.0.3 on an Ultra 10 running SunOS
5.7 and I have run across a couple of problems:
1) This line in the trace file: "Unable to obtain socket and address of
client: Socket operation on non-socket (95)" when run from cmd line.
2) When running with stls-support, I get errors about the inability to
seed PRNG with openssl 0.9.6c and egd 0.8 running on /dev/urandom.
Also, how would one make qpopper stls will bind to tcp port 995 without
use of inetd/tcp_wrappers?
any suggestions?
Thanks,
Rob Lake
Date: Tue, 12 Mar 2002 10:17:00 -0800
From: Kelly Kane <kkane at CHS.CUSD.Claremont dot Edu>
Subject: Re: QPopper on SunOS
>
>2) When running with stls-support, I get errors about the inability to
>seed PRNG with openssl 0.9.6c and egd 0.8 running on /dev/urandom.
>
In compile (run?) time you need to tell either qpopper, ssl, or
"egd" (don;t know what it is) where your random seed device is.
/dev/random. /dev/urandom is on GNUish machines.
Kelly
(ps(OT) i forgot to tell openssl where my random device was on a
/dev/random machine, and when i went to generate a key it says: You
don't seem to have an entropy device.\n\nStart Typing. (type type
type) Stop Typing. Ok the little things amuse me. :)
>
--
Kelly Kane
Claremont Unified School District
Date: Tue, 12 Mar 2002 14:10:29 -0500
From: Louis Bohm <lbohm at lightbridge dot com>
Subject: Error Compiling "Symbol referencing errors"
I have installed openssl 0.9.6c on my Solaris 8 server (64bit). I am not
sure if I need to setup anything with ssl right now or if it can wait
untill I have qpopper compiled.
Anyway. I am compiling qpopper with --with-openssl=/usr/local/ssl and
when
I run make I get the following at the end:
Undefined first referenced
symbol in file
SSL_library_init pop_tls_openssl.o
ERR_error_string pop_tls_openssl.o
SSL_CTX_set_cipher_list pop_tls_openssl.o
SSL_CIPHER_get_bits pop_tls_openssl.o
SSLv3_server_method pop_tls_openssl.o
SSL_shutdown pop_tls_openssl.o
SSL_CIPHER_get_name pop_tls_openssl.o
SSL_CTX_use_PrivateKey_file pop_tls_openssl.o
TLSv1_server_method pop_tls_openssl.o
SSL_CTX_check_private_key pop_tls_openssl.o
SSL_CTX_free pop_tls_openssl.o
SSL_load_error_strings pop_tls_openssl.o
SSL_get_current_cipher pop_tls_openssl.o
SSL_CTX_use_certificate_file pop_tls_openssl.o
SSL_CTX_new pop_tls_openssl.o
SSL_set_rfd pop_tls_openssl.o
SSL_CIPHER_description pop_tls_openssl.o
SSLv23_server_method pop_tls_openssl.o
SSL_write pop_tls_openssl.o
SSL_CIPHER_get_version pop_tls_openssl.o
SSL_new pop_tls_openssl.o
SSLv2_server_method pop_tls_openssl.o
SSL_set_wfd pop_tls_openssl.o
SSL_get_error pop_tls_openssl.o
SSL_free pop_tls_openssl.o
SSL_read pop_tls_openssl.o
SSL_accept pop_tls_openssl.o
ERR_get_error pop_tls_openssl.o
ld: fatal: Symbol referencing errors. No output written to popper
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `popper'
Current working directory /tmp/qpopper4.0.3/popper
*** Error code 1
make: Fatal error: Command failed for target `popper_server'
What does this all mean and how can I fix it.
Thanks,
Louis
--
¤¤º°`°º¤ø,¸¸,ø¤º°`°º¤øø¤º°`°
º¤ø,¸¸,ø¤º°`°º¤øø¤º°`°º¤
¤°`°Lightbridge, Inc
¤°`°67 South Bedford St.
¤°`°Burlington MA 01832
¤°`°781.359.4795 mailto:lbohm at lightbridge dot com
¤°`°http://www.lightbridge.com
¤¤º°`°º¤ø,¸¸,ø¤º°`°º¤øø¤º°`°
º¤ø,¸¸,ø¤º°`°º¤øø¤º°`°º¤
From: Robert Brandtjen <rob at prometheusmedia dot com>
Subject: Re: problem with RedHat 7.2
Date: Tue, 12 Mar 2002 15:53:42 -0600
On Tuesday 12 March 2002 10:46 am, Alan Brown wrote:
> Well for all the above, if they can't configure IMAP, then they're going
> to need hand holding to configure pop3 servers too.
Some of them do, sadly
--
Robert Brandtjen
--------------------------------------
Web Site Creation and Hosting Services
Hostmaster at prometheusmedia dot com
www.prometheusmedia.com
Date: Tue, 12 Mar 2002 13:59:18 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: QPopper on SunOS
At 2:27 PM -0330 3/12/02, Rob Lake wrote:
>1) This line in the trace file: "Unable to obtain socket and address of
>client: Socket operation on non-socket (95)" when run from cmd line.
That usually means you ran a non-standalone version of Qpopper from a
command line (instead of inetd).
>Also, how would one make qpopper stls will bind to tcp port 995 without
>use of inetd/tcp_wrappers?
Run two instances of standalone Qpopper. Pass the desired port to
each on the command line. The Administrator's Guide (and the FAQ)
have some examples of this, I believe.
Subject: RE: Outlook porblems with qpopper
From: Kenneth Porter <shiva at well dot com>
Date: 12 Mar 2002 14:42:01 -0800
On Tue, 2002-03-12 at 09:27, Bob Castleberry wrote:
> I have all my email clients hardcoded to eliminate dns lookup (anything
> to help the process along right), if we ever switch isp connections from
> uunet I'll be quitting in a hurry (over a hundred hardcoded outhouse
> clients to change, in multiple location), I was having resolution issues
> before hardcoding but only with outhouse, everything else works fine,
> now that I think about it I hadn't seen any of these issues with
> outhouse express (would that be jonny on the spot :) it's kind of
> funny, management insists we use this awful software and it's my fault
> when it doesn't work right, go figure
Seems like a short-sighted optimization. Instead, run a local DNS server
that you control, so your resolution issues are your own. Create a local
DNS record (eg. mail.mycompany.com) that points at the right mail server
for your clients. (I create separate records for each service, eg.
smtp.mycompany.com, pop3.mycompany.com, etc.) Then your clients will
resolve against a known good name server, and your configuration is in
one place, where it's easy to change if need be.
From: "Bob Castleberry" <castlebb at cuinc dot org>
Subject: RE: Outlook porblems with qpopper
Date: Wed, 13 Mar 2002 09:04:55 -0600
That was the first thing I did (dns), I have internal and external dns
(2 inside (ddns) and 1 outside, that are my boxes), all of them have
records for the mail server, but even with having all of this wonderful
dns in place outhouse still barfs sporadically, now I was using outhouse
express instead of outhouse and I could put in pop.cuinc.org or
smtp.cuinc.org and presto it would work great, but not with outhouse
(since all we are using is outhouse I pulled those records), I finally
just gave up on the sporatic problems by using the ip addy of the server
it's self, outhouse still gets sporadic issues but not near as often, it
might appear to be a short sighted opt. at first but trust me with the
calls I was getting, anything to cut them back was a good thing (mind
you I had to go to every machine and change these settings manually from
pop.cuinc.org to the ip).
Bob T. Kat
"When everyone's out to get you, paranoia's just good thinking!"
-- WKRP's Dr. Johnny Fever
Kenneth wrote:
Seems like a short-sighted optimization. Instead, run a local DNS server
that you control, so your resolution issues are your own. Create a local
DNS record (eg. mail.mycompany.com) that points at the right mail server
for your clients. (I create separate records for each service, eg.
smtp.mycompany.com, pop3.mycompany.com, etc.) Then your clients will
resolve against a known good name server, and your configuration is in
one place, where it's easy to change if need be.
Date: Wed, 13 Mar 2002 09:02:56 -0800 (PST)
From: The Little Prince <thelittleprince at asteroid-b612 dot org>
Subject: RE: Outlook porblems with qpopper
On Wed, 13 Mar 2002, Bob Castleberry wrote:
> That was the first thing I did (dns), I have internal and external dns
> (2 inside (ddns) and 1 outside, that are my boxes), all of them have
> records for the mail server, but even with having all of this wonderful
> dns in place outhouse still barfs sporadically, now I was using outhouse
alright, this is a little off the subject, but can we all just call the
mail clients what they're really called, please. i.e. outlook, not
outhouse. This is really insecure..and i pity the unenlightened people
that read the list archive looking for help to think "what the heck is
outhouse? What's this person talking about??"
And yes, there are lots of people that are that unelightened.
--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"It's hard work to fuck up, especially when you know what you're doing" --Me
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
>
> Kenneth wrote:
> Seems like a short-sighted optimization. Instead, run a local DNS server
> that you control, so your resolution issues are your own. Create a local
> DNS record (eg. mail.mycompany.com) that points at the right mail server
> for your clients. (I create separate records for each service, eg.
> smtp.mycompany.com, pop3.mycompany.com, etc.) Then your clients will
> resolve against a known good name server, and your configuration is in
> one place, where it's easy to change if need be.
>
>
>
--
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"It's hard work to fuck up, especially when you know what you're doing" --Me
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
Date: Wed, 13 Mar 2002 10:51:20 -0800
From: Leonard Hermens <Leonard.Hermens at rcity dot com>
Subject: RE: Outlook porblems with qpopper
I agree, but it is indeed amusing to vent in that way.
By using the incorrect term, we don't have to keep typing those TM symbols
after all the common English words that MS has tradmarked. :-)
-- Leonard
At 09:02 AM 3/13/2002, The Little Prince wrote:
>alright, this is a little off the subject, but can we all just call the
>mail clients what they're really called, please. i.e. outlook, not
>outhouse. This is really insecure..and i pity the unenlightened people
>that read the list archive looking for help to think "what the heck is
>outhouse? What's this person talking about??"
>And yes, there are lots of people that are that unelightened.
>
>--Tony
Date: Wed, 13 Mar 2002 16:04:44 -0500 (EST)
From: Alan Brown <alanb at digistar dot com>
Subject: RE: Outlook porblems with qpopper
On Wed, 13 Mar 2002, Leonard Hermens wrote:
> I agree, but it is indeed amusing to vent in that way.
>
> By using the incorrect term, we don't have to keep typing those TM symbols
> after all the common English words that MS has tradmarked. :-)
And besides that, these clients really do deserve this invective.
I spent more time supporting the 2% of my users who insist on running MS
Outlook (aka LookOut! or Outhouse) or MS Outlook Express (aka Outhouse
Distress or Outbreak Express) than every other user combined.
The prograns are the most badly coded pieces of grabage I have ever had
the misfortune to encounter. They simply don't play nice with anything
other than MS Exchange and are utterly unsuitable for dialup use.
The really stupid thing is that quite a few users acknowledged the
program works far worse than Eudora or Pegasus, but they've been forced
to use it due to the policies of companies they deal with, etc.
AB
Date: Wed, 13 Mar 2002 16:51:22 -0500 (EST)
From: Homer Wilson Smith <homer at lightlink dot com>
Subject: Time out errors
Qpopper rules!
I am sure this is a FAQ, and would appreicate a pointer to RTFM.
What causes these and what can I do about them?
Much Obliged, Homer
Mar 13 00:46:23 mx popper[22978]: (v4.0.3) Timeout (120 secs) during nw read from at 128.253.15.79 (128.253.15.79)
Mar 13 01:00:04 mx popper[28508]: (v4.0.3) Timeout (120 secs) during nw read from at el5-10.lightlink.com (207.127.232.195)
Mar 13 03:32:35 mx popper[21216]: (v4.0.3) Timeout (120 secs) during nw read from chefbob at isdn3-10.lightlink.com (205.232.34.41)
Mar 13 03:53:00 mx popper[28273]: (v4.0.3) Timeout (120 secs) during nw read from imr at isdn1-4.lightlink.com (205.232.34.69)
Mar 13 07:08:31 mx popper[31146]: (v4.0.3) Timeout (120 secs) during nw read from pag67 at isdn4-8.lightlink.com (205.232.34.212)
Mar 13 07:16:56 mx popper[1834]: (v4.0.3) Timeout (120 secs) during nw read from ithgun at isdn1-12.lightlink.com (205.232.34.77)
Mar 13 07:31:54 mx popper[7711]: (v4.0.3) Timeout (120 secs) during nw read from bsu06 at syr-24-24-13-189.twcny.rr.com (24.24.13.189)
Mar 13 07:41:11 mx popper[10380]: (v4.0.3) Timeout (120 secs) during nw read from cowan at usr3.lightlink.com (205.232.34.85)
Mar 13 07:49:58 mx popper[13026]: (v4.0.3) Timeout (120 secs) during nw read from fitterer at as45-119.brunet.bn (202.160.45.119)
Mar 13 07:51:39 mx popper[15959]: (v4.0.3) Timeout (120 secs) during nw read from 7song at port18.lightlink.com (205.232.34.118)
Mar 13 08:19:36 mx popper[27562]: (v4.0.3) Timeout (120 secs) during nw read from msemel at bgm-24-94-47-11.stny.rr.com (24.94.47.11)
Mar 13 08:44:52 mx popper[7399]: (v4.0.3) Timeout (120 secs) during nw read from cariba at syr-24-58-54-62.twcny.rr.com (24.58.54.62)
Mar 13 08:52:58 mx popper[11463]: (v4.0.3) Timeout (120 secs) during nw read from mplqc at port37.lightlink.com (205.232.34.137)
Mar 13 09:03:16 mx popper[16313]: (v4.0.3) Timeout (120 secs) during nw read from rsales at smtp.ridleysbookbindery.com (207.127.235.175)
Mar 13 09:07:07 mx popper[18279]: (v4.0.3) Timeout (120 secs) during nw read from jwingate at smtp.ridleysbookbindery.com (207.127.235.175)
Mar 13 09:09:12 mx popper[19401]: (v4.0.3) Timeout (120 secs) during nw read from mhbk at isdn4-5.lightlink.com (205.232.34.209)
Mar 13 09:18:31 mx popper[24254]: (v4.0.3) Timeout (120 secs) during nw read from tomjan at elpm2-05.lightlink.com (207.127.232.135)
Mar 13 09:26:02 mx popper[26683]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port37.lightlink.com (205.232.34.137)
Mar 13 09:31:00 mx popper[31049]: (v4.0.3) Timeout (120 secs) during nw read from tomjan at elpm2-18.lightlink.com (207.127.232.148)
Mar 13 10:11:30 mx popper[22183]: (v4.0.3) Timeout (120 secs) during nw read from stanton at 63.173.29.66 (63.173.29.66)
Mar 13 10:21:19 mx popper[28314]: (v4.0.3) Timeout (120 secs) during nw read from monica at syr-24-24-16-236.twcny.rr.com (24.24.16.236)
Mar 13 10:45:22 mx popper[9944]: (v4.0.3) Timeout (120 secs) during nw read from janeth at port13.lightlink.com (205.232.34.113)
Mar 13 10:45:25 mx popper[9976]: (v4.0.3) Timeout (120 secs) during nw read from janeth at port13.lightlink.com (205.232.34.113)
Mar 13 10:59:54 mx popper[18614]: (v4.0.3) Timeout (120 secs) during nw read from empire at isdn1-10.lightlink.com (205.232.34.75)
Mar 13 11:00:20 mx popper[18991]: (v4.0.3) Timeout (120 secs) during nw read from tomjan at elpm2-07.lightlink.com (207.127.232.137)
Mar 13 11:12:26 mx popper[26695]: (v4.0.3) Timeout (120 secs) during nw read from stagger at adeskout.autodesk.com (198.102.112.18)
Mar 13 11:15:44 mx popper[28827]: (v4.0.3) Timeout (120 secs) during nw read from at syr-24-58-48-77.twcny.rr.com (24.58.48.77)
Mar 13 11:24:42 mx popper[45]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port39.lightlink.com (205.232.34.139)
Mar 13 11:31:27 mx popper[4177]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port39.lightlink.com (205.232.34.139)
Mar 13 11:37:55 mx popper[9667]: (v4.0.3) Timeout (120 secs) during nw read from acwalbur at 162.39.44.181 (162.39.44.181)
Mar 13 11:53:00 mx popper[18408]: (v4.0.3) Timeout (120 secs) during nw read from jodie at isdn3-2.lightlink.com (205.232.34.33)
Mar 13 11:53:47 mx popper[16912]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port26.lightlink.com (205.232.34.126)
Mar 13 12:18:08 mx popper[31913]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port8.lightlink.com (205.232.34.108)
Mar 13 12:34:33 mx popper[15452]: (v4.0.3) Timeout (120 secs) during nw read from bobp at 209.150.239.114 (209.150.239.114)
Mar 13 12:44:34 mx popper[22069]: (v4.0.3) Timeout (120 secs) during nw read from wges at bgm-66-67-12-237.stny.rr.com (66.67.12.237)
Mar 13 12:55:49 mx popper[27394]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port27.lightlink.com (205.232.34.127)
Mar 13 13:04:31 mx popper[2643]: (v4.0.3) Timeout (120 secs) during nw read from bobp at 209.150.239.114 (209.150.239.114)
Mar 13 13:09:26 mx popper[5974]: (v4.0.3) Timeout (120 secs) during nw read from garyshap at isdn1-8.lightlink.com (205.232.34.73)
Mar 13 13:16:22 mx popper[10744]: (v4.0.3) Timeout (120 secs) during nw read from brock at maysles2006.erols.com (208.59.45.70)
Mar 13 13:29:31 mx popper[19544]: (v4.0.3) Timeout (120 secs) during nw read from answers at bgm-24-24-77-134.stny.rr.com (24.24.77.134)
Mar 13 13:30:43 mx popper[20455]: (v4.0.3) Timeout (120 secs) during nw read from babs at port22.lightlink.com (205.232.34.122)
Mar 13 13:31:58 mx popper[18763]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port26.lightlink.com (205.232.34.126)
Mar 13 13:34:35 mx popper[22616]: (v4.0.3) Timeout (120 secs) during nw read from bobp at 209.150.239.114 (209.150.239.114)
Mar 13 13:58:18 mx popper[1957]: (v4.0.3) Timeout (120 secs) during nw read from jjohnson at elpm1-01.lightlink.com (207.127.232.101)
Mar 13 14:08:19 mx popper[12424]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port21.lightlink.com (205.232.34.121)
Mar 13 14:20:31 mx popper[22769]: (v4.0.3) Timeout (120 secs) during nw read from pmiapp at isdn3-13.lightlink.com (205.232.34.44)
Mar 13 14:29:54 mx popper[26556]: (v4.0.3) Timeout (120 secs) during nw read from elmer at port38.lightlink.com (205.232.34.138)
Mar 13 14:33:41 mx popper[31087]: (v4.0.3) Timeout (120 secs) during nw read from jpl at elpm2-04.lightlink.com (207.127.232.134)
Mar 13 14:49:59 mx popper[8253]: (v4.0.3) Timeout (120 secs) during nw read from dewildes at isdn4-10.lightlink.com (205.232.34.214)
Mar 13 14:59:21 mx popper[17570]: (v4.0.3) Timeout (120 secs) during nw read from hilinda at syr-24-24-13-81.twcny.rr.com (24.24.13.81)
Mar 13 15:23:40 mx popper[32425]: (v4.0.3) Timeout (120 secs) during nw read from answers at bgm-24-24-77-134.stny.rr.com (24.24.77.134)
Mar 13 15:31:45 mx popper[3008]: (v4.0.3) Timeout (120 secs) during nw read from dove at elpm1-12.lightlink.com (207.127.232.112)
Mar 13 15:45:35 mx popper[10365]: (v4.0.3) Timeout (120 secs) during nw read from dove at elpm1-02.lightlink.com (207.127.232.102)
Mar 13 16:17:30 mx popper[4337]: (v4.0.3) Timeout (120 secs) during nw read from at bgm-66-24-129-218.stny.rr.com (66.24.129.218)
Mar 13 16:17:41 mx popper[4347]: (v4.0.3) Timeout (120 secs) during nw read from jkkissel at elpm2-07.lightlink.com (207.127.232.137)
Mar 13 16:20:06 mx popper[5100]: (v4.0.3) Timeout (120 secs) during nw read from ndh at 65.213.99.254 (65.213.99.254)
Mar 13 16:28:49 mx popper[10945]: (v4.0.3) Timeout (120 secs) during nw read from kogiah at isdn3-10.lightlink.com (205.232.34.41)
Mar 13 16:32:23 mx popper[13143]: (v4.0.3) Timeout (120 secs) during nw read from kogiah at isdn3-17.lightlink.com (205.232.34.48)
Mar 13 16:33:54 mx popper[14711]: (v4.0.3) Timeout (120 secs) during nw read from rumble at pool-141-149-206-34.syr.east.verizon.net (141.149.206.34)
Mar 13 16:35:01 mx popper[14791]: (v4.0.3) Timeout (120 secs) during nw read from jkkissel at elpm2-25.lightlink.com (207.127.232.155)
Mar 13 16:35:10 mx popper[15570]: (v4.0.3) Timeout (120 secs) during nw read from rumble at pool-141-149-206-34.syr.east.verizon.net (141.149.206.34)
Mar 13 16:35:14 mx popper[15614]: (v4.0.3) Timeout (120 secs) during nw read from rumble at pool-141-149-206-34.syr.east.verizon.net (141.149.206.34)
------------------------------------------------------------------------
Homer Wilson Smith The Paths of Lovers Art Matrix - Lightlink
(607) 277-0959 KC2ITF Cross Internet Access, Ithaca NY
homer at lightlink.com In the Line of Duty http://www.lightlink dot com
Date: Wed, 13 Mar 2002 14:01:19 -0800
From: Kelly Kane <kkane at CHS.CUSD.Claremont dot Edu>
Subject: RE: Outlook porblems with qpopper (OT)
>
>
>The prograns are the most badly coded pieces of grabage I have ever had
>the misfortune to encounter. They simply don't play nice with anything
>other than MS Exchange and are utterly unsuitable for dialup use.
>
Oddly enough, i have had no problem using Outlook with
sendmail/qpopper/pop3d. I use eudora at work because it's cool, but
i've been having problems getting it running at home, but that was on
a machine with a hosed wsock. It does have it's quirks, but nothing
unlike what i'm used to in this beta of eudora...then again this is
beta and thats release software :) I even have an oddball config for
sendmail. I've hacked up "secure" message sending because i'm an AOL
dial-up user at home (someone else pays for it ;-) and so i use an
SSH tunnel to my mail server, and send email to localhost:25, and
receive mail on localhost:110. It's a hackjob, but it's encrypted,
and it means my hosting provider doesn't have to open up sendmail to
any outside connections from aol or whatnot.
Kelly
--
Kelly Kane
Claremont Unified School District
Date: Wed, 13 Mar 2002 14:45:15 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: RE: Outlook porblems with qpopper (OT)
At 2:01 PM -0800 3/13/02, Kelly Kane wrote:
>I use eudora at work because it's cool, but i've been having
>problems getting it running at home, but that was on a machine with
>a hosed wsock. It does have it's quirks, but nothing unlike what i'm
>used to in this beta of eudora...then again this is beta and thats
>release software :) I even have an oddball config for sendmail. I've
>hacked up "secure" message sending because i'm an AOL dial-up user
>at home (someone else pays for it ;-) and so i use an SSH tunnel to
>my mail server, and send email to localhost:25, and receive mail on
>localhost:110. It's a hackjob, but it's encrypted, and it means my
>hosting provider doesn't have to open up sendmail to any outside
>connections from aol or whatnot.
There's nothing wrong with tunneling email traffic over SSH. It's
difficult for end-users to configure, so for them TLS (SSL) makes
sense.
Have you tried the released Eudora 5.1?
From: Anders Johansson <andjoh at cicada.linux-site dot net>
Subject: Possible bug in qpopper 4.0.3
Date: Wed, 13 Mar 2002 22:54:25 +0100
Hi,
I just subscribed to this list. I think I've found a problem in qpopper.
I received a mail today, the contents of which was http requests produced by
some IIS virus, and my qpopper daemon refused to read the mail.
I reduced the spool file to just that mail and let qpopper hang while I did a
lsof, and found that the file position was at EOF. The mail was 2628 bytes
long. I checked my mail client's debug output and it reported (as told by
qpopper) that the mail was 2633 bytes long. It looks to me like some part of
that mail made qpopper miscalculate the length of the mail.
qpopper version 4.0.3 on SuSE 7.3.
If anyone wants to look at the mail I can put it somewhere for download, (or
perhaps send it to someone :)
regards
Anders
Date: Wed, 13 Mar 2002 16:21:25 -0800 (PST)
From: The Little Prince <thelittleprince at asteroid-b612 dot org>
Subject: RE: Outlook porblems with qpopper (OT)
On Wed, 13 Mar 2002, Alan Brown wrote:
> On Wed, 13 Mar 2002, Leonard Hermens wrote:
>
> > I agree, but it is indeed amusing to vent in that way.
> >
> > By using the incorrect term, we don't have to keep typing those TM symbols
> > after all the common English words that MS has tradmarked. :-)
>
> And besides that, these clients really do deserve this invective.
>
whether they deserve it is irrelevant.
i dont see the beneficial result that defacing their name can have on the
list, only to cause confusion.
now if we were an email client list, with discussions about which clients
were better/worse than others, then i might be able to see how your
name-calling could influence someone not to use the client (but personally
i would just call it what it is and then just go on to describe why said
product sucks)
end of rant :)
--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"It's hard work to fuck up, especially when you know what you're doing" --Me
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.
Date: Wed, 13 Mar 2002 21:58:32 -0500
From: Chis Payne <cpayne at pr.uoguelph dot ca>
Subject: Re: Outlook porblems with qpopper (OT)
There is likely very minimal sway in what is posted on the list
to cause a preference between mail clients, as we are the server
admins, not the platform decision makers.
I wouldn't get in a knot about slang terms for software. We have
servers to run, users to babysit. And Microsoft already has market
share.
- Chris Payne
The Little Prince wrote:
>
> On Wed, 13 Mar 2002, Alan Brown wrote:
>
> > On Wed, 13 Mar 2002, Leonard Hermens wrote:
> >
> > > I agree, but it is indeed amusing to vent in that way.
> > >
> > > By using the incorrect term, we don't have to keep typing those TM symbols
> > > after all the common English words that MS has tradmarked. :-)
> >
> > And besides that, these clients really do deserve this invective.
> >
>
> whether they deserve it is irrelevant.
> i dont see the beneficial result that defacing their name can have on the
> list, only to cause confusion.
> now if we were an email client list, with discussions about which clients
> were better/worse than others, then i might be able to see how your
> name-calling could influence someone not to use the client (but personally
> i would just call it what it is and then just go on to describe why said
> product sucks)
> end of rant :)
>
> --Tony
Date: Thu, 14 Mar 2002 19:03:13 +1100
From: Wayne Heming <wheming at hemnet.com dot au>
Subject: Re: Possible bug in qpopper 4.0.3
This was similar to my problem a few weeks ago, I traced back the emails to
a attachment, that I thought was a virus of some kind but couldn't actually
prove it.
It has happened about 10 times to 4 users over a period of 3 months, so it
is very rare and hard to capture.
Be interested in the final analysis.
Wayne
At 10:54 PM 13-03-02 +0100, Anders Johansson wrote:
>Hi,
>
>I just subscribed to this list. I think I've found a problem in qpopper.
>
>I received a mail today, the contents of which was http requests produced by
>some IIS virus, and my qpopper daemon refused to read the mail.
>
>I reduced the spool file to just that mail and let qpopper hang while I did a
>lsof, and found that the file position was at EOF. The mail was 2628 bytes
>long. I checked my mail client's debug output and it reported (as told by
>qpopper) that the mail was 2633 bytes long. It looks to me like some part of
>that mail made qpopper miscalculate the length of the mail.
>
>qpopper version 4.0.3 on SuSE 7.3.
>
>If anyone wants to look at the mail I can put it somewhere for download, (or
>perhaps send it to someone :)
>
>regards
>Anders
Date: Thu, 14 Mar 2002 13:15:51 -0500
From: doryce moore <demoore at ccsalpha3.nrl.navy dot mil>
Subject: Statistics logging in Qpopper4.0.3
I am running Qpopper 4.03 on Solaris 8. I have the -s option on the
popper executable in inetd.conf. However I cannot get the
statistics. Sendmail and imapd are logging fine to the file
specified in syslog.conf. I am logging mail.info, mail.crit,
mail.debug and mail.err in syslog.conf. Any ideas?
--
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)
From: "Dan Schaper" <dschaper at midcom dot com>
Subject: Server mode and IMAP/WebMail
Date: Thu, 14 Mar 2002 12:24:45 -0800
I've seen Clifton's patch for Server mode/shell access protection, but how
about Server mode and IMAP or Server mode and WebMail access to the spool?
Potential corruption?
__
Thank You
Dan Schaper
Corporate Systems Administrator
MIDCOM Corporation
www.midcom.com
714-579-3000 x251
800-444-5443 (Fax)
714-822-4711 (Nextel)
Date: Thu, 14 Mar 2002 14:59:07 -0600
From: Shaun Landau <shaun.landau at rogers dot com>
Subject: Where are unsubscribe instructions for qpopper mailing list?
This is a multi-part message in MIME format.
--Boundary_(ID_w1PVFTelmNrY14GXWz6NrQ)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
--Boundary_(ID_w1PVFTelmNrY14GXWz6NrQ)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2713.1100" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV> </DIV></BODY></HTML>
--Boundary_(ID_w1PVFTelmNrY14GXWz6NrQ)--
Date: Thu, 14 Mar 2002 16:10:24 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Where are unsubscribe instructions for qpopper mailing
I notice you're using Outlook, which I'm told makes it hard to see
useful headers, such as "List-". Every message sent by this (and all
standard-compliant lists) includes a series of headers, which start
with "List-", which indicate how to subscribe, unsubscribe, see the
archive, get help, and even contain a unique list ID so that you can
easily filter the messages. For example, your message contained the
following headers:
At 2:59 PM -0600 3/14/02, Shaun Landau wrote:
>List-Subscribe: <mailto:qpopper-request at lists.pensive dot org?body=subscribe>
>List-Unsubscribe: <mailto:qpopper-request at lists.pensive dot org?body=unsubscribe>
>List-Archive: <http://www.pensive.org/mailing_lists/archives/qpopper/>
>List-Post: <mailto:qpopper at lists.pensive dot org>
>List-Owner: Pensive Mailing List Admin <listmaster at lists.pensive dot org>
>List-Help: http://www.pensive.org/Mailing_Lists/
>List-Id: <QPopper.lists.pensive.org>
Also, your message was sent as HTML. Many automated processes (such
as list servers) can not read HTML. If you want to subscribe or
unsubscribe, or perform some other list action, be sure to send plain
text. That means pure plain text, and just plain text. (If you send
both styled and plain, that usually doesn't work.)
Last updated on 14 Mar 2002 by Pensive Mailing List Admin