The qpopper list archive ending on 25 Sep 2001
Topics covered in this issue include:
1. Re: Redhat Linux 7.1 and qpopper
"Kenneth Porter" <shiva at well dot com>
Wed, 05 Sep 2001 16:09:41 -0700
2. create new user in qpopper
Alexander Pubanz <alexander.pubanz at teamware-gmbh dot de>
Thu, 06 Sep 2001 14:10:51 +0200
3. Error at end of pop stream.
Darren Dunham <ddunham at taos dot com>
Thu, 6 Sep 2001 15:49:37 -0700 (PDT)
4. Re: create new user in qpopper
"Kenneth Porter" <shiva at well dot com>
Thu, 06 Sep 2001 16:56:08 -0700
5. Re: Error at end of pop stream.
Randall Gellens <randy at pensive dot org>
Thu, 6 Sep 2001 19:15:13 -0700
6. TLS/SSL errors
The Doctor <doctor at doctor.nl2k.ab dot ca>
Fri, 7 Sep 2001 01:55:12 -0600
7. Re: TLS/SSL errors
"Kenneth Porter" <shiva at well dot com>
Fri, 07 Sep 2001 01:15:43 -0700
8. CA root certificates
"Mark J. de Jong" <dejongm at secdog dot com>
Fri, 7 Sep 2001 08:43:14 -0400
9. Re: Error at end of pop stream.
Darren Dunham <ddunham at taos dot com>
Fri, 7 Sep 2001 08:44:02 -0700 (PDT)
10. Re: TLS/SSL errors
The Doctor <doctor at doctor.nl2k.ab dot ca>
Fri, 7 Sep 2001 09:50:42 -0600
11. Re: TLS/SSL errors
"Kenneth Porter" <shiva at well dot com>
Fri, 07 Sep 2001 17:00:15 -0700
12. Re: TLS/SSL errors
The Doctor <doctor at doctor.nl2k.ab dot ca>
Sat, 8 Sep 2001 07:43:13 -0600
13. Separate machines
"Katsumi J. Saitoh" <jsaitoh at ntti.net dot sg>
Mon, 10 Sep 2001 12:57:38 +0800
14. Qpopper and DRAC on separate machines
"Kenneth Porter" <shiva at well dot com>
Mon, 10 Sep 2001 22:10:46 -0700
15. Configuration for standalone operation on port 110 AND 995
Debian User <eneal at bnbtv dot com>
11 Sep 2001 21:32:49 -0400
16. Re: Configuration for standalone operation on port 110 AND 995
The Doctor <doctor at doctor.nl2k.ab dot ca>
Tue, 11 Sep 2001 19:49:25 -0600
17. Re: Configuration for standalone operation on port 110 AND 995
Clifton Royston <cliftonr at lava dot net>
Tue, 11 Sep 2001 16:21:48 -1000
18. qpopper logs: syslog vs other log
"Nuno Teixeira" <nuno.mailinglists at pt-quorum dot com>
Wed, 12 Sep 2001 17:30:36 +0100
19. Re: qpopper logs: syslog vs other log
Chuck Yerkes <chuck+qpopper at yerkes dot com>
Wed, 12 Sep 2001 10:27:42 -0700
20. Re: Error at end of pop stream.
Clifton Royston <cliftonr at lava dot net>
Wed, 12 Sep 2001 10:44:40 -1000
21. Re: qpopper logs: syslog vs other log
Randall Gellens <randy at qualcomm dot com>
Wed, 12 Sep 2001 14:06:52 -0700
22. Re: Configuration for standalone operation on port 110 AND 995
Randall Gellens <randy at qualcomm dot com>
Wed, 12 Sep 2001 14:03:57 -0700
23. What can cause these errors?
Darren Dunham <ddunham at taos dot com>
Fri, 14 Sep 2001 10:25:28 -0700 (PDT)
24. Re: What can cause these errors?
Clifton Royston <cliftonr at lava dot net>
Fri, 14 Sep 2001 08:19:58 -1000
25. Re: What can cause these errors?
"Michael Kolos" <michael at colba dot net>
Fri, 14 Sep 2001 14:29:31 -0400
26. Re: What can cause these errors?
Randall Gellens <randy at qualcomm dot com>
Fri, 14 Sep 2001 15:53:26 -0700
27. hiding version
"Alex M" <alex at myzona dot net>
Sun, 16 Sep 2001 13:48:54 -0700
28. Re: hiding version
Frank Pineau <frank at pineaus dot com>
Sun, 16 Sep 2001 16:14:25 -0500
29. Re: What can cause these errors?
"Michael Kolos" <michael at colba dot net>
Mon, 17 Sep 2001 09:53:46 -0400
30. Re: hiding version
Randall Gellens <randy at qualcomm dot com>
Mon, 17 Sep 2001 10:08:12 -0700
31. acker attack?
"Ruggero Dell'Osso" <dellosso at agr.unipi dot it>
Tue, 18 Sep 2001 10:30:02 +0200
32. Re: acker attack?
Wayne Heming <wheming at hemnet.com dot au>
Tue, 18 Sep 2001 21:15:48 +1000
33. Anybody using an account other than root to run qpopper?
Ben Lormis <Ben.Lormis at dig dot com>
Tue, 18 Sep 2001 08:34:54 -0700
34. Re: acker attack?
Randall Gellens <randy at qualcomm dot com>
Tue, 18 Sep 2001 15:36:17 -0700
35. Re: acker attack?
Randall Gellens <randy at qualcomm dot com>
Tue, 18 Sep 2001 15:34:29 -0700
36. Re: Anybody using an account other than root to run qpopper?
Randall Gellens <randy at qualcomm dot com>
Tue, 18 Sep 2001 15:38:17 -0700
37. -ERR [SYS/TEMP] Unable to get spool name
<chandler at grendel.stranded dot org>
Thu, 20 Sep 2001 18:37:47 -0500 (CDT)
38. What does this mean
Homer Wilson Smith <homer at lightlink dot com>
Sat, 22 Sep 2001 13:01:20 -0400 (EDT)
39. User Disconnect, Popper keeps running for a long time afterwards
Qpopper Mailing List <popper at iggy.triode.net dot au>
Sun, 23 Sep 2001 16:45:49 +1000 (EST)
40. Re: -ERR [SYS/TEMP] Unable to get spool name
peter.allen at moon-light.co dot uk
Mon, 24 Sep 2001 11:27:54 +0100
41. Re: What does this mean
Randall Gellens <randy at qualcomm dot com>
Mon, 24 Sep 2001 15:15:01 -0700
42. What's up with qpopper-announce?
"Dan Harkless" <qpopper at dilvish.speed dot net>
Mon, 24 Sep 2001 19:46:28 -0700
43. I lose email when our server crashes due to lack of O_EXCL use
"Dan Harkless" <qpopper at dilvish.speed dot net>
Mon, 24 Sep 2001 20:31:18 -0700
44. Re: What's up with qpopper-announce?
Randall Gellens <randy at pensive dot org>
Mon, 24 Sep 2001 21:41:52 -0700
45. Re: I lose email when our server crashes due to lack of O_EXCL
peter.allen at moon-light.co dot uk
Tue, 25 Sep 2001 07:08:32 +0100
46. Re: I lose email when our server crashes due to lack of O_EXCL use
Peter Evans <peter at gol dot com>
Tue, 25 Sep 2001 20:37:17 +0900
47. troubleshooting with Qpopper standalone
=?iso-8859-1?Q?CRESTIN_Frédéric?= <fcrestin at lexsi dot com>
Tue, 25 Sep 2001 14:05:29 +0200
48. XTND XLST command
Steve Palm <stevep at sga dot org>
Tue, 25 Sep 2001 10:45:57 -0500
49. Re: I lose email when our server crashes due to lack of
Randall Gellens <randy at qualcomm dot com>
Tue, 25 Sep 2001 15:32:36 -0700
50. Re: I lose email when our server crashes due to lack of O_EXCL use
Gregory Hicks <ghicks at cadence dot com>
Tue, 25 Sep 2001 17:20:53 -0700 (PDT)
From: "Kenneth Porter" <shiva at well dot com>
Date: Wed, 05 Sep 2001 16:09:41 -0700
Subject: Re: Redhat Linux 7.1 and qpopper
On Wed, 05 Sep 2001 09:51:44 +0200, Ruggero Dell'Osso wrote:
>If you use PAM see also PAM configuration in users manual pag. 51
While that's often an issue, it doesn't apply in this case. Juan was
reporting that he couldn't even connect with telnet, so the problem was
before the authentication phase, somewhere in the connection
establishment phase. As he's reported, it was tcp_wrappers that was
blocking him.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Date: Thu, 06 Sep 2001 14:10:51 +0200
From: Alexander Pubanz <alexander.pubanz at teamware-gmbh dot de>
Subject: create new user in qpopper
Hi,
could anyone send me a link where it is described, how I can create a new
user in qpopper 4.0 ?
Or if you got a faq or howto I would really appreciate if you could send it
to me.
Thanks for your help !
Mit freundlichen Grüßen,
Alexander Pubanz
____________________________________________________________
Teamware GmbH
Stahlgruberring 11
81829 Muenchen
http://www.teamware-gmbh.de/
From: Darren Dunham <ddunham at taos dot com>
Subject: Error at end of pop stream.
Date: Thu, 6 Sep 2001 15:49:37 -0700 (PDT)
I'm running Qpopper 4.0.3 on a Solaris 8 machine. There are no local
users, just sendmail/procmail for delivery and qpopper for retreival.
The users are all automated processes which pull down the mail and
stick it into a database. Since we installed this version, they've
started getting some errors. This has shown up in their logs.
MailServerException: Unexpected response to command "QUIT" from POP server: -ERR maillock error 'Other lock error' (5) on '/var/mail/.dbuser.pop': No such file or directory (2)
So all the mail comes in, but the QUIT gives an error and the mail is
not deleted. It all comes down the next time it's queried. There are a
few hundred unique users on the box (all the same database), and they've
only seen the error a few times. It's not reproduceable by anything
that I've tried.
We are running in server mode, since the process does delete all the
mail at the end. Also, this process only grabs one mailbox at a time,
so I'm fairly sure there's nothing strange like multiple pop sessions
being attempted simultaneously.
Has anyone seen anything like this associated with 4.0.3?
Thanks!
--
Darren Dunham ddunham at taos dot com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< How are you gentlemen!! Take off every '.SIG'!! >
From: "Kenneth Porter" <shiva at well dot com>
Date: Thu, 06 Sep 2001 16:56:08 -0700
Subject: Re: create new user in qpopper
On Thu, 06 Sep 2001 14:10:51 +0200, Alexander Pubanz wrote:
>could anyone send me a link where it is described, how I can create a new
>user in qpopper 4.0 ?
>Or if you got a faq or howto I would really appreciate if you could send it
>to me.
Qpopper uses the native users supplied by the OS. Just add an OS user
and you'll have a qpopper user. If you use APOP for POP3 passwords,
you'll need to run popauth to add that password to the APOP password
file.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Date: Thu, 6 Sep 2001 19:15:13 -0700
From: Randall Gellens <randy at pensive dot org>
Subject: Re: Error at end of pop stream.
At 3:49 PM -0700 9/6/01, Darren Dunham wrote:
> MailServerException: Unexpected response to command "QUIT" from POP
> server: -ERR maillock error 'Other lock error' (5) on
> '/var/mail/.dbuser.pop': No such file or directory (2)
Qpopper is unable to lock the maildrop during the QUIT. Possibly a
lot of mail is being delivered.
Qpopper only tries four times to get the maillock during QUIT. It
may make sense to bump this up (or make it an option). As an
experiment, try changing the '4' to '30' in line 349 of
popper/pop_updt.c and see if that makes the problem go away. (You
don't want the value too large because Qmaillock() still uses sleep()
instead of doze() to wait, so it's seconds times attempt.)
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
Dimensions will always be expressed in the least usable term.
Velocity, for example, will be expressed in furlongs per fortnight.
Date: Fri, 7 Sep 2001 01:55:12 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: TLS/SSL errors
Can anyone explain whay this message is showing up?
Sep 7 01:37:11 doctor /usr/sbin/poppers[3181]: Error setting certificate PEM file
/etc/mail/certs/cert.pem
Sep 7 01:37:11 doctor /usr/sbin/poppers[3181]: ...SSL error: error:0906D06C:PEM r
outines:PEM_read_bio:no start line
Sep 7 01:37:11 doctor /usr/sbin/poppers[3181]: ...SSL error: error:140AD009:SSL r
outines:SSL_CTX_use_certificate_file:missing asn1 eos
Sep 7 01:37:11 doctor /usr/sbin/poppers[3181]: Failed initializing TLS/SSL
Cert not provided.
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 07 Sep 2001 01:15:43 -0700
Subject: Re: TLS/SSL errors
On Fri, 7 Sep 2001 01:55:12 -0600, The Doctor wrote:
>Can anyone explain whay this message is showing up?
Looks like SSL doesn't like something about your .pem file. You might
want to ask the SSL people.
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
From: "Mark J. de Jong" <dejongm at secdog dot com>
Subject: CA root certificates
Date: Fri, 7 Sep 2001 08:43:14 -0400
Hello,
I am having a problem with the certificates used with qpopper. We got it
through Equifax but for some reason our mail clients will not accept it as
being a trusted cert. Equifax supplied us with their own CAroot certificate
and we believe the problem is that qpopper doesn't know where to find it or
that it even exists. Is there an attribute that can be set in qpopper to
assign a CAroot certificate?? The cert that we are currently using works
fine in Apache so the cert is not the problem. Any advice would be
appreciated!!
Thanks,
Mark de Jong
From: Darren Dunham <ddunham at taos dot com>
Subject: Re: Error at end of pop stream.
Date: Fri, 7 Sep 2001 08:44:02 -0700 (PDT)
> > MailServerException: Unexpected response to command "QUIT" from POP
> > server: -ERR maillock error 'Other lock error' (5) on
> > '/var/mail/.dbuser.pop': No such file or directory (2)
>
> Qpopper is unable to lock the maildrop during the QUIT. Possibly a
> lot of mail is being delivered.
Maybe. I'm more worried that to me the message is saying that it can't
lock it because the file is no longer present.
It all my testing (when I can't reproduce the problem) the .dbuser.pop
file remains until the end of the session. In this case, it looks like
the file is gone.
The user can't log in, so I know they're not responsible for it. It
doesn't happen often enough for me to be able to truss all the qpopper
processes into log files and parse them.
I was just wondering if anyone had seen something like this before. For
now, I'm planning on turning off server mode and seeing if the problem
goes away.
Thanks.
--
Darren Dunham ddunham at taos dot com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< How are you gentlemen!! Take off every '.SIG'!! >
Date: Fri, 7 Sep 2001 09:50:42 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: TLS/SSL errors
On Fri, Sep 07, 2001 at 01:15:43AM -0700, Kenneth Porter wrote:
> On Fri, 7 Sep 2001 01:55:12 -0600, The Doctor wrote:
>
> >Can anyone explain whay this message is showing up?
>
> Looks like SSL doesn't like something about your .pem file. You might
> want to ask the SSL people.
>
http://www.sendmail.org/~ca/email/other/cagrag.html has the answer.
Next, I still am trying to set up the config files in /etc/mail/pop properly.
Page 51 should be more EXPLICITLY clear of the Qpopper Manual.
Pointers needed!
From: "Kenneth Porter" <shiva at well dot com>
Date: Fri, 07 Sep 2001 17:00:15 -0700
Subject: Re: TLS/SSL errors
On Fri, 7 Sep 2001 09:50:42 -0600, The Doctor wrote:
>http://www.sendmail.org/~ca/email/other/cagrag.html has the answer.
I'm getting a 404 on that link. How did you find it?
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Date: Sat, 8 Sep 2001 07:43:13 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: TLS/SSL errors
On Fri, Sep 07, 2001 at 05:00:15PM -0700, Kenneth Porter wrote:
> On Fri, 7 Sep 2001 09:50:42 -0600, The Doctor wrote:
>
> >http://www.sendmail.org/~ca/email/other/cagrag.html has the answer.
>
> I'm getting a 404 on that link. How did you find it?
>
http://www.sendmail.org/~ca/email/other/cagreg.html
is correct.
How did I get there?
Go to http://www.sendmail.org
Click on Tips and Hints
That gets you to http://www.sendmail.org/tips/
Then go to SMTP STARTTLS
That gets you to http://www.sendmail.org/~ca/email/starttls.html
Finally, click on Gregory Neil Shapiro and you are there.
I did finally get pooper to work securely on 110, but thanks to Netscape,
I think I am going to need to keep 110 unsecure and make 995 secure.
How did I do that and PLEASE no Read The Manual responses.
I NEEED LIVE examples below.
> Ken
> mailto:shiva at well dot com
> http://www.sewingwitch.com/ken/
> [If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
>
>
Unfortunately, mutt just reply-to you and cc the group.
From: "Katsumi J. Saitoh" <jsaitoh at ntti.net dot sg>
Subject: Separate machines
Date: Mon, 10 Sep 2001 12:57:38 +0800
This is a multi-part message in MIME format.
------=_NextPart_000_006B_01C139F8.2B526FA0
Content-Type: text/plain;
charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
The setup I currently have is as follows:
Server 1: qpopper with libdrac.a (RedHat 6.2)
Server 2: postfix with libdrac.a (RedHat 6.2)
I compiled qpopper with --with-drac, and ran popper -D (ip address of
the postfix machine) and get a "dracauth Server Returned permission
denied" error in my /var/log/maillog file. Are there anyone who
successfully configured a setup with POP and SMTP services on separate
machines using drac for POP-Before-SMTP? If anyone has any insight as
to what I am doing wrong, please advice me of how to fix/find
documentation to do this.
Thank you in advance,
Katsumi J. Saitoh
------=_NextPart_000_006B_01C139F8.2B526FA0
Content-Type: text/html;
charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=iso-2022-jp">
<META content="MSHTML 5.50.4616.200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>The setup I currently have is as
follows:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Server 1: qpopper with libdrac.a
(RedHat
6.2)</FONT></DIV>
<DIV><FONT face=Arial size=2>Server 2: postfix with libdrac.a
(RedHat
6.2)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I compiled qpopper with --with-drac,
and ran popper
-D (ip address of the postfix machine) and get a "dracauth Server
Returned
permission denied" error in my /var/log/maillog file. Are there
anyone who
successfully configured a setup with POP and SMTP services on separate
machines
using drac for POP-Before-SMTP? If anyone has any insight as to
what I am
doing wrong, please advice me of how to fix/find documentation to do
this.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thank you in advance,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Katsumi J. Saitoh</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_006B_01C139F8.2B526FA0--
From: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 10 Sep 2001 22:10:46 -0700
Subject: Qpopper and DRAC on separate machines
On Mon, 10 Sep 2001 12:57:38 +0800, Katsumi J. Saitoh wrote:
>I compiled qpopper with --with-drac, and ran popper -D (ip address of the postfix machine) and get a "dracauth Server Returned permission denied" error in my /var/log/maillog file. Are there anyone who successfully configured a setup with POP and SMT
ervices on separate machines using drac for POP-Before-SMTP? If anyone has any insight as to what I am doing wrong, please advice me of how to fix/find documentation to do this.
Sounds like the drac server is rejecting the connection from qpopper.
Make sure the drac/postfix server is configured to allow connections
from your qpopper machine. You should have a file somewhere that drac
consults to determine which hosts are allowed to connect to it to
submit new db entries. (On my system, it's /etc/mail/dracd.allow.)
Ken
mailto:shiva at well dot com
http://www.sewingwitch.com/ken/
[If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
Subject: Configuration for standalone operation on port 110 AND 995
From: Debian User <eneal at bnbtv dot com>
Date: 11 Sep 2001 21:32:49 -0400
Hello colleagues,
Before I ask you gentlemen my question, let me first say that I HAVE
READ the qpopper manual, searched these archives and searched on my
favourite search engines for the answer to my question. My results were
not helpful.
I am trying to enable qpopper to listen on both ports 110 for apop auth
and 995 for ssl/tls. I have read the manual and tried to initiate the
daemons using the three config files, but that didnt work. IT will ONLY
listen on port 110 and either do apop OR ssl. It will not do both. I am
not using tcpwrappers (inetd). My server is operating in standalone
mode, so I am asking you fine people that subscribe to this list for
help. How do I tell the server to listen to both ports. And please be
specific and verbose. I don't mean to sound demanding, but I have done
my due dilligence in searching this matter out and have gotten nothing
but more frustration in return for my efforts.
Thanks in advance.
Errol Neal
Date: Tue, 11 Sep 2001 19:49:25 -0600
From: The Doctor <doctor at doctor.nl2k.ab dot ca>
Subject: Re: Configuration for standalone operation on port 110 AND 995
On Tue, Sep 11, 2001 at 09:32:49PM -0400, Debian User wrote:
> Hello colleagues,
>
> Before I ask you gentlemen my question, let me first say that I HAVE
> READ the qpopper manual, searched these archives and searched on my
> favourite search engines for the answer to my question. My results were
> not helpful.
>
> I am trying to enable qpopper to listen on both ports 110 for apop auth
> and 995 for ssl/tls. I have read the manual and tried to initiate the
> daemons using the three config files, but that didnt work. IT will ONLY
> listen on port 110 and either do apop OR ssl. It will not do both. I am
> not using tcpwrappers (inetd). My server is operating in standalone
> mode, so I am asking you fine people that subscribe to this list for
> help. How do I tell the server to listen to both ports. And please be
> specific and verbose. I don't mean to sound demanding, but I have done
> my due dilligence in searching this matter out and have gotten nothing
> but more frustration in return for my efforts.
>
> Thanks in advance.
>
> Errol Neal
>
>
/path/to/poppers port -f configfile.
Date: Tue, 11 Sep 2001 16:21:48 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Configuration for standalone operation on port 110 AND 995
On Tue, Sep 11, 2001 at 09:32:49PM -0400, Debian User wrote:
> Hello colleagues,
>
> Before I ask you gentlemen my question, let me first say that I HAVE
> READ the qpopper manual, searched these archives and searched on my
> favourite search engines for the answer to my question. My results were
> not helpful.
>
> I am trying to enable qpopper to listen on both ports 110 for apop auth
> and 995 for ssl/tls. I have read the manual and tried to initiate the
> daemons using the three config files, but that didnt work. IT will ONLY
> listen on port 110 and either do apop OR ssl. It will not do both. I am
> not using tcpwrappers (inetd).
This makes it a little more complicated. You're sure you don't want to
do it from xinetd or inetd?
The reason is very practical: that's the way most people run it, so if
you want specific advice with real examples, those are the kind you are
most likely to get.
> My server is operating in standalone
> mode, so I am asking you fine people that subscribe to this list for
> help. How do I tell the server to listen to both ports.
You need to run two different instances of the server in standalone,
with totally different configurations, loaded from the command line via
"-f /path/to/configfile". Start one instance of the server configured
via its config file to listen on port 110 and use apop; start a
different one to listen on port 995 for SSL. BTW, you normally
wouldn't want to do TLS on a different port number than 110, because if
the client's configured for the non-standard port you would expect it
to also be configured for SSL; so you might as well set the port 995
one to use SSL exclusively.
Since I don't run it standalone, this info is all based on a purely
theoretical understanding of how it should work.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Nuno Teixeira" <nuno.mailinglists at pt-quorum dot com>
Subject: qpopper logs: syslog vs other log
Date: Wed, 12 Sep 2001 17:30:36 +0100
Hello to all,
I have qpopper confugured in this way:
---
[inetd.conf]
pop3 stream tcp nowait.400 root /usr/local/libexec/qpopper
qpopper -s -l 0
pop3s stream tcp nowait.400 root /usr/local/libexec/qpopper
qpopper -f /usr/local/etc/qpopper.conf
[qpopper.conf]
set statistics
set tls-support = alternate-port
set tls-server-cert-file = /usr/local/etc/certs/cert.pem
---
And it works perfectly.
With this configuration, all logs are recorded in /var/log/messages.
I'd like to know how to log to other file.
I've read the qpopper pdf but I didn't see how to do it.
Thanks very much,
Nuno Teixeira
Date: Wed, 12 Sep 2001 10:27:42 -0700
From: Chuck Yerkes <chuck+qpopper at yerkes dot com>
Subject: Re: qpopper logs: syslog vs other log
It doesn't log to /var/log/messages. It logs to syslog.
syslogd sends it to /var/log/messages.
You can compile qpopper to use whatever syslog facility
you want, but you must also configure syslogd (via syslog.conf).
Please approach THAT to solve your problem.
Quoting Nuno Teixeira (nuno.mailinglists at pt-quorum dot com):
> Hello to all,
>
> I have qpopper confugured in this way:
>
> ---
> [inetd.conf]
> pop3 stream tcp nowait.400 root /usr/local/libexec/qpopper
> qpopper -s -l 0
> pop3s stream tcp nowait.400 root /usr/local/libexec/qpopper
> qpopper -f /usr/local/etc/qpopper.conf
>
> [qpopper.conf]
> set statistics
> set tls-support = alternate-port
> set tls-server-cert-file = /usr/local/etc/certs/cert.pem
> ---
>
> And it works perfectly.
>
> With this configuration, all logs are recorded in /var/log/messages.
>
> I'd like to know how to log to other file.
> I've read the qpopper pdf but I didn't see how to do it.
>
>
> Thanks very much,
>
> Nuno Teixeira
>
>
Date: Wed, 12 Sep 2001 10:44:40 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Error at end of pop stream.
On Fri, Sep 07, 2001 at 08:44:02AM -0700, Darren Dunham wrote:
> > Qpopper is unable to lock the maildrop during the QUIT. Possibly a
> > lot of mail is being delivered.
>
> Maybe. I'm more worried that to me the message is saying that it can't
> lock it because the file is no longer present.
>
> It all my testing (when I can't reproduce the problem) the .dbuser.pop
> file remains until the end of the session. In this case, it looks like
> the file is gone.
>
> The user can't log in, so I know they're not responsible for it. It
> doesn't happen often enough for me to be able to truss all the qpopper
> processes into log files and parse them.
>
> I was just wondering if anyone had seen something like this before. For
> now, I'm planning on turning off server mode and seeing if the problem
> goes away.
Belated followup: I haven't seen anything like this, in my experience.
Maybe you could use a tool like lsof to look for anything else which
might be processing files in the directory where your poptemp files
are?
One more possiblity - maybe the locking mechanism qpopper is using
isn't working, allowing two pop sessions to start concurrently for the
same user? See if you can tell what lock mechanism it's using, and
whether it's one that makes sense for your OS/architecture.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
Date: Wed, 12 Sep 2001 14:06:52 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: qpopper logs: syslog vs other log
At 10:27 AM -0700 9/12/01, Chuck Yerkes wrote:
>You can compile qpopper to use whatever syslog facility
>you want
You can set this at run-time using the 'log-facility' option.
--
Date: Wed, 12 Sep 2001 14:03:57 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Configuration for standalone operation on port 110 AND 995
Run two instances of Qpopper, one that listens on port 110, and the
other on 995. Note that you can have the 110 one use both APOP and
STLS. The 995 one would do alternate-port TLS/SSL. That way modern
clients that support STLS can continue to use port 110.
--
From: Darren Dunham <ddunham at taos dot com>
Subject: What can cause these errors?
Date: Fri, 14 Sep 2001 10:25:28 -0700 (PDT)
After having some problems with some clients in 4.0, we've recompiled
and installed 3.1.2.
We're running it in debug mode and these messages are popping up
every once in a while..
Sep 13 23:40:47.109 [22366] new child for connection
Sep 13 23:40:47.109
Sep 13 23:40:47.116 [3852] forked() for new connection; pid=22366
Sep 13 23:40:47.116
Sep 13 23:40:47.597 [22366] file type of /var/mail/welcome.lock is S_IFLNK or more than 1 link
Sep 13 23:40:47.597
Sep 13 23:40:47.598 [22366] welcome at dbapp.company.com (xx.xx.xx.xx): -ERR [SYS/TEMP] maillock error 'Other lock error' (5) on '/var/mail/welcome': Bad file number (9)
Sep 13 23:40:47.598
Sep 13 23:40:57.598 [22366] exiting after Qpopper returned
Sep 13 23:40:57.598
What can cause such an error? Nothing is running on the box except for
sendmail/procmail for MTA and delivery and qpopper for pickup. Users
cannot log into the box, and I'm pretty certain that the user cannot be
logging in twice. It's actually picked up by an application that runs
on a single box, and it pops down mail from a series of mailboxes in
order.
The box is running Solaris 8, and all the filesystems are local (UFS).
The filesystem is nearly empty, both for blocks and inodes.
/dev/vx/dsk/mail 11212288 17952 11082214 1% /var/mail (blocks)
/dev/vx/dsk/mail 427 1365333 0% /var/mail (inodes)
Has anyone else seen these messages occur frequently? I can't reproduce
them at will, but the application is bombing out when it does occur, and
I get the above message in the debug file.
--
Darren Dunham ddunham at taos dot com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< How are you gentlemen!! Take off every '.SIG'!! >
Date: Fri, 14 Sep 2001 08:19:58 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: What can cause these errors?
On Fri, Sep 14, 2001 at 10:25:28AM -0700, Darren Dunham wrote:
> After having some problems with some clients in 4.0, we've recompiled
> and installed 3.1.2.
>
> We're running it in debug mode and these messages are popping up
> every once in a while..
>
> Sep 13 23:40:47.109 [22366] new child for connection
> Sep 13 23:40:47.109
> Sep 13 23:40:47.116 [3852] forked() for new connection; pid=22366
> Sep 13 23:40:47.116
> Sep 13 23:40:47.597 [22366] file type of /var/mail/welcome.lock is S_IFLNK or more than 1 link
> Sep 13 23:40:47.597
> Sep 13 23:40:47.598 [22366] welcome at dbapp.company.com (xx.xx.xx.xx): -ERR [SYS/TEMP] maillock error 'Other lock error' (5) on '/var/mail/welcome': Bad file number (9)
> Sep 13 23:40:47.598
> Sep 13 23:40:57.598 [22366] exiting after Qpopper returned
> Sep 13 23:40:57.598
>
> What can cause such an error?
Sounds to me like a different locking scheme between the MTA and
qpopper since you rebuilt it. I think normally you would indeed not
want to see links on the lock file (though some locking schemes work
that way.) It's a good thing that popper uses some sanity checks on the
lock or you'd be getting seriously corrupted mail spools.
Which 4.0 were you running?
The first versions had compatibility problems with some clients, but
4.0.3 seems to have no compatibility problems with anything our
customers run, which includes not just Mac and Windows, but Linux,
PDAs, old systems like Windows 3.1, pretty much you name it. (Of
course someone will now pop up and give a whole list of clients they've
had compatibility troubles with. Such is life.)
Nothing is running on the box except for
> sendmail/procmail for MTA and delivery and qpopper for pickup. Users
> cannot log into the box, and I'm pretty certain that the user cannot be
> logging in twice. It's actually picked up by an application that runs
> on a single box, and it pops down mail from a series of mailboxes in
> order.
>
> The box is running Solaris 8, and all the filesystems are local (UFS).
> The filesystem is nearly empty, both for blocks and inodes.
> /dev/vx/dsk/mail 11212288 17952 11082214 1% /var/mail (blocks)
> /dev/vx/dsk/mail 427 1365333 0% /var/mail (inodes)
>
> Has anyone else seen these messages occur frequently? I can't reproduce
> them at will, but the application is bombing out when it does occur, and
> I get the above message in the debug file.
BTW, thank you for including a lot of relevant info in your post. Us
mailing list types appreciate having enough info to make a relevant
guess.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Michael Kolos" <michael at colba dot net>
Subject: Re: What can cause these errors?
Date: Fri, 14 Sep 2001 14:29:31 -0400
----- Original Message -----
From: "Clifton Royston" <cliftonr at lava dot net>
To: "Darren Dunham" <ddunham at taos dot com>
Cc: "Subscribers of Qpopper" <qpopper at lists.pensive dot org>
Sent: Friday, September 14, 2001 2:19 PM
Subject: Re: What can cause these errors?
>
> Sounds to me like a different locking scheme between the MTA and
> qpopper since you rebuilt it. I think normally you would indeed not
> want to see links on the lock file (though some locking schemes work
> that way.) It's a good thing that popper uses some sanity checks on the
> lock or you'd be getting seriously corrupted mail spools.
>
> Which 4.0 were you running?
>
> The first versions had compatibility problems with some clients, but
> 4.0.3 seems to have no compatibility problems with anything our
> customers run, which includes not just Mac and Windows, but Linux,
> PDAs, old systems like Windows 3.1, pretty much you name it. (Of
> course someone will now pop up and give a whole list of clients they've
> had compatibility troubles with. Such is life.)
>
Since you asked for it...
Ironically, we seem to only have problems with Eudora users...
Michael Kolos
Administrateur de Réseaux
Network Administrator
ColbaNet Inc
Date: Fri, 14 Sep 2001 15:53:26 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: What can cause these errors?
At 2:29 PM -0400 9/14/01, Michael Kolos wrote:
>Ironically, we seem to only have problems with Eudora users...
What problems did you have?
--
From: "Alex M" <alex at myzona dot net>
Subject: hiding version
Date: Sun, 16 Sep 2001 13:48:54 -0700
Hello all,
Being a little security paranoic about my system, I tend to hide versions of
my services, But havent found a way of hiding the qpopper version display
upon telneting to port 110. Perhaps anybody know of a way, other than
hacking the source code and recompiling? :)
Thanks.
From: Frank Pineau <frank at pineaus dot com>
Subject: Re: hiding version
Date: Sun, 16 Sep 2001 16:14:25 -0500
It's in the manual. Use the --enable-shy configuration option.
=46P
On Sun, 16 Sep 2001 13:48:54 -0700, you wrote:
>Hello all,
>
>Being a little security paranoic about my system, I tend to hide
versions of
>my services, But havent found a way of hiding the qpopper version
display
>upon telneting to port 110. Perhaps anybody know of a way, other than
>hacking the source code and recompiling? :)
>
>Thanks.
--
<*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*>
=46rank Pineau ------------>
frank at pineaus.IHATESPAM dot com
http://www.pineaus.com
It is pitch black. You are likely to be eaten by a grue.
<*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*>
PGP Public Key:
http://www.pineaus.com/frankpineau.asc
No mail from free e-mail systems such as Hotmail
or Yahoo will be accepted.
From: "Michael Kolos" <michael at colba dot net>
Subject: Re: What can cause these errors?
Date: Mon, 17 Sep 2001 09:53:46 -0400
----- Original Message -----
From: "Randall Gellens" <randy at qualcomm dot com>
To: "Michael Kolos" <michael at colba dot net>; "Subscribers of Qpopper"
<qpopper at lists.pensive dot org>
Sent: Friday, September 14, 2001 6:53 PM
Subject: Re: What can cause these errors?
> At 2:29 PM -0400 9/14/01, Michael Kolos wrote:
>
> >Ironically, we seem to only have problems with Eudora users...
>
> What problems did you have?
> --
>
We tend to get a lot of "I/O error flushing output to client... Operation
not permitted"
with Eudora clients mostly.
Those are really the only problems we have with qpopper (version 4.0.3, and
I've added chunky-writes=never and timeout=600 to the config file, which
hasn't helped)
I run the standalone version.
Michael Kolos
Administrateur de Réseaux
Network Administrator
ColbaNet Inc
Date: Mon, 17 Sep 2001 10:08:12 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: hiding version
At 4:14 PM -0500 9/16/01, Frank Pineau wrote:
> It's in the manual. Use the --enable-shy configuration option.
You can also set or reset it at run-time using 'set shy'. No need to
recompile.
Date: Tue, 18 Sep 2001 10:30:02 +0200
From: "Ruggero Dell'Osso" <dellosso at agr.unipi dot it>
Subject: acker attack?
Hi,
I am testing qpopper 4.0.3 on redhat 7.1 system and I am the only user of
the server. I have a sospicious connection to the pop port. Someone can
help me to understand what means? Qpopper is vulnerable to acker attack?
These are the lines founded in /var/log/maillog
Sep 16 00:41:16 s2 popper[7239]: (null) at pD95410DD.dip.t-dialin.net
(217.84.16.221): -ERR POP EOF or I/O Error [popper.c:794]
Sep 16 00:41:16 s2 popper[7239]: I/O error flushing output to client at
pD95410DD.dip.t-dialin.net [217.84.16.221]: Operation not permitted (1)
[pop_send.c:685]
Sep 16 00:41:16 s2 popper[7239]: I/O error flushing output to client at
pD95410DD.dip.t-dialin.net [217.84.16.221]: Operation not permitted (1)
[pop_send.c:685]
Sep 16 00:41:16 s2 popper[7239]: (v4.0.3) Timing for
@pD95410DD.dip.t-dialin.net (error) auth=0 init=0 clean=0 [popper.c:375]
Sep 16 00:41:16 s2 sendmail[7238]: NOQUEUE: pD95410DD.dip.t-dialin.net
[217.84.16.221] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA
tank you
Ruggero
Date: Tue, 18 Sep 2001 21:15:48 +1000
From: Wayne Heming <wheming at hemnet.com dot au>
Subject: Re: acker attack?
I don't know about you but I have many "Hacker" intrusions from the
"t-dialin.net" domain, so many that every time I receive a hack alert, not
just popper, I add a filter to my firewall to drop their packets.
I have seen probes on just about every TCP and UDP port.
I think you will find that the intruder is trying to use popper to relay
mail. (Maybe)
Wayne
At 10:30 AM 18-09-01 +0200, Ruggero Dell'Osso wrote:
>Hi,
>I am testing qpopper 4.0.3 on redhat 7.1 system and I am the only user of
>the server. I have a sospicious connection to the pop port. Someone can
>help me to understand what means? Qpopper is vulnerable to acker attack?
>These are the lines founded in /var/log/maillog
>
>Sep 16 00:41:16 s2 popper[7239]: (null) at pD95410DD.dip.t-dialin.net
>(217.84.16.221): -ERR POP EOF or I/O Error [popper.c:794]
>Sep 16 00:41:16 s2 popper[7239]: I/O error flushing output to client at
>pD95410DD.dip.t-dialin.net [217.84.16.221]: Operation not permitted (1)
>[pop_send.c:685]
>Sep 16 00:41:16 s2 popper[7239]: I/O error flushing output to client at
>pD95410DD.dip.t-dialin.net [217.84.16.221]: Operation not permitted (1)
>[pop_send.c:685]
>Sep 16 00:41:16 s2 popper[7239]: (v4.0.3) Timing for
>@pD95410DD.dip.t-dialin.net (error) auth=0 init=0 clean=0 [popper.c:375]
>Sep 16 00:41:16 s2 sendmail[7238]: NOQUEUE: pD95410DD.dip.t-dialin.net
>[217.84.16.221] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA
>
>tank you
>
>Ruggero
>
From: Ben Lormis <Ben.Lormis at dig dot com>
Subject: Anybody using an account other than root to run qpopper?
Date: Tue, 18 Sep 2001 08:34:54 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C14057.76C096F0
Content-Type: text/plain;
charset="iso-8859-1"
I'm curious as to whether anybody is using an account other than root to run
qpopper 4.0.3 on unix and if so what permission changes have to be made.
Thanks,
Ben
------_=_NextPart_001_01C14057.76C096F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version
5.5.2654.45">
<TITLE>Anybody using an account other than root to run qpopper?</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2 FACE="Arial">I'm curious as to whether anybody is
using an account other than root to run qpopper 4.0.3 on unix and if so
what permission changes have to be made.</FONT></P>
<BR>
<P><FONT SIZE=2 FACE="Arial">Thanks,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Ben</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C14057.76C096F0--
Date: Tue, 18 Sep 2001 15:36:17 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: acker attack?
At 9:15 PM +1000 9/18/01, Wayne Heming wrote:
>I think you will find that the intruder is trying to use popper to
>relay mail. (Maybe)
They can't relay mail without a valid account, and even then only
with XTND XMIT. Perhaps they are just probing for buffer overflows.
There are none known in Qpopper 4.0.3. I have a utility that tries
every parameter of every command for buffer overflows, and it hasn't
found any.
--
Date: Tue, 18 Sep 2001 15:34:29 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: acker attack?
At 10:30 AM +0200 9/18/01, Ruggero Dell'Osso wrote:
>I have a sospicious connection to the pop port. Someone can help me
>to understand what means? Qpopper is vulnerable to acker attack?
Qpopper is not vulnerable. People can try, of course, unless you
block access, but they won't get anywhere.
--
Date: Tue, 18 Sep 2001 15:38:17 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Anybody using an account other than root to run qpopper?
At 8:34 AM -0700 9/18/01, Ben Lormis wrote:
>I'm curious as to whether anybody is using an account other than
>root to run qpopper 4.0.3 on unix and if so what permission changes
>have to be made.
Qpopper only uses root to authenticate the user, after which it
permanently drops privileges. It would probably be possible to run
under a different user in conjunction with PAM authentication, but I
haven't tried it.
--
Date: Thu, 20 Sep 2001 18:37:47 -0500 (CDT)
From: <chandler at grendel.stranded dot org>
Subject: -ERR [SYS/TEMP] Unable to get spool name
This is the error I get when trying to connect to the pop3 port. I tried
to search the archives, but they don't seem to be working at the moment.
I imagine this error is a result of qpoppers inability to find
/home/$/Mailbox for mail delivery, but I'm at a total loss on how to go
about fixing it.
Can someone point me in the right way?
Thanks for your time.
Date: Sat, 22 Sep 2001 13:01:20 -0400 (EDT)
From: Homer Wilson Smith <homer at lightlink dot com>
Subject: What does this mean
CUstomer trying to read mail from our servers in the US from
China, 61.154.233.13
Can't read mail, getting following errors.
What does it mean?
Thanks Homer
Sep 22 12:14:38 mx popper[30638]: (v4.0.3) POP login by user "bv" at (61.154.233.13) 61.154.233.13
Sep 22 12:14:46 mx popper[30638]: bv at 61.154.233.13 (61.154.233.13): -ERR POP EOF or I/O Error
Sep 22 12:14:46 mx popper[30638]: I/O error flushing output to client bv at 61.154.233.13 [61.154.233.13]: Operation not permitted (1)
Sep 22 12:14:46 mx popper[30638]: Stats: bv 0 0 393 3428088 61.154.233.13 61.154.233.13
Sep 22 12:14:48 mx popper[30638]: I/O error flushing output to client bv at 61.154.233.13 [61.154.233.13]: Operation not permitted (1)
Sep 22 12:28:30 mx popper[1253]: (v4.0.3) POP login by user "bv" at (61.154.237.205) 61.154.237.205
Sep 22 12:28:36 mx popper[1253]: bv at 61.154.237.205 (61.154.237.205): -ERR POP EOF or I/O Error
Sep 22 12:28:36 mx popper[1253]: I/O error flushing output to client bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
Sep 22 12:28:36 mx popper[1253]: Stats: bv 0 0 394 3429212 61.154.237.205 61.154.237.205
Sep 22 12:28:37 mx popper[1253]: I/O error flushing output to client bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
Sep 22 12:29:05 mx popper[1401]: (v4.0.3) POP login by user "bv" at (61.154.237.205) 61.154.237.205
Sep 22 12:29:10 mx popper[1401]: bv at 61.154.237.205 (61.154.237.205): -ERR POP EOF or I/O Error
Sep 22 12:29:10 mx popper[1401]: I/O error flushing output to client bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
Sep 22 12:29:10 mx popper[1401]: Stats: bv 0 0 394 3429222 61.154.237.205 61.154.237.205
Sep 22 12:29:10 mx popper[1401]: I/O error flushing output to client bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
Sep 22 12:30:46 mx popper[1822]: (v4.0.3) POP login by user "bv" at (61.154.236.157) 61.154.236.157
Sep 22 12:31:00 mx popper[1822]: bv at 61.154.236.157 (61.154.236.157): -ERR POP EOF or I/O Error
Sep 22 12:31:00 mx popper[1822]: I/O error flushing output to client bv at 61.154.236.157 [61.154.236.157]: Operation not permitted (1)
Sep 22 12:31:00 mx popper[1822]: Stats: bv 0 0 394 3429222 61.154.236.157 61.154.236.157
Sep 22 12:31:00 mx popper[1822]: I/O error flushing output to client bv at 61.154.236.157 [61.154.236.157]: Operation not permitted (1)
Sep 22 12:35:06 mx popper[6163]: (v4.0.3) POP login by user "bv" at (61.154.237.133) 61.154.237.133
Sep 22 12:35:14 mx popper[6163]: bv at 61.154.237.133 (61.154.237.133): -ERR POP EOF or I/O Error
Sep 22 12:35:14 mx popper[6163]: I/O error flushing output to client bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
Sep 22 12:35:14 mx popper[6163]: Stats: bv 0 0 396 3435089 61.154.237.133 61.154.237.133
Sep 22 12:35:15 mx popper[6163]: I/O error flushing output to client bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
Sep 22 12:42:57 mx popper[11778]: (v4.0.3) POP login by user "bv" at (61.154.237.133) 61.154.237.133
Sep 22 12:43:03 mx popper[11778]: bv at 61.154.237.133 (61.154.237.133): -ERR POP EOF or I/O Error
Sep 22 12:43:03 mx popper[11778]: I/O error flushing output to client bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
Sep 22 12:43:03 mx popper[11778]: Stats: bv 0 0 396 3435109 61.154.237.133 61.154.237.133
Sep 22 12:43:03 mx popper[11778]: I/O error flushing output to client bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
Sep 22 12:48:27 mx popper[13242]: (v4.0.3) POP login by user "bv" at (gem.lightlink.com) 205.232.34.13
Sep 22 12:48:27 mx popper[13242]: bv at gem.lightlink.com (205.232.34.13): -ERR POP EOF or I/O Error
Sep 22 12:48:27 mx popper[13242]: Stats: bv 0 0 396 3435109 gem.lightlink.com 205.232.34.13
Sep 22 12:48:27 mx popper[13242]: I/O error flushing output to client bv at gem.lightlink.com [205.232.34.13]: Operation not permitted (1)
Sep 22 12:49:15 mx popper[13488]: (v4.0.3) POP login by user "bv" at (gem.lightlink.com) 205.232.34.13
Sep 22 12:49:15 mx popper[13488]: bv at gem.lightlink.com (205.232.34.13): -ERR POP EOF or I/O Error
Sep 22 12:49:15 mx popper[13488]: Stats: bv 0 0 396 3435109 gem.lightlink.com 205.232.34.13
Sep 22 12:49:15 mx popper[13488]: I/O error flushing output to client bv at gem.lightlink.com [205.232.34.13]: Operation not permitted (1)
Sep 22 12:49:18 mx popper[13491]: (v4.0.3) POP login by user "bv" at (gem.lightlink.com) 205.232.34.13
Sep 22 12:49:18 mx popper[13491]: bv at gem.lightlink.com (205.232.34.13): -ERR POP EOF or I/O Error
Sep 22 12:49:18 mx popper[13491]: Stats: bv 0 0 396 3435109 gem.lightlink.com 205.232.34.13
Sep 22 12:49:18 mx popper[13491]: I/O error flushing output to client bv at gem.lightlink.com [205.232.34.13]: Operation not permitted (1)
Sep 22 12:53:14 mx popper[14722]: (v4.0.3) POP login by user "bv" at (gem.lightlink.com) 205.232.34.13
Sep 22 12:53:14 mx popper[14722]: bv at gem.lightlink.com (205.232.34.13): -ERR POP EOF or I/O Error
Sep 22 12:53:14 mx popper[14722]: Stats: bv 0 0 396 3435109 gem.lightlink.com 205.232.34.13
Sep 22 12:53:14 mx popper[14722]: I/O error flushing output to client bv at gem.lightlink.com [205.232.34.13]: Operation not permitted (1)
Sep 22 12:53:15 mx popper[14727]: (v4.0.3) POP login by user "bv" at (gem.lightlink.com) 205.232.34.13
Sep 22 12:53:15 mx popper[14727]: Stats: bv 0 0 396 3435109 gem.lightlink.com 205.232.34.13
------------------------------------------------------------------------
Homer Wilson Smith Clean Air, Clear Water, Art Matrix - Lightlink
(607) 277-0959 A Green Earth and Peace. Internet Access, Ithaca NY
homer at lightlink.com Is that too much to ask? http://www.lightlink dot com
From: Qpopper Mailing List <popper at iggy.triode.net dot au>
Subject: User Disconnect, Popper keeps running for a long time afterwards
Date: Sun, 23 Sep 2001 16:45:49 +1000 (EST)
I'm a small ISP running Redhat Linux 6.2. I've had a longstanding problem
when if a user is downloading their email via modem and then the modem
drops out before then dowload is finished, then a popper process is
left running. These popper processes could stay around for two hours or more.
When the user logs back in to tries and get there email again they get
a POP Lock Busy error message. This confuses and frustrates them no end.
I'm running Linux Kernel 2.4.0 and qpopper 4.0.3. I've done a bit of
debugging and found that the qpopper was waiting on the fflush call
in pop_write_flush function in file pop_send.c. I made a quick hack
to see if I could fix the problem. I put an alarm before the
fflush and reset it after the fflush. This fix seems to work quite nicely.
I've got a couple of questions which come from my testing:
1) Is Linux unique in being able to hang on an fflush where
the guy on the other end has been dropped out?
2) Has this situation been tested on other Unixes? Do they
have this problem of hanging as well.
3) How does Linux determine how long does the fflush call
wait for when the other end has disconnected?
If its agreed that my fix is a reasonable one I will be happy to
write up a full patch to fix this problem.
Regards. Paul (paulb at triode.net dot au)
Date: Mon, 24 Sep 2001 11:27:54 +0100
From: peter.allen at moon-light.co dot uk
Subject: Re: -ERR [SYS/TEMP] Unable to get spool name
Did you compile using --enable-home-dir-mail=Mailbox ? There is a section
in the INSTALL file called HOMEDIRMAIL which explains it.
I have a feeling that you may have a small error of syntax, especially as
it is unlikely that /home/$/Mailbox is what I guess you want.
HTH
Peter
At 18:37 20/09/01 -0500, chandler at grendel.stranded dot org wrote:
>This is the error I get when trying to connect to the pop3 port. I tried
>to search the archives, but they don't seem to be working at the moment.
>
>I imagine this error is a result of qpoppers inability to find
>/home/$/Mailbox for mail delivery, but I'm at a total loss on how to go
>about fixing it.
>
>Can someone point me in the right way?
>
>Thanks for your time.
Date: Mon, 24 Sep 2001 15:15:01 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: What does this mean
At 1:01 PM -0400 9/22/01, Homer Wilson Smith wrote:
> CUstomer trying to read mail from our servers in the US from
>China, 61.154.233.13
>
> Can't read mail, getting following errors.
>
> What does it mean?
It looks to me like the user can't maintain a connection. Can the
user use any other services besides POP (for example, can he or she
access your web pages or send mail through your SMTP server?)
>
> Thanks Homer
>
>Sep 22 12:14:38 mx popper[30638]: (v4.0.3) POP login by user "bv" at
>(61.154.233.13) 61.154.233.13
>Sep 22 12:14:46 mx popper[30638]: bv at 61.154.233.13
>(61.154.233.13): -ERR POP EOF or I/O Error
>Sep 22 12:14:46 mx popper[30638]: I/O error flushing output to
>client bv at 61.154.233.13 [61.154.233.13]: Operation not permitted
>(1)
>Sep 22 12:14:46 mx popper[30638]: Stats: bv 0 0 393 3428088
>61.154.233.13 61.154.233.13
>Sep 22 12:14:48 mx popper[30638]: I/O error flushing output to
>client bv at 61.154.233.13 [61.154.233.13]: Operation not permitted
>(1)
>Sep 22 12:28:30 mx popper[1253]: (v4.0.3) POP login by user "bv" at
>(61.154.237.205) 61.154.237.205
>Sep 22 12:28:36 mx popper[1253]: bv at 61.154.237.205
>(61.154.237.205): -ERR POP EOF or I/O Error
>Sep 22 12:28:36 mx popper[1253]: I/O error flushing output to client
>bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
>Sep 22 12:28:36 mx popper[1253]: Stats: bv 0 0 394 3429212
>61.154.237.205 61.154.237.205
>Sep 22 12:28:37 mx popper[1253]: I/O error flushing output to client
>bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
>Sep 22 12:29:05 mx popper[1401]: (v4.0.3) POP login by user "bv" at
>(61.154.237.205) 61.154.237.205
>Sep 22 12:29:10 mx popper[1401]: bv at 61.154.237.205
>(61.154.237.205): -ERR POP EOF or I/O Error
>Sep 22 12:29:10 mx popper[1401]: I/O error flushing output to client
>bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
>Sep 22 12:29:10 mx popper[1401]: Stats: bv 0 0 394 3429222
>61.154.237.205 61.154.237.205
>Sep 22 12:29:10 mx popper[1401]: I/O error flushing output to client
>bv at 61.154.237.205 [61.154.237.205]: Operation not permitted (1)
>Sep 22 12:30:46 mx popper[1822]: (v4.0.3) POP login by user "bv" at
>(61.154.236.157) 61.154.236.157
>Sep 22 12:31:00 mx popper[1822]: bv at 61.154.236.157
>(61.154.236.157): -ERR POP EOF or I/O Error
>Sep 22 12:31:00 mx popper[1822]: I/O error flushing output to client
>bv at 61.154.236.157 [61.154.236.157]: Operation not permitted (1)
>Sep 22 12:31:00 mx popper[1822]: Stats: bv 0 0 394 3429222
>61.154.236.157 61.154.236.157
>Sep 22 12:31:00 mx popper[1822]: I/O error flushing output to client
>bv at 61.154.236.157 [61.154.236.157]: Operation not permitted (1)
>Sep 22 12:35:06 mx popper[6163]: (v4.0.3) POP login by user "bv" at
>(61.154.237.133) 61.154.237.133
>Sep 22 12:35:14 mx popper[6163]: bv at 61.154.237.133
>(61.154.237.133): -ERR POP EOF or I/O Error
>Sep 22 12:35:14 mx popper[6163]: I/O error flushing output to client
>bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
>Sep 22 12:35:14 mx popper[6163]: Stats: bv 0 0 396 3435089
>61.154.237.133 61.154.237.133
>Sep 22 12:35:15 mx popper[6163]: I/O error flushing output to client
>bv at 61.154.237.133 [61.154.237.133]: Operation not permitted (1)
>Sep 22 12:42:57 mx popper[11778]: (v4.0.3) POP login by user "bv" at
>(61.154.237.133) 61.154.237.133
>Sep 22 12:43:03 mx popper[11778]: bv at 61.154.237.133
>(61.154.237.133): -ERR POP EOF or I/O Error
>Sep 22 12:43:03 mx popper[11778]: I/O error flushing output to
>client bv at 61.154.237.133 [61.154.237.133]: Operation not
>permitted (1)
>Sep 22 12:43:03 mx popper[11778]: Stats: bv 0 0 396 3435109
>61.154.237.133 61.154.237.133
>Sep 22 12:43:03 mx popper[11778]: I/O error flushing output to
>client bv at 61.154.237.133 [61.154.237.133]: Operation not
>permitted (1)
>Sep 22 12:48:27 mx popper[13242]: (v4.0.3) POP login by user "bv" at
>(gem.lightlink.com) 205.232.34.13
>Sep 22 12:48:27 mx popper[13242]: bv at gem.lightlink.com
>(205.232.34.13): -ERR POP EOF or I/O Error
>Sep 22 12:48:27 mx popper[13242]: Stats: bv 0 0 396 3435109
>gem.lightlink.com 205.232.34.13
>Sep 22 12:48:27 mx popper[13242]: I/O error flushing output to
>client bv at gem.lightlink.com [205.232.34.13]: Operation not
>permitted (1)
>Sep 22 12:49:15 mx popper[13488]: (v4.0.3) POP login by user "bv" at
>(gem.lightlink.com) 205.232.34.13
>Sep 22 12:49:15 mx popper[13488]: bv at gem.lightlink.com
>(205.232.34.13): -ERR POP EOF or I/O Error
>Sep 22 12:49:15 mx popper[13488]: Stats: bv 0 0 396 3435109
>gem.lightlink.com 205.232.34.13
>Sep 22 12:49:15 mx popper[13488]: I/O error flushing output to
>client bv at gem.lightlink.com [205.232.34.13]: Operation not
>permitted (1)
>Sep 22 12:49:18 mx popper[13491]: (v4.0.3) POP login by user "bv" at
>(gem.lightlink.com) 205.232.34.13
>Sep 22 12:49:18 mx popper[13491]: bv at gem.lightlink.com
>(205.232.34.13): -ERR POP EOF or I/O Error
>Sep 22 12:49:18 mx popper[13491]: Stats: bv 0 0 396 3435109
>gem.lightlink.com 205.232.34.13
>Sep 22 12:49:18 mx popper[13491]: I/O error flushing output to
>client bv at gem.lightlink.com [205.232.34.13]: Operation not
>permitted (1)
>Sep 22 12:53:14 mx popper[14722]: (v4.0.3) POP login by user "bv" at
>(gem.lightlink.com) 205.232.34.13
>Sep 22 12:53:14 mx popper[14722]: bv at gem.lightlink.com
>(205.232.34.13): -ERR POP EOF or I/O Error
>Sep 22 12:53:14 mx popper[14722]: Stats: bv 0 0 396 3435109
>gem.lightlink.com 205.232.34.13
>Sep 22 12:53:14 mx popper[14722]: I/O error flushing output to
>client bv at gem.lightlink.com [205.232.34.13]: Operation not
>permitted (1)
>Sep 22 12:53:15 mx popper[14727]: (v4.0.3) POP login by user "bv" at
>(gem.lightlink.com) 205.232.34.13
>Sep 22 12:53:15 mx popper[14727]: Stats: bv 0 0 396 3435109
>gem.lightlink.com 205.232.34.13
>
>------------------------------------------------------------------------
>Homer Wilson Smith Clean Air, Clear Water, Art Matrix - Lightlink
>(607) 277-0959 A Green Earth and Peace. Internet Access, Ithaca NY
>homer at lightlink.com Is that too much to ask? http://www.lightlink dot com
--
Subject: What's up with qpopper-announce?
From: "Dan Harkless" <qpopper at dilvish.speed dot net>
Date: Mon, 24 Sep 2001 19:46:28 -0700
So, what's the story with the qpopper-announce list? The last message I got
on it was "Qpopper LX 4.0b16 available", from February 15. I see that
qpopper 4.0 is out now. Was this not announced, or did I just not get the
mail for some reason?
It's not that I was silently unsubcribed or something, as I just
successfully unsubscribed from qpopper-announce using this email address and
re-subscribed with a different address.
It is *feasible* I got the message and it was lost, however, due to the
problem I'm about to describe in my next mail.
Before I leave the topic of qpopper-announce, though, why is it still not
mentioned in <http://www.eudora.com/qpopper/faq.html#list>? I believe I
brought this up some time in 1999 or 2000, and the reply was that it was a
known issue and should be fixed soon. How difficult is it to change the
faq.html file?
You shouldn't be coy about the existence of the -announce list for a
security-critical daemon like qpopper. Not everyone can afford the time to
keep up with the primary mailing list for a given piece of software, but no
administrator can afford *not* to subscribe to the -announce list, assuming
they know about it.
--
Dan Harkless
SpeedGate Communications, Inc.
Subject: I lose email when our server crashes due to lack of O_EXCL use
From: "Dan Harkless" <qpopper at dilvish.speed dot net>
Date: Mon, 24 Sep 2001 20:31:18 -0700
Hello. A few weeks ago I found out after the fact that an important email
someone had sent me had never gotten to me. I dismissed it at first,
thinking it must be their crappy Microsoft mail client or outgoing mail
server. Surely it couldn't be our UNIX-based mail server. ;^>
But then it happened again, and then yet again, where I failed to receive
important work emails. The three losses were from disparate senders and
domains.
Clearly the problem was on our side. I asked around and couldn't find any
other instances of people losing mail, so my mail client (nmh) was under
suspicion, but since its POP code has been pretty stable since like the
mid-1980s (!), I decided to investigate the server side first.
With a lot of log-surfing on the server, which is running qpopper 3.0.2 on
Solaris 2.5, I figured out that the two most recent mail losses coincided
with a mail server crash (unfortunately not all that rare an occurrence due
to an apparent hardware problem we have yet to figure out).
The crash didn't occur around the time of the mail delivery, so it was not
sendmail messing up here. Instead, the crashes occurred during or shortly
after POP3 number-of-messages queries by my mail-checking scripts. The
"Stats:" line in the log file before the crash showed I had messages
waiting, but the next one after the crash showed they were gone (and I know
by the timing that I was not doing any message-pulling during these
crashes).
It looks to me like what's happening is that my scripts do a POP3 connect
(which I do more often than anyone else, explaining why only _I_ have
noticed mail loss), my spool is emptied out of /var/mail/<user> into
/var/mail/.<user>.pop, the machine crashes, and then after the machine's
back up again, my spool is zero-length and the temp_drop is overwritten by
the first check.
I didn't pore through the code exhaustively, but I couldn't find any code
that would prevent this. Shouldn't there be code that would check for the
pre-existence of the temp_drop file and merge its messages back into the
spool before doing anything else??
As I understand things, the only way to prevent any possibility of
overwriting an existing temp_drop file would be to do it atomically, with
O_EXCL specified along with O_CREAT on the open() call. This is not being
done in 3.0.2, nor has this been fixed in subsequent versions. Here's line
1487 of qpopper 4.0.3's pop_dropcopy.c:
dfd = open ( p->temp_drop, O_RDWR | O_CREAT, 0660 );
This should be:
dfd = open ( p->temp_drop, O_RDWR | O_CREAT | O_EXCL, 0660 );
Even with that change alone, you'd prevent the mail loss that I'm seeing.
Ideally, though, there should also be appropriate checking of the errno and
if it's EEXIST, temp_drop's contents should be merged back into the mail
spool to prevent the mail lossage that I'm seeing.
--
Dan Harkless
SpeedGate Communications, Inc.
Date: Mon, 24 Sep 2001 21:41:52 -0700
From: Randall Gellens <randy at pensive dot org>
Subject: Re: What's up with qpopper-announce?
At 7:46 PM -0700 9/24/01, Dan Harkless wrote:
> So, what's the story with the qpopper-announce list? The last message I got
> on it was "Qpopper LX 4.0b16 available", from February 15. I see that
> qpopper 4.0 is out now. Was this not announced, or did I just not get the
> mail for some reason?
>
> It's not that I was silently unsubcribed or something, as I just
> successfully unsubscribed from qpopper-announce using this email address and
> re-subscribed with a different address.
>
> It is *feasible* I got the message and it was lost, however, due to the
> problem I'm about to describe in my next mail.
That's my guess. The announcement was sent to the -announce list:
At 6:01 PM -0700 4/12/01, Qpopper Customer Service wrote:
> To: Qpopper Public List <qpopper at lists.pensive dot org>,
> qpopper-announce at rohan.qualcomm dot com
> From: Qpopper Customer Service <qpop-custserv at qualcomm dot com>
> Subject: Qpopper 4.0 Available
>
> Before I leave the topic of qpopper-announce, though, why is it still not
> mentioned in <http://www.eudora.com/qpopper/faq.html#list>? I believe I
> brought this up some time in 1999 or 2000, and the reply was that it was a
> known issue and should be fixed soon. How difficult is it to change the
> faq.html file?
You're right that the link you cite doesn't mention the -announce
list, which is odd. It is, however, mentioned elsewhere:
<http://www.eudora.com/qpopper/faq.html#versions.notify> (It's the
link just above yours.)
--
Randall Gellens Randy at Pensive dot Org
---------------------- (randomly-selected tag) ---------------------
Where you stand depends on where you sit.
--R. Ploni
Date: Tue, 25 Sep 2001 07:08:32 +0100
From: peter.allen at moon-light.co dot uk
Subject: Re: I lose email when our server crashes due to lack of O_EXCL
Although I am not an expert on it, would this not be fixed by using qmail's
maildir functionality as outlined in
http://www.lifewithqmail.org/lwq.html#maildir-delivery ?
Peter
At 20:31 24/09/01 -0700, you wrote:
>Hello. A few weeks ago I found out after the fact that an important email
>someone had sent me had never gotten to me. I dismissed it at first,
>thinking it must be their crappy Microsoft mail client or outgoing mail
>server. Surely it couldn't be our UNIX-based mail server. ;^>
>
>But then it happened again, and then yet again, where I failed to receive
>important work emails. The three losses were from disparate senders and
>domains.
>
>Clearly the problem was on our side. I asked around and couldn't find any
>other instances of people losing mail, so my mail client (nmh) was under
>suspicion, but since its POP code has been pretty stable since like the
>mid-1980s (!), I decided to investigate the server side first.
>
>With a lot of log-surfing on the server, which is running qpopper 3.0.2 on
>Solaris 2.5, I figured out that the two most recent mail losses coincided
>with a mail server crash (unfortunately not all that rare an occurrence due
>to an apparent hardware problem we have yet to figure out).
>
>The crash didn't occur around the time of the mail delivery, so it was not
>sendmail messing up here. Instead, the crashes occurred during or shortly
>after POP3 number-of-messages queries by my mail-checking scripts. The
>"Stats:" line in the log file before the crash showed I had messages
>waiting, but the next one after the crash showed they were gone (and I know
>by the timing that I was not doing any message-pulling during these
>crashes).
>
>It looks to me like what's happening is that my scripts do a POP3 connect
>(which I do more often than anyone else, explaining why only _I_ have
>noticed mail loss), my spool is emptied out of /var/mail/<user> into
>/var/mail/.<user>.pop, the machine crashes, and then after the machine's
>back up again, my spool is zero-length and the temp_drop is overwritten by
>the first check.
>
>I didn't pore through the code exhaustively, but I couldn't find any code
>that would prevent this. Shouldn't there be code that would check for the
>pre-existence of the temp_drop file and merge its messages back into the
>spool before doing anything else??
>
>As I understand things, the only way to prevent any possibility of
>overwriting an existing temp_drop file would be to do it atomically, with
>O_EXCL specified along with O_CREAT on the open() call. This is not being
>done in 3.0.2, nor has this been fixed in subsequent versions. Here's line
>1487 of qpopper 4.0.3's pop_dropcopy.c:
>
> dfd = open ( p->temp_drop, O_RDWR | O_CREAT, 0660 );
>
>This should be:
>
> dfd = open ( p->temp_drop, O_RDWR | O_CREAT | O_EXCL, 0660 );
>
>Even with that change alone, you'd prevent the mail loss that I'm seeing.
>Ideally, though, there should also be appropriate checking of the errno and
>if it's EEXIST, temp_drop's contents should be merged back into the mail
>spool to prevent the mail lossage that I'm seeing.
>
>--
>Dan Harkless
>SpeedGate Communications, Inc.
Date: Tue, 25 Sep 2001 20:37:17 +0900
From: Peter Evans <peter at gol dot com>
Subject: Re: I lose email when our server crashes due to lack of O_EXCL use
peter.allen at moon-light.co.uk (peter.allen at moon-light dot co dot uk) wrote:
> Although I am not an expert on it, would this not be fixed by using qmail's
> maildir functionality as outlined in
> http://www.lifewithqmail.org/lwq.html#maildir-delivery ?
Not really, because then you have to teach qpopper about maildir.
Either way, he *has* outlined the problem.
"in mid pop, if the machine decides to pine for the fjords, your
mail goes poof"
I think he's using an antique popper, but if you try:
SERVERMODE
NOSTATUS
NOUPDATEONABORT
then it doesnt copy your mail to one side, and if you go poof, it
aborts any changes, it also doesnt re-write mailboxes.
this is *safer* but I would be inclined to say "fix your machine,
you have more serious problems than popper"
P
----*
--
New Snibbo! Combined Breakfast Cereal and Washing-Up Liquid!
From: =?iso-8859-1?Q?CRESTIN_Frédéric?= <fcrestin at lexsi dot com>
Subject: troubleshooting with Qpopper standalone
Date: Tue, 25 Sep 2001 14:05:29 +0200
Hi all,
I was using Qpopper in my inetd configuration file, and it was working
well.
But now, I would like to use it in a standalone version. After
compiling it
(with success), configuring it, and launch the
daemon, it could not work properly. When I Telnet to the port I get
those
messages :
>telnet 127.0.0.1 110
+Ok ready
Sep 25 12:58:02 seattle /usr/pkg/libexec/qpopper[26428]: (null) at
localhost
(127.0.0.1): -ERR POP EOF or I/O Error
-ERR POP EOF or I/O Error
+Ok Pop Server at 10.0.1.1 signing off
>
does somebody can help me ???
thanks in advance.
Vincent LUET
LEXSI - Laboratoire d'Expertise en Sécurité Informatique
Date: Tue, 25 Sep 2001 10:45:57 -0500
From: Steve Palm <stevep at sga dot org>
Subject: XTND XLST command
I had set up a web based e-mail system for someone to augment their normal e-mail clients for travelling people. To that end, when they sent a message using the web system, I send them a blind-carbon-copy with a X-HIDDENBCC: header.
The web based system doesn't show these on the screen to clutter it up, and the e-mail client has a filter set up to route this into their outbox, so it looks just like they sent it from there.
This has worked very well in the past.
When we upgraded to QPopper4, due to problems with their main Internet connection they weren't using the web based system, and have just started to use it again. It has a few problems, which I've traced to QPopper.
It used to be that the command:
XTND XLST X-HIDDENBCC
would return a list of headers which matched:
22 X-HIDDENBCC: Blah Blah Blah
38 X-HIDDENBCC: Blah Blah Blah
.
.
.
However, now it returns
+OK xlst command accepted, headers coming.
22 .
and when any other command is sent to it, it echoes
X-HIDDENBCC: Blah Blah Blah
I just did an XTND XLST From (to produce many matches), and see it does this:
1 2 3 4 5 6 7 8 9 10 11 From: Blah
From: Blah
From: Blah
From: Blah
From: Blah
Date: Tue, 25 Sep 2001 15:32:36 -0700
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: I lose email when our server crashes due to lack of
At 8:31 PM -0700 9/24/01, Dan Harkless wrote:
>It looks to me like what's happening is that my scripts do a POP3 connect
>(which I do more often than anyone else, explaining why only _I_ have
>noticed mail loss), my spool is emptied out of /var/mail/<user> into
>/var/mail/.<user>.pop, the machine crashes, and then after the machine's
>back up again, my spool is zero-length and the temp_drop is overwritten by
>the first check.
>
>I didn't pore through the code exhaustively, but I couldn't find any code
>that would prevent this. Shouldn't there be code that would check for the
>pre-existence of the temp_drop file and merge its messages back into the
>spool before doing anything else??
There is such code, and has been for as long as I can recall. I've
hit it many times in testing.
An popper/pop_dropcopy.c:1532, we revert to non-server mode if the
temp drop isn't empty:
/*
* If the temporary popdrop is not empty, revert to regular mode.
*/
if ( mybuf.st_size != 0 )
p->server_mode = 0;
Then at line 1604 we deal with any left-over mail in the temp drop:
if ( mybuf.st_size != 0 ) { /* Mostly this is for regular mode. */
DEBUG_LOG2 ( p, "Temp drop %s not empty (%u octets)",
p->temp_drop, (unsigned) mybuf.st_size );
if ( init_dropinfo ( p, p->temp_drop, p->drop, time(0) ) != POP_SUCCESS ) {
/* Occurs on temp_drop corruption */
flock ( dfd, LOCK_UN );
close ( dfd );
return ( POP_FAILURE );
}
At this point, the file pointer is at the end of the temp drop,
following any left-over mail. We then lock the spool, append mail
from it to the temp drop (after any left-over mail), zero the spool,
and work out of the temp drop.
>As I understand things, the only way to prevent any possibility of
>overwriting an existing temp_drop file would be to do it atomically, with
>O_EXCL specified along with O_CREAT on the open() call.
I'm not sure why O_EXCL is needed. Qpopper always locks the temp
drop before doing anything, to make sure only one Qpopper process is
active for the user. It then checks if the file is non-empty, and
processes any left-over mail.
--
Date: Tue, 25 Sep 2001 17:20:53 -0700 (PDT)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: Re: I lose email when our server crashes due to lack of O_EXCL use
Good call Randall... Were these in place for popper v3.0.2?
Regards,
Gregory Hicks
> Date: Tue, 25 Sep 2001 15:32:36 -0700
> To: "Dan Harkless" <qpopper at dilvish.speed dot net>, Subscribers of Qpopper
<qpopper at lists.pensive dot org>
> From: Randall Gellens <randy at qualcomm dot com>
> Subject: Re: I lose email when our server crashes due to lack of O_EXCL use
>
> At 8:31 PM -0700 9/24/01, Dan Harkless wrote:
>
> >It looks to me like what's happening is that my scripts do a POP3 connect
> >(which I do more often than anyone else, explaining why only _I_ have
> >noticed mail loss), my spool is emptied out of /var/mail/<user> into
> >/var/mail/.<user>.pop, the machine crashes, and then after the machine's
> >back up again, my spool is zero-length and the temp_drop is overwritten by
> >the first check.
> >
> >I didn't pore through the code exhaustively, but I couldn't find any code
> >that would prevent this. Shouldn't there be code that would check for the
> >pre-existence of the temp_drop file and merge its messages back into the
> >spool before doing anything else??
>
> There is such code, and has been for as long as I can recall. I've
> hit it many times in testing.
>
> An popper/pop_dropcopy.c:1532, we revert to non-server mode if the
> temp drop isn't empty:
>
> /*
> * If the temporary popdrop is not empty, revert to regular mode.
> */
> if ( mybuf.st_size != 0 )
> p->server_mode = 0;
>
>
> Then at line 1604 we deal with any left-over mail in the temp drop:
>
> if ( mybuf.st_size != 0 ) { /* Mostly this is for regular mode. */
> DEBUG_LOG2 ( p, "Temp drop %s not empty (%u octets)",
> p->temp_drop, (unsigned) mybuf.st_size );
> if ( init_dropinfo ( p, p->temp_drop, p->drop, time(0) ) !=
POP_SUCCESS ) {
> /* Occurs on temp_drop corruption */
> flock ( dfd, LOCK_UN );
> close ( dfd );
> return ( POP_FAILURE );
> }
>
> At this point, the file pointer is at the end of the temp drop,
> following any left-over mail. We then lock the spool, append mail
> from it to the temp drop (after any left-over mail), zero the spool,
> and work out of the temp drop.
>
>
> >As I understand things, the only way to prevent any possibility of
> >overwriting an existing temp_drop file would be to do it atomically, with
> >O_EXCL specified along with O_CREAT on the open() call.
>
> I'm not sure why O_EXCL is needed. Qpopper always locks the temp
> drop before doing anything, to make sure only one Qpopper process is
> active for the user. It then checks if the file is non-empty, and
> processes any left-over mail.
>
> --
---------------------------------------------------------------------
Gregory Hicks | Principal Systems Engineer
Cadence Design Systems | Direct: 408.576.3609
555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479
San Jose, CA 95134 | Internet: ghicks at cadence dot com
Tired of BSODs, My Computer, and Code Red?
http://www.sun.com/solaris/binaries/
Last updated on 25 Sep 2001 by Pensive Mailing List Admin