The qpopper list archive ending on 26 Apr 2010
Topics covered in this issue include:
1. slow PAM auth under load
"Ken Hohhof" <ken at mixedsignal dot com>
Mon, 29 Sep 2008 09:50:12 -0500
2. Qpopper 4.1 64-bit on Solaris 10?
Randall Gellens <randy at qualcomm dot com>
Sun, 5 Oct 2008 16:26:53 -0700
3. Qpopper 4.0.15 and 4.1b13 available
Randall Gellens <randy at qualcomm dot com>
Tue, 21 Oct 2008 22:42:01 -0700
4. AUTH PLAIN possible with qpopper???
Andre Heine <andre at linux-experience dot de>
Tue, 9 Dec 2008 14:43:22 +0100
5. Re: AUTH PLAIN possible with qpopper???
Randall Gellens <randy at qualcomm dot com>
Thu, 11 Dec 2008 17:41:15 -0800
6. Re: AUTH PLAIN possible with qpopper???
Randall Gellens <randy at qualcomm dot com>
Thu, 11 Dec 2008 19:13:25 -0800
7. Re: AUTH PLAIN possible with qpopper???
Andre Heine <andre at linux-experience dot de>
Fri, 12 Dec 2008 14:20:09 +0100
8. Relaying POP3 traffic
"Radakovich, Michael" <MRadakovich at wideopenwest dot com>
Mon, 22 Dec 2008 11:38:13 -0600
9. Re: Relaying POP3 traffic
Stefan Schweizer <stefan dot schweizer at villabruna dot com>
Mon, 22 Dec 2008 19:52:41 +0100
10. Re: AUTH PLAIN possible with qpopper???
Randall Gellens <randy at qualcomm dot com>
Mon, 22 Dec 2008 23:23:14 -0800
11. Viewing user password in POP log
"Radakovich, Michael" <MRadakovich at wideopenwest dot com>
Wed, 7 Jan 2009 14:09:51 -0600
12. Re: Viewing user password in POP log
Ken Hornstein <kenh at cmf dot nrl dot navy dot mil>
Wed, 07 Jan 2009 15:13:05 -0500
13. Re: Viewing user password in POP log
Randall Gellens <randy at qualcomm dot com>
Fri, 9 Jan 2009 16:54:06 -0800
14. Qpopper 4.0.16 and 4.1b14 available
Randall Gellens <randy at qualcomm dot com>
Sat, 10 Jan 2009 00:20:24 -0800
15. problem with building 64-bit binary of qpopper 4.1b14 on solaris
Stoyan Angelov <s_angelov at filibeto dot org>
Sun, 8 Feb 2009 17:25:31 +0200
16. Re: problem with building 64-bit binary of qpopper 4.1b14 on
Randall Gellens <randy at qualcomm dot com>
Thu, 12 Feb 2009 16:13:02 -0800
17. Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Stoyan Angelov <s_angelov at filibeto dot org>
Mon, 16 Feb 2009 23:15:24 +0200
18. Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Doug Hardie <bc979 at lafn dot org>
Mon, 16 Feb 2009 13:58:50 -0800
19. Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Stoyan Angelov <s_angelov at filibeto dot org>
Tue, 17 Feb 2009 00:27:23 +0200
20. Qpopper 4.1b15 available
Randall Gellens <randy at qualcomm dot com>
Fri, 20 Feb 2009 11:04:49 -0800
21. Re: problem with building 64-bit binary of qpopper 4.1b14 on
Randall Gellens <randy at qualcomm dot com>
Fri, 20 Feb 2009 11:03:42 -0800
22. Password incorrect
"Sasa" <sasa at shoponweb dot it>
Tue, 24 Mar 2009 12:46:50 +0100
23. Re: Password incorrect
"Sasa" <sasa at shoponweb dot it>
Fri, 27 Mar 2009 13:55:14 +0100
24. Re: Password incorrect
"Jim Cameron" <qpopper09 at moonpoint dot com>
Sat, 28 Mar 2009 20:40:56 -0400
25. Re: Password incorrect
Randall Gellens <randy at qualcomm dot com>
Tue, 31 Mar 2009 15:43:42 -0700
26. Export User mailbox
"Sasa" <sasa at shoponweb dot it>
Fri, 12 Jun 2009 16:12:03 +0200
27. Re: Export User mailbox
Doug Hardie <bc979 at lafn dot org>
Sun, 14 Jun 2009 20:59:26 -0700
28. Qpopper 4.1b16 available
Randall Gellens <randy at qualcomm dot com>
Mon, 13 Jul 2009 16:43:20 -0700
29. Qpopper 4.0.17 available
Randall Gellens <randy at qualcomm dot com>
Mon, 13 Jul 2009 16:41:04 -0700
30. Re: Qpopper 4.1b16 available
The Doctor <doctor at doctor dot nl2k dot ab dot ca>
Tue, 14 Jul 2009 07:27:13 -0600
31. Qpopper 4.0.18 and 4.1b17 available
Randall Gellens <randy at qualcomm dot com>
Sun, 19 Jul 2009 13:43:34 -0700
32. Re: Qpopper 4.0.18 and 4.1b17 available
Mark <manager at monmouth dot com>
Wed, 22 Jul 2009 15:57:26 -0400
33. Re: Qpopper 4.0.18 and 4.1b17 available
Randall Gellens <randy at qualcomm dot com>
Thu, 23 Jul 2009 16:00:17 -0700
34. Re: Qpopper 4.0.18 and 4.1b17 available
Mark <manager at monmouth dot com>
Fri, 24 Jul 2009 08:16:09 -0400
35. Re: Qpopper 4.0.18 and 4.1b17 available
Randall Gellens <randy at qualcomm dot com>
Mon, 27 Jul 2009 10:29:30 -0700
36. Re: Qpopper 4.0.18 and 4.1b17 available
Mark <manager at monmouth dot com>
Wed, 29 Jul 2009 15:06:47 -0400
37. Re: Qpopper 4.0.18 and 4.1b17 available
Randall Gellens <randy at qualcomm dot com>
Sun, 2 Aug 2009 15:53:53 -0700
38. Compiling 4.0.18 under Fedora 11 - getline() conflict
Matt Garretson <mattg at assembly dot state dot ny dot us>
Sun, 13 Sep 2009 17:37:42 -0400
39. Re: Compiling 4.0.18 under Fedora 11 - getline() conflict
jnemeth at victoria dot tc dot ca (John Nemeth)
Thu, 24 Sep 2009 02:23:07 -0700
40. Qpopper 4.1b18 available
Randall Gellens <randy at qualcomm dot com>
Sat, 17 Oct 2009 16:50:58 -0700
41. Qpopper 4.0.18 available
Randall Gellens <randy at qualcomm dot com>
Sat, 17 Oct 2009 16:50:10 -0700
42. Qpopper 4.1 Status
Randall Gellens <randy at qualcomm dot com>
Mon, 19 Oct 2009 11:36:43 -0700
43. "ERR POP EOF or I/O Error" messages have begun appearing in the
Keith Christian <keith1christian at gmail dot com>
Sun, 20 Dec 2009 12:09:10 -0700
44. Re: "ERR POP EOF or I/O Error" messages have begun appearing
Randall Gellens <randy at qualcomm dot com>
Mon, 21 Dec 2009 18:47:33 -0800
45. Re: "ERR POP EOF or I/O Error" messages have begun appearing in the
Keith Christian <keith1christian at gmail dot com>
Wed, 23 Dec 2009 07:38:06 -0700
46. FrameMaker users?
Randall Gellens <randy at qualcomm dot com>
Thu, 7 Jan 2010 09:53:52 -0800
47. A few pop locks in /var/spool/mail not removed
Keith Christian <keith1christian at gmail dot com>
Mon, 8 Mar 2010 10:01:05 -0700
48. Re: A few pop locks in /var/spool/mail not removed
Randall Gellens <randy at qualcomm dot com>
Sun, 14 Mar 2010 19:31:08 -0700
49. test -- please ignore
Randall Gellens <randy at qualcomm dot com>
Thu, 22 Apr 2010 08:45:25 -0700
50. test -- please ignore
Randall Gellens <randy at qualcomm dot com>
Mon, 26 Apr 2010 11:13:33 -0700
From: "Ken Hohhof" <ken at mixedsignal dot com>
Subject: slow PAM auth under load
Date: Mon, 29 Sep 2008 09:50:12 -0500
I have a server that has been running qpopper and sendmail on RH8 for
several years. I am having a problem where qpopper logins can take 15-20
seconds to authorize at peak usage times. Yet I look at the server and
neither CPU nor memory are maxed out. Load average might be up to 4 or 5
when this occurs. Also, if I try to telnet or ssh to the server while this
is occuring, often I will see a quick prompt for username/password, but then
the same wait for auth to complete.
I believe the server is a 1.26GHz Xeon with 2GB memory and a RAID5 array of
3x18GB 10K SCSI drives.
This is almost certainly a PAM question not specifically a Qpopper question,
but I'm hoping someone can point me in the right direction. I don't see any
configuration that would limit PAM to a certain number of logins per second
or something like that, so I'm stumped why the auth process gets bogged down
when the server seems to be working hard but not by any means overloaded.
I have a newer server running the same configuration on dual 2.4GHz Xeons
with a SATA drive and I'm not seeing the same issue, but that may be due to
different users rather than different server.
Date: Sun, 5 Oct 2008 16:26:53 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1 64-bit on Solaris 10?
Has anyone had any problems with Qpopper 4.1 in 64-bit mode on Solaris 10?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
I always avoid prophesying beforehand, because it is a much better
policy to prophesy after the event has already taken place.
--Winston Churchill
Date: Tue, 21 Oct 2008 22:42:01 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.15 and 4.1b13 available
Qpopper 4.0.15 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Qpopper 4.1b13 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
Changes from 4.0.13 to 4.0.14:
-----------------------------
1. Update ./configure using newer autoconf to fix 64-bit mode
problems on some platforms.
Changes from 4.1.b12 to 4.1.b13:
-------------------------------
1. Update ./configure using newer autoconf to fix 64-bit mode
problems on some platforms.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
The challenge of computer science is: How NOT to make a mess of it.
-Edsger W. Dijkstra
From: Andre Heine <andre at linux-experience dot de>
Subject: AUTH PLAIN possible with qpopper???
Date: Tue, 9 Dec 2008 14:43:22 +0100
Hello all,
supports qpopper the "Auth Plain" command with
PAM together?
We have a special program, which needs the command...
In the documentation I found that only RFC 1939 and 2449
is supported.
The AUTH command is described in RFC 1734 as "optional"...
We use PAM, that's works fine. But in that case "AUTH"
returns the following message:
----- snip ----
ahe@se6:~/src> telnet post 110
Trying XXX.XXX.XXX.XXX...
Connected to post.
Escape character is '^]'.
+OK ready <16263.1228829430@post>
AUTH
+OK Supported SASL mechanisms:
X-NONE-SO-USE-APOP-OR-STLS
.
"Plain" is not in the list and the switch "-p2" don't take any effect;()
Any hints?
Best regards
Andre
--
You've been leading a dog's life. Stay off the furniture.
Date: Thu, 11 Dec 2008 17:41:15 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: AUTH PLAIN possible with qpopper???
At 2:43 PM +0100 12/9/08, Andre Heine wrote:
> Hello all,
>
> supports qpopper the "Auth Plain" command with
> PAM together?
>
> We have a special program, which needs the command...
>
> In the documentation I found that only RFC 1939 and 2449
> is supported.
>
> The AUTH command is described in RFC 1734 as "optional"...
>
> We use PAM, that's works fine. But in that case "AUTH"
> returns the following message:
>
> ----- snip ----
> ahe@se6:~/src> telnet post 110
> Trying XXX.XXX.XXX.XXX...
> Connected to post.
> Escape character is '^]'.
> +OK ready <16263.1228829430@post>
> AUTH
> +OK Supported SASL mechanisms:
> X-NONE-SO-USE-APOP-OR-STLS.
Did you compile Qpopper with a SASL library, such as the one from
Cyrus? E.g., use "--with-cyrus-sasl" with ./configure.
> "Plain" is not in the list and the switch "-p2" don't take any effect;()
No SASL mechanisms were in the list, which is what happens when you
compile without a SASL library.
The idea of SASL is that the library implements specific
authentication mechanisms, so the individual servers (such as
Qpopper) only need to call the general library functions. This
allows new mechanisms to be invented and supported in one place (the
SASL library).
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
It is only the superficial qualities that last. Man's deeper
nature is soon found out. --Oscar Wilde
Date: Thu, 11 Dec 2008 19:13:25 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: AUTH PLAIN possible with qpopper???
Also, use Qpopper 4.1.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
If God lived on Earth, people would knock out all His windows.
--Yiddish saying
From: Andre Heine <andre at linux-experience dot de>
Subject: Re: AUTH PLAIN possible with qpopper???
Date: Fri, 12 Dec 2008 14:20:09 +0100
Hello Randall,
Am Freitag, 12. Dezember 2008 02:41 schrieb Randall Gellens:
> At 2:43 PM +0100 12/9/08, Andre Heine wrote:
> > supports qpopper the "Auth Plain" command with
> > PAM together?
[...]
> > +OK Supported SASL mechanisms:
> > X-NONE-SO-USE-APOP-OR-STLS.
>
> Did you compile Qpopper with a SASL library, such as the one from
> Cyrus? E.g., use "--with-cyrus-sasl" with ./configure.
I don't know. It's the original suse 10.1 qpopper...
> No SASL mechanisms were in the list, which is what happens when you
> compile without a SASL library.
Ok, I will try the to compile my qpopper...
> The idea of SASL is that the library implements specific
> authentication mechanisms, so the individual servers (such as
> Qpopper) only need to call the general library functions. This
> allows new mechanisms to be invented and supported in one place (the
> SASL library).
Give me some time to test it:-)
Thanks for your supplie!!!
Greetings
Andre
--
There is no distinctly native American criminal class except Congress.
-- Mark Twain
Subject: Relaying POP3 traffic
Date: Mon, 22 Dec 2008 11:38:13 -0600
From: "Radakovich, Michael" <MRadakovich at wideopenwest dot com>
This is a multi-part message in MIME format.
------_=_NextPart_001_01C9645C.1165832E
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Is it possible to configure qpopper to relay all POP3
connections it receives to another host ( external ). I am running
v4.0.5 .
Any help would be greatly appreciated.
Thank you,
Michael Radakovich
Systems Administrator
WOW! Internet-Cable-Phone
(630)536-3163
------_=_NextPart_001_01C9645C.1165832E
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'> Is it
possible to
configure qpopper to relay all POP3 connections it receives to another
host (
external ). I am running v4.0.5 .<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'> Any help would
be
greatly appreciated.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'> Thank
you,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>Michael Radakovich<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>Systems Administrator<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>WOW! Internet-Cable-Phone<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>(630)536-3163 <o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'> </span><o:p></o:p></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C9645C.1165832E--
From: Stefan Schweizer <stefan dot schweizer at villabruna dot com>
Date: Mon, 22 Dec 2008 19:52:41 +0100
Subject: Re: Relaying POP3 traffic
--Apple-Mail-47-409175209
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
Hi Michael,
Isn't that a task for rinetd?
Kind regards,
Stefan
Am 22.12.2008 um 18:38 schrieb Radakovich, Michael:
>
> Is it possible to configure qpopper to relay all POP3
> connections it receives to another host ( external ). I am running
> v4.0.5 .
>
>
> Any help would be greatly appreciated.
>
>
> Thank you,
>
>
>
> Michael Radakovich
> Systems Administrator
> WOW! Internet-Cable-Phone
> (630)536-3163
>
>
--Apple-Mail-47-409175209
Content-Type: text/html;
charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "><div>Hi
Michael,</div><div><br></div>Isn't that a task for
rinetd?<div><br></div><div>Kind
regards,</div><div><br></div><div>Stefan<br><div><br></div><div><br><div><
div>Am 22.12.2008 um 18:38 schrieb Radakovich, Michael:</div><br
class="Apple-interchange-newline"><blockquote type="cite"><span
class="Apple-style-span" style="border-collapse: separate; color:
rgb(0, 0, 0); font-family: 'Helvetica Neue'; font-size: 12px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2; text-align:
auto; text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust:
auto; -webkit-text-stroke-width: 0; "><div lang="EN-US" link="blue"
vlink="purple"><div class="Section1"><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="2"
face="Arial"><span style="font-size: 10pt; font-family: Arial;
"><o:p> </o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="2"
face="Arial"><span style="font-size: 10pt; font-family: Arial;
"> Is it possible to configure
qpopper to relay all POP3 connections it receives to another host (
external ). I am running v4.0.5 .<o:p></o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "><o:p> </o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "><o:p> </o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "> Any
help would be greatly appreciated.<o:p></o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "><o:p> </o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "><o:p> </o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="2" face="Arial"><span style="font-size:
10pt; font-family: Arial; "> Thank
you,<o:p></o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="2"
face="Arial"><span style="font-size: 10pt; font-family: Arial;
"><o:p> </o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="2"
face="Arial"><span style="font-size: 10pt; font-family: Arial;
"><o:p> </o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="2"
face="Arial"><span style="font-size: 10pt; font-family: Arial;
"><o:p> </o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="3" face="Times
New Roman"><span style="font-size: 12pt; ">Michael
Radakovich<o:p></o:p></span></font></div><div style="margin-top: 0in;
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size:
12pt; font-family: 'Times New Roman'; "><font size="3" face="Times
New Roman"><span style="font-size: 12pt; ">Systems
Administrator<o:p></o:p></span></font></div><div style="margin-top:
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt;
font-size: 12pt; font-family: 'Times New Roman'; "><font size="3"
face="Times New Roman"><span style="font-size: 12pt; ">WOW!
Internet-Cable-Phone<o:p></o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="3" face="Times New Roman"><span
style="font-size: 12pt;
">(630)536-3163 <o:p></o:p></span></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="3" face="Times New Roman"><span
style="font-size: 12pt; "> </span><o:p></o:p></font></div><div
style="margin-top: 0in; margin-right: 0in; margin-left: 0in;
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New
Roman'; "><font size="3" face="Times New Roman"><span
style="font-size: 12pt;
"><o:p> </o:p></span></font></div></div></div></span></blockquote></d
iv><br></div></div></body></html>
--Apple-Mail-47-409175209--
Date: Mon, 22 Dec 2008 23:23:14 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: AUTH PLAIN possible with qpopper???
At 2:20 PM +0100 12/12/08, Andre Heine wrote:
> > Did you compile Qpopper with a SASL library, such as the one from
>> Cyrus? E.g., use "--with-cyrus-sasl" with ./configure.
>
> I don't know. It's the original suse 10.1 qpopper...
Does that include a SASL library? If not, you can it from cmu.edu.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
It wasn't as easy to get programs right as we had thought.
--Wilkes, 1949
Subject: Viewing user password in POP log
Date: Wed, 7 Jan 2009 14:09:51 -0600
From: "Radakovich, Michael" <MRadakovich at wideopenwest dot com>
This is a multi-part message in MIME format.
------_=_NextPart_001_01C97103.E5A950E4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello,
I am using Qopper v4.0.5 and am using Openldap for
user authentication. Is there a way to recompile qpopper or add a line
in the config. file so I can see the user
password in the popper log files ?
Any help would be greatly appreciated.
Thank you,
Michael Radakovich
Systems Administrator
WOW! Internet-Cable-Phone
(630)536-3163
------_=_NextPart_001_01C97103.E5A950E4
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'>
Hello,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'>
I am using Qopper v4.0.5 and am using Openldap for user authentication.
Is
there a way to recompile qpopper or add a line in the config. file so I
can see
the user<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'>
password in the popper log files ?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'>
Any help would be greatly appreciated.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'>
Thank you,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>Michael Radakovich<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>Systems Administrator<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>WOW! Internet-Cable-Phone<o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'>(630)536-3163 <o:p></o:p></span></font></p>
<p class=MsoAutoSig><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'> </span><o:p></o:p></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C97103.E5A950E4--
Subject: Re: Viewing user password in POP log
Date: Wed, 07 Jan 2009 15:13:05 -0500
From: Ken Hornstein <kenh at cmf dot nrl dot navy dot mil>
> I am using Qopper v4.0.5 and am using Openldap for
>user authentication. Is there a way to recompile qpopper or add a line
>in the config. file so I can see the user password in the popper log files ?
Note to self: time to switch ISPs.
--Ken
Date: Fri, 9 Jan 2009 16:54:06 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Viewing user password in POP log
At 2:09 PM -0600 1/7/09, Michael Radakovich wrote:
>
>
> Hello,
> I am using Qopper v4.0.5 and am using Openldap
> for user authentication. Is there a way to recompile qpopper or add
> a line in the config. file so I can see the user
> password in the popper log files ?
>
>
> Any help would be greatly appreciated.
>
>
> Thank you,
Qpopper is careful to log a fixed string instead of the actual
password. Naturally, as an open-source project, you can comment out
or modify the line in the source and recompile, but logging passwords
is not something that is recommended.
If you want to muck with the source, look for the comment:
/*
* Do not log cleartext passwords
*/
But I'd caution against logging passwords. If you have an unusual
circumstance where you feel this is needed, you might consider
running the patched Qpopper on a different port.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
Democracy is a form of government that substitutes election by the
incompetent many for appointment by the corrupt few.
--G. B. Shaw
Date: Sat, 10 Jan 2009 00:20:24 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.16 and 4.1b14 available
Qpopper 4.0.16 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Qpopper 4.1b14 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
There is one patch in each:
Patch from Jason White to fix error when using Kerberos.
Also, I think 4.1 is ready to exit beta -- what do others think?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
I hold that the very purpose of existence is to reconcile the
glowing opinion we have of ourselves with the terrible things
that other people say about us. --Quentin Crisp
From: Stoyan Angelov <s_angelov at filibeto dot org>
Subject: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Date: Sun, 8 Feb 2009 17:25:31 +0200
hello all,
i am having problems building qpopper 4.1b14 in 64-bit mode on
solaris. the os is SXCE build 105 (x64) and Sun's Studio 12 compiler
is used (Sun C 5.9 SunOS_i386 Patch 124868-07 2008/10/07).
configure's "--enable-64-bit" option is set and i can see a line in
the output saying "Building 64-bit binary", however later on during
make i get the following error:
cc pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o
pop_init.o pop_last.o pop_list.o pop_log.o pop_lower.o pop_msg.o
pop_parse.o pop_pass.o pop_quit.o pop_rset.o pop_send.o pop_stat.o
pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o popper.o pop_bull.o
xtnd_xlst.o pop_uidl.o pop_rpop.o pop_apop.o pop_auth.o pop_pope.o
pop_extend.o scram.o hmac.o pop_util.o get_sub_opt.o msg_ptr.o drac.o
pop_config.o pop_tls.o pop_tls_openssl.o pop_tls_sslplus.o
sslplus_utils.o main.o pop_cache.o genpath.o pop_sasl.o md5.o
base64.o -o popper \
../mmangle/libmangle.a \
-I../common ../common/libcommon.a \
-lnsl -lsocket -lresolv -lmail -lnsl -lposix4 -lcrypt -L/
usr/lib -lssl -lcrypto -m64
ld: fatal: file pop_dele.o: wrong ELF class: ELFCLASS32
ld: fatal: file processing errors. No output written to popper
*** Error code 1
make: Fatal error: Command failed for target `popper'
Current working directory /root/sources/qpopper4.1b14/popper
*** Error code 1
make: Fatal error: Command failed for target `popper_server'
all other object files in the popper directory a 32-bit too:
base64.o: ELF 32-bit LSB relocatable 80386 Version 1
drac.o: ELF 32-bit LSB relocatable 80386 Version 1
genpath.o: ELF 32-bit LSB relocatable 80386 Version 1
<snip>
any help will be appreciated,
greetings,
Stoyan Angelov
Date: Thu, 12 Feb 2009 16:13:02 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: problem with building 64-bit binary of qpopper 4.1b14 on
At 5:25 PM +0200 2/8/09, Stoyan Angelov wrote:
> hello all,
>
> i am having problems building qpopper 4.1b14 in 64-bit mode on
> solaris. the os is SXCE build 105 (x64) and Sun's Studio 12
> compiler is used (Sun C 5.9 SunOS_i386 Patch 124868-07 2008/10/07).
Hi,
Have you tried using gcc instead of Sun's C compiler? It should work
either way, of course, but I'm trying to isolate the source of the
problem. It would help to know if the problem only happens with some
compilers.
> configure's "--enable-64-bit" option is set and i can see a line in
> the output saying "Building 64-bit binary", however later on during
> make i get the following error:
>
> cc pop_dele.o pop_dropcopy.o pop_get_command.o
> pop_get_subcommand.o pop_init.o pop_last.o pop_list.o pop_log.o
> pop_lower.o pop_msg.o pop_parse.o pop_pass.o pop_quit.o
> pop_rset.o pop_send.o pop_stat.o pop_updt.o pop_user.o pop_xtnd.o
> pop_xmit.o popper.o pop_bull.o xtnd_xlst.o pop_uidl.o pop_rpop.o
> pop_apop.o pop_auth.o pop_pope.o
> pop_extend.o scram.o hmac.o pop_util.o get_sub_opt.o msg_ptr.o
> drac.o pop_config.o pop_tls.o pop_tls_openssl.o pop_tls_sslplus.o
> sslplus_utils.o main.o pop_cache.o genpath.o pop_sasl.o md5.o
> base64.o -o popper \
> ../mmangle/libmangle.a \
> -I../common ../common/libcommon.a \
> -lnsl -lsocket -lresolv -lmail -lnsl -lposix4 -lcrypt
> -L/usr/lib -lssl -lcrypto -m64
> ld: fatal: file pop_dele.o: wrong ELF class: ELFCLASS32
> ld: fatal: file processing errors. No output written to popper
> *** Error code 1
> make: Fatal error: Command failed for target `popper'
> Current working directory /root/sources/qpopper4.1b14/popper
> *** Error code 1
> make: Fatal error: Command failed for target `popper_server'
>
> all other object files in the popper directory a 32-bit too:
> base64.o: ELF 32-bit LSB relocatable 80386 Version 1
> drac.o: ELF 32-bit LSB relocatable 80386 Version 1
> genpath.o: ELF 32-bit LSB relocatable 80386 Version 1
> <snip>
>
> any help will be appreciated,
>
>
> greetings,
>
> Stoyan Angelov
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
I suppose when it gets to that point, we shan't know how it does it.
--Alan Turing
From: Stoyan Angelov <s_angelov at filibeto dot org>
Subject: Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Date: Mon, 16 Feb 2009 23:15:24 +0200
On Feb 13, 2009, at 2:13 AM, Randall Gellens wrote:
> At 5:25 PM +0200 2/8/09, Stoyan Angelov wrote:
>> hello all,
>>
>> i am having problems building qpopper 4.1b14 in 64-bit mode on
>> solaris. the os is SXCE build 105 (x64) and Sun's Studio 12
>> compiler is used (Sun C 5.9 SunOS_i386 Patch 124868-07 2008/10/07).
>
> Hi,
>
> Have you tried using gcc instead of Sun's C compiler? It should
> work either way, of course, but I'm trying to isolate the source of
> the problem. It would help to know if the problem only happens with
> some compilers.
hi Randall,
i tried compiling with the bundled gcc - gcc version 3.4.3 (csl-
sol210-3_4-20050802) but i get a similar error:
ar -r libcommon.a flock.o maillock.o logit.o snprintf.o string_util.o
check_group.o utils.o
ar: creating libcommon.a
gmake[2]: Leaving directory `/root/sources/qpopper4.1b14/common'
gcc pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o
pop_init.o pop_last.o pop_list.o pop_log.o pop_lower.o pop_msg.o
pop_parse.o pop_pass.o pop_quit.o pop_rset.o pop_send.o pop_stat.o
pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o popper.o pop_bull.o
xtnd_xlst.o pop_uidl.o pop_rpop.o pop_apop.o pop_auth.o pop_pope.o
pop_extend.o scram.o hmac.o pop_util.o get_sub_opt.o msg_ptr.o drac.o
pop_config.o pop_tls.o pop_tls_openssl.o pop_tls_sslplus.o
sslplus_utils.o main.o pop_cache.o genpath.o pop_sasl.o md5.o base64.o
-o popper \
../mmangle/libmangle.a \
-I../common ../common/libcommon.a \
-lnsl -lsocket -lresolv -lmail -lnsl -lposix4 -
lcrypt -L/usr/lib -lssl -lcrypto -m64
ld: fatal: file pop_dele.o: wrong ELF class: ELFCLASS32
ld: fatal: file processing errors. No output written to popper
collect2: ld returned 1 exit status
gmake[1]: *** [popper] Error 1
gmake[1]: Leaving directory `/root/sources/qpopper4.1b14/popper'
gmake: *** [popper_server] Error 2
greetings,
Stoyan
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Date: Mon, 16 Feb 2009 13:58:50 -0800
Note that I have never used a 64 bit machine, but when I read the
error below it appears to me that the error is saying that pop_dele.o
was compiled as 32 bit and not 64 bit. Could it be a leftover that
never got recompiled?
On Feb 16, 2009, at 13:15, Stoyan Angelov wrote:
> On Feb 13, 2009, at 2:13 AM, Randall Gellens wrote:
>> At 5:25 PM +0200 2/8/09, Stoyan Angelov wrote:
>>> hello all,
>>>
>>> i am having problems building qpopper 4.1b14 in 64-bit mode on
>>> solaris. the os is SXCE build 105 (x64) and Sun's Studio 12
>>> compiler is used (Sun C 5.9 SunOS_i386 Patch 124868-07 2008/10/07).
>>
>> Hi,
>>
>> Have you tried using gcc instead of Sun's C compiler? It should
>> work either way, of course, but I'm trying to isolate the source of
>> the problem. It would help to know if the problem only happens
>> with some compilers.
>
> hi Randall,
>
> i tried compiling with the bundled gcc - gcc version 3.4.3 (csl-
> sol210-3_4-20050802) but i get a similar error:
>
> ar -r libcommon.a flock.o maillock.o logit.o snprintf.o
> string_util.o check_group.o utils.o
> ar: creating libcommon.a
> gmake[2]: Leaving directory `/root/sources/qpopper4.1b14/common'
> gcc pop_dele.o pop_dropcopy.o pop_get_command.o
> pop_get_subcommand.o pop_init.o pop_last.o pop_list.o pop_log.o
> pop_lower.o pop_msg.o pop_parse.o pop_pass.o pop_quit.o pop_rset.o
> pop_send.o pop_stat.o pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o
> popper.o pop_bull.o xtnd_xlst.o pop_uidl.o pop_rpop.o pop_apop.o
> pop_auth.o pop_pope.o pop_extend.o scram.o hmac.o pop_util.o
> get_sub_opt.o msg_ptr.o drac.o pop_config.o pop_tls.o
> pop_tls_openssl.o pop_tls_sslplus.o sslplus_utils.o main.o
> pop_cache.o genpath.o pop_sasl.o md5.o base64.o -o popper \
> ../mmangle/libmangle.a \
> -I../common ../common/libcommon.a \
> -lnsl -lsocket -lresolv -lmail -lnsl -lposix4 -
> lcrypt -L/usr/lib -lssl -lcrypto -m64
> ld: fatal: file pop_dele.o: wrong ELF class: ELFCLASS32
> ld: fatal: file processing errors. No output written to popper
> collect2: ld returned 1 exit status
> gmake[1]: *** [popper] Error 1
> gmake[1]: Leaving directory `/root/sources/qpopper4.1b14/popper'
> gmake: *** [popper_server] Error 2
>
>
> greetings,
>
> Stoyan
>
>
>
From: Stoyan Angelov <s_angelov at filibeto dot org>
Subject: Re: problem with building 64-bit binary of qpopper 4.1b14 on solaris
Date: Tue, 17 Feb 2009 00:27:23 +0200
On Feb 16, 2009, at 11:58 PM, Doug Hardie wrote:
> Note that I have never used a 64 bit machine, but when I read the
> error below it appears to me that the error is saying that
> pop_dele.o was compiled as 32 bit and not 64 bit. Could it be a
> leftover that never got recompiled?
hi Doug,
no, this is a new compilation and the object files were newly created.
all of them are 32-bit... that seems to be the problem.
> On Feb 8, 2009, at 5:25 PM, Stoyan Angelov wrote:
> all other object files in the popper directory a 32-bit too:
> base64.o: ELF 32-bit LSB relocatable 80386 Version 1
> drac.o: ELF 32-bit LSB relocatable 80386 Version 1
> genpath.o: ELF 32-bit LSB relocatable 80386 Version 1
> <snip>
greetings,
Stoyan
Date: Fri, 20 Feb 2009 11:04:49 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1b15 available
Qpopper 4.1b15 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
This fixes a bug compiling in 64-bit mode.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
I find that a great part of the information I have was acquired by
looking up something and finding something else on the way.
--Franklin P. Adams (1881-1960)
Date: Fri, 20 Feb 2009 11:03:42 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: problem with building 64-bit binary of qpopper 4.1b14 on
There was a stupid bug, sorry about that. Please try using 4.1b15.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
Happiness comes through doors you didn't even know you left open.
From: "Sasa" <sasa at shoponweb dot it>
Subject: Password incorrect
Date: Tue, 24 Mar 2009 12:46:50 +0100
Hi, I have a strange problem with QPopper 4.0.16 on Fedora Core 10.
I have installed QPopper with this option:
./configure --enable-standalone --without-pam
I have created users called 'test' but when I try to check mail I have
always in log file:
Mar 24 12:27:27 localhost popper[6488]: test at 192.168.1.15
(192.168.1.15): -ERR [AUTH] Password supplied for "test" is incorrect.
Mar 24 12:27:27 localhost popper[6488]: [AUTH] Failed attempted login to
test from host (192.168.1.15) 192.168.1.15
..but the password is certainly correct (for example with openwebmail I
haven't problem) !
Thanks in advance.
------
Salvatore.
From: "Sasa" <sasa at shoponweb dot it>
Subject: Re: Password incorrect
Date: Fri, 27 Mar 2009 13:55:14 +0100
Hi, someone has had a situation like this?
Thanks in advance.
------
Salvatore.
----- Original Message -----
From: "Sasa" <sasa@shoponweb.it>
To: "Subscribers of Qpopper" <qpopper@lists.pensive.org>
Sent: Tuesday, March 24, 2009 12:46 PM
Subject: Password incorrect
> Hi, I have a strange problem with QPopper 4.0.16 on Fedora Core 10.
> I have installed QPopper with this option:
>
> ./configure --enable-standalone --without-pam
>
> I have created users called 'test' but when I try to check mail I have
> always in log file:
>
> Mar 24 12:27:27 localhost popper[6488]: test at 192.168.1.15
> (192.168.1.15): -ERR [AUTH] Password supplied for "test" is incorrect.
> Mar 24 12:27:27 localhost popper[6488]: [AUTH] Failed attempted login to
> test from host (192.168.1.15) 192.168.1.15
>
> ..but the password is certainly correct (for example with openwebmail I
> haven't problem) !
> Thanks in advance.
>
> ------
>
> Salvatore.
>
>
From: "Jim Cameron" <qpopper09 at moonpoint dot com>
Subject: Re: Password incorrect
Date: Sat, 28 Mar 2009 20:40:56 -0400
I had the same problem with QPopper 4.0.16 on a Solaris system. I was able to remedy the problem using ./configure --enable-specialauth, which enables secure crypt or shadow passwords. Solaris uses shadow passwords, which I believe Fedora also uses by def
ault.
If you aren't familiar with shadow passwords, I would recommend the Wikipedia article on shadow passwords at http://en.wikipedia.org/wiki/Shadow_passwords
Jim
On Friday, March 27, 2009 9:05:14 AM, "Sasa" <sasa@shoponweb.it> wrote:
> Hi, someone has had a situation like this?
> Thanks in advance.
>
> ------
>
> Salvatore.
>
>
> ----- Original Message -----
> From: "Sasa" <sasa@shoponweb.it>
> To: "Subscribers of Qpopper" <qpopper@lists.pensive.org>
> Sent: Tuesday, March 24, 2009 12:46 PM
> Subject: Password incorrect
>
>
> > Hi, I have a strange problem with QPopper 4.0.16 on Fedora Core 10.
> > I have installed QPopper with this option:
> >
> > ./configure --enable-standalone --without-pam
> >
> > I have created users called 'test' but when I try to check mail I have
> > always in log file:
> >
> > Mar 24 12:27:27 localhost popper[6488]: test at 192.168.1.15
> > (192.168.1.15): -ERR [AUTH] Password supplied for "test" is incorrect.
> > Mar 24 12:27:27 localhost popper[6488]: [AUTH] Failed attempted login to
> > test from host (192.168.1.15) 192.168.1.15
> >
> > ..but the password is certainly correct (for example with openwebmail I
> > haven't problem) !
> > Thanks in advance.
> >
> > ------
> >
> > Salvatore.
> >
> >
Date: Tue, 31 Mar 2009 15:43:42 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Password incorrect
At 12:46 PM +0100 3/24/09, Sasa wrote:
> Hi, I have a strange problem with QPopper 4.0.16 on Fedora Core 10.
> I have installed QPopper with this option:
>
> ./configure --enable-standalone --without-pam
>
> I have created users called 'test' but when I try to check mail I
> have always in log file:
>
> Mar 24 12:27:27 localhost popper[6488]: test at 192.168.1.15
> (192.168.1.15): -ERR [AUTH] Password supplied for "test" is
> incorrect.
> Mar 24 12:27:27 localhost popper[6488]: [AUTH] Failed attempted
> login to test from host (192.168.1.15) 192.168.1.15
To get more detail, please enable tracing and repeat the steps.
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'.
At 8:40 PM -0400 3/28/09, Jim Cameron wrote:
> I had the same problem with QPopper 4.0.16 on a Solaris system. I
> was able to remedy the problem using ./configure
> --enable-specialauth, which enables secure crypt or shadow
> passwords. Solaris uses shadow passwords, which I believe Fedora
> also uses by def
> ault.
./configure tries to figure out on its own if --enable-specialauth is
needed. It may have guessed wrong in your case. To help fix this,
please do a 'make realclean' and re-reun ./configure with the same
parameters you used before, capture the output, and send it to me.
Also, please send the config.log and config.h files.
Thank you.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
Television has proved that people will look at anything rather than at
each other.
--Ann Landers
From: "Sasa" <sasa at shoponweb dot it>
Subject: Export User mailbox
Date: Fri, 12 Jun 2009 16:12:03 +0200
Hi, I use qpopper-4.0.9 with postfix/maia/amavis...is possible to export
(and then import on another pop3 server with the same qpopper version) the
user mailbox stored in /var/spool/mail/user1, /var/spool/mail/user2.... ?
Thanks.
------
Salvatore.
From: Doug Hardie <bc979 at lafn dot org>
Subject: Re: Export User mailbox
Date: Sun, 14 Jun 2009 20:59:26 -0700
On 12 June 2009, at 07:12, Sasa wrote:
> Hi, I use qpopper-4.0.9 with postfix/maia/amavis...is possible to
> export (and then import on another pop3 server with the same qpopper
> version) the user mailbox stored in /var/spool/mail/user1, /var/
> spool/mail/user2.... ?
Certainly. If the mailbox is not being used by a POP3 session, then
all you have to do is copy the file to the new server. If you use
bulletins you would want to copy the bulletin file also (presuming the
same bulletins are on both servers).
Date: Mon, 13 Jul 2009 16:43:20 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1b16 available
Qpopper 4.1b16 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.b15 to 4.1.b16:
--------------------------------
1. Replace some sprintf() calls with Qsnprintf().
2. Use PATH_MAX instead of hard-coded value for some buffers.
3. Add error check for impossible condition in get_sub_opt to
satisfy some automated code checkers.
4. Stop using sys_nerr and sys_errlist.
5. Fix syntax error with 64-bit mode on Solaris.
Changes from 4.1.b14 to 4.1.b15:
-------------------------------
1. Fix 64-bit compilation.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
The fewer episodes of a TV show one has seen, the greater the chance
that one has already viewed the episode one is watching.
--Randall Gellens
Date: Mon, 13 Jul 2009 16:41:04 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.17 available
Qpopper 4.0.17 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
The full list of changes is in the distribution.
Changes from 4.0.16 to 4.0.17:
-----------------------------
1. Replace some sprintf() calls with Qsnprintf().
2. Use PATH_MAX instead of hard-coded value for some buffers.
3. Add error check for impossible condition in get_sub_opt to
satisfy some automated code checkers.
4. Stop using sys_nerr and sys_errlist.
5. Fix syntax error with 64-bit mode on Solaris.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
In the beginning was the word...and it was the wrong length.
--Bob Barton (Burroughs computer architect)
Date: Tue, 14 Jul 2009 07:27:13 -0600
From: The Doctor <doctor at doctor dot nl2k dot ab dot ca>
Subject: Re: Qpopper 4.1b16 available
On Mon, Jul 13, 2009 at 04:43:20PM -0700, Randall Gellens wrote:
> Qpopper 4.1b16 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.b15 to 4.1.b16:
> --------------------------------
>
> 1. Replace some sprintf() calls with Qsnprintf().
> 2. Use PATH_MAX instead of hard-coded value for some buffers.
> 3. Add error check for impossible condition in get_sub_opt to
> satisfy some automated code checkers.
> 4. Stop using sys_nerr and sys_errlist.
> 5. Fix syntax error with 64-bit mode on Solaris.
>
>
> Changes from 4.1.b14 to 4.1.b15:
> -------------------------------
> 1. Fix 64-bit compilation.
>
>
Compile for BSD/OS 4.3.1 and it hung and went back to b15
and everything is to normal.
Please fix.
> --
> Randall Gellens
> Opinions are personal; facts are suspect; I speak for myself only
> -------------- Randomly selected tag: ---------------
> The fewer episodes of a TV show one has seen, the greater the chance
> that one has already viewed the episode one is watching.
> --Randall Gellens
--
Member - Liberal International This is doctor@nl2k.ab.ca
Ici doctor@nl2k.ab.ca God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
The fool says in his heart, "There is no God". They are corrupt, and their ways are vile; there is no one who does good. - Ps 53:1
Date: Sun, 19 Jul 2009 13:43:34 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.18 and 4.1b17 available
Qpopper 4.0.18 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
Qpopper 4.1b17 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
The full list of changes is in the distribution.
The 4.1b17 release fixes a number of 'make install' problems,
including failures to properly create a PAM authorization file,
initialize the popauth database for APOP, and consistently create
missing subdirectories. The 4.0.18 releases fixes most of these as
well, but still has issues creating missing subdirectories in some
cases.
At this point, 4.1 should be pretty much good to go -- please try it
and let me know if you find any issues.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
As soon as we started programming, we found to our surprise that it
wasn't as easy to get programs right as we had thought. Debugging had
to be discovered. I can remember the exact instant when I realized
that a large part of my life from then on was going to be spent in
finding mistakes in my own programs.
--Maurice Wilkes discovers debugging, 1949 (courtesy of Paul Robinson)
Date: Wed, 22 Jul 2009 15:57:26 -0400
From: Mark <manager at monmouth dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
--=====================_17731838==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
Does 4.1x write X-UID differently then 4.0x?
At 04:43 PM 7/19/2009, Randall Gellens wrote:
>Qpopper 4.0.18 is available at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
>Qpopper 4.1b17 is available at
><ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>.
>
>
>The full list of changes is in the distribution.
>
>The 4.1b17 release fixes a number of 'make install' problems,
>including failures to properly create a PAM authorization file,
>initialize the popauth database for APOP, and consistently create
>missing subdirectories. The 4.0.18 releases fixes most of these as
>well, but still has issues creating missing subdirectories in some cases.
>
>At this point, 4.1 should be pretty much good to go -- please try it
>and let me know if you find any issues.
>
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly-selected tag: ---------------
>As soon as we started programming, we found to our surprise that it
>wasn't as easy to get programs right as we had thought. Debugging had
>to be discovered. I can remember the exact instant when I realized
>that a large part of my life from then on was going to be spent in
>finding mistakes in my own programs.
>--Maurice Wilkes discovers debugging, 1949 (courtesy of Paul Robinson)
--=====================_17731838==.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<body>
<font size=3>Does 4.1x write X-UID differently then 4.0x?<br><br>
At 04:43 PM 7/19/2009, Randall Gellens wrote:<br>
<br>
<blockquote type=cite class=cite cite="">Qpopper 4.0.18 is available at
<<a href="ftp://ftp.qualcomm.com/eudora/servers/unix/popper/" eudora="autourl">
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/</a>>.<br>
Qpopper 4.1b17 is available at
<<a href="ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/" eudora="autourl">
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/</a>>.<br><br>
<br>
The full list of changes is in the distribution.<br><br>
The 4.1b17 release fixes a number of 'make install' problems, including
failures to properly create a PAM authorization file, initialize the
popauth database for APOP, and consistently create missing
subdirectories. The 4.0.18 releases fixes most of these as well,
but still has issues creating missing subdirectories in some
cases.<br><br>
At this point, 4.1 should be pretty much good to go -- please try it and
let me know if you find any issues.<br><br>
-- <br>
Randall Gellens<br>
Opinions are personal; facts are
suspect; I speak for myself only<br>
-------------- Randomly-selected tag: ---------------<br>
As soon as we started programming, we found to our surprise that it<br>
wasn't as easy to get programs right as we had thought. Debugging
had<br>
to be discovered. I can remember the exact instant when I
realized<br>
that a large part of my life from then on was going to be spent in<br>
finding mistakes in my own programs.<br>
--Maurice Wilkes discovers debugging, 1949 (courtesy of Paul
Robinson)<br>
</font></blockquote></body>
</html>
--=====================_17731838==.ALT--
Date: Thu, 23 Jul 2009 16:00:17 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
At 3:57 PM -0400 7/22/09, Mark wrote:
> Does 4.1x write X-UID differently then 4.0x?
No, but there are several options which control if and how X-UID is handled.
Are you seeing a problem with X-UIDL?
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
You have the right to remain silent. Anything you say will be
misquoted, then used against you.
Date: Fri, 24 Jul 2009 08:16:09 -0400
From: Mark <manager at monmouth dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
--=====================_162862344==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
I installed the 4.1b17 and the problems between IMAP and qpopper were
magnified by a factor of 5. Using the 4.0xx series of qpopper I would
have an issue once in awhile and easily fix the From lines being
broken. After getting a rash of support calls and my support staff
having a mini melt down, I restored the 4.014 qpopper I was running
and everything went back to normal. Editing mail spools to fix the
broken From lines I noticed two X-UID lines in the header which I did
not see before.
For example:
normal everyday X-UIDL line
X-UIDL: c@+"!-$`"!^gF"!^3f"!
and
X-UID:3
I assumed 4.b17 put the X-UID:3 in there and it was conflicting with
the old type of X-UIDL line because even fixing the From lines people
still could not pop those spools until I removed BOTH X-UID lines
Any ideas?
Thanks
Mark
At 07:00 PM 7/23/2009, Randall Gellens wrote:
>At 3:57 PM -0400 7/22/09, Mark wrote:
>
>> Does 4.1x write X-UID differently then 4.0x?
>
>No, but there are several options which control if and how X-UID is handled.
>
>Are you seeing a problem with X-UIDL?
>
>--
>Randall Gellens
>Opinions are personal; facts are suspect; I speak for myself only
>-------------- Randomly selected tag: ---------------
>You have the right to remain silent. Anything you say will be
>misquoted, then used against you.
--=====================_162862344==.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<body>
<font size=3>I installed the 4.1b17 and the problems between IMAP and
qpopper were magnified by a factor of 5. Using the 4.0xx series of
qpopper I would have an issue once in awhile and easily fix the From
lines being broken. After getting a rash of support calls and my support
staff having a mini melt down, I restored the 4.014 qpopper I was running
and everything went back to normal. Editing mail spools to fix the broken
From lines I noticed two X-UID lines in the header which I did not see
before.<br><br>
<br>
For example:<br><br>
normal everyday X-UIDL line<br>
X-UIDL: c@+"!-$`"!^gF"!^3f"!<br><br>
and<br><br>
X-UID:3<br><br>
<br>
I assumed 4.b17 put the X-UID:3 in there and it was conflicting with the
old type of X-UIDL line because even fixing the From lines people still
could not pop those spools until I removed BOTH X-UID lines<br><br>
<br>
Any ideas?<br><br>
Thanks<br><br>
Mark<br><br>
At 07:00 PM 7/23/2009, Randall Gellens wrote:<br>
<br>
<blockquote type=cite class=cite cite="">At 3:57 PM -0400 7/22/09, Mark
wrote:<br><br>
<blockquote type=cite class=cite cite=""> Does 4.1x write X-UID
differently then 4.0x?</blockquote><br>
No, but there are several options which control if and how X-UID is
handled.<br><br>
Are you seeing a problem with X-UIDL?<br><br>
-- <br>
Randall Gellens<br>
Opinions are personal; facts are
suspect; I speak for myself only<br>
-------------- Randomly selected tag: ---------------<br>
You have the right to remain silent. Anything you say will be<br>
misquoted, then used against you.<br>
</font></blockquote></body>
</html>
--=====================_162862344==.ALT--
Date: Mon, 27 Jul 2009 10:29:30 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
At 8:16 AM -0400 7/24/09, Mark wrote:
> I installed the 4.1b17 and the problems between IMAP and qpopper
> were magnified by a factor of 5. Using the 4.0xx series of qpopper
> I would have an issue once in awhile and easily fix the From lines
> being broken. After getting a rash of support calls and my support
> staff having a mini melt down, I restored the 4.014 qpopper I was
> running and everything went back to normal. Editing mail spools to
> fix the broken From lines I noticed two X-UID lines in the header
> which I did not see before.
>
>
> For example:
>
> normal everyday X-UIDL line
> X-UIDL: c@+"!-$`"!^gF"!^3f"!
>
> and
>
> X-UID:3
>
>
> I assumed 4.b17 put the X-UID:3 in there and it was conflicting
> with the old type of X-UIDL line because even fixing the From lines
> people still could not pop those spools until I removed BOTH X-UID
> lines
>
>
> Any ideas?
>
> Thanks
>
> Mark
Hi Mark,
Qpopper doesn't write "X-UID" lines. Maybe the IMAP server is doing
this? Even so, I'm not sure why there would be a difference between
4.0 and 4.1.
When you say users couldn't pop their mail until you deleted the
X--UID and X-UIDL lines, what was happening?
Would it be possible for you to reproduce the problem with Qpopper tracing?
To enable tracing in Qpopper in standalone mode:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
4. Add '-t <tracefile-path>' to the command line for Qpopper.
This causes detailed tracing to be written to the file specified as
'tracefile-path'.
>
> At 07:00 PM 7/23/2009, Randall Gellens wrote:
>
>
>> At 3:57 PM -0400 7/22/09, Mark wrote:
>>
>>> Does 4.1x write X-UID differently then 4.0x?
>>>
>>
>> No, but there are several options which control if and how X-UID is handled.
>>
>> Are you seeing a problem with X-UIDL?
>>
>> --
>> Randall Gellens
>> Opinions are personal; facts are suspect; I speak for myself only
>> -------------- Randomly selected tag: ---------------
>> You have the right to remain silent. Anything you say will be
>> misquoted, then used against you.
Date: Wed, 29 Jul 2009 15:06:47 -0400
From: Mark <manager at monmouth dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
--=====================_916724==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hi
Even when I corrected the bad from lines, the popper would still give
the from lines error until I removed both X-UID lines. Then it popped no issue.
As far as the X-UID lines, I am certain popper puts them in there
when people set their client to leave mail on server.
So the difference I saw was the different type of X-UID written.
4.015 writes X-UIDL and 4.1 writes X-UID
I do not want to run traces until we agree on popper writing X-UID
lines :-) because I feel that is where the problem lies
Thanks
Mark
At 01:29 PM 7/27/2009, Randall Gellens wrote:
>At 8:16 AM -0400 7/24/09, Mark wrote:
>
>> I installed the 4.1b17 and the problems between IMAP and qpopper
>> were magnified by a factor of 5. Using the 4.0xx series of qpopper
>> I would have an issue once in awhile and easily fix the From lines
>> being broken. After getting a rash of support calls and my support
>> staff having a mini melt down, I restored the 4.014 qpopper I was
>> running and everything went back to normal. Editing mail spools to
>> fix the broken From lines I noticed two X-UID lines in the header
>> which I did not see before.
>>
>>
>> For example:
>>
>> normal everyday X-UIDL line
>> X-UIDL: c@+"!-$`"!^gF"!^3f"!
>>
>> and
>>
>> X-UID:3
>>
>>
>> I assumed 4.b17 put the X-UID:3 in there and it was conflicting
>> with the old type of X-UIDL line because even fixing the From
>> lines people still could not pop those spools until I removed BOTH X-UID lines
>>
>>
>> Any ideas?
>>
>> Thanks
>>
>> Mark
>
>Hi Mark,
>
>Qpopper doesn't write "X-UID" lines. Maybe the IMAP server is doing
>this? Even so, I'm not sure why there would be a difference between
>4.0 and 4.1.
>
>When you say users couldn't pop their mail until you deleted the
>X--UID and X-UIDL lines, what was happening?
>
>Would it be possible for you to reproduce the problem with Qpopper tracing?
>
>To enable tracing in Qpopper in standalone mode:
>
>1. Do a 'make clean'
>2. Re-run ./configure, adding '--enable-debugging'.
>4. Add '-t <tracefile-path>' to the command line for Qpopper.
>
>This causes detailed tracing to be written to the file specified as
>'tracefile-path'.
>
>
>
>>
>> At 07:00 PM 7/23/2009, Randall Gellens wrote:
>>
>>
>>> At 3:57 PM -0400 7/22/09, Mark wrote:
>>>
>>>> Does 4.1x write X-UID differently then 4.0x?
>>>
>>> No, but there are several options which control if and how X-UID
>>> is handled.
>>>
>>> Are you seeing a problem with X-UIDL?
>>>
>>> --
>>> Randall Gellens
>>> Opinions are personal; facts are suspect; I speak for myself only
>>> -------------- Randomly selected tag: ---------------
>>> You have the right to remain silent. Anything you say will be
>>> misquoted, then used against you.
>
>
>
--=====================_916724==.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<body>
<font size=3>Hi<br><br>
Even when I corrected the bad from lines, the popper would still give the
from lines error until I removed both X-UID lines. Then it popped no
issue.<br><br>
As far as the X-UID lines, I am certain popper puts them in there when
people set their client to leave mail on server.<br><br>
So the difference I saw was the different type of X-UID written. 4.015
writes X-UIDL and 4.1 writes X-UID<br><br>
I do not want to run traces until we agree on popper writing X-UID lines
:-) because I feel that is where the problem lies <br><br>
<br>
Thanks<br><br>
Mark<br><br>
<br><br>
<br><br>
<br><br>
At 01:29 PM 7/27/2009, Randall Gellens wrote:<br>
<br>
<blockquote type=cite class=cite cite="">At 8:16 AM -0400 7/24/09, Mark
wrote:<br><br>
<blockquote type=cite class=cite cite=""> I installed the 4.1b17 and
the problems between IMAP and qpopper were magnified by a factor of 5.
Using the 4.0xx series of qpopper I would have an issue once in awhile
and easily fix the From lines being broken. After getting a rash of
support calls and my support staff having a mini melt down, I restored
the 4.014 qpopper I was running and everything went back to normal.
Editing mail spools to fix the broken From lines I noticed two X-UID
lines in the header which I did not see before.<br><br>
<br>
For example:<br><br>
normal everyday X-UIDL line<br>
X-UIDL: c@+"!-$`"!^gF"!^3f"!<br><br>
and<br><br>
X-UID:3<br><br>
<br>
I assumed 4.b17 put the X-UID:3 in there and it was conflicting
with the old type of X-UIDL line because even fixing the From lines
people still could not pop those spools until I removed BOTH X-UID
lines<br><br>
<br>
Any ideas?<br><br>
Thanks<br><br>
Mark</blockquote><br>
Hi Mark,<br><br>
Qpopper doesn't write "X-UID" lines. Maybe the IMAP
server is doing this? Even so, I'm not sure why there would be a
difference between 4.0 and 4.1.<br><br>
When you say users couldn't pop their mail until you deleted the X--UID
and X-UIDL lines, what was happening?<br><br>
Would it be possible for you to reproduce the problem with Qpopper
tracing?<br><br>
To enable tracing in Qpopper in standalone mode:<br><br>
1. Do a 'make clean'<br>
2. Re-run ./configure, adding '--enable-debugging'.<br>
4. Add '-t <tracefile-path>' to the command line for
Qpopper.<br><br>
This causes detailed tracing to be written to the file specified as
'tracefile-path'.<br><br>
<br><br>
<blockquote type=cite class=cite cite=""><br>
At 07:00 PM 7/23/2009, Randall Gellens wrote:<br><br>
<br>
<blockquote type=cite class=cite cite=""> At 3:57 PM -0400 7/22/09,
Mark wrote:<br><br>
<blockquote type=cite class=cite cite=""> Does 4.1x write X-UID
differently then 4.0x?<br>
</blockquote><br>
No, but there are several options which control if and how X-UID is
handled.<br><br>
Are you seeing a problem with X-UIDL?<br><br>
--<br>
Randall Gellens<br>
Opinions are personal; facts are
suspect; I speak for myself only<br>
-------------- Randomly selected tag: ---------------<br>
You have the right to remain silent. Anything you say will
be<br>
misquoted, then used against
you.</blockquote></blockquote><br><br>
<br>
</font></blockquote></body>
</html>
--=====================_916724==.ALT--
Date: Sun, 2 Aug 2009 15:53:53 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Qpopper 4.0.18 and 4.1b17 available
Hi Mark,
At 3:06 PM -0400 7/29/09, Mark wrote:
> Even when I corrected the bad from lines, the popper would still
> give the from lines error until I removed both X-UID lines. Then it
> popped no issue.
The error was that Qpopper was unable to parse the spool because it
couldn't find the "from " separator lines?
>
> As far as the X-UID lines, I am certain popper puts them in there
> when people set their client to leave mail on server.
If people leave mail on server and writing status/uidl hasn't been
disabled, then Qpopper writes a "Status:" header line. This is done
in popper/pop_updt.c lines 557-564 (an existing "Status:" header is
updated to indicate a message has been downloaded at lines 586-588).
> So the difference I saw was the different type of X-UID written.
> 4.015 writes X-UIDL and 4.1 writes X-UID
Qpopper writes an "X-UIDL:" header line if writing status/uidl hasn't
been disabled. It does this in popper/pop_updt.c lines 539-545. It
doesn't write "X-UID" lines, at least not intentionally.
Writing status/x-uidl headers is enabled by default, but can be
disabled by adding "set update-status-headers = false" in a
configuration file.
> I do not want to run traces until we agree on popper writing X-UID
> lines :-) because I feel that is where the problem lies
A trace can help show what is going on. Qpopper doesn't have any
code to generate or write a line such as "X-UID:3" so either there is
a weird bug in Qpopper or some other process is writing it.
Are you using server mode? Do you set any of the options which
affect cache files?
One difference between 4.0 and 4.1 is that 4.1 uses the cache file
even if new mail has arrived. This speeds up session start-up when
users leave mail on the server, since only the new mail is read from
the spool. However, if another process has modified the spool,
corruption can occur. Try setting the "conservative-cache" option,
which tells Qpopper not to use the cache if the spool doesn't exactly
match the cache. To do this, add "set conservative-cache = true" to
the configuration file. If you have a situation where some users
might use IMAP as well as POP, while others use only POP, you can set
the "conservative-cache" option for only those users who might use
IMAP. This will speed things up for the POP-only users if they leave
mail on the server. (Or, you can set the option in a global
configuration file and then set it to false for POP-only users.)
>
> At 01:29 PM 7/27/2009, Randall Gellens wrote:
>
>
>> At 8:16 AM -0400 7/24/09, Mark wrote:
>>
>>> I installed the 4.1b17 and the problems between IMAP and qpopper
>>> were magnified by a factor of 5. Using the 4.0xx series of
>>> qpopper I would have an issue once in awhile and easily fix the
>>> From lines being broken. After getting a rash of support calls
>>> and my support staff having a mini melt down, I restored the
>>> 4.014 qpopper I was running and everything went back to normal.
>>> Editing mail spools to fix the broken From lines I noticed two
>>> X-UID lines in the header which I did not see before.
>>>
>>>
>>> For example:
>>>
>>> normal everyday X-UIDL line
>>> X-UIDL: c@+"!-$`"!^gF"!^3f"!
>>>
>>> and
>>>
>>> X-UID:3
>>>
>>>
>>> I assumed 4.b17 put the X-UID:3 in there and it was conflicting
>>> with the old type of X-UIDL line because even fixing the From
>>> lines people still could not pop those spools until I removed
>>> BOTH X-UID lines
>>>
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>> Mark
>>>
>>
>> Hi Mark,
>>
>> Qpopper doesn't write "X-UID" lines. Maybe the IMAP server is
>> doing this? Even so, I'm not sure why there would be a difference
>> between 4.0 and 4.1.
>>
>> When you say users couldn't pop their mail until you deleted the
>> X--UID and X-UIDL lines, what was happening?
>>
>> Would it be possible for you to reproduce the problem with Qpopper tracing?
>>
>> To enable tracing in Qpopper in standalone mode:
>>
>> 1. Do a 'make clean'
>> 2. Re-run ./configure, adding '--enable-debugging'.
>> 4. Add '-t <tracefile-path>' to the command line for Qpopper.
>>
>> This causes detailed tracing to be written to the file specified
>> as 'tracefile-path'.
>>
>>
>>>
>>> At 07:00 PM 7/23/2009, Randall Gellens wrote:
>>>
>>>> At 3:57 PM -0400 7/22/09, Mark wrote:
>>>>
>>>>> Does 4.1x write X-UID differently then 4.0x?
>>>>>
>>>>
>>>> No, but there are several options which control if and how
>>>> X-UID is handled.
>>>>
>>>> Are you seeing a problem with X-UIDL?
>>>>
>>>> --
>>>> Randall Gellens
>>>> Opinions are personal; facts are suspect; I speak for myself only
>>>> -------------- Randomly selected tag: ---------------
>>>> You have the right to remain silent. Anything you say will be
>>>> misquoted, then used against you.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
Flappity, Floppity, Flip!
The Mouse on the M–bius Strip.
The Strip revolved,
The Mouse dissolved
In a chronodimensional skip.
--Frederick Winsor, "The Space Child's Mother Goose"
[Simon & Schuster 1966], paperback
Date: Sun, 13 Sep 2009 17:37:42 -0400
From: Matt Garretson <mattg at assembly dot state dot ny dot us>
Subject: Compiling 4.0.18 under Fedora 11 - getline() conflict
When trying to build Qpopper 4.0.18 on a fresh Fedora 11
installation, I got this error:
popper.c: In function ëqpopperí:
popper.c:153: error: conflicting types for ëgetlineí
/usr/include/stdio.h:653: note: previous declaration of ëgetlineí was here
getline() is indeed defined in stdio.h . But, interestingly, the
build succeeds under Fedora 10, which also has getline() in stdio.h.
The difference between the two Fedoras seems to be that in
Fedora 10, getline() is contained within an #ifdef __USE_GNU ,
while in Fedora 11, it's contained within an #ifdef __USE_XOPEN2K8
I'm not sure the implications of all this, but as a quick fix
I renamed all references to Qpopper's getline() to qgetline()
and now it builds successfully.
-Matt
From: jnemeth at victoria dot tc dot ca (John Nemeth)
Date: Thu, 24 Sep 2009 02:23:07 -0700
Subject: Re: Compiling 4.0.18 under Fedora 11 - getline() conflict
On Feb 3, 12:13pm, Matt Garretson wrote:
}
} When trying to build Qpopper 4.0.18 on a fresh Fedora 11
} installation, I got this error:
}
} popper.c: In function ëqpopperí:
} popper.c:153: error: conflicting types for ëgetlineí
} /usr/include/stdio.h:653: note: previous declaration of ëgetlineí was here
}
} getline() is indeed defined in stdio.h . But, interestingly, the
} build succeeds under Fedora 10, which also has getline() in stdio.h.
} The difference between the two Fedoras seems to be that in
} Fedora 10, getline() is contained within an #ifdef __USE_GNU ,
} while in Fedora 11, it's contained within an #ifdef __USE_XOPEN2K8
We're seeing the same type of problem on NetBSD. It seems that
getline() is now a POSIX functions. This means that all apps must be
adapted to use the OS supplied getline() if it exists or rename their
internal getline().
}-- End of excerpt from Matt Garretson
Date: Sat, 17 Oct 2009 16:50:58 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1b18 available
Qpopper 4.1b18 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.b17 to 4.1.b18:
--------------------------------
1. Rename 'getline' to 'Qgetline' (fix conflict on some platforms).
2. Resolve several compiler warnings.
Changes from 4.1.b16 to 4.1.b17:
--------------------------------
1. Fix several problems with 'make install'.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
I am not "Deliciously Saucy"
--Written on the chalkboard by Bart in the
opening of _The_Simpsons_ (TV show)
Date: Sat, 17 Oct 2009 16:50:10 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.0.18 available
Qpopper 4.0.18 is available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/>.
The full list of changes is in the distribution.
Changes from 4.0.18 to 4.0.19:
-----------------------------
1. Rename 'getline' to 'Qgetline' (fix conflict on some platforms).
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
I always avoid prophesying beforehand, because it is a much better
policy to prophesy after the event has already taken place.
--Winston Churchill
Date: Mon, 19 Oct 2009 11:36:43 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Qpopper 4.1 Status
Qpopper 4.1 is currently at b18 (available at
<ftp://ftp.qualcomm.com/eudora/servers/unix/popper/beta/>). I think
4.1 is ready to go official release, except for the documentation:
the source for the Admin Guide got messed up and I've been trying to
fix it for a while now.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
Democracy is a form of government that substitutes election by the
incompetent many for appointment by the corrupt few.
--G. B. Shaw
Date: Sun, 20 Dec 2009 12:09:10 -0700
Subject: "ERR POP EOF or I/O Error" messages have begun appearing in the
From: Keith Christian <keith1christian at gmail dot com>
Qpopper has been performing very well for us but lately (within the
last month) we've begun seeing quite a few (50 or more per day) of
these type of messages in the /var/log/maillog file (times, usernames,
and IP's have been changed.)
Dec 14 HH:MM:50 mailserver14414 popper[20830]: (v4.0.8) Servicing
request from "www.xxx.yyy.zzz" at www.xxx.yyy.zzz
Dec 14 HH:MM:50 mailserver14414 popper[20830]: (null) at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
Dec 14 HH:MM:50 mailserver14414 popper[20831]: (v4.0.8) Servicing
request from "www.xxx.yyy.zzz" at www.xxx.yyy.zzz
Dec 14 HH:MM:50 mailserver14414 popper[20831]: (null) at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
Dec 14 HH:MM:37 mailserver14414 popper[5619]: someuser15357 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
Dec 15 HH:MM:10 mailserver14414 popper[29457]: someuser1383 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
Dec 15 HH:MM:10 mailserver14414 popper[29457]: Stats: someuser1383 0 0
4 471851 www.xxx.yyy.zzz www.xxx.yyy.zzz
These occur anytime of day or night, and this behavior lasts anywhere
from a few minutes to a few hours. We had an eposode that ran for
about 2-1/2 hours yesterday.
Strangely, some of these occur with a user account (e.g. someuser15357
and/or someuser1383) are in the -ERR POP EOF or I/O Error line, but
the vast majority of these -ERR POP EOF or I/O Error lines have
"(null)" as the username.
Would appreciate any ideas. No other issues with the version of
Qpopper we're running, even though it's a bit older (v4.0.8) so I'm
not inclined to think it's the age of the build. OS is RHEL4 WS
Linux.
Thanks!
========Keith
Date: Mon, 21 Dec 2009 18:47:33 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: "ERR POP EOF or I/O Error" messages have begun appearing
At 12:09 PM -0700 12/20/09, Keith Christian wrote:
> Qpopper has been performing very well for us but lately (within the
> last month) we've begun seeing quite a few (50 or more per day) of
> these type of messages in the /var/log/maillog file (times, usernames,
> and IP's have been changed.)
>
> Dec 14 HH:MM:50 mailserver14414 popper[20830]: (v4.0.8) Servicing
> request from "www.xxx.yyy.zzz" at www.xxx.yyy.zzz
> Dec 14 HH:MM:50 mailserver14414 popper[20830]: (null) at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
> Dec 14 HH:MM:50 mailserver14414 popper[20831]: (v4.0.8) Servicing
> request from "www.xxx.yyy.zzz" at www.xxx.yyy.zzz
> Dec 14 HH:MM:50 mailserver14414 popper[20831]: (null) at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
> Dec 14 HH:MM:37 mailserver14414 popper[5619]: someuser15357 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
> Dec 15 HH:MM:10 mailserver14414 popper[29457]: someuser1383 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR POP EOF or I/O Error
> Dec 15 HH:MM:10 mailserver14414 popper[29457]: Stats: someuser1383 0 0
> 4 471851 www.xxx.yyy.zzz www.xxx.yyy.zzz
>
> These occur anytime of day or night, and this behavior lasts anywhere
> from a few minutes to a few hours. We had an eposode that ran for
> about 2-1/2 hours yesterday.
>
> Strangely, some of these occur with a user account (e.g. someuser15357
> and/or someuser1383) are in the -ERR POP EOF or I/O Error line, but
> the vast majority of these -ERR POP EOF or I/O Error lines have
> "(null)" as the username.
>
> Would appreciate any ideas. No other issues with the version of
> Qpopper we're running, even though it's a bit older (v4.0.8) so I'm
> not inclined to think it's the age of the build. OS is RHEL4 WS
> Linux.
The error message indicates that the connection with the client ended
abruptly; Qpopper got an error trying to read data from the client.
The presence or absence of a user account tells you if the
disconnection occurred before or after the user authenticated.
So, I think the question is: Why are you getting more of these now,
and why do you get these in flurries, instead of sporadically?
The error could be the client timing out and closing the connection
without sending a QUIT, or something in between the client and the
server (a NAT box maybe) sending a TCP RST to close the connection.
The client could be timing out because of network problems (for
example, congestion or other problems causing high packet loss,
forcing retransmission of packets and high latency), or server
problems delaying the Qpopper response, or client problems or
misconfiguration (such as a too-short timeout).
The log snippets above suggest that the error happens immediately
(same second) as the initial connection. Is this happening
generally? If so, it would tend to rule out the timeout situation,
suggesting instead a network box or problem with the client.
There are several things you can do to get more information and track
it down further. One would be to enable Qpopper debugging/trace
records, and another would be packet sniffing. If you can identify
certain clients or connections that tend to show the problem, you can
use Qpopper tracing or packet sniffing for those, to reduce the
amount of data.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
If Qpopper is run from inetd/xinetd:
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t <tracefile-path>'.
4. Send inetd (or xinetd) a HUP signal.
If Qpopper is run in standalone mode:
3. Add '-d' or '-t <tracefile-path>' to the command line
or
If you use a configuration file (in either inetd/xinetd or
standalone), you can instead:
3. Add 'set debug' or 'set tracefile = /some/path/tracefile' to
either a global or user-specific configuration file.
This causes detailed tracing to be written to the syslog or to the
file specified as 'tracefile'.
Date: Wed, 23 Dec 2009 07:38:06 -0700
Subject: Re: "ERR POP EOF or I/O Error" messages have begun appearing in the
From: Keith Christian <keith1christian at gmail dot com>
On Mon, Dec 21, 2009 at 7:47 PM, Randall Gellens <randy@qualcomm.com> wrote:
> To enable tracing in Qpopper:
Hi Randall,
Many thanks for the suggestions. Researching how to increase
Qpopper's logging was the next thing on my list.
I appreciate the detailed reply. When we find a root cause, I'll post
findings back to the list.
=======Keith
Date: Thu, 7 Jan 2010 09:53:52 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: FrameMaker users?
Anyone on the list know FrameMaker? I'm having some problems with
the source for the Administrator's Guide.
--
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: Mon, 8 Mar 2010 10:01:05 -0700
Subject: A few pop locks in /var/spool/mail not removed
From: Keith Christian <keith1christian at gmail dot com>
Hello fellow qpopper list dwellers,
I'm seeing a slowly increasing number of pop lock busy errors on our
mailserver. This mailserver load has been increasing over time but is
now capped. Running Qpopper 4.0.8.
Is there any interpretation of the reason for old lock files not being
removed? We see below 10 lock files more than 11 minutes old ("set
timeout = 600" in qpopper.cfg.)
Wondering why not all of the lock files are deleted, when the vast
majority are properly deleted?
Mon Mar 8 16:31:20 GMT 2010
+ find /var/spool/mailtemp/ -maxdepth 1 -type f -name '.*.pop' '!'
-newer /tmp/lock_timer_watch -exec ls -l '{}' ';'
-rw-rw---- 1 wxyz8653 mail 0 Mar 8 13:40 /var/spool/mailtemp/.wxyz8653.pop
-rw-rw---- 1 wxyza7833 mail 0 Mar 4 15:53 /var/spool/mailtemp/.wxyza7833.pop
-rw-rw---- 1 wxyz15771 mail 0 Mar 4 13:03 /var/spool/mailtemp/.wxyz15771.pop
-rw-rw---- 1 wxyz19850 mail 0 Mar 8 15:46 /var/spool/mailtemp/.wxyz19850.pop
-rw-rw---- 1 wxyz27862 mail 0 Mar 8 14:04 /var/spool/mailtemp/.wxyz27862.pop
-rw-rw---- 1 wxyz11913 mail 0 Mar 5 13:39 /var/spool/mailtemp/.wxyz11913.pop
-rw-rw---- 1 wxyz21606 mail 0 Mar 5 16:53 /var/spool/mailtemp/.wxyz21606.pop
-rw-rw---- 1 wxyza4996 mail 0 Mar 5 19:21 /var/spool/mailtemp/.wxyza4996.pop
-rw-rw---- 1 wxyz27508 mail 0 Mar 8 14:05 /var/spool/mailtemp/.wxyz27508.pop
-rw-rw---- 1 wxyza20122 mail 0 Mar 5 17:04 /var/spool/mailtemp/.wxyza20122.pop
+ touch /tmp/lock_timer_watch
+ sleep 660
grep "IN\-USE" /var/log/maillog | tail
Mar 8 16:42:37 mailserver-a123 popper[30501]: wxyz28518 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyz28518.pop lock busy! Is another session
active? (11)
Mar 8 16:43:09 mailserver-a123 popper[30602]: wxyza20439 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyza20439.pop lock busy! Is another session
active? (11)
Mar 8 16:44:40 mailserver-a123 popper[31064]: wxyz28518 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyz28518.pop lock busy! Is another session
active? (11)
Mar 8 16:44:51 mailserver-a123 popper[31126]: wxyza3777 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyza3777.pop lock busy! Is another session
active? (11)
Mar 8 16:45:00 mailserver-a123 popper[31168]: wxyza30999 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyza30999.pop lock busy! Is another session
active? (11)
Mar 8 16:45:51 mailserver-a123 popper[31471]: wxyz19586 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyz19586.pop lock busy! Is another session
active? (11)
Mar 8 16:47:20 mailserver-a123 popper[31854]: wxyza27661 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyza27661.pop lock busy! Is another session
active? (11)
Mar 8 16:47:48 mailserver-a123 popper[31992]: wxyz4458 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyz4458.pop lock busy! Is another session
active? (11)
Mar 8 16:47:52 mailserver-a123 popper[31994]: wxyza6021 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyza6021.pop lock busy! Is another session
active? (11)
Mar 8 16:49:06 mailserver-a123 popper[32350]: wxyz11814 at
www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
/var/spool/mailtemp/.wxyz11814.pop lock busy! Is another session
active? (11)
Thanks,
======Keith
Date: Sun, 14 Mar 2010 19:31:08 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: A few pop locks in /var/spool/mail not removed
At 10:01 AM -0700 3/8/10, Keith Christian wrote:
> Hello fellow qpopper list dwellers,
>
> I'm seeing a slowly increasing number of pop lock busy errors on our
> mailserver. This mailserver load has been increasing over time but is
> now capped. Running Qpopper 4.0.8.
>
> Is there any interpretation of the reason for old lock files not being
> removed? We see below 10 lock files more than 11 minutes old ("set
> timeout = 600" in qpopper.cfg.)
>
> Wondering why not all of the lock files are deleted, when the vast
> majority are properly deleted?
Hi Keith,
My guess is that something is unexpectedly killing the Qpopper
processes before they can release the locks. I'd be interested in
finding out what's going on. How often does this happen? Is it
feasible to run Qpopper with debug tracing to capture a lock not
being released?
>
> Mon Mar 8 16:31:20 GMT 2010
> + find /var/spool/mailtemp/ -maxdepth 1 -type f -name '.*.pop' '!'
> -newer /tmp/lock_timer_watch -exec ls -l '{}' ';'
>
> -rw-rw---- 1 wxyz8653 mail 0 Mar 8 13:40 /var/spool/mailtemp/.wxyz8653.pop
> -rw-rw---- 1 wxyza7833 mail 0 Mar 4 15:53
> /var/spool/mailtemp/.wxyza7833.pop
> -rw-rw---- 1 wxyz15771 mail 0 Mar 4 13:03
> /var/spool/mailtemp/.wxyz15771.pop
> -rw-rw---- 1 wxyz19850 mail 0 Mar 8 15:46
> /var/spool/mailtemp/.wxyz19850.pop
> -rw-rw---- 1 wxyz27862 mail 0 Mar 8 14:04
> /var/spool/mailtemp/.wxyz27862.pop
> -rw-rw---- 1 wxyz11913 mail 0 Mar 5 13:39
> /var/spool/mailtemp/.wxyz11913.pop
> -rw-rw---- 1 wxyz21606 mail 0 Mar 5 16:53
> /var/spool/mailtemp/.wxyz21606.pop
> -rw-rw---- 1 wxyza4996 mail 0 Mar 5 19:21
> /var/spool/mailtemp/.wxyza4996.pop
> -rw-rw---- 1 wxyz27508 mail 0 Mar 8 14:05
> /var/spool/mailtemp/.wxyz27508.pop
> -rw-rw---- 1 wxyza20122 mail 0 Mar 5 17:04
> /var/spool/mailtemp/.wxyza20122.pop
> + touch /tmp/lock_timer_watch
> + sleep 660
>
>
>
>
> grep "IN\-USE" /var/log/maillog | tail
>
> Mar 8 16:42:37 mailserver-a123 popper[30501]: wxyz28518 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyz28518.pop lock busy! Is another session
> active? (11)
> Mar 8 16:43:09 mailserver-a123 popper[30602]: wxyza20439 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyza20439.pop lock busy! Is another session
> active? (11)
> Mar 8 16:44:40 mailserver-a123 popper[31064]: wxyz28518 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyz28518.pop lock busy! Is another session
> active? (11)
> Mar 8 16:44:51 mailserver-a123 popper[31126]: wxyza3777 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyza3777.pop lock busy! Is another session
> active? (11)
> Mar 8 16:45:00 mailserver-a123 popper[31168]: wxyza30999 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyza30999.pop lock busy! Is another session
> active? (11)
> Mar 8 16:45:51 mailserver-a123 popper[31471]: wxyz19586 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyz19586.pop lock busy! Is another session
> active? (11)
> Mar 8 16:47:20 mailserver-a123 popper[31854]: wxyza27661 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyza27661.pop lock busy! Is another session
> active? (11)
> Mar 8 16:47:48 mailserver-a123 popper[31992]: wxyz4458 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyz4458.pop lock busy! Is another session
> active? (11)
> Mar 8 16:47:52 mailserver-a123 popper[31994]: wxyza6021 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyza6021.pop lock busy! Is another session
> active? (11)
> Mar 8 16:49:06 mailserver-a123 popper[32350]: wxyz11814 at
> www.xxx.yyy.zzz (www.xxx.yyy.zzz): -ERR [IN-USE]
> /var/spool/mailtemp/.wxyz11814.pop lock busy! Is another session
> active? (11)
>
>
> Thanks,
>
> ======Keith
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
Certe, Toto, sentio nos in Kansate non iam adesse. --Dorothea
Date: Thu, 22 Apr 2010 08:45:25 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: test -- please ignore
This is a test. Please ignore.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
The first ninety percent of the task takes ninety percent of
the time, and the last ten percent takes the other ninety percent.
Date: Mon, 26 Apr 2010 11:13:33 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: test -- please ignore
This is a test.
Please ignore.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly selected tag: ---------------
2 + 2 = 5 for extremely large values of 2.
Last updated on 26 Apr 2010 by Pensive Mailing List Admin