The qpopper list archive ending on 17 Feb 2000
Topics covered in this issue include:
1. RE: APOP Question.
"Benjamin Hyatt" <benski at pacbell dot net>
Fri, 11 Feb 2000 09:18:13 -0800
2. Re: APOP Question.
Gerhard Gonter <gonter at maestria.wu-wien.ac dot at>
Fri, 11 Feb 2000 18:36:43 +0100 (MEZ)
3. Re: APOP Question.
Williams Martinez <willie at uncoma.edu dot ar>
Fri, 11 Feb 2000 14:54:53 -0300
4. Re: APOP Question.
"Jeremy C. Reed" <reed at wcug.wwu dot edu>
Fri, 11 Feb 2000 10:09:35 -0800 (PST)
5. Re: APOP Question.
Williams Martinez <willie at uncoma.edu dot ar>
Fri, 11 Feb 2000 15:18:41 -0300
6. Re: Qpopper 3.0b34 available
"Kenneth Porter" <shiva at well dot com>
Fri, 11 Feb 2000 13:54:20 -0800
7. I hope someone can help me.
<qpopper at thebitch.twosexygeeks dot com>
Fri, 11 Feb 2000 16:03:00 -0800 (PST)
8. Re: I hope someone can help me.
"Kenneth Porter" <shiva at well dot com>
Fri, 11 Feb 2000 16:16:48 -0800
9. Re: I hope someone can help me.
"Jeremy C. Reed" <reed at wcug.wwu dot edu>
Fri, 11 Feb 2000 16:24:45 -0800 (PST)
10. Re: I hope someone can help me.
<qpopper at thebitch.twosexygeeks dot com>
Fri, 11 Feb 2000 18:17:04 -0800 (PST)
11. 3.0b24 on HP-UX 10.20
Tadeusz Wiewiorowski <twiewior at toronto.cbc dot ca>
Sun, 13 Feb 2000 13:41:51 -0500
12. Re: I hope someone can help me.
Qpopper Support <qpopper at qualcomm dot com>
Sat, 12 Feb 2000 16:44:49 -0800
13. aliasing /problem solved
hypnose at t-online dot de (guenter wessling)
Sat, 12 Feb 2000 11:12:32 +0100
14. APOP password proplem
Torbjorn Astlind <torbjorn at biophys.su dot se>
Mon, 14 Feb 2000 09:02:24 +0100
15. Re: APOP password proplem
"Julian Y. Koh" <kohster at mac dot com>
Mon, 14 Feb 2000 11:11:48 -0600
16. Failed make on IRIX: -ldir
"Neil R. Smith" <neils at ariel.met.tamu dot edu>
Mon, 14 Feb 2000 14:14:58 -0600
17. Re: swap issue
Joseph S D Yao <jsdy at cospo.osis dot gov>
Mon, 14 Feb 2000 16:18:18 -0500
18. Re: Qpopper 3.0b34 available
Joseph S D Yao <jsdy at cospo.osis dot gov>
Mon, 14 Feb 2000 19:00:20 -0500
19. qpopper beta and compiling on linux?
Jim Warren <jim at coam dot net>
Mon, 14 Feb 2000 16:55:02 -0800 (PST)
20. RE: qpopper beta and compiling on linux?
"Benjamin Hyatt" <benski at pacbell dot net>
Mon, 14 Feb 2000 17:15:38 -0800
21. RE: qpopper beta and compiling on linux?
Jim Warren <jim at coam dot net>
Mon, 14 Feb 2000 17:26:25 -0800 (PST)
22. RE: qpopper beta and compiling on linux?
"Igor S. Livshits" <igorl at life.uiuc dot edu>
Mon, 14 Feb 2000 19:36:22 -0600
23. Re: Qpopper 3.0b34 available
Qpopper Support <qpopper at qualcomm dot com>
Mon, 14 Feb 2000 18:25:37 -0800
24. RE: qpopper beta and compiling on linux?
Qpopper Support <qpopper at qualcomm dot com>
Mon, 14 Feb 2000 18:32:41 -0800
25. RE: qpopper beta and compiling on linux?
Jim Warren <jim at coam dot net>
Mon, 14 Feb 2000 23:55:37 -0800 (PST)
26. Qpopper 2.5.3
Karyn McCambridge <karynm at afb dot net>
Tue, 15 Feb 2000 10:34:33 -0500
27. Re: Qpopper 2.5.3
Mihigo John <nmj at gorilla.nur.ac dot rw>
Tue, 15 Feb 2000 19:04:08 +0200 (SAST)
28. Re: Qpopper 3.0b34 available
Joseph S D Yao <jsdy at cospo.osis dot gov>
Tue, 15 Feb 2000 12:53:27 -0500
29. spurious logging
Fergal Daly <fergal at esatclear dot ie>
Tue, 15 Feb 2000 20:09:22 +0000
30. Re: spurious logging
Qpopper Support <qpopper at qualcomm dot com>
Tue, 15 Feb 2000 14:46:48 -0800
31. Re: spurious logging
Fergal Daly <fergal at esatclear dot ie>
Tue, 15 Feb 2000 23:04:25 +0000
32. Re: spurious logging
Qpopper Support <qpopper at qualcomm dot com>
Tue, 15 Feb 2000 15:44:28 -0800
33. Announcing: Qpopper-Announce
Qpopper Support <qpopper at qualcomm dot com>
Tue, 15 Feb 2000 16:03:38 -0800
34. RADIUS auth testing
Admin Mailing Lists <mlist at intergrafix dot net>
Wed, 16 Feb 2000 10:38:13 -0500 (EST)
35. Re: RADIUS auth testing
Admin Mailing Lists <mlist at intergrafix dot net>
Wed, 16 Feb 2000 11:12:15 -0500 (EST)
36. Re: RADIUS auth testing
Vince Vielhaber <vev at michvhf dot com>
Wed, 16 Feb 2000 11:28:39 -0500 (EST)
37. Re: RADIUS auth testing
Admin Mailing Lists <mlist at intergrafix dot net>
Wed, 16 Feb 2000 11:46:27 -0500 (EST)
38. Re: RADIUS auth testing
Vince Vielhaber <vev at michvhf dot com>
Wed, 16 Feb 2000 11:55:42 -0500 (EST)
39. envelope error
Brent <bierblb at netins dot net>
Wed, 16 Feb 2000 12:24:22 -0600
40.
"Mike Giller" <mgiller at nwc dot net>
Wed, 16 Feb 2000 10:25:23 -0800
41. XUIDL ....... error
"Julio" <jrilo at asturnet dot es>
Wed, 16 Feb 2000 19:38:45 +0100
42. RE: envelope error
"Jlinux" <jlinux at asturnet dot es>
Wed, 16 Feb 2000 19:42:37 +0100
43. Got successful make on IRIX?
"Neil R. Smith" <neils at ariel.met.tamu dot edu>
Wed, 16 Feb 2000 15:39:52 -0600
44. Re: envelope error
James Triplett <james at mail.th dot net>
Wed, 16 Feb 2000 17:52:54 -0500
45. Re: envelope error
Qpopper Support <qpopper at qualcomm dot com>
Wed, 16 Feb 2000 15:24:47 -0800
46. Re: envelope error
Qpopper Support <qpopper at qualcomm dot com>
Wed, 16 Feb 2000 17:07:00 -0800
47. Re: envelope error
James Triplett <james at mail.th dot net>
Wed, 16 Feb 2000 23:35:47 -0500
48. Netscape sending unknown xsender command
"Kenneth Porter" <shiva at well dot com>
Wed, 16 Feb 2000 22:07:43 -0800
49. Re: Netscape sending unknown xsender command
Qpopper Support <qpopper at qualcomm dot com>
Thu, 17 Feb 2000 11:12:32 -0800
50. What does this mean in log file???
John Stevenson <JSteven1 at swst dot com>
Thu, 17 Feb 2000 13:20:34 -0600
From: "Benjamin Hyatt" <benski at pacbell dot net>
Subject: RE: APOP Question.
Date: Fri, 11 Feb 2000 09:18:13 -0800
Hello,
My understanding is....
Users must change their password via popauth.
. Ben
> -----Original Message-----
> From: Williams Martinez [mailto:willie at uncoma.edu dot ar]
> Sent: Friday, February 11, 2000 7:20 AM
> To: Subscribers of Qpopper
> Subject: APOP Question.
>
>
> Hi.
>
> I'm configuring Qpopper 3.0b34 with apop authentication.
>
> Is there any tools that users can use to change their own password via
> Eudora? Like poppassd wich we use to offer this service.
>
> Thanx
>
>
From: Gerhard Gonter <gonter at maestria.wu-wien.ac dot at>
Subject: Re: APOP Question.
Date: Fri, 11 Feb 2000 18:36:43 +0100 (MEZ)
According to Williams Martinez:
> I'm configuring Qpopper 3.0b34 with apop authentication.
> Is there any tools that users can use to change their own password via
> Eudora? Like poppassd wich we use to offer this service.
This is a design problem: apop authentication avoids the transfer
of clear passwords, the shared secret is saved in the popauth
database over another, presumably more secure, channel. The
user could log in on a physical terminal or use ssh etc. to log
into the host and save the password.
The poppass protocol however requires to send the password in
clear text over a TCP connection. This would render apop more or
less unnecessary.
Therefore it's necessary to store a new apop password using a
secure channel, external to the mail access protocol.
Otherwise, it would be quite trivial to hack popauth to function
as a poppass daemon.
+gg
--
Gerhard.Gonter at wu-wien.ac.at Fax: +43/1/31336/702 g dot gonter at ieee dot org
Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria
Date: Fri, 11 Feb 2000 14:54:53 -0300
From: Williams Martinez <willie at uncoma.edu dot ar>
Subject: Re: APOP Question.
Gerhard Gonter wrote:
>
> This is a design problem: apop authentication avoids the transfer
> of clear passwords, the shared secret is saved in the popauth
> database over another, presumably more secure, channel. The
> user could log in on a physical terminal or use ssh etc. to log
> into the host and save the password.
>
ok
>
> The poppass protocol however requires to send the password in
> clear text over a TCP connection. This would render apop more or
> less unnecessary.
>
That's rigth.
>
> Therefore it's necessary to store a new apop password using a
> secure channel, external to the mail access protocol.
>
> Otherwise, it would be quite trivial to hack popauth to function
> as a poppass daemon.
>
> +gg
>
> --
> Gerhard.Gonter at wu-wien.ac.at Fax: +43/1/31336/702 g dot gonter at ieee dot org
> Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria
Gerhard, you are rigth!!! I don't realize what you are pointing out.
Now it is quite clear that we need some sort of secure channel in order to
provide a tool to our users to change their password. Our users don't have
shell, as part of our security policy, so I need to find or write some sort
of app that use, perhaps, SSL and interact with popauth.
Anyway, thanks for the answer and take care.
Date: Fri, 11 Feb 2000 10:09:35 -0800 (PST)
From: "Jeremy C. Reed" <reed at wcug.wwu dot edu>
Subject: Re: APOP Question.
On Fri, 11 Feb 2000, Williams Martinez wrote:
> Now it is quite clear that we need some sort of secure channel in order to
> provide a tool to our users to change their password. Our users don't have
> shell, as part of our security policy, so I need to find or write some sort
> of app that use, perhaps, SSL and interact with popauth.
Maybe a https web-based script? Or you could allow the users to
login via ssh and have their "login shell" set to your changing password
routine.
Jeremy C. Reed
....................................................
BSD software, documentation, resources, news...
http://bsd.reedmedia.net
Date: Fri, 11 Feb 2000 15:18:41 -0300
From: Williams Martinez <willie at uncoma.edu dot ar>
Subject: Re: APOP Question.
"Jeremy C. Reed" wrote:
>
> Maybe a https web-based script? Or you could allow the users to
> login via ssh and have their "login shell" set to your changing password
> routine.
>
> Jeremy C. Reed
> ....................................................
> BSD software, documentation, resources, news...
> http://bsd.reedmedia.net
Yes, I'm thinking in a web-based script using SSL.
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 11 Feb 2000 13:54:20 -0800
Subject: Re: Qpopper 3.0b34 available
On Thu, 10 Feb 2000 19:06:04 -0800, Qpopper Support wrote:
>Qpopper 3.0b34 is available at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
I just uploaded a matching RPM package to Red Hat, and it should appear
shortly in the libc6 contribs and on rpmfind.net.
I changed the default logging facility to LOG_LOCAL1 to avoid
cluttering up sendmail's maillog with the frequent mail checks of my
users. To support this, I added a logrotate config file to the RPM
package. The package description includes a description of what you
need to do to syslog.conf to support this. (To view a package's
description, use "rpm -qpi package.rpm".) (If you don't change Red
Hat's syslog.conf, messages for the local1 facility will go into
/var/log/messages.)
If you use TCP Wrappers to run qpopper, you may also want to edit
hosts.allow to add "severity local1.info" to the access rule for
qpopper to redirect those entries from /var/log/messages to the new
qpopper log file.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
Date: Fri, 11 Feb 2000 16:03:00 -0800 (PST)
From: <qpopper at thebitch.twosexygeeks dot com>
Subject: I hope someone can help me.
I'm the sys admin at an ISP. For our mail I currently run sendmail and
qpopper3.0b30 and all of my customers are now getting the e-mail from
MAILER_DAEMON at mydoman dot net that says.
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
I believe that is something that is placed there because of
sendmail. However I would like to continue using sendmail but my
customers are getting irritated about this E-Mail. Could anyone point me
in the right direction to get this fixed? Thanks.
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 11 Feb 2000 16:16:48 -0800
Subject: Re: I hope someone can help me.
On Fri, 11 Feb 2000 16:03:00 -0800 (PST),
qpopper at thebitch.twosexygeeks dot com wrote:
>I'm the sys admin at an ISP. For our mail I currently run sendmail and
>qpopper3.0b30 and all of my customers are now getting the e-mail from
>MAILER_DAEMON at mydoman dot net that says.
>Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
>
>I believe that is something that is placed there because of
>sendmail. However I would like to continue using sendmail but my
>customers are getting irritated about this E-Mail. Could anyone point me
>in the right direction to get this fixed? Thanks.
You just missed all the relevant traffic on that subject on this list
over the last few days. The message is being inserted by University of
Washington software, probably imapd, ipop3d, or Pine. These programs
insert a special message at the top of the spool file to maintain state
data that assists in rapid restart of their servers. Sendmail is NOT
involved in this.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
Date: Fri, 11 Feb 2000 16:24:45 -0800 (PST)
From: "Jeremy C. Reed" <reed at wcug.wwu dot edu>
Subject: Re: I hope someone can help me.
On Fri, 11 Feb 2000 qpopper at thebitch.twosexygeeks dot com wrote:
> I'm the sys admin at an ISP. For our mail I currently run sendmail and
> qpopper3.0b30 and all of my customers are now getting the e-mail from
> MAILER_DAEMON at mydoman dot net that says.
> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
http://www.washington.edu/pine/faq/problems.html#pseudo-message
> I believe that is something that is placed there because of
> sendmail. However I would like to continue using sendmail but my
> customers are getting irritated about this E-Mail. Could anyone point me
> in the right direction to get this fixed? Thanks.
This message is used by UW email software (pine, imap, popd).
Did you recently change to qpopper?
(This should be added to the qpopper faq.)
Jeremy C. Reed
....................................................
BSD software, documentation, resources, news...
http://bsd.reedmedia.net
Date: Fri, 11 Feb 2000 18:17:04 -0800 (PST)
From: <qpopper at thebitch.twosexygeeks dot com>
Subject: Re: I hope someone can help me.
I C.. I finally found all that info. Does anyone know if they are going
to write the code into qpopper to ignore that message?
On Fri, 11 Feb 2000, Jeremy C. Reed wrote:
> On Fri, 11 Feb 2000 qpopper at thebitch.twosexygeeks dot com wrote:
>
> > I'm the sys admin at an ISP. For our mail I currently run sendmail and
> > qpopper3.0b30 and all of my customers are now getting the e-mail from
> > MAILER_DAEMON at mydoman dot net that says.
> > Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
>
> http://www.washington.edu/pine/faq/problems.html#pseudo-message
>
> > I believe that is something that is placed there because of
> > sendmail. However I would like to continue using sendmail but my
> > customers are getting irritated about this E-Mail. Could anyone point me
> > in the right direction to get this fixed? Thanks.
>
> This message is used by UW email software (pine, imap, popd).
> Did you recently change to qpopper?
>
> (This should be added to the qpopper faq.)
>
> Jeremy C. Reed
> ....................................................
> BSD software, documentation, resources, news...
> http://bsd.reedmedia.net
>
Date: Sun, 13 Feb 2000 13:41:51 -0500
From: Tadeusz Wiewiorowski <twiewior at toronto.cbc dot ca>
Subject: 3.0b24 on HP-UX 10.20
1.I have compiled 3.0b24 with only "enable-servermode" option,
but when I run it my popper.log contains "debug/trace" entries
from maillock/mailunlock/genpath .
2. I do have -s "RUN-TIME" option and -t [pointing to
/var/adm/syslog/popper.log]
but still no statistics .
Any idea why ?
Tadeusz Wiewiorowski
CBC
twiewior at toronto.cbc dot ca
Date: Sat, 12 Feb 2000 16:44:49 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: I hope someone can help me.
At 6:17 PM -0800 2/11/00, qpopper at thebitch.twosexygeeks dot com wrote:
>Does anyone know if they are going
>to write the code into qpopper to ignore that message?
This is something that will be looked at, to see if it can be done for 3.0.
Date: Sat, 12 Feb 2000 11:12:32 +0100
From: hypnose at t-online dot de (guenter wessling)
Subject: aliasing /problem solved
Hi, all.
Thanks a lot.
Just putting
´mydomain.de IN A 123.123.123.123´
in addition to
´servername.mydomain.de IN A 123.123.123.123´
to the dns-files solved the problem.
qpopper accepts all requests for "....@mydomain.de" now.
I did *not* change MX records.
guenter
guenter wessling (hypnose at t-online dot de)
http://home.t-online.de/home/hypnose
Date: Mon, 14 Feb 2000 09:02:24 +0100
From: Torbjorn Astlind <torbjorn at biophys.su dot se>
Subject: APOP password proplem
Hi all,
I find there is a difference about what passwords are usable with APOP
than with std authentication. Only letters and number characters seems to
be allowed with APOP. What are the rules? Could this be a character
mapping problem when changing password with popauth or is it in Eudora?
Any info or advice how to find out is most welcome.
Torbjörn
Torbjorn Astlind, research engineer Tel. INT + (0)8 - 162431
Dept. of Biophysics
The Arrhenius laboratories Fax. INT + (0)8 - 155597
Stockholm University
S - 10691 Stockholm e-mail torbjorn at biophys.su dot se
Sweden
Date: Mon, 14 Feb 2000 11:11:48 -0600
From: "Julian Y. Koh" <kohster at mac dot com>
Subject: Re: APOP password proplem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 09:02 +0100 2/14/2000, Torbjorn Astlind wrote:
>Hi all,
>I find there is a difference about what passwords are usable with APOP
>than with std authentication. Only letters and number characters seems to
>be allowed with APOP.
Hmmm...I don't have any problems using punctuation, letters, and numbers
in APOP passwords...
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.2
Comment: <http://charlotte.at.nwu.edu/julian/pgppubkey.html>
iQA/AwUBOKg3Uw5UB5zJHgFjEQJd3wCaA3HQs+WDcOnEq5z7yEW66FR3smsAnRB5
pC5QT2SqC+91AObSfKLTRNAI
ïWN
-----END PGP SIGNATURE-----
--
Julian Y. Koh
kohster at mac dot com
PGP Key: <http://charlotte.at.nwu.edu/julian/pgppubkey.html>
Date: Mon, 14 Feb 2000 14:14:58 -0600
From: "Neil R. Smith" <neils at ariel.met.tamu dot edu>
Subject: Failed make on IRIX: -ldir
I'm having trouble getting successful make on IRIX 6.4. This with
both native compiler cc and gcc (vendor-supplied distribution).
Make bails after warning limit of 50. Is there a know problem
or workaround for IRIX? Seems "-ldir" doesn't work.
Can someone help me out on diagnosing the problem?
Here is config.log
configure -------------------------------------
# ./configure
creating cache ./config.cache
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for POSIXized ISC... no
Will NOT compile in debugging code
checking size of unsigned long int... 4
checking for sendmail program... found at /usr/lib/sendmail
checking for mail spool directory... found at /usr/mail
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for prot.h... no
checking for fcntl.h... yes
checking for strings.h... yes
checking for sys/param.h... yes
checking for sys/file.h... yes
checking for sys/security.h... no
checking for sys/syslog.h... yes
checking for sys/types.h... yes
checking for sys/fcntl.h... yes
checking for sys/stat.h... yes
checking for sys/unistd.h... yes
checking for sys/netinet/in.h... no
checking for syslog.h... yes
checking for net/errno.h... no
checking for unistd.h... yes
checking for netinet/in.h... yes
checking for maillock.h... no
checking for ndbm.h... yes
checking for gdbm.h... no
checking for dbm.h... yes
checking for shadow.h... yes
checking for t_accept in -lnsl... yes
checking for socket in -lsocket... yes
checking for res_init in -lresolv... no
checking for maillock in -lmail... no
checking for krb_recvauth in -lkrb... no
checking for dbm_open in -lndbm... no
checking for dbm_open in -ldbm... no
checking for gdbm_open in -lgdbm... no
checking for set_auth_parameters in -lsecurity... no
checking for crypt in -lcrypt... yes
checking for pw_encrypt in -lshadow... no
checking for working const... yes
checking for uid_t in sys/types.h... yes
checking for off_t... yes
checking for size_t... yes
checking for sys_siglist declaration in signal.h or unistd.h... no
checking return type of signal handlers... void
checking for vprintf... yes
checking for gethostname... yes
checking for getusershell... no
checking for strdup... yes
checking for strerror... yes
checking for bcopy... yes
checking for index... yes
checking for flock... yes
checking for set_auth_parameters... no
checking for pw_encrypt... no
checking for ftruncate... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating config.h
make ---------------------------------------------
# make
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX flock.c -o flock.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_dele.c -o pop_dele.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_dropcopy.c -o pop_dropcopy.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_get_command.c -o pop_get_command.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_get_subcommand.c -o
pop_get_subcommand.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_init.c -o pop_init.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_last.c -o pop_last.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_list.c -o pop_list.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_log.c -o pop_log.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_lower.c -o pop_lower.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_msg.c -o pop_msg.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_parse.c -o pop_parse.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_pass.c -o pop_pass.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_quit.c -o pop_quit.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_rset.c -o pop_rset.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_send.c -o pop_send.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_stat.c -o pop_stat.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_updt.c -o pop_updt.o
gcc: unrecognized option `-cckr'
pop_updt.c:44: warning: `BBSIZE' redefined
/usr/include/sys/param.h:290: warning: this is the location of the
previous definition
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_user.c -o pop_user.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_xtnd.c -o pop_xtnd.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_xmit.c -o pop_xmit.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX popper.c -o popper.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_bull.c -o pop_bull.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX xtnd_xlst.c -o xtnd_xlst.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_uidl.c -o pop_uidl.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX mktemp.c -o mktemp.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_rpop.c -o pop_rpop.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_apop.c -o pop_apop.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX md5.c -o md5.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_auth.c -o pop_auth.o
gcc: unrecognized option `-cckr'
gcc flock.o pop_dele.o pop_dropcopy.o pop_get_command.o
pop_get_subcommand.o pop_init.o pop_last.o pop_list.o pop_log.o
pop_lower.o pop_msg.o pop_parse.o pop_pass.o pop_quit.o pop_rset.o
pop_send.o pop_stat.o pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o
popper.o pop_bull.o xtnd_xlst.o pop_uidl.o mktemp.o pop_rpop.o
pop_apop.o md5.o pop_auth.o -o popper -lnsl -lsocket -lcrypt
ld32: WARNING 84: /usr/lib32/libsocket.so is not used for resolving any
symbol.
ld3# make
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX flock.c -o flock.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_dele.c -o pop_dele.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_dropcopy.c -o pop_dropcopy.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_get_command.c -o pop_get_command.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_get_subcommand.c -o
pop_get_subcommand.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_init.c -o pop_init.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_last.c -o pop_last.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_list.c -o pop_list.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_log.c -o pop_log.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_lower.c -o pop_lower.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_msg.c -o pop_msg.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_parse.c -o pop_parse.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_pass.c -o pop_pass.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_quit.c -o pop_quit.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_rset.c -o pop_rset.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_send.c -o pop_send.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_stat.c -o pop_stat.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_updt.c -o pop_updt.o
gcc: unrecognized option `-cckr'
pop_updt.c:44: warning: `BBSIZE' redefined
/usr/include/sys/param.h:290: warning: this is the location of the
previous definition
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_user.c -o pop_user.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_xtnd.c -o pop_xtnd.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_xmit.c -o pop_xmit.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX popper.c -o popper.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_bull.c -o pop_bull.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX xtnd_xlst.c -o xtnd_xlst.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_uidl.c -o pop_uidl.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX mktemp.c -o mktemp.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_rpop.c -o pop_rpop.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_apop.c -o pop_apop.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX md5.c -o md5.o
gcc: unrecognized option `-cckr'
gcc -c -I. -I. -g -O2 -fstrength-reduce -fpcc-struct-return
-DHAVE_CONFIG_H -cckr -DIRIX pop_auth.c -o pop_auth.o
gcc: unrecognized option `-cckr'
gcc flock.o pop_dele.o pop_dropcopy.o pop_get_command.o
pop_get_subcommand.o pop_init.o pop_last.o pop_list.o pop_log.o
pop_lower.o pop_msg.o pop_parse.o pop_pass.o pop_quit.o pop_rset.o
pop_send.o pop_stat.o pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o
popper.o pop_bull.o xtnd_xlst.o pop_uidl.o mktemp.o pop_rpop.o
pop_apop.o md5.o pop_auth.o -o popper -lnsl -lsocket -lcrypt
ld32: WARNING 84: /usr/lib32/libsocket.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
.
.
.
ld32: Giving up after printing 50 warnings. Use -wall to print all
warnings.
config.log -----------------------------------------------
config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:537: checking whether make sets ${MAKE}
configure:566: checking for gcc
configure:643: checking whether the C compiler (gcc ) works
configure:657: gcc -o conftest conftest.c 1>&5
configure:677: checking whether the C compiler (gcc ) is a
cross-compiler
configure:682: checking whether we are using GNU C
configure:691: gcc -E conftest.c
configure:706: checking whether gcc accepts -g
configure:734: checking for POSIXized ISC
configure:1018: checking size of unsigned long int
configure:1037: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c 1>&5
configure:1058: checking for sendmail program
configure:1085: checking for mail spool directory
configure:1168: checking how to run the C preprocessor
configure:1189: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1229: checking for ANSI C header files
configure:1242: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1309: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c 1>&5
configure:1337: checking for dirent.h that defines DIR
configure:1350: gcc -c -g -O2 -fstrength-reduce -fpcc-struct-return
conftest.c 1>&5
configure:1375: checking for opendir in -ldir
configure:1394: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -ldir 1>&5
ld32: FATAL 9: I/O error (-ldir): No such file or directory
configure: failed program was:
#line 1383 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char opendir();
int main() {
opendir()
; return 0; }
configure:1458: checking for sys/wait.h that is POSIX.1 compatible
configure:1479: gcc -c -g -O2 -fstrength-reduce -fpcc-struct-return
conftest.c 1>&5
configure:1525: checking for prot.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: prot.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <prot.h>
configure:1525: checking for fcntl.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for strings.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/param.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/file.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/security.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: sys/security.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <sys/security.h>
configure:1525: checking for sys/syslog.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/types.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/fcntl.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/stat.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/unistd.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for sys/netinet/in.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: sys/netinet/in.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <sys/netinet/in.h>
configure:1525: checking for syslog.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for net/errno.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: net/errno.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <net/errno.h>
configure:1525: checking for unistd.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for netinet/in.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for maillock.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: maillock.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <maillock.h>
configure:1525: checking for ndbm.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for gdbm.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1531: gdbm.h: No such file or directory
configure: failed program was:
#line 1530 "configure"
#include "confdefs.h"
#include <gdbm.h>
configure:1525: checking for dbm.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1525: checking for shadow.h
configure:1535: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1564: checking for t_accept in -lnsl
configure:1583: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lnsl 1>&5
ld32: WARNING 134: weak definition of ffs in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _ffs in /usr/lib32/libnsl.so preempts
that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_create in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_create_vers in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _clnt_create_vers in
/usr/lib32/libnsl.so preempts that definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_sperror in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_perror in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_sperrno in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_perrno in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _clnt_perrno in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_spcreateerror in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_pcreateerror in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _clntraw_create in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clntraw_create in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of callrpc in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _callrpc in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnttcp_create in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clntudp_bufcreate in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clntudp_create in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of netname2user in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _netname2user in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of netname2host in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _netname2host in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of getnetname in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _getnetname in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of user2netname in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of host2netname in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of pmap_set in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of pmap_unset in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _pmap_getmaps in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of pmap_getmaps in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of pmap_getport in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_pmap in /usr/lib32/libnsl.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_pmaplist in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of pmap_rmtcall in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _pmap_rmtcall in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_rmtcall_args in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_rmtcallres in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _clnt_broadcast in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of clnt_broadcast in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_callmsg in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_opaque_auth in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _xdr_des_block in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_des_block in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_accepted_reply in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_rejected_reply in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_replymsg in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of xdr_callhdr in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of svcraw_create in
/usr/lib32/libnsl.so preempts that weak definition in
/usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _svcraw_create in /usr/lib32/libnsl.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: Giving up after printing 50 warnings. Use -wall to print all
warnings.
configure:1604: checking for socket in -lsocket
configure:1623: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lsocket 1>&5
ld32: WARNING 84: /usr/lib32/libsocket.so is not used for resolving any
symbol.
configure:1644: checking for res_init in -lresolv
configure:1663: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lresolv 1>&5
ld32: FATAL 9: I/O error (-lresolv): No such file or directory
configure: failed program was:
#line 1652 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char res_init();
int main() {
res_init()
; return 0; }
configure:1684: checking for maillock in -lmail
configure:1703: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lmail 1>&5
ld32: FATAL 9: I/O error (-lmail): No such file or directory
configure: failed program was:
#line 1692 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char maillock();
int main() {
maillock()
; return 0; }
configure:1727: checking for krb_recvauth in -lkrb
configure:1746: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lkrb 1>&5
ld32: FATAL 9: I/O error (-lkrb): No such file or directory
configure: failed program was:
#line 1735 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char krb_recvauth();
int main() {
krb_recvauth()
; return 0; }
configure:1767: checking for dbm_open in -lndbm
configure:1786: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lndbm 1>&5
ld32: FATAL 9: I/O error (-lndbm): No such file or directory
configure: failed program was:
#line 1775 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char dbm_open();
int main() {
dbm_open()
; return 0; }
configure:1807: checking for dbm_open in -ldbm
configure:1826: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -ldbm 1>&5
ld32: FATAL 9: I/O error (-ldbm): No such file or directory
configure: failed program was:
#line 1815 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char dbm_open();
int main() {
dbm_open()
; return 0; }
configure:1847: checking for gdbm_open in -lgdbm
configure:1866: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lgdbm 1>&5
ld32: FATAL 9: I/O error (-lgdbm): No such file or directory
configure: failed program was:
#line 1855 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char gdbm_open();
int main() {
gdbm_open()
; return 0; }
configure:1890: checking for set_auth_parameters in -lsecurity
configure:1909: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lsecurity 1>&5
ld32: FATAL 9: I/O error (-lsecurity): No such file or directory
configure: failed program was:
#line 1898 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char set_auth_parameters();
int main() {
set_auth_parameters()
; return 0; }
configure:1930: checking for crypt in -lcrypt
configure:1949: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:1970: checking for pw_encrypt in -lshadow
configure:1989: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lshadow -lcrypt 1>&5
ld32: FATAL 9: I/O error (-lshadow): No such file or directory
configure: failed program was:
#line 1978 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char pw_encrypt();
int main() {
pw_encrypt()
; return 0; }
configure:2017: checking for working const
configure:2071: gcc -c -g -O2 -fstrength-reduce -fpcc-struct-return
conftest.c 1>&5
configure:2092: checking for uid_t in sys/types.h
configure:2126: checking for off_t
configure:2159: checking for size_t
configure:2192: checking for sys_siglist declaration in signal.h or
unistd.h
configure:2209: gcc -c -g -O2 -fstrength-reduce -fpcc-struct-return
conftest.c 1>&5
configure: In function `main':
configure:2205: `sys_siglist' undeclared (first use in this function)
configure:2205: (Each undeclared identifier is reported only once
configure:2205: for each function it appears in.)
configure: failed program was:
#line 2197 "configure"
#include "confdefs.h"
#include <sys/types.h>
#include <signal.h>
/* NetBSD declares sys_siglist in unistd.h. */
#ifdef HAVE_UNISTD_H
#include <unistd.h>
#endif
int main() {
char *msg = *(sys_siglist + 1);
; return 0; }
configure:2231: checking return type of signal handlers
configure:2253: gcc -c -g -O2 -fstrength-reduce -fpcc-struct-return
conftest.c 1>&5
configure:2272: checking for vprintf
configure:2300: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for gethostname
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for getusershell
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: ERROR 33: Unresolved text symbol "getusershell" -- 1st referenced
by /var/tmp/cca001p11.o.
Use linker option -v to see when and which objects, archives and
dsos are loaded.
ld32: INFO 152: Output file removed because of error.
configure: failed program was:
#line 2395 "configure"
#include "confdefs.h"
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char getusershell(); below. */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char getusershell();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_getusershell) || defined (__stub___getusershell)
choke me
#else
getusershell();
#endif
; return 0; }
configure:2390: checking for strdup
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for strerror
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for bcopy
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for index
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for flock
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
configure:2390: checking for set_auth_parameters
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: ERROR 33: Unresolved text symbol "set_auth_parameters" -- 1st
referenced by /var/tmp/cca001px1.o.
Use linker option -v to see when and which objects, archives and
dsos are loaded.
ld32: INFO 152: Output file removed because of error.
configure: failed program was:
#line 2395 "configure"
#include "confdefs.h"
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char set_auth_parameters(); below. */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char set_auth_parameters();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_set_auth_parameters) || defined
(__stub___set_auth_parameters)
choke me
#else
set_auth_parameters();
#endif
; return 0; }
configure:2390: checking for pw_encrypt
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: ERROR 33: Unresolved text symbol "pw_encrypt" -- 1st referenced by
/var/tmp/cca001q51.o.
Use linker option -v to see when and which objects, archives and
dsos are loaded.
ld32: INFO 152: Output file removed because of error.
configure: failed program was:
#line 2395 "configure"
#include "confdefs.h"
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char pw_encrypt(); below. */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char pw_encrypt();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_pw_encrypt) || defined (__stub___pw_encrypt)
choke me
#else
pw_encrypt();
#endif
; return 0; }
configure:2390: checking for ftruncate
configure:2418: gcc -o conftest -g -O2 -fstrength-reduce
-fpcc-struct-return conftest.c -lcrypt 1>&5
ld32: WARNING 84: /usr/lib32/libcrypt.so is not used for resolving any
symbol.
ld32: WARNING 134: weak definition of setkey in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of encrypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 134: weak definition of crypt in /usr/lib32/libcrypt.so
preempts that weak definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _crypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _setkey in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
ld32: WARNING 85: definition of _encrypt in /usr/lib32/libcrypt.so
preempts that definition in /usr/lib32/mips3/libc.so.
--
Neil R. Smith, Comp. Sys. Mngr. neils at ariel.met.tamu dot edu
Dept. Atmospheric Sci., Texas A&M Univ. 409/845-6272 FAX:409/862-4466
Date: Mon, 14 Feb 2000 16:18:18 -0500
From: Joseph S D Yao <jsdy at cospo.osis dot gov>
Subject: Re: swap issue
On Tue, Jan 25, 2000 at 07:18:17PM -0800, Rich Quinn wrote:
> I have a Solaris 2.7 box that serves as my DNS server as well as mail
> server.
> It runs both postfix and Qpop.
...
> I get an error about the system not being able to start up any more shells.
>
> I also get an error about the system being out of swap space.
...
> Jan 25 15:27:14 mybox postfix/smtpd[13042]: fatal: mymalloc: insufficient
> memory: Resource temporarily unavailable
> Jan 25 15:27:15 mybox inetd[136]: pop3[13047] from 198.XXX.XX.XX 3183
> Jan 25 15:27:16 mybox unix: WARNING: Sorry, no swap space to grow stack for
> pid 13047 (popper-3.0)
It's hard to tell whether this is a problem with 'postfix' growing out
of bounds, or 'popper' doing too many function calls, or something else
entirely eating up all of your swap space. You will have to have
something monitor this and record it up to just prior to the time you
have to power-cycle it.
Please be aware that Solaris systems have tended to put the "/tmp" file
system on swap! If you have lots of /tmp usage [and if 2.7 follows
this trend], that WILL eat up your swap space. If I have the disk
space, I tend to make separate /tmp and swap disk partitions.
--
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, 14 Feb 2000 19:00:20 -0500
From: Joseph S D Yao <jsdy at cospo.osis dot gov>
Subject: Re: Qpopper 3.0b34 available
On Thu, Feb 10, 2000 at 07:06:04PM -0800, Qpopper Support wrote:
> Qpopper 3.0b34 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 beta 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>.
You know, you don't need to rush these changes out if testing quality
suffers.
> Changes from 3.0b33 to 3.0b34
> -----------------------------
>
> 1. Remove CRs in some files.
=======================================================================
PROBLEM 1
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
===== popper/scram.c =====
19d18
<
193,196c192,193
< hmac_md5( (unsigned char *)packet,
< plen,
< icontrols->prefix,
< SCRAM_MD5_COUNTSIZE + HMAC_MD5_SIZE,
---
> hmac_md5( packet, plen,^M
> icontrols->prefix, SCRAM_MD5_COUNTSIZE+HMAC_MD5_SIZE,^M
[carriage returns]
=======================================================================
> 2. Make len param of StrNCat0 const to agree with .h
=======================================================================
PROBLEM 2
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
===== mmangle/utils.c =====
137c128
< void StrNCat0(char *dest, const char *src, const int len)
---
> void StrNCat0(char *dest, const char *src, int len)
but there is a "--len" in StrNCat0(), and a strict ANSI compiler [like
HP/UX ANSI C for HP/UX 10.20] absolutely forbids you to decrement a
constant!
=======================================================================
=======================================================================
PROBLEM 3
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Also, how does testing isupper(*mp) twice enhance the following code?
===== popper/pop_lower.c =====
...
28,30c21,22
...
< if ( isupper ( *mp ) )
< *mp = (char) tolower ( (int)*mp );
---
...
> if (isupper(*mp) && isupper(*mp)) *mp = (char)tolower((int)*mp);
=======================================================================
--
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, 14 Feb 2000 16:55:02 -0800 (PST)
From: Jim Warren <jim at coam dot net>
Subject: qpopper beta and compiling on linux?
I have tried compiling the most recent beta on Redhat 5.2 and 6.1, using
the configure script....... on both systems the make bombs out with two
pages of errors...... am I missing something glaring about compiling on
linux? Havent been able to find any references in the docs yet that even
hint at solutions......
thanks...
Jim Warren Connecting America
jim at coam.net www.coam dot net
Phone: 702-648-0390 Fax: 702-631-3303
Direct: 648-2712
From: "Benjamin Hyatt" <benski at pacbell dot net>
Subject: RE: qpopper beta and compiling on linux?
Date: Mon, 14 Feb 2000 17:15:38 -0800
Can you be a bit more specific?
i.e what parameters are you passing ./configure ???
What version of gcc? and the most helpful would be a summary
of the page(s) of errors your getting.
. Ben
> -----Original Message-----
> From: Jim Warren [mailto:jim at coam dot net]
> Sent: Monday, February 14, 2000 4:55 PM
> To: Subscribers of Qpopper
> Subject: qpopper beta and compiling on linux?
> Importance: High
>
>
> I have tried compiling the most recent beta on Redhat 5.2 and 6.1, using
> the configure script....... on both systems the make bombs out with two
> pages of errors...... am I missing something glaring about compiling on
> linux? Havent been able to find any references in the docs yet that even
> hint at solutions......
>
> thanks...
>
> Jim Warren Connecting America
> jim at coam.net www.coam dot net
> Phone: 702-648-0390 Fax: 702-631-3303
> Direct: 648-2712
>
Date: Mon, 14 Feb 2000 17:26:25 -0800 (PST)
From: Jim Warren <jim at coam dot net>
Subject: RE: qpopper beta and compiling on linux?
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.
--215059433-2063522311-950577985=:1792
Content-Type: TEXT/PLAIN; charset=US-ASCII
see attached for output of make with configure options.... and gcc version
output (gcc -v)
also, i havent compared line for line, but it looks like pretty much the
same results if i run configure with no options at all..... :-(
Jim Warren Connecting America
jim at coam.net www.coam dot net
Phone: 702-648-0390 Fax: 702-631-3303
Direct: 648-2712
On Mon, 14 Feb 2000, Benjamin Hyatt wrote:
> Date: Mon, 14 Feb 2000 17:15:38 -0800
> From: Benjamin Hyatt <benski at pacbell dot net>
> To: Jim Warren <jim at coam dot net>,
> Subscribers of Qpopper <qpopper at lists.pensive dot org>
> Subject: RE: qpopper beta and compiling on linux?
>
> Can you be a bit more specific?
> i.e what parameters are you passing ./configure ???
>
> What version of gcc? and the most helpful would be a summary
> of the page(s) of errors your getting.
>
> . Ben
>
> > -----Original Message-----
> > From: Jim Warren [mailto:jim at coam dot net]
> > Sent: Monday, February 14, 2000 4:55 PM
> > To: Subscribers of Qpopper
> > Subject: qpopper beta and compiling on linux?
> > Importance: High
> >
> >
> > I have tried compiling the most recent beta on Redhat 5.2 and 6.1, using
> > the configure script....... on both systems the make bombs out with two
> > pages of errors...... am I missing something glaring about compiling on
> > linux? Havent been able to find any references in the docs yet that even
> > hint at solutions......
> >
> > thanks...
> >
> > Jim Warren Connecting America
> > jim at coam.net www.coam dot net
> > Phone: 702-648-0390 Fax: 702-631-3303
> > Direct: 648-2712
> >
>
--215059433-2063522311-950577985=:1792
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=out1
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.3.96.1000214172625.1792P at thar.coam dot net>
Content-Description:
DQpDb25maWd1cmUgcnVuIHdpdGggdGhlIGZvbGxvd2luZzoNCg0KLi9jb25m
aWd1cmUgLS1lbmFibGUtc2VydmVybW9kZSBcDQotLWVuYWJsZS1idWxsZXRp
bnM9L3Zhci9zcG9vbC9idWxscyBcDQotLWVuYWJsZS1idWxsZGI9L3Zhci9z
cG9vbC9idWxscyBcDQotLWVuYWJsZS1wb3BidWxsZGlyPS92YXIvc3Bvb2wv
cG9wYnVsbCBcDQotLWVuYWJsZS1kZWJ1Z2dpbmcNCg0KIyMjIyMjIyMjIyBv
dXRwdXQgb2YgbWFrZSBpczoNCg0KDQoNCmNkIC4vcG9wcGVyICAmJiBtYWtl
IGFsbA0KbWFrZVsxXTogRW50ZXJpbmcgZGlyZWN0b3J5IGAvdXNyL2xvY2Fs
L3NyYy9xcG9wcGVyMy4wYjM0L3BvcHBlcicNCmdjYyAtYyAtSS4uIC1JLi4g
LUkuIC1JLi4vbW1hbmdsZSAtSS4uL2NvbW1vbiBcDQotZyAtTzIgLWZwY2Mt
c3RydWN0LXJldHVybiAgLURIQVZFX0NPTkZJR19IICAtRExJTlVYIC1EVU5J
WCBwb3BfZGVsZS5jIC1vIHBvcF9kZWxlLm8NCkluIGZpbGUgaW5jbHVkZWQg
ZnJvbSAvdXNyL2luY2x1ZGUvc3RkaW8uaDozMywNCiAgICAgICAgICAgICAg
ICAgZnJvbSBwb3BfZGVsZS5jOjg6DQovdXNyL2xpYi9nY2MtbGliL2kzODYt
cmVkaGF0LWxpbnV4L2VnY3MtMi45MS42Ni9pbmNsdWRlL3N0ZGRlZi5oOjE3
MDogd2FybmluZzogZW1wdHkgZGVjbGFyYXRpb24NCkluIGZpbGUgaW5jbHVk
ZWQgZnJvbSBwb3BfZGVsZS5jOjExOg0KcG9wcGVyLmg6NTE3OiB3YXJuaW5n
OiBwYXJhbWV0ZXIgbmFtZXMgKHdpdGhvdXQgdHlwZXMpIGluIGZ1bmN0aW9u
IGRlY2xhcmF0aW9uDQpwb3BwZXIuaDo1MTg6IHdhcm5pbmc6IHBhcmFtZXRl
ciBuYW1lcyAod2l0aG91dCB0eXBlcykgaW4gZnVuY3Rpb24gZGVjbGFyYXRp
b24NCmdjYyAtYyAtSS4uIC1JLi4gLUkuIC1JLi4vbW1hbmdsZSAtSS4uL2Nv
bW1vbiBcDQotZyAtTzIgLWZwY2Mtc3RydWN0LXJldHVybiAgLURIQVZFX0NP
TkZJR19IICAtRExJTlVYIC1EVU5JWCBwb3BfZHJvcGNvcHkuYyAtbyBwb3Bf
ZHJvcGNvcHkubw0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3IvaW5jbHVk
ZS9zdGRpby5oOjMzLA0KICAgICAgICAgICAgICAgICBmcm9tIHBvcF9kcm9w
Y29weS5jOjc4Og0KL3Vzci9saWIvZ2NjLWxpYi9pMzg2LXJlZGhhdC1saW51
eC9lZ2NzLTIuOTEuNjYvaW5jbHVkZS9zdGRkZWYuaDoxNzA6IHdhcm5pbmc6
IGVtcHR5IGRlY2xhcmF0aW9uDQpJbiBmaWxlIGluY2x1ZGVkIGZyb20gcG9w
X2Ryb3Bjb3B5LmM6MTA2Og0KcG9wcGVyLmg6NTE3OiB3YXJuaW5nOiBwYXJh
bWV0ZXIgbmFtZXMgKHdpdGhvdXQgdHlwZXMpIGluIGZ1bmN0aW9uIGRlY2xh
cmF0aW9uDQpwb3BwZXIuaDo1MTg6IHdhcm5pbmc6IHBhcmFtZXRlciBuYW1l
cyAod2l0aG91dCB0eXBlcykgaW4gZnVuY3Rpb24gZGVjbGFyYXRpb24NCmdj
YyAtYyAtSS4uIC1JLi4gLUkuIC1JLi4vbW1hbmdsZSAtSS4uL2NvbW1vbiBc
DQotZyAtTzIgLWZwY2Mtc3RydWN0LXJldHVybiAgLURIQVZFX0NPTkZJR19I
ICAtRExJTlVYIC1EVU5JWCBwb3BfZ2V0X2NvbW1hbmQuYyAtbyBwb3BfZ2V0
X2NvbW1hbmQubw0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3IvaW5jbHVk
ZS9zdGRpby5oOjMzLA0KICAgICAgICAgICAgICAgICBmcm9tIHBvcF9nZXRf
Y29tbWFuZC5jOjEwOg0KL3Vzci9saWIvZ2NjLWxpYi9pMzg2LXJlZGhhdC1s
aW51eC9lZ2NzLTIuOTEuNjYvaW5jbHVkZS9zdGRkZWYuaDoxNzA6IHdhcm5p
bmc6IGVtcHR5IGRlY2xhcmF0aW9uDQpJbiBmaWxlIGluY2x1ZGVkIGZyb20g
cG9wX2dldF9jb21tYW5kLmM6MTY6DQpwb3BwZXIuaDo1MTc6IHdhcm5pbmc6
IHBhcmFtZXRlciBuYW1lcyAod2l0aG91dCB0eXBlcykgaW4gZnVuY3Rpb24g
ZGVjbGFyYXRpb24NCnBvcHBlci5oOjUxODogd2FybmluZzogcGFyYW1ldGVy
IG5hbWVzICh3aXRob3V0IHR5cGVzKSBpbiBmdW5jdGlvbiBkZWNsYXJhdGlv
bg0KZ2NjIC1jIC1JLi4gLUkuLiAtSS4gLUkuLi9tbWFuZ2xlIC1JLi4vY29t
bW9uIFwNCi1nIC1PMiAtZnBjYy1zdHJ1Y3QtcmV0dXJuICAtREhBVkVfQ09O
RklHX0ggIC1ETElOVVggLURVTklYIHBvcF9nZXRfc3ViY29tbWFuZC5jIC1v
IHBvcF9nZXRfc3ViY29tbWFuZC5vDQpJbiBmaWxlIGluY2x1ZGVkIGZyb20g
L3Vzci9pbmNsdWRlL3N0ZGlvLmg6MzMsDQogICAgICAgICAgICAgICAgIGZy
b20gcG9wX2dldF9zdWJjb21tYW5kLmM6MjA6DQovdXNyL2xpYi9nY2MtbGli
L2kzODYtcmVkaGF0LWxpbnV4L2VnY3MtMi45MS42Ni9pbmNsdWRlL3N0ZGRl
Zi5oOjE3MDogd2FybmluZzogZW1wdHkgZGVjbGFyYXRpb24NCkluIGZpbGUg
aW5jbHVkZWQgZnJvbSBwb3BfZ2V0X3N1YmNvbW1hbmQuYzoyODoNCnBvcHBl
ci5oOjUxNzogd2FybmluZzogcGFyYW1ldGVyIG5hbWVzICh3aXRob3V0IHR5
cGVzKSBpbiBmdW5jdGlvbiBkZWNsYXJhdGlvbg0KcG9wcGVyLmg6NTE4OiB3
YXJuaW5nOiBwYXJhbWV0ZXIgbmFtZXMgKHdpdGhvdXQgdHlwZXMpIGluIGZ1
bmN0aW9uIGRlY2xhcmF0aW9uDQpnY2MgLWMgLUkuLiAtSS4uIC1JLiAtSS4u
L21tYW5nbGUgLUkuLi9jb21tb24gXA0KLWcgLU8yIC1mcGNjLXN0cnVjdC1y
ZXR1cm4gIC1ESEFWRV9DT05GSUdfSCAgLURMSU5VWCAtRFVOSVggcG9wX2lu
aXQuYyAtbyBwb3BfaW5pdC5vDQpJbiBmaWxlIGluY2x1ZGVkIGZyb20gL3Vz
ci9pbmNsdWRlL3N0ZGlvLmg6MzMsDQogICAgICAgICAgICAgICAgIGZyb20g
cG9wX2luaXQuYzoxOToNCi91c3IvbGliL2djYy1saWIvaTM4Ni1yZWRoYXQt
bGludXgvZWdjcy0yLjkxLjY2L2luY2x1ZGUvc3RkZGVmLmg6MTcwOiB3YXJu
aW5nOiBlbXB0eSBkZWNsYXJhdGlvbg0KSW4gZmlsZSBpbmNsdWRlZCBmcm9t
IHBvcF9pbml0LmM6NTQ6DQpwb3BwZXIuaDo1MTc6IHdhcm5pbmc6IHBhcmFt
ZXRlciBuYW1lcyAod2l0aG91dCB0eXBlcykgaW4gZnVuY3Rpb24gZGVjbGFy
YXRpb24NCnBvcHBlci5oOjUxODogd2FybmluZzogcGFyYW1ldGVyIG5hbWVz
ICh3aXRob3V0IHR5cGVzKSBpbiBmdW5jdGlvbiBkZWNsYXJhdGlvbg0KcG9w
X2luaXQuYzo5MzogcGFyc2UgZXJyb3IgYmVmb3JlIGBfX2V4dGVuc2lvbl9f
Jw0KcG9wX2luaXQuYzo5MzogYF9fbGVuJyB1bmRlY2xhcmVkIGhlcmUgKG5v
dCBpbiBhIGZ1bmN0aW9uKQ0KcG9wX2luaXQuYzo5MzogaW5pdGlhbGl6ZXIg
ZWxlbWVudCBpcyBub3QgY29uc3RhbnQNCnBvcF9pbml0LmM6OTM6IHBhcnNl
IGVycm9yIGJlZm9yZSBgaWYnDQpwb3BfaW5pdC5jOjkzOiBjb25mbGljdGlu
ZyB0eXBlcyBmb3IgYF9fcmV0dmFsJw0KcG9wX2luaXQuYzo5MzogcHJldmlv
dXMgZGVjbGFyYXRpb24gb2YgYF9fcmV0dmFsJw0KcG9wX2luaXQuYzo5Mzog
d2FybmluZzogZGF0YSBkZWZpbml0aW9uIGhhcyBubyB0eXBlIG9yIHN0b3Jh
Z2UgY2xhc3MNCnBvcF9pbml0LmM6OTM6IHBhcnNlIGVycm9yIGJlZm9yZSBg
fScNCnBvcF9pbml0LmM6OTk6IGBzdHInIHVuZGVjbGFyZWQgaGVyZSAobm90
IGluIGEgZnVuY3Rpb24pDQpwb3BfaW5pdC5jOjk5OiBpbml0aWFsaXplciBl
bGVtZW50IGlzIG5vdCBjb25zdGFudA0KcG9wX2luaXQuYzo5OTogd2Fybmlu
ZzogZGF0YSBkZWZpbml0aW9uIGhhcyBubyB0eXBlIG9yIHN0b3JhZ2UgY2xh
c3MNCnBvcF9pbml0LmM6MTAwOiBwYXJzZSBlcnJvciBiZWZvcmUgYGlmJw0K
cG9wX2luaXQuYzogSW4gZnVuY3Rpb24gYHBvcF9pbml0JzoNCnBvcF9pbml0
LmM6MzI5OiBgTUFYSE9TVE5BTUVMRU4nIHVuZGVjbGFyZWQgKGZpcnN0IHVz
ZSBpbiB0aGlzIGZ1bmN0aW9uKQ0KcG9wX2luaXQuYzozMjk6IChFYWNoIHVu
ZGVjbGFyZWQgaWRlbnRpZmllciBpcyByZXBvcnRlZCBvbmx5IG9uY2UNCnBv
cF9pbml0LmM6MzI5OiBmb3IgZWFjaCBmdW5jdGlvbiBpdCBhcHBlYXJzIGlu
LikNCm1ha2VbMV06ICoqKiBbcG9wX2luaXQub10gRXJyb3IgMQ0KbWFrZVsx
XTogTGVhdmluZyBkaXJlY3RvcnkgYC91c3IvbG9jYWwvc3JjL3Fwb3BwZXIz
LjBiMzQvcG9wcGVyJw0KbWFrZTogKioqIFtwb3BwZXJfc2VydmVyXSBFcnJv
ciAyDQo=
--215059433-2063522311-950577985=:1792
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=out2
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.3.96.1000214172625.1792Q at thar.coam dot net>
Content-Description:
DQpSZWFkaW5nIHNwZWNzIGZyb20gL3Vzci9saWIvZ2NjLWxpYi9pMzg2LXJl
ZGhhdC1saW51eC9lZ2NzLTIuOTEuNjYvc3BlY3MNCmdjYyB2ZXJzaW9uIGVn
Y3MtMi45MS42NiAxOTk5MDMxNC9MaW51eCAoZWdjcy0xLjEuMiByZWxlYXNl
KQ0K
--215059433-2063522311-950577985=:1792--
Date: Mon, 14 Feb 2000 19:36:22 -0600
From: "Igor S. Livshits" <igorl at life.uiuc dot edu>
Subject: RE: qpopper beta and compiling on linux?
Make sure that you have the following packages:
glibc-devel
kernel-headers
you may also need gdbm-devel for bulletins and other stuff.
Cheers, igor
Date: Mon, 14 Feb 2000 18:25:37 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Qpopper 3.0b34 available
At 7:00 PM -0500 2/14/00, Joseph S D Yao wrote:
>
>> Changes from 3.0b33 to 3.0b34
>> -----------------------------
>>
>> 1. Remove CRs in some files.
>=======================================================================
> PROBLEM 1
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>===== popper/scram.c =====
>19d18
><
>193,196c192,193
>< hmac_md5( (unsigned char *)packet,
>< plen,
>< icontrols->prefix,
>< SCRAM_MD5_COUNTSIZE + HMAC_MD5_SIZE,
>---
> > hmac_md5( packet, plen,^M
>> icontrols->prefix, SCRAM_MD5_COUNTSIZE+HMAC_MD5_SIZE,^M
> [carriage returns]
I don't see this at all. When I open popper/scram.c I see:
> /* HMAC data portion of the packet: result into iproof */
>
> hmac_md5( (unsigned char *)packet,
> plen,
> icontrols->prefix,
> SCRAM_MD5_COUNTSIZE + HMAC_MD5_SIZE,
> icontrols->iproof );
>=======================================================================
> > 2. Make len param of StrNCat0 const to agree with .h
>=======================================================================
> PROBLEM 2
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>===== mmangle/utils.c =====
>137c128
>< void StrNCat0(char *dest, const char *src, const int len)
>---
>> void StrNCat0(char *dest, const char *src, int len)
>
>but there is a "--len" in StrNCat0(), and a strict ANSI compiler [like
>HP/UX ANSI C for HP/UX 10.20] absolutely forbids you to decrement a
>constant!
The fix has been checked-in and will be in b35.
>=======================================================================
>
>=======================================================================
> PROBLEM 3
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Also, how does testing isupper(*mp) twice enhance the following code?
>===== popper/pop_lower.c =====
>...
>28,30c21,22
>...
>< if ( isupper ( *mp ) )
>< *mp = (char) tolower ( (int)*mp );
>---
>...
>> if (isupper(*mp) && isupper(*mp)) *mp = (char)tolower((int)*mp);
>=======================================================================
I don't see the duplication. When I open popper/pop_lower.c, I see:
>void
>pop_lower ( buf )
>char * buf;
>{
> char * mp;
>
> for ( mp = buf; *mp != '\0'; mp++ )
> if ( isupper ( *mp ) )
> *mp = (char) tolower ( (int)*mp );
>}
Date: Mon, 14 Feb 2000 18:32:41 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: RE: qpopper beta and compiling on linux?
At 5:26 PM -0800 2/14/00, Jim Warren wrote:
>In file included from pop_dele.c:11:
>popper.h:517: warning: parameter names (without types) in function declaration
>popper.h:518: warning: parameter names (without types) in function declaration
Looks like STDC_HEADERS didn't get set by ./configure...do you have
the usual standard C headers, such as stdlib.h, stdarg.h, etc. in the
usual place? ./configure couldn't compile with them.
Date: Mon, 14 Feb 2000 23:55:37 -0800 (PST)
From: Jim Warren <jim at coam dot net>
Subject: RE: qpopper beta and compiling on linux?
actually, yes, it is just a stock installation (upgraded from rh 5.2):
/usr/include/stdlib.h
/usr/lib/bcc/include/bsd/stdlib.h
/usr/lib/bcc/include/stdlib.h
/usr/i386-glibc20-linux/include/stdlib.h
and,
locate stdarg.h
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/stdarg.h
/usr/lib/bcc/include/stdarg.h
Jim Warren Connecting America
jim at coam.net www.coam dot net
Phone: 702-648-0390 Fax: 702-631-3303
Direct: 648-2712
On Mon, 14 Feb 2000, Qpopper Support wrote:
> Date: Mon, 14 Feb 2000 18:32:41 -0800
> From: Qpopper Support <qpopper at qualcomm dot com>
> To: Jim Warren <jim at coam dot net>, Benjamin Hyatt <benski at pacbell dot net>
> Cc: Subscribers of Qpopper <qpopper at lists.pensive dot org>,
> qpopper at qualcomm dot com
> Subject: RE: qpopper beta and compiling on linux?
>
> At 5:26 PM -0800 2/14/00, Jim Warren wrote:
>
> >In file included from pop_dele.c:11:
> >popper.h:517: warning: parameter names (without types) in function declaration
> >popper.h:518: warning: parameter names (without types) in function declaration
>
> Looks like STDC_HEADERS didn't get set by ./configure...do you have
> the usual standard C headers, such as stdlib.h, stdarg.h, etc. in the
> usual place? ./configure couldn't compile with them.
>
Date: Tue, 15 Feb 2000 10:34:33 -0500
From: Karyn McCambridge <karynm at afb dot net>
Subject: Qpopper 2.5.3
I am running 2.5.3 on a Sun Solaris Server and notice sluggishness lately
that is intermittent. I was thinking that perhaps if I recompile enabling
server mode that may help. Any ideas?
Also if I recompile it how do I go about doing that?
Thanks
Date: Tue, 15 Feb 2000 19:04:08 +0200 (SAST)
From: Mihigo John <nmj at gorilla.nur.ac dot rw>
Subject: Re: Qpopper 2.5.3
nice way is to recompile your qpopper with a new release. It could happen
something not compatible. Try even your Sun compiler (cc or gcc normally
don't have problem)
*****************************
Mihigo John
National University of Rwanda
Computing Center
InternetWorking Administrator
Phone: 250 32147 (office)
08511917 (mobile)
Fax : 250 32142
URL: www.nur.ac.rw
BP: 56 Butare, Rwanda
On Tue, 15 Feb 2000, Karyn McCambridge wrote:
> I am running 2.5.3 on a Sun Solaris Server and notice sluggishness lately
> that is intermittent. I was thinking that perhaps if I recompile enabling
> server mode that may help. Any ideas?
>
> Also if I recompile it how do I go about doing that?
>
> Thanks
>
Date: Tue, 15 Feb 2000 12:53:27 -0500
From: Joseph S D Yao <jsdy at cospo.osis dot gov>
Subject: Re: Qpopper 3.0b34 available
On Mon, Feb 14, 2000 at 05:47:13PM -0800, Qpopper Support wrote:
> At 7:00 PM -0500 2/14/00, Joseph S D Yao wrote:
...
> >> 1. Remove CRs in some files.
...
> > [carriage returns]
>
> I don't see this at all. When I open popper/scram.c I see:
My apologies! In my haste, after finding the first bug, I did my mass
'diff' BACKWARDS - I found bugs that you had REMOVED.
Mea culpa, mea culpa, mea maxima culpa!
...
> > > 2. Make len param of StrNCat0 const to agree with .h
So this is the only real bug I reported.
...
> The fix has been checked-in and will be in b35.
...
> >Also, how does testing isupper(*mp) twice enhance the following code?
...
> I don't see the duplication. When I open popper/pop_lower.c, I see:
Again, did the 'diff' backwards. It was MY haste to report this that
caused two of the three reports, improperly. ;-/
--
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: Tue, 15 Feb 2000 20:09:22 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: spurious logging
Hi,
can anyone tell me why the 2 lines marked with *** are in pop_log.c,
firstly at line 116 we have
fprintf ( p->trace, "%s [%d] %s\n", date_time, getpid(), msgbuf );
*** fprintf ( p->trace, "%s \n", date_time );
and then at line 128
if ( p->debug && p->trace ) {
fprintf ( p->trace, "%s [%d] Buffer size exceeded logging msg:
%s\n
date_time, getpid(), format );
*** fprintf ( p->trace, "%s \n", date_time );
}
all they do is create is create an extra line in the log file every time
something is logged. This has been happenening for as long as I can
remember using qpopper and doesn't seem to have any purpose. Are they a
remnant from some previous logging code or am I missing something?
I'm using b31 by the way, so if they have been removed since then, just
ignore me,
Fergal
Date: Tue, 15 Feb 2000 14:46:48 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: spurious logging
At 8:09 PM +0000 2/15/00, Fergal Daly wrote:
>all they do is create is create an extra line in the log file every time
>something is logged. This has been happenening for as long as I can
>remember using qpopper and doesn't seem to have any purpose.
I always assumed the code was there to make the log easier to read,
by double-spacing the entries. Perhaps this should be an option.
Date: Tue, 15 Feb 2000 23:04:25 +0000
From: Fergal Daly <fergal at esatclear dot ie>
Subject: Re: spurious logging
At 14:46 15/02/00 -0800, Qpopper Support wrote:
>At 8:09 PM +0000 2/15/00, Fergal Daly wrote:
>
>>all they do is create is create an extra line in the log file every time
>>something is logged. This has been happenening for as long as I can
>>remember using qpopper and doesn't seem to have any purpose.
>
>I always assumed the code was there to make the log easier to read,
>by double-spacing the entries. Perhaps this should be an option.
I'd certainly like to see it as an option rather than a default. Our
poplogs are big enough as it is eg. in the last 43 hours our qpopper has
produced a log file with 223707 "Stats: " lines alone! As you can imagine
they are quite big and take a long time to search.
Most of the lines wrap around on an 80 column terminal anyway so double
spacing isn't much help.
Anyway, at least I know now that I can remove them without any ill effects,
thanks,
Fergal
Date: Tue, 15 Feb 2000 15:44:28 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: spurious logging
At 11:04 PM +0000 2/15/00, Fergal Daly wrote:
>Most of the lines wrap around on an 80 column terminal anyway so double
>spacing isn't much help.
I think that's why the double-spacing *does* help. It makes it clear
where one log entry ends and another begins.
Date: Tue, 15 Feb 2000 16:03:38 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Announcing: Qpopper-Announce
The much-requested, long-awaited Qpopper-Announce list is now
available. This is a low-volume list for announcements from Qualcomm
regarding Qpopper. This is the only traffic on the list. Any
discussion must continue to take place on this, the public,
non-official, mailing list.
To subscribe, send the word "subscribe" (without the quotes) as the
body of an email to <qpopper-announce-request at rohan.qualcomm dot com>.
Or, click here:
<mailto:qpopper-announce-request at rohan.qualcomm dot com?body=subscribe>
Please note that future announcements of new Qpopper versions will be
sent to the Qpopper-Announce list only (not to the public list).
Date: Wed, 16 Feb 2000 10:38:13 -0500 (EST)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: RADIUS auth testing
Ok, so I've been patching qpopper to do radius auth. I can do the
password/username checking fine, but now I need to get it to do it with 0
passwd/shadow entries (save system entries wheel, bin, blah blah)
To do this, i need the RADIUS to return (at least) the following (i'm
assuming)
a UID (integer)
a home directory (string)
allowed to retrieve mail? (possibly integer - 0/1, string - yes/no)
what i'm iffy on is GID. I've looked at the code but can someone explain
the use of this in qpopper and/or what it ensures/provides against so I
know if i'll have to also add this field in radius.
also, if anyone has any tips/thoughts on ALL this, things I should watch
out for, cavets, etc..email is welcome.
Thanx,
-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, 16 Feb 2000 11:12:15 -0500 (EST)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: Re: RADIUS auth testing
>
> A while back I submitted patches for qpop3 that would allow you to use a
> separate file (like a password file) to auth users. The intent was that
> rather than use up all of your system UIDs for mail-only users you could
> assign all of the mail-only users the same UID/GID and let the file point
> you to the proper directory in a general mail directory for dir/mailbox
> type boxes. It worked quite well and proved that the UID/GID didn't
> matter as long as the UID could write to the file or directory. The
> patch consisted of only two (I think) line additions to one file and a
> new file containing the auth code - which could be used with any kind of
> auth. If you're interested I should still have it hanging around and it
> would probably solve your problem.
>
what fields did the auth file contain?
The inherit problem I see with the popper process and the user mailfiles
being chowned to a common UID/GID is a security one. The possibility of a
user being able to access (read/write/delete) another user's mailfile.
What are the possiblities of this happening, and the implications?
Another little glitch I have is disk quotas..they go by specific UIDs to
work. Now I planned on putting quota fields also in my radius to forego
disk quotas on the machines themselves, but until I/someone has a way to
get sendmail/procmail to deliver mail A) without passwd entries but
against a RADIUS db to check user existance and B) check a RADIUS db for
disk quotas (obviously to see if it can quite a new message or not)
i'm kinda stuck on my whole project..i'm not too comfortable modifying the
sendmail/procmail source for fear of missing some needed modifications and
f***ing it up majorly. Wonder if anyone has done this.
-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, 16 Feb 2000 11:28:39 -0500 (EST)
From: Vince Vielhaber <vev at michvhf dot com>
Subject: Re: RADIUS auth testing
On Wed, 16 Feb 2000, Admin Mailing Lists wrote:
> >
> > A while back I submitted patches for qpop3 that would allow you to use a
> > separate file (like a password file) to auth users. The intent was that
> > rather than use up all of your system UIDs for mail-only users you could
> > assign all of the mail-only users the same UID/GID and let the file point
> > you to the proper directory in a general mail directory for dir/mailbox
> > type boxes. It worked quite well and proved that the UID/GID didn't
> > matter as long as the UID could write to the file or directory. The
> > patch consisted of only two (I think) line additions to one file and a
> > new file containing the auth code - which could be used with any kind of
> > auth. If you're interested I should still have it hanging around and it
> > would probably solve your problem.
> >
>
> what fields did the auth file contain?
> The inherit problem I see with the popper process and the user mailfiles
> being chowned to a common UID/GID is a security one. The possibility of a
> user being able to access (read/write/delete) another user's mailfile.
> What are the possiblities of this happening, and the implications?
Zero, since a mail-only user wouldn't have any kind of access to the
machine beyond POP3 and qpopper isn't going to give them someone else's
directory any more than it will now.
Side note.. Only admins have shell access.
> Another little glitch I have is disk quotas..they go by specific UIDs to
> work. Now I planned on putting quota fields also in my radius to forego
> disk quotas on the machines themselves, but until I/someone has a way to
> get sendmail/procmail to deliver mail A) without passwd entries but
> against a RADIUS db to check user existance and B) check a RADIUS db for
> disk quotas (obviously to see if it can quite a new message or not)
> i'm kinda stuck on my whole project..i'm not too comfortable modifying the
> sendmail/procmail source for fear of missing some needed modifications and
> f***ing it up majorly. Wonder if anyone has done this.
Dunno, I use qmail which will deliver mail without passwd entries and
I'm not currently using quotas, even for regular users.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev at michvhf.com http://www.pop4 dot net
128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Date: Wed, 16 Feb 2000 11:46:27 -0500 (EST)
From: Admin Mailing Lists <mlist at intergrafix dot net>
Subject: Re: RADIUS auth testing
>
> Zero, since a mail-only user wouldn't have any kind of access to the
> machine beyond POP3 and qpopper isn't going to give them someone else's
> directory any more than it will now.
>
umm, i think you mean 1 field (username?)
zero fields would mean the file was blank, no? :-)
-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, 16 Feb 2000 11:55:42 -0500 (EST)
From: Vince Vielhaber <vev at michvhf dot com>
Subject: Re: RADIUS auth testing
On Wed, 16 Feb 2000, Admin Mailing Lists wrote:
> >
> > Zero, since a mail-only user wouldn't have any kind of access to the
> > machine beyond POP3 and qpopper isn't going to give them someone else's
> > directory any more than it will now.
> >
>
> umm, i think you mean 1 field (username?)
> zero fields would mean the file was blank, no? :-)
I was answering this question:
> The inherit problem I see with the popper process and the user mailfiles
> being chowned to a common UID/GID is a security one. The possibility of a
> user being able to access (read/write/delete) another user's mailfile.
> What are the possiblities of this happening, and the implications?
The number of fields is six. username, password, uid, gid, homedir and
shell, although the only ones required are username, password and homedir.
The uid & gid are typically the same for all of the entries, but hardcoding
them in wasn't something I wanted to have.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev at michvhf.com http://www.pop4 dot net
128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Date: Wed, 16 Feb 2000 12:24:22 -0600
From: Brent <bierblb at netins dot net>
Subject: envelope error
Can anyone tell me what this error means?
-ERR Unable to process From lines (envelopes), change recognition modes.
Thanks for your help!
Brent
From: "Mike Giller" <mgiller at nwc dot net>
Date: Wed, 16 Feb 2000 10:25:23 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_0512_01BF7868.22677280
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
UNSUB
------=_NextPart_000_0512_01BF7868.22677280
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" =
http-equiv=Content-Type>
<META content="MSHTML 5.00.2314.1000" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>UNSUB</FONT></DIV></BODY></HTML>
------=_NextPart_000_0512_01BF7868.22677280--
From: "Julio" <jrilo at asturnet dot es>
Subject: XUIDL ....... error
Date: Wed, 16 Feb 2000 19:38:45 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0027_01BF78B5.6FE22AD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi, i'm having problems with Qpopper 3.0b34, i related it :
Some times, the users can't received his mail, because inside it =
appears a text just in the second line of the mail, this line is :
XUIDL: .............................
in this case we manually delete the line and all is OK, but only if i =
delete "manually" this line .... it's a problem when we are not here !
We are using Qpopper 3.0b34 in server mode, and sadow passwords with a =
Linux Slackware 2.0.38 and last version of Procmail ( ...14 ) and =
Sendmail.
I think the reason is that Procmail insert this line, or Qpopper, i =
don't now ... The qpopper team said me that it's a problem that resolve =
the last version of Qpopper and Procmail, but i do it and all it's =
unresolve.
Julio.
------=_NextPart_000_0027_01BF78B5.6FE22AD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" =
http-equiv=Content-Type>
<META content="MSHTML 5.00.2722.2800" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi, i'm having problems with Qpopper =
3.0b34, i
related it :</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Some times, the users can't =
received his
mail, because inside it appears a text just in the second line of the =
mail, this
line is :</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> XUIDL:
.............................</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>in this case we manually delete the =
line and all is
OK, but only if i delete "manually" this line .... it's a problem =
when we
are not here !</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>We are using Qpopper 3.0b34 in server =
mode, and
sadow passwords with a Linux Slackware 2.0.38 and last version of =
Procmail (
...14 ) and Sendmail. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I think the reason is that Procmail =
insert this
line, or Qpopper, i don't now ... The qpopper team said me that =
it's a
problem that resolve the last version of Qpopper and Procmail, but i do =
it and
all it's unresolve.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Julio.</FONT></DIV></BODY></HTML>
------=_NextPart_000_0027_01BF78B5.6FE22AD0--
From: "Jlinux" <jlinux at asturnet dot es>
Subject: RE: envelope error
Date: Wed, 16 Feb 2000 19:42:37 +0100
I've having a similar problem , i said our problem and temporal solution :
Inside the mail file appears a text just in the second line, this line is :
XUIDL: .............................
in this case we manually delete the line and all is OK, but only if i delete
"manually" this line .... it's a problem when we are not here !
----- Original Message -----
From: Brent <bierblb at netins dot net>
To: Subscribers of Qpopper <qpopper at lists.pensive dot org>
Sent: Wednesday, February 16, 2000 7:24 PM
Subject: envelope error
> Can anyone tell me what this error means?
>
> -ERR Unable to process From lines (envelopes), change recognition modes.
>
> Thanks for your help!
>
> Brent
>
Date: Wed, 16 Feb 2000 15:39:52 -0600
From: "Neil R. Smith" <neils at ariel.met.tamu dot edu>
Subject: Got successful make on IRIX?
I'm having trouble getting a workable popper in an
SGI Origin 200 running IRIX 6.4, which is an NIS client.
The /etc/passwd is not shadowed. I'm only specifying
a --prefix on the configure. Execution (telnet to the
110 port) results in message 'password supplied for _____
is incorrect'. The user is a valid NIS user with UID
far greater than 10. GID is < 10.
Has someone built popper on IRIX 6.4 or earlier running
as NIS client? Did you use extra configure flags, or
use some non-default macros in the Makefile? If you got
a correct make product that works, just what did you
do to get it? (I'm baffled)
Thanks, -Neil
--
Neil R. Smith, Comp. Sys. Mngr. neils at ariel.met.tamu dot edu
Dept. Atmospheric Sci., Texas A&M Univ. 409/845-6272 FAX:409/862-4466
Date: Wed, 16 Feb 2000 17:52:54 -0500
From: James Triplett <james at mail.th dot net>
Subject: Re: envelope error
The message is a cruel ruse, designed to make you run
back to your SMTP documents and figure out what an
"envelope" is, and what different "recognition modes"
popper might get itself into...
(at least I did, the first time I saw it)
More likely, it means there is a .pop-userlock file
lying around for this particular user. Check (with ls -l) your mail spool directory.
----james
On Wed, Feb 16, 2000 at 12:24:22PM -0600, Brent wrote:
> Can anyone tell me what this error means?
>
> -ERR Unable to process From lines (envelopes), change recognition modes.
>
> Thanks for your help!
>
> Brent
>
Date: Wed, 16 Feb 2000 15:24:47 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: envelope error
At 12:24 PM -0600 2/16/00, Brent wrote:
>Can anyone tell me what this error means?
>
>-ERR Unable to process From lines (envelopes), change recognition modes.
>
>Thanks for your help!
>
>Brent
See <http://www.eudora.com/qpopper/faq.html#from.lines>.
Date: Wed, 16 Feb 2000 17:07:00 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: envelope error
At 5:52 PM -0500 2/16/00, James Triplett wrote:
>The message is a cruel ruse, designed to make you run
>back to your SMTP documents and figure out what an
>"envelope" is, and what different "recognition modes"
>popper might get itself into...
>(at least I did, the first time I saw it)
Yes, and when chumps fall for it we all cackle and rub our hands.
Seriously, the message indicates that Qpopper couldn't figure out the
message separator from looking at the first line of the spool file.
In the case of un uncorrupted spool file, it could mean Qpopper is
looking for classic "From " lines in an mmdf format spool. Lately,
it is more common that the spool is corrupted.
>
>More likely, it means there is a .pop-userlock file
>lying around for this particular user. Check (with ls -l) your mail
>spool directory.
There was a bug in earlier versions of Qpopper that caused a
corrupted .user.pop file to be left around if the disk filled up or
the user hit a quota limit when Qpopper was copying the spool to the
temp drop (in non-server mode). This has been fixed, but of course
if such a corrupted .user.pop file were created in an earlier version
and is still there, it would cause this error message.
>
Date: Wed, 16 Feb 2000 23:35:47 -0500
From: James Triplett <james at mail.th dot net>
Subject: Re: envelope error
> >More likely, it means there is a .pop-userlock file
> >lying around for this particular user. Check (with ls -l) your mail
> >spool directory.
>
> There was a bug in earlier versions of Qpopper that caused a
> corrupted .user.pop file to be left around if the disk filled up or
> the user hit a quota limit when Qpopper was copying the spool to the
> temp drop (in non-server mode). This has been fixed, but of course
> if such a corrupted .user.pop file were created in an earlier version
> and is still there, it would cause this error message.
Yup, this is the "feature" that I was referring to. Took me a long time
to find the .user.pop lock that was stimulating all this high-falutin'
envelope talk... ;-)
----james
From: "Kenneth Porter" <shiva at well dot com>
Date: Wed, 16 Feb 2000 22:07:43 -0800
Subject: Netscape sending unknown xsender command
Anyone know what the xsender command is supposed to do? My qpopper logs
are reporting seeing this periodically and it looks like it's coming
from Netscape Messenger, I think 4.7. Should qpopper do something with
it?
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
Date: Thu, 17 Feb 2000 11:12:32 -0800
From: Qpopper Support <qpopper at qualcomm dot com>
Subject: Re: Netscape sending unknown xsender command
At 10:07 PM -0800 2/16/00, Kenneth Porter wrote:
>Anyone know what the xsender command is supposed to do? My qpopper logs
>are reporting seeing this periodically and it looks like it's coming
>from Netscape Messenger, I think 4.7. Should qpopper do something with
>it?
>
>Ken
>mailto:shiva at well dot com
>http://www.sewingwitch.com/ken/
See <http://www.eudora.com/qpopper/faq.html#netscape.auth>
From: John Stevenson <JSteven1 at swst dot com>
Subject: What does this mean in log file???
Date: Thu, 17 Feb 2000 13:20:34 -0600
Hello. Can someone please inform me as to what each of the 0's mean in this
log entry?
Feb 17 00:00:49 mail popper[29402]: Stats: jsteven1 0 0 0 0
Thank you,
John Stevenson