The qpopper list archive ending on 11 May 2000
Topics covered in this issue include:
1. Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
Fergal Daly <fergal at esatclear dot ie>
Thu, 04 May 2000 23:23:47 +0100
2. FreeBSD 4.0 Compile Trouble.
"Mitch Vincent" <mitch at venux dot net>
Thu, 4 May 2000 21:46:21 -0400
3. FreeBSD troubles - nevermind!
"Mitch Vincent" <mitch at venux dot net>
Thu, 4 May 2000 21:49:28 -0400
4. Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Thu, 4 May 2000 22:37:17 -0700
5. Illegal seek
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Thu, 4 May 2000 23:38:51 -0700
6. I still have popper hang problems with tcpd
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Thu, 4 May 2000 23:47:59 -0700
7. Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
Alan Brown <alan at manawatu.gen dot nz>
Fri, 5 May 2000 17:17:55 +1200 (NZST)
8. Qpopper 3.01b2 on HPUX 10.20
"Erik Langeland" <erik.langeland at home dot com>
Fri, 5 May 2000 00:14:23 -0600
9. Problems with server mode
Javier Castillo <castillo at alhsys dot es>
Fri, 05 May 2000 09:47:19 +0000
10. Re: Qpopper 3.01b2 on HPUX 10.20
Joseph S D Yao <jsdy at cospo.osis dot gov>
Fri, 5 May 2000 10:24:58 -0400
11. Re: Illegal seek
Qpopper Support <qpopper at qualcomm dot com>
Fri, 5 May 2000 09:23:38 -0700
12. Enable APOP and USER/PASS
Adam Siegel <adam at buttonwoodinet dot com>
Fri, 05 May 2000 17:36:51 -0400
13. Re: Enable APOP and USER/PASS (fwd)
Dejan Ilic <dejan at knuten.liu dot se>
Fri, 5 May 2000 19:32:04 +0200 (MET DST)
14. Qpopper 3.0.1 (final) available
Qpopper Support <qpopper at qualcomm dot com>
Fri, 5 May 2000 17:22:09 -0700
15. Re: Qpopper 3.0.1 (final) available
"Lisa Casey" <lisa at jellico dot com>
Fri, 5 May 2000 20:50:13 -0400
16. Re: Illegal seek
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Fri, 5 May 2000 22:22:11 -0700
17. Re: Qpopper 3.0.1 (final) available
Peter Evans <peter at gol dot com>
Sat, 6 May 2000 13:21:30 +0900
18. Re: Enable APOP and USER/PASS
Georg Schwarz <schwarz at physik.tu-berlin dot de>
Sat, 6 May 2000 08:18:30 +0200 (MEST)
19. Re: standalone popper 3
Kevin Dabson <kevin at dnc-electronics dot com>
Sat, 6 May 2000 07:32:18 +0000 (GMT)
20. Qpopper / Sendmail question
"Mitch Vincent" <mitch at venux dot net>
Sat, 6 May 2000 12:57:21 -0400
21. AW: Qpopper / Sendmail question
"Martin Bene" <mb at sime dot com>
Sat, 6 May 2000 20:04:50 +0200
22. Re: AW: Qpopper / Sendmail question
"Robin" <krystal at devnull dot net>
Sat, 06 May 2000 11:49:38 PDT
23. Re: AW: Qpopper / Sendmail question
Forrest Aldrich <forrie at forrie dot com>
Sat, 06 May 2000 14:57:20 -0400
24. Re: AW: Qpopper / Sendmail question
"Mitch Vincent" <mitch at venux dot net>
Sat, 6 May 2000 16:38:07 -0400
25. Re: AW: Qpopper / Sendmail question
Forrest Aldrich <forrie at forrie dot com>
Sat, 06 May 2000 16:54:31 -0400
26. Re: AW: Qpopper / Sendmail question
"Mitch Vincent" <mitch at venux dot net>
Sat, 6 May 2000 17:27:35 -0400
27. Re: AW: Qpopper / Sendmail question
Steven Champeon <schampeo at hesketh dot com>
Sat, 6 May 2000 17:34:07 -0400 (EDT)
28. Re: AW: Qpopper / Sendmail question
Garlic <garlic at garlic dot com>
Sat, 06 May 2000 15:42:18 -0700
29. APOP & USER
Ted Parnefors <ted at mtv dot se>
Sun, 7 May 2000 22:51:02 +0200 (CEST)
30. Re: Qpopper 3.0.1 (final) available
Qpopper Support <qpopper at qualcomm dot com>
Sun, 7 May 2000 18:28:54 -0700
31. Re: Qpopper 3.01b2 on HPUX 10.20
Joseph S D Yao <jsdy at cospo.osis dot gov>
Mon, 8 May 2000 06:50:25 -0400
32. Filters...
Karyn McCambridge <karynm at afb dot net>
Mon, 08 May 2000 09:57:02 -0400
33. Re: Filters...
"Igor S. Livshits" <igorl at life.uiuc dot edu>
Mon, 8 May 2000 10:38:35 -0500
34. Re: Filters...
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Mon, 8 May 2000 11:23:19 -0700
35. Re: Filters...
Fergal Daly <fergal at esatclear dot ie>
Mon, 08 May 2000 17:45:27 +0100
36. Re: Filters...
Steven Champeon <schampeo at hesketh dot com>
Mon, 8 May 2000 12:46:51 -0400 (EDT)
37. RE: standalone popper 3
"John W. Keener" <jkeener at utsi dot com>
Mon, 8 May 2000 12:56:36 -0500
38. Re: Filters...
"Jerry O'Brien" <jobrien at cuttingedge dot net>
Mon, 8 May 2000 15:04:14 -0700
39. Re: Filters...
Steven Champeon <schampeo at hesketh dot com>
Mon, 8 May 2000 16:09:59 -0400 (EDT)
40. Re: Problems with server mode
Qpopper Support <qpopper at qualcomm dot com>
Mon, 8 May 2000 18:28:24 -0700
41. Re: Illegal seek
Qpopper Support <qpopper at qualcomm dot com>
Mon, 8 May 2000 18:31:07 -0700
42. Re: standalone popper 3
Qpopper Support <qpopper at qualcomm dot com>
Mon, 8 May 2000 18:32:50 -0700
43. Poppper 3.0.1 on RedHat Linux 6.2
"James Nelson" <james at digit.bloomnet dot com>
Mon, 8 May 2000 20:48:43 -0500
44. Re: Problems with server mode
Javier Castillo <castillo at alhsys dot es>
Tue, 09 May 2000 08:06:05 +0000
45. Re: Poppper 3.0.1 on RedHat Linux 6.2
"Kenneth Porter" <shiva at well dot com>
Tue, 09 May 2000 10:18:49 -0700
46. Re: Qpopper 3.0.1 (final) available
Joel Laing <joel at scripps dot edu>
Tue, 09 May 2000 14:09:25 -0700
47. popper.log file format??
Brad Groshok <bgroshok at odyssey.on dot ca>
Wed, 10 May 2000 21:51:22 -0400
48. Re: popper.log file format??
Eric Luyten <Eric.Luyten at vub.ac dot be>
Thu, 11 May 2000 10:42:05 +0200 (MET DST)
49. checking for mail spool directory... ERROR: Couln't locate the mail spool
"Keith Warno" <keith at HaggleWare dot com>
Thu, 11 May 2000 11:13:18 -0400
50. Re: checking for mail spool directory... ERROR: Couln't locate the mail spool
"Keith Warno" <keith at HaggleWare dot com>
Thu, 11 May 2000 11:37:09 -0400
Date: Thu, 04 May 2000 23:23:47 +0100
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
Without meaning to be rude, "Cutting Edge Systems" and Linux 1.2.13!!
At 00:38 05/05/00, Jerry O'Brien wrote:
>At first it felt like a SYN flood attack, but I have a bunch of hanging
>popper processes not in the SYN_RCVD state. I've been using 3.0 since it was
>announced with no problems until today. I'm running RH Linux kernel 1.2.13
>
>Client connections are hanging and the system is sluggish.
>
>Any ideas?
...
>Jerry O'Brien
>Cutting Edge Systems
From: "Mitch Vincent" <mitch at venux dot net>
Subject: FreeBSD 4.0 Compile Trouble.
Date: Thu, 4 May 2000 21:46:21 -0400
pop_pass.o: In function `pop_pass':
/usr/home/mitch/qpopper3.0/popper/pop_pass.c(.text+0xed): undefined
reference to `auth_user'
*** Error code 1
Stop in /usr/home/mitch/qpopper3.0/popper.
*** Error code 1
FreeBSD 4.0, I see the auth_user function, looks like it's only included if
AIX is defined..
Any suggestions?
Thanks!
-Mitch
From: "Mitch Vincent" <mitch at venux dot net>
Subject: FreeBSD troubles - nevermind!
Date: Thu, 4 May 2000 21:49:28 -0400
Oops guys, I'm an idiot.
-Mitch
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
Date: Thu, 4 May 2000 22:37:17 -0700
Yeah, Yeah, I know, but there's something to "if it ain't broke, don't fix
it" right? Plus, it's not the age of the knife, but the quality of the
steel.
Enough of that... I think it was that "I Love You" email overload that did
it. It still seems odd how it cleared up when I removed the tcpd wrapper,
though.
Jerry O'Brien
Cutting Edge Systems
----- Original Message -----
From: Fergal Daly <fergal at esatclear dot ie>
To: Jerry O'Brien <jobrien at cuttingedge dot net>; Subscribers of Qpopper
<qpopper at lists.pensive dot org>
Sent: Thursday, May 04, 2000 3:23 PM
Subject: Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
> Without meaning to be rude, "Cutting Edge Systems" and Linux 1.2.13!!
>
> At 00:38 05/05/00, Jerry O'Brien wrote:
> >At first it felt like a SYN flood attack, but I have a bunch of hanging
> >popper processes not in the SYN_RCVD state. I've been using 3.0 since it
was
> >announced with no problems until today. I'm running RH Linux kernel
1.2.13
> >
> >Client connections are hanging and the system is sluggish.
> >
> >Any ideas?
>
> ...
>
> >Jerry O'Brien
> >Cutting Edge Systems
>
>
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: Illegal seek
Date: Thu, 4 May 2000 23:38:51 -0700
What would cause this? The user name appears to be null. Client error? Is it
being handled OK?
May 4 22:38:42 TAIPAN popper[22297]: (null) at
dialup-brf-10.cuttingedge.net (208.35.151.10): -ERR
POP EOF or I/O error: Illegal seek (29) [popper.c:560]
Jerry O'Brien
Cutting Edge Systems
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: I still have popper hang problems with tcpd
Date: Thu, 4 May 2000 23:47:59 -0700
If I try to connect from a windows dial-up client, it says connecting, then
I see this in netstat:
tcp 0 0 208.35.150.2:110 208.35.151.1:1853 FIN_WAIT2
root
tcp 1 0 208.35.150.2:110 216.145.160.178:2536 CLOSE_WAIT
root
tcp 1 0 208.35.150.2:110 129.89.178.97:1795 CLOSE_WAIT
root
I'm the top one. There is a growing number of these CLOSE_WAIT sessions
that never seem to get cleaned up.
Any ideas? (ver 3.0)
Jerry O'Brien
Cutting Edge Systems
Date: Fri, 5 May 2000 17:17:55 +1200 (NZST)
From: Alan Brown <alan at manawatu.gen dot nz>
Subject: Re: qpopper 3.0 & 3.0.1b2 hanging in LAST_ACK & CLOSE_WAIT
On Thu, 4 May 2000, Jerry O'Brien wrote:
> Yeah, Yeah, I know, but there's something to "if it ain't broke, don't fix
> it" right? Plus, it's not the age of the knife, but the quality of the
> steel.
There are something like 100 rmeote user can get root holes in linux
1.2.13-based distributions - it's _very_ old and effectively swiss
cheese as it predates major Linux security efforts.
You really need to update that box, particularly if it's being used for
anything facing the world.
AB
From: "Erik Langeland" <erik.langeland at home dot com>
Subject: Qpopper 3.01b2 on HPUX 10.20
Date: Fri, 5 May 2000 00:14:23 -0600
I am getting compile errors with the latest beta (2) of Qpopper 3.01 (also
with the final 3.0) on HPUX 10.20. If anyone has successfully compiled it
on HPUX, I could use some pointers. The compile errors I get occur in
pop_dropcopy.c. Failing that, how does the HPUX-ported version of 2.53
work?
Thanks in advance.
Erik Langeland
Date: Fri, 05 May 2000 09:47:19 +0000
From: Javier Castillo <castillo at alhsys dot es>
Subject: Problems with server mode
Hi there,
I have compiled last version of qpopper with this options:
./configure --enable-specialauth --enable-servermode
--enable-debugging
--enable-auto-delete
My problem is: how I run popper on server mode?. Last version
2.53 has
-S flag, that activate server mode...
Thanks.
Date: Fri, 5 May 2000 10:24:58 -0400
From: Joseph S D Yao <jsdy at cospo.osis dot gov>
Subject: Re: Qpopper 3.01b2 on HPUX 10.20
On Fri, May 05, 2000 at 12:14:23AM -0600, Erik Langeland wrote:
> I am getting compile errors with the latest beta (2) of Qpopper 3.01 (also
> with the final 3.0) on HPUX 10.20. If anyone has successfully compiled it
> on HPUX, I could use some pointers. The compile errors I get occur in
> pop_dropcopy.c. Failing that, how does the HPUX-ported version of 2.53
> work?
>
> Thanks in advance.
>
> Erik Langeland
Compiled fine and running, using the HP-UX C compiler. What errors are
you getting?
--
Joe Yao jsdy at cospo.osis dot gov - Joseph S. D. Yao
COSPO/OSIS Computer Support EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.
Date: Fri, 5 May 2000 09:23:38 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Illegal seek
At 11:38 PM -0700 5/4/00, Jerry O'Brien wrote:
> What would cause this? The user name appears to be null. Client error? Is it
> being handled OK?
>
> May 4 22:38:42 TAIPAN popper[22297]: (null) at
> dialup-brf-10.cuttingedge.net (208.35.151.10): -ERR
> POP EOF or I/O error: Illegal seek (29) [popper.c:560]
>
> Jerry O'Brien
> Cutting Edge Systems
This is a misleading error message. By the time this message is
generated, we no longer know if what happened was an EOF (client
closed the connection) or an I/O error on the file descriptor mapped
to the client socket. If it is an EOF, the error number is
meaningless noise. If it is an I/O error, the error number says
which one. It generally is an EOF.
Qpopper does write more specific log entries when the even happens,
so if you check the log there should be a en entry saying "EOF" with
more details.
A null user name just means the user hadn't logged in yet.
Probably someone cancelled or got disconnected before logging in.
Date: Fri, 05 May 2000 17:36:51 -0400
From: Adam Siegel <adam at buttonwoodinet dot com>
Subject: Enable APOP and USER/PASS
I would like to have qpopper support both APOP and USER/PASS at the same time.
Any ideas???
Thanks,
Adam
Date: Fri, 5 May 2000 19:32:04 +0200 (MET DST)
From: Dejan Ilic <dejan at knuten.liu dot se>
Subject: Re: Enable APOP and USER/PASS (fwd)
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime at docserver.cac.washington dot edu for more info.
---559023410-1804928587-957547888=:16372
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.21.0005051931392.16372 at sture.lysator.liu dot se>
Sure, I've done it and sent the patch to the popper maintainters.
Don't know if they want to add it (or a variation) to the main source.
The Real Way of doing it is to have a Configure option as it changes the
default behavior. But the patch does what you want (checks user/pass even
if there is a APOP passwd in the database). We needed this as we have 22000
users and we want a "soft" transition to APOP from standard POP3. Now
change to APOP if the can/want, but still have the possibility to use
their favorite clients that only supports POP3 on other
places/computers). This way we keep the mobility also and we open the
possibility to upgrade the security by not transmiting the passwords in
cleartext.
This patch also adds the option to add a extra parameter to popauth
(the password) so that it can be used in scripts and not just with
interactive input.
Patch is against QP3.0.1b2 and strictly unofficial, for home use only,
on your own responsibility :-) But it works flawlessly AFAIK.
Dejan
On Fri, 5 May 2000, Adam Siegel wrote:
> I would like to have qpopper support both APOP and USER/PASS at the same time.
> Any ideas???
>
> Thanks,
> Adam
---559023410-1804928587-957547888=:16372
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="fixapop-30.diff"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.GSO.4.21.0005051931280.16372 at sture.lysator.liu dot se>
Content-Description: fixapop-30.diff
Content-Disposition: ATTACHMENT; FILENAME="fixapop-30.diff"
LS0tIHBvcHBlci9wb3BhdXRoLmMub3JpZwlTYXQgQXByIDIyIDAwOjI0OjE0
IDIwMDANCisrKyBwb3BwZXIvcG9wYXV0aC5jCVR1ZSBNYXkgIDIgMTU6MDE6
NDQgMjAwMA0KQEAgLTMyMiw2ICszMjIsNyBAQA0KICAgICBjaGFyICAgKmJw
LA0KICAgICAqY3AsDQogICAgICp1c2Vyc3cgPSBOVUxMLA0KKyAgICAqZ2l2
ZW5wYXNzd29yZCA9IE5VTEwsDQogICAgIGFwb3BmbGRbQlVGU0laXSwNCiAg
ICAgc2NyYW1mbGRbQlVGU0laXSwNCiAgICAgb3V0ZmxkW0JVRlNJWl0sDQpA
QCAtNDA1LDcgKzQwNiwxMiBAQA0KICAgICAgICAgICAgIGRlbGVzdyA9IDEs
IGluaXRzdyA9IDA7IGxpc3RzdyA9IDA7DQogICAgICAgICAgICAgaWYgKGFy
Z2MgPCAyIHx8IGFyZ3ZbMV1bMF0gPT0gJy0nKQ0KICAgICAgICAgICAgIGFk
aW9zICgibWlzc2luZyBhcmd1bWVudCB0byAlcyIsIGFyZ3ZbMF0pOw0KLSAg
ICAgICAgICAgIHVzZXJzdyA9IGFyZ3ZbMV07DQorCSAgICB1c2Vyc3cgPSBh
cmd2WzFdOw0KKwkgICAgaWYgKGFyZ2MgPT0gMyl7DQorCSAgICAgIGdpdmVu
cGFzc3dvcmQgPSBhcmd2WzJdOw0KKwkgICAgICBhcmdjLS07DQorCSAgICAg
IGFyZ3YrKzsNCisJICAgIH0NCiAgICAgICAgICAgICBhcmdjLS07DQogICAg
ICAgICAgICAgYXJndisrOw0KICAgICAgICAgICAgIGJyZWFrOw0KQEAgLTcz
NiwxNSArNzQyLDE4IEBADQogICAgICAgICAgICAgZmxhZ3MgPT0gMSA/ICJh
dCBsZWFzdCBvbmUgbm9uLW51bWVyaWMgY2hhcmFjdGVyIg0KICAgICAgICAg
ICAgIDogKHBhc3N0eXBlPyJhIGxvbmdlciBwYXNzIHBocmFzZSI6ImEgbG9u
Z2VyIHBhc3N3b3JkIikpOw0KIA0KLSAgICBpZiAoKChpID0gc3RybGVuKHN0
cm5jcHkoYnVmLA0KLSAgICAgICAgICAgICAgICAgZ2V0cGFzcyhwYXNzdHlw
ZT8iTmV3IHBhc3MgcGhyYXNlOiI6Ik5ldyBwYXNzd29yZDoiKSwgc2l6ZW9m
KGJ1ZikpKSkgPT0gMCkgfHwNCi0gICAgICAgICAgIXN0cm5jbXAoYnVmLCBv
YnVmLCBpKSkgew0KKyAgICBpZiAoZ2l2ZW5wYXNzd29yZCkNCisgICAgICBp
ID0gc3RybGVuKHN0cm5jcHkoYnVmLGdpdmVucGFzc3dvcmQsc2l6ZW9mKGJ1
ZikpKTsNCisgICAgZWxzZXsNCisgICAgICBpZiAoKChpID0gc3RybGVuKHN0
cm5jcHkoYnVmLA0KKwkgIGdldHBhc3MocGFzc3R5cGU/Ik5ldyBwYXNzIHBo
cmFzZToiOiJOZXcgcGFzc3dvcmQ6IiksIHNpemVvZihidWYpKSkpID09IDAp
IHx8DQorCSAgIXN0cm5jbXAoYnVmLCBvYnVmLCBpKSkgew0KICAgICAgICAg
ZnByaW50ZiAoc3RkZXJyLCBwYXNzdHlwZT8iUGFzcyBwaHJhc2UgdW5jaGFu
Z2VkLlxuIjoiUGFzc3dvcmQgdW5jaGFuZ2VkLlxuIik7DQogICAgICAgICBl
eGl0ICgxKTsNCisgICAgICB9DQogICAgIH0NCi0NCi0gICAgICAgIGlmICgg
IXN0cmNtcChidWYsIioiKSApDQotICAgICAgICAgIGJyZWFrOw0KKyAgICAg
IGlmICggIXN0cmNtcChidWYsIioiKSApDQorCWJyZWFrOw0KIA0KICAgICBm
bGFncyA9IDA7DQogICAgIGZvciAoY3AgPSBidWY7IGMgPSAqY3ArKzspDQpA
QCAtNzU5LDE0ICs3NjgsMTUgQEANCiAgICAgICAgICAgICBlbHNlDQogICAg
ICAgICAgICAgZmxhZ3MgfD0gODsNCiANCi0gICAgaWYgKChmbGFncyA+PSA3
ICYmIGkgPj0gNCkNCisgICAgaWYgKGdpdmVucGFzc3dvcmQgfHwNCisJKGZs
YWdzID49IDcgJiYgaSA+PSA0KQ0KICAgICAgICAgfHwgKChmbGFncyA9PSAy
IHx8IGZsYWdzID09IDQpICYmIGkgPj0gNikNCiAgICAgICAgIHx8ICgoZmxh
Z3MgPT0gMyB8fCBmbGFncyA9PSA1IHx8IGZsYWdzID09IDYpICYmIGkgPj0g
NSkpDQogICAgICAgICBicmVhazsNCiAgICAgfQ0KIA0KICAgICANCi0gICAg
aWYgKHN0cmNtcChidWYsDQorICAgIGlmICghZ2l2ZW5wYXNzd29yZCAmJiBz
dHJjbXAoYnVmLA0KICAgICAgICAgICBnZXRwYXNzKHBhc3N0eXBlPyJSZXR5
cGUgbmV3IHBhc3MgcGhyYXNlOiI6IlJldHlwZSBuZXcgcGFzc3dvcmQ6Iikp
KSB7DQogICAgIGZwcmludGYgKHN0ZGVyciwNCiAgICAgIHBhc3N0eXBlPyJN
aXNtYXRjaCAtLSBwYXNzIHBocmFzZSB1bmNoYW5nZWQuXG4iOiJNaXNtYXRj
aCAtLSBwYXNzd29yZCB1bmNoYW5nZWQuXG4iKTsNCi0tLSBwb3BwZXIvcG9w
X3VzZXIuYy5vcmlnCVR1ZSBNYXkgIDIgMTQ6NDI6MDggMjAwMA0KKysrIHBv
cHBlci9wb3BfdXNlci5jCVR1ZSBNYXkgIDIgMTQ6NDY6MzIgMjAwMA0KQEAg
LTIyOSw2ICsyMjksNyBAQA0KICNlbmRpZg0KICAgICAgICAgKHZvaWQpIGNs
b3NlKGZpZCk7DQogDQorI2lmZGVmIE5PX0NPTVBVTFNBUllfQVBPUF9TQ1JB
TQ0KICAgICAgICAgaWYgKCh2YWx1ZS5kcHRyICE9IE5VTEwpICYmDQogICAg
ICAgICAgICAgICAgICgqdmFsdWUuZHB0ciAgIT0gMCAgIHx8DQogICAgICAg
ICAgICAgICAgICggdmFsdWUuZHNpemUgPj0gKGk9c3RybGVuKHZhbHVlLmRw
dHIpKzIpDQpAQCAtMjM4LDYgKzIzOSw3IEBADQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICJzdWNoIGFzIEFVVEggU0NSQU0tTUQ1
IG9yIEFQT1AgdG8gY29ubmVjdCAiDQogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICJ0byB0aGlzIHNlcnZlciIgKSApOw0KICAgICAg
ICAgfQ0KKyNlbmRpZiAvKiBOT19DT01QVUxTQVJZX0FQT1BfU0NSQU0gKi8N
CiAgICAgfQ0KICNlbmRpZiAvKiBBVVRIT04gKi8NCiANCg==
---559023410-1804928587-957547888=:16372--
Date: Fri, 5 May 2000 17:22:09 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Qpopper 3.0.1 (final) available
Qpopper 3.0.1 (final) 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.1b2 to 3.0.1 (final)
-------------------------------------
1. Improved log entries for I/O errors on client input stream.
2. Fixed encode64/decode64 prototypes (thanks to J.J.Bailey).
3. Fixed crash in popauth on OpenBSD.
From: "Lisa Casey" <lisa at jellico dot com>
Subject: Re: Qpopper 3.0.1 (final) available
Date: Fri, 5 May 2000 20:50:13 -0400
Hi,
I'm downloaded and installed what was referred to as a candidate release of
qpopper 3.0.1. Whats the difference between the candidate release and the
3.0.1b2 release mentioned below? Besides the fact that the b2 is a beta and
(I think) the candidate is not. I didn't see anything mentioned about a
candidate release in the release notes on the FTP site. Is there (in your
opinion) a compelling reason to upgrade from the candidate release to the
final release?
Thanks for the info,
Lisa Casey, Webmaster
Interstate 2000, Inc.
lisa at jellico dot com
----- Original Message -----
From: Qpopper Support <qpopper at qualcomm dot com>
To: Subscribers of Qpopper <qpopper at lists.pensive dot org>;
<qpopper-announce at qualcomm dot com>
Cc: <qpopper at qualcomm dot com>
Sent: Friday, May 05, 2000 8:22 PM
Subject: Qpopper 3.0.1 (final) available
> Qpopper 3.0.1 (final) 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.1b2 to 3.0.1 (final)
> -------------------------------------
>
> 1. Improved log entries for I/O errors on client input stream.
> 2. Fixed encode64/decode64 prototypes (thanks to J.J.Bailey).
> 3. Fixed crash in popauth on OpenBSD.
>
>
>
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: Re: Illegal seek
Date: Fri, 5 May 2000 22:22:11 -0700
No APOP, but the illegal seek comes in every few minutes and is not tied to
a single IP or NAS.
JO
----- Original Message -----
From: Spencer Yost <yostsw at newidea.atis dot net>
To: <jobrien at cuttingedge dot net>
Sent: Friday, May 05, 2000 4:09 AM
Subject: Re: Illegal seek
> If you have APOP enabled, Outlook Express clients will cause Qpopper to
> generate this message.
>
> Just a thought,
>
> Spencer Yost
> Owner, ATIS
> Plow the Net!
> http://www.atis.net
>
> *********** REPLY SEPARATOR ***********
>
> On 5/4/00 at 11:38 PM Jerry O'Brien wrote:
>
> >What would cause this? The user name appears to be null. Client error? Is
> it
> >being handled OK?
> >
> >May 4 22:38:42 TAIPAN popper[22297]: (null) at
> >dialup-brf-10.cuttingedge.net (208.35.151.10): -ERR
> >POP EOF or I/O error: Illegal seek (29) [popper.c:560]
> >
> >Jerry O'Brien
> >Cutting Edge Systems
>
>
>
Date: Sat, 6 May 2000 13:21:30 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: Qpopper 3.0.1 (final) available
Qpopper Support (qpopper at qualcomm dot com) wrote:
> Qpopper 3.0.1 (final) is available at
> <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Perhaps its just my compiler, or OS, but qpopper3 isnt really ready for
release yet. (Sorry I am late, not enough hours in the day.)
irix 6.5.blah, irix c compiler.
Errors that snuck through:
cc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_msg.c -o pop_msg.o
"pop_msg.c", line 108: warning(1185): enumerated type mixed with another type
pop_log ( p, LOG_NOTICE, fn, ln,
[this one looks like a typo. everywhere else, its POP_NOTICE]
cc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_pass.c -o pop_pass.o
"pop_pass.c", line 984: warning(1177): argument is incompatible with formal
parameter
if ( ( p->kerberos ? auth_user_kerberos ( p, pw )
^
[
int
auth_user_kerberos (p, pw)
POP * p;
struct passwd *pw;
but in pop_pass, pw is defined as:
struct passwd pw, *pwp;
so this is probably a typo too.
]
cc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_send.c -o pop_send.o
"pop_send.c", line 440: warning(1116): non-void function "pop_sendline"
(declared at line 411) should return a value
}
[usual default type is "int" not "void" complaint]
cc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_updt.c -o pop_updt.o
"pop_updt.c", line 86: warning(1047): macro redefined differently
#define BBSIZE 4096
^
[ odd one. Maybe the system is defining this one, ^_^;]
cc -c -I.. -I.. -I. -I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DIRIX -DUNIX popper.c -o popper.o
"popper.c", line 136: warning(1048): cast between pointer-to-object and
pointer-to-function
if ( signal (SIGHUP, VOIDSTAR catchSIGHUP ) == SIG_ERR ||
^
"popper.c", line 136: warning(1164): argument of type "void *" is incompatible
with parameter of type "void (*)()"
if ( signal (SIGHUP, VOIDSTAR catchSIGHUP ) == SIG_ERR ||
[times several]
The mime/mangler stuff is one big error according to the compiler.
nested comments, enumerated type mixed with another type.
operand types are incompatible, possible use of "=" where "==" was
intended, etc ^^;
in common:
cc -c -I.. -I. -I.. -I../popper -g -DHAVE_CONFIG_H -DIRIX -DUNIX maillock.c -o maillock.o
"maillock.c", line 404: warning(1172): subscript out of range
buf[BUF_SIZE] = '\0';
then at link time, the compiler moans and groans about ...
ld32: WARNING 15: multiply defined:(s) in pop_dele.o and pop_get_command.o (2nd definition ignored).
ld32: WARNING 15: multiply defined:(size) in pop_dele.o and pop_get_command.o (2nd definition ignored).
ld32: WARNING 15: multiply defined:(stream) in pop_dele.o and pop_get_command.o (2nd definition ignored).
This comes from stuff leaking out of popper.h
at line 506.
char *s;
int size;
FILE *stream;
P
----*
--
Remember The 5 K's.
The Justified Agents of Munya-munya-muuuu ...
Subject: Re: Enable APOP and USER/PASS
Date: Sat, 6 May 2000 08:18:30 +0200 (MEST)
From: Georg Schwarz <schwarz at physik.tu-berlin dot de>
> I would like to have qpopper support both APOP and USER/PASS at the same =
time.
> Any ideas???
>
I've built patches which can be configured to do just that.
--
Georg Schwarz schwarz at physik.tu-berlin dot de
Institut für Theoretische Physik Tel. +49 30 314-24254, FAX -21130
Technische Universität Berlin http://home.pages.de/~schwarz/
Sekr. PN 7-1, Hardenbergstr. 36, D-10623 Berlin IRC: kuroi
Date: Sat, 6 May 2000 07:32:18 +0000 (GMT)
From: Kevin Dabson <kevin at dnc-electronics dot com>
Subject: Re: standalone popper 3
Thanks for help regarding main.c bug.
Had to take out equal sign.
Now have qpopper 3 running in standalone
on redhat 6.1 without inetd.
Do have one problem though.
When I run popper of linux command line i can
no longer use it!. I have to press Ctrl C or Z
to exit it which quits program.
Does anybody know how to run popper direct of
command line or rc.local and carry on using system?
Some bash script perhaps.
KD
From: "Mitch Vincent" <mitch at venux dot net>
Subject: Qpopper / Sendmail question
Date: Sat, 6 May 2000 12:57:21 -0400
This is more for the Qpopper hacker than anything, just a few quick
programming questions..
Sendmail carries with it makemap, something to make it's database files. If
I'm not mistaken, sendmail uses Berkeley DB files for this (I'm talking
specifically about writing a popauth file)..
Now, using the sendmail hack 'popauth', it will look at a database of
allowed IPs (for lack of a better word). there are some perl scripts and
such to parse logs and add IPs that have successfully authenticated into a
plain text file, then call makemap but I've found that it is too slow. Often
times the log parser doesn't parse the log and add the right IP until after
the person has tried to send mail, causing an error..
My solution is just to take the parser out of the loop and make qpopper add
the IP to the database once authentication was successful... I've done this
with the flat-file and I *guess* I could execute makemap from within qpopper
but damn that's messy (and potentially dangerous). If I wanted to write to
the popauth.db file directly, I'll have to get to know the Berkeley DB and
any formatting involved in turning a file like :
10.0.0.1
10.0.0.2
..into a sendmail-readable database file..
Basically, I need to know what the makemap does and code that into my little
qpopper hack..
Am I overstating this? Is it a lot easier than I think ? :-)
Any and all pointers are appreciated, thanks!!
-Mitch
From: "Martin Bene" <mb at sime dot com>
Subject: AW: Qpopper / Sendmail question
Date: Sat, 6 May 2000 20:04:50 +0200
This is a multi-part message in MIME format.
------=_NextPart_000_000B_01BFB796.5624E860
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hi Mitch,
> Basically, I need to know what the makemap does and code that
> into my little
> qpopper hack..
>
> Am I overstating this? Is it a lot easier than I think ? :-)
I'm currently doing it this way; to make it work you need:
1) the patch to make qpopper write the popauth.db file directly and
2) a small program to remove old entries from the db file; you only want to
enable access from an external address for a certain time after all. this
little program should be run from a cronjob.
Included Files:
1) qpopper/popper/auth_sendmail.c -> module that logs pop authentications
directly to .db file.
2) popusers/popusers.c -> program specified in (2). Compile using
gcc -o popusers popusers.c -ldb
start without parameters for usage notes.
How to use it:
1) put a prototype in popper.h:
extern void auth_sendmail(char*);
2) put a call to the function in pop_pass.c, pop_auth.c and pop_apop.c,
right before pop_dropcopy:
auth_sendmail(p->ipaddr);
if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
(need to put it before pop_dropcopy as that call will also also drop
privileges)
3) if the -ldb is not in your makefile, add it
LIBS = -lgdbm -ldb
Hope this helps you,
Martin
"you have moved your mouse, please reboot to make this change take effect"
--------------------------------------------------
Martin Bene vox: +43-316-813824
simon media fax: +43-316-813824-6
Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
8010 Graz, Austria
--------------------------------------------------
finger mb at mail.sime dot com for PGP public key
------=_NextPart_000_000B_01BFB796.5624E860
Content-Type: application/x-gzip;
name="qpopper_popauth.tar.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="qpopper_popauth.tar.gz"
H4sIAK1cFDkAA+0YaW/aSLRfw694oWpqpybYNKFSKJV60DbaKKlI9lIaIWOPYVSwXXtIN93mv+97
c2DjkITsVlutlvkAc7x59zVOk3SWsyxvpnqyEzz43sNz3fbuLjwAGm7lH6C96+3hb3vPc9tPWy2c
e0/dvd0H4H53TpaMWS78DOBBliTiNri7zv+j4yGPg8ksZPA8HO6MX9SKdS5CnlS2LvNmxCdscVfw
qdypBWPU5HaaJaPMn3ZqtYuEhzDL/REDy4Y/awBRmvFYRBbiZlnm1NXhPjzK4awx4bk4/3bWoK0p
j2eC5ecf47qjEdqdJQjQfeS9faBfCJJYsFhAEoH2Zwh94Q/9nCGmmzDoEXE2CfN94KkfhhnLcwdI
NOCxYQdyFJoRapgkIx7fgrMsxT5kbJpcMEDWMo5okgnCgRizAnOUJdNrvLI/uLA8nF5pZU59ZMZC
WuBno8ABpfFtXFyQgvEKneXC4R1avHkFsB0OO3J6Chf+ZMbM4hO77Gj4SRJ8IrPiGndenfZ7vYOj
t8cw5HGUdMBAsdiJQrojqebCO2u5rnvu4LSlpnRIKhsIEJ4jWgohBpjgAf5lswCZ+8KF9AUzlAyx
P5WsXUmAYMzys3PoSsCHIYt4zODlu97Jr5g49N06arjulM4PD05OCcAzAOQSEgLg6OfDQ5pdEQ0l
0AYd51+QiOvM2UGcZmtjmoQM/0g7NJ1Lvh2kqF1cNbfhdTKd+nGI3ocMRDPxFbabeKJdFhGRac5I
M7hL8ydPOmoWNBpKPV/GqHqwaAtegGtr5QRp+Tbt8AisbdruwuPGY3uuRDIOd+CiY9bEv1lc4KLh
mVWUZJY6LtTMz3ek8oE/eWKXLMPJn7NgmlpbQXrmkZ0rV2xiRTK8oQih1+FsmDH/E86uNCrzH6RK
eBoKFVgXZYpoR382wVgmLNWYamCOmMWf4uRLDEkqeELR5wSpLWnKRGLZC/QDjCTtFPu0P7e31yns
fP2GdLPFCwqK9C+t9Bxa8O2bMo53jvYpmWRDqrnC+5TnmDlGdGM2pfwkEkx5xL82sGJ8UYwr+snz
wI8jS5Ny6o/CurMlmbcLnmjZ7bo3kucxRr7MHn+Q4GXS3s2ktY+CnkvPLXSlTbsho0BbU7o+hTCb
oB6NXeeIC1+Yuz+Ug+IKI7OmRLKU6kmora1CQLtWQViC3SzBbl6H3ZBhj7zymAuO6vjKYCgyRuk9
ShTrw68sS8DaknkP3R1hksiSK9vuGN6U9rV4lBjQQY4H/Te/9pVAJl/g9uHx658Gvd+UcCWllG4d
Hx3+vvzeyfuSUpDx4xTLhWLZ1AnFdjjEK/ibEIBVbzIRNLFQTIqWLhzWHZnN3LbrOm9eDWSOd5Sg
c0VuhkP7T6gt86C3bDzBijVkHIiKqU+Y6PAYc0q5RJfKlmIfpOjyBMUgMYGqjXEXZUNdglASIrBU
CgNTd5S6vx0PXvd7L0+lVLbd7Ta8IptUJZB8StwUiAbVjpIE2VIJz4rCbjhsvIhCC5VhP3fvQjhi
gvBJ1kOWBxrhdlNdWqqeBQWZkCAtRMTWXBWOcQj7LiYI0HBRmOY+1I1xcsFS7EuyZDYaV7xsXqg2
SUE5+4wacrawi3C2ZF/h9AdHvd9OS8xiw4DmRIgdiqSOFBH3Xui4wgYCgXGjW9ooShXWnjhIL2nX
IRzEjYPQdqmWYSvUxa0Of+7tdWT5oq6En3cfw+MCj9r56M63FGOS65tYa1VZay1lreUoLNeYo5YI
14t0hYdkqT+y3AJQJXhCVX80mWF2R1LzSk5syexmz4uk9oA6JnHxKKREThqyhNfAi822u3C5SIeY
GgsY7DNUFitXX4O4r3rVO/ErCuQMIZvMnYES75Lq3ZOOKttg8lRVgcjg5UqiHbJWxh1MkpxRMGLV
LUXjUtcuXVXXTCitdvmq9qMfYz9gfMb0ivp4uuNGgddUi6Y/E+NBzuKQEvA//yBwx/t/9+mzXYBn
brvttVu77jPs4Pee7a7f///KKJ7x+HaO+GilbwDiMmV5FRIDXt+O4P3LX3qDk9P+wdG7k8H72kOo
wKnL6GA8KnDUlfftjOu1W75KLP0EQbsY1HFyw5cJ+Xhe8GpMEfItpx771x7PxTt21Yd09dm8/NUc
ENozT7+VPxx/wGx07RkOtSXN6tjPx/fqVRevh7Pp9FJ+uVDv8FnGFhGljsaRyvvUEiH0YJKM6Aw5
HXzoHxz3D05/d973+j2nfoJxIxaV6sgGq2gcZLdmdxQh08JKQf5OB7uk61ull71dClWY8G1pWsMF
kqgrVSukc9m6VGQM1RdX2lvVQ95ETFOTCrje0BoV/ZsN8ipqqbbLi6wXjeZCoTabhZaouK7SYq/C
EjbclY5bNoJlq92HLaNf1XpHoaOfbLIzUl38HZZVzB2S0W4z7JL+vkxqdQWYZv+fSCx/TFPdVSmw
M9+kPNBFz8fUZRkgjUx0ZftKX9P0Tq4bPZnYdAsr9FnRG3flcXm3TKSAM5nnztzjyzby4MM+Rq4v
KH5FYlQiI3f+ZCgjN8ZY6DDTmag+ZVx7s3tPv8z/Hkf6gwmsJvZrNC1RMdlT+9dKDfNqWTDQFFbI
glf347kSE0Vmq7Tq34nvIhfexP3/st1fj/VYj/VYj/VYj/VYj/VYj//x+Asa2ceJACgAAA==
------=_NextPart_000_000B_01BFB796.5624E860--
Subject: Re: AW: Qpopper / Sendmail question
Date: Sat, 06 May 2000 11:49:38 PDT
From: "Robin" <krystal at devnull dot net>
Could we get this merged in as an optional feature in Qpopper? Our
coop has several users on dynamic IP dialups outside our network and
it'd be nice not to have to modify the source every time I upgrade the
POP server.
-robin
>Hi Mitch,
>
>
>> Basically, I need to know what the makemap does and code that
>> into my little
>> qpopper hack..
>>
>> Am I overstating this? Is it a lot easier than I think ? :-)
>
>I'm currently doing it this way; to make it work you need:
>
>1) the patch to make qpopper write the popauth.db file directly and
>2) a small program to remove old entries from the db file; you only
want to
>enable access from an external address for a certain time after all.
this
>little program should be run from a cronjob.
>
>Included Files:
>1) qpopper/popper/auth_sendmail.c -> module that logs pop
authentications
>directly to .db file.
>
>2) popusers/popusers.c -> program specified in (2). Compile using
>gcc -o popusers popusers.c -ldb
>start without parameters for usage notes.
>
>How to use it:
>1) put a prototype in popper.h:
>extern void auth_sendmail(char*);
>
>2) put a call to the function in pop_pass.c, pop_auth.c and
pop_apop.c,
>right before pop_dropcopy:
>
>auth_sendmail(p->ipaddr);
>if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
>
>(need to put it before pop_dropcopy as that call will also also drop
>privileges)
>
>3) if the -ldb is not in your makefile, add it
>
>LIBS = -lgdbm -ldb
>
>Hope this helps you,
>
>Martin
>
>"you have moved your mouse, please reboot to make this change take
effect"
>--------------------------------------------------
> Martin Bene vox: +43-316-813824
> simon media fax: +43-316-813824-6
> Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> 8010 Graz, Austria
>--------------------------------------------------
>finger mb at mail.sime dot com for PGP public key
>
Turning and turning in the widening gyre
The falcon cannot hear the falconer;
Things fall apart; the centre cannot hold;
Mere anarchy is loosed upon the world.
Date: Sat, 06 May 2000 14:57:20 -0400
From: Forrest Aldrich <forrie at forrie dot com>
Subject: Re: AW: Qpopper / Sendmail question
I suggest looking at DRAC:
http://mail.cc.umanitoba.ca/drac/index.html
For which I've already submitted patches to qpopper -- I understand those
will be included in the next release.
_F
At 11:49 AM 5/6/00 -0700, Robin wrote:
>Could we get this merged in as an optional feature in Qpopper? Our
>coop has several users on dynamic IP dialups outside our network and
>it'd be nice not to have to modify the source every time I upgrade the
>POP server.
>
>-robin
>
> >Hi Mitch,
> >
> >
> >> Basically, I need to know what the makemap does and code that
> >> into my little
> >> qpopper hack..
> >>
> >> Am I overstating this? Is it a lot easier than I think ? :-)
> >
> >I'm currently doing it this way; to make it work you need:
> >
> >1) the patch to make qpopper write the popauth.db file directly and
> >2) a small program to remove old entries from the db file; you only
>want to
> >enable access from an external address for a certain time after all.
>this
> >little program should be run from a cronjob.
> >
> >Included Files:
> >1) qpopper/popper/auth_sendmail.c -> module that logs pop
>authentications
> >directly to .db file.
> >
> >2) popusers/popusers.c -> program specified in (2). Compile using
> >gcc -o popusers popusers.c -ldb
> >start without parameters for usage notes.
> >
> >How to use it:
> >1) put a prototype in popper.h:
> >extern void auth_sendmail(char*);
> >
> >2) put a call to the function in pop_pass.c, pop_auth.c and
>pop_apop.c,
> >right before pop_dropcopy:
> >
> >auth_sendmail(p->ipaddr);
> >if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
> >
> >(need to put it before pop_dropcopy as that call will also also drop
> >privileges)
> >
> >3) if the -ldb is not in your makefile, add it
> >
> >LIBS = -lgdbm -ldb
> >
> >Hope this helps you,
> >
> >Martin
> >
> >"you have moved your mouse, please reboot to make this change take
>effect"
> >--------------------------------------------------
> > Martin Bene vox: +43-316-813824
> > simon media fax: +43-316-813824-6
> > Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> > 8010 Graz, Austria
> >--------------------------------------------------
> >finger mb at mail.sime dot com for PGP public key
> >
>
>Turning and turning in the widening gyre
>The falcon cannot hear the falconer;
>Things fall apart; the centre cannot hold;
>Mere anarchy is loosed upon the world.
From: "Mitch Vincent" <mitch at venux dot net>
Subject: Re: AW: Qpopper / Sendmail question
Date: Sat, 6 May 2000 16:38:07 -0400
I looked at this and it does looks like it works, however the way it works I
don't like too much.
----- Original Message -----
From: Forrest Aldrich <forrie at forrie dot com>
To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
Sent: Saturday, May 06, 2000 2:57 PM
Subject: Re: AW: Qpopper / Sendmail question
> I suggest looking at DRAC:
>
> http://mail.cc.umanitoba.ca/drac/index.html
>
> For which I've already submitted patches to qpopper -- I understand those
> will be included in the next release.
>
>
> _F
>
>
> At 11:49 AM 5/6/00 -0700, Robin wrote:
> >Could we get this merged in as an optional feature in Qpopper? Our
> >coop has several users on dynamic IP dialups outside our network and
> >it'd be nice not to have to modify the source every time I upgrade the
> >POP server.
> >
> >-robin
> >
> > >Hi Mitch,
> > >
> > >
> > >> Basically, I need to know what the makemap does and code that
> > >> into my little
> > >> qpopper hack..
> > >>
> > >> Am I overstating this? Is it a lot easier than I think ? :-)
> > >
> > >I'm currently doing it this way; to make it work you need:
> > >
> > >1) the patch to make qpopper write the popauth.db file directly and
> > >2) a small program to remove old entries from the db file; you only
> >want to
> > >enable access from an external address for a certain time after all.
> >this
> > >little program should be run from a cronjob.
> > >
> > >Included Files:
> > >1) qpopper/popper/auth_sendmail.c -> module that logs pop
> >authentications
> > >directly to .db file.
> > >
> > >2) popusers/popusers.c -> program specified in (2). Compile using
> > >gcc -o popusers popusers.c -ldb
> > >start without parameters for usage notes.
> > >
> > >How to use it:
> > >1) put a prototype in popper.h:
> > >extern void auth_sendmail(char*);
> > >
> > >2) put a call to the function in pop_pass.c, pop_auth.c and
> >pop_apop.c,
> > >right before pop_dropcopy:
> > >
> > >auth_sendmail(p->ipaddr);
> > >if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
> > >
> > >(need to put it before pop_dropcopy as that call will also also drop
> > >privileges)
> > >
> > >3) if the -ldb is not in your makefile, add it
> > >
> > >LIBS = -lgdbm -ldb
> > >
> > >Hope this helps you,
> > >
> > >Martin
> > >
> > >"you have moved your mouse, please reboot to make this change take
> >effect"
> > >--------------------------------------------------
> > > Martin Bene vox: +43-316-813824
> > > simon media fax: +43-316-813824-6
> > > Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> > > 8010 Graz, Austria
> > >--------------------------------------------------
> > >finger mb at mail.sime dot com for PGP public key
> > >
> >
> >Turning and turning in the widening gyre
> >The falcon cannot hear the falconer;
> >Things fall apart; the centre cannot hold;
> >Mere anarchy is loosed upon the world.
>
>
Date: Sat, 06 May 2000 16:54:31 -0400
From: Forrest Aldrich <forrie at forrie dot com>
Subject: Re: AW: Qpopper / Sendmail question
FWIW, we've been using DRAC on an old FreeBSD-2.2.8 system that has been
delivering 1000s of messages for the last few months with NO problems.
_F
At 04:38 PM 5/6/00 -0400, Mitch Vincent wrote:
>I looked at this and it does looks like it works, however the way it works I
>don't like too much.
>
>
>----- Original Message -----
>From: Forrest Aldrich <forrie at forrie dot com>
>To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
>Sent: Saturday, May 06, 2000 2:57 PM
>Subject: Re: AW: Qpopper / Sendmail question
>
>
> > I suggest looking at DRAC:
> >
> > http://mail.cc.umanitoba.ca/drac/index.html
> >
> > For which I've already submitted patches to qpopper -- I understand those
> > will be included in the next release.
> >
> >
> > _F
> >
> >
> > At 11:49 AM 5/6/00 -0700, Robin wrote:
> > >Could we get this merged in as an optional feature in Qpopper? Our
> > >coop has several users on dynamic IP dialups outside our network and
> > >it'd be nice not to have to modify the source every time I upgrade the
> > >POP server.
> > >
> > >-robin
> > >
> > > >Hi Mitch,
> > > >
> > > >
> > > >> Basically, I need to know what the makemap does and code that
> > > >> into my little
> > > >> qpopper hack..
> > > >>
> > > >> Am I overstating this? Is it a lot easier than I think ? :-)
> > > >
> > > >I'm currently doing it this way; to make it work you need:
> > > >
> > > >1) the patch to make qpopper write the popauth.db file directly and
> > > >2) a small program to remove old entries from the db file; you only
> > >want to
> > > >enable access from an external address for a certain time after all.
> > >this
> > > >little program should be run from a cronjob.
> > > >
> > > >Included Files:
> > > >1) qpopper/popper/auth_sendmail.c -> module that logs pop
> > >authentications
> > > >directly to .db file.
> > > >
> > > >2) popusers/popusers.c -> program specified in (2). Compile using
> > > >gcc -o popusers popusers.c -ldb
> > > >start without parameters for usage notes.
> > > >
> > > >How to use it:
> > > >1) put a prototype in popper.h:
> > > >extern void auth_sendmail(char*);
> > > >
> > > >2) put a call to the function in pop_pass.c, pop_auth.c and
> > >pop_apop.c,
> > > >right before pop_dropcopy:
> > > >
> > > >auth_sendmail(p->ipaddr);
> > > >if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
> > > >
> > > >(need to put it before pop_dropcopy as that call will also also drop
> > > >privileges)
> > > >
> > > >3) if the -ldb is not in your makefile, add it
> > > >
> > > >LIBS = -lgdbm -ldb
> > > >
> > > >Hope this helps you,
> > > >
> > > >Martin
> > > >
> > > >"you have moved your mouse, please reboot to make this change take
> > >effect"
> > > >--------------------------------------------------
> > > > Martin Bene vox: +43-316-813824
> > > > simon media fax: +43-316-813824-6
> > > > Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> > > > 8010 Graz, Austria
> > > >--------------------------------------------------
> > > >finger mb at mail.sime dot com for PGP public key
> > > >
> > >
> > >Turning and turning in the widening gyre
> > >The falcon cannot hear the falconer;
> > >Things fall apart; the centre cannot hold;
> > >Mere anarchy is loosed upon the world.
> >
> >
From: "Mitch Vincent" <mitch at venux dot net>
Subject: Re: AW: Qpopper / Sendmail question
Date: Sat, 6 May 2000 17:27:35 -0400
I'm sorry, I never meant to imply there were any problems with it, it's just
that I *personally* didn't like the way it was being done.
I'm sure DRAC is a workable solution...
-Mitch
----- Original Message -----
From: Forrest Aldrich <forrie at forrie dot com>
To: Mitch Vincent <mitch at venux dot net>; Subscribers of Qpopper
<qpopper at lists.pensive dot org>
Sent: Saturday, May 06, 2000 4:54 PM
Subject: Re: AW: Qpopper / Sendmail question
> FWIW, we've been using DRAC on an old FreeBSD-2.2.8 system that has been
> delivering 1000s of messages for the last few months with NO problems.
>
>
> _F
>
>
> At 04:38 PM 5/6/00 -0400, Mitch Vincent wrote:
> >I looked at this and it does looks like it works, however the way it
works I
> >don't like too much.
> >
> >
> >----- Original Message -----
> >From: Forrest Aldrich <forrie at forrie dot com>
> >To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
> >Sent: Saturday, May 06, 2000 2:57 PM
> >Subject: Re: AW: Qpopper / Sendmail question
> >
> >
> > > I suggest looking at DRAC:
> > >
> > > http://mail.cc.umanitoba.ca/drac/index.html
> > >
> > > For which I've already submitted patches to qpopper -- I understand
those
> > > will be included in the next release.
> > >
> > >
> > > _F
> > >
> > >
> > > At 11:49 AM 5/6/00 -0700, Robin wrote:
> > > >Could we get this merged in as an optional feature in Qpopper? Our
> > > >coop has several users on dynamic IP dialups outside our network and
> > > >it'd be nice not to have to modify the source every time I upgrade
the
> > > >POP server.
> > > >
> > > >-robin
> > > >
> > > > >Hi Mitch,
> > > > >
> > > > >
> > > > >> Basically, I need to know what the makemap does and code that
> > > > >> into my little
> > > > >> qpopper hack..
> > > > >>
> > > > >> Am I overstating this? Is it a lot easier than I think ? :-)
> > > > >
> > > > >I'm currently doing it this way; to make it work you need:
> > > > >
> > > > >1) the patch to make qpopper write the popauth.db file directly and
> > > > >2) a small program to remove old entries from the db file; you only
> > > >want to
> > > > >enable access from an external address for a certain time after
all.
> > > >this
> > > > >little program should be run from a cronjob.
> > > > >
> > > > >Included Files:
> > > > >1) qpopper/popper/auth_sendmail.c -> module that logs pop
> > > >authentications
> > > > >directly to .db file.
> > > > >
> > > > >2) popusers/popusers.c -> program specified in (2). Compile using
> > > > >gcc -o popusers popusers.c -ldb
> > > > >start without parameters for usage notes.
> > > > >
> > > > >How to use it:
> > > > >1) put a prototype in popper.h:
> > > > >extern void auth_sendmail(char*);
> > > > >
> > > > >2) put a call to the function in pop_pass.c, pop_auth.c and
> > > >pop_apop.c,
> > > > >right before pop_dropcopy:
> > > > >
> > > > >auth_sendmail(p->ipaddr);
> > > > >if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
> > > > >
> > > > >(need to put it before pop_dropcopy as that call will also also
drop
> > > > >privileges)
> > > > >
> > > > >3) if the -ldb is not in your makefile, add it
> > > > >
> > > > >LIBS = -lgdbm -ldb
> > > > >
> > > > >Hope this helps you,
> > > > >
> > > > >Martin
> > > > >
> > > > >"you have moved your mouse, please reboot to make this change take
> > > >effect"
> > > > >--------------------------------------------------
> > > > > Martin Bene vox: +43-316-813824
> > > > > simon media fax: +43-316-813824-6
> > > > > Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> > > > > 8010 Graz, Austria
> > > > >--------------------------------------------------
> > > > >finger mb at mail.sime dot com for PGP public key
> > > > >
> > > >
> > > >Turning and turning in the widening gyre
> > > >The falcon cannot hear the falconer;
> > > >Things fall apart; the centre cannot hold;
> > > >Mere anarchy is loosed upon the world.
> > >
> > >
>
>
Date: Sat, 6 May 2000 17:34:07 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: AW: Qpopper / Sendmail question
On Sat, 6 May 2000, Mitch Vincent wrote:
> I'm sorry, I never meant to imply there were any problems with it, it's just
> that I *personally* didn't like the way it was being done.
>
> I'm sure DRAC is a workable solution...
I'm curious as to why you had a problem with DRAC - it seems to me that
the approach you outline would have all sorts of problems with race
conditions and file contention, since multiple qpoppers can run at the
same time. So given the immediately obvious problems with your approach,
I'm curious as to what you didn't like about DRAC. It just may be that
the things you didn't like were put there for reasons that simply aren't
obvious to you yet.
Just a thought,
Steve
Date: Sat, 06 May 2000 15:42:18 -0700
From: Garlic <garlic at garlic dot com>
Subject: Re: AW: Qpopper / Sendmail question
DRAC doesn't work on all UNIX platforms unfortunately
Forrest Aldrich wrote:
> FWIW, we've been using DRAC on an old FreeBSD-2.2.8 system that has been
> delivering 1000s of messages for the last few months with NO problems.
>
> _F
>
> At 04:38 PM 5/6/00 -0400, Mitch Vincent wrote:
> >I looked at this and it does looks like it works, however the way it works I
> >don't like too much.
> >
> >
> >----- Original Message -----
> >From: Forrest Aldrich <forrie at forrie dot com>
> >To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
> >Sent: Saturday, May 06, 2000 2:57 PM
> >Subject: Re: AW: Qpopper / Sendmail question
> >
> >
> > > I suggest looking at DRAC:
> > >
> > > http://mail.cc.umanitoba.ca/drac/index.html
> > >
> > > For which I've already submitted patches to qpopper -- I understand those
> > > will be included in the next release.
> > >
> > >
> > > _F
> > >
> > >
> > > At 11:49 AM 5/6/00 -0700, Robin wrote:
> > > >Could we get this merged in as an optional feature in Qpopper? Our
> > > >coop has several users on dynamic IP dialups outside our network and
> > > >it'd be nice not to have to modify the source every time I upgrade the
> > > >POP server.
> > > >
> > > >-robin
> > > >
> > > > >Hi Mitch,
> > > > >
> > > > >
> > > > >> Basically, I need to know what the makemap does and code that
> > > > >> into my little
> > > > >> qpopper hack..
> > > > >>
> > > > >> Am I overstating this? Is it a lot easier than I think ? :-)
> > > > >
> > > > >I'm currently doing it this way; to make it work you need:
> > > > >
> > > > >1) the patch to make qpopper write the popauth.db file directly and
> > > > >2) a small program to remove old entries from the db file; you only
> > > >want to
> > > > >enable access from an external address for a certain time after all.
> > > >this
> > > > >little program should be run from a cronjob.
> > > > >
> > > > >Included Files:
> > > > >1) qpopper/popper/auth_sendmail.c -> module that logs pop
> > > >authentications
> > > > >directly to .db file.
> > > > >
> > > > >2) popusers/popusers.c -> program specified in (2). Compile using
> > > > >gcc -o popusers popusers.c -ldb
> > > > >start without parameters for usage notes.
> > > > >
> > > > >How to use it:
> > > > >1) put a prototype in popper.h:
> > > > >extern void auth_sendmail(char*);
> > > > >
> > > > >2) put a call to the function in pop_pass.c, pop_auth.c and
> > > >pop_apop.c,
> > > > >right before pop_dropcopy:
> > > > >
> > > > >auth_sendmail(p->ipaddr);
> > > > >if ( pop_dropcopy ( p, &pw ) != POP_SUCCESS ) {
> > > > >
> > > > >(need to put it before pop_dropcopy as that call will also also drop
> > > > >privileges)
> > > > >
> > > > >3) if the -ldb is not in your makefile, add it
> > > > >
> > > > >LIBS = -lgdbm -ldb
> > > > >
> > > > >Hope this helps you,
> > > > >
> > > > >Martin
> > > > >
> > > > >"you have moved your mouse, please reboot to make this change take
> > > >effect"
> > > > >--------------------------------------------------
> > > > > Martin Bene vox: +43-316-813824
> > > > > simon media fax: +43-316-813824-6
> > > > > Andreas-Hofer-Platz 9 e-mail: mb at sime dot com
> > > > > 8010 Graz, Austria
> > > > >--------------------------------------------------
> > > > >finger mb at mail.sime dot com for PGP public key
> > > > >
> > > >
> > > >Turning and turning in the widening gyre
> > > >The falcon cannot hear the falconer;
> > > >Things fall apart; the centre cannot hold;
> > > >Mere anarchy is loosed upon the world.
> > >
> > >
Date: Sun, 7 May 2000 22:51:02 +0200 (CEST)
From: Ted Parnefors <ted at mtv dot se>
Subject: APOP & USER
After having enabled APOP for a specific user, Is it then totally
impossible to at the same time have normal plaintext user-identification
active also (for that specific account) ?
--
Ted Parnefors <ted at mtv dot se>, KeyID 0x6627DEE4
PGP Fingerprint 1C39FA94703EB54A011CF18932018E256627DEE4
Date: Sun, 7 May 2000 18:28:54 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0.1 (final) available
At 8:50 PM -0400 5/5/00, Lisa Casey wrote:
> Hi,
>
> I'm downloaded and installed what was referred to as a candidate release of
> qpopper 3.0.1. Whats the difference between the candidate release and the
> 3.0.1b2 release mentioned below? Besides the fact that the b2 is a beta and
> (I think) the candidate is not.
The difference is the changes noted in the announcement. If you are
not experiencing any problems, there probably is no urgent need to
move from 3.0.1b2 to 3.0.1.
> I didn't see anything mentioned about a
> candidate release in the release notes on the FTP site. Is there (in your
> opinion) a compelling reason to upgrade from the candidate release to the
> final release?
>
> Thanks for the info,
>
> Lisa Casey, Webmaster
> Interstate 2000, Inc.
> lisa at jellico dot com
>
>
> ----- Original Message -----
> From: Qpopper Support <qpopper at qualcomm dot com>
> To: Subscribers of Qpopper <qpopper at lists.pensive dot org>;
> <qpopper-announce at qualcomm dot com>
> Cc: <qpopper at qualcomm dot com>
> Sent: Friday, May 05, 2000 8:22 PM
> Subject: Qpopper 3.0.1 (final) available
>
>
>> Qpopper 3.0.1 (final) 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.1b2 to 3.0.1 (final)
>> -------------------------------------
>>
>> 1. Improved log entries for I/O errors on client input stream.
>> 2. Fixed encode64/decode64 prototypes (thanks to J.J.Bailey).
>> 3. Fixed crash in popauth on OpenBSD.
>>
>>
>>
Date: Mon, 8 May 2000 06:50:25 -0400
From: Joseph S D Yao <jsdy at cospo.osis dot gov>
Subject: Re: Qpopper 3.01b2 on HPUX 10.20
On Fri, May 05, 2000 at 12:14:23AM -0600, Erik Langeland wrote:
> I am getting compile errors with the latest beta (2) of Qpopper 3.01 (also
> with the final 3.0) on HPUX 10.20. If anyone has successfully compiled it
> on HPUX, I could use some pointers. The compile errors I get occur in
> pop_dropcopy.c. Failing that, how does the HPUX-ported version of 2.53
> work?
>
> Thanks in advance.
>
> Erik Langeland
It appears that I'm using HP-UX ANSI C. You may need to upgrade to
that product or to 'gcc'. Sorry for the earlier and possibly
misleading note.
--
Joe Yao jsdy at cospo.osis dot gov - Joseph S. D. Yao
COSPO/OSIS Computer Support EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.
Date: Mon, 08 May 2000 09:57:02 -0400
From: Karyn McCambridge <karynm at afb dot net>
Subject: Filters...
Does anyone know if I can set filters with qpopper or do I need to use
another program. I am using sendmail 8.9.3 and qpopper 2.5.3.
I want to be able to setup filters for all users especially after the new
Love Bug virus.
Date: Mon, 8 May 2000 10:38:35 -0500
From: "Igor S. Livshits" <igorl at life.uiuc dot edu>
Subject: Re: Filters...
At 9:57 AM -0400 on 5/8/00, Karyn McCambridge wrote:
>Does anyone know if I can set filters with qpopper or do I need to use
>another program. I am using sendmail 8.9.3 and qpopper 2.5.3.
>
>I want to be able to setup filters for all users especially after the new
>Love Bug virus.
Karyn,
You should be filtering on the sendmail side -- take a look at
<http://www.digitalanswers.de/org/check_local/> (there is also
version 3.15 which works well with SM 8.9.3),
<http://www.agh.cc.kcl.ac.uk/unix/archive/checking/latest/> and
<http://www.informatik.uni-kiel.de/%7Eca/email/chk-89f.html>.
Good luck, Igor
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: Re: Filters...
Date: Mon, 8 May 2000 11:23:19 -0700
Hi Karyn,
This is an MTA ( sendmail ) issue. I think the best way to do it is to use
procmail for the local mailer and write a general recipe to scan headers.
I got it working for individual .procmailrc recipes, but I have yet to get
it to filter all mail. I need to learn how to tell sendmail to everything
through the /etc/procmailrcs
Better ideas, anyone?
Jerry O'Brien
Cutting Edge Systems
----- Original Message -----
From: Karyn McCambridge <karynm at afb dot net>
To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
Sent: Monday, May 08, 2000 6:57 AM
Subject: Filters...
> Does anyone know if I can set filters with qpopper or do I need to use
> another program. I am using sendmail 8.9.3 and qpopper 2.5.3.
>
> I want to be able to setup filters for all users especially after the new
> Love Bug virus.
>
>
Date: Mon, 08 May 2000 17:45:27 +0100
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: Filters...
At 19:23 08/05/00, Jerry O'Brien wrote:
>Hi Karyn,
>
>This is an MTA ( sendmail ) issue. I think the best way to do it is to use
>procmail for the local mailer and write a general recipe to scan headers.
>
>I got it working for individual .procmailrc recipes, but I have yet to get
>it to filter all mail. I need to learn how to tell sendmail to everything
>through the /etc/procmailrcs
>
>Better ideas, anyone?
Although this isn't the place to be discussing this sort of stuff, this
just arrived on another list I'm on, I haven't used it but it got high
praise and apparently it will do stuff like checking for files with any
.vbs attachments
ftp://ftp.rubyriver.com/pub/jhardin/antispam/procmail-security.html
Fergal.
Date: Mon, 8 May 2000 12:46:51 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: Filters...
On Mon, 8 May 2000, Jerry O'Brien wrote:
> This is an MTA ( sendmail ) issue. I think the best way to do it is to use
> procmail for the local mailer and write a general recipe to scan headers.
>
> I got it working for individual .procmailrc recipes, but I have yet to get
> it to filter all mail. I need to learn how to tell sendmail to everything
> through the /etc/procmailrcs
>
> Better ideas, anyone?
Here's what I'm using currently (stick in your sendmail.cf and kill -HUP):
D{MLovePat}ILOVEYOU
D{MJokePat}Joke
D{MMotherPat}Mother's Day Order Confirmation
D{MBVariantPat}Susitikim
D{MMsg}"Virus denied! For more information, see http://www.symantec.com/avcenter/venc/data/vbs.loveletter.a.html"
SCheckSubject
R${MLovePat} $* $#error $@ 5.7.1 $: 553 ${MMsg}
RRe: ${MLovePat} $* $#error $: 553 ${MMsg}
RRe:${MLovePat} $* $#error $: 553 ${MMsg}
RFW: ${MLovePat} $* $#error $: 553 ${MMsg}
RFW:${MLovePat} $* $#error $: 553 ${MMsg}
Rfwd: ${MJokePat} $* $#error $: 553 ${MMsg}
R${MMotherPat} $* $#error $: 553 ${MMsg}
RRe:${MMotherPat} $* $#error $: 553 ${MMsg}
RRe: ${MMotherPat} $* $#error $: 553 ${MMsg}
RFW:${MMotherPat} $* $#error $: 553 ${MMsg}
RFW: ${MMotherPat} $* $#error $: 553 ${MMsg}
R${MBVariantPat} $* $#error $: 553 ${MMsg}
RRe:${MBVariantPat} $* $#error $: 553 ${MMsg}
RRe: ${MBVariantPat} $* $#error $: 553 ${MMsg}
RFW:${MBVariantPat} $* $#error $: 553 ${MMsg}
RFW: ${MBVariantPat} $* $#error $: 553 ${MMsg}
I know there are other variants, but we haven't seen any of them yet.
Steve
--
tired of being an underappreciated functionary in a soulless machine?
hesketh.com is hiring: <http://hesketh.com/careers/>
From: "John W. Keener" <jkeener at utsi dot com>
Subject: RE: standalone popper 3
Date: Mon, 8 May 2000 12:56:36 -0500
You can start the popper up in the background. The proper solution, though,
is to daemonize it. This will give you your propmt back, and disconnect the
popper from any controling terminal etc.
John Keener
jkeener at utsi dot com
UTSI International
1560 West Bay Area Blvd
Friendswood TX 77546
-----Original Message-----
From: Kevin Dabson [mailto:kevin at dnc-electronics dot com]
Sent: Saturday, May 06, 2000 2:32 AM
To: dejan at knuten.liu dot se
Cc: qpopper at lists.pensive dot org
Subject: Re: standalone popper 3
Thanks for help regarding main.c bug.
Had to take out equal sign.
Now have qpopper 3 running in standalone
on redhat 6.1 without inetd.
Do have one problem though.
When I run popper of linux command line i can
no longer use it!. I have to press Ctrl C or Z
to exit it which quits program.
Does anybody know how to run popper direct of
command line or rc.local and carry on using system?
Some bash script perhaps.
KD
From: "Jerry O'Brien" <jobrien at cuttingedge dot net>
Subject: Re: Filters...
Date: Mon, 8 May 2000 15:04:14 -0700
Thanks Steven,
I have a couple errors under when I try to use this, though. First, I put it
in my .mc file in cf/cf using the LOCAL_RULESET command. This seems to work
fine, and inserts the following into the .cf file:
SLocal_check_mail
D{MLovePat}ILOVEYOU
D{MJokePat}Joke
D{MMotherPat}Mother's Day Order Confirmation
D{MBVariantPat}Susitikim
D{MMsg}"Virus denied! For more information, see
http://www.symantec.com/avcenter
/venc/data/vbs.loveletter.a.html"
SCheckSubject
R${MLovePat} $* $#error $@ 5.7.1 $: 553 ${MMsg}
RRe: ${MLovePat} $* $#error $: 553 ${MMsg}
RRe:${MLovePat} $* $#error $: 553 ${MMsg}
RFW: ${MLovePat} $* $#error $: 553 ${MMsg}
RFW:${MLovePat} $* $#error $: 553 ${MMsg}
Rfwd: ${MJokePat} $* $#error $: 553 ${MMsg}
R${MMotherPat} $* $#error $: 553 ${MMsg}
RRe:${MMotherPat} $* $#error $: 553 ${MMsg}
RRe: ${MMotherPat} $* $#error $: 553 ${MMsg}
RFW:${MMotherPat} $* $#error $: 553 ${MMsg}
RFW: ${MMotherPat} $* $#error $: 553 ${MMsg}
R${MBVariantPat} $* $#error $: 553 ${MMsg}
RRe:${MBVariantPat} $* $#error $: 553 ${MMsg}
RRe: ${MBVariantPat} $* $#error $: 553 ${MMsg}
RFW:${MBVariantPat} $* $#error $: 553 ${MMsg}
RFW: ${MBVariantPat} $* $#error $: 553 ${MMsg}
However, HUPping the running deamon does not effect any change (test
messages with ILOVEYOU in the subject still pass. Whereas, restarting the
daemon gives this error:
Starting sendmail: sendmail 554 5.0.0 /etc/mail/sendmail.cf: line 1016:
invalid
rewrite line "RRe: $ * #error : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1017: invalid rewrite line "RRe:$ *
#
error : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1018: invalid rewrite line "RFW: $ *
#
error : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1019: invalid rewrite line "RFW:$ *
#
error : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1020: invalid rewrite line "Rfwd: % *
#
error : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1021: invalid rewrite line "R& *
#er
ror : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1022: invalid rewrite line "RRe:& *
#er
ror : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1023: invalid rewrite line "RRe: & *
#er
ror : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1024: invalid rewrite line "RFW:& *
#er
ror : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1025: invalid rewrite line "RFW: & *
#er
ror : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1026: invalid rewrite line "R' *
#erro
r : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1027: invalid rewrite line "RRe:' *
#erro
r : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1028: invalid rewrite line "RRe: ' *
#erro
r : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1029: invalid rewrite line "RFW:' *
#erro
r : 553 (" (tab expected)
554 5.0.0 /etc/mail/sendmail.cf: line 1030: invalid rewrite line "RFW: ' *
#erro
r : 553 (" (tab expected)
Jerry O'Brien
Cutting Edge Systems
----- Original Message -----
From: Steven Champeon <schampeo at hesketh dot com>
To: Jerry O'Brien <jobrien at cuttingedge dot net>
Cc: Karyn McCambridge <karynm at afb.net>; qpopper <qpopper at lists dot pensive dot org>
Sent: Monday, May 08, 2000 9:46 AM
Subject: Re: Filters...
> On Mon, 8 May 2000, Jerry O'Brien wrote:
> > This is an MTA ( sendmail ) issue. I think the best way to do it is to
use
> > procmail for the local mailer and write a general recipe to scan
headers.
> >
> > I got it working for individual .procmailrc recipes, but I have yet to
get
> > it to filter all mail. I need to learn how to tell sendmail to
everything
> > through the /etc/procmailrcs
> >
> > Better ideas, anyone?
>
> Here's what I'm using currently (stick in your sendmail.cf and kill -HUP):
>
> D{MLovePat}ILOVEYOU
> D{MJokePat}Joke
> D{MMotherPat}Mother's Day Order Confirmation
> D{MBVariantPat}Susitikim
> D{MMsg}"Virus denied! For more information, see
http://www.symantec.com/avcenter/venc/data/vbs.loveletter.a.html"
>
>
> SCheckSubject
> R${MLovePat} $* $#error $@ 5.7.1 $: 553 ${MMsg}
> RRe: ${MLovePat} $* $#error $: 553 ${MMsg}
> RRe:${MLovePat} $* $#error $: 553 ${MMsg}
> RFW: ${MLovePat} $* $#error $: 553 ${MMsg}
> RFW:${MLovePat} $* $#error $: 553 ${MMsg}
> Rfwd: ${MJokePat} $* $#error $: 553 ${MMsg}
> R${MMotherPat} $* $#error $: 553 ${MMsg}
> RRe:${MMotherPat} $* $#error $: 553 ${MMsg}
> RRe: ${MMotherPat} $* $#error $: 553 ${MMsg}
> RFW:${MMotherPat} $* $#error $: 553 ${MMsg}
> RFW: ${MMotherPat} $* $#error $: 553 ${MMsg}
> R${MBVariantPat} $* $#error $: 553 ${MMsg}
> RRe:${MBVariantPat} $* $#error $: 553 ${MMsg}
> RRe: ${MBVariantPat} $* $#error $: 553 ${MMsg}
> RFW:${MBVariantPat} $* $#error $: 553 ${MMsg}
> RFW: ${MBVariantPat} $* $#error $: 553 ${MMsg}
>
> I know there are other variants, but we haven't seen any of them yet.
>
> Steve
>
> --
> tired of being an underappreciated functionary in a soulless machine?
> hesketh.com is hiring: <http://hesketh.com/careers/>
>
Date: Mon, 8 May 2000 16:09:59 -0400 (EDT)
From: Steven Champeon <schampeo at hesketh dot com>
Subject: Re: Filters...
On Mon, 8 May 2000, Jerry O'Brien wrote:
> Starting sendmail: sendmail 554 5.0.0 /etc/mail/sendmail.cf: line 1016:
> invalid
> rewrite line "RRe: $ * #error : 553 (" (tab expected)
Well, the error should be clear, even if I wasn't :) Sendmail is
expecting a tab between the $* and the $#error in the lines I sent
along; if you're hacking a sendmail.cf file and didn't check the
rulesets for tabs, what can I say? :)
As for placement, I just stuck mine in my sendmail.cf file right
before the Options section and it works fine for me. Thanks for the
suggestions WRT the mc file; that'll come in handy.
Steve
--
tired of being an underappreciated functionary in a soulless machine?
hesketh.com is hiring: <http://hesketh.com/careers/>
Date: Mon, 8 May 2000 18:28:24 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Problems with server mode
At 9:47 AM +0000 5/5/00, Javier Castillo wrote:
> Hi there,
>
> I have compiled last version of qpopper with this options:
>
> ./configure --enable-specialauth --enable-servermode
> --enable-debugging
> --enable-auto-delete
>
>
> My problem is: how I run popper on server mode?. Last version
> 2.53 has
> -S flag, that activate server mode...
>
All you need is the --enable-servermode flag to ./configure.
Date: Mon, 8 May 2000 18:31:07 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Illegal seek
At 10:22 PM -0700 5/5/00, Jerry O'Brien wrote:
> No APOP, but the illegal seek comes in every few minutes and is not tied to
> a single IP or NAS.
If you're getting this error frequently, and the user name is null,
it seems that a client is closing the connection after getting the
greeting, or is getting disconnected.
Is there any pattern to the IPs? Are they all dial-ups? Do they
all use the same client?
>
> JO
>
> ----- Original Message -----
> From: Spencer Yost <yostsw at newidea.atis dot net>
> To: <jobrien at cuttingedge dot net>
> Sent: Friday, May 05, 2000 4:09 AM
> Subject: Re: Illegal seek
>
>
>> If you have APOP enabled, Outlook Express clients will cause Qpopper to
>> generate this message.
>>
>> Just a thought,
>>
>> Spencer Yost
>> Owner, ATIS
>> Plow the Net!
>> http://www.atis.net
>>
>> *********** REPLY SEPARATOR ***********
>>
>> On 5/4/00 at 11:38 PM Jerry O'Brien wrote:
>>
>> >What would cause this? The user name appears to be null. Client error? Is
>> it
>> >being handled OK?
>> >
>> >May 4 22:38:42 TAIPAN popper[22297]: (null) at
>> >dialup-brf-10.cuttingedge.net (208.35.151.10): -ERR
>> >POP EOF or I/O error: Illegal seek (29) [popper.c:560]
>> >
>> >Jerry O'Brien
>> >Cutting Edge Systems
>>
>>
>>
Date: Mon, 8 May 2000 18:32:50 -0700
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: standalone popper 3
At 7:32 AM +0000 5/6/00, Kevin Dabson wrote:
> Does anybody know how to run popper direct of
> command line
You can always use 'telnet localhost 110'.
From: "James Nelson" <james at digit.bloomnet dot com>
Subject: Poppper 3.0.1 on RedHat Linux 6.2
Date: Mon, 8 May 2000 20:48:43 -0500
3.0.1 builds but will not run. I've got 3.0b34 working without any
problems. I've tried it with and without pam, with and without shadow
passwords, with and without md5 enabled.
The /usr/include/asm and /usr/src/linux directories are from the
latest redhat kernel source RPM.
I've sent straces and config info previously but have not heard
anything more about it. If anyone would be willing to help me look at
this please let me know. I am concerned that an exploit will come out
and I will be stuck running 3.0b34 with the hole because I can't patch
it and nothing else will work on 6.2.
Date: Tue, 09 May 2000 08:06:05 +0000
From: Javier Castillo <castillo at alhsys dot es>
Subject: Re: Problems with server mode
Qpopper Support wrote:
>
> At 9:47 AM +0000 5/5/00, Javier Castillo wrote:
>
> > Hi there,
> >
> > I have compiled last version of qpopper with this options:
> >
> > ./configure --enable-specialauth --enable-servermode
> > --enable-debugging
> > --enable-auto-delete
> >
> >
> > My problem is: how I run popper on server mode?. Last version
> > 2.53 has
> > -S flag, that activate server mode...
> >
>
> All you need is the --enable-servermode flag to ./configure.
Yes, I have enable this flag as you can see....
From: "Kenneth Porter" <shiva at well dot com>
Date: Tue, 09 May 2000 10:18:49 -0700
Subject: Re: Poppper 3.0.1 on RedHat Linux 6.2
On Mon, 8 May 2000 20:48:43 -0500, James Nelson wrote:
>3.0.1 builds but will not run. I've got 3.0b34 working without any
>problems. I've tried it with and without pam, with and without shadow
>passwords, with and without md5 enabled.
>
>The /usr/include/asm and /usr/src/linux directories are from the
>latest redhat kernel source RPM.
I just created a 3.0.1 RPM and installed it on my 6.1 system. Seems to
be working ok. The RPM for 3.0.0 is available in the RH FTP contrib
directory. I've been running that since its release, supporting a
couple dozen users.
See http://rpmfind.net/linux/RPM/qpopper.html for the latest available
version. Includes source, so you can tweak the spec file for your own
config and then rebuild it. I'm about to upload the 3.0.1 package to
RH, so you should see it appear in the RH contrib directory in 2 days
and at rpmfind in about 3-4 days.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
http://www.harrybrowne2000.org/
Date: Tue, 09 May 2000 14:09:25 -0700
From: Joel Laing <joel at scripps dot edu>
Subject: Re: Qpopper 3.0.1 (final) available
I've not tried 3.0.1 nor kerberos support, but I did get 3.0 running
with apop under IRIX6.5.7... Qpopper is ready for release, it's just
that IRIX neds a bit more tweaking than most systems. I've found this to
be true with most freeware I've gotten. They usually compile fine on
Solaris, then I go to make IRIX binaries and have to fiddle.
Here's a few bits that helped me with my compile:
- Warnings are just warnings. Ignore them. You'll sleep better.
- use the CFLAG -common in your makefiles. This will prevent LD from
blowing chunks after 50 warnings of "multiply defined" (see the cc man
page)
- Grab the GNU gdbm librarie and stick um in usr/include. This was only
need when compiling in apop support....
- Make sure you have the entire development libraries and development
foundation installed (or at least the right pieces). Along with any MIPS
compiler patches etc...
- Make sure that your LM_LICENSE_FILE environment variable is set
properly so that you do not get annoying license messages (this can
confuse the parsing during configure even thought the compiler may work)
Can't think of any more right now.... Beer can help.
-Joel
Peter Evans wrote:
>
> Qpopper Support (qpopper at qualcomm dot com) wrote:
> > Qpopper 3.0.1 (final) is available at
> > <ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
>
> Perhaps its just my compiler, or OS, but qpopper3 isnt really ready for
> release yet. (Sorry I am late, not enough hours in the day.)
>
> irix 6.5.blah, irix c compiler.
>
> Errors that snuck through:
>
> cc -c -I.. -I.. -I. -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_msg.c -o pop_msg.o
> "pop_msg.c", line 108: warning(1185): enumerated type mixed with another type
> pop_log ( p, LOG_NOTICE, fn, ln,
>
> [this one looks like a typo. everywhere else, its POP_NOTICE]
>
> cc -c -I.. -I.. -I. -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_pass.c -o pop_pass.o
> "pop_pass.c", line 984: warning(1177): argument is incompatible with formal
> parameter
> if ( ( p->kerberos ? auth_user_kerberos ( p, pw )
> ^
> [
> int
> auth_user_kerberos (p, pw)
> POP * p;
> struct passwd *pw;
>
> but in pop_pass, pw is defined as:
>
> struct passwd pw, *pwp;
>
> so this is probably a typo too.
> ]
>
> cc -c -I.. -I.. -I. -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_send.c -o pop_send.o
> "pop_send.c", line 440: warning(1116): non-void function "pop_sendline"
> (declared at line 411) should return a value
> }
>
> [usual default type is "int" not "void" complaint]
>
> cc -c -I.. -I.. -I. -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DIRIX -DUNIX pop_updt.c -o pop_updt.o
> "pop_updt.c", line 86: warning(1047): macro redefined differently
> #define BBSIZE 4096
> ^
> [ odd one. Maybe the system is defining this one, ^_^;]
>
> cc -c -I.. -I.. -I. -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DIRIX -DUNIX popper.c -o popper.o
> "popper.c", line 136: warning(1048): cast between pointer-to-object and
> pointer-to-function
> if ( signal (SIGHUP, VOIDSTAR catchSIGHUP ) == SIG_ERR ||
> ^
> "popper.c", line 136: warning(1164): argument of type "void *" is incompatible
> with parameter of type "void (*)()"
> if ( signal (SIGHUP, VOIDSTAR catchSIGHUP ) == SIG_ERR ||
>
> [times several]
>
> The mime/mangler stuff is one big error according to the compiler.
> nested comments, enumerated type mixed with another type.
> operand types are incompatible, possible use of "=" where "==" was
> intended, etc ^^;
>
> in common:
> cc -c -I.. -I. -I.. -I../popper -g -DHAVE_CONFIG_H -DIRIX -DUNIX maillock.c -o maillock.o
> "maillock.c", line 404: warning(1172): subscript out of range
> buf[BUF_SIZE] = '\0';
>
> then at link time, the compiler moans and groans about ...
>
> ld32: WARNING 15: multiply defined:(s) in pop_dele.o and pop_get_command.o (2nd definition ignored).
> ld32: WARNING 15: multiply defined:(size) in pop_dele.o and pop_get_command.o (2nd definition ignored).
> ld32: WARNING 15: multiply defined:(stream) in pop_dele.o and pop_get_command.o (2nd definition ignored).
>
> This comes from stuff leaking out of popper.h
> at line 506.
>
> char *s;
> int size;
> FILE *stream;
>
>
> P
> ----*
>
> --
> Remember The 5 K's.
> The Justified Agents of Munya-munya-muuuu ...
Date: Wed, 10 May 2000 21:51:22 -0400
From: Brad Groshok <bgroshok at odyssey.on dot ca>
Subject: popper.log file format??
I've just installed qpopper 3.0 on a sun Solaris 8 system.
and am getting an "extra" field in the popper.log file than I am used to
seeing.
[ID 702911 local0.notice] is what I'm not used to
Have I done something wrong in the setup, or is this field normal?
The complete popper line is:
May 10 12:19:47 chip popper[25067]: [ID 702911 local0.notice] Stats: brad 0
0 0 0 cr7434-a.lndn1.on.wave.home.com 24.112.80.7
The line I added to my /etc/syslog.conf is:
local0.notice /var/log/popper.log
(killed and restarted syslogd of course)
qpopper built with gcc version 2.95.2
no special switches for qpopper during build.
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/ Regards: Brad Groshok (bgroshok at odyssey.on dot ca) _/
_/ President Odyssey Network Inc. http://www.odyssey.on.ca _/
_/ London Ontario Canada PH:(519)660-8883 Fax:(519)660-6111 _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Subject: Re: popper.log file format??
Date: Thu, 11 May 2000 10:42:05 +0200 (MET DST)
From: Eric Luyten <Eric.Luyten at vub.ac dot be>
> I've just installed qpopper 3.0 on a sun Solaris 8 system.
> and am getting an "extra" field in the popper.log file than I am used to
> seeing.
>
> [ID 702911 local0.notice] is what I'm not used to
> Have I done something wrong in the setup, or is this field normal?
>
> The complete popper line is:
> May 10 12:19:47 chip popper[25067]: [ID 702911 local0.notice] Stats: brad 0
> 0 0 0 cr7434-a.lndn1.on.wave.home.com 24.112.80.7
>
> The line I added to my /etc/syslog.conf is:
> local0.notice /var/log/popper.log
> (killed and restarted syslogd of course)
Check file /kernel/drv/log.conf
There is probably a line reading 'msgid=1;' at the end.
Remove that line (but check with the sysadmin first) and
you'll again have the old, familiar format.
More information : man -s 7d log
Eric.
From: "Keith Warno" <keith at HaggleWare dot com>
Subject: checking for mail spool directory... ERROR: Couln't locate the mail spool
Date: Thu, 11 May 2000 11:13:18 -0400
... And it shouldn't have found the mail spool because it doesn't exist!
;-)
(This error was received when trying to configure the latest qpopper source,
3.0.1)
OK, we have a SuSE 6.2 box that is *sendmail free*. We use qmail for
delivering mail to ~/Mailbox (the default for qmail setups). So I attempt
to configure qpopper like so:
./configure --enable-log-login --enable-shy --enable-home-dir-mail=Mailbox
So why is it still looking for sendmail and the mail spool? sendmail exists
(as a wrapper for other programs that don't believe in qmail), although the
mail spool doesn't (there's no need for it) and the configure exits.
Can I safely comment out the mail spool & sendmail checks in the configure
script? Or are some sort of meaningless values for these still required?
Thanks,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
From: "Keith Warno" <keith at HaggleWare dot com>
Subject: Re: checking for mail spool directory... ERROR: Couln't locate the mail spool
Date: Thu, 11 May 2000 11:37:09 -0400
I hate to reply to my own msgs. But.. ;p
Seems qpopper wants to know about sendmail but doesn't care about the mail
spool in this situation. However something else that popped up (um, no pun
here) is the slew of "multiple common" wanrings:
[...]
pop_dropcopy.o: warning: multiple common of `s'
pop_dele.o: warning: previous common is here
pop_dropcopy.o: warning: multiple common of `size'
pop_dele.o: warning: previous common is here
pop_dropcopy.o: warning: multiple common of `stream'
pop_dele.o: warning: previous common is here
pop_get_command.o: warning: multiple common of `s'
pop_dele.o: warning: previous common is here
pop_get_command.o: warning: multiple common of `size'
pop_dele.o: warning: previous common is here
pop_get_command.o: warning: multiple common of `stream'
pop_dele.o: warning: previous common is here
pop_get_subcommand.o: warning: multiple common of `s'
pop_dele.o: warning: previous common is here
pop_get_subcommand.o: warning: multiple common of `size'
pop_dele.o: warning: previous common is here
pop_get_subcommand.o: warning: multiple common of `stream'
pop_dele.o: warning: previous common is here
pop_init.o: warning: multiple common of `s'
pop_dele.o: warning: previous common is here
pop_init.o: warning: multiple common of `size'
pop_dele.o: warning: previous common is here
pop_init.o: warning: multiple common of `stream'
pop_dele.o: warning: previous common is here
[...]
Sometimes I ignore these. In this case I won't. ;p Looks like a bunch of
variables were declared in header files maybe? tsk tsk.
The compiler in use is:
keith at develop[pts/14]:~/qpopper3.0 dot 1$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
keith at develop[pts/14]:~/qpopper3.0 dot 1$
Cheers,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
----- Original Message -----
From: "Keith Warno" <keith at HaggleWare dot com>
To: "Subscribers of Qpopper" <qpopper at lists.pensive dot org>
Sent: 11 May 2000, Thursday 11:13
Subject: checking for mail spool directory... ERROR: Couln't locate the mail
spool
... And it shouldn't have found the mail spool because it doesn't exist!
;-)
(This error was received when trying to configure the latest qpopper source,
3.0.1)
OK, we have a SuSE 6.2 box that is *sendmail free*. We use qmail for
delivering mail to ~/Mailbox (the default for qmail setups). So I attempt
to configure qpopper like so:
./configure --enable-log-login --enable-shy --enable-home-dir-mail=Mailbox
So why is it still looking for sendmail and the mail spool? sendmail exists
(as a wrapper for other programs that don't believe in qmail), although the
mail spool doesn't (there's no need for it) and the configure exits.
Can I safely comment out the mail spool & sendmail checks in the configure
script? Or are some sort of meaningless values for these still required?
Thanks,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/