The qpopper list archive ending on 24 May 2000
Topics covered in this issue include:
1. APOP and normal authentication
"Rui Paz" <rpaz at uevora dot pt>
Tue, 16 May 2000 23:36:52 +0100
2. Re: APOP and normal authentication
"Julian Y. Koh" <kohster at mac dot com>
Tue, 16 May 2000 17:42:51 -0500
3. Re: APOP and normal authentication
"Rui Paz" <rpaz at uevora dot pt>
Tue, 16 May 2000 23:56:01 +0100
4. maillock error 4 & 5
civ at gbis dot com
Wed, 17 May 2000 02:04:06 -0700
5. Configuring gcc
"Gregory Hall" <Ghall at HAI dot COM>
Wed, 17 May 2000 07:55:19 -0400
6. Re: APOP and normal authentication
Admin Mailing Lists <mlist at intergrafix dot net>
Wed, 17 May 2000 09:06:53 -0400 (EDT)
7. 2.53 was Re: APOP and normal authentication
Peter Evans <peter at gol dot com>
Wed, 17 May 2000 22:24:31 +0900
8. Re: 2.53 was Re: APOP and normal authentication
Alan Brown <alan at manawatu.gen dot nz>
Thu, 18 May 2000 01:41:52 +1200 (NZST)
9. Re: 2.53 was Re: APOP and normal authentication
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Wed, 17 May 2000 09:44:53 -0400
10. Re: 2.53 was Re: APOP and normal authentication
Eric Hunter <ehunter at netrover dot com>
Wed, 17 May 2000 09:50:54 -0400
11. Re: 2.53 was Re: APOP and normal authentication
Peter Evans <peter at gol dot com>
Wed, 17 May 2000 23:02:25 +0900
12. Re: 2.53 was Re: APOP and normal authentication
"Michael D. Sofka" <sofkam at rpi dot edu>
Wed, 17 May 2000 09:55:08 -0400
13. POP 2.53 (was: Re: APOP and normal authentication)
"Michael D. Sofka" <sofkam at rpi dot edu>
Wed, 17 May 2000 09:54:04 -0400
14. Re: 2.53 was Re: APOP and normal authentication
Admin Mailing Lists <mlist at intergrafix dot net>
Wed, 17 May 2000 11:13:25 -0400 (EDT)
15. Qpopper 3.1b1 available
Qpopper Support <qpopper at qualcomm dot com>
Wed, 17 May 2000 16:48:51 -0700
16. Qpopper 3.0.2 available
Qpopper Support <qpopper at qualcomm dot com>
Wed, 17 May 2000 16:48:17 -0700
17. solution - maillock error 5
civ at gbis dot com
Thu, 18 May 2000 05:54:57 -0700
18. Qpopper & SASL
Patrick LIN <patrickl at cst dot ca>
Thu, 18 May 2000 01:14:52 +0000
19. Re: Qpopper & SASL
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Thu, 18 May 2000 12:30:21 -0400
20. POP3 service terminated
"Fabio Oliveira" <fabio.oliveira at nttb.com dot br>
Fri, 19 May 2000 17:01:26 -0300
21. Re: POP3 service terminated
Vinay Bharel <vinay at bharel dot com>
Fri, 19 May 2000 13:11:15 -0700 (PDT)
22. Re: POP3 service terminated
"Fabio Oliveira" <fabio.oliveira at nttb.com dot br>
Fri, 19 May 2000 17:24:47 -0300
23. RE: qpopper3.0 install on Solaris 7
"Ben Hyatt" <benski at pacbell dot net>
Fri, 19 May 2000 17:20:06 -0700
24. Re: POP3 service terminated
Peter Evans <peter at gol dot com>
Sat, 20 May 2000 13:08:55 +0900
25. New qpopper 3.0.2 RPM
"Kenneth Porter" <shiva at well dot com>
Sat, 20 May 2000 17:29:02 -0700
26. How to install qpopper
Luis M.Cova A. <lcova at usa dot net>
21 May 00 00:58:54 AST
27. Re: How to install qpopper
Alex Charalabidis <alex at wnm dot net>
Sun, 21 May 2000 01:15:02 -0500 (CDT)
28. Some assistance with an error message would be greatly appreciate
Filippo Dello <fdello at zoo.net dot uk>
Mon, 22 May 2000 15:03:37 +0100
29. Re: Some assistance with an error message would be greatly appreciate d
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Mon, 22 May 2000 10:52:43 -0400
30. Re: Some assistance with an error message would be greatly appreciate
Jason Englander <jason at interl dot net>
Mon, 22 May 2000 18:39:07 -0500 (CDT)
31. Re: Some assistance with an error message would be greatly
Qpopper Support <qpopper at qualcomm dot com>
Tue, 23 May 2000 09:10:43 -0700
32. Re: Some assistance with an error message would be greatly appreciate d
Joel Laing <joel at scripps dot edu>
Tue, 23 May 2000 09:24:28 -0700
33. New version of Cyrus-SASL patches
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Wed, 24 May 2000 00:44:23 -0400
34. Re: New version of Cyrus-SASL patches
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Wed, 24 May 2000 00:48:32 -0400
35. Security Vulnerability in Qpopper 2.53 (Upgrade to 3.0.2)
Qpopper Support <qpopper at qualcomm dot com>
Tue, 23 May 2000 22:37:30 -0700
36. libgdbm.so.2 error
"Serkan AKCIN" <serkan at baskent.edu dot tr>
Wed, 24 May 2000 14:03:14 +0300
37. Re: libgdbm.so.2 error
Fergal Daly <fergal at esatclear dot ie>
Wed, 24 May 2000 12:36:06 +0100
38. Mail Delivery Process
"Gregory Hall" <Ghall at HAI dot COM>
Wed, 24 May 2000 10:10:19 -0400
39. Re: Mail Delivery Process
Fergal Daly <fergal at esatclear dot ie>
Wed, 24 May 2000 15:36:02 +0100
40. 3.0.2 distribution problem
Tadeusz Wiewiorowski <twiewior at toronto.cbc dot ca>
Wed, 24 May 2000 12:39:48 -0400
41. MAXHOSTNAMELEN
Mikio Watanabe <nabe at sahs.med.osaka-u.ac dot jp>
Thu, 25 May 2000 10:52:00 +0900
42. patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Steven Champeon <schampeo at hesketh dot com>
Wed, 24 May 2000 21:49:57 -0400 (EDT)
43. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
"Mitch Vincent" <mitch at venux dot net>
Wed, 24 May 2000 22:13:04 -0400
44. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Steven Champeon <schampeo at hesketh dot com>
Wed, 24 May 2000 22:17:10 -0400 (EDT)
45. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Ken Hornstein <kenh at cmf.nrl.navy dot mil>
Wed, 24 May 2000 22:57:47 -0400
46. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Alan Brown <alan at manawatu.gen dot nz>
Thu, 25 May 2000 15:30:28 +1200 (NZST)
47. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Steven Champeon <schampeo at hesketh dot com>
Wed, 24 May 2000 23:26:45 -0400 (EDT)
48. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Alan Brown <alan at manawatu.gen dot nz>
Thu, 25 May 2000 15:52:08 +1200 (NZST)
49. Re: patch for DRAC support in qpopper 3.0.2 (includes
Randall Gellens <randy at qualcomm dot com>
Wed, 24 May 2000 21:08:51 -0700
50. Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Alan Brown <alan at manawatu.gen dot nz>
Thu, 25 May 2000 17:31:57 +1200 (NZST)
From: "Rui Paz" <rpaz at uevora dot pt>
Subject: APOP and normal authentication
Date: Tue, 16 May 2000 23:36:52 +0100
Hi,
Maybe this is a very simple question, but I'm new on this list.
I'm using qpopper 2.53-3 and I want to know if is possible to set qpopper to
allowed some users to use APOP authentication, and other clear pass.
This works on 2.3-4 and now don't. Is this a result off changes on qpopper?
Tanks,
Rui Paz
Date: Tue, 16 May 2000 17:42:51 -0500
From: "Julian Y. Koh" <kohster at mac dot com>
Subject: Re: APOP and normal authentication
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 23:36 +0100 5/16/2000, Rui Paz wrote:
>Maybe this is a very simple question, but I'm new on this list.
>
>I'm using qpopper 2.53-3 and I want to know if is possible to set
>qpopper to allowed some users to use APOP authentication, and other
>clear pass.
>
>This works on 2.3-4 and now don't. Is this a result off changes on
>qpopper?
Sure it's possible. The only users who will use APOP are those who
appear in /etc/pop.auth. Those that don't will use regular USER/PASS
authentication.
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.2
Comment: <http://charlotte.at.northwestern.edu/julian/pgppubkey.html>
iQA/AwUBOSHO6A5UB5zJHgFjEQJqzwCg8G2XedrYonMZ3qRDH4KkVSLVngcAn25l
AJKqMFaoHb1lvRa2q/DlL1OG
=vBLY
-----END PGP SIGNATURE-----
--
Julian Y. Koh
kohster at mac dot com
PGP Public Key:<http://charlotte.at.northwestern.edu/julian/pgppubkey.html>
From: "Rui Paz" <rpaz at uevora dot pt>
Subject: Re: APOP and normal authentication
Date: Tue, 16 May 2000 23:56:01 +0100
----- Original Message -----
From: "Julian Y. Koh" <kohster at mac dot com>
To: "Rui Paz" <rpaz at uevora dot pt>; "Subscribers of Qpopper"
<qpopper at lists.pensive dot org>
Sent: Tuesday, May 16, 2000 11:42 PM
Subject: Re: APOP and normal authentication
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At 23:36 +0100 5/16/2000, Rui Paz wrote:
> >Maybe this is a very simple question, but I'm new on this list.
> >
> >I'm using qpopper 2.53-3 and I want to know if is possible to set
> >qpopper to allowed some users to use APOP authentication, and other
> >clear pass.
> >
> >This works on 2.3-4 and now don't. Is this a result off changes on
> >qpopper?
>
> Sure it's possible. The only users who will use APOP are those who
> appear in /etc/pop.auth. Those that don't will use regular USER/PASS
> authentication.
Yes this is working on version 2.3-4 but now it gives this error on the log:
-ERR Unknown command: "pass" for a user that is not on pop.auth
Any ideas how to solve this?
Rui Paz
Date: Wed, 17 May 2000 02:04:06 -0700
From: civ at gbis dot com
Subject: maillock error 4 & 5
Can any one help me with the following errors qpopper 3.0 on FreeBSD.. was
working fine, /var ran out of disk space, now I cannot fix this error
(after freeing up space). All POP3 users receive it for their various
usernames.
Have tried restarting inetd, recompiling popper. no luck.
How can I fix this?
Thanks for any help / links / advice in advance.
--Mike
from /var/log/messages
<snip>
May 17 01:32:01 vector qpopper[1755]: fstat() for /var/mail/tucker.lock
returned No such file or directory (2) and open() returned EACCESS
May 17 01:32:01 vector qpopper[1755]: fstat() for /var/mail/tucker.lock
returned No such file or directory (2) and open() returned EACCESS
May 17 01:32:01 vector qpopper[1755]: tucker at rno-dsl0b-190.gbis.net
(216.82.145.190): -ERR [SYS/TEMP] maillock error 5: '/var/mail/tucker'
May 17 01:32:01 vector qpopper[1755]: tucker at rno-dsl0b-190.gbis.net
(216.82.145.190): -ERR [SYS/TEMP] maillock error 5: '/var/mail/tucker'
</snip>
Date: Wed, 17 May 2000 07:55:19 -0400
From: "Gregory Hall" <Ghall at HAI dot COM>
Subject: Configuring gcc
To all who helped me yesterday I thank you. I ask once again for your =
assistance. I have never compiled, built or installed gcc before. I have =
it on my Solaris 7 platform but after reading what directions I found =
available I am not sure how to proceed. All I want is to get this loaded =
correctly so I can get my qpopper3.0 going as well. Any clearly defined =
directions on what to do would be greatly appreciated.
Thanks in advance,
Greg
Date: Wed, 17 May 2000 09:06:53 -0400 (EDT)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: Re: APOP and normal authentication
i am amazed at the number of people that post to this list that still use
2.53 or older. what gives?
just a random thought.
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
admin at intergrafix dot net Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://cygnus.ncohafmuta.com http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
On Tue, 16 May 2000, Rui Paz wrote:
> ----- Original Message -----
> From: "Julian Y. Koh" <kohster at mac dot com>
> To: "Rui Paz" <rpaz at uevora dot pt>; "Subscribers of Qpopper"
> <qpopper at lists.pensive dot org>
> Sent: Tuesday, May 16, 2000 11:42 PM
> Subject: Re: APOP and normal authentication
>
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > At 23:36 +0100 5/16/2000, Rui Paz wrote:
> > >Maybe this is a very simple question, but I'm new on this list.
> > >
> > >I'm using qpopper 2.53-3 and I want to know if is possible to set
> > >qpopper to allowed some users to use APOP authentication, and other
> > >clear pass.
> > >
> > >This works on 2.3-4 and now don't. Is this a result off changes on
> > >qpopper?
> >
> > Sure it's possible. The only users who will use APOP are those who
> > appear in /etc/pop.auth. Those that don't will use regular USER/PASS
> > authentication.
>
> Yes this is working on version 2.3-4 but now it gives this error on the log:
> -ERR Unknown command: "pass" for a user that is not on pop.auth
>
> Any ideas how to solve this?
>
> Rui Paz
>
>
>
Date: Wed, 17 May 2000 22:24:31 +0900
From: Peter Evans <peter at gol dot com>
Subject: 2.53 was Re: APOP and normal authentication
Admin Mailing Lists (mlist at intergrafix dot net) wrote:
> i am amazed at the number of people that post to this list that still use
> 2.53 or older. what gives?
> just a random thought.
"If it aint broke, don't fix it."
P
----*
gnu-pop3d, btw isnt ready for prime time.
so back to 2.53 as 3.x has all that blecherous mime.
--
Remember The 5 K's.
The Justified Agents of Munya-munya-muuuu ...
Date: Thu, 18 May 2000 01:41:52 +1200 (NZST)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: 2.53 was Re: APOP and normal authentication
On Wed, 17 May 2000, Peter Evans wrote:
> > i am amazed at the number of people that post to this list that still use
> > 2.53 or older. what gives?
> > just a random thought.
>
>
> "If it aint broke, don't fix it."
I guess "remote attacker can get root shell" doesn't count as broken in
some universes.
AB
Subject: Re: 2.53 was Re: APOP and normal authentication
Date: Wed, 17 May 2000 09:44:53 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
> gnu-pop3d, btw isnt ready for prime time.
> so back to 2.53 as 3.x has all that blecherous mime.
Errr, _what_ blecherous mime? If you're talking about the MIME mangling
stuff, you don't have to use it at all.
(I just upgraded to 3.0.1 last week, but that's mostly because I'm
lazy).
--Ken
Date: Wed, 17 May 2000 09:50:54 -0400
From: Eric Hunter <ehunter at netrover dot com>
Subject: Re: 2.53 was Re: APOP and normal authentication
Has it been CONFIRMED that 2.53 is vulnerable?
Eric
At 01:41 AM 5/18/00 +1200, Alan Brown wrote:
>On Wed, 17 May 2000, Peter Evans wrote:
>
>> > i am amazed at the number of people that post to this list that still use
>> > 2.53 or older. what gives?
>> > just a random thought.
>>
>>
>> "If it aint broke, don't fix it."
>
>I guess "remote attacker can get root shell" doesn't count as broken in
>some universes.
>
>AB
>
>
Date: Wed, 17 May 2000 23:02:25 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: 2.53 was Re: APOP and normal authentication
Alan Brown (alan at manawatu.gen dot nz) wrote:
> On Wed, 17 May 2000, Peter Evans wrote:
(oops, trimmed too much)
Someone wrote:
> > > i am amazed at the number of people that post to this list that still use
> > > 2.53 or older. what gives?
> > > just a random thought.
> > "If it aint broke, don't fix it."
> I guess "remote attacker can get root shell" doesn't count as broken in
> some universes.
Those are the people who only fix things when they get hacked. Personally
I prefer the pro-active approach to the "its ok, no one will ever want to
hack us" mentality[1]
I was under the impression, misguided or otherwise, that 2.53
was the fixed one. (3.0 with its mime evil is a whole new can of worms,
I want a #define NOMIMECRUFT just so it will compile cleanly ^_^)
the root shell stuff appears almost exclusively to be an anathema
for linux and mumble-bsd on intel, since it seems to rely on walking
off a buffer and executing it, I doubt people are going to write such
a hack for irix. (now that must be flame bait ^_^)
P
[1] our local version is "too stupid to README" then they whine when they get
hacked, used as a spam relay, have their web page defaced, etc etc. -.-; a good
example is ns*.*.*.jp is almost certainly an open relay, but thats offtopic for
this list ...
--
Remember The 5 K's.
The Justified Agents of Munya-munya-muuuu ...
Date: Wed, 17 May 2000 09:55:08 -0400
From: "Michael D. Sofka" <sofkam at rpi dot edu>
Subject: Re: 2.53 was Re: APOP and normal authentication
At 01:41 AM 5/18/00 +1200, Alan Brown wrote:
>On Wed, 17 May 2000, Peter Evans wrote:
>
> > > i am amazed at the number of people that post to this list that still use
> > > 2.53 or older. what gives?
> > > just a random thought.
> >
> >
> > "If it aint broke, don't fix it."
>
>I guess "remote attacker can get root shell" doesn't count as broken in
>some universes.
One of the nice things about souce-code distributions is they
come complete with their own patch kit.
Mike
--
Michael D. Sofka sofkam at rpi dot edu
CIS/SSS Sr. Systems Programmer AFS/DFS, email, listproc, TeX, epistemology.
Rensselaer Polytechnic Institute, Troy, NY. http://www.rpi.edu/~sofkam/
Date: Wed, 17 May 2000 09:54:04 -0400
From: "Michael D. Sofka" <sofkam at rpi dot edu>
Subject: POP 2.53 (was: Re: APOP and normal authentication)
At 09:06 AM 5/17/00 -0400, Admin Mailing Lists wrote:
>i am amazed at the number of people that post to this list that still use
>2.53 or older. what gives?
>just a random thought.
3.0 was in beta until just recently (maybe two months ago). Until
then, 2.53 was the latest production release. Despite encouragement
to go to 3.0, there were enough problems being reported that I saw
no need to turn our mail server into a beta test machine. (Although I
did compile one of the betas and run it on a test machine.) As
a practice, I tend to wait until the first patch release anyway.
Also, being a University, any server upgrades are likely to occur
between semesters.
Mike
--
Michael D. Sofka sofkam at rpi dot edu
CIS/SSS Sr. Systems Programmer AFS/DFS, email, listproc, TeX, epistemology.
Rensselaer Polytechnic Institute, Troy, NY. http://www.rpi.edu/~sofkam/
Date: Wed, 17 May 2000 11:13:25 -0400 (EDT)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: Re: 2.53 was Re: APOP and normal authentication
>
> I was under the impression, misguided or otherwise, that 2.53
> was the fixed one. (3.0 with its mime evil is a whole new can of worms,
> I want a #define NOMIMECRUFT just so it will compile cleanly ^_^)
>
i wasn't aware of any mime thingie either, i've been using 3.0.x on linux
without any problems so far, is this some sort of OS-dependent thing?
> the root shell stuff appears almost exclusively to be an anathema
> for linux and mumble-bsd on intel, since it seems to rely on walking
> off a buffer and executing it, I doubt people are going to write such
> a hack for irix. (now that must be flame bait ^_^)
>
i wouldn't shout that too loud :) some people are mighty bored and might
just be up for the challenge
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
admin at intergrafix dot net Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://cygnus.ncohafmuta.com http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Date: Wed, 17 May 2000 16:48:51 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Qpopper 3.1b1 available
Qpopper 3.1b1 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta>.
A somewhat abbreviated change list is on the Qpopper web site at
<http://www.qpopper.org/changelist.html>
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/beta/Changes>.
The 3.1 release notes are at:
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/Release.Notes>.
Changes from 3.0.1 to 3.1b1
---------------------------
1. Added '--enable-drop-dir=spool-dir' ./configure option to
specify the location of the mail spool. The default is to
search for it as previous.
2. Added '-L msgs' run-time flag to specify the number of msgs
we process during initialization and cleanup before checking
if we need to refresh the mail lock. Default is 500. The
value should be small enough to be able to be processed in
60 seconds.
3. Added '-Z' run-time flag to revert to old (pre-3.x) locking.
This is dangerous and will likely be removed prior to release.
4. Added '--enable-timing' ./configure option to write log records
with elapsed time for authentication, initialization, and
cleanup.
Date: Wed, 17 May 2000 16:48:17 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Qpopper 3.0.2 available
Qpopper 3.0.2 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
A somewhat abbreviated change list is on the Qpopper web site at
<http://www.qpopper.org/changelist.html>
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>.
The 3.0 release notes are at:
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/Release.Notes>.
Changes from 3.0.1 to 3.0.2:
1. Tweaked the maillock refresh algorithm to avoid performance
hit. This should help complaints of slow response and some cases
of client timeouts with 3.0.
Date: Thu, 18 May 2000 05:54:57 -0700
From: civ at gbis dot com
Subject: solution - maillock error 5
To resolve the maillock error 5 issue I did the following:
1. Updated to 3.0.2
2. Noticed that files in my mailspool directory had owner:group of
root:wheel with only user permission of rw. Chaned owner:group to actual
user of the file and maillock error was resolved. (#1 probably had nothing
to do with the resolution).
Still looking in to how permissions changed.
--Mike
Date: Thu, 18 May 2000 01:14:52 +0000
From: Patrick LIN <patrickl at cst dot ca>
Subject: Qpopper & SASL
Hi,
perhaps it is a bad question or someone already ask for this
but i cannot find anything about this in the list
someone Know if there are a way to use SASL with qpopper ?
thanks
pat
Subject: Re: Qpopper & SASL
Date: Thu, 18 May 2000 12:30:21 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
>perhaps it is a bad question or someone already ask for this
>but i cannot find anything about this in the list
>
>someone Know if there are a way to use SASL with qpopper ?
Yes! I suppose it's as good of a time as any to announce this.
I've done some patches to qpopper 3.0.1 to add support to the Cyrus
SASL library. This _includes_ support for layer encryption. I've
only tested it currently with the GSSAPI mechanism, but I think
it should work fine with other mechanisms.
There really needs to be some more work done to add some configuration
support to qpopper (such as specifying minimum/maximum encryption
layer preferences, mechanism preferences, etc etc), but the hard
work is all done. I've tested this with some SASL patches I've been
working on for NMH (and no, I'm not done with that yet :-) ), and
so far it seems to work great.
It's perfectly possible that I've messed something up, but I think
it's mostly right. Feedback is welcome. You can get the patch from:
ftp://ftp.cmf.nrl.navy.mil/pub/kenh/qpopper-sasl-patch
Enjoy!
--Ken
From: "Fabio Oliveira" <fabio.oliveira at nttb.com dot br>
Subject: POP3 service terminated
Date: Fri, 19 May 2000 17:01:26 -0300
Hi all,
I would like to know the causes to a problem that is occuring in my system.
I am using the QPOPPER 2.53 e I had get some messages about problem with
pop-3 service.
The message is the following:
pop-3/tcp server failing (looping) , service terminated.
It is happen unexpected in our server.
Please if someone can help us , I hope it.....
Thanks in advance.
Best Regards,
Fabio Oliveira
System Engineer
Date: Fri, 19 May 2000 13:11:15 -0700 (PDT)
From: Vinay Bharel <vinay at bharel dot com>
Subject: Re: POP3 service terminated
From the Readme:
If you have a lot of users connecting, you may need to
increase the inetd timeout value, to prevent it from assuming
popper is looping, which causes it to kill popper and write a
log entry noting "service looping". You can increase the global
inetd timeout by passing inetd a command line argument. On some
systems, you can alter the timeout for qpopper by changing
"nowait" to "nowait.timeout", for example, "nowait.400".
---
Vinay Bharel
vinay at bharel dot com
http://www.bharel.com
On Fri, 19 May 2000, Fabio Oliveira wrote:
> Hi all,
>
> I would like to know the causes to a problem that is occuring in my system.
> I am using the QPOPPER 2.53 e I had get some messages about problem with
> pop-3 service.
>
> The message is the following:
> pop-3/tcp server failing (looping) , service terminated.
>
> It is happen unexpected in our server.
> Please if someone can help us , I hope it.....
>
> Thanks in advance.
>
> Best Regards,
>
> Fabio Oliveira
> System Engineer
>
>
>
>
From: "Fabio Oliveira" <fabio.oliveira at nttb.com dot br>
Subject: Re: POP3 service terminated
Date: Fri, 19 May 2000 17:24:47 -0300
Thank you so much for your tip.
I am using the Linux Red Hat 6, so I am going to change in /etc/services
this value to:
pop-3 stream tcp nowait.400 root /usr/sbin/tcpd in.qpopper
I hope that it run correctly..
Regards,
Fabio Oliveira
System Engineer
-----Mensagem original-----
De: Vinay Bharel <vinay at bharel dot com>
Para: Fabio Oliveira <fabio.oliveira at nttb.com dot br>
Cc: Subscribers of Qpopper <qpopper at lists.pensive dot org>
Data: Sexta-feira, 19 de Maio de 2000 17:14
Assunto: Re: POP3 service terminated
>From the Readme:
>
>If you have a lot of users connecting, you may need to
>increase the inetd timeout value, to prevent it from assuming
>popper is looping, which causes it to kill popper and write a
>log entry noting "service looping". You can increase the global
>inetd timeout by passing inetd a command line argument. On some
>systems, you can alter the timeout for qpopper by changing
>"nowait" to "nowait.timeout", for example, "nowait.400".
>
>---
>Vinay Bharel
>vinay at bharel dot com
>http://www.bharel.com
>
>On Fri, 19 May 2000, Fabio Oliveira wrote:
>
>> Hi all,
>>
>> I would like to know the causes to a problem that is occuring in my
system.
>> I am using the QPOPPER 2.53 e I had get some messages about problem with
>> pop-3 service.
>>
>> The message is the following:
>> pop-3/tcp server failing (looping) , service terminated.
>>
>> It is happen unexpected in our server.
>> Please if someone can help us , I hope it.....
>>
>> Thanks in advance.
>>
>> Best Regards,
>>
>> Fabio Oliveira
>> System Engineer
>>
>>
>>
>>
>
>
From: "Ben Hyatt" <benski at pacbell dot net>
Subject: RE: qpopper3.0 install on Solaris 7
Date: Fri, 19 May 2000 17:20:06 -0700
Hi,
The easiest thing to do is....
Get the gcc package from http://www.sunfreeware.com
pkgadd -d
--Ben
-----Original Message-----
From: Gregory Hall [mailto:Ghall at HAI dot COM]
Sent: Tuesday, May 16, 2000 8:25 AM
To: Subscribers of Qpopper
Subject: qpopper3.0 install on Solaris 7
I am trying to install qpopper3.0 on a Solaris 7 platform. I am getting an
error from the get go when I issue the command ./configure. The error reads
as such.
creating cache ./config.cache
checking whether make sets ${MAKE}... yes
checking for gcc... no
checking for cc... no
configure:error: no acceptable cc found in $PATH
My guess is I don't have cc on my machine. I did do a man on cc and it
tells me that /usr/ucb/cc is the interface to the BSD Compatibility Package
C compiler. It is a script that looks for the link /usr/ccs/bin/ucbcc to
the C compiler. /usr/ccs/bin/ucbcc is available only w/ the SPROcc package,
whose default location is /opt/SUNWspro. I did check to see if SUNWspro
was located under /opt and I did not see it. If this is the case and I
don't have the necessary C compiler needed to configure qpopper can someone
give me some help on how I can get what I need.
Thanks in advance
Greg
Greg Hall
Unix Systems Administrator
Houston Associates, Inc.
703 284-8777
Date: Sat, 20 May 2000 13:08:55 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: POP3 service terminated
Vinay Bharel (vinay at bharel dot com) wrote:
> >From the Readme:
> If you have a lot of users connecting, you may need to
> increase the inetd timeout value, to prevent it from assuming
> popper is looping, which causes it to kill popper and write a
> log entry noting "service looping". You can increase the global
> inetd timeout by passing inetd a command line argument. On some
> systems, you can alter the timeout for qpopper by changing
> "nowait" to "nowait.timeout", for example, "nowait.400".
Or you can install DJB's "tcpserver", which has been doing
a sterling job of spawning poppers on our server for the past
couple of months.
mail 14055379 1 0 Jan 21 ? 789:41 /usr/local/bin/tcpserver -c 512 -R -g 4 -u 44444 my.ip.addr.ess 110 /mail/sbin/borg.popper -s
P
--
Remember The 5 K's.
The Justified Agents of Munya-munya-muuuu ...
From: "Kenneth Porter" <shiva at well dot com>
Date: Sat, 20 May 2000 17:29:02 -0700
Subject: New qpopper 3.0.2 RPM
I just uploaded an RPM for 3.0.2 to Red Hat's incoming directory, so it
should appear in the usual places in a couple of days. Of note to those
who rebuild from the SRPM: As qpopper 3.1 is now in beta, I changed the
name of the 3.0.2 spec file from qpopper3.0.spec to qpopper.spec.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
http://www.harrybrowne2000.org/
Date: 21 May 00 00:58:54 AST
From: Luis M.Cova A. <lcova at usa dot net>
Subject: How to install qpopper
I have a problem installing qpopper (or i dont know how to install it)
I downloaded qpopper 2.52 & 3.02 to my linux computer (in format *.tar.Z =
$
*.tar.gz)...
First, how do i uncompress those files (unzip doesent work)
Then, i manage to convert the files to *.zip format (copying to a win98
machine and with winzip uncompressing and then compressing again).
when i downloaded it to the linux server i then use unzip qpopper3.02.zip=
and
the file uncompress fine to all there directories,but when i try to confi=
gure
it (./configure) the system tell's me "permision denied"...
So what am i doing wrong, and how do i fix it....
Please tell me step by step (assume i just downloades the *.tar.Z and/or
*.tar.Z files)
So how do i decompress those files...
How do i install the program.. ???
Please HELP
Luis Cova
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N==
1
Date: Sun, 21 May 2000 01:15:02 -0500 (CDT)
From: Alex Charalabidis <alex at wnm dot net>
Subject: Re: How to install qpopper
On 21 May 2000, Luis M.Cova A. wrote:
> I have a problem installing qpopper (or i dont know how to install it)
>
> I downloaded qpopper 2.52 & 3.02 to my linux computer (in format *.tar.Z $
> *.tar.gz)...
> First, how do i uncompress those files (unzip doesent work)
>
> Then, i manage to convert the files to *.zip format (copying to a win98
> machine and with winzip uncompressing and then compressing again).
> when i downloaded it to the linux server i then use unzip qpopper3.02.zip and
> the file uncompress fine to all there directories,but when i try to configure
> it (./configure) the system tell's me "permision denied"...
>
> So what am i doing wrong, and how do i fix it....
>
Sorry to be the one to say so, but your question shows unacceptable
ignorance of basic Unix use, let alone system administration. In your
own and your users' best interest, I strongly recommend you get a good
book on using Linux and read it thoroughly before going any further. By
the time you're halfway through it, you'll understand why I'm saying this.
> Please tell me step by step (assume i just downloades the *.tar.Z and/or
> *.tar.Z files)
> So how do i decompress those files...
> How do i install the program.. ???
Regards
-ac
--
==============================================================
Alex Charalabidis (AC8139) 5050 Poplar Ave, Ste 170
Systems Administrator Memphis, TN 38157
WebNet Memphis (901) 432 6000
Author, The Book of IRC http://www.bookofirc.com/
==============================================================
From: Filippo Dello <fdello at zoo.net dot uk>
Subject: Some assistance with an error message would be greatly appreciate
Date: Mon, 22 May 2000 15:03:37 +0100
Can someone please help me with a problem i am encountering with some of our
clients.
In ther popper logs i am getting the following error message.
-ERR POP EOF or I/O error: Resource temporarily unavailable
and also
-ERR Unknown authentication mechanism: twinki
Has anyone else experienced this problem.?
Thanks in advance
Filippo Dello
Subject: Re: Some assistance with an error message would be greatly appreciate d
Date: Mon, 22 May 2000 10:52:43 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
>-ERR POP EOF or I/O error: Resource temporarily unavailable
This is typically the Unix error EAGAIN; you might want to check your
system's man pages to see why read(2) would return EAGAIN (I suspect
it's just clients closing their connections ungracefully).
>-ERR Unknown authentication mechanism: twinki
I seem to remember seeing this one before, but I can't find it now. Anyway,
this comes from some client issuing an "AUTH twinki" command; why it
would do that, I have NO idea.
--Ken
Date: Mon, 22 May 2000 18:39:07 -0500 (CDT)
From: Jason Englander <jason at interl dot net>
Subject: Re: Some assistance with an error message would be greatly appreciate
On Mon, 22 May 2000, Ken Hornstein wrote:
> >-ERR Unknown authentication mechanism: twinki
>
> I seem to remember seeing this one before, but I can't find it now. Anyway,
> this comes from some client issuing an "AUTH twinki" command; why it
> would do that, I have NO idea.
>
> --Ken
I think that one is a client using APOP when it's not supported
(enabled) in qpopper.
qpopper 3.0.2 logs this:
-ERR Unknown authentication mechanism: twinkie
Jason
--
Jason Englander <jason at interl dot net>
Systems Administrator - InterLink L.C.
Date: Tue, 23 May 2000 09:10:43 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Some assistance with an error message would be greatly
At 6:39 PM -0500 5/22/00, Jason Englander wrote:
> On Mon, 22 May 2000, Ken Hornstein wrote:
>
>> >-ERR Unknown authentication mechanism: twinki
>>
>> I seem to remember seeing this one before, but I can't find it
>> now. Anyway,
>> this comes from some client issuing an "AUTH twinki" command; why it
>> would do that, I have NO idea.
>>
>> --Ken
>
> I think that one is a client using APOP when it's not supported
> (enabled) in qpopper.
>
> qpopper 3.0.2 logs this:
>
> -ERR Unknown authentication mechanism: twinkie
This is a client sending AUTH TWINKIE, which of course is an
unsupported, non-standard mechanism, so of course it is a MS product
that is doing this.
If a client tries APOP when Qpopper doesn't support APOP, the error
is "Unknown command: APOP".
Date: Tue, 23 May 2000 09:24:28 -0700
From: Joel Laing <joel at scripps dot edu>
Subject: Re: Some assistance with an error message would be greatly appreciate d
Check the client's timeouts. Is this a dial up? In particular, I've
found that older versions of Eudora (great product even with the ads :)
) seem to default to too short a timeout... From a previous message on
this list, it was mentioned that the I/O part of the error is just error
handling confusion. That is, that there is no reliable way to know if
it's EOF or I/O, so both are printed. It's almost always premature I/O
caused by client timeouts and/or slow connections. You can always check
the syslog to confirm that there really are no I/O errors.. scsi
timeouts etc...
-Joel
Ken Hornstein wrote:
>
> >-ERR POP EOF or I/O error: Resource temporarily unavailable
>
> This is typically the Unix error EAGAIN; you might want to check your
> system's man pages to see why read(2) would return EAGAIN (I suspect
> it's just clients closing their connections ungracefully).
>
> >-ERR Unknown authentication mechanism: twinki
>
> I seem to remember seeing this one before, but I can't find it now. Anyway,
> this comes from some client issuing an "AUTH twinki" command; why it
> would do that, I have NO idea.
>
> --Ken
Subject: New version of Cyrus-SASL patches
Date: Wed, 24 May 2000 00:44:23 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
I've placed a new version of my qpopper-SASL patches, updated for
qpopper 3.0.2 (which didn't really require any changes, actually :-) ).
Included in this patch is a small bugfix to the SASL code which may
affect interoperability with other systems if you're using the CRAM-MD5
mechanism.
Comments & suggestions are welcome. "Share and enjoy"
--Ken
Subject: Re: New version of Cyrus-SASL patches
Date: Wed, 24 May 2000 00:48:32 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
>I've placed a new version of my qpopper-SASL patches, updated for
>qpopper 3.0.2 (which didn't really require any changes, actually :-) ).
>Included in this patch is a small bugfix to the SASL code which may
>affect interoperability with other systems if you're using the CRAM-MD5
>mechanism.
Whoops, sorry ... I forgot to mention WHERE THEY ARE!
ftp://ftp.cmf.nrl.navy.mil/pub/kenh/qpopper-sasl-patch-3.0.2
--Ken
Date: Tue, 23 May 2000 22:37:30 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Security Vulnerability in Qpopper 2.53 (Upgrade to 3.0.2)
Qpopper development has learned of a security vulnerability in
Qpopper 2.53 (and older). All users of Qpopper are urged to upgrade
to 3.0.2 or later.
The details have been reported to CERT and BugTraq. The exploit
involves sending a specially-constructed message to a user, then
logging in as that user and issuing the EUIDL command. A successful
attack can yield a shell running with group 'mail'.
It is important to note that the attack:
1. Requires the ability to log in as a user.
2. Can at most give a shell with uid of the user and gid of mail,
potentially allowing access to other user's mail.
3. Will be logged.
4. Requires Qpopper 2.53 or older. The current released version is 3.0.2.
In addition, not all sites use group 'mail' or have Qpopper set to
run with gid=mail, or have spools owned by group 'mail' and have rw
group access. However, this is a very common configuration.
Qpopper 3.0 has additional protections against buffer overflows; this
exploit proves the usefulness of this approach.
From: "Serkan AKCIN" <serkan at baskent.edu dot tr>
Subject: libgdbm.so.2 error
Date: Wed, 24 May 2000 14:03:14 +0300
Hi,
I want to enable APOP service.
First, I installed GDBM successfully on my system. (Solaris 2.7)
All the other qpopper compilations are successfully ended.
popauth command work successful. (Like popauth -init).
And I can set passwords for users.
But when I want to get message from Pop3 Client (Outlook Express)
it gives an error like "libgdbm.so.2: open failed: No such file or
directory"
I know this error comes from LD_LIBRARY_PATH.
But How can I set the LD_LIBRARY_PATH.
I use /etc/profile or /etc/default/login or ~./tcshrc.
But nothing changed.
(The above files are login based files. But qpopper service run from
inetd.conf. And don't get variables from this files.)
I want to learn any files like ld.so.conf under LINUX. That I can write the
lib paths. Or any other solutions.
Date: Wed, 24 May 2000 12:36:06 +0100
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: libgdbm.so.2 error
Have a look in /etc/ld.so.conf or something like that (it may vary
depending on distribution) add a line for the directory containing libgdbm
then run ldconfig to update the library cache,
Fergal
At 12:03 24/05/00, Serkan AKCIN wrote:
>Hi,
>
>I want to enable APOP service.
>First, I installed GDBM successfully on my system. (Solaris 2.7)
>All the other qpopper compilations are successfully ended.
>popauth command work successful. (Like popauth -init).
>And I can set passwords for users.
>
>But when I want to get message from Pop3 Client (Outlook Express)
>it gives an error like "libgdbm.so.2: open failed: No such file or
>directory"
>
>I know this error comes from LD_LIBRARY_PATH.
>But How can I set the LD_LIBRARY_PATH.
>I use /etc/profile or /etc/default/login or ~./tcshrc.
>But nothing changed.
>(The above files are login based files. But qpopper service run from
>inetd.conf. And don't get variables from this files.)
>
>I want to learn any files like ld.so.conf under LINUX. That I can write the
>lib paths. Or any other solutions.
Date: Wed, 24 May 2000 10:10:19 -0400
From: "Gregory Hall" <Ghall at HAI dot COM>
Subject: Mail Delivery Process
To all,
I have set up my qpopper mail server and I believe everything is as it =
should be in that server. I have created a user account under /var/mail. =
Now I am trying to figure out exactly how to add whatever is needed in my =
DNS server. Currently there is a MX entry for a customer using their own =
mail server(sendmail). I don't believe adding my machine w/ the same "1" =
priority under the current customer MX entry will cause a problem as long =
as I point the machines under those entries to the correct server.
So far the problem I am having is when a message is sent from a machine to =
the new mail server, it can't find the user account on the mail server I =
have set up. I know I'm doing something wrong I just don't know what it =
is.
My guess is that when a message is sent to my user on my new mail server =
it hits the DNS server and from their should point the message to the =
correct machine and user account. It isn't doing that. Instead I'm =
getting error messages in my root mail account on both my DNS server and =
mail server. I realize this is probably very general in detail, but if =
anyone can help me or tell me how entries in my DNS server can or should =
be set up I would appreciate it.
Thanks in advance,
Greg Hall
ps. When a message is sent should it include the DNS server name in the =
full address ie: greg at mailserver.dnsserver.xxx.xxx dot xxx or should it read =
greg at mailserver.xxx.xxx dot xxx?
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: Mail Delivery Process
Date: Wed, 24 May 2000 15:36:02 +0100
This is completely off topic for this list. Why not ask this on a sendmail list
where you're far more likely to get a rapid and accurate response?
Fergal
On Wed, 24 May 2000, Gregory Hall wrote:
> To all,
>
> I have set up my qpopper mail server and I believe everything is as it should be in that server. I have created a user account under /var/mail. Now I am trying to figure out exactly how to add whatever is needed in my DNS server. Currently there i
MX entry for a customer using their own mail server(sendmail). I don't believe adding my machine w/ the same "1" priority under the current customer MX entry will cause a problem as long as I point the machines under those entries to the correct server.
>
> So far the problem I am having is when a message is sent from a machine to the new mail server, it can't find the user account on the mail server I have set up. I know I'm doing something wrong I just don't know what it is.
>
> My guess is that when a message is sent to my user on my new mail server it hits the DNS server and from their should point the message to the correct machine and user account. It isn't doing that. Instead I'm getting error messages in my root mail
count on both my DNS server and mail server. I realize this is probably very general in detail, but if anyone can help me or tell me how entries in my DNS server can or should be set up I would appreciate it.
>
> Thanks in advance,
>
> Greg Hall
>
>
> ps. When a message is sent should it include the DNS server name in the full address ie: greg at mailserver.dnsserver.xxx.xxx dot xxx or should it read
Date: Wed, 24 May 2000 12:39:48 -0400
From: Tadeusz Wiewiorowski <twiewior at toronto.cbc dot ca>
Subject: 3.0.2 distribution problem
I have just downloaded and compiled qpopper 3.0.2 on HP-UX 10.20.
In order to get "make" working I had to change permissions on the
etags.c [in the mmangle subdir] from 444 to 644 .
Any comments ?
Tadeusz Wiewiorowski
CBC Toronto
Date: Thu, 25 May 2000 10:52:00 +0900
From: Mikio Watanabe <nabe at sahs.med.osaka-u.ac dot jp>
Subject: MAXHOSTNAMELEN
Hi, friends,
I compiled qpopper3.0.2 on Soralis 2.5.1,
but failed and received following messages.
What can I do for conpile successfully?
Thanks.
M.Watanabe
----MESSAGES----
# make
cd ./popper && make all
gcc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -O2 -fpcc-struct-return -DHAVE_CONFIG_H -DSOLARIS2 -DSPEC_POP_AUTH
-DGNU_PAS
S -DNO_GETLINE -DCONTENT_LENGTH=1 -DUNIX pop_init.c -o pop_init.o
pop_init.c: In function `pop_init':
pop_init.c:340: `MAXHOSTNAMELEN' undeclared (first use this function)
pop_init.c:340: (Each undeclared identifier is reported only once
pop_init.c:340: for each function it appears in.)
*** Error code 1
make: Fatal error: Command failed for target `pop_init.o'
Current working directory /tmp/qpopper3.0.2/popper
*** Error code 1
make: Fatal error: Command failed for target `popper_server'
Date: Wed, 24 May 2000 21:49:57 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Hello, folks -
I've finally gotten around to making a more-or-less official patch for
qpopper 3.0.2 that adds support for DRAC (Dynamic Relay Authorization
Control) to the base distrib, including hacks to pop_pass.c and the GNU
autoconf configure.in file, config.h.in, etc.
If you have autoconf and can figure out how to run it (in order to
generate the 'configure' script) then you can simply grab this patch:
http://hesketh.com/schampeo/qpopper/patch-qpopper-3.0.2-drac-no-configure
If you don't have autoconf, or don't want to bother running autoconf to
create the new configure script, use this patch, which is much longer due
to all the line numbers changing from one configure file to the next (a
minor complaint, to be sure.)
http://hesketh.com/schampeo/qpopper/patch-qpopper-3.0.2-drac
Both patches may be applied via the usual means:
tar xvzf qpopper3.0.2.tar.gz
cat patch-qpopper-3.0.2-drac | patch -p0
or
tar xvzf qpopper3.0.2.tar.gz
cat patch-qpopper-3.0.2-drac-no-configure | patch -p0
cd qpopper3.02
autoconf
Hopefully, now these will make it into the base distrib so I don't
have to keep hacking this stuff into qpopper every time a new dot
version or beta is released. The basic hacks haven't changed at all
since 2.52/pop_pass.c. This just makes it easier.
I've only tested this on Linux, but the hack is relatively small and
I can't imagine that any platform which supports RPCs and on which DRAC
compiles cleanly would have any problems.
If you don't know what DRAC is, see:
http://mail.cc.umanitoba.ca/drac/
(It's basically an implementation of POP-before-SMTP using an RPC
daemon to store IP addresses of roamers as they authenticate, so
that sendmail can check subsequent attempts to relay from those IPs
and determine whether or not to accept the mail.)
Thanks,
Steve
--
tired of being an underappreciated functionary in a soulless machine?
hesketh.com is hiring: <http://hesketh.com/careers/>
From: "Mitch Vincent" <mitch at venux dot net>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Date: Wed, 24 May 2000 22:13:04 -0400
Have you guys noticed that a lot of mail clients try to send mail before
they try to check it? I ran into horrible troubles after we started using
POP3 -before-SMTP relay prevention. I haven't been able to totally verify
this but some versions of Eudora, Outlook and Netscape mail seem to be givin
my customers problems..
-Mitch
----- Original Message -----
From: Steven Champeon <schampeo at hesketh dot com>
To: <qpopper at qualcomm dot com>
Cc: <qpopper at lists.pensive dot org>
Sent: Wednesday, May 24, 2000 9:49 PM
Subject: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
> Hello, folks -
>
> I've finally gotten around to making a more-or-less official patch for
> qpopper 3.0.2 that adds support for DRAC (Dynamic Relay Authorization
> Control) to the base distrib, including hacks to pop_pass.c and the GNU
> autoconf configure.in file, config.h.in, etc.
>
> If you have autoconf and can figure out how to run it (in order to
> generate the 'configure' script) then you can simply grab this patch:
>
> http://hesketh.com/schampeo/qpopper/patch-qpopper-3.0.2-drac-no-configure
>
> If you don't have autoconf, or don't want to bother running autoconf to
> create the new configure script, use this patch, which is much longer due
> to all the line numbers changing from one configure file to the next (a
> minor complaint, to be sure.)
>
> http://hesketh.com/schampeo/qpopper/patch-qpopper-3.0.2-drac
>
> Both patches may be applied via the usual means:
>
> tar xvzf qpopper3.0.2.tar.gz
> cat patch-qpopper-3.0.2-drac | patch -p0
>
> or
>
> tar xvzf qpopper3.0.2.tar.gz
> cat patch-qpopper-3.0.2-drac-no-configure | patch -p0
> cd qpopper3.02
> autoconf
>
> Hopefully, now these will make it into the base distrib so I don't
> have to keep hacking this stuff into qpopper every time a new dot
> version or beta is released. The basic hacks haven't changed at all
> since 2.52/pop_pass.c. This just makes it easier.
>
> I've only tested this on Linux, but the hack is relatively small and
> I can't imagine that any platform which supports RPCs and on which DRAC
> compiles cleanly would have any problems.
>
> If you don't know what DRAC is, see:
>
> http://mail.cc.umanitoba.ca/drac/
>
> (It's basically an implementation of POP-before-SMTP using an RPC
> daemon to store IP addresses of roamers as they authenticate, so
> that sendmail can check subsequent attempts to relay from those IPs
> and determine whether or not to accept the mail.)
>
> Thanks,
> Steve
>
> --
> tired of being an underappreciated functionary in a soulless machine?
> hesketh.com is hiring: <http://hesketh.com/careers/>
>
>
>
Date: Wed, 24 May 2000 22:17:10 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
On Wed, 24 May 2000, Mitch Vincent wrote:
> Have you guys noticed that a lot of mail clients try to send mail before
> they try to check it? I ran into horrible troubles after we started using
> POP3 -before-SMTP relay prevention. I haven't been able to totally verify
> this but some versions of Eudora, Outlook and Netscape mail seem to be givin
> my customers problems..
My copy of Eudora Light here on my iMac has a setting called "send on
check", which tries to send outbound mail first, before checking for new
mail. So, yes. If your users have that set they'll have trouble sending
the first time, but it should work the next time after that.
We don't have many complaints, though.
Steve
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
Date: Wed, 24 May 2000 22:57:47 -0400
From: Ken Hornstein <kenh at cmf.nrl.navy dot mil>
>Have you guys noticed that a lot of mail clients try to send mail before
>they try to check it? I ran into horrible troubles after we started using
>POP3 -before-SMTP relay prevention. I haven't been able to totally verify
>this but some versions of Eudora, Outlook and Netscape mail seem to be givin
>my customers problems..
I don't want to dismiss the DRAC work, as I believe it's certainly
useful in some cases, _but_ you might want to consider using SMTP
authentication, as two of the major MTA's (sendmail and qmail)
support SMTP AUTH, and I believe all of the MUAs you've listed do.
--Ken
Date: Thu, 25 May 2000 15:30:28 +1200 (NZST)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
On Wed, 24 May 2000, Steven Champeon wrote:
> My copy of Eudora Light here on my iMac has a setting called "send on
> check", which tries to send outbound mail first, before checking for new
> mail.
Um, no. Unless the Mac version is radically different from the PeeCee
version, it sends any queued mail _after_ checking.
AB
Date: Wed, 24 May 2000 23:26:45 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
On Thu, 25 May 2000, Alan Brown wrote:
> On Wed, 24 May 2000, Steven Champeon wrote:
> > My copy of Eudora Light here on my iMac has a setting called "send on
> > check", which tries to send outbound mail first, before checking for new
> > mail.
>
> Um, no. Unless the Mac version is radically different from the PeeCee
> version, it sends any queued mail _after_ checking.
If the "send on check" box is checked, Eudora Light 3.1.3 for the Mac
tries to send queued mail before trying to check POP. I just double
checked. I don't have access to the PeeCee version at the moment, but
I suspect it's the same.
Of course, if the "send on check" box *isn't* checked, it does POP
before trying to send any queued messages.
Steve
--
tired of being an underappreciated functionary in a soulless machine?
hesketh.com is hiring: <http://hesketh.com/careers/>
Date: Thu, 25 May 2000 15:52:08 +1200 (NZST)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
On Wed, 24 May 2000, Steven Champeon wrote:
> If the "send on check" box is checked, Eudora Light 3.1.3 for the Mac
> tries to send queued mail before trying to check POP. I just double
> checked. I don't have access to the PeeCee version at the moment, but
> I suspect it's the same.
It isn't. The PC version checks first.
AB
Date: Wed, 24 May 2000 21:08:51 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes
At 11:26 PM -0400 5/24/00, Steven Champeon wrote:
> If the "send on check" box is checked, Eudora Light 3.1.3 for the Mac
> tries to send queued mail before trying to check POP.
That's because you're using an old version. Current versions of
Eudora for both Windows and Mac do background sending and receiving
(so you can continue to read and edit while checking and sending) and
are careful to check before sending.
You can upgrade to the current version at <http://www.eudora.com>.
There is no more Eudora Light or Eudora Pro: it's all just Eudora
now, and it runs in one of three modes: light (fewer features), paid
(full-featured and you pay) or sponsored (full-featured and there's a
small ad window that doesn't flash or annoy you). You can switch
between the modes at will.
I also agree that it makes sense to include the drac patches, but
that SMTP AUTH is a better solution, and over time it will become the
norm. Already most clients and servers support it.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
f u cn rd ths, itn tyg h myxbl cd.
Date: Thu, 25 May 2000 17:31:57 +1200 (NZST)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: patch for DRAC support in qpopper 3.0.2 (includes autoconf hacks)
On Wed, 24 May 2000, Randall Gellens wrote:
> I also agree that it makes sense to include the drac patches, but
> that SMTP AUTH is a better solution, and over time it will become the
> norm. Already most clients and servers support it.
Not enough of them, unfortunately.
For the meantime, support for pop-before-smtp and DRAC should be built
into qpopper. I would suggest this is going to be required until at
least the end of 2002 as it will take that long or more to move people
across to up-to-date server and client software.
AB