The qpopper list archive ending on 11 May 2008
Topics covered in this issue include:
1. Enable Statistics Logging and pam.d
James Medley <jmedley at aesrg dot tamu dot edu>
Thu, 31 May 2007 08:21:08 -0500
2. Unable to obtain socket and address
"Salvatore" <sasa at shoponweb dot it>
Mon, 2 Jul 2007 13:40:16 +0200
3. Re: Unable to obtain socket and address
Martin Kellermann <kellermann at sk-datentechnik dot com>
Tue, 03 Jul 2007 14:18:53 +0200
4. Re: Unable to obtain socket and address
Martin Kellermann <kellermann at sk-datentechnik dot com>
Tue, 03 Jul 2007 14:43:34 +0200
5. Re: Unable to obtain socket and address
"Salvatore" <sasa at shoponweb dot it>
Tue, 3 Jul 2007 17:11:05 +0200
6. Problems with list
Randall Gellens <randy at qualcomm dot com>
Tue, 16 Oct 2007 09:30:03 -0700
7. listserv test
Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Tue, 16 Oct 2007 17:07:25 -0700
8. APOP, SSL, and PAM
Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Wed, 17 Oct 2007 15:02:30 -0700
9. Re: APOP, SSL, and PAM
Randall Gellens <randy at qualcomm dot com>
Thu, 18 Oct 2007 12:18:03 -0700
10. Re: APOP, SSL, and PAM
Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Thu, 18 Oct 2007 14:33:21 -0700
11. test -- please ignore [eom]
Randall Gellens <randy at qualcomm dot com>
Wed, 31 Oct 2007 15:04:00 -0700
12. test -- please ignore [eom]
Randall Gellens <randy at qualcomm dot com>
Wed, 31 Oct 2007 15:31:57 -0700
13. Tru64 and C2
J Bacher <jb at jbacher dot com>
Fri, 30 Nov 2007 17:17:04 -0600
14. Re: Tru64 and C2
Randall Gellens <randy at qualcomm dot com>
Sat, 1 Dec 2007 09:57:41 -0800
15. Re: Tru64 and C2
Vic Summerour <vic at perceptive dot net>
Sun, 02 Dec 2007 16:10:59 -0600
16. Re: Tru64 and C2
Randall Gellens <randy at qualcomm dot com>
Sun, 2 Dec 2007 15:47:32 -0800
17. Re: Tru64 and C2
Vic Summerour <vic at perceptive dot net>
Mon, 03 Dec 2007 18:21:24 -0600
18. Re: Tru64 and C2
Randall Gellens <randy at qualcomm dot com>
Mon, 3 Dec 2007 18:37:01 -0800
19. Qpopper and Tru64 (was "Re: Tru64 and C2")
Randall Gellens <randy at qualcomm dot com>
Mon, 3 Dec 2007 18:50:22 -0800
20. Re: Qpopper and Tru64 (was "Re: Tru64 and C2")
Hajimu UMEMOTO <ume at mahoroba dot org>
Wed, 05 Dec 2007 04:02:23 +0900
21. Re: Qpopper and Tru64 (was "Re: Tru64 and C2")
Vic Summerour <vic at perceptive dot net>
Wed, 05 Dec 2007 13:30:16 -0600
22. Re: Tru64 and C2
Vic Summerour <vic at perceptive dot net>
Wed, 05 Dec 2007 14:02:33 -0600
23. Qpopper 4.1a6 available
Randall Gellens <randy at qualcomm dot com>
Wed, 5 Dec 2007 19:02:50 -0800
24. Too few arguments for the pass command
James Medley <jmedley at aesrg dot tamu dot edu>
Mon, 17 Dec 2007 08:52:05 -0600
25. Re: Too few arguments for the pass command
Doug Hardie <bc979 at lafn dot org>
Mon, 17 Dec 2007 13:41:32 -0800
26. Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Tue, 8 Apr 2008 09:21:31 +0000
27. Re: Qpopper failure while using with pam option enabled
Randall Gellens <randy at qualcomm dot com>
Tue, 8 Apr 2008 18:24:13 -0700
28. RE: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Wed, 9 Apr 2008 09:08:13 +0000
29. RE: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Fri, 25 Apr 2008 10:36:54 +0000
30. RE: Qpopper failure while using with pam option enabled
Randall Gellens <randy at qualcomm dot com>
Sun, 27 Apr 2008 16:40:49 -0700
31. RE: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Mon, 28 Apr 2008 06:52:09 +0000
32. Recall: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Mon, 28 Apr 2008 06:55:02 +0000
33. RE: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Mon, 28 Apr 2008 08:16:59 +0000
34. Qpopper 4.0.12 available
Randall Gellens <randy at qualcomm dot com>
Fri, 2 May 2008 17:33:11 -0700
35. Qpopper 4.1b8 available
Randall Gellens <randy at qualcomm dot com>
Fri, 2 May 2008 17:34:36 -0700
36. Easier Access to Qpopper Source Repository
Randall Gellens <randy at qualcomm dot com>
Sun, 4 May 2008 16:42:49 -0700
37. Password incorrect
"Sasa" <sasa at shoponweb dot it>
Mon, 5 May 2008 12:30:28 +0200
38. Problems compiling qpopper 4.0.12 with openssl
"Giannis Mantzouranis" <jman at physics dot upatras dot gr>
Mon, 5 May 2008 21:51:33 +0300
39. Re: Password incorrect
Doug Hardie <bc979 at lafn dot org>
Mon, 5 May 2008 11:48:27 -0700
40. Re: Problems compiling qpopper 4.0.12 with openssl
Randall Gellens <randy at qualcomm dot com>
Mon, 5 May 2008 12:26:43 -0700
41. Re: Problems compiling qpopper 4.0.12 with openssl
Doug Hardie <bc979 at lafn dot org>
Mon, 5 May 2008 12:35:44 -0700
42. configure / make error 4.0.12
Martin Kellermann <kellermann at sk-datentechnik dot com>
Tue, 06 May 2008 12:12:31 +0200
43. Re: Password incorrect
"Sasa" <sasa at shoponweb dot it>
Tue, 6 May 2008 16:30:47 +0200
44. Re: Password incorrect
Doug Hardie <bc979 at lafn dot org>
Tue, 6 May 2008 10:17:39 -0700
45. Re: configure / make error 4.0.12
Randall Gellens <randy at qualcomm dot com>
Wed, 7 May 2008 19:21:21 -0700
46. Qpopper 4.0.13 available
Randall Gellens <randy at qualcomm dot com>
Wed, 7 May 2008 19:19:36 -0700
47. Re: Problems compiling qpopper 4.0.12 with openssl
"Giannis Mantzouranis" <jman at physics dot upatras dot gr>
Thu, 8 May 2008 05:34:36 +0300
48. Re: configure / make error 4.0.12
Martin Kellermann <kellermann at sk-datentechnik dot com>
Thu, 08 May 2008 09:14:25 +0200
49. Re: Problems compiling qpopper 4.0.12 with openssl
Randall Gellens <randy at qualcomm dot com>
Thu, 8 May 2008 08:21:19 -0700
50. RE: Qpopper failure while using with pam option enabled
"Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Mon, 12 May 2008 06:23:56 +0000
From: James Medley <jmedley at aesrg dot tamu dot edu>
Subject: Enable Statistics Logging and pam.d
Date: Thu, 31 May 2007 08:21:08 -0500
--Apple-Mail-1-447005735
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed
I have been trying to Enable Statistics Logging for qpopper on a Mac
OS 10.4.9 and one of the suggestions I received said to configure
qpopper in standalone mode (see below). I thought that since I was
going to re-configure qpopper I would just used the latest version
(4.1a5). After configuring in standalone mode, I restarted everything
and was unable to authenticate (pam). Looking at the pop3 file in
pam.d I saw;
# pop3 : auth account
auth required pam_nologin.so
auth sufficient pam_unix.so
auth required pam_deny.so
account required pam_permit.so
I remembered from sometime back that I had taken one of the other
files in pam.d and used it for pop3 to make it work. This time I used
the imap file from pam.d and changed out imap with pop3. After doing
this everything worked.
# pop3 : auth account password session
auth required pam_nologin.so
auth sufficient pam_securityserver.so
auth sufficient pam_unix.so
auth required pam_deny.so
account required pam_permit.so
password required pam_deny.so
Through the process of elimination I found that the "auth sufficient
pam_securityserver.so" line had to be in there for it to work.
Thanks,
Jim
PS. I still haven't gotten statistics logging to work.
> I had the same problem on MacOS X 10.3, it was resolved by using
> standalone mode rather than running popper from xinetd.
>
> Best wishes,
> Damon
>
> On 12/05/07, James Medley <jmedley@aesrg.tamu.edu> wrote:
>
>> Hi All,
>>
>> I have a small mail server running on a Mac G5 desktop OS X
>> 10.4.9, using
>> postfix 2.1.5 and qpopper 4.0.9. I am trying to enable statistics
>> logging
>> and haven't had any luck. The earlier versions of OS X worked off
>> of an
>> inetd.conf file where I put in;
>> #pop3 stream tcp nowait root /usr/libexec/tcpd
>> /usr/libexec/popper qpopper -s
>> But the newer OS uses xinetd and I'm not sure how to enable the
>> logging. Can
>> someone please put me on the right path.
>>
>> Thanks Much,
>> Jim
--Apple-Mail-1-447005735
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=ISO-8859-1
<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space;
-khtml-line-break: after-white-space; "><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I have been
trying to Enable Statistics Logging for qpopper on a Mac OS 10.4.9 and
one of the suggestions I received said to configure qpopper in
standalone mode (see below). I thought that since I was going to
re-configure qpopper I would just used the latest version (4.1a5). After
configuring in standalone mode, I restarted everything and was unable
to=A0authenticate (pam). Looking at the pop3 file in pam.d I
saw;</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font: normal normal normal
16px/normal Times New Roman; min-height: 18px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; "># pop3 : auth account</DIV><DIV style="margin-top:
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">auth
required pam_nologin.so</DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">auth
sufficient pam_unix.so</DIV><DIV style="margin-top: 0px; margin-right:
0px; margin-bottom: 0px; margin-left: 0px; ">auth required
pam_deny.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">account required
pam_permit.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font: normal normal normal
16px/normal Times New Roman; min-height: 18px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">I remembered from sometime back that I had taken one
of the other files in pam.d and used it for pop3 to make it work. This
time I used the imap file from pam.d and changed out imap with pop3.
After doing this everything worked.=A0=A0</DIV><DIV style="margin-top:
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font:
normal normal normal 16px/normal Times New Roman; min-height: 18px;
"><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; "># pop3 : auth account password
session</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">auth required
pam_nologin.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">auth sufficient
pam_securityserver.so</DIV><DIV style="margin-top: 0px; margin-right:
0px; margin-bottom: 0px; margin-left: 0px; ">auth sufficient
pam_unix.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">auth required
pam_deny.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">account required
pam_permit.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">password required
pam_deny.so</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font: normal normal normal
16px/normal Times New Roman; min-height: 18px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">Through the process of elimination I found that the
"auth sufficient pam_securityserver.so" line had to be in there for it
to work.</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; font: normal normal normal
16px/normal Times New Roman; min-height: 18px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">Thanks,</DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Jim</DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; font: normal normal normal 16px/normal Times New
Roman; min-height: 18px; "><BR></DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">PS.=A0 I
still haven't gotten statistics logging to work.</DIV><BR><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; "><BLOCKQUOTE type="cite"><DIV style="margin-top:
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I had
the same problem on MacOS X 10.3, it was resolved by using</DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">standalone mode rather than running popper from
xinetd.</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">Best wishes,</DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;
">Damon</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">On 12/05/07, James Medley <<A
href="mailto:jmedley@aesrg.tamu.edu">jmedley@aesrg.tamu.edu</A>>
wrote:</DIV><BR><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Hi
All,</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">I have a small mail server running on a Mac G5
desktop OS X 10.4.9, using</DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">postfix 2.1.5
and qpopper 4.0.9. I am trying to enable statistics logging</DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">and haven't had any luck. The earlier versions of OS
X worked off of an</DIV><DIV style="margin-top: 0px; margin-right:
0px; margin-bottom: 0px; margin-left: 0px; ">inetd.conf file where I put
in;</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px; ">#pop3 =A0 stream=A0 tcp =A0 =A0
nowait=A0 root=A0 =A0 /usr/libexec/tcpd</DIV><DIV style="margin-top:
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;
">/usr/libexec/popper qpopper -s</DIV><DIV style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">But the newer
OS uses xinetd and I'm not sure how to enable the logging. Can</DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; ">someone please put me on the right path.</DIV><DIV
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top:
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Thanks
Much,</DIV><DIV style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px;
">Jim</DIV></BLOCKQUOTE></BLOCKQUOTE></DIV><DIV> <SPAN
class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Times New
Roman; font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent:
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2;
white-space: normal; widows: 2; word-spacing: 0px; "><BR
class="Apple-interchange-newline"><SPAN class="Apple-style-span"
style="border-collapse: separate; border-spacing: 0px 0px; color:
rgb(0, 0, 0); font-family: Times New Roman; font-size: 16px; font-style:
normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; text-align: auto;
-khtml-text-decorations-in-effect: none; text-indent: 0px;
-apple-text-size-adjust: auto; text-transform: none; orphans: 2;
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN
class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Times New
Roman; font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent:
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2;
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN
class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Times New
Roman; font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent:
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2;
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN
class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Times New
Roman; font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent:
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2;
white-space: normal; widows: 2; word-spacing: 0px; "><DIV><BR
class="khtml-block-placeholder"></DIV></SPAN></SPAN></SPAN></SPAN></SPAN
></DIV><BR></BODY></HTML>
--Apple-Mail-1-447005735--
From: "Salvatore" <sasa at shoponweb dot it>
Subject: Unable to obtain socket and address
Date: Mon, 2 Jul 2007 13:40:16 +0200
Hi, I have a problem with qpopper 4.0.9 on Fedora Core 6, when:
/etc/rc.d/init.d/popper start
Jul 2 13:18:33 localhost popper[2621]: Unable to obtain socket and address
of client: Socket operation on non-socket (88)
..I have used parameter:
#./configure --enable-standalone --without pam
Thanks.
------
Salvatore.
Date: Tue, 03 Jul 2007 14:18:53 +0200
From: Martin Kellermann <kellermann at sk-datentechnik dot com>
Subject: Re: Unable to obtain socket and address
--=====================_83866140==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
this indicates that you try to run a version that is NOT compiled
with standalone mode enabled.
maybe you have more than one version of popper installed!?
try "cd / && find . -name popper"
if there really is one single executable, recompile it:
try doing with a 'make realclean' first....
MK
At 13:40 02.07.2007, you wrote:
>Hi, I have a problem with qpopper 4.0.9 on Fedora Core 6, when:
>
>/etc/rc.d/init.d/popper start
>Jul 2 13:18:33 localhost popper[2621]: Unable
>to obtain socket and address of client: Socket operation on non-socket (88)
>
>..I have used parameter:
>
>#./configure --enable-standalone --without pam
>
>Thanks.
>
>------
>Salvatore.
___________________________
sk datentechnik GmbH
Stalleickenweg 5
44867 Bochum
Tel: 02327-9501-0
Fax: 02327-9501-25
HRB 6176 AG Bochum
Geschäftsführer: Martin Kellermann
USt-ID DE196142436
--=====================_83866140==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<body>
this indicates that you try to run a version that is NOT compiled<br>
with standalone mode enabled.<br><br>
maybe you have more than one version of popper installed!?<br><br>
try "cd / && find . -name popper"<br><br>
if there really is one single executable, recompile it:<br>
<pre>try doing with a 'make realclean' first....
</pre>MK<br><br>
At 13:40 02.07.2007, you
wrote:<blockquote type=cite class=cite cite="">Hi, I have a problem wi
th
qpopper 4.0.9 on Fedora Core 6, when:<br><br>
/etc/rc.d/init.d/popper start<br>
Jul 2 13:18:33 localhost popper[2621]: Unable to obtain socket and
address of client: Socket operation on non-socket (88)<br><br>
..I have used parameter:<br><br>
#./configure --enable-standalone --without pam<br><br>
Thanks.<br><br>
------<br>
Salvatore.<br>
</blockquote>
<x-sigsep><p></x-sigsep>
<font face="Arial, Helvetica" size=2><br><br>
___________________________<br><br>
sk datentechnik GmbH<br>
Stalleickenweg 5<br>
44867 Bochum<br>
Tel: 02327-9501-0<br>
Fax: 02327-9501-25<br><br>
</font><font face="Arial, Helvetica" size=1> HRB 6176 AG
Bochum<br>
Geschäftsführer: Martin Kellermann<br>
USt-ID DE196142436<br>
</font></body>
</html>
--=====================_83866140==.ALT--
Date: Tue, 03 Jul 2007 14:43:34 +0200
From: Martin Kellermann <kellermann at sk-datentechnik dot com>
Subject: Re: Unable to obtain socket and address
--=====================_85347562==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
this indicates that you try to run a version that is NOT compiled
with standalone mode enabled.
maybe you have more than one version of popper installed!?
try "cd / && find . -name popper"
if there really is one single executable, recompile it:
try doing with a 'make realclean' first....
MK
At 13:40 02.07.2007, you wrote:
>Hi, I have a problem with qpopper 4.0.9 on Fedora Core 6, when:
>
>/etc/rc.d/init.d/popper start
>Jul 2 13:18:33 localhost popper[2621]: Unable to obtain socket and
>address of client: Socket operation on non-socket (88)
>
>..I have used parameter:
>
>#./configure --enable-standalone --without pam
>
>Thanks.
>
>------
>Salvatore.
--=====================_85347562==.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<body>
this indicates that you try to run a version that is NOT compiled<br>
with standalone mode enabled.<br><br>
maybe you have more than one version of popper installed!?<br><br>
try "cd / && find . -name popper"<br><br>
if there really is one single executable, recompile it:<br><br>
<pre>try doing with a 'make realclean' first....
</pre>MK<br><br>
At 13:40 02.07.2007, you
wrote:<blockquote type=cite class=cite cite="">Hi, I have a problem with
qpopper 4.0.9 on Fedora Core 6, when:<br><br>
/etc/rc.d/init.d/popper start<br>
Jul 2 13:18:33 localhost popper[2621]: Unable to obtain socket and
address of client: Socket operation on non-socket (88)<br><br>
..I have used parameter:<br><br>
#./configure --enable-standalone --without pam<br><br>
Thanks.<br><br>
------<br>
Salvatore.</blockquote></body>
</html>
--=====================_85347562==.ALT--
From: "Salvatore" <sasa at shoponweb dot it>
Subject: Re: Unable to obtain socket and address
Date: Tue, 3 Jul 2007 17:11:05 +0200
Hi and thanks for your support, I am sure that I have used:
#./configure --enable-standalone --without-pam
..and I am sure that I have only qpopper installation, however yesterday I
have solved my problem (as say you as) in this mode:
#./configure --enable-standalone --without-pam
#make clean
#make && make install
Thanks again.
------
Salvatore.
----- Original Message -----
From: "Martin Kellermann" <kellermann@sk-datentechnik.com>
To: "Subscribers of Qpopper" <qpopper@lists.pensive.org>
Sent: Tuesday, July 03, 2007 2:43 PM
Subject: Re: Unable to obtain socket and address
> this indicates that you try to run a version that is NOT compiled
> with standalone mode enabled.
>
> maybe you have more than one version of popper installed!?
>
> try "cd / && find . -name popper"
>
> if there really is one single executable, recompile it:
>
> try doing with a 'make realclean' first....
>
>
> MK
>
> At 13:40 02.07.2007, you wrote:
>>Hi, I have a problem with qpopper 4.0.9 on Fedora Core 6, when:
>>
>>/etc/rc.d/init.d/popper start
>>Jul 2 13:18:33 localhost popper[2621]: Unable to obtain socket and
>>address of client: Socket operation on non-socket (88)
>>
>>..I have used parameter:
>>
>>#./configure --enable-standalone --without pam
>>
>>Thanks.
>>
>>------
>>Salvatore.
>
Date: Tue, 16 Oct 2007 09:30:03 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Problems with list
Hi everyone,
I discovered that there was a problem where the backup MX was
accidently blocked. If you tried to post anything to the list, or
subscribe, unsubscribe, or change your list options, and received a
bounce, please try again.
My apologizes for this.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
There's nothing wrong with me. Maybe there's something wrong with
the universe. --'Dr. Beverly Crusher' in ST:TNG _Remember Me_.
Date: Tue, 16 Oct 2007 17:07:25 -0700
From: Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Subject: listserv test
OK, subscribing seems to be fixed (thanks Randall!); let's see if
posting is working....
Date: Wed, 17 Oct 2007 15:02:30 -0700
From: Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Subject: APOP, SSL, and PAM
I just got this working (on FreeBSD 6.2). Whew!
I set up my system using the Vanemery.com qpopper page as a guide.
I had originally put all my users into the APOP db, but that confused
Qpopper when a PC user on OE tried to connect. So I deleted the PC
users from the APOP db (leaving the Mac users in, since both Eudora
and Mail.app do APOP), and that left me with a PAM error
("pam_authenticate returned 9").
Turned out that all I needed to do was reset the PC users' passwords,
and then PAM noticed whatever it needed to notice, and everything's
working now.
I also learned that pam.d/* replaces pam.conf, so I didn't really
need to go looking for a "missing" config file.
-Walter
Date: Thu, 18 Oct 2007 12:18:03 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: APOP, SSL, and PAM
At 3:02 PM -0700 10/17/07, Walter Ian Kaye wrote:
> I just got this working (on FreeBSD 6.2). Whew!
>
> I set up my system using the Vanemery.com qpopper page as a guide.
I'm not familiar with that. If you have suggestions for changes to
the Qpopper FAQ or the Administrators Guide, please send them in.
Sending a patch is always welcome.
> I had originally put all my users into the APOP db, but that
> confused Qpopper when a PC user on OE tried to connect. So I
> deleted the PC users from the APOP db (leaving the Mac users in,
> since both Eudora and Mail.app do APOP), and that left me with a
> PAM error ("pam_authenticate returned 9").
The default setting for 'clear-text-password' rejects attempts to log
in with username/password if the user exists in the APOP database.
Looking at the code, setting 'clear-text-password' to 'TLS' also does
this, but I'm thinking this may be a bug. Specifically, the code at
pop_user.c line (line 256 in qpopper4.0.9) should check for other
values as well.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
It is easier to fight for one's principles than to live up to them.
--Alfred Adler
Date: Thu, 18 Oct 2007 14:33:21 -0700
From: Walter Ian Kaye <qpopper-list at natural-innovations dot com>
Subject: Re: APOP, SSL, and PAM
At 12:18 p -0700 10/18/2007, Randall Gellens didst inscribe upon an
electronic papyrus:
>At 3:02 PM -0700 10/17/07, Walter Ian Kaye wrote:
>
>> I just got this working (on FreeBSD 6.2). Whew!
>>
>> I set up my system using the Vanemery.com qpopper page as a guide.
>
>I'm not familiar with that. If you have suggestions for changes to
>the Qpopper FAQ or the Administrators Guide, please send them in.
>Sending a patch is always welcome.
Quickstart Guide - Qpopper on FreeBSD
http://www.vanemery.com/Protocols/POP/qpopper-bsd-howto.html
Of course neither one helped me solve my SSL certificate issues -- I
kept getting signature error code 7. A friend pointed me to
<http://www.rpatrick.com/tech/makecert/>; meanwhile I had been
reading the FAQ on RapidSSL.com which spoke of invalid characters
such as "," and "." -- I had those in the company name field, so I
removed them when I followed the third set of instructions, and
finally got a working certificate.
>> I had originally put all my users into the APOP db, but that
>>confused Qpopper when a PC user on OE tried to connect. So I
>>deleted the PC users from the APOP db (leaving the Mac users in,
>>since both Eudora and Mail.app do APOP), and that left me with a
>>PAM error ("pam_authenticate returned 9").
>
>The default setting for 'clear-text-password' rejects attempts to
>log in with username/password if the user exists in the APOP
>database. Looking at the code, setting 'clear-text-password' to
>'TLS' also does this, but I'm thinking this may be a bug.
>Specifically, the code at pop_user.c line (line 256 in qpopper4.0.9)
>should check for other values as well.
Yeah, my thinking was that a PC user should be able to, um, upgrade
from Outlook to Eudora without requiring sysadmin help; that's why I
put all the users into the APOP database.
Aside: the old hosting service, which registered the domain name as
well, switched the DNS while I was sleeping. I awoke today to a call
from my coworker saying that email wasn't working. Oy. Hopefully
nothing was lost; thank goodness the mail system stores and retries.
Everything's working now. :-)
-Walter
Date: Wed, 31 Oct 2007 15:04:00 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: test -- please ignore [eom]
Date: Wed, 31 Oct 2007 15:31:57 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: test -- please ignore [eom]
Date: Fri, 30 Nov 2007 17:17:04 -0600
From: J Bacher <jb at jbacher dot com>
Subject: Tru64 and C2
Does qpopper no longer support Tru64 5.1 enhanced security?
It's been awhile since I've been asked to upgrade qpopper on Tru64 and previous
versions (at least up to 4.0.4) supported enhanced security with the
--enable-specialauth configuration option.
Date: Sat, 1 Dec 2007 09:57:41 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Tru64 and C2
At 5:17 PM -0600 11/30/07, J Bacher wrote:
> Does qpopper no longer support Tru64 5.1 enhanced security?
>
> It's been awhile since I've been asked to upgrade qpopper on Tru64
> and previous versions (at least up to 4.0.4) supported enhanced
> security with the --enable-specialauth configuration option.
The --enable-specialauth option is still there, although ./configure
figures out if it is needed for many platforms. Are you having a
problem with Tru64?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
When we remember we are all mad, the mysteries disappear and
life stands explained. --Mark Twain
Date: Sun, 02 Dec 2007 16:10:59 -0600
From: Vic Summerour <vic at perceptive dot net>
Subject: Re: Tru64 and C2
I have used qpopper with Tru64, Digital Unix, OSF/1 for
years. Sometime in the not so distant past but I can't remember when
or the details of why, I have had to configure with the following:
./configure --enable-specialauth --without-pam
Currently with Tru64 V5.1A with PK6, I have successfully compiled and
run 4.1a4 with the following compiler:
alpha> cc -V
Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
Compiler Driver V6.4-215 (sys) cc Driver
Unfortunately, 4.1a5 will not successfully compile based on the same
configure. It stop with the error:
cc -c -I.. -I.. -I. \
-I../mmangle -I../common \
-g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
cc: Error: main.c, line 150: Missing type specifier or type
qualifier. (missingtype)
socklen_t ai_addrlen;
--------^
make[1]: *** [main.o] Error 1
make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
make: *** [popper_server] Error 2
This appears to be associated with 4.1a4 to 4.1a5 enhancements
associated with ipv6 support. Since Tru 5.1A supports ipv6 even
though it is not being used, I tried to configure with:
./configure --enable-specialauth --without-pam --enable-ipv6
but that made no difference. By defining INET6 in config.h, 4.1a5
will successfully compile and run.
Vic Summerour
At 09:57 AM 12/1/2007 -0800, Randall Gellens wrote:
>At 5:17 PM -0600 11/30/07, J Bacher wrote:
>
>> Does qpopper no longer support Tru64 5.1 enhanced security?
>>
>> It's been awhile since I've been asked to upgrade qpopper on
>> Tru64 and previous versions (at least up to 4.0.4) supported
>> enhanced security with the --enable-specialauth configuration option.
>
>The --enable-specialauth option is still there, although ./configure
>figures out if it is needed for many platforms. Are you having a
>problem with Tru64?
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly-selected tag: ---------------
>When we remember we are all mad, the mysteries disappear and
>life stands explained. --Mark Twain
Date: Sun, 2 Dec 2007 15:47:32 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Tru64 and C2
At 4:10 PM -0600 12/2/07, Vic Summerour wrote:
> I have used qpopper with Tru64, Digital Unix, OSF/1 for years.
> Sometime in the not so distant past but I can't remember when or
> the details of why, I have had to configure with the following:
>
> ./configure --enable-specialauth --without-pam
Was --enable-specialauth needed? If you left it off, what happened?
>
> Currently with Tru64 V5.1A with PK6, I have successfully compiled
> and run 4.1a4 with the following compiler:
>
> alpha> cc -V
> Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
> Compiler Driver V6.4-215 (sys) cc Driver
>
>
> Unfortunately, 4.1a5 will not successfully compile based on the
> same configure. It stop with the error:
>
> cc -c -I.. -I.. -I. \
> -I../mmangle -I../common \
> -g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
> cc: Error: main.c, line 150: Missing type specifier or type
> qualifier. (missingtype)
> socklen_t ai_addrlen;
> --------^
> make[1]: *** [main.o] Error 1
> make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
> make: *** [popper_server] Error 2
>
> This appears to be associated with 4.1a4 to 4.1a5 enhancements
> associated with ipv6 support. Since Tru 5.1A supports ipv6 even
> though it is not being used, I tried to configure with:
>
> ./configure --enable-specialauth --without-pam --enable-ipv6
>
> but that made no difference. By defining INET6 in config.h, 4.1a5
> will successfully compile and run.
Do you know in which header file this is normally defined? If it is
a missing .h on Tru64, fixing ./configure to add it or add it in the
right place might be the proper solution.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
Computers ... are not designed, as we are, for ambiguity. --Thomas
Date: Mon, 03 Dec 2007 18:21:24 -0600
From: Vic Summerour <vic at perceptive dot net>
Subject: Re: Tru64 and C2
At 03:47 PM 12/2/2007 -0800, Randall Gellens wrote:
>At 4:10 PM -0600 12/2/07, Vic Summerour wrote:
>
>> I have used qpopper with Tru64, Digital Unix, OSF/1 for years.
>> Sometime in the not so distant past but I can't remember when or
>> the details of why, I have had to configure with the following:
>>
>> ./configure --enable-specialauth --without-pam
>
>Was --enable-specialauth needed? If you left it off, what happened?
With ./configure only, the following occurs:
./configure
.
.
.
checking for pam_authenticate in -lpam... no
Can't use PAM: can't find libpam
With ./configure --without-pam, it will configure and compile
correctly. Attempts to retrieve pop mail results in an invalid
password message:
With ./configure --enable-specialauth --without-pam, it will
configure correctly, compile, and work.
>> Currently with Tru64 V5.1A with PK6, I have successfully compiled
>> and run 4.1a4 with the following compiler:
>>
>> alpha> cc -V
>> Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
>> Compiler Driver V6.4-215 (sys) cc Driver
>>
>>
>> Unfortunately, 4.1a5 will not successfully compile based on the
>> same configure. It stop with the error:
>>
>> cc -c -I.. -I.. -I. \
>> -I../mmangle -I../common \
>> -g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
>> cc: Error: main.c, line 150: Missing type specifier or type
>> qualifier. (missingtype)
>> socklen_t ai_addrlen;
>> --------^
>> make[1]: *** [main.o] Error 1
>> make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
>> make: *** [popper_server] Error 2
>>
>> This appears to be associated with 4.1a4 to 4.1a5 enhancements
>> associated with ipv6 support. Since Tru 5.1A supports ipv6 even
>> though it is not being used, I tried to configure with:
>>
>> ./configure --enable-specialauth --without-pam --enable-ipv6
>>
>> but that made no difference. By defining INET6 in config.h,
>> 4.1a5 will successfully compile and run.
>
>Do you know in which header file this is normally defined? If it is
>a missing .h on Tru64, fixing ./configure to add it or add it in the
>right place might be the proper solution.
For Tru64 5.1A PK6, I could not find INET6 defined in any header file
in any of the obvious include directories. I also looked briefly
through the Network Programmer's Guide for mention of it without success.
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly-selected tag: ---------------
>Computers ... are not designed, as we are, for ambiguity. --Thomas
Date: Mon, 3 Dec 2007 18:37:01 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Tru64 and C2
--============_-1015386643==_============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
At 5:18 PM -0600 12/3/07, J Springer wrote:
> Randall Gellens wrote:
>
>> Hmmm. I think I see the problem. There is some confusion in the
>> script with "no" and "no_" for pam, and only for pam. Problem ...
>> ...snip...
>> ... confirmation, if you don't mind, could you run the attached
>> ./configure script (after another 'make realclean') and send me
>> the output?
>
> Holler when you're ready for me to run another test.
>
> I have one [dumb] question, if configure fails and a Makefile isn't
> created, shouldn't 'make realclean' fail? Or do I need to copy the
> Makefile.in to Makefile first?
If ./configure fails, then there is no Makefile, and hence 'make
realclea' will fail. That's fine, as there shouldn't be a config.h
or any of the other files created by ./configure. I get in the habit
of recommending 'make realclean' just to be sure that the stuff isn't
there. So, no need to copy a Makefile.
> ./configure --enable-temp-drop-dir=/usr/poptmp --enable-log-login
> --enable-server-mode --enable-standalone --enable-specialauth
>
> "use_pam is no_"
> checking for dlopen in -ldl... no
> checking for pam_authenticate in -lpam... no
> Can't use PAM: can't find libpam
OK, that confirms what I found the first time. The second
./configure I sent does indeed fix what I found the first time, which
is why pam was enabled by default when it should be off by default.
At 6:21 PM -0600 12/3/07, Vic Summerour wrote:
> At 03:47 PM 12/2/2007 -0800, Randall Gellens wrote:
>> At 4:10 PM -0600 12/2/07, Vic Summerour wrote:
>>
>>> I have used qpopper with Tru64, Digital Unix, OSF/1 for years.
>>> Sometime in the ...
>>> ...snip...
>>> ./configure --enable-specialauth --without-pam
>>
>> Was --enable-specialauth needed? If you left it off, what happened?
>
> With ./configure only, the following occurs:
>
> ./configure
> .
> .
> .
> checking for pam_authenticate in -lpam... no
> Can't use PAM: can't find libpam
This is fixed by the first change to ./configure.
> With ./configure --without-pam, it will configure and compile
> correctly. Attempts to retrieve pop mail results in an invalid
> password message:
>
> With ./configure --enable-specialauth --without-pam, it will
> configure correctly, compile, and work.
I believe this is because TRUE64 uses getprpwnam() instead of
getspnam(), and ./configure was only checking for the later when
deciding if specialauth should be enabled by default. I've added a
check for the former, so hopefully a default ./configure will now
correctly check passwords on True64. If you could verify this for
me, I'd be very grateful. I'm attaching a new ./configure. Please
be sure to do a 'make realclean' beforehand.
--============_-1015386643==_============
Content-Id:
Content-Type: application/octet-stream; name="configure"
Content-Disposition: attachment; filename="configure"
Content-Transfer-Encoding: base64
--============_-1015386643==_============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Date: Mon, 3 Dec 2007 18:50:22 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper and Tru64 (was "Re: Tru64 and C2")
At 6:21 PM -0600 12/3/07, Vic Summerour wrote:
>>> Currently with Tru64 V5.1A with PK6, I have successfully
>>> compiled and run 4.1a4 with the following compiler:
>>>
>>> alpha> cc -V
>>> Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
>>> Compiler Driver V6.4-215 (sys) cc Driver
>>>
>>>
>>> Unfortunately, 4.1a5 will not successfully compile based on the
>>> same configure. It stop with the error:
>>>
>>> cc -c -I.. -I.. -I. \
>>> -I../mmangle -I../common \
>>> -g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
>>> cc: Error: main.c, line 150: Missing type specifier or type
>>> qualifier. (missingtype)
>>> socklen_t ai_addrlen;
>>> --------^
>>> make[1]: *** [main.o] Error 1
>>> make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
>>> make: *** [popper_server] Error 2
>>>
>>> This appears to be associated with 4.1a4 to 4.1a5 enhancements
>>> associated with ipv6 support. Since Tru 5.1A supports ipv6 even
>>> though it is not being used, I tried to configure with:
>>>
>>> ./configure --enable-specialauth --without-pam --enable-ipv6
>>>
>>> but that made no difference. By defining INET6 in config.h,
>>> 4.1a5 will successfully compile and run.
>>
>> Do you know in which header file this is normally defined? If it
>> is a missing .h on Tru64, fixing ./configure to add it or add it
>> in the right place might be the proper solution.
>
> For Tru64 5.1A PK6, I could not find INET6 defined in any header
> file in any of the obvious include directories. I also looked
> briefly through the Network Programmer's Guide for mention of it
> without success.
My apologies, my question was incorrect.
So, a default ./configure does not add "define INET6 1" to config.h?
But if you manually add this, it compiles?
The ./configure script should set this based on checking for v6
version of getaddrinfo(). Do you see any messages related to this in
the output of ./configure?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
wabi (wah-BI; Japanese; noun): a flawed detail that creates an
elegant whole.
Date: Wed, 05 Dec 2007 04:02:23 +0900
From: Hajimu UMEMOTO <ume at mahoroba dot org>
Subject: Re: Qpopper and Tru64 (was "Re: Tru64 and C2")
Hi,
>>>>> On Mon, 3 Dec 2007 18:50:22 -0800
>>>>> Randall Gellens <randy@qualcomm.com> said:
randy> At 6:21 PM -0600 12/3/07, Vic Summerour wrote:
>>> Currently with Tru64 V5.1A with PK6, I have successfully
>>> compiled and run 4.1a4 with the following compiler:
>>>
>>> alpha> cc -V
>>> Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
>>> Compiler Driver V6.4-215 (sys) cc Driver
>>>
>>>
>>> Unfortunately, 4.1a5 will not successfully compile based on the
>>> same configure. It stop with the error:
>>>
>>> cc -c -I.. -I.. -I. \
>>> -I../mmangle -I../common \
>>> -g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
>>> cc: Error: main.c, line 150: Missing type specifier or type
>>> qualifier. (missingtype)
>>> socklen_t ai_addrlen;
>>> --------^
>>> make[1]: *** [main.o] Error 1
>>> make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
>>> make: *** [popper_server] Error 2
Oops, it seems my fault. The socklen_t is used in an offhand.
Please try this patch:
Index: config.h.in
diff -u config.h.in.orig config.h.in
--- config.h.in.orig 2007-04-27 06:59:36.000000000 +0900
+++ config.h.in 2007-12-05 03:46:16.000000000 +0900
@@ -197,6 +197,9 @@
/* Define if you have the iruserok_sa function. */
#undef HAVE_IRUSEROK_SA
+/* do we have socklen_t? */
+#undef HAVE_SOCKLEN_T
+
/* Define if you have the <dbm.h> header file. */
#undef HAVE_DBM_H
Index: configure.in
diff -u configure.in.orig configure.in
--- configure.in.orig 2007-04-27 06:59:36.000000000 +0900
+++ configure.in 2007-12-05 03:43:57.000000000 +0900
@@ -991,6 +991,7 @@
IPv6_CHECK_FUNC(iruserok_sa)
fi
+AC_EGREP_HEADER(socklen_t, sys/socket.h, AC_DEFINE(HAVE_SOCKLEN_T))
AC_ARG_ENABLE(tempnam, [ --enable-tempnam Use tempnam() instead of mkstemp()],
Index: popper/main.c
diff -u -p popper/main.c.orig popper/main.c
--- popper/main.c.orig 2007-04-27 07:11:00.000000000 +0900
+++ popper/main.c 2007-12-05 03:51:07.000000000 +0900
@@ -138,6 +138,10 @@
# endif /* HAVE_PAM_PAM_APPL_H */
#endif /* USE_PAM */
+#ifndef HAVE_SOCKLEN_T
+typedef unsigned int socklen_t;
+#endif /* HAVE_SOCKLEN_T */
+
#ifdef INET6
# include <netdb.h>
#else /* not INET6 */
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Date: Wed, 05 Dec 2007 13:30:16 -0600
From: Vic Summerour <vic at perceptive dot net>
Subject: Re: Qpopper and Tru64 (was "Re: Tru64 and C2")
The patches below fix the compile problem and INET6 is not defined in config.h.
Note the configure as supplied with qpopper4.1a5 must still be run
with --enable-specialauth and --without-pam for popper to work. The
results from the modified configure supplied by Randall Gallens will
be provided in another message.
Not certain what's happening with configure regarding getaddrinfo,
but it is not finding it even though it is available in the system.
checking for getaddrinfo... no
checking for getaddrinfo in -lsocket... no
checking whether your system has IPv6 directory... no
checking for iruserok_sa... no
checking for iruserok_sa in -lsocket... no
checking whether your system has IPv6 directory... (cached) no
System name: OSF1; System version: V5.1
Set OS_DEFS = " -DOSF1 -DUNIX"
Vic Summerour
At 04:02 AM 12/5/2007 +0900, Hajimu UMEMOTO wrote:
>Hi,
>
> >>>>> On Mon, 3 Dec 2007 18:50:22 -0800
> >>>>> Randall Gellens <randy@qualcomm.com> said:
>
>randy> At 6:21 PM -0600 12/3/07, Vic Summerour wrote:
>
> >>> Currently with Tru64 V5.1A with PK6, I have successfully
> >>> compiled and run 4.1a4 with the following compiler:
> >>>
> >>> alpha> cc -V
> >>> Compaq C V6.4-014 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
> >>> Compiler Driver V6.4-215 (sys) cc Driver
> >>>
> >>>
> >>> Unfortunately, 4.1a5 will not successfully compile based on the
> >>> same configure. It stop with the error:
> >>>
> >>> cc -c -I.. -I.. -I. \
> >>> -I../mmangle -I../common \
> >>> -g -DHAVE_CONFIG_H -DOSF1 -DUNIX main.c -o main.o
> >>> cc: Error: main.c, line 150: Missing type specifier or type
> >>> qualifier. (missingtype)
> >>> socklen_t ai_addrlen;
> >>> --------^
> >>> make[1]: *** [main.o] Error 1
> >>> make[1]: Leaving directory `/dsk1/vic/qpopper/qpopper4.1a5/popper'
> >>> make: *** [popper_server] Error 2
>
>Oops, it seems my fault. The socklen_t is used in an offhand.
>Please try this patch:
>
>Index: config.h.in
>diff -u config.h.in.orig config.h.in
>--- config.h.in.orig 2007-04-27 06:59:36.000000000 +0900
>+++ config.h.in 2007-12-05 03:46:16.000000000 +0900
>@@ -197,6 +197,9 @@
> /* Define if you have the iruserok_sa function. */
> #undef HAVE_IRUSEROK_SA
>
>+/* do we have socklen_t? */
>+#undef HAVE_SOCKLEN_T
>+
> /* Define if you have the <dbm.h> header file. */
> #undef HAVE_DBM_H
>
>Index: configure.in
>diff -u configure.in.orig configure.in
>--- configure.in.orig 2007-04-27 06:59:36.000000000 +0900
>+++ configure.in 2007-12-05 03:43:57.000000000 +0900
>@@ -991,6 +991,7 @@
> IPv6_CHECK_FUNC(iruserok_sa)
> fi
>
>+AC_EGREP_HEADER(socklen_t, sys/socket.h, AC_DEFINE(HAVE_SOCKLEN_T))
>
>
> AC_ARG_ENABLE(tempnam, [ --enable-tempnam Use tempnam()
> instead of mkstemp()],
>Index: popper/main.c
>diff -u -p popper/main.c.orig popper/main.c
>--- popper/main.c.orig 2007-04-27 07:11:00.000000000 +0900
>+++ popper/main.c 2007-12-05 03:51:07.000000000 +0900
>@@ -138,6 +138,10 @@
> # endif /* HAVE_PAM_PAM_APPL_H */
> #endif /* USE_PAM */
>
>+#ifndef HAVE_SOCKLEN_T
>+typedef unsigned int socklen_t;
>+#endif /* HAVE_SOCKLEN_T */
>+
> #ifdef INET6
> # include <netdb.h>
> #else /* not INET6 */
>
>
>Sincerely,
>
>--
>Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
>ume@mahoroba.org ume@{,jp.}FreeBSD.org
>http://www.imasy.org/~ume/
Date: Wed, 05 Dec 2007 14:02:33 -0600
From: Vic Summerour <vic at perceptive dot net>
Subject: Re: Tru64 and C2
At 06:37 PM 12/3/2007 -0800, Randall Gellens wrote:
>At 5:18 PM -0600 12/3/07, J Springer wrote:
>
>> Randall Gellens wrote:
>>
>>> Hmmm. I think I see the problem. There is some confusion in
>>> the script with "no" and "no_" for pam, and only for pam. Problem ...
>>> ...snip...
>>> ... confirmation, if you don't mind, could you run the attached
>>> ./configure script (after another 'make realclean') and send me the output?
>>
>> Holler when you're ready for me to run another test.
>>
>> I have one [dumb] question, if configure fails and a Makefile
>> isn't created, shouldn't 'make realclean' fail? Or do I need to
>> copy the Makefile.in to Makefile first?
>
>If ./configure fails, then there is no Makefile, and hence 'make
>realclea' will fail. That's fine, as there shouldn't be a config.h
>or any of the other files created by ./configure. I get in the
>habit of recommending 'make realclean' just to be sure that the
>stuff isn't there. So, no need to copy a Makefile.
>
>> ./configure --enable-temp-drop-dir=/usr/poptmp --enable-log-login
>> --enable-server-mode --enable-standalone --enable-specialauth
>>
>> "use_pam is no_"
>> checking for dlopen in -ldl... no
>> checking for pam_authenticate in -lpam... no
>> Can't use PAM: can't find libpam
>
>OK, that confirms what I found the first time. The second
>./configure I sent does indeed fix what I found the first time,
>which is why pam was enabled by default when it should be off by default.
>
>At 6:21 PM -0600 12/3/07, Vic Summerour wrote:
>
>> At 03:47 PM 12/2/2007 -0800, Randall Gellens wrote:
>>> At 4:10 PM -0600 12/2/07, Vic Summerour wrote:
>>>
>>>> I have used qpopper with Tru64, Digital Unix, OSF/1 for years.
>>>> Sometime in the ...
>>>> ...snip...
>>>> ./configure --enable-specialauth --without-pam
>>>
>>> Was --enable-specialauth needed? If you left it off, what happened?
>>
>> With ./configure only, the following occurs:
>>
>> ./configure
>> .
>> .
>> .
>> checking for pam_authenticate in -lpam... no
>> Can't use PAM: can't find libpam
>
>This is fixed by the first change to ./configure.
>
>> With ./configure --without-pam, it will configure and compile
>> correctly. Attempts to retrieve pop mail results in an invalid
>> password message:
>>
>> With ./configure --enable-specialauth --without-pam, it will
>> configure correctly, compile, and work.
>
>I believe this is because TRUE64 uses getprpwnam() instead of
>getspnam(), and ./configure was only checking for the later when
>deciding if specialauth should be enabled by default. I've added a
>check for the former, so hopefully a default ./configure will now
>correctly check passwords on True64. If you could verify this for
>me, I'd be very grateful. I'm attaching a new ./configure. Please
>be sure to do a 'make realclean' beforehand.
Using the original qpopper4.1a5 distribution with the new configure
supplied by Randall, the following occurs when ./configure is done.
<snip>
checking if ar chokes on -r... no
checking for getspnam... no
checking for getprpwnam... no
checking for getspnam in -lshadow... no
Will NOT compile in debugging code
System name: OSF1; System version: V5.1
Set OS_DEFS = " -DOSF1 -DUNIX"
<snip>
checking for set_auth_parameters in -lsecurity... yes
"use_pam is _default_"
checking for dlopen in -ldl... no
checking for pam_authenticate in -lpam... no
Can't use PAM: can't find libpam
When using the original qpopper4.1a5 distribution with the new
configure, the ./configure --without-pam results in:
<snip>
checking if ar chokes on -r... no
checking for getspnam... no
checking for getprpwnam... no
checking for getspnam in -lshadow... no
Will NOT compile in debugging code
System name: OSF1; System version: V5.1
Set OS_DEFS = " -DOSF1 -DUNIX"
<snip>
checking for set_auth_parameters in -lsecurity... yes
"use_pam is no"
checking for dlopen in -ldl... no
checking for pam_authenticate in -lpam... no
Can't use PAM: can't find libpam
Here's the configure results when new configure is used with the
qpopper4.1a5 distrubution that contains patches supplied by Hujimu Umemoto.
<snip>
checking if ar chokes on -r... no
checking for getspnam... no
checking for getprpwnam... no
checking for getspnam in -lshadow... no
Will NOT compile in debugging code
System name: OSF1; System version: V5.1
Set OS_DEFS = " -DOSF1 -DUNIX"
<snip>
checking for set_auth_parameters in -lsecurity... yes
"use_pam is _default_"
checking for dlopen in -ldl... no
checking for pam_authenticate in -lpam... no
Can't use PAM: can't find libpam
I am not sure why configure is not finding getprpwnam. This system
is definitely configured for C2 security. If you want, I can supply
config.log files.
Vic Summerour
Date: Wed, 5 Dec 2007 19:02:50 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1a6 available
Qpopper 4.1a6 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
Changes from 4.1.a6 to 4.1.a7:
------------------------------
1. Updated IPv6 support (thanks to Hajimu UMEMOTO).
- Check for socklen_t
Note: There will be another update coming soon for the Tru64 thing.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
Man is the only animal that can remain on friendly terms with the
victims he intends to eat until he eats them. - -Samuel Butler
From: James Medley <jmedley at aesrg dot tamu dot edu>
Subject: Too few arguments for the pass command
Date: Mon, 17 Dec 2007 08:52:05 -0600
Good Morning,
I have a client who cannot relay mail from home even though I have
entered his IP into the access file. This person is using Outlook for
his client. (Names have been changed to protect the innocent).
Thanks Much,
Jim
Mac OS X 10.4.10
Qpopper 4.0.9
>
> Dec 15 10:56:04 AESRG-2 popper[23764]: dummyaesrg.tamu.edu at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR [AUTH] Password
> supplied for "dummyaesrg.tamu.edu" is incorrect.
> Dec 15 10:56:20 AESRG-2 popper[23766]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR Too few
> arguments for the pass command.
> Dec 15 10:56:20 AESRG-2 popper[23766]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR POP EOF or I/O
> Error
> Dec 15 10:56:43 AESRG-2 postfix/smtpd[23728]: warning:
> 148.250.25.66.relays.ordb.org: RBL lookup error: Host or domain name
> not found. Name service error for name=148.250.25.66.relays.ordb.org
> type=A: Host not found, try again
> Dec 15 10:56:44 AESRG-2 postfix/smtpd[23728]: warning:
> 148.250.25.66.sbl-xbl.spamhaus.org: RBL lookup error: Host or domain
> name not found. Name service error for
> name=148.250.25.66.sbl-xbl.spamhaus.org type=A: Host not found, try
> again
> Dec 15 10:56:46 AESRG-2 popper[23767]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR Too few
> arguments for the pass command.
> Dec 15 10:56:46 AESRG-2 popper[23767]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR POP EOF or I/O
> Error
> Dec 15 10:57:12 AESRG-2 popper[23772]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR Too few
> arguments for the pass command.
> Dec 15 10:57:12 AESRG-2 popper[23772]: dummy at
> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR POP EOF or I/O
> Error
>
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: Too few arguments for the pass command
Date: Mon, 17 Dec 2007 13:41:32 -0800
On Dec 17, 2007, at 06:52, James Medley wrote:
> Good Morning,
>
> I have a client who cannot relay mail from home even though I have
> entered his IP into the access file. This person is using Outlook
> for his client. (Names have been changed to protect the innocent).
>
> Thanks Much,
> Jim
>
> Mac OS X 10.4.10
> Qpopper 4.0.9
>
>>
>> Dec 15 10:56:04 AESRG-2 popper[23764]: dummyaesrg.tamu.edu at
>> cpexx-xx-xxx-xxx.gt.res.rr.com (xx.xx.xxx.xxx): -ERR [AUTH] Password
>> supplied for "dummyaesrg.tamu.edu" is incorrect.
I would suggest correcting the password issue first. The other
problem might be fallout from this.
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Tue, 8 Apr 2008 09:21:31 +0000
Subject: Qpopper failure while using with pam option enabled
--_000_9C7EF3538272C1469E834EFA2D2378A403C129A53BG3W0067americ_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
I have built qpopper(4.0.9) on hpux 11.11 using --with-pam option.
But when I try to test this I am getting the following o/p.
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test
Connection closed by foreign host.
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598, resp=0x7f
7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from /usr/lib/libpam.1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from /usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from /usr/lib/security/libpam_uni
x.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at pop_pass.c:56
4
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at popper.c:349
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv) is generated withi
n __pam_input_output with num_msg=3 .msg[1] is showing bad address
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc services
that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but PAM_qpopper_conv is
unable to access the msg memory structure
When I gave wrong password I am getting this error
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test1
-ERR [AUTH] PAM authentication failed for user "test": Authentication faile
d (9)
+OK Pop server at skoda.ind.hp.com signing off.
Connection closed by foreign host.
Seems it is authenticating but not able to read the msg structure
Hope you can help me to fix this issue or do I need to send any additional
information regard this issue.
Thanks & Regards,
Ravindranath
--_000_9C7EF3538272C1469E834EFA2D2378A403C129A53BG3W0067americ_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P>Hi,<BR> I have built qpopper(4
.0.9)
on hpux 11.11 using --with-pam option.<BR>But when I try to test this I am
getting the following o/p.<BR><BR># telnet localhost
110<BR>Trying...<BR>Connected to localhost.<BR>Escape character is '^]'.<BR
>+OK
Qpopper (version 4.0.9) at skoda.ind.hp.com starting.<BR>user test<BR>+OK
Password required for test.<BR>pass test<BR>Connection closed by foreign
host.<BR><BR>when I debugged with gdb backtrace looks like this<BR><BR>#0&n
bsp;
0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598,
resp=0x7f7f6520,<BR> appdata_ptr=0x7f7f0bb8) at
pop_pass.c:442<BR>#1 0x7aeb5f10 in __pam_input_output+0x128 () from
/usr/lib/libpam.1<BR>#2 0x7aeb5d90 in __pam_display_msg+0x24 () from
/usr/lib/libpam.1<BR>#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from
/usr/lib/security/libpam_unix.1<BR>#4 0x7aeb3a90 in pam_setcred+0xec
()
from /usr/lib/libpam.1<BR>#5 0x1c754 in auth_user (p=0x7f7f0bb8,
pw=0x7f7f1d24) at pop_pass.c:564<BR>#6 0x1ca68 in pop_pass (p=0x7
f7f0bb8)
at pop_pass.c:1261<BR>#7 0x237f0 in qpopper (argc=1, argv=0x7f7f0
9ec) at
popper.c:349<BR>#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at
main.c:168<BR><BR>the <STRONG>msg</STRONG> structure(second argument for&nb
sp;
PAM_qpopper_conv) is generated within __pam_input_output with num_msg=3 .
msg[1]
is showing bad address<BR><BR>(gdb) p (char *) msg[0]->msg<BR>$26 =
0x7f7f2498 "Removing root credentials would break the rpc services
that"<BR>(gdb) p (char *) msg[1]->msg<BR>Error accessing memory address
0x4:
Bad address.<BR><BR>In libpam library,<STRONG>msg</STRONG> structure is cre
ated
properly but PAM_qpopper_conv is unable to access the <STRONG>msg</STRONG>
memory structure</P>
<P><BR><BR>When I gave wrong password I am getting this
error<BR><BR><BR># telnet localhost 110<BR>Trying...<BR>Connected to
localhost.<BR>Escape character is '^]'.<BR>+OK Qpopper (version 4.0.9) at
skoda.ind.hp.com starting.<BR>user test<BR>+OK Password required for
test.<BR>pass test1<BR>-ERR [AUTH] PAM authentication failed for user "test
":
Authentication failed (9)<BR>+OK Pop server at skoda.ind.hp.com signing
off.<BR>Connection closed by foreign host.<BR><BR><BR>Seems it is
authenticating but not able to read the <STRONG>msg</STRONG> structure </P>
<P>Hope you can help me to fix this issue or do I need to s
end
any additional information regard this issue.</P>
<P>Thanks & Regards,</P>
<P>Ravindranath</P></BODY></HTML>
--_000_9C7EF3538272C1469E834EFA2D2378A403C129A53BG3W0067americ_--
Date: Tue, 8 Apr 2008 18:24:13 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Qpopper failure while using with pam option enabled
Re: Qpopper failure while using with pam option
enabled
At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:
Hi,
I have built qpopper(4.0.9)
on hpux 11.11 using --with-pam option.
But when I try to test this I am getting the following o/p.
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test
Connection closed by foreign host.
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598,
resp=0x7f7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from
/usr/lib/libpam.1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from
/usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from
/usr/lib/security/libpam_unix.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at
pop_pass.c:564
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at
popper.c:349
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv)
is generated within __pam_input_output with num_msg=3 .msg[1] is
showing bad address
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc
services that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but
PAM_qpopper_conv is unable to access the msg memory
structure
When I gave wrong password I am getting this error
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test1
-ERR [AUTH] PAM authentication failed for user "test":
Authentication failed (9)
+OK Pop server at skoda.ind.hp.com signing off.
Connection closed by foreign host.
Seems it is authenticating but not able to read the msg
structure
Hope you can help me to fix this
issue or do I need to send any additional information regard
this issue.
Thanks & Regards,
Ravindranath
I'm puzzled. Did you build from the original 4.0.9 sources
or from a package?
I'm wondering if perhaps there is a problem with a library
mismatch from a precompiled or intermediate file?
You could try building 4.0.11 to see if it is better.
I'd also suggest getting a Qpopper trace just to see what it
shows.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t
<tracefile-path>'.
4. Send inetd (or xinetd) a HUP signal.
(Steps 3 and 4 are only needed if you use inetd (or xinetd). In
standalone mode, you can add '-d' or '-t <tracefile-path>' to
the command line directly.)
(In either standalone or inetd mode, if you use a configuration file
you can add 'set debug' or 'set tracefile = <tracefile>' to
either a global or user-specific configuration file instead of steps 3
and 4.)
This causes detailed tracing to be written to the syslog or to the
file specified as 'tracefile'.
If you're still getting a crash, I'd suggest a kernel trace using
ktrace(1) or whatever is the HPUX tool. Normally, the way to do
this is to modify the inetd or xinetd line to run qpopper via ktrace,
usually on a different port so as to not affect production users
(unless this is on a test system). For standalone on a test
system, also run qpopper from ktrace.
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Wed, 9 Apr 2008 09:08:13 +0000
Subject: RE: Qpopper failure while using with pam option enabled
--_003_9C7EF3538272C1469E834EFA2D2378A403C129AA6FG3W0067americ_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Randell,
Thanks a lot for the quick response.
I have taken the qoppper source from this location ftp://ftp.qualcomm.c=
om/eudora/servers/unix/popper/ .Also I did'nt get any mismatched libraries
issues while
compiling.
This is the configraion script I used for compiling qpopper
./configure --prefix=/opt/iexpress/qpopper --with-openssl=/opt/openssl
--with-pam=pop3 --enable-low-debug --enable-debugging
(/opt is standard location in hpux)
And I debugged qpopper with -t option and TUSC(Trace Unix System Calls.. h
ope it is similar to ktrace in linux)
But these results are similar to the result when I compiled qoppper with
gdb(gnudebugger).
I am attaching the corresponding logs.
trace.hp is the log for popper when debugged with -t option
kerneltrace.hp is the log for popper when debugged with tusc (These logs ca
n be better viewed in wordpad)
Can you suggest solution if any.
Thanks & Regards,
Ravindranath
________________________________
From: Randall Gellens [mailto:randy@qualcomm.com]
Sent: Wednesday, April 09, 2008 6:54 AM
To: Ravindranath, Chavalam
Cc: qpopper@lists.pensive.org
Subject: Re: Qpopper failure while using with pam option enabled
At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:
Hi,
I have built qpopper(4.0.9) on hpux 11.11 using --with-pam
option.
But when I try to test this I am getting the following o/p.
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test
Connection closed by foreign host.
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598, res
p=0x7f7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from /usr/lib/libpam.
1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from /usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from /usr/lib/security/li
bpam_unix.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at pop_p
ass.c:564
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at popper.c:34
9
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv) is generat
ed within __pam_input_output with num_msg=3 .msg[1] is showing bad addres
s
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc s
ervices that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but PAM_qpopper
_conv is unable to access the msg memory structure
When I gave wrong password I am getting this error
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test1
-ERR [AUTH] PAM authentication failed for user "test": Authenticati
on failed (9)
+OK Pop server at skoda.ind.hp.com signing off.
Connection closed by foreign host.
Seems it is authenticating but not able to read the msg structure
Hope you can help me to fix this issue or do I need to send any ad
ditional information regard this issue.
Thanks & Regards,
Ravindranath
I'm puzzled. Did you build from the original 4.0.9 sources or from a packa
ge?
I'm wondering if perhaps there is a problem with a library mismatch from a
precompiled or intermediate file?
You could try building 4.0.11 to see if it is better.
I'd also suggest getting a Qpopper trace just to see what it shows.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t <tracefile-pat
h>'.
4. Send inetd (or xinetd) a HUP signal.
(Steps 3 and 4 are only needed if you use inetd (or xinetd). In standalone
mode, you can add '-d' or '-t <tracefile-path>' to the command line direct
ly.)
(In either standalone or inetd mode, if you use a configuration file you ca
n add 'set debug' or 'set tracefile = <tracefile>' to either a global or
user-specific configuration file instead of steps 3 and 4.)
This causes detailed tracing to be written to the syslog or to the file spe
cified as 'tracefile'.
If you're still getting a crash, I'd suggest a kernel trace using ktrace(1)
or whatever is the HPUX tool. Normally, the way to do this is to modify t
he inetd or xinetd line to run qpopper via ktrace, usually on a different p
ort so as to not affect production users (unless this is on a test system).
For standalone on a test system, also run qpopper from ktrace.
--_003_9C7EF3538272C1469E834EFA2D2378A403C129AA6FG3W0067americ_
Content-Type: application/octet-stream; name="kerneltrace.hp"
Content-Description: kerneltrace.hp
Content-Disposition: attachment; filename="kerneltrace.hp"; size=21900;
creation-date="Wed, 09 Apr 2008 08:48:46 GMT";
modification-date="Wed, 09 Apr 2008 08:48:46 GMT"
Content-Transfer-Encoding: base64
--_003_9C7EF3538272C1469E834EFA2D2378A403C129AA6FG3W0067americ_
Content-Type: application/octet-stream; name="trace.hp"
Content-Description: trace.hp
Content-Disposition: attachment; filename="trace.hp"; size=5418;
creation-date="Wed, 09 Apr 2008 08:45:21 GMT";
modification-date="Wed, 09 Apr 2008 08:45:21 GMT"
Content-Transfer-Encoding: base64
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Fri, 25 Apr 2008 10:36:54 +0000
Subject: RE: Qpopper failure while using with pam option enabled
Hi,
I have compiled Qpopper-4.0.9 with --with-pam option on hpux11iv1
where it is not working properly,but Qpopper-4.0.5 is not giving issues if
I give this option.You can find details of the problem below.
Thanks & Regards,
Ravindranath
-----Original Message-----
From: Ravindranath, Chavalam
Sent: Wednesday, April 09, 2008 2:38 PM
To: 'Randall Gellens'
Cc: qpopper@lists.pensive.org
Subject: RE: Qpopper failure while using with pam option enabled
Hi Randell,
Thanks a lot for the quick response.
I have taken the qoppper source from this location ftp://ftp.qualcomm.c=
om/eudora/servers/unix/popper/ .Also I did'nt get any mismatched libraries
issues while compiling.
This is the configraion script I used for compiling qpopper
./configure --prefix=/opt/iexpress/qpopper --with-openssl=/opt/openssl
--with-pam=pop3 --enable-low-debug --enable-debugging
(/opt is standard location in hpux)
And I debugged qpopper with -t option and TUSC(Trace Unix System Calls.. h
ope it is similar to ktrace in linux)
But these results are similar to the result when I compiled qoppper with
gdb(gnudebugger).
I am attaching the corresponding logs.
trace.hp is the log for popper when debugged with -t option kerneltrace.hp
is the log for popper when debugged with tusc (These logs can be better vie
wed in wordpad)
Can you suggest solution if any.
Thanks & Regards,
Ravindranath
________________________________
From: Randall Gellens [mailto:randy@qualcomm.com]
Sent: Wednesday, April 09, 2008 6:54 AM
To: Ravindranath, Chavalam
Cc: qpopper@lists.pensive.org
Subject: Re: Qpopper failure while using with pam option enabled
At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:
Hi,
I have built qpopper(4.0.9) on hpux 11.11 using --with-pam
option.
But when I try to test this I am getting the following o/p.
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test
Connection closed by foreign host.
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598, res
p=0x7f7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from /usr/lib/libpam.
1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from /usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from /usr/lib/security/li
bpam_unix.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at pop_p
ass.c:564
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at popper.c:34
9
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv) is generat
ed within __pam_input_output with num_msg=3 .msg[1] is showing bad addres
s
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc s
ervices that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but PAM_qpopper
_conv is unable to access the msg memory structure
When I gave wrong password I am getting this error
# telnet localhost 110
Trying...
Connected to localhost.
Escape character is '^]'.
+OK Qpopper (version 4.0.9) at skoda.ind.hp.com starting.
user test
+OK Password required for test.
pass test1
-ERR [AUTH] PAM authentication failed for user "test": Authenticati
on failed (9)
+OK Pop server at skoda.ind.hp.com signing off.
Connection closed by foreign host.
Seems it is authenticating but not able to read the msg structure
Hope you can help me to fix this issue or do I need to send any ad
ditional information regard this issue.
Thanks & Regards,
Ravindranath
I'm puzzled. Did you build from the original 4.0.9 sources or from a packa
ge?
I'm wondering if perhaps there is a problem with a library mismatch from a
precompiled or intermediate file?
You could try building 4.0.11 to see if it is better.
I'd also suggest getting a Qpopper trace just to see what it shows.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t <tracefile-pat
h>'.
4. Send inetd (or xinetd) a HUP signal.
(Steps 3 and 4 are only needed if you use inetd (or xinetd). In standalone
mode, you can add '-d' or '-t <tracefile-path>' to the command line direct
ly.)
(In either standalone or inetd mode, if you use a configuration file you ca
n add 'set debug' or 'set tracefile = <tracefile>' to either a global or
user-specific configuration file instead of steps 3 and 4.)
This causes detailed tracing to be written to the syslog or to the file spe
cified as 'tracefile'.
If you're still getting a crash, I'd suggest a kernel trace using ktrace(1)
or whatever is the HPUX tool. Normally, the way to do this is to modify t
he inetd or xinetd line to run qpopper via ktrace, usually on a different p
ort so as to not affect production users (unless this is on a test system).
For standalone on a test system, also run qpopper from ktrace.
Date: Sun, 27 Apr 2008 16:40:49 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: RE: Qpopper failure while using with pam option enabled
--============_-1002782628==_============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>RE: Qpopper failure while using with pam option
enabled</title></head><body>
<div>At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:</div>
<div><br></div>
<blockquote type="cite" cite>when I debugged with gdb backtrace looks
like this<br>
<br>
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598,
resp=0x7f7f6520,<br>
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442<br>
#1 0x7aeb5f10 in __pam_input_output+0x128 () from
/usr/lib/libpam.1<br>
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from
/usr/lib/libpam.1<br>
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from
/usr/lib/security/libpam_unix.1<br>
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1<br>
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at
pop_pass.c:564<br>
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261<br>
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at
popper.c:349<br>
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168<br>
<br>
the<b> msg</b> structure(second argument for PAM_qpopper_conv)
is generated within __pam_input_output with num_msg=3 .msg[1] is
showing bad address<br>
<br>
(gdb) p (char *) msg[0]->msg<br>
$26 = 0x7f7f2498 "Removing root credentials would break the rpc
services that"<br>
(gdb) p (char *) msg[1]->msg<br>
Error accessing memory address 0x4: Bad address.<br>
</blockquote>
<blockquote type="cite" cite>In libpam library,<b>msg</b> structure is
created properly but PAM_qpopper_conv is unable to access the<b>
msg</b> memory structure</blockquote>
<div><br></div>
<blockquote type="cite" cite>Seems it is authenticating but not
able to read the<b> msg</b> structure</blockquote>
<div><br></div>
<div><br></div>
<div>At 9:08 AM +0000 4/9/08, Chavalam Ravindranath wrote:<br>
</div>
<blockquote type="cite" cite>And I debugged qpopper with -t option and
TUSC(Trace Unix System Calls.. hope it is similar to ktrace in
linux)</blockquote>
<blockquote type="cite" cite>But these results are similar to the
result when I compiled qoppper with gdb(gnudebugger).<br>
I am attaching the corresponding logs.<br>
trace.hp is the log for popper when debugged with -t
option</blockquote>
<blockquote type="cite" cite>kerneltrace.hp is the log for popper when
debugged with tusc (These logs can be better viewed in
wordpad)</blockquote>
<div><br>
<br>
</div>
<div>At 10:36 AM +0000 4/25/08, Chavalam Ravindranath wrote:</div>
<blockquote type="cite" cite>I have compiled Qpopper-4.0.9 with
--with-pam option on hpux11iv1 where it is not working properly,but
Qpopper-4.0.5 is not giving issues if I give this option</blockquote>
<div><br></div>
<div>It looks like with 4.0.11, pam is trying to return an error
message:</div>
<div><br></div>
<blockquote type="cite" cite>Apr 9 12:50:29.000 2008 [10527]
PAM_qpopper_conv: msg_style[0]=3 [pop_pass.c:441]</blockquote>
<div><br></div>
<div>According to _pam_types.h, a msg_style of 3 is
PAM_ERROR_MSG.</div>
<div><br></div>
<div>The Qpopper PAM code changed a bit between 4.0.5, which works for
you, and 4.0.11, which doesn't. For example, the calls on
pam_acct_mgmt() and pam_set_cred() are in different orders.</div>
<div><br></div>
<div>I'm not a PAM expert, nor one on HPUX. I'd like to get this
resolved soon. Maybe someone on this list can help?</div>
<div><br></div>
<div>I'm attaching a pop_pass.c file to replace the one in your 4.0.11
popper/ directory. It has slightly better diagnostics for
tracing the pam calls. Can you please try it and send me the
Qpopper trace?</div>
<div><br></div>
<div>Note that file attachments are stripped by the mailing list, so
list recipients will see an empty file.</div>
--============_-1002782628==_============
Content-Id:
Content-Type: application/octet-stream; name="pop_pass.c"
Content-Disposition: attachment; filename="pop_pass.c"
Content-Transfer-Encoding: base64
--============_-1002782628==_============
Content-Type: text/html; charset="us-ascii"
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Mon, 28 Apr 2008 06:52:09 +0000
Subject: RE: Qpopper failure while using with pam option enabled
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9C26G3W0067americ_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Randall,
Thanks for the response.Can you send me the pop_pass.c file to my mail,beca
use the mailing list is stripping of the attachments.
Thanks & Regards,
Ravindranath
________________________________
From: Randall Gellens [mailto:randy@qualcomm.com]
Sent: Monday, April 28, 2008 5:11 AM
To: Ravindranath, Chavalam
Cc: qpopper@lists.pensive.org; Randall Gellens
Subject: RE: Qpopper failure while using with pam option enabled
At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598, resp=0x7f
7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from /usr/lib/libpam.1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from /usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from /usr/lib/security/libpam_uni
x.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at pop_pass.c:56
4
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at popper.c:349
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv) is generated withi
n __pam_input_output with num_msg=3 .msg[1] is showing bad address
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc services
that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but PAM_qpopper_conv is
unable to access the msg memory structure
Seems it is authenticating but not able to read the msg structure
At 9:08 AM +0000 4/9/08, Chavalam Ravindranath wrote:
And I debugged qpopper with -t option and TUSC(Trace Unix System Calls.. ho
pe it is similar to ktrace in linux)
But these results are similar to the result when I compiled qoppper with
gdb(gnudebugger).
I am attaching the corresponding logs.
trace.hp is the log for popper when debugged with -t option
kerneltrace.hp is the log for popper when debugged with tusc (These logs ca
n be better viewed in wordpad)
At 10:36 AM +0000 4/25/08, Chavalam Ravindranath wrote:
I have compiled Qpopper-4.0.9 with --with-pam option on hpux11iv1 where it
is not working properly,but Qpopper-4.0.5 is not giving issues if I give t
his option
It looks like with 4.0.11, pam is trying to return an error message:
Apr 9 12:50:29.000 2008 [10527] PAM_qpopper_conv: msg_style[0]=3 [pop_pa
ss.c:441]
According to _pam_types.h, a msg_style of 3 is PAM_ERROR_MSG.
The Qpopper PAM code changed a bit between 4.0.5, which works for you, and
4.0.11, which doesn't. For example, the calls on pam_acct_mgmt() and pam_s
et_cred() are in different orders.
I'm not a PAM expert, nor one on HPUX. I'd like to get this resolved soon.
Maybe someone on this list can help?
I'm attaching a pop_pass.c file to replace the one in your 4.0.11 popper/ d
irectory. It has slightly better diagnostics for tracing the pam calls. C
an you please try it and send me the Qpopper trace?
Note that file attachments are stripped by the mailing list, so list recipi
ents will see an empty file.
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9C26G3W0067americ_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: Qpopper failure while using with pam option enabled<
/TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>BLOCKQUOTE {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
DL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
UL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
OL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
LI {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=234084906-28042008><FONT face=A
rial
color=#0000ff size=2>Hi Randall,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=234084906-28042008><FONT face=A
rial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=234084906-28042008><FONT face=A
rial
color=#0000ff size=2>Thanks for the response.Can you send me the pop_pa
ss.c file
to my mail,because the mailing list is stripping of the
attachments.</FONT> </SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=234084906-28042008></SPAN> <
/DIV>
<DIV dir=ltr align=left><SPAN class=234084906-28042008><FONT face=A
rial
color=#0000ff size=2>Thanks & Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=234084906-28042008><FONT face=A
rial
color=#0000ff size=2>Ravindranath</FONT></SPAN></DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B> Randa
ll Gellens
[mailto:randy@qualcomm.com] <BR><B>Sent:</B> Monday, April 28, 2008 5:11
AM<BR><B>To:</B> Ravindranath, Chavalam<BR><B>Cc:</B> qpopper@lists.pensive=
.org;
Randall Gellens<BR><B>Subject:</B> RE: Qpopper failure while using with pam
option enabled<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">when I debugged with gdb backtrace look
s like
this<BR><BR>#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f
7f6598,
resp=0x7f7f6520,<BR> appdata_ptr=0x7f7f0bb8) at
pop_pass.c:442<BR>#1 0x7aeb5f10 in __pam_input_output+0x128 () from
/usr/lib/libpam.1<BR>#2 0x7aeb5d90 in __pam_display_msg+0x24 () fro
m
/usr/lib/libpam.1<BR>#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from
/usr/lib/security/libpam_unix.1<BR>#4 0x7aeb3a90 in pam_setcred+0xe
c ()
from /usr/lib/libpam.1<BR>#5 0x1c754 in auth_user (p=0x7f7f0bb8,
pw=0x7f7f1d24) at pop_pass.c:564<BR>#6 0x1ca68 in pop_pass
(p=0x7f7f0bb8) at pop_pass.c:1261<BR>#7 0x237f0 in qpopper (argc
=1,
argv=0x7f7f09ec) at popper.c:349<BR>#8 0x30d1c in main (argc=1,
argv=0x7f7f09ec) at main.c:168<BR><BR>the<B> msg</B> structure(second a
rgument
for PAM_qpopper_conv) is generated within __pam_input_output with
num_msg=3 .msg[1] is showing bad address<BR><BR>(gdb) p (char *)
msg[0]->msg<BR>$26 = 0x7f7f2498 "Removing root credentials would bre
ak the
rpc services that"<BR>(gdb) p (char *) msg[1]->msg<BR>Error accessing
memory address 0x4: Bad address.<BR></BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">In libpam library,<B>msg</B> structure
is
created properly but PAM_qpopper_conv is unable to access the<B> msg</B>
memory structure</BLOCKQUOTE>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">Seems it is authenticating but no
t able
to read the<B> msg</B> structure</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>At 9:08 AM +0000 4/9/08, Chavalam Ravindranath wrote:<BR></DIV>
<BLOCKQUOTE cite="" type="cite">And I debugged qpopper with -t option a
nd
TUSC(Trace Unix System Calls.. hope it is similar to ktrace in
linux)</BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">But these results are similar to the re
sult
when I compiled qoppper with gdb(gnudebugger).<BR>I am attach
ing
the corresponding logs.<BR>trace.hp is the log for popper when debugged w
ith
-t option</BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">kerneltrace.hp is the log for popper wh
en
debugged with tusc (These logs can be better viewed in wordpad)</BLOCKQUO
TE>
<DIV><BR><BR></DIV>
<DIV>At 10:36 AM +0000 4/25/08, Chavalam Ravindranath wrote:</DIV>
<BLOCKQUOTE cite="" type="cite">I have compiled Qpopper-4.0.9 with 
;
--with-pam option on hpux11iv1 where it is not working properly,but
Qpopper-4.0.5 is not giving issues if I give this option</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>It looks like with 4.0.11, pam is trying to return an error message:</
DIV>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">Apr 9 12:50:29.000 2008 [10527]
PAM_qpopper_conv: msg_style[0]=3 [pop_pass.c:441]</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>According to _pam_types.h, a msg_style of 3 is PAM_ERROR_MSG.</DIV>
<DIV><BR></DIV>
<DIV>The Qpopper PAM code changed a bit between 4.0.5, which works for you,
and
4.0.11, which doesn't. For example, the calls on pam_acct_mgmt() and
pam_set_cred() are in different orders.</DIV>
<DIV><BR></DIV>
<DIV>I'm not a PAM expert, nor one on HPUX. I'd like to get this reso
lved
soon. Maybe someone on this list can help?</DIV>
<DIV><BR></DIV>
<DIV>I'm attaching a pop_pass.c file to replace the one in your 4.0.11 popp
er/
directory. It has slightly better diagnostics for tracing the pam
calls. Can you please try it and send me the Qpopper trace?</DIV>
<DIV><BR></DIV>
<DIV>Note that file attachments are stripped by the mailing list, so list
recipients will see an empty file.</DIV></BODY></HTML>
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9C26G3W0067americ_--
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Mon, 28 Apr 2008 06:55:02 +0000
Subject: Recall: Qpopper failure while using with pam option enabled
Ravindranath, Chavalam would like to recall the message, "Qpopper failure w
hile using with pam option enabled".
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Mon, 28 Apr 2008 08:16:59 +0000
Subject: RE: Qpopper failure while using with pam option enabled
--_005_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_
Content-Type: multipart/alternative;
boundary="_000_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_"
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Randell,
I replaced the old pop_pass.c with the one you have sent.Attaching the
new trace logs.
Thanks & Regards,
Ravindranath
________________________________
From: Randall Gellens [mailto:randy@qualcomm.com]
Sent: Monday, April 28, 2008 5:11 AM
To: Ravindranath, Chavalam
Cc: qpopper@lists.pensive.org; Randall Gellens
Subject: RE: Qpopper failure while using with pam option enabled
At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:
when I debugged with gdb backtrace looks like this
#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f7f6598, resp=0x7f
7f6520,
appdata_ptr=0x7f7f0bb8) at pop_pass.c:442
#1 0x7aeb5f10 in __pam_input_output+0x128 () from /usr/lib/libpam.1
#2 0x7aeb5d90 in __pam_display_msg+0x24 () from /usr/lib/libpam.1
#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from /usr/lib/security/libpam_uni
x.1
#4 0x7aeb3a90 in pam_setcred+0xec () from /usr/lib/libpam.1
#5 0x1c754 in auth_user (p=0x7f7f0bb8, pw=0x7f7f1d24) at pop_pass.c:56
4
#6 0x1ca68 in pop_pass (p=0x7f7f0bb8) at pop_pass.c:1261
#7 0x237f0 in qpopper (argc=1, argv=0x7f7f09ec) at popper.c:349
#8 0x30d1c in main (argc=1, argv=0x7f7f09ec) at main.c:168
the msg structure(second argument for PAM_qpopper_conv) is generated withi
n __pam_input_output with num_msg=3 .msg[1] is showing bad address
(gdb) p (char *) msg[0]->msg
$26 = 0x7f7f2498 "Removing root credentials would break the rpc services
that"
(gdb) p (char *) msg[1]->msg
Error accessing memory address 0x4: Bad address.
In libpam library,msg structure is created properly but PAM_qpopper_conv is
unable to access the msg memory structure
Seems it is authenticating but not able to read the msg structure
At 9:08 AM +0000 4/9/08, Chavalam Ravindranath wrote:
And I debugged qpopper with -t option and TUSC(Trace Unix System Calls.. ho
pe it is similar to ktrace in linux)
But these results are similar to the result when I compiled qoppper with
gdb(gnudebugger).
I am attaching the corresponding logs.
trace.hp is the log for popper when debugged with -t option
kerneltrace.hp is the log for popper when debugged with tusc (These logs ca
n be better viewed in wordpad)
At 10:36 AM +0000 4/25/08, Chavalam Ravindranath wrote:
I have compiled Qpopper-4.0.9 with --with-pam option on hpux11iv1 where it
is not working properly,but Qpopper-4.0.5 is not giving issues if I give t
his option
It looks like with 4.0.11, pam is trying to return an error message:
Apr 9 12:50:29.000 2008 [10527] PAM_qpopper_conv: msg_style[0]=3 [pop_pa
ss.c:441]
According to _pam_types.h, a msg_style of 3 is PAM_ERROR_MSG.
The Qpopper PAM code changed a bit between 4.0.5, which works for you, and
4.0.11, which doesn't. For example, the calls on pam_acct_mgmt() and pam_s
et_cred() are in different orders.
I'm not a PAM expert, nor one on HPUX. I'd like to get this resolved soon.
Maybe someone on this list can help?
I'm attaching a pop_pass.c file to replace the one in your 4.0.11 popper/ d
irectory. It has slightly better diagnostics for tracing the pam calls. C
an you please try it and send me the Qpopper trace?
Note that file attachments are stripped by the mailing list, so list recipi
ents will see an empty file.
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: Qpopper failure while using with pam option enabled<
/TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>BLOCKQUOTE {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
DL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
UL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
OL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
LI {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008><FONT face=A
rial
color=#0000ff size=2>Hi Randell,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008><FONT face=A
rial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008> &n
bsp; <FONT
face=Arial color=#0000ff size=2>I replaced the old pop_pass.c w
ith the one
you have sent.Attaching the new trace logs.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008><FONT face=A
rial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008><FONT face=A
rial
color=#0000ff size=2>Thanks & Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class‘0371308-28042008><FONT face=A
rial
color=#0000ff size=2>Ravindranath</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Randall Gellens
[mailto:randy@qualcomm.com] <BR><B>Sent:</B> Monday, April 28, 2008 5:11
AM<BR><B>To:</B> Ravindranath, Chavalam<BR><B>Cc:</B> qpopper@lists.pensive=
.org;
Randall Gellens<BR><B>Subject:</B> RE: Qpopper failure while using with pam
option enabled<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>At 9:21 AM +0000 4/8/08, Chavalam Ravindranath wrote:</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">when I debugged with gdb backtrace look
s like
this<BR><BR>#0 0x1bf50 in PAM_qpopper_conv (num_msg=3, msg=0x7f
7f6598,
resp=0x7f7f6520,<BR> appdata_ptr=0x7f7f0bb8) at
pop_pass.c:442<BR>#1 0x7aeb5f10 in __pam_input_output+0x128 () from
/usr/lib/libpam.1<BR>#2 0x7aeb5d90 in __pam_display_msg+0x24 () fro
m
/usr/lib/libpam.1<BR>#3 0x7ad89fb8 in pam_sm_setcred+0x2e8 () from
/usr/lib/security/libpam_unix.1<BR>#4 0x7aeb3a90 in pam_setcred+0xe
c ()
from /usr/lib/libpam.1<BR>#5 0x1c754 in auth_user (p=0x7f7f0bb8,
pw=0x7f7f1d24) at pop_pass.c:564<BR>#6 0x1ca68 in pop_pass
(p=0x7f7f0bb8) at pop_pass.c:1261<BR>#7 0x237f0 in qpopper (argc
=1,
argv=0x7f7f09ec) at popper.c:349<BR>#8 0x30d1c in main (argc=1,
argv=0x7f7f09ec) at main.c:168<BR><BR>the<B> msg</B> structure(second a
rgument
for PAM_qpopper_conv) is generated within __pam_input_output with
num_msg=3 .msg[1] is showing bad address<BR><BR>(gdb) p (char *)
msg[0]->msg<BR>$26 = 0x7f7f2498 "Removing root credentials would bre
ak the
rpc services that"<BR>(gdb) p (char *) msg[1]->msg<BR>Error accessing
memory address 0x4: Bad address.<BR></BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">In libpam library,<B>msg</B> structure
is
created properly but PAM_qpopper_conv is unable to access the<B> msg</B>
memory structure</BLOCKQUOTE>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">Seems it is authenticating but no
t able
to read the<B> msg</B> structure</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>At 9:08 AM +0000 4/9/08, Chavalam Ravindranath wrote:<BR></DIV>
<BLOCKQUOTE cite="" type="cite">And I debugged qpopper with -t option a
nd
TUSC(Trace Unix System Calls.. hope it is similar to ktrace in
linux)</BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">But these results are similar to the re
sult
when I compiled qoppper with gdb(gnudebugger).<BR>I am attach
ing
the corresponding logs.<BR>trace.hp is the log for popper when debugged w
ith
-t option</BLOCKQUOTE>
<BLOCKQUOTE cite="" type="cite">kerneltrace.hp is the log for popper wh
en
debugged with tusc (These logs can be better viewed in wordpad)</BLOCKQUO
TE>
<DIV><BR><BR></DIV>
<DIV>At 10:36 AM +0000 4/25/08, Chavalam Ravindranath wrote:</DIV>
<BLOCKQUOTE cite="" type="cite">I have compiled Qpopper-4.0.9 with 
;
--with-pam option on hpux11iv1 where it is not working properly,but
Qpopper-4.0.5 is not giving issues if I give this option</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>It looks like with 4.0.11, pam is trying to return an error message:</
DIV>
<DIV><BR></DIV>
<BLOCKQUOTE cite="" type="cite">Apr 9 12:50:29.000 2008 [10527]
PAM_qpopper_conv: msg_style[0]=3 [pop_pass.c:441]</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>According to _pam_types.h, a msg_style of 3 is PAM_ERROR_MSG.</DIV>
<DIV><BR></DIV>
<DIV>The Qpopper PAM code changed a bit between 4.0.5, which works for you,
and
4.0.11, which doesn't. For example, the calls on pam_acct_mgmt() and
pam_set_cred() are in different orders.</DIV>
<DIV><BR></DIV>
<DIV>I'm not a PAM expert, nor one on HPUX. I'd like to get this reso
lved
soon. Maybe someone on this list can help?</DIV>
<DIV><BR></DIV>
<DIV>I'm attaching a pop_pass.c file to replace the one in your 4.0.11 popp
er/
directory. It has slightly better diagnostics for tracing the pam
calls. Can you please try it and send me the Qpopper trace?</DIV>
<DIV><BR></DIV>
<DIV>Note that file attachments are stripped by the mailing list, so list
recipients will see an empty file.</DIV></BODY></HTML>
--_000_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_--
--_005_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_
Content-Type: application/octet-stream; name="trace.log"
Content-Description: trace.log
Content-Disposition: attachment; filename="trace.log"; size=5422;
creation-date="Mon, 28 Apr 2008 08:12:43 GMT";
modification-date="Mon, 28 Apr 2008 08:12:43 GMT"
Content-Transfer-Encoding: base64
--_005_9C7EF3538272C1469E834EFA2D2378A403C14D9CE0G3W0067americ_--
Date: Fri, 2 May 2008 17:33:11 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.12 available
Qpopper 4.0.12 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Please let me know if you experience problems with this.
I'm especially interested in reports, good and bad, of PAM usage and
HPUX usage.
The full list of changes is on the FTP site, at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/Changes>.
Changes from 4.0.11 to 4.0.12:
-----------------------------
1. Fixed bug that enabled pam by default (it should
only be enabled by default on certain platforms).
2. Fixed off-by-one error in strlcpy (thanks to Derek Chan)
3. Fixed strlcpy off-by-one error when source exceeds dest (thanks
to Derek Chan for reporting this bug).
4. Prevent strlcat from examining destination past buffer size.
5. Guard strlcpy and strlcat so they aren't compiled if the
platform supplies them.
6. Fix problem with default pam values on MacOS X.
7. Fix crash if mangle string ended with header and no ")".
8. Allow 'announce-expire' configuration file option to be set to -1.
Changes from 4.0.10 to 4.0.11:
------------------------------
1. Tweaked pam so that default isn't enabled accidently.
2. Added check for getprpwnam() and if found, enable
specialauth, just like we do for getspnam(). This
should fix default configuration on platforms like
Tru64 (thanks to J Bacher for his help on this).
3. Added more checks to try and find getprpwnam().
4. Fixed bug that enabled pam by default (it should
only be default enabled on certain platforms).
5. Fixed typo in README (thanks to Eric Klien).
Changes from 4.0.9 to 4.0.10:
-----------------------------
1. Correct milliseconds calculation (thanks to Jose Marcio
Martins da Cruz for the patch).
2. Added '-d' flag to 'install' (to create directories).
3. Fix error message in 'make realclean' on some platforms.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
Some days you feel like Schrodinger's cat. --M. S. Hutchenreuther
Date: Fri, 2 May 2008 17:34:36 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1b8 available
Qpopper 4.1b8 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
Changes from 4.1.a7 to 4.1.b8:
------------------------------
1. Added more checks to try and find getprpwnam().
2. Fixed bug that enabled pam by default (it should
only be enabled by default on certain platforms).
3. Fixed typo in README (thanks to Eric Klien).
4. Further checks for getaddrinfo() on Tru64 (thanks
to Vic Summerour).
5. Fixed typo in README (thanks to Eric Klien).
6. Fixed strlcpy off-by-one error when source exceeds dest (thanks
to Derek Chan for reporting this bug).
7. Prevent strlcat from examining destination past buffer size.
8. Guard strlcpy and strlcat so they aren't compiled if the
platform supplies them.
9. Fix problem with default pam values on MacOS X.
10. Fix pop_parse.c compilation errors on some compilers.
11. Fix crash if mangle string ended with header and no ")".
12. Allow 'announce-expire' configuration file option to be set to -1.
Changes from 4.1.a6 to 4.1.a7:
------------------------------
1. Tweaked pam so that default isn't enabled accidently.
2. Added check for getprpwnam() and if found, enable
specialauth, just like we do for getspnam(). This
should fix default configuration on platforms like
Tru64 (thanks to J Bacher for his help on this).
Changes from 4.1.a5 to 4.1.a6:
------------------------------
1. Updated IPv6 support (thanks to Hajimu UMEMOTO).
- Check for socklen_t
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
An economist is an expert who will know tomorrow why the things he
predicted yesterday didn't happen today. --Laurence J. Peter
Date: Sun, 4 May 2008 16:42:49 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Easier Access to Qpopper Source Repository
The Qpopper source code repository can now be accessed from a web
browser, at <http://qpopper.pensive.org:8989>. Also, the
instructions for full access to the repository, using Perforce
clients, have been simplified
<http://qpopper.pensive.org/Qpopper-Perforce.html>.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
They say that 90 per cent of TV is junk. But 90 per cent
of *everything* is junk.
--Gene Roddenberry, interview in TV Guide, Apr. 27, 1974
(quoting Sturgeon's Revelation: "Ninety percent of
everything is crap.")
From: "Sasa" <sasa at shoponweb dot it>
Subject: Password incorrect
Date: Mon, 5 May 2008 12:30:28 +0200
Hi, I have a strange problem with QPopper4.0.9..occasionally I have with
same users the error message that the password for check mail is incorrect
and for to resolve this problem I must delete user/mailbox (I have use linux
users) and the '/var/spool/mail/myuser.pop' file.
Thanks.
------
Salvatore.
From: "Giannis Mantzouranis" <jman at physics dot upatras dot gr>
Subject: Problems compiling qpopper 4.0.12 with openssl
Date: Mon, 5 May 2008 21:51:33 +0300
Hello
I had compiled qpopper 4.0.12 with openssl 0.8.9g patching the Makefile in
the popper directory with -ldl so that it compiles fluently with this
version of openssl. The server works in plain sessions on port 110 but dies
with the following error message
Expected comment or end of line; found ""
at line 2 of config file /etc/mail/qpoppera.config
I must address that I kept the same configuration with qpopper 4.0.9 witch I
used already. I would appreciate any comments or suggestions
Thanks In Advance
Giannis Mantzouranis
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: Password incorrect
Date: Mon, 5 May 2008 11:48:27 -0700
On May 5, 2008, at 03:30, Sasa wrote:
> Hi, I have a strange problem with QPopper4.0.9..occasionally I have
> with same users the error message that the password for check mail
> is incorrect and for to resolve this problem I must delete user/
> mailbox (I have use linux users) and the '/var/spool/mail/
> myuser.pop' file.
Qpopper is quite sensitive to permissions. You should check carefully
the permissions on those files when it happens. Also, it might be
helpful to run ktrace, strace etc. on qpopper when the problem is
occuring. Then look to see which check is causing the error message.
Date: Mon, 5 May 2008 12:26:43 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Problems compiling qpopper 4.0.12 with openssl
Hi Giannis,
At 9:51 PM +0300 5/5/08, Giannis Mantzouranis wrote:
> I had compiled qpopper 4.0.12 with openssl 0.8.9g patching the
> Makefile in the popper directory with -ldl so that it compiles
> fluently with this version of openssl.
Why did you need to patch popper/Makefile? What did you use for ./configure?
> The server works in plain sessions on port 110 but dies with the
> following error message
> Expected comment or end of line; found ""
> at line 2 of config file /etc/mail/qpoppera.config
> I must address that I kept the same configuration with qpopper
> 4.0.9 witch I used already. I would appreciate any comments or
> suggestions
This looks to have been introduced in 4.0.12 as part of allowing
"announce-expire" to be set to -1. This change will be backed out
for 4.0.13 (with a better fix in 4.1b9). For now, try changing your
/etc/mail/qpoppera.config file so that for TLS options that take file
names, either put the file name in quotes, or just add a blank space
after the file name.
Please let me know if this fixes it for you, and also about why you
needed to modify popper/Makefile.
Thank you.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
The single biggest problem in communication is the illusion that it
has taken place. --G. B. Shaw
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: Problems compiling qpopper 4.0.12 with openssl
Date: Mon, 5 May 2008 12:35:44 -0700
On May 5, 2008, at 11:51, Giannis Mantzouranis wrote:
> Hello
> I had compiled qpopper 4.0.12 with openssl 0.8.9g patching the
> Makefile in the popper directory with -ldl so that it compiles
> fluently with this version of openssl. The server works in plain
> sessions on port 110 but dies with the following error message
> Expected comment or end of line; found ""
> at line 2 of config file /etc/mail/qpoppera.config
> I must address that I kept the same configuration with qpopper 4.0.9
> witch I used already. I would appreciate any comments or suggestions
You didn't let us know what line 2 of the config file says, but I
suspect its one of the TLS key file names. There seems to be a bug in
4.0.12 with the way it parses those file names. There are 2 temporary
workarounds if that is the problem: Add a space after the end of the
file name, or put the file name in quotes. Both of those worked for me.
Date: Tue, 06 May 2008 12:12:31 +0200
From: Martin Kellermann <kellermann at sk-datentechnik dot com>
Subject: configure / make error 4.0.12
--=====================_1213385828==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
hi,
i get following error on configure:
./configure: line 3035: WARNING:: command not found
my configure line is
./configure --prefix=/usr
--sysconfdir=/etc --enable-shy --with-pam=pop3
and an error on "make install":
/bin/install -c -md 0644 -o root ./man/popper.8 /usr/man/man8/
/bin/install: invalid mode `d'
make: *** [install] Error 1
strange... your Makefile is: "install -c -md 0644 -o ..." !?
shouldn't it be "install -c -d -m 0644 -o..." ??
when removing the "d", installation works.
install --version => install (coreutils) 5.2.1
regards
At 02:33 03.05.2008, you wrote:
>Qpopper 4.0.12 is available at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
>
>Please let me know if you experience problems with this.
>
>I'm especially interested in reports, good and
>bad, of PAM usage and HPUX usage.
>
>The full list of changes is on the FTP site, at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/Changes>.
>
>Changes from 4.0.11 to 4.0.12:
>-----------------------------
> 1. Fixed bug that enabled pam by default (it should
> only be enabled by default on certain platforms).
> 2. Fixed off-by-one error in strlcpy (thanks to Derek Chan)
> 3. Fixed strlcpy off-by-one error when source exceeds dest (thanks
> to Derek Chan for reporting this bug).
> 4. Prevent strlcat from examining destination past buffer size.
> 5. Guard strlcpy and strlcat so they aren't compiled if the
> platform supplies them.
> 6. Fix problem with default pam values on MacOS X.
> 7. Fix crash if mangle string ended with header and no ")".
> 8. Allow 'announce-expire' configuration file option to be set to -1.
>
>
>Changes from 4.0.10 to 4.0.11:
>------------------------------
> 1. Tweaked pam so that default isn't enabled accidently.
> 2. Added check for getprpwnam() and if found, enable
> specialauth, just like we do for getspnam(). This
> should fix default configuration on platforms like
> Tru64 (thanks to J Bacher for his help on this).
> 3. Added more checks to try and find getprpwnam().
> 4. Fixed bug that enabled pam by default (it should
> only be default enabled on certain platforms).
> 5. Fixed typo in README (thanks to Eric Klien).
>
>
>Changes from 4.0.9 to 4.0.10:
>-----------------------------
> 1. Correct milliseconds calculation (thanks to Jose Marcio
> Martins da Cruz for the patch).
> 2. Added '-d' flag to 'install' (to create directories).
> 3. Fix error message in 'make realclean' on some platforms.
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly-selected tag: ---------------
>Some days you feel like Schrodinger's cat. --M. S. Hutchenreuther
___________________________
sk datentechnik GmbH
Stalleickenweg 5
44867 Bochum
Tel: 02327-9501-0
Fax: 02327-9501-25
HRB 6176 AG Bochum
Geschäftsführer: Martin Kellermann
USt-ID DE196142436
--=====================_1213385828==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<body>
hi,<br><br>
i get following error on configure:<br>
<x-tab> </x-tab>
./configure: line 3035: WARNING:: command not found<br><br>
my configure line is <br>
<x-tab> </x-tab>
./configure --prefix=/usr --sysconfdir=/etc --enable-shy
--with-pam=pop3<br><br>
<br>
and an error on "make install":<br><br>
<x-tab> </x-tab>
/bin/install -c -md 0644 -o root ./man/popper.8 /usr/man/man8/<br>
<x-tab> </x-tab>
/bin/install: invalid mode `d'<br>
<x-tab> </x-tab>make: ***
[install] Error 1<br><br>
strange... your Makefile is: "install -c -md 0644 -o ..."
!?<br>
shouldn't it be "install -c -d -m 0644 -o..." ??<br>
when removing the "d", installation works.<br>
<x-tab> </x-tab>install
--version => install (coreutils) 5.2.1<br><br>
regards<br><br>
<br><br>
At 02:33 03.05.2008, you wrote:<br>
<blockquote type=cite class=cite cite="">Qpopper 4.0.12 is available a
t
<<a href="ftp://ftp.qualcomm.com/eudora/servers/unix/popper/" eudora=
"autourl">
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/</a>>.<br><br>
Please let me know if you experience problems with this.<br><br>
I'm especially interested in reports, good and bad, of PAM usage and HPUX
usage.<br><br>
The full list of changes is on the FTP site, at
<<a
s" eudora="autourl">
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/Changes</a>
>.<br><br>
Changes from 4.0.11 to 4.0.12:<br>
-----------------------------<br>
1. Fixed bug that enabled pam by default (it should<br>
only be enabled by default on certain
platforms).<br>
2. Fixed off-by-one error in strlcpy (thanks to Derek
Chan)<br>
3. Fixed strlcpy off-by-one error when source exceeds dest
(thanks<br>
to Derek Chan for reporting this bug).<br>
4. Prevent strlcat from examining destination past buffer
size.<br>
5. Guard strlcpy and strlcat so they aren't compiled if
the<br>
platform supplies them.<br>
6. Fix problem with default pam values on MacOS X.<br>
7. Fix crash if mangle string ended with header and no
")".<br>
8. Allow 'announce-expire' configuration file option to be
set to -1.<br><br>
<br>
Changes from 4.0.10 to 4.0.11:<br>
------------------------------<br>
1. Tweaked pam so that default isn't enabled accidently.<br>
2. Added check for getprpwnam() and if found, enable<br>
specialauth, just like we do for
getspnam(). This<br>
should fix default configuration on platforms
like<br>
Tru64 (thanks to J Bacher for his help on
this).<br>
3. Added more checks to try and find getprpwnam().<br>
4. Fixed bug that enabled pam by default (it should<br>
only be default enabled on certain
platforms).<br>
5. Fixed typo in README (thanks to Eric Klien).<br><br>
<br>
Changes from 4.0.9 to 4.0.10:<br>
-----------------------------<br>
1. Correct milliseconds calculation (thanks to Jose
Marcio<br>
Martins da Cruz for the patch).<br>
2. Added '-d' flag to 'install' (to create directories).<br>
3. Fix error message in 'make realclean' on some
platforms.<br>
-- <br>
Randall Gellens<br>
Opinions are personal; facts are
suspect; I speak for myself only<br>
-------------- Randomly-selected tag: ---------------<br>
Some days you feel like Schrodinger's cat. --M. S.
Hutchenreuther<br>
</blockquote>
<x-sigsep><p></x-sigsep>
<font face="Arial, Helvetica" size=2><br><br>
___________________________<br><br>
sk datentechnik GmbH<br>
Stalleickenweg 5<br>
44867 Bochum<br>
Tel: 02327-9501-0<br>
Fax: 02327-9501-25<br><br>
</font><font face="Arial, Helvetica" size=1> HRB 6176 AG
Bochum<br>
Geschäftsführer: Martin Kellermann<br>
USt-ID DE196142436<br>
</font></body>
</html>
--=====================_1213385828==.ALT--
From: "Sasa" <sasa at shoponweb dot it>
Subject: Re: Password incorrect
Date: Tue, 6 May 2008 16:30:47 +0200
Hi and thanks for you aid, now I haven't problem and permission are:
-rw-rw---- 1 pippo.pluto mail 8890312 6 mag 13:00 pippo.pluto
-rw------- 1 pippo.pluto mail 10 6 mag 13:00 pippo.pluto.lock
..but why occassionaly I have a problem about incorrect password ? when the
problem is present the
password is incorrect because the permission are corrupted ? and because
happen this ?
Thanks.
------
Salvatore.
----- Original Message -----
From: "Doug Hardie" <bc979@lafn.org>
To: "Sasa" <sasa@shoponweb.it>
Cc: "Subscribers of Qpopper" <qpopper@lists.pensive.org>
Sent: Monday, May 05, 2008 8:48 PM
Subject: Re: Password incorrect
> On May 5, 2008, at 03:30, Sasa wrote:
>
>> Hi, I have a strange problem with QPopper4.0.9..occasionally I have with
>> same users the error message that the password for check mail is
>> incorrect and for to resolve this problem I must delete user/ mailbox (I
>> have use linux users) and the '/var/spool/mail/ myuser.pop' file.
>
> Qpopper is quite sensitive to permissions. You should check carefully
> the permissions on those files when it happens. Also, it might be
> helpful to run ktrace, strace etc. on qpopper when the problem is
> occuring. Then look to see which check is causing the error message.
>
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: Password incorrect
Date: Tue, 6 May 2008 10:17:39 -0700
Then run a ktrace or strace when the problem occurs and see what is
causing the message.
On May 6, 2008, at 07:30, Sasa wrote:
> Hi and thanks for you aid, now I haven't problem and permission are:
>
> -rw-rw---- 1 pippo.pluto mail 8890312 6 mag 13:00 pippo.pluto
> -rw------- 1 pippo.pluto mail 10 6 mag 13:00
> pippo.pluto.lock
>
> ..but why occassionaly I have a problem about incorrect password ?
> when the problem is present the
> password is incorrect because the permission are corrupted ? and
> because happen this ?
> Thanks.
>
> ------
>
> Salvatore.
>
>
> ----- Original Message ----- From: "Doug Hardie" <bc979@lafn.org>
> To: "Sasa" <sasa@shoponweb.it>
> Cc: "Subscribers of Qpopper" <qpopper@lists.pensive.org>
> Sent: Monday, May 05, 2008 8:48 PM
> Subject: Re: Password incorrect
>
>
>> On May 5, 2008, at 03:30, Sasa wrote:
>>
>>> Hi, I have a strange problem with QPopper4.0.9..occasionally I
>>> have with same users the error message that the password for
>>> check mail is incorrect and for to resolve this problem I must
>>> delete user/ mailbox (I have use linux users) and the '/var/spool/
>>> mail/ myuser.pop' file.
>>
>> Qpopper is quite sensitive to permissions. You should check
>> carefully the permissions on those files when it happens. Also, it
>> might be helpful to run ktrace, strace etc. on qpopper when the
>> problem is occuring. Then look to see which check is causing the
>> error message.
>
>
Date: Wed, 7 May 2008 19:21:21 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: configure / make error 4.0.12
The 'make install' error should be fixed in 4.0.13, please try and let me know.
Thanks.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
If you attack stupidity you attack an entrenched interest with friends
in government and every walk of public life, and you will make small
progress against it. --Samuel Marchbanks
Date: Wed, 7 May 2008 19:19:36 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.13 available
Qpopper 4.0.13 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Please let me know if you experience problems with this.
I'm especially interested in reports, good and bad, of PAM usage and
HPUX usage.
This should fix the problems with syntax errors on configuration
files that worked prior to 4.0.12, as well as errors with 'make
install'.
The full list of changes is on the FTP site, at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/Changes>.
Changes from 4.0.12 to 4.0.13:
-------------------------------
1. Back out change allowing 'announce-expire' configuration file
option to be set to -1.
2. Fix problems with 'make install'.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
A child of five would understand this. Send somebody to
fetch a child of five. --Groucho Marx, "Duck Soup"
From: "Giannis Mantzouranis" <jman at physics dot upatras dot gr>
Subject: Re: Problems compiling qpopper 4.0.12 with openssl
Date: Thu, 8 May 2008 05:34:36 +0300
Hi Randall
Thanks for the reply! I put a blank space after the tls and it worked! Now
for the patch in the makefile. I had noticed As I had moved from openssl
0.9.7x to 0.9.8x that it did not linked properly with the libraries. When I
typed make the linker failed with errors. This was due as some people
suggested in the openssl-users email list (as that time I did the transition
this list had problems with the posts) to the missing -ldl parameter in the
libraries section of the makefile in the popper directory. I added this
parameter _-ldl_ and the make worked fluently!
Thanks A lot for the replies All of you!
Giannis Mantzouranis
----- Original Message -----
From: "Randall Gellens" <randy@qualcomm.com>
To: "Giannis Mantzouranis" <jman@physics.upatras.gr>; "Subscribers of
Qpopper" <qpopper@lists.pensive.org>
Sent: ÄåõôÝñá, 5 ÌáÀïõ 2008 10:26 ìì
Subject: Re: Problems compiling qpopper 4.0.12 with openssl
> Hi Giannis,
>
> At 9:51 PM +0300 5/5/08, Giannis Mantzouranis wrote:
>
>> I had compiled qpopper 4.0.12 with openssl 0.8.9g patching the Makefile
>> in the popper directory with -ldl so that it compiles fluently with this
>> version of openssl.
>
> Why did you need to patch popper/Makefile? What did you use for
> ./configure?
>
>> The server works in plain sessions on port 110 but dies with the
>> following error message
>> Expected comment or end of line; found ""
>> at line 2 of config file /etc/mail/qpoppera.config
>> I must address that I kept the same configuration with qpopper 4.0.9
>> witch I used already. I would appreciate any comments or suggestions
>
> This looks to have been introduced in 4.0.12 as part of allowing
> "announce-expire" to be set to -1. This change will be backed out for
> 4.0.13 (with a better fix in 4.1b9). For now, try changing your
> /etc/mail/qpoppera.config file so that for TLS options that take file
> names, either put the file name in quotes, or just add a blank space after
> the file name.
>
> Please let me know if this fixes it for you, and also about why you needed
> to modify popper/Makefile.
>
> Thank you.
>
> --
> Randall Gellens
> Opinions are personal; facts are suspect; I speak for myself only
> -------------- Randomly-selected tag: ---------------
> The single biggest problem in communication is the illusion that it
> has taken place. --G. B. Shaw
>
Date: Thu, 08 May 2008 09:14:25 +0200
From: Martin Kellermann <kellermann at sk-datentechnik dot com>
Subject: Re: configure / make error 4.0.12
yep! "make install" is working as expected - no errors.
thank you!
regards
At 04:21 08.05.2008, you wrote:
>The 'make install' error should be fixed in 4.0.13, please try and
>let me know.
>
>Thanks.
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly-selected tag: ---------------
>If you attack stupidity you attack an entrenched interest with friends
>in government and every walk of public life, and you will make small
>progress against it. --Samuel Marchbanks
Date: Thu, 8 May 2008 08:21:19 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Problems compiling qpopper 4.0.12 with openssl
Hi Giannis,
At 5:34 AM +0300 5/8/08, Giannis Mantzouranis wrote:
> Thanks for the reply! I put a blank space after the tls and it worked!
That's just a work-around for a bug that was in 4.0.12, and only
4.0.12 -- there is no need for this extra space in 4.0.13. Feel free
to take those spaces out if you like, throw out 4.0.12, and use
4.0.13.
> Now for the patch in the makefile. I had noticed As I had moved
> from openssl 0.9.7x to 0.9.8x that it did not linked properly with
> the libraries. When I typed make the linker failed with errors.
> This was due as some people suggested in the openssl-users email
> list (as that time I did the transition this list had problems with
> the posts) to the missing -ldl parameter in the libraries section
> of the makefile in the popper directory. I added this parameter
> _-ldl_ and the make worked fluently!
This should have been added automatically y ./configure and I'd like
to know why it wasn't. Can you please try a 'make realclean' and
then re-run ./configure, capture the output to a file, and send me
the file?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
Perhaps the real reason why we have always been able to champion free
speech in this country is that we know perfectly well that hardly
anybody has got anything to say, and that no one will listen to anyone
that has. -- Editorial, Daily Mail [British Paper, date unknown]
From: "Ravindranath, Chavalam" <chavalam dot ravindranath at hp dot com>
Date: Mon, 12 May 2008 06:23:56 +0000
Subject: RE: Qpopper failure while using with pam option enabled
Hi Randell,
Think there is a problem in the hpux libpam itself I need to debu
g that and let you know the details.Qpopper.4.0.13 is working fine in 11.31
ia but not working in 11.23 ia(11.31 is next version of 11.23)
Thanks & Regards,
Ravindranath
-----Original Message-----
From: Randall Gellens [mailto:randy@qualcomm.com]
Sent: Saturday, May 03, 2008 6:01 AM
To: Ravindranath, Chavalam
Subject: RE: Qpopper failure while using with pam option enabled
Hi Ravindranath,
Can you send me your /etc/pam.d/pop3 file? Also, please send some of the o
ther files in there, such as sshd. How did you create the
/etc/pam.d/pop3 file?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: --------------- If Murphy's Law can g
o wrong, it will.
Last updated on 11 May 2008 by Pensive Mailing List Admin