The qpopper list archive ending on 16 Apr 2002
Topics covered in this issue include:
1. Re: Please Test Qpopper 4.0.4fc3
Scott McDermott <mcdermot at questra dot com>
Tue, 9 Apr 2002 16:42:05 -0400
2. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Scott McDermott <mcdermot at questra dot com>
Tue, 9 Apr 2002 17:06:33 -0400
3. Re: Please Test Qpopper 4.0.4fc3
Randall Gellens <randy at qualcomm dot com>
Tue, 9 Apr 2002 12:10:50 -0700
4. RE: Qpopper 4.0.4fc3 Need Help
Daniel Senie <dts at senie dot com>
Tue, 09 Apr 2002 16:18:02 -0400
5. Re: Please Test Qpopper 4.0.4fc3
Alan Brown <alanb at digistar dot com>
Tue, 9 Apr 2002 17:17:47 -0400 (EDT)
6. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Clifton Royston <cliftonr at lava dot net>
Tue, 9 Apr 2002 14:01:15 -1000
7. Re: Please Test Qpopper 4.0.4fc3
Randall Gellens <randy at qualcomm dot com>
Tue, 9 Apr 2002 15:11:39 -0700
8. Re: Please Test Qpopper 4.0.4fc3
Oliver Fleischmann <ogf at bnv-bamberg dot de>
Tue, 9 Apr 2002 21:51:28 +0200 (MEST)
9. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Scott McDermott <mcdermot at questra dot com>
Tue, 9 Apr 2002 23:17:38 -0400
10. Re: Qpopper 4.0.4fc3 Need Help
Joseph S D Yao <jsdy at center.osis dot gov>
Tue, 9 Apr 2002 17:04:24 -0400
11. When to use qpopper?
PM WONG <pmwong at power25t.hkbu.edu dot hk>
Fri, 12 Apr 2002 09:31:10 +0800 (HKT)
12. Re: Suggestion for a new and enhanced "server mode"
Jesus Cea Avion <jcea at argo dot es>
Thu, 11 Apr 2002 20:07:51 +0200
13. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new
Randall Gellens <randy at qualcomm dot com>
Wed, 10 Apr 2002 15:23:13 -0700
14. Re: Please Test Qpopper 4.0.4fc3
hypnose at t-online dot de (guenter wessling)
Wed, 10 Apr 2002 00:00:09 +0200
15. Re: When to use qpopper?
Alan Brown <alanb at digistar dot com>
Fri, 12 Apr 2002 06:51:23 -0400 (EDT)
16. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Thu, 11 Apr 2002 11:52:39 +0200
17. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Scott McDermott <mcdermot at questra dot com>
Wed, 10 Apr 2002 21:43:43 -0400
18. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Scott McDermott <mcdermot at questra dot com>
Wed, 10 Apr 2002 23:25:43 -0400
19. TLS/SSL question
Mark Wendt <wendt at kingcrab.nrl.navy dot mil>
Fri, 12 Apr 2002 07:51:41 -0400
20. version check w/ bsdi4.2
Jeff Donovan <jdonovan at beth.k12.pa dot us>
Wed, 10 Apr 2002 08:06:29 -0400
21. Re: When to use qpopper?
Michal Jeczalik <listy at samotnia.eu dot org>
12 Apr 2002 14:47:44 +0200
22. qpopper110.cfg Need Help
"Matthew D. Hon" <matthewhon at iname dot com>
Thu, 11 Apr 2002 12:58:50 -0500
23. Re: When to use qpopper?
Thomas Eisenbarth <eisenbarth at planet-design-don dot de>
Fri, 12 Apr 2002 16:54:42 +0200
24. Re: Please Test Qpopper 4.0.4fc3
"Christopher Crowley" <ccrowley at tulane dot edu>
Wed, 10 Apr 2002 14:12:01 -0500
25. Re: Please Test Qpopper 4.0.4fc3
Ayamura KIKUCHI <ayamura at ayamura dot org>
Wed, 10 Apr 2002 18:55:20 +0900
26. Re: TLS/SSL question
Mark Wendt <wendt at kingcrab.nrl.navy dot mil>
Fri, 12 Apr 2002 13:31:17 -0400
27. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Clifton Royston <cliftonr at lava dot net>
Fri, 12 Apr 2002 10:55:23 -1000
28. Re: TLS/SSL question
Clifton Royston <cliftonr at lava dot net>
Fri, 12 Apr 2002 11:42:52 -1000
29. Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new
Randall Gellens <randy at qualcomm dot com>
Wed, 10 Apr 2002 15:27:16 -0700
30. Re: Suggestion for a new and enhanced "server mode"
Joseph S D Yao <jsdy at center.osis dot gov>
Fri, 12 Apr 2002 12:12:05 -0400
31. Qpopper Error - Please Help
"Matthew D. Hon" <matthewhon at iname dot com>
Fri, 12 Apr 2002 11:26:18 -0500
32. Qpopper 4.0.4 (final) available
Randall Gellens <randy at qualcomm dot com>
Fri, 12 Apr 2002 17:03:38 -0700
33. Re: version check w/ bsdi4.2
Randall Gellens <randy at qualcomm dot com>
Fri, 12 Apr 2002 17:06:21 -0700
34. Re: TLS/SSL question
Randall Gellens <randy at qualcomm dot com>
Fri, 12 Apr 2002 17:12:30 -0700
35. RE: When to use qpopper?
"Chris" <yahoogroups at xymox1 dot com>
Fri, 12 Apr 2002 11:03:20 -0700
36. Re: TLS/SSL question
Clifton Royston <cliftonr at lava dot net>
Fri, 12 Apr 2002 17:04:11 -1000
37. Please Help - Regarding alias name
kkim at telcordia dot com
Fri, 12 Apr 2002 15:11:48 -0400
38. Correct Syntax for home-dir-mail
"Lyle Schofield" <Lyle.Schofield at daou dot com>
Fri, 12 Apr 2002 10:32:20 -0400
39. RE: Qpopper 4.0.4fc3 Need Help
Kenneth Porter <shiva at well dot com>
10 Apr 2002 06:38:45 -0700
40. Re: Qpopper 4.0.4 (final) available
The Doctor <doctor at doctor.nl2k.ab dot ca>
Sat, 13 Apr 2002 09:55:38 -0600
41. Re: Suggestion for a new and enhanced "server mode"
Jesus Cea Avion <jcea at argo dot es>
Thu, 11 Apr 2002 20:11:32 +0200
42. Re: Qpopper 4.0.4 (final) available
Randall Gellens <randy at qualcomm dot com>
Sat, 13 Apr 2002 12:04:17 -0700
43. Re: qpopper110.cfg Need Help
Randall Gellens <randy at qualcomm dot com>
Fri, 12 Apr 2002 17:08:07 -0700
44. Re: TLS/SSL question
Daniel Senie <dts at senie dot com>
Fri, 12 Apr 2002 12:45:45 -0400
45. Re: Qpopper 4.0.4 (final) available
The Doctor <doctor at doctor.nl2k.ab dot ca>
Sat, 13 Apr 2002 08:38:23 -0600
46. Re: version check w/ bsdi4.2
Clifton Royston <cliftonr at lava dot net>
Fri, 12 Apr 2002 10:57:06 -1000
47. DRAC support for 4.0.4
Ayamura KIKUCHI <ayamura at ayamura dot org>
Tue, 16 Apr 2002 00:30:16 +0900
48. Re: Suggestion for a new and enhanced "server mode"
Alan Brown <alanb at digistar dot com>
Mon, 15 Apr 2002 05:13:37 -0400 (EDT)
49. openSSl error
Auxiliar <aux at aitemin dot es>
Mon, 15 Apr 2002 12:17:06 +0200
50. a minor patch for 4.0.4
Ayamura KIKUCHI <ayamura at ayamura dot org>
Mon, 15 Apr 2002 23:45:59 +0900
Date: Tue, 9 Apr 2002 16:42:05 -0400
From: Scott McDermott <mcdermot at questra dot com>
Subject: Re: Please Test Qpopper 4.0.4fc3
To qpopper at lists.pensive dot org on Tue 9/04 16:14 -0400:
> like I said, no config or cert changes, same openssl library, worked
> fine before upgrade. Platform Linux 2.2, glibc 2.1.
btw here is a log entry with 4.0.3 which also shows errors, but actually
works, the client can receive without problems. Looks almost the same
but without the signals, strange that it works.
: (v4.0.3) POP login by user "mfiegl" at (userjoe.ddns.our.domain.com) 10.20.10.248 [pop_log.c:244]
: I/O Error [pop_tls_openssl.c:730]
: Error writing to client [pop_send.c:724]
: I/O Error [pop_tls_openssl.c:730]
: Error writing to client [pop_send.c:724]
: Stats: mfiegl 1 770 0 0 userjoe.ddns.our.domain.com 10.20.10.248 [pop_updt.c:296]
: TLS shutdown Error [pop_tls_openssl.c:789]
: (v4.0.3) Timing for mfiegl at userjoe.ddns.our.domain dot com (normal) auth=0 init=0 clean=0 [popper.c:375]
Date: Tue, 9 Apr 2002 17:06:33 -0400
From: Scott McDermott <mcdermot at questra dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Christopher Crowley on Tue 9/04 14:49 -0500:
> The locking mechanisms are not the same, and thereby there is no
> coordinated locking system between qpopper and uw-imap.
If you use uw-imap with the mlock program from the UW imap-utils,
building the IMAP server with LOCKPGM defined to it, it uses a hitchpost
dotlock in the mail spool, just make it setgid mail along with mail
writable spool dir. I think that should work, no? It appears that
qpopper does use dotlocks in Qmaillock() at common/maillock.c:205.
Better idea is to write an mlock replacement that uses flock() or fcntl
with F_SETLK, but dotlock should work as long as only qpopper and
uw-imap access your spool. Otherwise you definitely will see
corruption if they don't cooperate and are run concurrently.
also if you run server mode, all bets are off since the lock only occurs
once at the beginning and then at the end of the dropcopy, so you have
to turn that off. I still think the lock should surround the session
and let MDA handle temporary errors, but maybe that is bad policy, I
don't know.
Date: Tue, 9 Apr 2002 12:10:50 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Please Test Qpopper 4.0.4fc3
At 9:01 PM +0200 4/9/02, Michael Zimmermann wrote:
>At Dienstag, 9. April 2002 20:12 Oliver Fleischmann wrote:
>> [about hanging popper processes laying around]
>> Strace shows the processes waiting in a "read(0, " call; I have never
>> been able to get more information out of it.
>
>Am I wrong, Randall, that this smells of the old hang-up situation
>which Clifton tried to solve with his signal-patch?
Sounds plausible.
>Wouldn't it be worth, Olivier, to try a 4.0.4fc3 plus Clifton's
>patches (or similiar) on your site?
That would be a good idea.
Date: Tue, 09 Apr 2002 16:18:02 -0400
From: Daniel Senie <dts at senie dot com>
Subject: RE: Qpopper 4.0.4fc3 Need Help
At 02:48 PM 4/9/02, Matthew D. Hon wrote:
>With RedHat 7.2 I cannot find a inetd.conf file. Do I just put the same line
>in the xinetd.conf file as I would in the other?
You need a new xinetd config file. We (developers group for qpopper) need
to start putting an xinetd config file somewhere in the distribution.
[Randy: I'll send you a sample one]
>-----Original Message-----
>From: Pastor Stuart Thiessen [mailto:sthiessen at firstfederated dot org]
>Sent: Tuesday, April 09, 2002 12:38 PM
>To: Matthew D. Hon
>Subject: Re: Qpopper 4.0.4fc3 Need Help
>
>
>I had the same problem. It is a firewall issue. By default, RedHat blocks
>port 110 where POP comes in. Do you know how to use ipchains to configure
>the firewall? If not, I can send you the commands that worked for me.
>
>Thanks,
>
>Stuart
>
>----- Original Message -----
>From: "Matthew D. Hon" <matthewhon at iname dot com>
>To: "Subscribers of Qpopper" <qpopper at lists.pensive dot org>
>Sent: Tuesday, 09 April 2002 11:52
>Subject: Qpopper 4.0.4fc3 Need Help
>
>
> > I have downloaded and run the ./configure script. I have followed the
> > directions on the web site to the best of my abilities and I still cannot
> > get qpopper to work. I am running Redhat 7.2. When I try to do a telnet to
> > check if things are working I get the connection refused error message.
>Any
> > ideas or tell me where to start?
> >
> > Matthew
> >
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Date: Tue, 9 Apr 2002 17:17:47 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: Please Test Qpopper 4.0.4fc3
On Tue, 9 Apr 2002, Randall Gellens wrote:
> I couldn't reproduce it. Do I need to use a certain client?
My own experience with hanging sessions tended to point towards Eudora
1.* and 2.* clients being the most likely trigger.
HTH HAND
Date: Tue, 9 Apr 2002 14:01:15 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <781148769498124573227 at lists.pensive dot org>; from mcdermot at questra dot com on Tue, Apr 09, 2002 at 05:06:33PM -0400
On Tue, Apr 09, 2002 at 05:06:33PM -0400, Scott McDermott wrote:
> Christopher Crowley on Tue 9/04 14:49 -0500:
> > The locking mechanisms are not the same, and thereby there is no
> > coordinated locking system between qpopper and uw-imap.
>
> If you use uw-imap with the mlock program from the UW imap-utils,
> building the IMAP server with LOCKPGM defined to it, it uses a hitchpost
> dotlock in the mail spool, just make it setgid mail along with mail
> writable spool dir. I think that should work, no? It appears that
> qpopper does use dotlocks in Qmaillock() at common/maillock.c:205.
This part actually works, yes. Both lock against mail delivery
successfully at this point. It's only the server mode that's a
problem, where qpopper assumes nothing happened to the spool between
start of session and end of session except appending to it.
> also if you run server mode, all bets are off since the lock only occurs
> once at the beginning and then at the end of the dropcopy, so you have
> to turn that off.
This is the part everyone's concerned about.
> I still think the lock should surround the session
> and let MDA handle temporary errors, but maybe that is bad policy, I
> don't know.
One problem with that solution is that lock is by convention considered
dead and removable by the MDA after 6 minutes, and a POP session can go
longer.
-- 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, 9 Apr 2002 15:11:39 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Please Test Qpopper 4.0.4fc3
At 4:14 PM -0400 4/9/02, Scott McDermott wrote:
>Any ideas? Any more info needed?
It looks like a timeout. Hard to see how the fc3 changes could cause
that, but you never know.
Can you try it with debug tracing?
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: Tue, 9 Apr 2002 21:51:28 +0200 (MEST)
From: Oliver Fleischmann <ogf at bnv-bamberg dot de>
Subject: Re: Please Test Qpopper 4.0.4fc3
On Tue, 9 Apr 2002, Randall Gellens wrote:
> At 9:01 PM +0200 4/9/02, Michael Zimmermann wrote:
>
> >At Dienstag, 9. April 2002 20:12 Oliver Fleischmann wrote:
> >> [about hanging popper processes laying around]
> >> Strace shows the processes waiting in a "read(0, " call; I have never
> >> been able to get more information out of it.
> >
> >Am I wrong, Randall, that this smells of the old hang-up situation
> >which Clifton tried to solve with his signal-patch?
>
> Sounds plausible.
>
> >Wouldn't it be worth, Olivier, to try a 4.0.4fc3 plus Clifton's
> >patches (or similiar) on your site?
>
> That would be a good idea.
OK, I have applied the patches to 4.0.4fc3, I hope It works... I will tell
you about the results!
Oliver
Date: Tue, 9 Apr 2002 23:17:38 -0400
From: Scott McDermott <mcdermot at questra dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
<20020409140114.A22047 at lava dot net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3us
In-Reply-To: <20020409140114.A22047 at lava dot net>
Clifton Royston on Tue 9/04 14:01 -1000:
> > [uw-imap with LOCKPGM set to mlock from imap-utils allows qpopper
> > and uw-imap to co-exist]
>
> This part actually works, yes.
>
> > [but not in server mode]
>
> This is the part everyone's concerned about.
>
> > I still think the lock should surround the session and let MDA
> > handle temporary errors, but maybe that is bad policy, I don't know.
>
> One problem with that solution is that lock is by convention
> considered dead and removable by the MDA after 6 minutes, and a POP
> session can go longer.
I don't know what you mean by `convention.' I recall a discussion where
somebody said their copy of sendmail did this after a configurable
default of 6 minutes. We are using procmail for delivery, which waits
for a configurable default of 17 minutes, then clears the lock like
sendmail. And looks like qmail with its own DA timeouts in 30 seconds
but the message gets re-queued instead of forcing the lock off (which,
IMO is the right thing to do, something has not cleaned up after itself
and the bug should be found, not ignored by destroying the lock)
- If your MDA timeout is configured too short and POP sessions overrun
it commonly, block longer on delivery (or better yet forever), dont
use server mode, or disable full pop session lock. I realize that a
user could be getting a gig through email over a modem and holding up
all his deliveries, but this user has other problems and we should not
worry about him, besides we have quotas to enforce upper bounds and
prevent timeouts from getting too crazy, and idle timeouts on the
server to prevent this from being a problem for hungup clients.
- If your MTA does not properly handle MDA errors, get a new one.
- If something is ignoring both dotlocks and file locks and just
overwriting files, you have a misbehaving program somewhere, fix it,
or get a new one.
- In all cases timeouts are configurable. So why wouldn't it follow
that a full session lock be optional to people that know what they are
doing.
I am interested in how you solved this problem with the blackbox devices
you were looking into for in an earlier thread.
I also wonder how ipop3d handles it, I suspect it just isn't optimized
for this case like qpopper in server mode and thus doesn't run into this
problem.
Date: Tue, 9 Apr 2002 17:04:24 -0400
From: Joseph S D Yao <jsdy at center.osis dot gov>
Subject: Re: Qpopper 4.0.4fc3 Need Help
On Tue, Apr 09, 2002 at 01:48:26PM -0500, Matthew D. Hon wrote:
> With RedHat 7.2 I cannot find a inetd.conf file. Do I just put the same line
> in the xinetd.conf file as I would in the other?
Different versions of 'inetd' work differently, especially 'xinetd'.
First, try modifying the files in /etc/xinetd.d.
--
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: Fri, 12 Apr 2002 09:31:10 +0800 (HKT)
From: PM WONG <pmwong at power25t.hkbu.edu dot hk>
Subject: When to use qpopper?
Since most Unix servers come with a pop server of their own
OS, i wonder when do we consider switching to use qpopper
instead.
Date: Thu, 11 Apr 2002 20:07:51 +0200
From: Jesus Cea Avion <jcea at argo dot es>
Subject: Re: Suggestion for a new and enhanced "server mode"
> And you never hereafter receive mail?
The mbox -> database could be done both:
- From a cron job
- Every time the user enters a POP3 session.
> You need to at least have some interface for MTAs to deliver mail into
> the database other than by someone popping their mail!
That's other option, but the problem is to do a MDA for every MTA
available, IMAP, and so on.
With my approach you only need a mbox -> database transfer process that
understand "mbox" and "MAILDIR" formats, for example.
> I think you're really no longer talking about redesigning Qpopper
> when you add this scope, you are talking about implementing most of a
> complete new mail system, and you need to make it coexist with at
> least the most common dozen or so other packages that form other parts
> of the mail system.
The implementing cost should be low, and current QPOPPER performance
problems would banish.
> see <http://www.dbmail.org/>
I'll check it out.
> If you're keeping initial messages delivered from [your MTA] in mbox
> format, this probably means you're doing this mbox scan on many
> sessions, which means you're doing a large part of the I/O currently
> needed.
When you copy "mbox" messages to the database, you delete the mbox.
> This is the key advantage, but really this part boils down to having
> a better message info cache system, which can be implemented without
> completely reimplementing Qpopper into a database.
Yeah. A possibility would be to keep certains headers (like "status" and
"UIDL") in the cache file, INSTEAD the BIG mbox file. When you send a
message to user, you insert the "cached" headers.
So, you don't need to rewrite a entire mbox spool to rewrite a "Status:
U" to "Status: RO".
A paliative solution to current qpopper performance problems.
> > - You can delete individual messages without needing a mailbox
> > rewriting.
>
> You still have to rewrite the database... but you do save on
> avoiding repeated handling of the old saved messages. (Maildir also
> wins on this.)
When you delete a message in the database, the write traffic is almost
null. You mark blocks as "free" and almost nothing more. Nowhere near an
entire spool rewrite.
> Qpopper shouldn't be modifying the headers, other than to add a UID
> (which can be avoided!)
Qpopper rewrites "STATUS" header.
Those modified headers should be kept in the cache file, not in the
spool.
> They require loading into the database at the next POP session,
> though.
Yeah. You aparentily triplicate disk activity: the email arrives and
appends to mbox. The user POPs and POP daemon read the message and
inserts it into the DB.
But this cost is per message, and nothing comparing to an user with a 50
Mbytes spool file and "check email every minute" checked on :-).
> That doesn't actually reduce I/O, just splits it up. Qpopper
> doesn't read the whole 15MB in one chunk either.
I know. I'm talking about memory issues, since many databases retrieve
the entire register, eating tons of memory. Berkeley DB has not that
problem.
> Perhaps another way of putting it is: if all these changes were made
> to Qpopper as you describe, would it still be Qpopper at the end and
> usable as it is now, or would it be a totally different beast?
Qpopper changes should be small; you change disk read/writes to database
read/writes. Fairly drop-in.
The mbox/maildir -> database translator should be least of 100 C
language lines.
The support utilities can be keep separated and the should be fairly
simple also.
> For Qpopper to be able to work as it does now, for systems using
> just mbox format, but also be able to work as you describe, then its
> present mailbox I/O would need to be abstracted to a separate mailbox
> interface I/O layer
This should be way. Right!.
> All IMHO. As your sig says "Things are not so easy."
Life is hard and we keep doing things in the hard way :-)
--
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea at argo.es http://www.argo dot es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/
_/_/ _/_/ _/_/_/_/_/
PGP Key Available at KeyServ _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
Date: Wed, 10 Apr 2002 15:23:13 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new
At 2:01 PM -1000 4/9/02, Clifton Royston wrote:
> > I still think the lock should surround the session
>> and let MDA handle temporary errors, but maybe that is bad policy, I
>> don't know.
>
>One problem with that solution is that lock is by convention considered
>dead and removable by the MDA after 6 minutes, and a POP session can go
>longer.
You can add calls on Qtouchlok() to refresh the dot lock periodically
during the session, as is done currently in pop_dropcopy.c and
pop_update.c
Date: Wed, 10 Apr 2002 00:00:09 +0200
From: hypnose at t-online dot de (guenter wessling)
Subject: Re: Please Test Qpopper 4.0.4fc3
No problems here.
Two servers; one Linux and one FreeBSD4.
Both on Pentium III.
Traffic not too high, though. At most 400 connections/day.
Special: Outlook not allowed due to APOP reasons.
guenter
guenter wessling (hypnose at t-online dot de)
Date: Fri, 12 Apr 2002 06:51:23 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: When to use qpopper?
On Fri, 12 Apr 2002, 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.
In any instance where the supplied version is Berkeley popper or an old
version of Qpopper.
...Unless you like having your system rootkitted.
AB
From: Oliver Egginger <Oliver.Egginger at dvz.fh-giessen dot de>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
Date: Thu, 11 Apr 2002 11:52:39 +0200
Summary:
Also I have to use dotlocking for qpopper and the UW imapd.
And qpopper should not run in server mode.
Thank you for your comments.
regards
oliver
> <20020409140114.A22047 at lava dot net>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 1.0pre3us
> In-Reply-To: <20020409140114.A22047 at lava dot net>
>
> Clifton Royston on Tue 9/04 14:01 -1000:
> > > [uw-imap with LOCKPGM set to mlock from imap-utils allows qpopper
> > > and uw-imap to co-exist]
> >
> > This part actually works, yes.
> >
> > > [but not in server mode]
> >
> > This is the part everyone's concerned about.
> >
> > > I still think the lock should surround the session and let MDA
> > > handle temporary errors, but maybe that is bad policy, I don't know.
> >
> > One problem with that solution is that lock is by convention
> > considered dead and removable by the MDA after 6 minutes, and a POP
> > session can go longer.
>
> I don't know what you mean by `convention.' I recall a discussion where
> somebody said their copy of sendmail did this after a configurable
> default of 6 minutes. We are using procmail for delivery, which waits
> for a configurable default of 17 minutes, then clears the lock like
> sendmail. And looks like qmail with its own DA timeouts in 30 seconds
> but the message gets re-queued instead of forcing the lock off (which,
> IMO is the right thing to do, something has not cleaned up after itself
> and the bug should be found, not ignored by destroying the lock)
>
> - If your MDA timeout is configured too short and POP sessions overrun
> it commonly, block longer on delivery (or better yet forever), dont
> use server mode, or disable full pop session lock. I realize that a
> user could be getting a gig through email over a modem and holding up
> all his deliveries, but this user has other problems and we should not
> worry about him, besides we have quotas to enforce upper bounds and
> prevent timeouts from getting too crazy, and idle timeouts on the
> server to prevent this from being a problem for hungup clients.
>
> - If your MTA does not properly handle MDA errors, get a new one.
>
> - If something is ignoring both dotlocks and file locks and just
> overwriting files, you have a misbehaving program somewhere, fix it,
> or get a new one.
>
> - In all cases timeouts are configurable. So why wouldn't it follow
> that a full session lock be optional to people that know what they are
> doing.
>
> I am interested in how you solved this problem with the blackbox devices
> you were looking into for in an earlier thread.
>
> I also wonder how ipop3d handles it, I suspect it just isn't optimized
> for this case like qpopper in server mode and thus doesn't run into this
> problem.
--
Oliver Egginger
FH Giessen-Friedberg
DV-Zentrum
Wiesenstrasse 14
35390 Giessen
Tel. +49 641 309-1283
Fax +49 641 309-2908
Mail: Oliver.Egginger at dvz.fh-giessen dot de
*************************************************************************
Die aktuellen Sprechzeiten des DV-Zentrums für
E-Mail-Angelegenheiten finden Sie unter:
http://www.fh-giessen.de/WEB_NADM/dvz/personen.shtml
*************************************************************************
Date: Wed, 10 Apr 2002 21:43:43 -0400
From: Scott McDermott <mcdermot at questra dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
<324025258399407099417 at lists.pensive.org> <a05101500b8da6b71d11d at [129 dot 46 dot 156 dot 156]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <a05101500b8da6b71d11d at [129.46.156 dot 156]>; from randy at qualcomm dot com on Wed, Apr 10, 2002 at 03:23:13PM -0700
Randall Gellens on Wed 10/04 15:23 -0700:
> > > I still think the lock should surround the session and let MDA
> > > handle temporary errors, but maybe that is bad policy, I don't
> > > know.
> >
> > One problem with that solution is that lock is by convention
> > considered dead and removable by the MDA after 6 minutes, and a POP
> > session can go longer.
>
> You can add calls on Qtouchlok() to refresh the dot lock periodically
> during the session, as is done currently in pop_dropcopy.c and
> pop_update.c
Qtouchlock eh? Ok which operations can cause time to elapse:
- POP_TIMEOUT already is 120 seconds
- pop_timeout is controlled by the admin
- update already uses Qtouchlock in its unbounded loop
- dropcopy already uses Qtouchlock in its unbounded loop
- user could do nops to reset idle counter, how about touching
the lock in tgetline() to solve this? no, no...
- pop_send() is potentially unbounded, maybe touch in
pop_write()?
- other commands
ok nevermind that, how about setting an alarm every time we execute a
command which can run in unbounded time, and we're running under a
full-session-lock. When the alarm is raised the handler refreshes the
lock and resets the alarm, then returns to continue doing work. We
already have the lock path in szLock[] global so it will be available
from the handler. The alarm will be conditional on full-session-lock
option and everything will work unchanged without it. When we exit a
command we restore the alarm be used just as tgetline() already does.
Does that sound reasonable? I'm sure I'm missing something.
Date: Wed, 10 Apr 2002 23:25:43 -0400
From: Scott McDermott <mcdermot at questra dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
<324288528446165629879 at lists.pensive.org> <a05101501b8da6c4e0534 at [129 dot 46 dot 156 dot 156]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3us
In-Reply-To: <a05101501b8da6c4e0534 at [129.46.156 dot 156]>
Randall Gellens on Wed 10/04 15:27 -0700:
> >I don't know what you mean by `convention.'
>
> From the man page for maillock(3MAIL) on Solaris:
>
> If a lockfile already exists, and it has not been modified in the
> last 5 minutes, maillock() will remove the lockfile and set its
> own lockfile.
hmm interesting why does it recommend to refresh "at least every 3
minutes" in the next paragraph, why not 4 for instance?
It seems that we can't guarantee anything about 3 minutes without
interrupting it that often to refresh it. Right now it is done with
Qtouchfile() every check_lock_refresh messages if LOCK_REFRESH_INTERVAL
has elapsed, but this could easily exceed 3 minutes already.
Date: Fri, 12 Apr 2002 07:51:41 -0400
From: Mark Wendt <wendt at kingcrab.nrl.navy dot mil>
Subject: TLS/SSL question
Hi,
Any chance we might see in a future release an option to set port 110 as a
TLS/SSL only? Currently that option is only available for the alternate
port, 995. We have a requirement to use encrypted communications only, and
we're currently forcing the clients to use the alternate port. Be nice if
we could set port 110 with that option, and shut down clear text on that port.
Mark Wendt
System/Network Administrator
Naval Research Laboratory
Washington, DC
Date: Wed, 10 Apr 2002 08:06:29 -0400
From: Jeff Donovan <jdonovan at beth.k12.pa dot us>
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
Subject: Re: When to use qpopper?
From: Michal Jeczalik <listy at samotnia.eu dot org>
Date: 12 Apr 2002 14:47:44 +0200
PM WONG <pmwong at power25t.hkbu.edu dot hk> writes:
> Since most Unix servers come with a pop server of their own
> OS, i wonder when do we consider switching to use qpopper
> instead.
Because it's much better. :P
--
Samotnik
Michal Jeczalik Sr, http://www.samotnia.eu.org/
From: "Matthew D. Hon" <matthewhon at iname dot com>
Subject: qpopper110.cfg Need Help
Date: Thu, 11 Apr 2002 12:58:50 -0500
Hello Thanks for everyone's help. Now when I telnet into the server at port
110 I get the error message "Unable to process config file
/etc/qpopper110.cfg" Did I miss doing something during the install? I am
able to get in now though so that is an improvement.
Matthew
Date: Fri, 12 Apr 2002 16:54:42 +0200
From: Thomas Eisenbarth <eisenbarth at planet-design-don dot de>
Subject: Re: When to use qpopper?
hello,
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.
greets, Thomas
From: "Christopher Crowley" <ccrowley at tulane dot edu>
Subject: Re: Please Test Qpopper 4.0.4fc3
Date: Wed, 10 Apr 2002 14:12:01 -0500
FYI -
It compiles and runs on Solaris 8. However, it has not experienced any
substantial load.
Chris
Date: Wed, 10 Apr 2002 18:55:20 +0900
From: Ayamura KIKUCHI <ayamura at ayamura dot org>
Subject: Re: Please Test Qpopper 4.0.4fc3
> I'd like to release 4.0.4 as soon as possible, so I'm asking for your
> help. Please try out 4.0.4fc3 and let me know of any problems.
I'm trying to compile Qpopper 4.0.4fc3 on IRIX 6.5.15f plathomes
with MIPSpro Compilers 7.3.1.3m, but compilation errors are
detected.
cc -c -I.. -I. -I../mmangle -I../common -I/usr/local/include \
-I/usr/local/ssl/include -O2 -OPT:Olimit=0 -w \
-DHAVE_CONFIG_H -DIRIX -DUNIX pop_auth.c -o pop_auth.o
cc-1515 cc: ERROR File = pop_auth.c, Line = 354
A value of type "struct passwd" cannot be assigned to an entity of type
"struct passwd *".
pw = p->pw;
^
1 error detected in the compilation of "pop_auth.c".
gmake: *** [pop_auth.o] Error 2
cc -c -I.. -I. -I../mmangle -I../common -I/usr/local/include \
-I/usr/local/ssl/include -O2 -OPT:Olimit=0 -w \
-DHAVE_CONFIG_H -DIRIX -DUNIX pop_extend.c -o pop_extend.o
cc-1055 cc: ERROR File = pop_extend.c, Line = 72
A macro invocation has too many arguments.
POP_WRITE_LIT ( p, "SASL SCRAM-MD5\r\n", );
^
1 error detected in the compilation of "pop_extend.c".
gmake: *** [pop_extend.o] Error 2
-- ayamura
Date: Fri, 12 Apr 2002 13:31:17 -0400
From: Mark Wendt <wendt at kingcrab.nrl.navy dot mil>
Subject: Re: TLS/SSL question
At 12:45 PM 4/12/2002 -0400, you wrote:
>At 07:51 AM 4/12/02, Mark Wendt wrote:
>>Hi,
>>
>> Any chance we might see in a future release an option to set
>> port 110 as a TLS/SSL only?
>
>Current release can do this.
Not according to the manual. "-l 1 - Enables support for the STLS
command. This permits TLS/SSL negotiations on the standard (or any) port,
allowing the same port to be used by TLS/SSL "and" regular clients". There
is no way to set the port as TLS/SSL from my take on the manual.
>> Currently that option is only available for the alternate port, 995.
>
>Not true.
>
>You're confusing "alternate-port" which is a mode of operation, with the
>port it's most commonly run atop. They are separately configured items.
>You can do what you want today by configuring qpopper correctly.
Nope, I understand what alternate-port does. Currently I'm
running alternate-port on 995using the config file, and it only accepts
encrypted connections, and have set up port 110 with the "-l 1" qualifier,
which gives clear and encrypted communications
>> We have a requirement to use encrypted communications only, and we're
>> currently forcing the clients to use the alternate port. Be nice if we
>> could set port 110 with that option, and shut down clear text on that port.
>
>I think you can today specify TLS is required even if STARTTLS is used.
>That'd certainly be the preferred solution to what you're trying to do.
That's at the client end of Eudora. We also have Outlook users,
and Netscape users, but that's not what I'm getting at. The only way I can
keep port 110 open at the firewall, is to ensure that only encrypted
communications happen at that port, which with the way the current version
is set up, that's not possible
>>Mark Wendt
>>System/Network Administrator
>>Naval Research Laboratory
>>Washington, DC
>
>-----------------------------------------------------------------
>Daniel Senie dts at senie dot com
>Amaranth Networks Inc. http://www.amaranth.com
Mark Wendt
System/Network Administrator
Naval Research Laboratory
Washington, DC
Date: Fri, 12 Apr 2002 10:55:23 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new and enhanced "server mode"
On Thu, Apr 11, 2002 at 11:52:39AM +0200, Oliver Egginger wrote:
> Summary:
> Also I have to use dotlocking for qpopper and the UW imapd.
> And qpopper should not run in server mode.
> Thank you for your comments.
Correct. At least until one of these many locking schemes people are
discussing is fully implemented, which could be a while.
...
> > I also wonder how ipop3d handles it, I suspect it just isn't optimized
> > for this case like qpopper in server mode and thus doesn't run into this
> > problem.
ipop3d is part of the UW imap package, and therefore uses the same base
code as UW imapd for mailbox access and locking, and so is compatible
with its locking conventions. However, it seems to be pretty much an
afterthought. Probably because Mark Crispin just doesn't think much of
POP3 as a protocol as compared to IMAP, for understandable reasons.
-- 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: Fri, 12 Apr 2002 11:42:52 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: TLS/SSL question
On Fri, Apr 12, 2002 at 07:51:41AM -0400, Mark Wendt wrote:
> Any chance we might see in a future release an option to set
> port 110 as a TLS/SSL only? Currently that option is only available
> for the alternate port, 995. We have a requirement to use encrypted
> communications only, and we're currently forcing the clients to use
> the alternate port. Be nice if we could set port 110 with that
> option, and shut down clear text on that port.
You can simply do that with existing options; qpopper can force TLS/SSL
with the "alternate-port" setting on any port number including 110.
-- 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, 10 Apr 2002 15:27:16 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: c-client & Qpopper coexist? WAS: Re: Suggestion for a new
At 11:17 PM -0400 4/9/02, Scott McDermott wrote:
> > One problem with that solution is that lock is by convention
>> considered dead and removable by the MDA after 6 minutes, and a POP
>> session can go longer.
>
>I don't know what you mean by `convention.'
From the man page for maillock(3MAIL) on Solaris:
If a lockfile already exists, and it has not been modified in the
last 5 minutes, maillock() will remove the lockfile and set its own
lockfile.
Date: Fri, 12 Apr 2002 12:12:05 -0400
From: Joseph S D Yao <jsdy at center.osis dot gov>
Subject: Re: Suggestion for a new and enhanced "server mode"
On Thu, Apr 11, 2002 at 08:07:51PM +0200, Jesus Cea Avion wrote:
> Yeah. A possibility would be to keep certains headers (like "status" and
> "UIDL") in the cache file, INSTEAD the BIG mbox file. When you send a
> message to user, you insert the "cached" headers.
>
> So, you don't need to rewrite a entire mbox spool to rewrite a "Status:
> U" to "Status: RO".
>
> A paliative solution to current qpopper performance problems.
Which totally breaks down if any other mail system touches just the
mbox and not the header files.
--
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.
From: "Matthew D. Hon" <matthewhon at iname dot com>
Subject: Qpopper Error - Please Help
Date: Fri, 12 Apr 2002 11:26:18 -0500
Hello Thanks for everyone's help. Now when I telnet into the server at port
110 I get the error message "Unable to process config file
/etc/qpopper110.cfg" Did I miss doing something during the install? I am
able to get in now though so that is an improvement.
Matthew
Date: Fri, 12 Apr 2002 17:03:38 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.4 (final) available
Qpopper 4.0.4 (final) is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
The full list of changes from one release to the next is on the FTP
site, at <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/Changes>.
Changes from 4.0.3 to 4.0.4:
----------------------------
1. Fixed DOS attack seen on some systems.
2. Fixed standalone mode on OpenBSD.
3. Fixed "noop has null function" log entry.
4. Fixed 'make install' error on systems w/o group 'root'.
5. Allow '-p' to be used when APOP not defined (noted by Daniel Senie).
6. Enforce ClearTextPassword even without APOP (noted by Daniel Senie).
7. Restrict clear-text-password=never to APOP.
8. Restrict clear-text-password=tls to QPOP_SSL.
9. Fixed qpopper hanging on I/O error on some platforms.
(No changes from 4.0.4fc3 other than the version number no longer has "fc3")
Date: Fri, 12 Apr 2002 17:06:21 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: version check w/ bsdi4.2
At 8:06 AM -0400 4/10/02, Jeff Donovan wrote:
>how do I check which version of qpopper I am running?
Try running it with a '-v' flag. It should show the version and if
it's compiled for standalone or inetd. If it doesn't do this, then
it's an old version.
(For old versions, you can try strings(1) or telnet to it and see
what the banner says. If the banner doesn't say, login and send
'capa'.)
Date: Fri, 12 Apr 2002 17:12:30 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: TLS/SSL question
At 7:51 AM -0400 4/12/02, Mark Wendt wrote:
>Any chance we might see in a future release an option to set port
>110 as a TLS/SSL only? Currently that option is only available for
>the alternate port, 995. We have a requirement to use encrypted
>communications only, and we're currently forcing the clients to use
>the alternate port. Be nice if we could set port 110 with that
>option, and shut down clear text on that port.
Actually, Qpopper doesn't care what port it runs on. The choice of
how to support TLS (STLS or alternate-port) is independent of the
port number. Some people get confused by this, and try to run on
port 995 simply by setting TLS support to alternate-port, without
also having Qpopper listen on port 995.
Probably the easiest way to ensure encrypted communications only is
to set the clear-text-password option to tls. If you don't add APOP
support, that forces everyone to use TLS. You can do this
independently of which port or how TLS is supported. So you can have
Qpopper available on 110 and 995, offering STLS on 110 and
alternate-port-tls on 995.
Date: Fri, 12 Apr 2002 11:03:20 -0700
From: "Chris" <yahoogroups at xymox1 dot com>
Subject: RE: When to use qpopper?
Ummm, when you want TLS/SSL and of course you want speed...
-----Original Message-----
From: PM WONG [mailto:pmwong at power25t.hkbu.edu dot hk]
Sent: Thursday, April 11, 2002 6:31 PM
To: Subscribers of Qpopper
Subject: When to use qpopper?
Since most Unix servers come with a pop server of their own
OS, i wonder when do we consider switching to use qpopper instead.
Date: Fri, 12 Apr 2002 17:04:11 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: TLS/SSL question
On Fri, Apr 12, 2002 at 01:31:17PM -0400, Mark Wendt wrote:
> Nope, I understand what alternate-port does. Currently I'm
> running alternate-port on 995using the config file, and it only accepts
> encrypted connections ...
Isn't that exactly what you say you want on port 110?
> >> We have a requirement to use encrypted communications only, and we're
> >> currently forcing the clients to use the alternate port. Be nice if we
> >> could set port 110 with that option, and shut down clear text on that port.
> >
> >I think you can today specify TLS is required even if STARTTLS is used.
> >That'd certainly be the preferred solution to what you're trying to do.
Set "alternate-port" on the instance you're running on port 110, with
the same syntax you're using on 995. Just use the same options file
and/or the same command line parameters.
If this doesn't work, either I don't understand what you want to do or
I will be *very* surprised. AFAIK there is no "magic" which does
things specially based on what port Eudora is running on.
-- 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
From: kkim at telcordia dot com
Subject: Please Help - Regarding alias name
Date: Fri, 12 Apr 2002 15:11:48 -0400
Hello,
I am trying to figure out how to change the alias name that
is appeared on 'From' so for example, If I receive email from
qpopper, from field says Subscripber for qpopper<qpopper at lists.pensive dot org>
I am trying to change the 'Subscriber for qpopper' portion to whatever I
want and not
tied to /etc/passwd file.....is this possible ?
Thanks for the help,
-K..Kim-
Subject: Correct Syntax for home-dir-mail
Date: Fri, 12 Apr 2002 10:32:20 -0400
From: "Lyle Schofield" <Lyle.Schofield at daou dot com>
This is a multi-part message in MIME format.
------_=_NextPart_001_01C1E22E.DA8FC1A0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi:
I'm trying to get qpopper running on a SuSE Linux 7.3 box that uses
sendmail, configured to dump mail into the users directory "Mail"
($HOME/Mail). I'm using a configuration file with the -f parameter in
inetd which has the line:
set home-dir-mail = Mail
The debug log shows:
Apr 12 21:58:45 mail popper[5756]: Set debug to true [pop_config.c:1167]
Apr 12 21:58:45 mail popper[5756]: ...read line 7 (24): set
home-dir-mail = Mail [pop_config.c:1315]
Apr 12 21:58:45 mail popper[5756]: Set home-dir-mail to "Mail"
[pop_config.c:1211]
Apr 12 21:58:45 mail popper[5756]: Finished processing config file
'/etc/mail/qpopper.conf'; rslt=1 [pop_config.c:1463]
which looks like proper execution. During a POP session when trying to
access messages with account "lyle", the following shows up:
Apr 12 21:58:54 mail popper[5756]: Getting mail lock
[pop_dropcopy.c:1625]
Apr 12 21:58:54 mail popper[5756]: successfully opened (exclusive) lock
/home/lyle/Mail.lock [maillock.c:477]
Apr 12 21:58:54 mail popper[5756]: maillock() on file /home/lyle/Mail
(/home/lyle/Mail.lock) [pop_dropcopy.c:1631] returning 0 (1 attempt(s))
[maillock.c:549]
Apr 12 21:58:54 mail popper[5756]: Unable to open maildrop
/home/lyle/Mail: Is a directory (21) [pop_dropcopy.c:1741]
Apr 12 21:58:54 mail popper[5756]: ...built: (39) '/var/mail/'
[genpath.c:158]
Is the proper value for "home-dir-mail" supposed to be the mail
directory, or maybe just the path to the inbox (value should be
"Mail/inbox")? Or, is this a security setting issue?
Any help appreciated.
-Lyle
Lyle Schofield
Sentient
A Division of DAOU Systems, Inc. <http://www.daou.com/>
Kensington, Maryland USA
v:301.929.7624 f:301.929.7680 e:lyle.schofield at daou dot com
------_=_NextPart_001_01C1E22E.DA8FC1A0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html;
charset=us-ascii">
<META content="MSHTML 5.50.4913.1100" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana
size=2>Hi:</FONT></SPAN></DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana size=2>I'm
trying to get
qpopper running on a SuSE Linux 7.3 box that uses sendmail, configured
to dump
mail into the users directory "Mail" ($HOME/Mail). I'm using a
configuration file with the -f parameter in inetd which has the
line:</FONT></SPAN></DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana size=2>set
home-dir-mail
= Mail</FONT></SPAN></DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana size=2>The
debug log
shows:</FONT></SPAN></DIV>
<DIV><SPAN class=318362114-12042002><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=318362114-12042002> </DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><?xml:namespace prefix = st1 ns =
"urn:schemas-microsoft-com:office:smarttags" /><st1:time Hour="21"
Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:45</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: Set debug to true
[pop_config.c:1167]</SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:45</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: ...read line 7 (24): set home-dir-mail = Mail
[pop_config.c:1315]<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office"
/><o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:45</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: Set home-dir-mail to "Mail"
[pop_config.c:1211]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:45</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: Finished processing config file
'/etc/mail/qpopper.conf';
rslt=1 [pop_config.c:1463]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT></SPAN> </DIV>
<DIV><FONT face=Verdana size=2>which looks like proper
execution. During a
POP session when trying to access messages with account "lyle", the
following
shows up:</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV> </DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:54</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: Getting mail lock
[pop_dropcopy.c:1625]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:54</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: successfully opened (exclusive) lock
/home/lyle/Mail.lock
[maillock.c:477]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:54</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: maillock() on file /home/lyle/Mail
(/home/lyle/Mail.lock)
[pop_dropcopy.c:1631] returning 0 (1 attempt(s))
[maillock.c:549]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; COLOR: blue; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; COLOR: blue; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:54</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; COLOR: blue; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: Unable to open maildrop /home/lyle/Mail: Is a
directory (21)
[pop_dropcopy.c:1741]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV class=MsoPlainText style="MARGIN-LEFT: 0.5in; TEXT-INDENT:
-0.5in"><FONT
face=Verdana><FONT size=2><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">Apr
12 </SPAN><st1:time Hour="21" Minute="58"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size:
10.0pt">21:58:54</SPAN></st1:time><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Lucida Console';
mso-fareast-font-family: 'MS Mincho'; mso-bidi-font-size: 10.0pt">
mail popper[5756]: ...built: (39) '/var/mail/'
[genpath.c:158]<o:p></o:p></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV><FONT face=Verdana><FONT size=2>Is the proper value for
"home-dir-mail"
supposed to be the mail directory, or maybe just the path to the inbox
(value
should be "M<SPAN class=318362114-12042002>a</SPAN>il/inbox"<SPAN
class=318362114-12042002>)</SPAN>?<SPAN
class=318362114-12042002> Or, is
this a security setting issue?</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Verdana><FONT size=2><SPAN
class=318362114-12042002></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Verdana><FONT size=2><SPAN
class=318362114-12042002>Any help
appreciated.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Verdana><FONT size=2><SPAN
class=318362114-12042002></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Verdana><FONT size=2><SPAN
class=318362114-12042002>-Lyle</SPAN></FONT></FONT></DIV>
<P class=MsoAutoSig align=left><st1:PersonName
style="BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE:
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"><SPAN
class=GramE><B style="mso-bidi-font-weight: normal"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Lyle
Schofield</SPAN></B></SPAN></st1:PersonName><SPAN class=GramE><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"><BR></SPAN></B><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-SIZE: 11pt; COLOR: maroon; FONT-FAMILY:
Verdana">Sentient<BR></SPAN></B><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">A Division of <A
href="http://www.daou.com/">DAOU Systems,
Inc.</A><BR></SPAN></SPAN><st1:place><st1:City><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language: AR-SA">Kensington</SPAN></st1:City><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language: AR-SA">,
</SPAN><st1:State><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language: AR-SA">Maryland</SPAN></st1:State><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language: AR-SA">
</SPAN><st1:country-region><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language:
AR-SA">USA</SPAN></st1:country-region></st1:place><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana; mso-fareast-font-family:
'Times New Roman'; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-US; mso-fareast-language: EN-US;
mso-bidi-language: AR-SA"><BR>v<SPAN
class=GramE>:301.929.7624</SPAN><SPAN style="mso-spacerun:
yes">
</SPAN>f:301.929.7680<SPAN style="mso-spacerun: yes">
</SPAN>e:<A
href="mailto:lyle.schofield@daou.com">lyle.schofield@daou dot com</A><BR
style="mso-special-character: line-break"><BR
style="mso-special-character: line-break"><o:p></o:p></SPAN></P>
<DIV> </DIV></BODY></HTML>
=00
------_=_NextPart_001_01C1E22E.DA8FC1A0--
Subject: RE: Qpopper 4.0.4fc3 Need Help
From: Kenneth Porter <shiva at well dot com>
Date: 10 Apr 2002 06:38:45 -0700
On Tue, 2002-04-09 at 13:18, Daniel Senie wrote:
> At 02:48 PM 4/9/02, Matthew D. Hon wrote:
> >With RedHat 7.2 I cannot find a inetd.conf file. Do I just put the same line
> >in the xinetd.conf file as I would in the other?
>
> You need a new xinetd config file. We (developers group for qpopper) need
> to start putting an xinetd config file somewhere in the distribution.
> [Randy: I'll send you a sample one]
Here's what I package in my RPM for use as /etc/xinetd.d/pop3:
# qpopper config file for xinetd
service pop3
{
flags = REUSE NAMEINARGS
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/in.qpopper
server_args = in.qpopper -s
# use this line once you create your certificate to enable STLS
# server_args = in.qpopper -s -l 1 -f /etc/mail/qpopper.conf
}
Date: Sat, 13 Apr 2002 09:55:38 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: Qpopper 4.0.4 (final) available
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/>.
>
> The full list of changes from one release to the next is on the FTP
> site, at <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/Changes>.
>
> Changes from 4.0.3 to 4.0.4:
> ----------------------------
> 1. Fixed DOS attack seen on some systems.
> 2. Fixed standalone mode on OpenBSD.
> 3. Fixed "noop has null function" log entry.
> 4. Fixed 'make install' error on systems w/o group 'root'.
> 5. Allow '-p' to be used when APOP not defined (noted by Daniel Senie).
> 6. Enforce ClearTextPassword even without APOP (noted by Daniel Senie).
> 7. Restrict clear-text-password=never to APOP.
> 8. Restrict clear-text-password=tls to QPOP_SSL.
> 9. Fixed qpopper hanging on I/O error on some platforms.
>
> (No changes from 4.0.4fc3 other than the version number no longer has "fc3")
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)
--
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: Thu, 11 Apr 2002 20:11:32 +0200
From: Jesus Cea Avion <jcea at argo dot es>
Subject: Re: Suggestion for a new and enhanced "server mode"
> 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 :-)
--
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea at argo.es http://www.argo dot es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/
_/_/ _/_/ _/_/_/_/_/
PGP Key Available at KeyServ _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
Date: Sat, 13 Apr 2002 12:04:17 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Qpopper 4.0.4 (final) available
At 8:38 AM -0600 4/13/02, The Doctor wrote:
> Does not run well on BSD/OS 4.3
In what way? Does 4.0.3 run OK?
Date: Fri, 12 Apr 2002 17:08:07 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: qpopper110.cfg Need Help
At 12:58 PM -0500 4/11/02, Matthew D. Hon wrote:
>Hello Thanks for everyone's help. Now when I telnet into the server at port
>110 I get the error message "Unable to process config file
>/etc/qpopper110.cfg" Did I miss doing something during the install? I am
>able to get in now though so that is an improvement.
There should be a more detailed error message written somewhere, such
as wherever it's logging. If you're having trouble, try enabling
debug messages.
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: Fri, 12 Apr 2002 12:45:45 -0400
From: Daniel Senie <dts at senie dot com>
Subject: Re: TLS/SSL question
At 07:51 AM 4/12/02, Mark Wendt wrote:
>Hi,
>
> Any chance we might see in a future release an option to set port
> 110 as a TLS/SSL only?
Current release can do this.
> Currently that option is only available for the alternate port, 995.
Not true.
You're confusing "alternate-port" which is a mode of operation, with the
port it's most commonly run atop. They are separately configured items. You
can do what you want today by configuring qpopper correctly.
> We have a requirement to use encrypted communications only, and we're
> currently forcing the clients to use the alternate port. Be nice if we
> could set port 110 with that option, and shut down clear text on that port.
I think you can today specify TLS is required even if STARTTLS is used.
That'd certainly be the preferred solution to what you're trying to do.
>Mark Wendt
>System/Network Administrator
>Naval Research Laboratory
>Washington, DC
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Date: Sat, 13 Apr 2002 08:38:23 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: Qpopper 4.0.4 (final) available
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/>.
>
> The full list of changes from one release to the next is on the FTP
> site, at <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/Changes>.
>
> Changes from 4.0.3 to 4.0.4:
> ----------------------------
> 1. Fixed DOS attack seen on some systems.
> 2. Fixed standalone mode on OpenBSD.
> 3. Fixed "noop has null function" log entry.
> 4. Fixed 'make install' error on systems w/o group 'root'.
> 5. Allow '-p' to be used when APOP not defined (noted by Daniel Senie).
> 6. Enforce ClearTextPassword even without APOP (noted by Daniel Senie).
> 7. Restrict clear-text-password=never to APOP.
> 8. Restrict clear-text-password=tls to QPOP_SSL.
> 9. Fixed qpopper hanging on I/O error on some platforms.
>
> (No changes from 4.0.4fc3 other than the version number no longer has "fc3")
Does not run well on BSD/OS 4.3
--
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: Fri, 12 Apr 2002 10:57:06 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: version check w/ bsdi4.2
On Wed, Apr 10, 2002 at 08:06:29AM -0400, Jeff Donovan wrote:
> Greetings,
> how do I check which version of qpopper I am running?
popper -v
> 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?
Not offhand.
-- 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 00:30:16 +0900
From: Ayamura KIKUCHI <ayamura at ayamura dot org>
Subject: DRAC support for 4.0.4
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
Date: Mon, 15 Apr 2002 05:13:37 -0400 (EDT)
From: Alan Brown <alanb at digistar dot com>
Subject: Re: Suggestion for a new and enhanced "server mode"
On Thu, 11 Apr 2002, Jesus Cea Avion wrote:
> > At this point, I think the scalability of database mail solutions is
> > unproven one way or the other.
There are Oracle-based email solutions. They basically suck, but this
isn't an Oracle problem - it's because the coders writing the "Mail
Transports" involved are less skilled than an infinite bunch of monkeys
with typewriters pounding out Shakespearean sonnets and haven't bothered
reading the applicable RFCs before starting (and this goes for Dan
Bernstein's Qmail too).
Hint: RFC "MUST" = if you don't do this, I'm going to come pound on your ass
Hint2: RFC "SHOULD" = if you don't do this, I'm going to come pound on your ass.
Where "I" = a large bunch of admins who are pissed off with
broken-by-design mail transports (such as qmail) causing DoS attacks on
our systems with massive parallel connects, or causing our systems to
become bogged down with bogus bounces (Qmail, Groupwise, Notes,
Exchange, PostOffice, etc) or causing our systems to back up because
the destination system has suddenly decided it will only accept 2
messages per hour from anyone (Exchange, Notes, Groupwise, etc)
My personal opinion after evaluating database storage of several tens of
millions of variable (but highly similar and short length) message blobs
vs hashed filesystem storage is that databases are _not_ suited for this
kind of activity.
If you're running NT or DOS based systems then this may be different,
but for almost all *nix filesystems it holds true.
Most of Qpopper's problems stem from trying to cope with people leaving
mail on the mail server, simultaneous access from differing IPs or
processes (local vs pop3 access, etc)
The POP3 protocol is unsuitable for this as it doesn't support switching
folders, forcing users to leave everything in the inbox, which then
grows to massive size. This is because POP3 wasn't designed with these
possibilities in mind. It was and is a _simple_ access method, for a
world where access methods are ever-increasingly complex - but only for
about 0.1% of the users.
If users are doing these things or want to do these things, use IMAP.
We'd be switching to it in droves if it was renamed POP4...
I'm _not_ slamming Qpopper. It's very good at what it does, but it's not
a swiss army knife and we really need to resist the urge to turn it into
one.
AB
Date: Mon, 15 Apr 2002 12:17:06 +0200
From: Auxiliar <aux at aitemin dot es>
Subject: openSSl error
Hi everybody, here is my problem:
when running "popper -f /etc/qpopper.config" I get this:
Unable to obtain socket and address of client: Socket operation on
non-socket (88)
If it helps, I have qpopper4.0.3 with Red Hat 7.2 and openssl-0.9.6b-8.
Thanks !!
Date: Mon, 15 Apr 2002 23:45:59 +0900
From: Ayamura KIKUCHI <ayamura at ayamura dot org>
Subject: a minor patch for 4.0.4
--- qpopper4.0.4/popper/pop_auth.c.orig 2001-02-21 10:15:17.000000000 +0900
+++ qpopper4.0.4/popper/pop_auth.c 2002-04-13 22:30:00.000000000 +0900
@@ -351,7 +351,7 @@
/* Blow away everyone who UNIX knows nothing about */
- pw = p->pw;
+ pw = &p->pw;
if ( *p->authid &&
((pw == NULL) || (pw->pw_passwd == NULL)
|| (*pw->pw_passwd == '\0')) )
--- qpopper4.0.4/popper/pop_extend.c.orig 2001-02-21 10:15:18.000000000 +0900
+++ qpopper4.0.4/popper/pop_extend.c 2002-04-13 22:30:00.000000000 +0900
@@ -69,7 +69,7 @@
*/
# if defined(SCRAM)
- POP_WRITE_LIT ( p, "SASL SCRAM-MD5\r\n", );
+ POP_WRITE_LIT ( p, "SASL SCRAM-MD5\r\n" );
# endif
# if !defined(APOP_ONLY) && !defined(SCRAM_ONLY)
-- ayamura
Ayamura KIKUCHI, M.D., Ph.D.
Last updated on 16 Apr 2002 by Pensive Mailing List Admin