The qpopper list archive ending on 18 Apr 2002
Topics covered in this issue include:
1. Re: Qpopper 4.0.4 (final) available
Chuck Yerkes <chuck+qpopper at yerkes dot com>
Mon, 15 Apr 2002 20:59:27 -0700
2. Re: Suggestion for a new and enhanced "server mode"
Chuck Yerkes <chuck+qpopper at yerkes dot com>
Mon, 15 Apr 2002 21:28:04 -0700
3. Re: When to use qpopper?
PM WONG <pmwong at power25t.hkbu.edu dot hk>
Sat, 13 Apr 2002 13:45:28 +0800 (HKT)
4. RE: version check w/ bsdi4.2
"Lyle Schofield" <Lyle.Schofield at daou dot com>
Fri, 12 Apr 2002 17:40:57 -0400
5. Re: Qpopper 4.0.4 (final) available
Chuck Yerkes <chuck+qpopper at yerkes dot com>
Tue, 16 Apr 2002 08:13:53 -0700
6. UIDL/Maildir question
The Little Prince <thelittleprince at asteroid-b612 dot org>
Fri, 12 Apr 2002 12:04:11 -0700 (PDT)
7. Re: Qpopper 4.0.4 (final) available
The Doctor <doctor at doctor.nl2k.ab dot ca>
Tue, 16 Apr 2002 05:50:01 -0600
8. Re: When to use qpopper?
Alan Brown <alanb at digistar dot com>
Tue, 16 Apr 2002 14:44:48 -0400 (EDT)
9. RE: version check w/ bsdi4.2
Drew Weaver <drew.weaver at thenap dot com>
Tue, 16 Apr 2002 16:24:55 -0400
10. Re: Qpopper 4.0.4 (final) available
The Doctor <doctor at doctor.nl2k.ab dot ca>
Tue, 16 Apr 2002 15:01:09 -0600
11. Re: Suggestion for a new and enhanced "server mode"
Clifton Royston <cliftonr at lava dot net>
Tue, 16 Apr 2002 13:30:08 -1000
12. Re: When to use qpopper?
Clifton Royston <cliftonr at lava dot net>
Tue, 16 Apr 2002 13:45:48 -1000
13. Re: Qpopper 4.0.4 (final) available
Kenneth Porter <shiva at well dot com>
16 Apr 2002 13:13:43 -0700
14. [peter at ixp dot jp: interesting compile errors. - solaris, forte c 6 u 2]
Peter Evans <peter at gol dot com>
Wed, 17 Apr 2002 10:13:47 +0900
15. Re: Qpopper 4.0.4 (final) available
Clifton Royston <cliftonr at lava dot net>
Tue, 16 Apr 2002 16:53:53 -1000
16. Socket operation on non-socket
Randall Gellens <randy at qualcomm dot com>
Tue, 16 Apr 2002 12:19:49 -0700
17. Re: DRAC support for 4.0.4
Mike Hendrix <mike at logical dot net>
Mon, 15 Apr 2002 22:15:51 -0400 (EDT)
18. Re: UIDL/Maildir question
Peter Evans <peter at gol dot com>
Wed, 17 Apr 2002 10:23:10 +0900
19. Re: UIDL/Maildir question
Mark <admin at asarian-host dot net>
Wed, 17 Apr 2002 17:04:05 +0200
20. Need aid with checking mail too often...
Tim Meader <tmeader at cne-odin.gsfc.nasa dot gov>
Tue, 16 Apr 2002 15:24:20 -0400
21. Re: UIDL/Maildir question
The Little Prince <thelittleprince at asteroid-b612 dot org>
Wed, 17 Apr 2002 08:11:51 -0700 (PDT)
22. Re: qpopper on linux problem
Joseph S D Yao <jsdy at center.osis dot gov>
Wed, 17 Apr 2002 11:12:29 -0400
23. Re: qpopper on linux problem
Alan Brown <alanb at digistar dot com>
Wed, 17 Apr 2002 14:32:21 -0400 (EDT)
24. Re: Need aid with checking mail too often...
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Apr 2002 11:32:36 -0700
25. compiling qpopper on SCO OS 5.0.5
"Don" <don at lclcan dot com>
Wed, 17 Apr 2002 14:43:22 -0400
26. two patches for qpopper 4.0.4
James Ralston <qralston+ml.qpopper at andrew.cmu dot edu>
Wed, 17 Apr 2002 16:06:51 -0400 (EDT)
27. Re: qpopper on linux problem
Clifton Royston <cliftonr at lava dot net>
Wed, 17 Apr 2002 08:37:17 -1000
28. Re: Need aid with checking mail too often...
Alan Brown <alanb at digistar dot com>
Wed, 17 Apr 2002 18:03:42 -0400 (EDT)
29. Re: two patches for qpopper 4.0.4
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Apr 2002 15:53:50 -0700
30. Re: Need aid with checking mail too often...
Steve Perrault <sperraul at mnsi dot net>
Wed, 17 Apr 2002 16:58:57 -0400
31. Re: Need aid with checking mail too often...
Alan Brown <alanb at digistar dot com>
Wed, 17 Apr 2002 17:10:03 -0400 (EDT)
32. disabling the XTND XMIT command
James Ralston <qralston+ml.qpopper at andrew.cmu dot edu>
Wed, 17 Apr 2002 15:38:29 -0400 (EDT)
33. Re: Need aid with checking mail too often...
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Apr 2002 14:25:30 -0700
34. Re: compiling qpopper on SCO OS 5.0.5
Lars Nordin <lnordin at noblesys dot com>
Wed, 17 Apr 2002 18:32:06 -0400
35. Re: Need aid with checking mail too often...
The Little Prince <thelittleprince at asteroid-b612 dot org>
Wed, 17 Apr 2002 18:35:33 -0700 (PDT)
36. Re: Need aid with checking mail too often...
peter at netlink.com dot au
Thu, 18 Apr 2002 12:07:56 +1000 (EST)
37. Re: disabling the XTND XMIT command
Randall Gellens <randy at qualcomm dot com>
Wed, 17 Apr 2002 22:05:49 -0700
38.
AA <aish at infinitum-global dot net>
Thu, 18 Apr 2002 08:42:44 +0100 (BST)
39. Re: Need aid with checking mail too often...
Chad <chad_ny_01 at yahoo dot com>
Thu, 18 Apr 2002 01:08:16 -0700 (PDT)
40. Re: compiling qpopper on SCO OS 5.0.5
Patrick Guillot <pguillot at paanjaru dot com>
Thu, 18 Apr 2002 11:53:59 +0200
41. Re: Qpopper Won't Start
Butch Kemper <kemper at tstar dot net>
Thu, 18 Apr 2002 08:29:05 -0500
42. Re: Qpopper Won't Start
"Chris Payne" <cpayne at pr.uoguelph dot ca>
Thu, 18 Apr 02 10:53:57 -0500
43. Re: Qpopper Won't Start
AA <aish at infinitum-global dot net>
Thu, 18 Apr 2002 15:59:22 +0100 (BST)
44. Re: Need aid with checking mail too often...
Chip Old <fold at bcpl dot net>
Thu, 18 Apr 2002 11:45:46 -0400 (EDT)
45. A lot of timeouts
"Stephen Conway" <sconway at wlnet dot com>
Thu, 18 Apr 2002 12:39:03 -0400
46. Re: Need aid with checking mail too often...
Randall Gellens <randy at qualcomm dot com>
Thu, 18 Apr 2002 09:59:59 -0700
47. Bulletin does not start with a valid "From " separator
"Lisa Casey" <lisa at jellico dot com>
Thu, 18 Apr 2002 14:09:43 -0400
48. Re: Bulletin does not start with a valid "From " separator
Clifton Royston <cliftonr at lava dot net>
Thu, 18 Apr 2002 08:58:47 -1000
49. Re: A lot of timeouts
Randall Gellens <randy at qualcomm dot com>
Thu, 18 Apr 2002 11:48:25 -0700
50. REMOVE
"Houman Langroodi" <houman88 at hotmail dot com>
Thu, 18 Apr 2002 18:39:00 +0000
Date: Mon, 15 Apr 2002 20:59:27 -0700
From: Chuck Yerkes <chuck+qpopper at yerkes dot com>
Subject: Re: Qpopper 4.0.4 (final) available
It sounds like you're not invoking it from inetd
or from the command line without the standalone flags.
More information will get you better answers.
Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> On Fri, Apr 12, 2002 at 05:03:38PM -0700, Randall Gellens wrote:
> > Qpopper 4.0.4 (final) is available at
> > <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
...
> Here is the error message I have been getting SINCE 4.0.4fc1.
>
> This is a non-issue in 4.0.3
>
> Apr 13 09:53:23 doctor /usr/sbin/popper[9697]: Unable to obtain socket and address
> of client: Socket operation on non-socket (38)
Date: Mon, 15 Apr 2002 21:28:04 -0700
From: Chuck Yerkes <chuck+qpopper at yerkes dot com>
Subject: Re: Suggestion for a new and enhanced "server mode"
Actually, storing messages in databases is provably not scalable.
Unless that database is perhaps a file system.
RDBMS's typically don't handle data that varies from 50 bytes to
several megabytes. They MIGHT do okay at pointers, but there is
no RDBMS that is as fast as Sleepycat DB v4. RDBMS is tuned for
entirely different uses that a mail server would need.
Changes require new delivery methods and dedicated access methods.
POP doesn't cut if for me for that.
Other ways to do it? IMAP servers. It's an open protocol that
lets you maintain a variety of state flags about the message,
move messages around into folders and lets you keep the messages
on the server for location independant mail reading.
Did I say it's Open? I use Mutt and Mozilla and Mulberry and
Evolution to access it. Outlook can do it.
And I've used ones that scale massively (a tad more than the 800
or so that an Exchange box can handle - or, folks are learning with
slightly more scalable Exchange 2000 that the machines that they
can reclaim from Exchange service are now needed for ActiveDirectory.
Ooops.)
But the qpopper advantage is that I can use POP, or tools that
manage a System 7 mailbox.
Quoting Gregory Hicks (ghicks at cadence dot com):
>
> > Date: Fri, 05 Apr 2002 15:17:01 +0200
> > From: Jesus Cea Avion <jcea at argo dot es>
> >
> > Problem:
> [...snip...]
> >
> > Solution:
> >
> > A simple and efficient database (key/value) used to store messages.
>
> This is a solution that is commercially available and has a good many
> customers. The software integrates nicely with many current desktop
> apps. Comes complete with built in calendaring and appointment system.
> Unfortunately, it only *nicely* uses ONE mail reader... It has the
> potential to use many readers but deliberately does not integrate at ALL
> with any of the others.
>
> The name of this commercial package and the reader? Exchange and
> Outlook...
>
> The rest of your idea, though, are good and seem well thought out...
>
> Personally, I don't like the idea of keeping messages in a database...
> >From experience, it is way too hard to guarantee good backups and thus
> be sure that you will get a usable restore... Of course, that might
> just be the product being restored...
Date: Sat, 13 Apr 2002 13:45:28 +0800 (HKT)
From: PM WONG <pmwong at power25t.hkbu.edu dot hk>
Subject: Re: When to use qpopper?
> On Fri, Apr 12, 2002 at 09:31:10AM +0800, PM WONG wrote:
> > Since most Unix servers come with a pop server of their own
> > OS, i wonder when do we consider switching to use qpopper
> > instead.
>
> SuSE imho comes e.g. with Qpopper.
> so if you use an very old version of this os, you can/or have
> to install a new version for example.
> another scenario would be, that you have to switch to another
> os and would like to use qpopper, because you know the syntax
> of the conf-file, etc.
But some of the people who has used qpopper commented about its
sophistication, such as slowness for too much I/O (creation of
temp files ..etc) and other things.
So why don't we use a simple one like those which comes with the OS
Subject: RE: version check w/ bsdi4.2
Date: Fri, 12 Apr 2002 17:40:57 -0400
From: "Lyle Schofield" <Lyle.Schofield at daou dot com>
I think you can just run "popper -v" from the command line.
-Lyle
Lyle Schofield
Sentient
A Division of DAOU Systems, Inc.
Kensington, Maryland USA
v:301.929.7624 f:301.929.7680 e:lyle.schofield at daou dot com
-----Original Message-----
From: Jeff Donovan [mailto:jdonovan at beth.k12.pa dot us]
Sent: Wednesday, April 10, 2002 8:06 AM
To: Subscribers of Qpopper
Subject: version check w/ bsdi4.2
Greetings,
how do I check which version of qpopper I am running?
also, has anyone with BSDI 4.2 upgraded to qpopper 4.0.3? are there
any issues I need to be aware of before I install?
thanks
-j
--
------------------------------------------------------------------------
Jeff Donovan Network Analyst
Bethlehem Area School District Network Operations
Bethlehem, PA 18020 (610) 807-5571 jdonovan at beth.k12.pa dot us
Date: Tue, 16 Apr 2002 08:13:53 -0700
From: Chuck Yerkes <chuck+qpopper at yerkes dot com>
Subject: Re: Qpopper 4.0.4 (final) available
Given the lack of information, I'd say that you
called it on the command line without the standalone
flags and it spewed this back at you.
or
And you did WHAT to get that error?
(cmon, you know how this works).
Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> On Mon, Apr 15, 2002 at 08:59:27PM -0700, Chuck Yerkes wrote:
> > It sounds like you're not invoking it from inetd
> > or from the command line without the standalone flags.
> >
> > More information will get you better answers.
> >
> > Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> > > On Fri, Apr 12, 2002 at 05:03:38PM -0700, Randall Gellens wrote:
> > > Here is the error message I have been getting SINCE 4.0.4fc1.
> > > This is a non-issue in 4.0.3
> > > Apr 13 09:53:23 doctor /usr/sbin/popper[9697]: Unable to obtain socket and address
> > > of client: Socket operation on non-socket (38)
>
> Here is may configuration file:
> ./configure --prefix=/usr --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man --with-low-memory --with-newlib --enable-servermode --enable-shy --enable-poppassd --enable-log-login --with-openssl=/usr/contrib
Date: Fri, 12 Apr 2002 12:04:11 -0700 (PDT)
From: The Little Prince <thelittleprince at asteroid-b612 dot org>
Subject: UIDL/Maildir question
in my quest to finish my Maildir patch, i'm a little confused on how
UIDs/UIDLs work.
with my patch, first, Postfix generates no 'From blah blah' line, which it
looks like what a generated UID is made from? So right now it just does it
from the first line which is a Delivered-To header, and comes up with:
X-UIDL: _8,"!U16!!]AA!!6$X!!
I dont know if this is right, corrupted, or what?
Lastly, in pop_send i notice that even though a message is in the mp
structure, it's still read in and wrote out from p->drop. Can this be
explained? Right now for maildir type, p->drop is nothing, but since it's
used in said function, i'm simply pointing p->drop to the current filename
and doing fopen on it.
Any enlightenment is appreciated,
--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"Strange, but it seems, there's a mutiny brewing inside of me"
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Date: Tue, 16 Apr 2002 05:50:01 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: Qpopper 4.0.4 (final) available
On Mon, Apr 15, 2002 at 08:59:27PM -0700, Chuck Yerkes wrote:
> It sounds like you're not invoking it from inetd
> or from the command line without the standalone flags.
>
> More information will get you better answers.
>
> Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> > On Fri, Apr 12, 2002 at 05:03:38PM -0700, Randall Gellens wrote:
> > > Qpopper 4.0.4 (final) is available at
> > > <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
> ...
> > Here is the error message I have been getting SINCE 4.0.4fc1.
> >
> > This is a non-issue in 4.0.3
> >
> > Apr 13 09:53:23 doctor /usr/sbin/popper[9697]: Unable to obtain socket and address
> > of client: Socket operation on non-socket (38)
Here is may configuration file:
./configure --prefix=/usr --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man --with-low-memory --with-newlib --enable-servermode --enable-shy --enable-poppassd --enable-log-login --with-openssl=/usr/contrib
--
Member - Liberal International On 11 Sept 2001 the WORLD was violated.
This is doctor at nl2k.ab.ca Ici doctor at nl2k dot ab dot ca
Society MUST be saved! Extremists must dissolve.
Beware of defining as intelligent only those who share your opinions
Date: Tue, 16 Apr 2002 14:44:48 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: When to use qpopper?
On Sat, 13 Apr 2002, PM WONG wrote:
> But some of the people who has used qpopper commented about its
> sophistication, such as slowness for too much I/O (creation of
> temp files ..etc) and other things.
Much other code has worse bugs
> So why don't we use a simple one like those which comes with the OS
Usually because the POP3 daemon bundled with the OS is so old that it's
susceptable to someone hacking into the system and getting root level
access.
This is "a very, very bad thing", unless you like finding your machine
has been taken over by IRC script kiddies hellbent on making your system
part of their Distributed Denial of Service attack network, or spammers
sending out millions of advertisments.
And yes, both scenarios are regular occurances for improperly secured
machines. Korea and China are currently very popular countries with
these kinds of people at the moment due to extremely high numbers of
machines connected to the Internet which are easily hacked into and
taken over.
AB
From: Drew Weaver <drew.weaver at thenap dot com>
Subject: RE: version check w/ bsdi4.2
Date: Tue, 16 Apr 2002 16:24:55 -0400
Or the obvious telnet 127.0.0.1 110
Unless you modified the header.
-Drew
-----Original Message-----
From: Lyle Schofield [mailto:Lyle.Schofield at daou dot com]
Sent: Friday, April 12, 2002 5:41 PM
To: Subscribers of Qpopper
Subject: RE: version check w/ bsdi4.2
I think you can just run "popper -v" from the command line.
-Lyle
Lyle Schofield
Sentient
A Division of DAOU Systems, Inc.
Kensington, Maryland USA
v:301.929.7624 f:301.929.7680 e:lyle.schofield at daou dot com
-----Original Message-----
From: Jeff Donovan [mailto:jdonovan at beth.k12.pa dot us]
Sent: Wednesday, April 10, 2002 8:06 AM
To: Subscribers of Qpopper
Subject: version check w/ bsdi4.2
Greetings,
how do I check which version of qpopper I am running?
also, has anyone with BSDI 4.2 upgraded to qpopper 4.0.3? are there
any issues I need to be aware of before I install?
thanks
-j
--
------------------------------------------------------------------------
Jeff Donovan Network Analyst
Bethlehem Area School District Network Operations
Bethlehem, PA 18020 (610) 807-5571 jdonovan at beth.k12.pa dot us
Date: Tue, 16 Apr 2002 15:01:09 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: Qpopper 4.0.4 (final) available
On Tue, Apr 16, 2002 at 08:13:53AM -0700, Chuck Yerkes wrote:
> Given the lack of information, I'd say that you
> called it on the command line without the standalone
> flags and it spewed this back at you.
>
> or
>
> And you did WHAT to get that error?
> (cmon, you know how this works).
>
> Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> > On Mon, Apr 15, 2002 at 08:59:27PM -0700, Chuck Yerkes wrote:
> > > It sounds like you're not invoking it from inetd
> > > or from the command line without the standalone flags.
> > >
> > > More information will get you better answers.
> > >
> > > Quoting The Doctor (doctor at doctor.nl2k.ab dot ca):
> > > > On Fri, Apr 12, 2002 at 05:03:38PM -0700, Randall Gellens wrote:
> > > > Here is the error message I have been getting SINCE 4.0.4fc1.
> > > > This is a non-issue in 4.0.3
> > > > Apr 13 09:53:23 doctor /usr/sbin/popper[9697]: Unable to obtain socket and address
> > > > of client: Socket operation on non-socket (38)
> >
> > Here is may configuration file:
> > ./configure --prefix=/usr --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man --with-low-memory --with-newlib --enable-servermode --enable-shy --enable-poppassd --enable-log-login --with-openssl=/usr/contrib
/usr/sbin/popper 110
/usr/sbin/popper 995 -f /etc/mail/qpop/config.tls
is what I typed.
--
Member - Liberal International On 11 Sept 2001 the WORLD was violated.
This is doctor at nl2k.ab.ca Ici doctor at nl2k dot ab dot ca
Society MUST be saved! Extremists must dissolve.
Beware of defining as intelligent only those who share your opinions
Date: Tue, 16 Apr 2002 13:30:08 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Suggestion for a new and enhanced "server mode"
On Thu, Apr 11, 2002 at 08:11:32PM +0200, Jesus Cea Avion wrote:
> > At this point, I think the scalability of database mail solutions is
> > unproven one way or the other.
>
> An interesting starting point could be to modify QPOPPER to manage the
> user mailbox using an abstract API. In this way, future support for
> MAILDIR format should be trivial and sparate from QPOPPER maintainance.
> And the day after the release I could do some DB testing on my own :-)
I think this would be an excellent approach; I have been thinking
about it too.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
Date: Tue, 16 Apr 2002 13:45:48 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: When to use qpopper?
On Sat, Apr 13, 2002 at 01:45:28PM +0800, PM WONG wrote:
...
> But some of the people who has used qpopper commented about its
> sophistication, such as slowness for too much I/O (creation of
> temp files ..etc) and other things.
> So why don't we use a simple one like those which comes with the OS
I'm sorry, your wording is so unclear to me that I can not understand
quite what you are getting at. You could be trolling us, but I can't
tell, so I'll give you a straight answer.
First, the "simple one like those which comes with the OS" is going to
depend on what OS you have. Several people pointed out that with a
number of OSes it may actually be qpopper, but may be an older version.
If it's not qpopper, then it's some other program. That program could
be fine to use, or could be very old, or buggy, or have major security
holes, or be lacking in features.
Second, most of the discussion about qpopper performance stems from end
users basically abusing the POP protocol in ways that it was never
intended for, and admins trying to tweak the performance on their
systems to work around this. It is a pretty safe bet that other popper
programs you may look at will not deal with these performance issues
any better, and very likely worse. (That is, if they can even attempt
to POP an 80MB inbox.)
I haven't heard anyone mention a case in which qpopper performs worse
than an older POP daemon and I'd be surprised if there is one. (I have
to admit, I haven't looked at ipop3d performance, but I suspect it's
much less optimized.)
Finally, I'd be surprised if anyone is twisting your arm to use
qpopper. If you have some other program, it's not full of bugs or
security holes, it works well enough for you and you are happy with it,
by all means use it. If however you have thousands of users POPping
mail off your server and it is slowing to a crawl with this other
program... then maybe at that time you'd want to consider qpopper.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
Subject: Re: Qpopper 4.0.4 (final) available
From: Kenneth Porter <shiva at well dot com>
Date: 16 Apr 2002 13:13:43 -0700
On Fri, 2002-04-12 at 17:03, Randall Gellens wrote:
> Qpopper 4.0.4 (final) is available at
> <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
RPM and SRPM packages are now available at
<http://www.sewingwitch.com/ken/SRPMS/>.
Randall, the file Mailing.List is in the FTP directory but not in the
tarball. All other files in the directory are included in the tarball,
so could you add Mailing.List to the doc subdirectory?
Meanwhile, I'm including the copy from the FTP directory in my RPM
packages.
Date: Wed, 17 Apr 2002 10:13:47 +0900
From: Peter Evans <peter at gol dot com>
Subject: [peter at ixp dot jp: interesting compile errors. - solaris, forte c 6 u 2]
I wish there was a --disable-mimerelatedcrap
anyway
pop_config.c is full of bogons relating to the use of enums, which I expect GCC
will let through.
"pop_config.c", line 1220: warning: enum type mismatch: op "="
"pop_config.c", line 1416: warning: enum type mismatch: op "="
"pop_config.c", line 1419: warning: enum type mismatch: arg #2
"pop_config.c", line 1428: warning: enum type mismatch: op "="
"pop_config.c", line 1430: warning: enum type mismatch: op "="
"pop_config.c", line 1554: warning: enum type mismatch: op "="
pretty much all of these are caused because the following are used:
typedef enum {
POP_FAILURE = 0,
POP_SUCCESS = 1
} pop_result;
as you can see, there is no way in hell that this can agree with:
/*
* The possible errors.
*/
typedef enum
{
kER_SUCCESS = 1,
kER_NOFILE,
kER_LINE_LEN,
kER_EXP_SET,
kER_UNKN_OPT,
kER_UNKN_MNEM,
kER_RESTR,
kER_NOT_BOOL,
kER_EXP_EQL,
kER_BAD_VAL,
kER_EXP_BOOL,
kER_EXP_INT,
kER_EXP_STR,
kER_EXP_MNEM,
kER_EXP_EOL,
kER_RECURS,
kER_CONNECTED,
kER_NOT_COMPILED_WITH,
kER_ALREADY_SET,
kER_HANDLED,
kER_SYSTEM,
kER_INTERNAL,
kER_LAST_ERROR
} error_code_type;
...
P
I also think that AB's comments about not turning qpopper into a swiss army knife
are valid. I dont want it to do mime, I want it to POP.
--
END OF LINE.
Date: Tue, 16 Apr 2002 16:53:53 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Qpopper 4.0.4 (final) available
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <438266398238441391594 at lists.pensive.org>; from doctor at doctor dot nl2k dot ab dot ca on Tue, Apr 16, 2002 at 03:01:09PM -0600
On Tue, Apr 16, 2002 at 03:01:09PM -0600, The Doctor wrote:
> On Tue, Apr 16, 2002 at 08:13:53AM -0700, Chuck Yerkes wrote:
> > Given the lack of information, I'd say that you
> > called it on the command line without the standalone
> > flags and it spewed this back at you.
> > And you did WHAT to get that error?
> > (cmon, you know how this works).
...
> > > Here is may configuration file:
> > > ./configure --prefix=/usr --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man --with-low-memory --with-newlib --enable-servermode --enable-shy --enable-poppassd --enable-log-login --with-openssl=/usr/contrib
>
> /usr/sbin/popper 110
> /usr/sbin/popper 995 -f /etc/mail/qpop/config.tls
>
> is what I typed.
Then if you built it like that, that is the error you would always have
gotten on doing this, because that's not how you start popper.
If your inetd.conf references /usr/sbin/popper, then you're probably
running 4.04 just fine right now.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
Date: Tue, 16 Apr 2002 12:19:49 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Socket operation on non-socket
If you're getting this error (as several recent posters are), it
usually means that you compiled Qpopper for use with inetd (or
similar) yet are trying to run it from a command prompt. The
solution is either to run Qpopper from inetd/xinetd/etc., or to use
the '--enable-standalone' option with ./configure (after doing a
'make realclean').
Date: Mon, 15 Apr 2002 22:15:51 -0400 (EDT)
From: Mike Hendrix <mike at logical dot net>
Subject: Re: DRAC support for 4.0.4
I had the same problem on Solaris 2.6/2.7. I got the compile to work by
modifying the configure program and adding the -lnsl to the lines that
reference -ldrac in the configure script. I also copied the libdrac.a to
/usr/lib. Once I modified the configure script the configure/compile worked
just fine.
On Tue, 16 Apr 2002, Ayamura KIKUCHI wrote:
> configure script with --with-drac option fails on Solaris 8:
> zsh% env LDFLAGS="-L/usr/local/lib -R/usr/local/lib" ./configure
> --with-drac=/usr/local/lib
> ...
> checking for dracauth in -ldrac... no
> Can't use DRAC: dracauth not found in -ldrac
>
> config.log:
> ...
> configure:3955: checking for dracauth in -ldrac
> configure:3974: gcc -o conftest -O2 -idirafter /usr/local/include -fpcc-struct-return -idirafter /usr/local/include -L/usr/local/lib -R/usr/local/lib conftest.c -ldrac -L/usr/local/lib -ldrac -lposix4 -lcrypt 1>&5
> Undefined first referenced
> symbol in file
> xdr_enum /usr/local/lib/libdrac.a(drac_xdr.o)
> clnt_create /usr/local/lib/libdrac.a(dracauth.o)
> clnt_sperror /usr/local/lib/libdrac.a(dracauth.o)
> xdr_u_long /usr/local/lib/libdrac.a(drac_xdr.o)
> clnt_spcreateerror /usr/local/lib/libdrac.a(dracauth.o)
> ld: fatal: Symbol referencing errors. No output written to conftest
> collect2: ld returned 1 exit status
>
> libnsl(3LIB) is also need to be linked with libdrac on Solaris 8.
> It is also true of IRIX.
>
> solution:
> 1. install shared library libdrac.so linked with libnsl
> 2. modify configure.in/configure
>
> Which is the best way?
>
> -- ayamura
>
-----------------------------------------------
"I have not failed. I've just found 10,000 ways
that won't work." - Thomas Edison
Michael Hendrix mike at logical dot net
Systems Engineer / SysAdmin Team Leader
Logical Net / Capital Net (518) 292-4509
Date: Wed, 17 Apr 2002 10:23:10 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: UIDL/Maildir question
The Little Prince (thelittleprince at asteroid-b612 dot org) wrote:
> in my quest to finish my Maildir patch, i'm a little confused on how
> UIDs/UIDLs work.
> with my patch, first, Postfix generates no 'From blah blah' line, which it
> looks like what a generated UID is made from? So right now it just does it
> from the first line which is a Delivered-To header, and comes up with:
> X-UIDL: _8,"!U16!!]AA!!6$X!!
> I dont know if this is right, corrupted, or what?
Horses for courses, there are already poppers that deal with maildir,
why not use one of them. Don't try and bastardize qpopper.
courier,
qmail's pop3
solidpop3d
...
and probably a dozen others.
Lets not make qpopper any more bloated than it already is with that
evil mimemangling.
P
--
END OF LINE.
From: Mark <admin at asarian-host dot net>
Date: Wed, 17 Apr 2002 17:04:05 +0200
Subject: Re: UIDL/Maildir question
The Little Prince (thelittleprince at asteroid-b612 dot org) wrote:
> from the first line which is a Delivered-To header, and comes up
> with:
> X-UIDL: _8,"!U16!!]AA!!6$X!!
> I dont know if this is right, corrupted, or what?
From the ever useful qpopper FAQ at:
http://www.eudora.com/qpopper/faq.html#3.0.uidl
Qpopper 3.0 introduced a more compact encoding of message unique identifiers
(known as UIDs or UIDLs). For example, a UID may now look like
E`'!!Y]+"!(-i!!Tl$#!
These UIDs are fine, they are not corrupted. They may look strange, but
that is OK. They are in full conformance with RFC 1939. Specifically, see
"UIDL Command" in section 7.
The unique-id of a message is an arbitrary server-determined string,
consisting of one to 70 characters in the range 0x21 to 0x7E
This means that the UID can consist of any characters in the ASCII range
(hex) 21-7E; (decimal) 33-126; (characters) '!' - '~'.
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx
Date: Tue, 16 Apr 2002 15:24:20 -0400
From: Tim Meader <tmeader at cne-odin.gsfc.nasa dot gov>
Subject: Need aid with checking mail too often...
--=====================_621274195==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hello all,
I was just wondering if anyone knew of a commonly used program used in
conjunction with Qpopper, or perhaps even a widely used patch, that would
enable me to limit the frequency with which users check their
mail. Currently there is no such limit, and believe it or not many have
their Eudora setup to autocheck every minute. This is unacceptable with
almost 2000 users per machine. Especially considering that they regularly
keep messages on server as well for a period of at least 5 days. I know
that I've seen other institutions implement such restrictions, and you are
sent an error message via standard POP protocol it appears, which Eudora
displays in the status telling you you are checking mail too often. THis is
more than sufficient. Any help or recommendations would be GREATLY
appreciated. Thanks in advance.
PS - The client getting the descriptive error message is by FAR the most
important thing, as to avoid unnecessary calls to our helpdesk people.
---
Tim Meader
ACS Government Services, Inc. - (301) 286-8013
tmeader at cne-odin.gsfc.nasa dot gov
--=====================_621274195==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<font size=3>Hello all,<br><br>
I was just wondering if anyone knew of a commonly used program used in
conjunction with Qpopper, or perhaps even a widely used patch, that would
enable me to limit the frequency with which users check their mail.
Currently there is no such limit, and believe it or not many have their
Eudora setup to autocheck every minute. This is unacceptable with
almost 2000 users per machine. Especially considering that they regularly
keep messages on server as well for a period of at least 5 days. I
know that I've seen other institutions implement such restrictions, and
you are sent an error message via standard POP protocol it appears, which
Eudora displays in the status telling you you are checking mail too
often. THis is more than sufficient. Any help or recommendations
would be GREATLY appreciated. Thanks in advance.<br><br>
PS - The client getting the descriptive error message is by FAR the most
important thing, as to avoid unnecessary calls to our helpdesk
people.<br><br>
<x-sigsep><p></x-sigsep>
---<br>
Tim Meader<br>
ACS Government Services, Inc. - (301) 286-8013<br>
tmeader at cne-odin.gsfc.nasa dot gov</font></html>
--=====================_621274195==_.ALT--
Date: Wed, 17 Apr 2002 08:11:51 -0700 (PDT)
From: The Little Prince <thelittleprince at asteroid-b612 dot org>
Subject: Re: UIDL/Maildir question
On Wed, 17 Apr 2002, Peter Evans wrote:
> The Little Prince (thelittleprince at asteroid-b612 dot org) wrote:
> > in my quest to finish my Maildir patch, i'm a little confused on how
> > UIDs/UIDLs work.
> > with my patch, first, Postfix generates no 'From blah blah' line, which it
> > looks like what a generated UID is made from? So right now it just does it
> > from the first line which is a Delivered-To header, and comes up with:
> > X-UIDL: _8,"!U16!!]AA!!6$X!!
> > I dont know if this is right, corrupted, or what?
>
> Horses for courses, there are already poppers that deal with maildir,
> why not use one of them. Don't try and bastardize qpopper.
>
> courier,
> qmail's pop3
> solidpop3d
> ...
>
> and probably a dozen others.
>
> Lets not make qpopper any more bloated than it already is with that
> evil mimemangling.
>
no offense, but I didn't ask for other maildir-capable pop3 solutions.
FWIW, i didn't decide to do this patch because i needed it (which i dont)
, but that i know others have expressed interest in such a feature.
and I dont understand how me asking how and EXISTING concept, like UIDL,
is done makes me bloat it with mimemangling.
--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"Strange, but it seems, there's a mutiny brewing inside of me"
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Date: Wed, 17 Apr 2002 11:12:29 -0400
From: Joseph S D Yao <jsdy at center.osis dot gov>
Subject: Re: qpopper on linux problem
On Wed, Apr 17, 2002 at 09:52:24AM +0800, jinjj at east165 dot net wrote:
> hi,
> I have Qpopper 4.0.4. I am installing it on a Red Hat 7.2 system.
> I am able to telnet to my local interface and eth0 and access Qpopper
> with no problem.
> ( telnet 127.0.0.1 110 or telnet 211.91.4.98 110 )
>
>
> However, when I attempt to telnet from another box on
> the same network, I get connection refused.
> telnet 211.91.4.98 110
> and i can not retrieve mail from the server. i was informed 'Time Out!'
>
> but i can do telnet 211.91.4.98 or ftp 211.91.4.98
>
> I looked at the
> troubleshooting guide to follow its instructions and I still have
> problems.
>
> I have no firewall on the system , and I use IP address instead of hostname .
>
> I have compile qpopper also as a part of xinetd or a standalone application. the problems are same.
>
> What do you suggest I look at next?
>
> Thanks,
>
> jinjj
> NingBo,China
I would suggest that you send this to the mailing list, where someone
may have had and solved this problem already. I vaguely remember that
there might be a way to restrict access per IP address, other than
using TCP wrappers, but I don't remember what it is.
--
Joe Yao jsdy at center.osis dot gov - Joseph S. D. Yao
OSIS Center Systems Support EMT-B
-----------------------------------------------------------------------
This message is not an official statement of OSIS Center policies.
Date: Wed, 17 Apr 2002 14:32:21 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: qpopper on linux problem
On Wed, 17 Apr 2002, Joseph S D Yao wrote:
> > However, when I attempt to telnet from another box on
> > the same network, I get connection refused.
> > telnet 211.91.4.98 110
> > and i can not retrieve mail from the server. i was informed 'Time Out!'
> >
> > but i can do telnet 211.91.4.98 or ftp 211.91.4.98
> > I have no firewall on the system , and I use IP address instead of hostname .
What about kernel firewalling rules?
The machine is linux, what distribution and version? Several ship with
quite stringent firewalling rules in place.
AB
Date: Wed, 17 Apr 2002 11:32:36 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Need aid with checking mail too often...
At 3:24 PM -0400 4/16/02, Tim Meader wrote:
>believe it or not many have their Eudora setup to autocheck every
>minute. This is unacceptable with almost 2000 users per machine.
>Especially considering that they regularly keep messages on server
>as well for a period of at least 5 days.
Make sure you're using the latest version (4.0.4) and have enabled
server mode. That way Qpopper keeps a cache file between mail
checks, so in the vast majority of those 1-minute POP checks, it
won't have to read the spool at all (just the cache). That should
make a *huge* difference.
(Of course, don't enable server mode for users that access the spool
through any means other than POP.)
> I know that I've seen other institutions implement such
>restrictions, and you are sent an error message via standard POP
>protocol it appears, which Eudora displays in the status telling you
>you are checking mail too often. THis is more than sufficient. Any
>help or recommendations would be GREATLY appreciated. Thanks in
>advance.
Qpopper does support the LOGIN-DELAY CAPA tag, which informs clients
of the minimum mail permitted mail check interval. However, I don't
think Eudora currently pays attention to this. If support for
LOGIN-DELAY would be important to you, be sure to let the Eudora
people know this. If you use some other client, let them know.
Qpopper doesn't currently enforce LOGIN-DELAY, but that wouldn't be a
terribly difficult patch. But try 4.0.4 server mode first, and see
if that helps enough.
From: "Don" <don at lclcan dot com>
Subject: compiling qpopper on SCO OS 5.0.5
Date: Wed, 17 Apr 2002 14:43:22 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_02CF_01C1E61E.395BA800
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I'm trying to compile Qpopper 4.0.3 on SCO OS 5.0.5. I've made the
changes to the make files but am getting the following error:
gcc: installation problem, cannot exec `cpp': No such file or directory
*** Error code 1 (bu21)
*** Error code 1 (bu21)
Using the SCO Open Server Development System. Any ideas?
------=_NextPart_000_02CF_01C1E61E.395BA800
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!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 5.50.4915.500" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I'm trying to compile Qpopper 4.0.3 on
SCO OS
5.0.5. I've made the changes to the make files but am getting the
following error:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>gcc: installation problem, cannot exec
`cpp': No
such file or directory<BR>*** Error code 1 (bu21)<BR>*** Error code 1
(bu21)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Using the SCO Open Server Development
System.
Any ideas?</FONT></DIV></BODY></HTML>
------=_NextPart_000_02CF_01C1E61E.395BA800--
Date: Wed, 17 Apr 2002 16:06:51 -0400 (EDT)
From: James Ralston <qralston+ml.qpopper at andrew.cmu dot edu>
Subject: two patches for qpopper 4.0.4
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime at docserver.cac.washington dot edu for more info.
---310360313-1221624866-1019074011=:17241
Content-Type: TEXT/PLAIN; charset=US-ASCII
Here are two simple patches for qpopper.
The first patch adds DESTDIR support for the "make install" step.
This is very handy for building packages (RPMs / .deb files) of
qpopper. (When building packages, software is installed into a
temporary directory hierarchy, instead of being installed directly to
the actual location.)
The second patch removes the double dashes from the NAME section of
the man pages. (Most catman/makewhatis packages expect only one dash,
and fail to catalog any of the qpopper package's man pages due to the
double dashes.)
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA
---310360313-1221624866-1019074011=:17241
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="qpopper4.0.4-destdir.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.44.0204171606510.17241 at pcmy.sei.cmu dot edu>
Content-Description:
Content-Disposition: attachment; filename="qpopper4.0.4-destdir.patch"
LS0tIHFwb3BwZXI0LjAuMy9wb3BwZXIvTWFrZWZpbGUuaW4uZGVzdGRpcglT
dW4gQXByIDIyIDE4OjU5OjE1IDIwMDENCisrKyBxcG9wcGVyNC4wLjMvcG9w
cGVyL01ha2VmaWxlLmluCU1vbiBBcHIgIDggMTM6NDA6MTkgMjAwMg0KQEAg
LTE5OSw4ICsxOTksOCBAQA0KICR7UE9QQVVUSFNSQ1N9Og0KIA0KIGluc3Rh
bGw6IHBvcHBlciAke3BvcF9hdXRofQ0KLQkke0lOU1RBTEx9IC1zIC1tIDA3
NTUgLW8gcm9vdCBwb3BwZXIgJHtpbnN0YWxsZGlyfS9wb3BwZXINCi0JZWNo
byAiSW5zdGFsbGVkIHBvcHBlciBhcyAke2luc3RhbGxkaXJ9L3BvcHBlciIN
CisJJHtJTlNUQUxMfSAtcyAtbSAwNzU1IHBvcHBlciAkKERFU1RESVIpJHtp
bnN0YWxsZGlyfS9wb3BwZXINCisJZWNobyAiSW5zdGFsbGVkIHBvcHBlciBh
cyAkKERFU1RESVIpJHtpbnN0YWxsZGlyfS9wb3BwZXIiDQogCWlmIFsgIngk
e3BvcHBhc3NkfSIgIT0gIngiIF07IHRoZW4gXA0KIAkgICAgY2QgJHtwYXNz
d29yZF9kaXJ9ICYmICR7TUFLRX0gJEAgO1wNCiAJZmkNCi0tLSBxcG9wcGVy
NC4wLjMvTWFrZWZpbGUuaW4uZGVzdGRpcglTdW4gQXByIDIyIDE4OjU5OjE0
IDIwMDENCisrKyBxcG9wcGVyNC4wLjMvTWFrZWZpbGUuaW4JTW9uIEFwciAg
OCAxMzo0MDoxOSAyMDAyDQpAQCAtNTgsMTAgKzU4LDEwIEBADQogCWNkICR7
cG9wcGVyX2Rpcn0gICYmICR7TUFLRX0gYWxsDQogDQogaW5zdGFsbDoNCi0J
JHtJTlNUQUxMfSAtbSAwNjQ0IC1vIHJvb3QgJHt0b3Bfc3JjZGlyfS9tYW4v
cG9wcGVyLjggICR7bWFuZGlyfS9tYW44Lw0KLQllY2hvICJJbnN0YWxsZWQg
bWFuL3BvcHBlci44IGFzICR7bWFuZGlyfS9tYW44L3BvcHBlci44Ig0KLQkk
e0lOU1RBTEx9IC1tIDA2NDQgLW8gcm9vdCAke3RvcF9zcmNkaXJ9L21hbi9w
b3BhdXRoLjggJHttYW5kaXJ9L21hbjgvDQotCWVjaG8gIkluc3RhbGxlZCBt
YW4vcG9wYXV0aC44IGFzICR7bWFuZGlyfS9tYW44L3BvcGF1dGguOCINCisJ
JHtJTlNUQUxMfSAtbSAwNjQ0ICR7dG9wX3NyY2Rpcn0vbWFuL3BvcHBlci44
ICAkKERFU1RESVIpJHttYW5kaXJ9L21hbjgvDQorCWVjaG8gIkluc3RhbGxl
ZCBtYW4vcG9wcGVyLjggYXMgJChERVNURElSKSR7bWFuZGlyfS9tYW44L3Bv
cHBlci44Ig0KKwkke0lOU1RBTEx9IC1tIDA2NDQgJHt0b3Bfc3JjZGlyfS9t
YW4vcG9wYXV0aC44ICQoREVTVERJUikke21hbmRpcn0vbWFuOC8NCisJZWNo
byAiSW5zdGFsbGVkIG1hbi9wb3BhdXRoLjggYXMgJChERVNURElSKSR7bWFu
ZGlyfS9tYW44L3BvcGF1dGguOCINCiAJY2QgJHtwb3BwZXJfZGlyfSAgJiYg
JHtNQUtFfSBpbnN0YWxsDQogDQogY2xlYW46DQo
---310360313-1221624866-1019074011=:17241
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="qpopper4.0.4-man.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.44.0204171606511.17241 at pcmy.sei.cmu dot edu>
Content-Description:
Content-Disposition: attachment; filename="qpopper4.0.4-man.patch"
LS0tIHFwb3BwZXI0LjAuMy9tYW4vcG9wYXV0aC44Lm1hbglUdWUgQXByICAz
IDIwOjIzOjEzIDIwMDENCisrKyBxcG9wcGVyNC4wLjMvbWFuL3BvcGF1dGgu
OAlNb24gQXByICA4IDE0OjQ1OjIzIDIwMDINCkBAIC05LDcgKzksNyBAQA0K
IC5cIg0KIC5USCBQT1BBVVRIIDgNCiAuU0ggTkFNRQ0KLXBvcGF1dGggXC1c
LSBtYW5pcHVsYXRlIFBPUCBhdXRob3JpemF0aW9uIERCDQorcG9wYXV0aCBc
LSBtYW5pcHVsYXRlIFBPUCBhdXRob3JpemF0aW9uIERCDQogLlNIIFNZTk9Q
U0lTDQogLkIgcG9wYXV0aA0KIFsNCi0tLSBxcG9wcGVyNC4wLjMvbWFuL3Bv
cHBhc3NkLjgubWFuCVR1ZSBBcHIgIDMgMjA6MjM6MTMgMjAwMQ0KKysrIHFw
b3BwZXI0LjAuMy9tYW4vcG9wcGFzc2QuOAlNb24gQXByICA4IDE0OjQ1OjE4
IDIwMDINCkBAIC04LDcgKzgsNyBAQA0KIC5cIg0KIC5USCBQT1BBVVRIIDgN
CiAuU0ggTkFNRQ0KLXBvcHBhc3NkIFwtXC0gcGFzc3dvcmQtY2hhbmdpbmcg
ZGFlbW9uDQorcG9wcGFzc2QgXC0gcGFzc3dvcmQtY2hhbmdpbmcgZGFlbW9u
DQogLlNIIFNZTk9QU0lTDQogLkIgcG9wcGFzc2QNCiBbDQotLS0gcXBvcHBl
cjQuMC4zL21hbi9wb3BwZXIuOC5tYW4JVHVlIEFwciAgMyAyMDoyMzoxMyAy
MDAxDQorKysgcXBvcHBlcjQuMC4zL21hbi9wb3BwZXIuOAlNb24gQXByICA4
IDE0OjQ1OjEyIDIwMDINCkBAIC0xNyw3ICsxNyw3IEBADQogLlVDIDYNCiAu
YWQNCiAuU0ggTkFNRQ0KLXFwb3BwZXIgXC1cLSBQT1AzIHNlcnZlciAodjQu
MCkNCitxcG9wcGVyIFwtIFBPUDMgc2VydmVyICh2NC4wKQ0KIC5TSCBTWU5P
UFNJUw0KIC5CIC91c3IvbG9jYWwvbGliL3BvcHBlcg0KIFsNCg=
---310360313-1221624866-1019074011=:17241--
Date: Wed, 17 Apr 2002 08:37:17 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: qpopper on linux problem
On Wed, Apr 17, 2002 at 11:12:29AM -0400, Joseph S D Yao wrote:
> On Wed, Apr 17, 2002 at 09:52:24AM +0800, jinjj at east165 dot net wrote:
> > hi,
> > I have Qpopper 4.0.4. I am installing it on a Red Hat 7.2 system.
> > I am able to telnet to my local interface and eth0 and access Qpopper
> > with no problem.
> > ( telnet 127.0.0.1 110 or telnet 211.91.4.98 110 )
> >
> > However, when I attempt to telnet from another box on
> > the same network, I get connection refused.
> > telnet 211.91.4.98 110
> > and i can not retrieve mail from the server. i was informed 'Time Out!'
> >
> > but i can do telnet 211.91.4.98 or ftp 211.91.4.98
This definitely sounds like a firewall problem.
> > I looked at the
> > troubleshooting guide to follow its instructions and I still have
> > problems.
> >
> > I have no firewall on the system , and I use IP address instead of hostname .
If you're on Redhat 7.2, I believe you have a firewall installed by
default whether or not you are aware of it. I don't use Linux much so
I can't tell you what config file to look at.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
Date: Wed, 17 Apr 2002 18:03:42 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: Need aid with checking mail too often...
On Wed, 17 Apr 2002, Randall Gellens wrote:
> I agree there should be an option in Qpopper to enforce login-delay.
> If the clients supports the LOGIN-DELAY tag, then some administrators
> might choose to advertise but not enforce it. This would prevent
> users from setting an automatic mail check that was too frequent, but
> still allow a user who was expecting something important to do manual
> mail checks more often.
The way to satisfy both requirements is to allow 4-5 login-delay
violations, then start enforcing it. That requires some more logic than
just checking the timestamp on the tmp file.
AB
Date: Wed, 17 Apr 2002 15:53:50 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: two patches for qpopper 4.0.4
At 4:06 PM -0400 4/17/02, James Ralston wrote:
>The second patch removes the double dashes from the NAME section of
>the man pages. (Most catman/makewhatis packages expect only one dash,
>and fail to catalog any of the qpopper package's man pages due to the
>double dashes.)
That's a shame, since one hyphen is incorrect usage. What's really
wanted here is an em-dash, and the way to represent an em-dash with
US-ASCII is to use two hyphens. Sadly, (mis)using just one hyphen is
all too common.
Date: Wed, 17 Apr 2002 16:58:57 -0400
From: Steve Perrault <sperraul at mnsi dot net>
Subject: Re: Need aid with checking mail too often...
I'm dealing with the next order of magnitude of users, many checking every
minute. We're logging 150-200 pop sessions/minute. However, this frequent
checking (especially with LMOS) is more of an annoyance to ME than
affecting anyone.
I've considered modifying the qpopper source to keep the connection open
for x minutes after the customer closes the session. I'd also change the
pop lock error message to explain it (instead of the POP lock
busy). However, any changes to customers will just get them calling in,
regardless of how well I explain things in the error message. My poor tech
support reps will be tied up:
1) explaining why they can't check mail "like the always have"
2) justifying our policy to the people who understand it
3) spend x minutes waiting for pop sessions to time out after the customer
attempts to check mail
- SteveP
At 03:24 PM 4/16/2002 -0400, you wrote:
>Hello all,
>
>I was just wondering if anyone knew of a commonly used program used in
>conjunction with Qpopper, or perhaps even a widely used patch, that would
>enable me to limit the frequency with which users check their
>mail. Currently there is no such limit, and believe it or not many have
>their Eudora setup to autocheck every minute. This is unacceptable with
>almost 2000 users per machine. Especially considering that they regularly
>keep messages on server as well for a period of at least 5 days. I know
>that I've seen other institutions implement such restrictions, and you are
>sent an error message via standard POP protocol it appears, which Eudora
>displays in the status telling you you are checking mail too often. THis
>is more than sufficient. Any help or recommendations would be GREATLY
>appreciated. Thanks in advance.
>
>PS - The client getting the descriptive error message is by FAR the most
>important thing, as to avoid unnecessary calls to our helpdesk people.
>
>---
>Tim Meader
>ACS Government Services, Inc. - (301) 286-8013
>tmeader at cne-odin.gsfc.nasa dot gov
Date: Wed, 17 Apr 2002 17:10:03 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: Need aid with checking mail too often...
On Wed, 17 Apr 2002, Randall Gellens wrote:
> At 3:24 PM -0400 4/16/02, Tim Meader wrote:
>
> >believe it or not many have their Eudora setup to autocheck every
> >minute. This is unacceptable with almost 2000 users per machine.
It's unacceptable most times and really does need some form of throttle.
passwd -l works well.
> Qpopper does support the LOGIN-DELAY CAPA tag, which informs clients
> of the minimum mail permitted mail check interval.
It doesn't enforce it.
> However, I don't
> think Eudora currently pays attention to this.
I don't believe any package pays attention to it.
> Qpopper doesn't currently enforce LOGIN-DELAY, but that wouldn't be a
> terribly difficult patch. But try 4.0.4 server mode first, and see
> if that helps enough.
I believe it should be patched. There are a few packages which are
obnoxiously set by default and a clueless user repeatedly hitting "check
mail" with a large inbox can affect system load badly, even in server
mode.
AB
Date: Wed, 17 Apr 2002 15:38:29 -0400 (EDT)
From: James Ralston <qralston+ml.qpopper at andrew.cmu dot edu>
Subject: disabling the XTND XMIT command
Qpopper (version 4.0.4, at least) does not provide an easy way to
disable support for the XNTD XMIT command. In order to disable it
when I built qpopper for our site, I had to remove its entry from the
subcommands table in popper/pop_get_subcommand.c.
IMO, any feature that cannot be disabled is a bug. Qpopper should
provide an easy mechanism (a ./configure flag, a qpopper command-line
flag, and/or a config file variable) to disable this feature.
If the qpopper maintainers would be willing to accept it, I'd be
willing to produce a patch to implement the above behavior. Let me
know.
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA
Date: Wed, 17 Apr 2002 14:25:30 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Need aid with checking mail too often...
At 5:10 PM -0400 4/17/02, Alan Brown wrote:
>I believe it should be patched. There are a few packages which are
>obnoxiously set by default and a clueless user repeatedly hitting "check
>mail" with a large inbox can affect system load badly, even in server
>mode.
I agree there should be an option in Qpopper to enforce login-delay.
If the clients supports the LOGIN-DELAY tag, then some administrators
might choose to advertise but not enforce it. This would prevent
users from setting an automatic mail check that was too frequent, but
still allow a user who was expecting something important to do manual
mail checks more often.
From: Lars Nordin <lnordin at noblesys dot com>
Subject: Re: compiling qpopper on SCO OS 5.0.5
Date: Wed, 17 Apr 2002 18:32:06 -0400
Do you have gcc installed?
It is not clear to me which one is trying to be used.
You may need to explictly tell configure to use cc, I think that I had to do
this for v3.1.2.
On Wednesday 17 April 2002 02:43 pm, Don wrote:
> Hi,
>
> I'm trying to compile Qpopper 4.0.3 on SCO OS 5.0.5. I've made the changes
> to the make files but am getting the following error:
>
> gcc: installation problem, cannot exec `cpp': No such file or directory
> *** Error code 1 (bu21)
> *** Error code 1 (bu21)
>
> Using the SCO Open Server Development System. Any ideas?
Date: Wed, 17 Apr 2002 18:35:33 -0700 (PDT)
From: The Little Prince <thelittleprince at asteroid-b612 dot org>
Subject: Re: Need aid with checking mail too often...
On Wed, 17 Apr 2002, Steve Perrault wrote:
> I've considered modifying the qpopper source to keep the connection open
> for x minutes after the customer closes the session. I'd also change the
boy, i dont know about that..holding a process entry and memory usage
(that could be spent in another 'active' pop session) to just do a wait.
and if you were the customer, would you really sit there for 4-5 mins
while your mail client just sat there while qpopper held the connection
open. they'd be clicking cancel and closing the connection from their end.
i think i'd rather see the unixtime of login written to the user's cache
file and a config file/user file option of letting them only check every x
minutes (like someone said).
if (((current_time - last_login_time)/60) < LOGIN_DELAY_MINS) you can't
check your mail again this soon, blah blah blah, close connection.
--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"Strange, but it seems, there's a mutiny brewing inside of me"
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
>
> At 03:24 PM 4/16/2002 -0400, you wrote:
> >Hello all,
> >
> >I was just wondering if anyone knew of a commonly used program used in
> >conjunction with Qpopper, or perhaps even a widely used patch, that would
> >enable me to limit the frequency with which users check their
> >mail. Currently there is no such limit, and believe it or not many have
> >their Eudora setup to autocheck every minute. This is unacceptable with
> >almost 2000 users per machine. Especially considering that they regularly
> >keep messages on server as well for a period of at least 5 days. I know
> >that I've seen other institutions implement such restrictions, and you are
> >sent an error message via standard POP protocol it appears, which Eudora
> >displays in the status telling you you are checking mail too often. THis
> >is more than sufficient. Any help or recommendations would be GREATLY
> >appreciated. Thanks in advance.
> >
> >PS - The client getting the descriptive error message is by FAR the most
> >important thing, as to avoid unnecessary calls to our helpdesk people.
> >
> >---
> >Tim Meader
> >ACS Government Services, Inc. - (301) 286-8013
> >tmeader at cne-odin.gsfc.nasa dot gov
>
>
--
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
thelittleprince at asteroid-b612.org http://www.asteroid-b612 dot org
"Strange, but it seems, there's a mutiny brewing inside of me"
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
From: peter at netlink.com dot au
Subject: Re: Need aid with checking mail too often...
Date: Thu, 18 Apr 2002 12:07:56 +1000 (EST)
We too have a problem with:
- some users checking mail too frequently
- some users leaving large amounts of mail on the server
- compounded with some few users who do both!
Running qpopper 4.0.3, using inetd, linux and peaking at around 100 pop sessions
per minute (24 hour average is around 30 per minute).
Although the point made about qpopper's server mode lessening problems caused by
large maiboxes is good (in fact this was a great improvement for us), there is
still a considerable extra load on the server caused by leaving large amounts of
mail on the server. One problem is that users make frequent failed attempts to
download the mail - not grasping the fact that some patience is required. It also
seems to me that qpopper will still have to 'index' the mailbox each time it is
accessed and calculate uidl's (someone correct me if I'm wrong in this).
In order to provide a *fair* and workable mail service for all, we have implemented
two 'policing' systems:
1. The poplog is periodically checked and users who are checking mail at, say
more than 10 times in 10 minutes are added to qpopper's 'nonauth' file and
thus prevented from acessing mail for, say a 30 minute period
2. All mailboxes are checked in the early hours of the morning and any exceeding
a specified size limit (eg. 10Mb) are prevented from receiving additional mail
as well as added to the qpopper 'nonauth' file - this time they cannot be removed
except by a manual process (eg. if the user calls the helpdesk the problem is
explained and the blocks are removed).
Both systems are fully automated (via scripts run from crontab) and exceptions are
allowed (for example some corporate customers using fetchmail to distribute mail
to users whose mailbox can grow very large).
If anything implementing this policy has slightly increased the workload on our
helpdesk, however most users (we are a dial-up isp) are unable or unwilling to download
large mailboxes so would have called the helpdesk anyway and the frequent poppers
(some of whom are constantly getting 'blocked') were not responding to other, less
drastic measures.
The only thing I can't be sure of is that these measures have actually reduced server
load or improved server performance :-;
The point made in the original post re notifying users of the problem is a good one and
we should do this (obviously pointless for the large mailboxes).
If anyone else has ideas or experience I would be interested to hear them...
Regards, Peter
Netlink Connect, Australia
>
> I'm dealing with the next order of magnitude of users, many checking every
> minute. We're logging 150-200 pop sessions/minute. However, this frequent
> checking (especially with LMOS) is more of an annoyance to ME than
> affecting anyone.
>
> I've considered modifying the qpopper source to keep the connection open
> for x minutes after the customer closes the session. I'd also change the
> pop lock error message to explain it (instead of the POP lock
> busy). However, any changes to customers will just get them calling in,
> regardless of how well I explain things in the error message. My poor tech
> support reps will be tied up:
>
> 1) explaining why they can't check mail "like the always have"
> 2) justifying our policy to the people who understand it
> 3) spend x minutes waiting for pop sessions to time out after the customer
> attempts to check mail
>
>
> - SteveP
>
> At 03:24 PM 4/16/2002 -0400, you wrote:
> >Hello all,
> >
> >I was just wondering if anyone knew of a commonly used program used in
> >conjunction with Qpopper, or perhaps even a widely used patch, that would
> >enable me to limit the frequency with which users check their
> >mail. Currently there is no such limit, and believe it or not many have
> >their Eudora setup to autocheck every minute. This is unacceptable with
> >almost 2000 users per machine. Especially considering that they regularly
> >keep messages on server as well for a period of at least 5 days. I know
> >that I've seen other institutions implement such restrictions, and you are
> >sent an error message via standard POP protocol it appears, which Eudora
> >displays in the status telling you you are checking mail too often. THis
> >is more than sufficient. Any help or recommendations would be GREATLY
> >appreciated. Thanks in advance.
> >
> >PS - The client getting the descriptive error message is by FAR the most
> >important thing, as to avoid unnecessary calls to our helpdesk people.
> >
> >---
> >Tim Meader
> >ACS Government Services, Inc. - (301) 286-8013
> >tmeader at cne-odin.gsfc.nasa dot gov
>
>
Date: Wed, 17 Apr 2002 22:05:49 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: disabling the XTND XMIT command
At 3:38 PM -0400 4/17/02, James Ralston wrote:
> Qpopper (version 4.0.4, at least) does not provide an easy way to
> disable support for the XNTD XMIT command.
Have you tried setting the 'mail-command' option to something bogus?
There doesn't appear to be any error checking in the code, so this
won't give a nice error message, but it will prevent XTND XMIT from
working. You could even try having 'mail-command' point at a shell
script that prints an error message.
From the sample config 'sample/qpopper.config':
# Set this to the full path to sendmail or other such program used to
# submit new messages. Qpopper uses this to implement XTND XMIT.
#
# The default is determined at compile time.
#
#
# set mail-command = /usr/sbin/sendmail
Date: Thu, 18 Apr 2002 08:42:44 +0100 (BST)
From: AA <aish at infinitum-global dot net>
I installed the QPopper4.0.4 and followed the instructions in the manual.
I added the following line to /etc/inetd,conf:
pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -s
I also checked /etc/services to ensure that pop3 had been included and
found the following line under the 'Network services, Internet style'
pop3 110/tcp # Post Office Protocol - Version 3
According to the manual, this is correct, but when I try to telnet I
receive the following message:
telnet: Unable to connect to remote host: Connection refused
The manual states that this is because the port name pop3 is not the same
as the one in inetd.conf, but as the above demonstrates this is not the
case.
Could you possibly help me with this?
I am using
QPopper4.0.4
Solaris 8
Thanks.
Ayasha
Date: Thu, 18 Apr 2002 01:08:16 -0700 (PDT)
From: Chad <chad_ny_01 at yahoo dot com>
Subject: Re: Need aid with checking mail too often...
Hi Group,
I've spent the last two days searching Google and
other search engines for good links to qpopper mailing
lists -now that I've found you <g> -I think it's
ironic the very dilemma that sent me searching the net
for a solution, is a hot thread on the new mailing
list I just discovered. :-)
The James Bond crowd really has me under the weather.
You know the ones, the users with 5-12 user accounts,
who now have that blazing fast access connection and
thinks they check all 12 user accounts in 60 second
intervals -just waiting for that next message to
arrive. Iíve begged, preached, offered instruction on
good net etiquette and system usage, Iíve tried to
convey the of shared web hosting ñand how everyone
shares the bus and gets to ride for a REAL small
price.. But seriously, over the last year, for me
personally, this has become a major problem. Take JB
and multiply him/her by say 100 or so domains <frown>.
Currently, current systems are all running older
versions of qpopper (3.x) under initd and consume well
over 50-70% of all the total CPU cycles used. The good
news is, I just built a system with Qpopper 4.0.4 as
stand alone, so all that's going to change a great
deal here real soon (I do believe)... But there's
still something about this issue that just screams
"greedy".. Itís like my users who open a half dozen
FTP sessions (on a 56k line) just because they think
itís makes the upload go faster.. <?> I'd thoroughly
enjoy finding a way to throttle the James Bond crew
from banging on qpopper with a dozen or more IDís more
than once every 5 minutes or so... (oh, to be a fly on
that wall). <g>
I'm very interested in hearing what others are
experiencing in regards to this issue and/or any
possible solutions or suggestions that can be imposed
on a system to limit the freq of login POP's....
Best Regards,
Chad
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
Date: Thu, 18 Apr 2002 11:53:59 +0200
From: Patrick Guillot <pguillot at paanjaru dot com>
Subject: Re: compiling qpopper on SCO OS 5.0.5
Don,
> I'm trying to compile Qpopper 4.0.3 on SCO OS 5.0.5. I've made the
> changes to the make files but am getting the following error:
>
> gcc: installation problem, cannot exec `cpp': No such file or
> directory
> *** Error code 1 (bu21)
> *** Error code 1 (bu21)
>
> Using the SCO Open Server Development System. Any ideas?
Cpp is the Gnu C preprocessor : It seems your install of gcc
is not complete. Try a __which cpp__ ( or find ) to find if cpp
is at least installed somewhere. Maybe go to http://gcc.gnu.org
to find more informations.
Have you eve compiled something else than qpopper with GCC ?
Patrick
--
Patrick Guillot mailto:pguillot at paanjaru dot com - +33 (0)6 08 41 11 54
Online Development - Paanjaru http://www.paanjaru.com
Riding the Shockwave in cyberspace, for now ... and ever
Date: Thu, 18 Apr 2002 08:29:05 -0500
From: Butch Kemper <kemper at tstar dot net>
Subject: Re: Qpopper Won't Start
Did you restart "inetd" so that it would read the new configuration file?
Did you check the log to see if inetd was having problems starting qpopper?
Butch
At 02:42 AM 4/18/02, you wrote:
>I installed the QPopper4.0.4 and followed the instructions in the manual.
>I added the following line to /etc/inetd,conf:
>
>pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -s
>
>I also checked /etc/services to ensure that pop3 had been included and
>found the following line under the 'Network services, Internet style'
>
>pop3 110/tcp # Post Office Protocol - Version 3
>
>According to the manual, this is correct, but when I try to telnet I
>receive the following message:
>
>telnet: Unable to connect to remote host: Connection refused
>
>The manual states that this is because the port name pop3 is not the same
>as the one in inetd.conf, but as the above demonstrates this is not the
>case.
>
>Could you possibly help me with this?
>
>I am using
>
>QPopper4.0.4
>Solaris 8
>
>Thanks.
>
>Ayasha
TSTAR Internet, Inc | Making the Net Work
Marble Falls, TX | Serving Blanco, Burnet,
830-693-6967 | Llano, and Mason Counties
From: "Chris Payne" <cpayne at pr.uoguelph dot ca>
Date: Thu, 18 Apr 02 10:53:57 -0500
Subject: Re: Qpopper Won't Start
Make sure that you used a TAB between parameters, not spaces
otherwise Inetd will not recognize the command string and
abort the loading.
- Chris Payne
On Thu, 18 Apr 2002 08:29:05 -0500, Butch Kemper wrote:
>Did you restart "inetd" so that it would read the new configuration file?
>
>Did you check the log to see if inetd was having problems starting qpopper?
>
>Butch
>
>At 02:42 AM 4/18/02, you wrote:
>>I installed the QPopper4.0.4 and followed the instructions in the manual.
>>I added the following line to /etc/inetd,conf:
>>
>>pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -s
>>
>>I also checked /etc/services to ensure that pop3 had been included and
>>found the following line under the 'Network services, Internet style'
>>
>>pop3 110/tcp # Post Office Protocol - Version 3
>>
>>According to the manual, this is correct, but when I try to telnet I
>>receive the following message:
>>
>>telnet: Unable to connect to remote host: Connection refused
>>
>>The manual states that this is because the port name pop3 is not the same
>>as the one in inetd.conf, but as the above demonstrates this is not the
>>case.
>>
>>Could you possibly help me with this?
>>
>>I am using
>>
>>QPopper4.0.4
>>Solaris 8
>>
>>Thanks.
>>
>>Ayasha
>
>
>TSTAR Internet, Inc | Making the Net Work
>Marble Falls, TX | Serving Blanco, Burnet,
>830-693-6967 | Llano, and Mason Counties
>
- -
Chris Payne
Network Administrator
Physical Resources Dept,
University of Guelph
(519)824-4120 x2882
cpayne at pr.uoguelph dot ca
Date: Thu, 18 Apr 2002 15:59:22 +0100 (BST)
From: AA <aish at infinitum-global dot net>
Subject: Re: Qpopper Won't Start
It's working now.. once I restarted inetd. Thanks for your help.
Ayasha
On Thu, 18 Apr 2002, Chris Payne wrote:
> Make sure that you used a TAB between parameters, not spaces
> otherwise Inetd will not recognize the command string and
> abort the loading.
>
> - Chris Payne
>
>
>
> On Thu, 18 Apr 2002 08:29:05 -0500, Butch Kemper wrote:
>
> >Did you restart "inetd" so that it would read the new configuration file?
> >
> >Did you check the log to see if inetd was having problems starting qpopper?
> >
> >Butch
> >
> >At 02:42 AM 4/18/02, you wrote:
> >>I installed the QPopper4.0.4 and followed the instructions in the manual.
> >>I added the following line to /etc/inetd,conf:
> >>
> >>pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -s
> >>
> >>I also checked /etc/services to ensure that pop3 had been included and
> >>found the following line under the 'Network services, Internet style'
> >>
> >>pop3 110/tcp # Post Office Protocol - Version 3
> >>
> >>According to the manual, this is correct, but when I try to telnet I
> >>receive the following message:
> >>
> >>telnet: Unable to connect to remote host: Connection refused
> >>
> >>The manual states that this is because the port name pop3 is not the same
> >>as the one in inetd.conf, but as the above demonstrates this is not the
> >>case.
> >>
> >>Could you possibly help me with this?
> >>
> >>I am using
> >>
> >>QPopper4.0.4
> >>Solaris 8
> >>
> >>Thanks.
> >>
> >>Ayasha
> >
> >
> >TSTAR Internet, Inc | Making the Net Work
> >Marble Falls, TX | Serving Blanco, Burnet,
> >830-693-6967 | Llano, and Mason Counties
> >
>
>
> - -
>
> Chris Payne
> Network Administrator
> Physical Resources Dept,
> University of Guelph
> (519)824-4120 x2882
> cpayne at pr.uoguelph dot ca
>
>
>
>
Date: Thu, 18 Apr 2002 11:45:46 -0400 (EDT)
From: Chip Old <fold at bcpl dot net>
Subject: Re: Need aid with checking mail too often...
On Wed, 17 Apr 2002, Randall Gellens wrote to Alan Brown:
> I agree there should be an option in Qpopper to enforce login-delay.
> If the clients supports the LOGIN-DELAY tag, then some administrators
> might choose to advertise but not enforce it. This would prevent users
> from setting an automatic mail check that was too frequent, but still
> allow a user who was expecting something important to do manual mail
> checks more often.
Sounds like there's fairly strong sentiment on the list in favor of being
able to enforce LOGIN-DELAY. Can we expect that soon? I know it would
help here. We have a lot of our 9000 +/- customers hitting the POP server
at very shorty intervals, and getting then to voluntarily limit their
polling to once every 4 or 5 minutes is impossible.
--
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: "Stephen Conway" <sconway at wlnet dot com>
Subject: A lot of timeouts
Date: Thu, 18 Apr 2002 12:39:03 -0400
Good day:
We are using qpopper4.0.3 on a P4 1.5Ghz with 1Gb RAM, server running
Slackware Linux version 8.0 (kernel 2.4.5). Currently running in inetd
as
"pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -s
-R" . We have seen no problems connecting on the LAN but within the
last couple days we have seen an increase in timeouts and .pop files
remaining, as if there is some sort of network problems occurring. With
larger mailboxes, some only even 1Mb , this is happening. I have
tracerouted from some of the problem networks to us, and back and the
connections are all fine, I have tried to change hubs that the server is
on and the problem remains, could this be a problem with the network
card or something? Is it a qpopper problem? I have added the -R above
to try and reduce the time of connection, but it is still the same. Any
assistance is appreciated, we are using an onboard Intel Ethernet
adapter.
Thanks,
Steve
Date: Thu, 18 Apr 2002 09:59:59 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Need aid with checking mail too often...
At 12:07 PM +1000 4/18/02, peter at netlink.com dot au wrote:
> It also
> seems to me that qpopper will still have to 'index' the mailbox
> each time it is
> accessed and calculate uidl's (someone correct me if I'm wrong in this).
UIDs are cached, so if no new mail arrived since the last mail check,
there is no need to read the spool.
From: "Lisa Casey" <lisa at jellico dot com>
Subject: Bulletin does not start with a valid "From " separator
Date: Thu, 18 Apr 2002 14:09:43 -0400
Hi,
I have compiled qpopper 4.0.3 with support for bulletins and read the
Administrators Guide on writing bulletins. But when I create a bulletin in
/var/spool/bull I get the following error message in /var/log/messages:
Bulletin 000100.message_4-18-02 does not start with a valid "From "
separator
When I created the bulletin, I used a text editor on the system to write
this:
i2000# more 000100.message_4-18-02
From qpop Thurs Apr 18 13:47:00 2002
Date: Thurs, 18 April 2002 13:47:00
To: user@localhost
From: Lisa Casey <lisa at jellico dot net>
Subject: Spam Filter Update
Greetings Members,
Just wanted to let you know that we are still working on the Spam
Filtering for our e-mail server and hope to have it working within
a month or less. Those of you who do not wish to participate in
this will not have to. I'll keep you updated on this.
Lisa Casey
Netlink 2000, Inc.
lisa at jellico dot net
What did I do wrong?
Thanks,
Lisa Casey, Webmaster
Netlink 2000, Inc.
lisa at jellico dot net
Date: Thu, 18 Apr 2002 08:58:47 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Bulletin does not start with a valid "From " separator
On Thu, Apr 18, 2002 at 02:09:43PM -0400, Lisa Casey wrote:
> Hi,
>
> I have compiled qpopper 4.0.3 with support for bulletins and read the
> Administrators Guide on writing bulletins. But when I create a bulletin in
> /var/spool/bull I get the following error message in /var/log/messages:
>
> Bulletin 000100.message_4-18-02 does not start with a valid "From "
> separator
>
> When I created the bulletin, I used a text editor on the system to write
> this:
>
> i2000# more 000100.message_4-18-02
> >From qpop Thurs Apr 18 13:47:00 2002
The allowable date formats in the From line are very limited. Copy the
format exactly from the first line in your mailbox. At a glance, the
"Thurs" there is probably invalid.
Try instead:
From localhost!qpop Thu Apr 10 13:47:00 2002
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
"What do we need to make our world come alive?
What does it take to make us sing?
While we're waiting for the next one to arrive..." - Sisters of Mercy
Date: Thu, 18 Apr 2002 11:48:25 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: A lot of timeouts
At 12:39 PM -0400 4/18/02, Stephen Conway wrote:
>we have seen an increase in timeouts and .pop files
>remaining, as if there is some sort of network problems occurring.
Timeouts, or other reasons for aborted sessions, should not result in
left-over .pop files hanging around. The Qpopper process should
clean up, no matter why the session ended (not counting being killed,
of course).
Are you completely sure that there are no Qpopper processes still
active when you see the .pop files?
You might try turning on debug tracing. If the problems only happen
for some users, you can turn on tracing for them only (using a
user-specific configuration file).
From: "Houman Langroodi" <houman88 at hotmail dot com>
Subject: REMOVE
Date: Thu, 18 Apr 2002 18:39:00 +0000
REMOVE
_________________________________________________________________
Join the worldís largest e-mail service with MSN Hotmail.
http://www.hotmail.com
Last updated on 18 Apr 2002 by Pensive Mailing List Admin