The qpopper list archive ending on 26 Nov 2001
Topics covered in this issue include:
1. Re: Qpopper on Tru64 unix 4.0f
Clifton Royston <cliftonr at lava dot net>
Tue, 13 Nov 2001 10:06:42 -1000
2. Checking wrong folder.
"Mark Weisman" <mweisman at gci dot net>
Tue, 13 Nov 2001 20:43:56 -0900
3. don't want to delete messages
¥^ƒÍ¼F <daniel at rebar.net dot tw>
Wed, 14 Nov 2001 19:16:31 +0800
4. Re: don't want to delete messages
Randall Gellens <randy at qualcomm dot com>
Wed, 14 Nov 2001 17:37:58 -0800
5. Re: Checking wrong folder.
Randall Gellens <randy at qualcomm dot com>
Wed, 14 Nov 2001 17:50:25 -0800
6. Re: Checking wrong folder.
Ted Cabeen <ted at impulse dot net>
Wed, 14 Nov 2001 18:15:11 -0800
7. Fw: don't want to delete messages
¥^ƒÍ¼F <daniel at rebar.net dot tw>
Thu, 15 Nov 2001 15:24:51 +0800
8. Re: Fw: don't want to delete messages
"Kenneth Porter" <shiva at well dot com>
Wed, 14 Nov 2001 23:56:50 -0800
9. RE: Checking wrong folder.
"Mark Weisman" <mweisman at gci dot net>
Wed, 14 Nov 2001 23:23:06 -0900
10. Re: Fw: don't want to delete messages
Clifton Royston <cliftonr at lava dot net>
Thu, 15 Nov 2001 08:38:40 -1000
11. DRAC with qpopper 4.0.3 on Solaris
"Paul McKinley" <qpopper at airparks dot com>
Fri, 16 Nov 2001 23:19:44 -0600
12. my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Sat, 17 Nov 2001 18:36:23 +0000
13. Re: my Qpopper isn't seeing any messages
peter.allen at moon-light.co dot uk
Sun, 18 Nov 2001 00:19:04 +0000
14. Re: my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Sun, 18 Nov 2001 09:48:55 +0000
15. Re: my Qpopper isn't seeing any messages
peter.allen at moon-light.co dot uk
Sun, 18 Nov 2001 23:50:31 +0000
16. Re: Fw: don't want to delete messages
Chuck Yerkes <chuck+qpopper at yerkes dot com>
Sun, 18 Nov 2001 16:02:58 -0800
17. Re: my Qpopper isn't seeing any messages
Randall Gellens <randy at qualcomm dot com>
Sun, 18 Nov 2001 16:51:10 -0800
18. Re: my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Sun, 18 Nov 2001 20:37:48 +0000
19. Re: my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Sun, 18 Nov 2001 21:01:01 +0000
20. Re: my Qpopper isn't seeing any messages
Randall Gellens <randy at qualcomm dot com>
Sun, 18 Nov 2001 18:36:10 -0800
21. Re: my Qpopper isn't seeing any messages
Randall Gellens <randy at qualcomm dot com>
Sun, 18 Nov 2001 18:39:54 -0800
22. qpopper with maildir
"SÈbastien Legillon" <slegillon at cudl-lille dot fr>
Mon, 19 Nov 2001 16:38:35 +0100
23. Re: my Qpopper isn't seeing any messages
Ted Cabeen <ted at impulse dot net>
Mon, 19 Nov 2001 09:01:31 -0800
24. Re: my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Mon, 19 Nov 2001 16:12:31 +0000
25. Solution: DRAC with qpopper 4.0.3 on Solaris
"Paul McKinley" <qpopper at airparks dot com>
Mon, 19 Nov 2001 16:01:07 -0600
26. Re: Solution: DRAC with qpopper 4.0.3 on Solaris
"Kenneth Porter" <shiva at well dot com>
Mon, 19 Nov 2001 21:21:12 -0800
27. RE: Solution: DRAC with qpopper 4.0.3 on Solaris
"Kenneth Porter" <shiva at well dot com>
Mon, 19 Nov 2001 22:34:59 -0800
28. qpopper + ssl
"beepee" <baling at freemail dot hu>
Tue, 20 Nov 2001 15:13:55 +0100
29. Re: qpopper + ssl
Daniel Senie <dts at senie dot com>
Tue, 20 Nov 2001 10:27:44 -0500
30. Re: qpopper + ssl
"Kenneth Porter" <shiva at well dot com>
Tue, 20 Nov 2001 20:12:36 -0800
31. Re: my Qpopper isn't seeing any messages
Rick Hoffman <hoffy at gnc dot net>
Wed, 21 Nov 2001 01:57:10 +0000
32. Re: qpopper + ssl
Rick Hoffman <hoffy at gnc dot net>
Wed, 21 Nov 2001 10:22:26 +0000
33. Re: qpopper + ssl
peter.allen at moon-light.co dot uk
Wed, 21 Nov 2001 15:46:38 +0000
34. Re: qpopper + ssl
Daniel Senie <dts at senie dot com>
Wed, 21 Nov 2001 11:09:28 -0500
35. Re: qpopper + ssl
Rick Hoffman <hoffy at gnc dot net>
Wed, 21 Nov 2001 18:23:09 +0000
36. Re: qpopper + ssl
Daniel Senie <dts at senie dot com>
Thu, 22 Nov 2001 00:54:37 -0500
37. Re: qpopper + ssl
Eric Luyten <Eric.Luyten at vub.ac dot be>
Thu, 22 Nov 2001 10:50:40 +0100 (MET)
38. PAM authentication failure (7) and more
Jens <jens at pacificsun dot ca>
Thu, 22 Nov 2001 15:04:24 -0800
39. Re: PAM authentication failure (7) and more
Jens <jens at pacificsun dot ca>
Thu, 22 Nov 2001 22:29:06 -0800
40. qpopper won't start
Peter Santiago <petersantiago at bigfoot dot com>
Fri, 23 Nov 2001 18:14:17 +0800
41. qpopper + ssl
"beepee" <baling at freemail dot hu>
Fri, 23 Nov 2001 18:40:39 +0100
42. Re: qpopper won't start
Clifton Royston <cliftonr at lava dot net>
Fri, 23 Nov 2001 12:20:44 -1000
43. Re: qpopper won't start
Michael Motal <michi at topfen dot net>
Sat, 24 Nov 2001 15:27:04 +0100
44. RE: qpopper won't start
"Peter Santiago" <petersantiago at bigfoot dot com>
Sat, 24 Nov 2001 21:50:33 +0800
45. RE: qpopper won't start
"Michael Motal" <michi at topfen dot net>
Sat, 24 Nov 2001 19:05:25 +0100 (CET)
46. POP Before SMTP.
Qpopper <qpopper at crestarnet dot net>
Mon, 26 Nov 2001 13:10:36 +0500
47. Re: POP Before SMTP.
Gregory Hicks <ghicks at cadence dot com>
Mon, 26 Nov 2001 07:24:51 -0800 (PST)
48. Re: POP Before SMTP.
Daniel Senie <dts at senie dot com>
Mon, 26 Nov 2001 10:49:27 -0500
49. Re: PAM authentication failure (7) and more
Randall Gellens <randy at qualcomm dot com>
Mon, 26 Nov 2001 18:26:38 -0800
50. Mail gets downloaded again on changing server.
Anil Shewale <anil.shewale at timesgroup dot com>
Tue, 27 Nov 2001 10:47:08 +0530
Date: Tue, 13 Nov 2001 10:06:42 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Qpopper on Tru64 unix 4.0f
On Tue, Nov 13, 2001 at 02:01:37PM +1100, David Nillesen wrote:
> Hi,
>
> We are looking at replacing the uw-imap package with qpopper to
> increase speed and efficiancy on our server, but when we went live we
> ran into a few issues.
>
> The server would happily answer requests for a while but started
> to choke with a buildup of popper processes that were hanging around
> after the user had closed the session. Users started to get the 'mailbox
> already in use' message.
>
> We were upto 450+ popper sessions active when there should only
> be about 40 concurrent users at any one time. uw-imap's ipop3d works
> fine on the same system but is slow.
Shooting from the hip, this sounds like a problem with it not getting
a HUP signal when the session goes away unexpectedly.
> Qpopper was running in server and standalone mode. It was
> compiled with the following options:
>
> ./configure --enable-spool-dir=/var/spool/mail --disable-check-hash-dir
> --disable-old-spool-loc --enable-log-login --enable-server-mode
> --enable-shy --enable-standalone --enable-uw-kludge --enable-specialauth
>
> It compiled cleanly.
>
> I've moved the source over to a debian linux system where it
> compiled cleanly and ran without the same errors. When tested on our
> production server we were using live users, when running on the test bed
> we used the 'postal' package and the executable 'rabid' to generate an
> artifical POP3 load.
> There are 17000 accounts on the production system and approx
> 10000 accounts on our test bed server.
>
> The other thing worth mentioning is that our /var/spool/mail is
> on a very very inefficient raid setup and it bottlenecks on IO a fair
> bit. However ipop3d seems to cope ok at the moment, albeit a lot slower.
Probably not related, would be my guess.
> Any suggestions would be most welcome. Especially if anyone
> could suggest other areas to check.
>
> So far, my own thoughts point to a few areas but I dont know how
> likely my guesses are:
>
> 1: Filesystem is too slow to release locks.
> * But ipop3d works, perhaps due to the fact it is slower?
> * is it possible to just use fcntl locking without dotlocking so
> as to move the locking off the filesystem? I cant modify the
> source code, due to maintainence problems.
Offhand, I don't think the problem is on the locking side. (You
probably need the dotlock to keep mail delivery from colliding with
mail retrieval, unless you can also change postfix or your delivery
agent to do only fcntl locking on the spool.)
> 2: Tru64 libraries / OS is slow to release fcntl locks and / or
> sockets.
> * A friend of mine who has used unix since moses built the ark, told
> me that some unix's (unii??) are very slow to release sockets.
unices ;-) (a la index, indices)
> Would this give me the symptoms we are experiencing? The
> linux testing would seem to indicate that it's OS based...
This sounds closer to the mark - I would guess specifically that your
qpopper processes are clinging to the broken connection in hopes that
it will return. Try seeing if TruUnix supports the following sysctl
parameters, and if so, query them:
net.inet.tcp.keepinterval integer yes
net.inet.tcp.maxpersistidle integer yes
These are very OS-specific, but if available, with much consulting of
man pages and documentation, may tell you how your UNIX handles
detection of idle sessions. If not, it may at least point you in the
right direction.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Mark Weisman" <mweisman at gci dot net>
Subject: Checking wrong folder.
Date: Tue, 13 Nov 2001 20:43:56 -0900
-----BEGIN PGP SIGNED MESSAGE-----
Hello all:
Got a few questions to ask if anyone has the time. I've got a
Qpopper 3.1.2 server running on a Linux v6.2 box. The combination has
run flawlessly up to now. I recently installed Virtual Hosts, and
things got real creative. The server was setup originally as a
singular domain, with Qpopper checking "/var/spool/mail/username".
However, now the setup has changed and I've set the original server
up as a Virtual Host, and installed two additional Virtual Hosts.
I've somehow got them routing email is routed to
"/var/spool/vmail/username". How can I add another Qpopper
installation that looks at both? I could add another virtual email
domain, and then point all of Qpopper to the new subdirectories. I'm
unaware on how to do this, any suggestions?
In Christ Jesus,
Rev.Mark Weisman
Infinite Visions Technology
Anchorage, AK
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
iQEVAwUBO/IEmw1iBtl8ydnLAQEEGAgApUi16lIVgiTzqJ8nZ8fAsoyRYTiykDTX
zg9hS59zl9+eKb6PdxR3lU1BD1Za+obQdzMBx2k2qXApu7ZOrPaQL4h71ariOCo9
FVh2PiHR6G5tpKkAi2OUZRFubMdRNQGBre8CJQk2gAGcwhGQ9u97r9w7ylez1+2W
C0gyU4FlL6zj55pVDqnkH5tiQF9U4h1ednWzFizFwrlLjkQLa/1IPZq4vZqq5gYl
WDCGVBEiUIQy+13QydD3drUaSA7VdggzhBy1L4DT64K/UJpbPrjM/f+/Io0RzdaE
SBnfgj45EkAV6Nkdly0M9+wX0+wJeNrIEXsfeSqB2voWyoNk1l3Eig=
=8crO
-----END PGP SIGNATURE-----
From: ¥^ƒÍ¼F <daniel at rebar.net dot tw>
Subject: don't want to delete messages
Date: Wed, 14 Nov 2001 19:16:31 +0800
Sir:
Please give me some suggestion for the following situation:
Environment: qpopper-4.0.3, SuSE 7.0
Situation: When mail client quit session, qpopper should automatically keep
all messages in mailbox, although mail client choose to delete messages
after session close and mail been retrieved.
I've tried to set my qpopper as follow
configure qpopper as server mode.
startup qpopper with "/usr/local/sbin/popper -S -f /etc/qpopper.config".
qpopper.config is copied from original samples comes with tarball.
The only modification is "set update-on-about = false" (default = true).
Other values are kept as original.
Thanks again
Daniel Pan
Date: Wed, 14 Nov 2001 17:37:58 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: don't want to delete messages
At 7:16 PM +0800 11/14/01, ¥^ƒÍ¼F wrote:
>Situation: When mail client quit session, qpopper should automatically keep
>all messages in mailbox, although mail client choose to delete messages
>after session close and mail been retrieved.
If you want Qpopper to ignore DELE commands, there currently isn't a
way to do that. You could of course modify the source, for example,
change pop_dele.c to not mark the message as deleted (comment out
line 57), or change pop_updt.c to not delete messages even if they
are marked deleted, or change the table in pop_get_command.c (line
65) so that 'quit' in the TRANSACTION state calls pop_restore()
instead of pop_quit(). The first one would likely be the easiest,
and the file least likely to change in future releases.
I don't recall anyone ever asking for this before, so I'm curious why
you want to keep all messages.
--
Date: Wed, 14 Nov 2001 17:50:25 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: Checking wrong folder.
I'm not sure exactly what you're asking, but if you want to tell
Qpopper to look in a different directory for the spool, you can use
the 'spool-dir' option in a configuration file. (I think you can use
this in a user-specific configuration file if you want, but the
configuration file has to be in the default spool directory, and I'm
not sure that scenario was tested, so try it first.) See the
Administrator's Guide for more details.
You can also use the '--enable-spool-dir' option with ./configure.
Try './configure --help' for a full list. All of them should also be
in the Administrator's Guide, but I think a few were left out by
accident.
--
From: Ted Cabeen <ted at impulse dot net>
Subject: Re: Checking wrong folder.
Date: Wed, 14 Nov 2001 18:15:11 -0800
In message <524912507584089676114 at lists.pensive dot org>, Randall Gellens writes:
>I'm not sure exactly what you're asking, but if you want to tell
>Qpopper to look in a different directory for the spool, you can use
>the 'spool-dir' option in a configuration file. (I think you can use
>this in a user-specific configuration file if you want, but the
>configuration file has to be in the default spool directory, and I'm
>not sure that scenario was tested, so try it first.) See the
>Administrator's Guide for more details.
>
>You can also use the '--enable-spool-dir' option with ./configure.
>Try './configure --help' for a full list. All of them should also be
>in the Administrator's Guide, but I think a few were left out by
>accident.
Quick related question. Is there a way to get qpopper to put the poplocks and
cache files in the users' home directory when we use home dir mail spools?
Currently, it sticks them in the spool dir. That can be a problem if user
home directories are spread across multiple partitions.
--
Ted Cabeen http://www.pobox.com/~secabeen ted at impulse dot net
Check Website or Keyserver for PGP/GPG Key BA0349D2 secabeen at pobox dot com
"I have taken all knowledge to be my province." -F. Bacon secabeen at cabeen dot org
"Human kind cannot bear very much reality."-T.S.Eliot cabeen at netcom dot com
From: ¥^ƒÍ¼F <daniel at rebar.net dot tw>
Subject: Fw: don't want to delete messages
Date: Thu, 15 Nov 2001 15:24:51 +0800
Randall:
Thank you so much for your idea. Actually, I did it in a different w
ay
and got what I want. You told me to comment out line 57 delete_msg. I tr
ied
but didn't work (maybe I didn't understand what you mean). I change
delete_msg call to undelete_msg call. When delete_msg is called, qpopper
actually mark messages as undelete. It work with outlook express so far.
Others should be teseted later.
Any idea for this kind of trick?
Will it cause any problem?
In response to your curiosity:
The story wourld sound like:
User pcs are always infected by virus and crashed by some other reaso
n.
Users don't have any sense to backup their important files from mail to f
ile
server IT people feel it too much trouble to educate users. Whenever th
eir
pc crashed, important messages or even files are lost. IT people don't w
ant
to use tar or tape backup and restore utility to backup user maildrop. M
y
idea is that, we can use a secondary mail server as mail backup server.
By
using aliases name, user mail can be forwarded to secondary mail server.
Secondary server will have a big enough disk array to store mail for abou
t
one year. Of course, secondary are redundant for first mail server.
Whenever pc crashed, user can retrieve all their mail from the second
ary
(mail for this year). After they retrieve backup mail from secondary, ma
il
should be kept, not deleted. They can retrieve mail again from secondary
server, if their pc crashed and mail lost again. Also, IT people feel it
extremely difficult to ask user to configure their mail client software t
o
keep mail archive in mail server. That's why I asked for this solution.
I know there must some other solutions, but this one is fully automat
ic
and the best (so far) in my idea. If you have any better idea, please le
t
me know. I would appreciate it very much.
Still there are a lot to consider. Like, will the big maildrop infec
ted
system performance, can qpopper handle single maildrop larger 200MB or ev
en
400MB. Let me know if you have any valuable suggestion or experience for
my
idea.
Thanks so much again,
dp
----- Original Message -----
From: "Randall Gellens" <randy at qualcomm dot com>
To: "¥^fͼF" <daniel at rebar.net dot tw>; "Subscribers of Qpopper"
<qpopper at lists.pensive dot org>
Sent: Thursday, November 15, 2001 9:37 AM
Subject: Re: don't want to delete messages
> At 7:16 PM +0800 11/14/01, ¥^fͼF wrote:
> >Situation: When mail client quit session, qpopper should automatically
keep
> >all messages in mailbox, although mail client choose to delete message
s
> >after session close and mail been retrieved.
>
> If you want Qpopper to ignore DELE commands, there currently isn't a
> way to do that. You could of course modify the source, for example,
> change pop_dele.c to not mark the message as deleted (comment out
> line 57), or change pop_updt.c to not delete messages even if they
> are marked deleted, or change the table in pop_get_command.c (line
> 65) so that 'quit' in the TRANSACTION state calls pop_restore()
> instead of pop_quit(). The first one would likely be the easiest,
> and the file least likely to change in future releases.
>
> I don't recall anyone ever asking for this before, so I'm curious why
> you want to keep all messages.
> --
>
From: "Kenneth Porter" <shiva at well dot com>
Date: Wed, 14 Nov 2001 23:56:50 -0800
Subject: Re: Fw: don't want to delete messages
On Thu, 15 Nov 2001 15:24:51 +0800, ´^øˆ¹F wrote:
>Whenever pc crashed, user can retrieve all their mail from the secondar
y
>(mail for this year). After they retrieve backup mail from secondary,
mail
>should be kept, not deleted.
You might accomplish this with file permissions and ownerships. Let the
MDA have write access to the spools, but only let qpopper have read
access. Not sure if that'll break qpopper, though.
For instance, create the spool files with ownership root.user (ie.
owner root, group set to the user for that spool file), and set the
permissions to 740.
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'l
l take my answer on the list.]
From: "Mark Weisman" <mweisman at gci dot net>
Subject: RE: Checking wrong folder.
Date: Wed, 14 Nov 2001 23:23:06 -0900
-----BEGIN PGP SIGNED MESSAGE-----
Randall,
Basically I'm trying to use Qpopper to check Virtual email domains
on my 3.1.2 server. I have 4.0.3 in my possession and I'm ready to
install, however, I don't think the problem is with Qpopper, it's
actually in Sendmail. When I set up Virtual Email Domains within
mailconf it routes mail to a folder called
/var/spool/vmail/domainname/username (and this works 100%). Now what
I need is to redirect the Virtual Email domain aliases to "real"
local users. I'm thinking once that happens, then Qpopper will work
as designed. However, I am unaware on how to change this setting. Any
ideas on this piece would be appreciated greatly.
In Christ Jesus,
Rev.Mark Weisman
Infinite Visions Technology
Anchorage, AK
- -----Original Message-----
From: Randall Gellens [mailto:randy at qualcomm dot com]
Sent: Wednesday, November 14, 2001 4:50 PM
To: Mark Weisman; Subscribers of Qpopper
Subject: Re: Checking wrong folder.
I'm not sure exactly what you're asking, but if you want to tell
Qpopper to look in a different directory for the spool, you can use
the 'spool-dir' option in a configuration file. (I think you can use
this in a user-specific configuration file if you want, but the
configuration file has to be in the default spool directory, and I'm
not sure that scenario was tested, so try it first.) See the
Administrator's Guide for more details.
You can also use the '--enable-spool-dir' option with ./configure.
Try './configure --help' for a full list. All of them should also be
in the Administrator's Guide, but I think a few were left out by
accident.
- --
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
iQEVAwUBO/N7aQ1iBtl8ydnLAQFfBggAuvFdcB0L4Ni/htJK7V2fSkq2qDHBj5Qs
hOSpXQeJppg7cvZkAkaA9TnCbVkdpv6/ItxkwiuIoePPWvdcmNts+rm5UP85hCcw
QjtpmS5Nxbf5WfdSDS2+6k8b9p2DgKfrknvPpHhFXAidSx2XWhl32LvGCQw3UBLO
pYsoiX/YjgzGhGFrb1Yk43VqH3TW6EIuE9UG5zYx2zSWVHA5ijW1a9oeSm3VTbwt
wtvBJezZKdxyx6zPuPPbxx6kxWML3GrN/skQS/Tzjxv0wtZsfGkSiVdW/lzvLjgF
ECcGw9662SFEfc9j38yNZhu+M1BjA1f3FmVbdLSqiIhsZLQiDREvdg=
=Rgt4
-----END PGP SIGNATURE-----
Date: Thu, 15 Nov 2001 08:38:40 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: Fw: don't want to delete messages
On Thu, Nov 15, 2001 at 03:24:51PM +0800, ´^°ê¹F wrote:
> Randall:
>
> Thank you so much for your idea. Actually, I did it in a different way
> and got what I want. You told me to comment out line 57 delete_msg. I tried
> but didn't work (maybe I didn't understand what you mean). I change
> delete_msg call to undelete_msg call. When delete_msg is called, qpopper
> actually mark messages as undelete. It work with outlook express so far.
> Others should be teseted later.
> Any idea for this kind of trick?
Sounds like a pretty good way to do it.
> In response to your curiosity:
> The story wourld sound like:
>
> User pcs are always infected by virus and crashed by some other reason.
> Users don't have any sense to backup their important files from mail to file
> server IT people feel it too much trouble to educate users. Whenever their
> pc crashed, important messages or even files are lost. IT people don't want
> to use tar or tape backup and restore utility to backup user maildrop. My
> idea is that, we can use a secondary mail server as mail backup server. By
> using aliases name, user mail can be forwarded to secondary mail server.
> Secondary server will have a big enough disk array to store mail for about
> one year. Of course, secondary are redundant for first mail server.
> Whenever pc crashed, user can retrieve all their mail from the secondary
> (mail for this year). After they retrieve backup mail from secondary, mail
> should be kept, not deleted. They can retrieve mail again from secondary
> server, if their pc crashed and mail lost again. Also, IT people feel it
> extremely difficult to ask user to configure their mail client software to
> keep mail archive in mail server. That's why I asked for this solution.
> I know there must some other solutions, but this one is fully automatic
> and the best (so far) in my idea. If you have any better idea, please let
> me know. I would appreciate it very much.
That's a very creative solution! It'll probably take some refining,
but if you're willing to invest the money in the storage, it could
certainly help with the problem you describe.
If IT doesn't want to educate users, that's the biggest problem that
you need to work around. In that case, you might also think about
investing some effort in preventing the virus infections, e.g. by
developing procmail filters to run on the server where mail is
delivered, which will very selectively delete the most common types of
email viruses on your system before they reach your users. Viruses
such as Sircam, Nimda, Magistr, etc. are all quite possible to detect
and drop when incoming.
> Still there are a lot to consider. Like, will the big maildrop infected
> system performance, can qpopper handle single maildrop larger 200MB or even
> 400MB.
My experience is that it may cause problems on the client side at
connection time, due to the delays when qpopper needs to actually scan
the whole spool and build the list of UIDLs, which it does right after
authenticating the password. Large mail downloads can be a problem
over modem connections but should not be over LAN.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: "Paul McKinley" <qpopper at airparks dot com>
Subject: DRAC with qpopper 4.0.3 on Solaris
Date: Fri, 16 Nov 2001 23:19:44 -0600
qpopper 4.0.3
DRAC version is 1.11, libdrac.a installed in /usr/lib
BerkeleyDB.3.3 installed
Solaris 8 with MU3
qpopper configure line is:
configure --with-openssl=/usr/local/ssl --enable-specialauth --enable-timing
--enable-apop --with-popuid=pop --enable-log-facility=local1 --enable-log-l
ogin --with-drac=/usr/lib
The configure fails on dracauth:
...
checking for set_auth_parameters in -lsecurity... no
checking for crypt in -lcrypt... yes
checking for dracauth in -ldrac... no
Can't use DRAC: dracauth not found in -ldrac
strings /usr/lib/libdrac.a | grep dracauth
dracauth
dracauth.o/ 1005971984 1000 14 100644 52244 `
dracauth.c
dracauth.c
dracauth:F(0,1)
dracauth.c
dracauth
So, why doesn't he see dracauth?
Thanks in advance,
Paul McKinley
Date: Sat, 17 Nov 2001 18:36:23 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: my Qpopper isn't seeing any messages
I am very new to this so please be gentle, clear and concise and thank
you
in advance for any response.
When using the following:
$ telnet myHostName pop3
I am always getting:
"... has 0 visible messages (0 hidden) in 0 octets"
even when I stick new test messages into my mailbox.
My situation may seem rather obtuse to any of you. I am using a dial-up
ISP in which I retrieve my mail from. On my system Fetchmail gets them,
postfix processes them and hands them off to procmail which finally
delivers
to my mailboxes. My ISP mailing address is "hoffy@gnc dot net". I have
procmail
set up to recognize different users on my system addressed as:
"hoffy@gnc dot net" mail spool is supposed to be
/var/spool/mail/hoffy(this being me, of course)
"hoffy+user1@gnc dot net" mail spool is supposed to be
/var/spool/mail/user1
"hoffy+user2@gnc dot net" mail spool is supposed to be
/var/spool/mail/user2
etc.
When I installed Qpopper a "/var/spool/pop" directory was created. It
is in that directory
where it creates this temp file .user.pop during a session. Even if
I put a file called
"hoffy" in that directory with new messages in it I still get the same
result.
FYI, I am using Debian and installed Qpopper with its package management
system, like RPMs, only better :) so I only have executables installed,
therefore I did not
configure the program, it was all done for me.
Can anybody help me here? Why am I never seeing any new messages? Can
I download
a message from my ISP's POP server then turn around and serve the same
message
to a user on my local network with my own POP server?
Date: Sun, 18 Nov 2001 00:19:04 +0000
From: peter.allen at moon-light.co dot uk
Subject: Re: my Qpopper isn't seeing any messages
Can I suggest that you break down this problem into two parts.
Firstly you need to determine whether your mail is being delivered to the
right place. Can you send yourself a message and then read your mailbox
any way you choose (though obviously not with qpopper). This could be by
using Pine, running less or more on the file or even ftp the file to a
local machine and view it there.
If the mail is getting not getting through then you should investigate the
various mail delivery mechanisms you described.
The second aspect is if mail does arrive where it should. In that case
then qpopper is either not running or looking in the wrong place. Checking
for this will involve reviewing both configuration and log files.
Do e-mail again for any more specific points, either privately or to the
list.
Peter
At 18:36 17/11/01 +0000, Rick Hoffman wrote:
>I am very new to this so please be gentle, clear and concise and thank
>you
>in advance for any response.
>
>When using the following:
>
>$ telnet myHostName pop3
>
>I am always getting:
>"... has 0 visible messages (0 hidden) in 0 octets"
>
>even when I stick new test messages into my mailbox.
>
>My situation may seem rather obtuse to any of you. I am using a dial-up
>
>ISP in which I retrieve my mail from. On my system Fetchmail gets them,
>
>postfix processes them and hands them off to procmail which finally
>delivers
>to my mailboxes. My ISP mailing address is "hoffy@gnc dot net". I have
>procmail
>set up to recognize different users on my system addressed as:
>"hoffy@gnc dot net" mail spool is supposed to be
>/var/spool/mail/hoffy(this being me, of course)
>"hoffy+user1@gnc dot net" mail spool is supposed to be
>/var/spool/mail/user1
>"hoffy+user2@gnc dot net" mail spool is supposed to be
>/var/spool/mail/user2
>etc.
>
>When I installed Qpopper a "/var/spool/pop" directory was created. It
>is in that directory
>where it creates this temp file .user.pop during a session. Even if
>I put a file called
>"hoffy" in that directory with new messages in it I still get the same
>result.
>
>FYI, I am using Debian and installed Qpopper with its package management
>
>system, like RPMs, only better :) so I only have executables installed,
>therefore I did not
>configure the program, it was all done for me.
>
>Can anybody help me here? Why am I never seeing any new messages? Can
>I download
>a message from my ISP's POP server then turn around and serve the same
>message
>to a user on my local network with my own POP server?
Date: Sun, 18 Nov 2001 09:48:55 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: my Qpopper isn't seeing any messages
Thanks for your response, Peter.
> Can you send yourself a message and then read your mailbox
> any way you choose (though obviously not with qpopper).
Oh, yes. Like I said, I am using a dial-up account with an ISP and
my mail messages addressed to hoffy at gnc dot net are sent to and stored on
it's machine. I easily found out that my ISP will also accept and
store messages addressed to hoffy+user1 at gnc.net, hoffy+user2 at gnc dot net,
etc. where user1, user2, etc. are people on my local network. So I use
Fetchmail on my machine to retrieve these messages from my ISP and I
have Procmail set-up through Postfix to filter these messages into their
appropriate mailboxes also on my machine. I read my own messages with
mutt from /var/spool/mail/hoffy. I also have directories called
/var/spool/mail/[user1],[user2],[etc] for those other valid and expected
messages. I am trying to set up Qpopper on my machine to deliver those
messages again but only locally this time to the users on my other local
machines.
Am I explaining this very well? I don't know.
So, my current mail spool is in the path /var/spool/mail/...
I am trying to get Qpopper to use this path.
When I installed Qpopper /var/spool/mail/pop and /var/spool/mail/popbull
were created. I don't know what these directories are for. I do know
that during a session with Qpopper it creates a temp file called .hoffy.pop
in the /pop directory. It appears this directory is what Qpopper wants to
use for its mail spool.
> The second aspect is if mail does arrive where it should.
Yes it does. I set-up Procmail to deliver to the /var/spool/mail/... path.
> In that case then qpopper is either not running
Qpopper is definently running because I can use the:
"$ telnet myHostname pop3" command with no errors but also always zero
messages which is the crux of my problem, here.
> or looking in the wrong place.
This I have a feeling is happening. I copy my mailbox file (/var/spool/
mail/hoffy) into /var/spool/pop expecting Qpopper to see it but it still
tells me zero messages.
> Checking for this will involve reviewing both configuration and log files.
Debian's package management system(dpkg) installed Qpopper for me and no
configuration file was created. It placed the line:
"pop-3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.qpopper"
in my /etc/inetd.conf file.
I created a config file and tried adding a "-f /path/to/config/file" to the
end of the line. In the config file I put:
"set spool-dir=/var/spool/mail"
I am not getting any errors but Qpopper is still creating that temp file
.hoffy.pop in the /var/spool/pop directory and showing zero messages. The
log file is not showing anything useful unless you have other suggestions
in which to use it.
Thanks again.
Date: Sun, 18 Nov 2001 23:50:31 +0000
From: peter.allen at moon-light.co dot uk
Subject: Re: my Qpopper isn't seeing any messages
At 09:48 18/11/01 +0000, you wrote:
>Thanks for your response, Peter.
No problem. My thoughts are at the bottom of your (edited) e-mail.
>snip --> I read my own messages with mutt from
>/var/spool/mail/hoffy. So, my current mail spool is in the path
>/var/spool/mail/...
>
>When I installed Qpopper /var/spool/mail/pop and /var/spool/mail/popbull
>were created. During a session with Qpopper it creates a temp file called
>.hoffy.pop in the /pop directory.
>
> > or looking in the wrong place.
>This I have a feeling is happening. I copy my mailbox file (/var/spool/
>mail/hoffy) into /var/spool/pop expecting Qpopper to see it but it still
>tells me zero messages.
>
>I created a config file and tried adding a "-f /path/to/config/file" to the
>end of the line. In the config file I put:
>"set spool-dir=/var/spool/mail"
>
>I am not getting any errors but Qpopper is still creating that temp file
>.hoffy.pop in the /var/spool/pop directory
In summary the rest of your setup is putting mail into /var/spool/mail/ but
qpopper is checking from the /var/spool/mail/pop/ directory. Using set
spool-dir=/var/spool/mail does not override this (though it should - did
you ps ax | grep inetd and then kill -HUP <pid> the process identity shown ?)
If restarting inetd does not work can you either a) re-compile qpopper to
deliver to /var/spool/mail or b) change Procmail etc to deliver to
/var/spool/mail/pop ?
Unfortunately I cannot be specific on a) as we deliver to users' home
directories as we run qmail. However either a) or b) should get you up and
running.
(Incidentally copying your mailbox to /var/spool/mail/pop should also have
worked. Out of interest doing cp -a or checking permissions carefully
would probably solve this [academic] point.)
Good luck !!
Peter
Date: Sun, 18 Nov 2001 16:02:58 -0800
From: Chuck Yerkes <chuck+qpopper at yerkes dot com>
Subject: Re: Fw: don't want to delete messages
You are describing a scenario where POP is the WRONG answer.
You might want to try IMAP which is more geared to keeping
data on the server than having smart clients. IMAP servers abound,
commercial and free.
Quoting ´^°ê¹F (daniel at rebar.net dot tw):
> Randall:
>
> Thank you so much for your idea. Actually, I did it in a different way
> and got what I want. You told me to comment out line 57 delete_msg. I tried
> but didn't work (maybe I didn't understand what you mean). I change
> delete_msg call to undelete_msg call. When delete_msg is called, qpopper
> actually mark messages as undelete. It work with outlook express so far.
> Others should be teseted later.
> Any idea for this kind of trick?
> Will it cause any problem?
>
> In response to your curiosity:
> The story wourld sound like:
>
> User pcs are always infected by virus and crashed by some other reason.
> Users don't have any sense to backup their important files from mail to file
> server IT people feel it too much trouble to educate users. Whenever their
> pc crashed, important messages or even files are lost. IT people don't want
> to use tar or tape backup and restore utility to backup user maildrop. My
> idea is that, we can use a secondary mail server as mail backup server. By
> using aliases name, user mail can be forwarded to secondary mail server.
> Secondary server will have a big enough disk array to store mail for about
> one year. Of course, secondary are redundant for first mail server.
> Whenever pc crashed, user can retrieve all their mail from the secondary
> (mail for this year). After they retrieve backup mail from secondary, mail
> should be kept, not deleted. They can retrieve mail again from secondary
> server, if their pc crashed and mail lost again. Also, IT people feel it
> extremely difficult to ask user to configure their mail client software to
> keep mail archive in mail server. That's why I asked for this solution.
> I know there must some other solutions, but this one is fully automatic
> and the best (so far) in my idea. If you have any better idea, please let
> me know. I would appreciate it very much.
> Still there are a lot to consider. Like, will the big maildrop infected
> system performance, can qpopper handle single maildrop larger 200MB or even
> 400MB. Let me know if you have any valuable suggestion or experience for my
> idea.
>
> Thanks so much again,
> dp
>
> ----- Original Message -----
> From: "Randall Gellens" <randy at qualcomm dot com>
> To: "¥^fͼF" <daniel at rebar.net dot tw>; "Subscribers of Qpopper"
> <qpopper at lists.pensive dot org>
> Sent: Thursday, November 15, 2001 9:37 AM
> Subject: Re: don't want to delete messages
>
>
> > At 7:16 PM +0800 11/14/01, ¥^fͼF wrote:
> > >Situation: When mail client quit session, qpopper should automatically
> keep
> > >all messages in mailbox, although mail client choose to delete messages
> > >after session close and mail been retrieved.
> >
> > If you want Qpopper to ignore DELE commands, there currently isn't a
> > way to do that. You could of course modify the source, for example,
> > change pop_dele.c to not mark the message as deleted (comment out
> > line 57), or change pop_updt.c to not delete messages even if they
> > are marked deleted, or change the table in pop_get_command.c (line
> > 65) so that 'quit' in the TRANSACTION state calls pop_restore()
> > instead of pop_quit(). The first one would likely be the easiest,
> > and the file least likely to change in future releases.
> >
> > I don't recall anyone ever asking for this before, so I'm curious why
> > you want to keep all messages.
> > --
> >
Date: Sun, 18 Nov 2001 16:51:10 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: my Qpopper isn't seeing any messages
At 9:48 AM +0000 11/18/01, Rick Hoffman wrote:
> > or looking in the wrong place.
> This I have a feeling is happening. I copy my mailbox file (/var/spool/
> mail/hoffy) into /var/spool/pop expecting Qpopper to see it but it still
> tells me zero messages.
That seems very odd.
>
>> Checking for this will involve reviewing both configuration and log files.
> Debian's package management system(dpkg) installed Qpopper for me and no
> configuration file was created. It placed the line:
> "pop-3 stream tcp nowait root /usr/sbin/tcpd
> /usr/sbin/in.qpopper"
> in my /etc/inetd.conf file.
Which version of Qpopper?
>
> I created a config file and tried adding a "-f /path/to/config/file" to the
> end of the line. In the config file I put:
> "set spool-dir=/var/spool/mail"
Make sure you're using Qpopper 4.0.3.
Probably the best thing is to get a fresh copy of 4.0.3 and run
'./configure' and 'make' yourself. Then, if you still have any
problems, you can enable debug tracing and see what's going on.
Date: Sun, 18 Nov 2001 20:37:48 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: my Qpopper isn't seeing any messages
Thanks for your response Randall.
> > > or looking in the wrong place.
> > This I have a feeling is happening. I copy my mailbox file (/var/spool/
> > mail/hoffy) into /var/spool/pop expecting Qpopper to see it but it still
> > tells me zero messages.
>
> That seems very odd.
Yeah, just what I thought. I figured that should've done it to.
Any ideas on why this didn't work? You also saw, I'm sure, that I
explicitly created a config file and was trying to order Qpopper to
use /var/spool/mail as my mailbox path but it appears it is totally
ignoring that. Could it be that Qpopper is not seeing this config
file for some reason?
Also, when I use the telnet command to invoke Qpopper and it accepts the
user and password stuff and then tells me no messages, doesn't that mean
Qpopper is up and running?
> Which version of Qpopper?
$ qpopper -v
Qpopper version 4.0.3 (non-standalone)
> Probably the best thing is to get a fresh copy of 4.0.3 and run
> './configure' and 'make' yourself. Then, if you still have any
> problems, you can enable debug tracing and see what's going on.
I have no problem doing that but its a shame I should have to.
I am curious what difference this would make? I suppose I can't
enable debug tracing unless that is compiled into the executable, is
that right?
I am guessing the Debian maintainer of this package used all the
default settings when he/she compiled it. I am also guessing that
would be the most logical thing to do because if there are any
specific user settings/configuration issues shouldn't I be able to
negociate those through command line options or a configuration file?
If not then I wonder what it is that I need to compile in to make
a difference from what is going on now.
For some reason I have a feeling I am in for a big time-consuming
fight here. I don't understand what I am doing wrong. It all seems
so cut and dried.
My ISP is, of course, using a POP server to deliver messages to me.
Could there be something his POP server is doing so that these messages
can't be delivered again by another POP server? Does that make any
sense?
Thanks again.
Date: Sun, 18 Nov 2001 21:01:01 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: my Qpopper isn't seeing any messages
> In summary the rest of your setup is putting mail into /var/spool/mail/ but
> qpopper is checking from the /var/spool/mail/pop/ directory. Using set
> spool-dir=/var/spool/mail does not override this (though it should - did
> you ps ax | grep inetd and then kill -HUP <pid> the process identity shown
> ?)
>
FYI, I miss typed the directories Qpopper created upon install. They are
/var/spool/pop and popbull not /var/spool/mail/pop and popbull. Although
that probably makes little difference. After I changed the inetd.conf file
I did the following:
$ /etc/init.d/inetd reload
Reloading internet superserver: inetd.
Isn't this achieving the same thing as killing the process then restarting it?
> If restarting inetd does not work can you either a) re-compile qpopper to
> deliver to /var/spool/mail
Like I said I have installed a binary copy of Qpopper. I don't have the
source.
> or b) change Procmail etc to deliver to /var/spool/mail/pop ?
Well, like I said I already have tried coping my mailbox file into the /pop
directory and it still tells me no messages even though I know for a fact
there are. In fact, the same file in my /mail directory causes the following
to appear above my command prompt:
"you have mail in /var/spool/mail/hoffy"
This message stays there until I use mutt to read the new mail. I copied the
exact same file before using mutt into the /pop directory then tried to
telnet Qpopper and it tells me there are zero messages. This to me seems very
odd.
> (Incidentally copying your mailbox to /var/spool/mail/pop should also have
> worked. Out of interest doing cp -a or checking permissions carefully
> would probably solve this [academic] point.)
If that temp file .hoffy.pop shows up shouldn't that mean that directory is
fine as far as owner/permissions is concerned? Also when I copy the mailbox
file into that directory its ownership/permissions are:
owner - hoffy
group - staff
permissions - 0660.
Could there a problem here? Heck, it is working for the procmail/postfix/mutt
combo. Maybe Qpopper doesn't like those settings for that file?
Date: Sun, 18 Nov 2001 18:36:10 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: my Qpopper isn't seeing any messages
At 8:37 PM +0000 11/18/01, Rick Hoffman wrote:
> Thanks for your response Randall.
>
>> > > or looking in the wrong place.
>> > This I have a feeling is happening. I copy my mailbox file (/var/spool/
>> > mail/hoffy) into /var/spool/pop expecting Qpopper to see it but it still
>> > tells me zero messages.
>>
>> That seems very odd.
>
> Yeah, just what I thought. I figured that should've done it to.
> Any ideas on why this didn't work? You also saw, I'm sure, that I
> explicitly created a config file and was trying to order Qpopper to
> use /var/spool/mail as my mailbox path but it appears it is totally
> ignoring that. Could it be that Qpopper is not seeing this config
> file for some reason?
That's possible. Since you're running Qpopper through tcpd instead
of directly from inetd there may be something funny about parameters.
>
> Also, when I use the telnet command to invoke Qpopper and it accepts the
> user and password stuff and then tells me no messages, doesn't that mean
> Qpopper is up and running?
It sure does.
>
>> Which version of Qpopper?
>
> $ qpopper -v
> Qpopper version 4.0.3 (non-standalone)
That version certainly knows about configuration files and the
spool-dir option.
> > Probably the best thing is to get a fresh copy of 4.0.3 and run
>> './configure' and 'make' yourself. Then, if you still have any
>> problems, you can enable debug tracing and see what's going on.
>
> I have no problem doing that but its a shame I should have to.
> I am curious what difference this would make? I suppose I can't
> enable debug tracing unless that is compiled into the executable, is
> that right?
That's it.
>
> I am guessing the Debian maintainer of this package used all the
> default settings when he/she compiled it. I am also guessing that
> would be the most logical thing to do because if there are any
> specific user settings/configuration issues shouldn't I be able to
> negociate those through command line options or a configuration file?
> If not then I wonder what it is that I need to compile in to make
> a difference from what is going on now.
You should be able to set almost everything using a configuration file.
>
> For some reason I have a feeling I am in for a big time-consuming
> fight here. I don't understand what I am doing wrong. It all seems
> so cut and dried.
You could try, just as a test, changing the inetd.conf line from:
"pop-3 stream tcp nowait root /usr/sbin/tcpd
/usr/sbin/in.qpopper -f /path/to/config/file"
to:
"pop-3 stream tcp nowait root /usr/sbin/in.qpopper
qpopper -f /path/to/config/file"
You could also try putting something bogus in the configuration file.
That should cause Qpopper to spit out an error message and close the
connection. That would confirm that it's reading the configuration
file. (For example, "set foobar gork"). If this doesn't happen, try
adding a bogus command-line argument. The idea to isolate where the
problem is:
- Are you failing to send inetd a HUP signal?
- Are your command-line flags not being passed to Qpopper?
- Is Qpopper failing to read or process the config file?
>
> My ISP is, of course, using a POP server to deliver messages to me.
> Could there be something his POP server is doing so that these messages
> can't be delivered again by another POP server? Does that make any
> sense?
That should have nothing to do with it. As a totally separate
matter from your current problem, SMTP delivery is much more reliable
than POP delivery. If your ISP supports it, you could use ODMR
(On-Demand Mail Relay, RFC 2645), which fetchmail now supports.
Date: Sun, 18 Nov 2001 18:39:54 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: my Qpopper isn't seeing any messages
At 9:01 PM +0000 11/18/01, Rick Hoffman wrote:
> If that temp file .hoffy.pop shows up shouldn't that mean that directory is
> fine as far as owner/permissions is concerned? Also when I copy the mailbox
> file into that directory its ownership/permissions are:
> owner - hoffy
> group - staff
> permissions - 0660.
>
> Could there a problem here? Heck, it is working for the
> procmail/postfix/mutt
> combo. Maybe Qpopper doesn't like those settings for that file?
If Qpopper finds something wrong with owner/permission settings it
reports and error. Since you get a normal session that reports no
messages, it doesn't seem (at least at this stage) to be a
permissions issue. But a debug trace would confirm this.
From: "SÈbastien Legillon" <slegillon at cudl-lille dot fr>
Subject: qpopper with maildir
Date: Mon, 19 Nov 2001 16:38:35 +0100
hi,
I want to know how configure qpopper with option Maildir.
I configure a webmail with courrir-imap. But i want to work with qpopper for POP3
acces.
Thanks in advance
SÈabstien Legillon
www.illico.org
Ce courrier a ÈtÈ contrÙlÈ contre des virus.
CUDL - TÈlÈcoms
postmaster at cudl-lille dot fr
From: Ted Cabeen <ted at impulse dot net>
Subject: Re: my Qpopper isn't seeing any messages
Date: Mon, 19 Nov 2001 09:01:31 -0800
In message <392567428430858033389 at lists.pensive dot org>, Rick Hoffman writes:
>> Probably the best thing is to get a fresh copy of 4.0.3 and run
>> './configure' and 'make' yourself. Then, if you still have any
>> problems, you can enable debug tracing and see what's going on.
>
>I am guessing the Debian maintainer of this package used all the
>default settings when he/she compiled it. I am also guessing that
>would be the most logical thing to do because if there are any
>specific user settings/configuration issues shouldn't I be able to
>negociate those through command line options or a configuration file?
>If not then I wonder what it is that I need to compile in to make
>a difference from what is going on now.
That's not necessarily true. Why don't you contact the Debian developer for
this package? He can probably tell you if the problems you're seeing are due
to how he packaged it or not. In general, bugs in Debian packages should be
reported to the Debian Bug Tracking System first, and then to the upstream
developers, so that the upstream isn't bothered trying to support bugs that
were introduced by Debian in the first place.
You can find instructions for submitting Debian bug reports here:
http://www.debian.org/Bugs/Reporting
Thanks.
--
Ted Cabeen http://www.pobox.com/~secabeen ted at impulse dot net
Check Website or Keyserver for PGP/GPG Key BA0349D2 secabeen at pobox dot com
"I have taken all knowledge to be my province." -F. Bacon secabeen at cabeen dot org
"Human kind cannot bear very much reality."-T.S.Eliot cabeen at netcom dot com
Date: Mon, 19 Nov 2001 16:12:31 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: my Qpopper isn't seeing any messages
mpulse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011119170131.F17C3375E7 at gray.impulse dot net>
User-Agent: Mutt/1.3.22i
> >I am guessing the Debian maintainer of this package used all the
> >default settings when he/she compiled it. I am also guessing that
> >would be the most logical thing to do because if there are any
> >specific user settings/configuration issues shouldn't I be able to
> >negociate those through command line options or a configuration file?
> >If not then I wonder what it is that I need to compile in to make
> >a difference from what is going on now.
>
> That's not necessarily true. Why don't you contact the Debian developer for
> this package? He can probably tell you if the problems you're seeing are due
> to how he packaged it or not. In general, bugs in Debian packages should be
> reported to the Debian Bug Tracking System first, and then to the upstream
> developers, so that the upstream isn't bothered trying to support bugs that
> were introduced by Debian in the first place.
>
> You can find instructions for submitting Debian bug reports here:
> http://www.debian.org/Bugs/Reporting
I have isolated a problem I am having.
When I use the following line in inetd.conf I am always getting an "unable to
process config file" error message.
"pop-3 stream tcp nowait root /usr/sbin/in.qpopper qpopper -f /etc/postfix/qpopper/qpopper.conf"
This seems to be no matter what the ownership/permission settings are for the
config file and/or for the file's path. As far as the content of the config
file I have tried:
set spool-dir=/var/spool/mail
I also tried removing any content from the config file and I still get the
error.
When I remove the -f option, the error message goes away.
I'm just hoping that someone on this mailing list might be familiar with this
situation that could shed some light. I'm not reporting any bug. I don't know
that it is or not.
I am also hoping its something simple that I am missing. I have read the
Qpopper FAQ and any documentation, searched the Web, etc. Now I have come to
this mailing list for help.
I really don't know what else to do. I can try to contact the Debian
maintainer but I am pretty sure this person is not considered as a "developer"
as such. Unless I am mistaken this person only pre-compiles the source and
creates the configuration and make stuff into a package that will
"automatically" install onto a Debian system. Are you saying this is an
installation problem?
From: "Paul McKinley" <qpopper at airparks dot com>
Subject: Solution: DRAC with qpopper 4.0.3 on Solaris
Date: Mon, 19 Nov 2001 16:01:07 -0600
I didn't get any responses on this, so maybe nobody else is having this
issue, although I did see reference to a couple other people using
qpopper/drac on Solaris. I'm posting these workarounds for others who might
trip over these issues in the future.
There were several different issues.
First was that drac was apparently not working judging by the results of the
"testing" program:
If I use
testing localhost 130.179.18.188
I get
testing: Server reports permission denied
It turns out that for some reason "localhost" doesn't work with "testing" in
my environment. If I use the hostname of the machine, or "127.0.0.1" or
"localhost.{domain}" (substitute the domain for {domain}) it works fine. I
can poke addresses in with "testing" and check them with db_dump, everything
checks out there. So, drac works fine... just not with "localhost".
Next issue: getting drac to work with sendmail version 8.12.1 -- the latest
as of this writing. The instructions say to put the drac rules in the cf
file just before the
# anything else is bogus
R$* $#error $@ 5.7.1 $: "550 Relaying denied"
in the SBasic_check_rcpt ruleset. This works fine... except that sendmail
8.12 by default rejects unresolvable ip's, and the client ip doesn't resolve
(typical of dialup) so he denies based on unresolvable IP before getting to
the drac rules. So, the rules need to go a bit before then. I put it in
SBasic_check_rcpt thus:
R$* $: $1 $| @ $>"Rcpt_ok" $1
R$* $| @ $#TEMP $+ $: $1 $| T $2
R$* $| @ $#$* $#$2
R$* $| @ RELAY $@ RELAY
# start drac rules: allow recent POP/IMAP mail clients to relay
R$* $: $&{client_addr}
R$+ $: $(drac $1 $: ? $)
R? $:
R$+ $@ RELAYFROM
# end drac rules
R$* $| @ $* $: O $| $>"Relay_ok" $1
R$* $| T $+ $: T $2 $| $>"Relay_ok" $1
R$* $| $#TEMP $+ $#error $2
R$* $| $#$* $#$2
R$* $| RELAY $@ RELAY
R T $+ $| $* $#error $1
# anything else is bogus
R$* $#error $@ 5.7.1 $: "550 Relaying denied"
That seems to work without breaking other things. It was a bit easier to
test whether sendmail was still rejecting unresolved IP's while allowing
drac-authorized unresolved IP's because qpopper wasn't yet configured to use
drac -- so I could add/remove myself from the drac db at will and verify the
results.
Next, getting qpopper to compile with drac. As mentioned in the previous
post, I got the dreaded
Can't use DRAC: dracauth not found in -ldrac
error from configure. But libdrac.a was in the right places -- all of them!
It turns out that it WAS finding dracauth, but had some unreferenced symbols
that drac uses from other libraries and the configure error message was
inaccurate -- probably should have just mentioned there was something wrong
with dracauth. Here's the telltale snippet from config.log:
configure:3974: gcc -o conftest -g -O2 -fpcc-struct-return
conftest.c -ldrac
-L/usr/lib/libdrac.a -ldrac -lposix4 -lcrypt 1>&5
Undefined first referenced
symbol in file
xdr_enum /usr/local/lib/libdrac.a(drac_xdr.o)
clnt_create /usr/local/lib/libdrac.a(dracauth.o)
clnt_sperror /usr/local/lib/libdrac.a(dracauth.o)
xdr_u_long /usr/local/lib/libdrac.a(drac_xdr.o)
clnt_spcreateerror /usr/local/lib/libdrac.a(dracauth.o)
ld: fatal: Symbol referencing errors. No output written to conftest
So I went back to the Makefile for drac to see what other libraries he was
using, did a bit of trial-and-error testing, and discovered that "-lnsl" is
needed along with "-ldrac". There's a few places in the configure file for
qpopper that need to be changed. Search for "-ldrac" and change it to
"-ldrac -lnsl". Now qpopper configures properly.
One last thing: Remember that "localhost" didn't work for drac? And
"localhost" is the default drac server... so ya gotta change it, via a "-D
127.0.0.1" argument for qpopper. For instance, my inetd.conf contains:
pop3 stream tcp nowait root /usr/local/sbin/popper qpopper -D 127.0.0.1 -f
/etc/mail/pop.conf
Summary:
1. use "127.0.0.1" instead of "localhost" for any instance of a dracauth()
call:
a. for the drac "testing" utility,
b. for qpopper, via the "-D 127.0.0.1" command-line option.
2. drac rules for sendmail.cf go before the $#error rules in the
SBasic_check_rcpt ruleset.
3. change "-ldrac" to "-ldrac -lnsl" in qpopper "configure" script.
Hope this helps someone!
Paul McKinley
> -----Original Message-----
> From: Paul McKinley
> Sent: Friday, November 16, 2001 11:20 PM
> To: Subscribers of Qpopper
> Subject: DRAC with qpopper 4.0.3 on Solaris
>
>
> qpopper 4.0.3
> DRAC version is 1.11, libdrac.a installed in /usr/lib
> BerkeleyDB.3.3 installed
> Solaris 8 with MU3
>
> qpopper configure line is:
> configure --with-openssl=/usr/local/ssl --enable-specialauth
> --enable-timing
> --enable-apop --with-popuid=pop --enable-log-facility=local1
> --enable-log-l
> ogin --with-drac=/usr/lib
>
> The configure fails on dracauth:
> ....
> checking for set_auth_parameters in -lsecurity... no
> checking for crypt in -lcrypt... yes
> checking for dracauth in -ldrac... no
> Can't use DRAC: dracauth not found in -ldrac
>
> strings /usr/lib/libdrac.a | grep dracauth
> dracauth
> dracauth.o/ 1005971984 1000 14 100644 52244 `
> dracauth.c
> dracauth.c
> dracauth:F(0,1)
> dracauth.c
> dracauth
>
> So, why doesn't he see dracauth?
> Thanks in advance,
> Paul McKinley
>
>
>
>
From: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 19 Nov 2001 21:21:12 -0800
Subject: Re: Solution: DRAC with qpopper 4.0.3 on Solaris
On Mon, 19 Nov 2001 16:01:07 -0600, Paul McKinley wrote:
>Summary:
>1. use "127.0.0.1" instead of "localhost" for any instance of a dracauth()
>call:
> a. for the drac "testing" utility,
> b. for qpopper, via the "-D 127.0.0.1" command-line option.
This sounds like a resolver issue. One usually finds localhost defined
in /etc/hosts. Does Solaris not provide that entry?
>2. drac rules for sendmail.cf go before the $#error rules in the
>SBasic_check_rcpt ruleset.
I recommend putting this in sendmail.mc, which is compiled with m4 to
become sendmail.cf. Does the m4 divert macro used to place the rules in
sendmail.mc need to change to move the rules to an earlier section?
>3. change "-ldrac" to "-ldrac -lnsl" in qpopper "configure" script.
Good catch. This is where package-based installations work well, as a
DRAC package would not install if a prerequisite library were not
present. You would have found out about this problem when you installed
DRAC.
I suspect it's hard for a configure script to guess *why* a particular
library is failing to work. That's why it prints the detailed error
info, so you can take it from there.
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: "Kenneth Porter" <shiva at well dot com>
Date: Mon, 19 Nov 2001 22:34:59 -0800
Subject: RE: Solution: DRAC with qpopper 4.0.3 on Solaris
On Mon, 19 Nov 2001 23:56:09 -0600, Paul McKinley wrote:
>Yes, localhost is in /etc/hosts. No apparent issue with localhost,
>resolution, etc, except that drac doesn't understand it... in this
>environment. Could be something else is wrong, but I think I've checked all
>the right stuff.
I looked into this and it looks like dracauth passes the hostname to
RPC's clnt_create. For Linux, this is in glibc, and I didn't chase it
down into that. Could be that glibc uses the nss stuff to search
/etc/hosts before DNS, but Solaris RPC just looks at DNS.
>drac cf rules: see drac instructions. Unfortunately I'm not up to speed
>sufficiently at the moment with m4 to figure out how to get the rules to go
>in the right place with features or hacks, I'd prefer it to be a single
>feature that does the entire drac thing. So I follow the directions. The
>directions didn't quite work, so I posted the workaround.
When Red Hat packages sendmail 8.12, I expect I'll have to face this
myself. I'll report back what I find. (Red Hat is still packaging
8.11.6.)
>The nsl library is native to solaris 8 as I've installed it -- but popper
>configure doesn't know to include it unless you tell him to. It's not a
>dependency issue, it's a qpopper-with-drac-on-solaris configure issue.
Ah, thanks for the clarification. nsl is part of the glibc package on
Linux, and I don't see it referenced in any qpopper Makefiles, so I
don't know why the Linux system picks it up automatically and Solaris
doesn't. It *is* mentioned in the qpopper configure script, but I don't
know why. I don't see the tested API used in any C or H files.
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: "beepee" <baling at freemail dot hu>
Subject: qpopper + ssl
Date: Tue, 20 Nov 2001 15:13:55 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0095_01C171D5.F8B5C7C0
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Hi,
i run a debian server with pop3ssl (qpopper 4.0.3). If im trying to
connect
to my servers port 995 i recevie an error message:
telnet localhost 995
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
i compiled with ./configure --with-openssl=path-to-openssl
my inetd.conf looks like this:
pop3s stream tcp nowait root /usr/local/sbin/popper
-s -f
/etc/mail/pop/qpopper.conf
my qpopper.conf:
set clear-text-password = ssl
set tls-support = alternate-port
set tls-version = default
set tls-server-cert-file = /etc/mail/cert/cert.pem
and when iam trying to reach the server with outlook experss ive got the
same error.
what can be the problem?
thx.
beepee
------=_NextPart_000_0095_01C171D5.F8B5C7C0
Content-Type: text/html;
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-2"
http-equiv=Content-Type>
<META content="MSHTML 5.00.2920.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,<BR><BR>i run a debian server with
pop3ssl
(qpopper 4.0.3). If im trying to connect<BR>to my servers port 995 i
recevie an
error message:<BR>telnet localhost 995<BR>Trying
127.0.0.1...<BR>Connected to
localhost.<BR>Escape character is '^]'.<BR>Connection closed by foreign
host.<BR><BR>i compiled with ./configure
--with-openssl=path-to-openssl<BR>my
inetd.conf looks like
this:<BR>pop3s  
;
stream tcp nowait
root
/usr/local/sbin/popper -s -f<BR>/etc/mail/pop/qpopper.conf<BR>my
qpopper.conf:<BR>set clear-text-password =
ssl<BR>set
tls-support &n
bsp; =
alternate-port<BR>set
tls-version &n
bsp; =
default<BR>set tls-server-cert-file =
/etc/mail/cert/cert.pem<BR><BR>and when iam trying to reach the server
with
outlook experss ive got the<BR>same error.<BR>what can be the
problem?<BR>thx.<BR>beepee<BR><BR><BR></FONT></DIV></BODY></HTML>
------=_NextPart_000_0095_01C171D5.F8B5C7C0--
Date: Tue, 20 Nov 2001 10:27:44 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: qpopper + ssl
At 09:13 AM 11/20/01, you wrote:
>Hi,
>
>i run a debian server with pop3ssl (qpopper 4.0.3). If im trying to connect
>to my servers port 995 i recevie an error message:
>telnet localhost 995
>Trying 127.0.0.1...
>Connected to localhost.
>Escape character is '^]'.
>Connection closed by foreign host.
>
>i compiled with ./configure --with-openssl=path-to-openssl
>my inetd.conf looks like this:
>pop3s stream tcp nowait root /usr/local/sbin/popper -s -f
>/etc/mail/pop/qpopper.conf
That part looks OK, though you may want to be using tcp wrappers (always a
good idea).
>my qpopper.conf:
>set clear-text-password = ssl
>set tls-support = alternate-port
>set tls-version = default
>set tls-server-cert-file = /etc/mail/cert/cert.pem
You're missing a 'set tls-private-key-file' line.
I expect that's having an impact.
>and when iam trying to reach the server with outlook experss ive got the
>same error.
>what can be the problem?
>thx.
>beepee
>
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
From: "Kenneth Porter" <shiva at well dot com>
Date: Tue, 20 Nov 2001 20:12:36 -0800
Subject: Re: qpopper + ssl
On Tue, 20 Nov 2001 15:13:55 +0100, beepee wrote:
>my inetd.conf looks like this:
>pop3s stream tcp nowait root /usr/local/sbin/popper -s -f
>/etc/mail/pop/qpopper.conf
Pay close attention to the requirements for this line.
There should be *2* program names. One is the file that inetd will
invoke, and the 2nd is the value that inetd will pass to the program as
argv[0]. Your config line is using /usr/local/sbin/popper as the
program filename, but is passing -s as argv[0]. Usually you want
"popper" there.
If you use tcp_wrappers, then the program filename will be tcpd, and
argv[0] will be /usr/local/sbin/popper.
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: Wed, 21 Nov 2001 01:57:10 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: my Qpopper isn't seeing any messages
org> <20011119124218.A1948 at hoffy.gnc.net> <p05100300b81f1db7fdee at [129.46 dot 156 dot 156]> <
Date: Wed, 21 Nov 2001 10:22:26 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: qpopper + ssl
> If you use tcp_wrappers, then the program filename will be tcpd, and
> argv[0] will be /usr/local/sbin/popper.
What is tcp_wrappers, anyway? What does it do?
Date: Wed, 21 Nov 2001 15:46:38 +0000
From: peter.allen at moon-light.co dot uk
Subject: Re: qpopper + ssl
At 10:22 21/11/01 +0000, Rick Hoffman wrote:
> > If you use tcp_wrappers, then the program filename will be tcpd, and
> > argv[0] will be /usr/local/sbin/popper.
>
>What is tcp_wrappers, anyway? What does it do?
A good way to do access control for any service that runs out of inetd such
as (potentially) ftp, popper, finger, telnet etc, by limiting which IP
addresses can and cannot use those services.
You can learn more from looking at the tcpd man pages.
Of course this has the same effect as a decent firewall but provides an
additional depth to your security.
Peter
Date: Wed, 21 Nov 2001 11:09:28 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: qpopper + ssl
At 10:46 AM 11/21/01, peter.allen at moon-light.co dot uk wrote:
>At 10:22 21/11/01 +0000, Rick Hoffman wrote:
>> > If you use tcp_wrappers, then the program filename will be tcpd, and
>> > argv[0] will be /usr/local/sbin/popper.
>>
>>What is tcp_wrappers, anyway? What does it do?
>
>A good way to do access control for any service that runs out of inetd
>such as (potentially) ftp, popper, finger, telnet etc, by limiting which
>IP addresses can and cannot use those services.
Also any daemon application which cares to make library calls to the
wrapper library. I build sendmail with wrapper support. This permits me
another method for blocking spammers, especially if what I'm trying to
block is a large subnet from a spamhaus, or some such.
>You can learn more from looking at the tcpd man pages.
>
>Of course this has the same effect as a decent firewall but provides an
>additional depth to your security.
I use routers for first line, ipchains for second line, and tcp wrappers
for third line. The advantage of wrappers is the ability to deny based on
DNS naming, including anything within a domain. Changing ACLs in the router
is the least-preferred method since it is the most annoying to change and
have take effect, but it does cover all systems. Changes in ipchains are
next easier, but only IP address based (the way our setups work, at least).
So wrappers provides a useful level too.
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Date: Wed, 21 Nov 2001 18:23:09 +0000
From: Rick Hoffman <hoffy at gnc dot net>
Subject: Re: qpopper + ssl
Daniel wrote:
> Also any daemon application which cares to make library calls to the
> wrapper library. I build sendmail with wrapper support. This permits me
> another method for blocking spammers, especially if what I'm trying to
> block is a large subnet from a spamhaus, or some such.
Peter wrote:
> >Of course this has the same effect as a decent firewall but provides an
> >additional depth to your security.
Daniel wrote:
> I use routers for first line, ipchains for second line, and tcp wrappers
> for third line. The advantage of wrappers is the ability to deny based on
> DNS naming, including anything within a domain. Changing ACLs in the router
> is the least-preferred method since it is the most annoying to change and
> have take effect, but it does cover all systems. Changes in ipchains are
> next easier, but only IP address based (the way our setups work, at least).
> So wrappers provides a useful level too.
I think I understand. IP_chains can be considered as like a first-line
filter and tcp_wrappers a second? I'm guessing that incoming traffic first
is processed by IP_chains and then is passed on to ports where tcp_wrappers
can pick it up if you are using it. Is that right?
So I guess since you say Daniel, that you build sendmail with wrapper
support you must not be running sendmail with inetd *and* you don't have to
explicitly invoke tcp_wrappers through a command line or something.
If I am correct with these assumsuptions I can see how you can use an
IP_chains/tcp_wrappers combination to allow access for specific IP_addresses
to some services on your network but not with others.
That's interesting. Thanks.
Also, "tcpd". Does the 'd' mean dameon? I guess that means you can constantly
run tcp_wrappers? If so then why would you have to build the support into
a particular service if it can always be running anyway? Maybe I'm a little
confused about that.
Date: Thu, 22 Nov 2001 00:54:37 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: qpopper + ssl
At 01:23 PM 11/21/01, Rick Hoffman wrote:
>Daniel wrote:
> > Also any daemon application which cares to make library calls to the
> > wrapper library. I build sendmail with wrapper support. This permits me
> > another method for blocking spammers, especially if what I'm trying to
> > block is a large subnet from a spamhaus, or some such.
>
>Peter wrote:
> > >Of course this has the same effect as a decent firewall but provides an
> > >additional depth to your security.
>
>Daniel wrote:
> > I use routers for first line, ipchains for second line, and tcp wrappers
> > for third line. The advantage of wrappers is the ability to deny based on
> > DNS naming, including anything within a domain. Changing ACLs in the
> router
> > is the least-preferred method since it is the most annoying to change and
> > have take effect, but it does cover all systems. Changes in ipchains are
> > next easier, but only IP address based (the way our setups work, at
> least).
> > So wrappers provides a useful level too.
>
>I think I understand. IP_chains can be considered as like a first-line
>filter and tcp_wrappers a second? I'm guessing that incoming traffic first
>is processed by IP_chains and then is passed on to ports where tcp_wrappers
>can pick it up if you are using it. Is that right?
That's how I use it and view it. IP chains works at the packet level as
packets arrive from interfaces or are delivered to interfaces. TCP Wrappers
gets involved when connections are established, but is not involved on a
packet-by-packet basis.
>So I guess since you say Daniel, that you build sendmail with wrapper
>support you must not be running sendmail with inetd *and* you don't have to
>explicitly invoke tcp_wrappers through a command line or something.
Any application which uses the Wrappers library can get the benefits of
wrappers without having to invoke via inetd or equivalent. In the case of
sendmail, running from inetd isn't really practical (its not impossible,
but really not generally done or recommended). By building with wrappers, I
can explicitly allow or block whatever I wish. If I don't want to receive
mail from a particular host, I can put that into /etc/hosts.allow. In
reality, I could also add IP chains filters in many cases as well. In the
sendmail case, I can also use the access.db within sendmail for much of
this. There are many ways to approach this issue.
>If I am correct with these assumsuptions I can see how you can use an
>IP_chains/tcp_wrappers combination to allow access for specific IP_addresses
>to some services on your network but not with others.
Yep.
>That's interesting. Thanks.
>
>Also, "tcpd". Does the 'd' mean dameon? I guess that means you can
>constantly
>run tcp_wrappers? If so then why would you have to build the support into
>a particular service if it can always be running anyway? Maybe I'm a little
>confused about that.
Daemon (correcting your spelling). Yes that's what the 'd' is for. Running
constantly? No. The tcpd gets launched by inetd or xinetd.
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Subject: Re: qpopper + ssl
Date: Thu, 22 Nov 2001 10:50:40 +0100 (MET)
From: Eric Luyten <Eric.Luyten at vub.ac dot be>
> ... In the case of
> sendmail, running from inetd isn't really practical (its not impossible,
> but really not generally done or recommended).
We handle incoming SMTP connections via inetd-invoked sendmail on our
largest mail server (20,000+ accounts) and our two external mail relays.
Those are Sun Solaris systems (6-proc. E4000, 1-proc. E250 and 4-proc. E450)
and handle tens of thousands of SMTP connections per day. No ill effects ;
we are working like this for over a year.
The /etc/hosts.allow file now allows us to return a particular SMTP code
to a certain host or to divert incoming messages in an alternate queue,
which is a great help to put virus-infected PC's "in quarantaine" for a
while to verify whether they behave properly following disinfection.
Feel free to e-mail me for examples or discussion.
Eric Luyten, Computing Centre VUB/ULB.
From: Jens <jens at pacificsun dot ca>
Subject: PAM authentication failure (7) and more
Date: Thu, 22 Nov 2001 15:04:24 -0800
Hi
I have several little things that are driving me absolutely nuts because I
can't seem to figure them out ..... any help is appreciated.
When I telnet to localhost 110 on the machine that qpopper is installed,
everything seems ok. I enter 'user username' to which qpopper replies that a
password is required. I then enter 'pass password' and after contemplating
life for some time, qpopper tells me that there is a PAM authentication
failure (7).
In a possibly related situation, I see 'can't get canonical name' errors in
my mail log when logging in from an outside connection. Qpopper is called
from inetd and I have added the -R option to the 'in.qpopper' startup command
in hopes of eliminating this message but to no avail.
I have been trying different things for quite some time but I just don't seem
to be hitting the right combinations since I can't get rid of the errors
..... HELP !!!
Jens
From: Jens <jens at pacificsun dot ca>
Subject: Re: PAM authentication failure (7) and more
Date: Thu, 22 Nov 2001 22:29:06 -0800
On November 22, 2001 03:04 pm, you wrote:
> In a possibly related situation, I see 'can't get canonical name' errors in
> my mail log when logging in from an outside connection. Qpopper is called
> from inetd and I have added the -R option to the 'in.qpopper' startup
> command in hopes of eliminating this message but to no avail.
Got that one figured out - case of 'operator error'
I am still getting the PAM authentication failures when trying to log in
directly. One thing I forgot to mention is that remote users using their own
mail program can get their mail just fine. Only when I try to access qpopper
directly through port 110 and then the 'user' and 'pass' commands do I get
these errors.
BTW, I am using Debian (unstable) with kernel 2.4.12 and qpopper 4.03 from a
deb package.
Jens
Date: Fri, 23 Nov 2001 18:14:17 +0800
From: Peter Santiago <petersantiago at bigfoot dot com>
Subject: qpopper won't start
Below is the error messages I'm getting. I'm using Exim as MTA. Prior to
CPU upgrade, qpopper worked flawlessly. I don't know what happened. Right
now I'm using kernel 2.4.7-10 (RH 7.2).
Nov 23 15:04:17 linbox in.qpopper[3707]: Unable to obtain socket and
address of client: Socket operation on non-socket (88) [pop_init.c:1029]
Nov 23 15:04:22 linbox in.qpopper[3708]: Unable to obtain socket and
address of client: Socket operation on non-socket (88) [pop_init.c:1029]
From: "beepee" <baling at freemail dot hu>
Subject: qpopper + ssl
Date: Fri, 23 Nov 2001 18:40:39 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0022_01C1744E.59317890
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
please help me: When i want to download my letter from the server using
pop3ssl (qpopper 4.0.3), my server writes this in its lockfile:
Nov 22 12:15:18 draco popper[9455]: ...SSL error: error:0200100E:system
library:fopen:Bad address
Nov 22 12:15:18 draco popper[9455]: Failed initializing TLS/SSL
Nov 22 12:16:20 draco popper[9458]: ...SSL error: error:0200100E:system
library:fopen:Bad address
Nov 22 12:16:20 draco popper[9458]: Failed initializing TLS/SSL
i dont know what to do.......
thx
beepee
------=_NextPart_000_0022_01C1744E.59317890
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=iso-8859-1">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>please help me: When i want to download
my letter
from the server using pop3ssl (qpopper 4.0.3), my server writes this in
its
lockfile:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Nov 22 12:15:18 draco popper[9455]: ...SSL error:
error:0200100E:system
library:fopen:Bad address<BR>Nov 22 12:15:18 draco popper[9455]: Failed
initializing TLS/SSL<BR>Nov 22 12:16:20 draco popper[9458]: ...SSL
error:
error:0200100E:system library:fopen:Bad address<BR>Nov 22 12:16:20 draco
popper[9458]: Failed initializing TLS/SSL</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>i dont know what to
do.......</FONT></DIV>
<DIV><FONT face=Arial size=2>thx </FONT></DIV>
<DIV><FONT face=Arial size=2>beepee</FONT><BR></DIV></BODY></HTML>
------=_NextPart_000_0022_01C1744E.59317890--
Date: Fri, 23 Nov 2001 12:20:44 -1000
From: Clifton Royston <cliftonr at lava dot net>
Subject: Re: qpopper won't start
On Fri, Nov 23, 2001 at 06:14:17PM +0800, Peter Santiago wrote:
> Below is the error messages I'm getting. I'm using Exim as MTA. Prior to
> CPU upgrade, qpopper worked flawlessly. I don't know what happened. Right
> now I'm using kernel 2.4.7-10 (RH 7.2).
>
> Nov 23 15:04:17 linbox in.qpopper[3707]: Unable to obtain socket and
> address of client: Socket operation on non-socket (88) [pop_init.c:1029]
> Nov 23 15:04:22 linbox in.qpopper[3708]: Unable to obtain socket and
> address of client: Socket operation on non-socket (88) [pop_init.c:1029]
How are you starting qpopper in this example? Is it being started from
inetd or xinetd?
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- cliftonr at lava dot net
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
From: Michael Motal <michi at topfen dot net>
Subject: Re: qpopper won't start
Date: Sat, 24 Nov 2001 15:27:04 +0100
On Friday 23 November 2001 23:20, Clifton Royston used many innocent IP
packets to transport this:
> > Nov 23 15:04:17 linbox in.qpopper[3707]: Unable to obtain socket and
> > address of client: Socket operation on non-socket (88) [pop_init.c:1029]
> > Nov 23 15:04:22 linbox in.qpopper[3708]: Unable to obtain socket and
> > address of client: Socket operation on non-socket (88) [pop_init.c:1029]
this normally happens, if qpopper is compiled as non-standalone server and is
*not* started through inetd. Did you reconfigure/recompile qpopper?
--
I love deadlines. I love the whooshing sound they make as they fly by.
-- Douglas Adams
From: "Peter Santiago" <petersantiago at bigfoot dot com>
Subject: RE: qpopper won't start
Date: Sat, 24 Nov 2001 21:50:33 +0800
well, it's a rpm package. And I started it from xinetd.
# qpopper config file for xinetd
service pop3
{
flags = REUSE NAMEINARGS
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/in.qpopper
server_args = in.qpopper -s
}
thanks
-----Original Message-----
From: Michael Motal [mailto:michi at topfen dot net]
Sent: Saturday, November 24, 2001 10:27 PM
To: Subscribers of Qpopper
Subject: Re: qpopper won't start
On Friday 23 November 2001 23:20, Clifton Royston used many innocent IP
packets to transport this:
> > Nov 23 15:04:17 linbox in.qpopper[3707]: Unable to obtain socket and
> > address of client: Socket operation on non-socket (88) [pop_init.c:1029]
> > Nov 23 15:04:22 linbox in.qpopper[3708]: Unable to obtain socket and
> > address of client: Socket operation on non-socket (88) [pop_init.c:1029]
this normally happens, if qpopper is compiled as non-standalone server and
is
*not* started through inetd. Did you reconfigure/recompile qpopper?
--
I love deadlines. I love the whooshing sound they make as they fly by.
-- Douglas Adams
From: "Michael Motal" <michi at topfen dot net>
Subject: RE: qpopper won't start
Date: Sat, 24 Nov 2001 19:05:25 +0100 (CET)
> well, it's a rpm package. And I started it from xinetd.
what do you mean by CPU upgrade?
hardware upgrade? reinstall?
> # qpopper config file for xinetd
> service pop3
> {
> flags = REUSE NAMEINARGS
> socket_type = stream
> protocol = tcp
> wait = no
> user = root
> server = /usr/sbin/in.qpopper
> server_args = in.qpopper -s
> }
this looks ok, afaik...
you could try reinstalling qpopper from source
(www.eudora.com/qpopper)...
please let me know of your progress!
lg, michi
Date: Mon, 26 Nov 2001 13:10:36 +0500
From: Qpopper <qpopper at crestarnet dot net>
Subject: POP Before SMTP.
Hi,
I am using the WU ipop3d and have recently shifted to Qpopper 4, can
anybody guide me how to configure the POP before SMTP feature with the
qpopper version 4. I am using sendmail 8.12.1 on Solaris 8.
Regards,
Sohail
Date: Mon, 26 Nov 2001 07:24:51 -0800 (PST)
From: Gregory Hicks <ghicks at cadence dot com>
Subject: Re: POP Before SMTP.
> Date: Mon, 26 Nov 2001 13:10:36 +0500
> From: Qpopper <qpopper at crestarnet dot net>
>
> I am using the WU ipop3d and have recently shifted to Qpopper 4, can
> anybody guide me how to configure the POP before SMTP feature with the
> qpopper version 4. I am using sendmail 8.12.1 on Solaris 8.
POP before SMTP is configured on the client...
Regards,
Gregory Hicks
>
> Regards,
>
> Sohail
>
---------------------------------------------------------------------
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
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
"The trouble with doing anything right the first time is that nobody
appreciates how difficult it was."
When a team of dedicated individuals makes a commitment to act as
one... the sky's the limit.
Date: Mon, 26 Nov 2001 10:49:27 -0500
From: Daniel Senie <dts at senie dot com>
Subject: Re: POP Before SMTP.
At 03:10 AM 11/26/01, Qpopper wrote:
>Hi,
>
>I am using the WU ipop3d and have recently shifted to Qpopper 4, can
>anybody guide me how to configure the POP before SMTP feature with the
>qpopper version 4. I am using sendmail 8.12.1 on Solaris 8.
There's DRAC, which is presently supported in qpopper 4.0.3. DRAC is called
when users request their mail and successfully authenticate to QPOPPER. The
downside to DRAC, and the main reason I don't use it is its reliance on
SunRPC. We don't use or want that on our mail servers. Since you run a
Solaris setup, though, you really have no choice but to have SunRPC active
anyway. So, check out DRAC.
We use POPDB, a mechanism we developed. It operates on a single server
only. It is called by popper when users authenticate, and adds users to a
hash database file that's then used by sendmail. The POPPER changes for
this have been submitted and will hopefully show up in a future release.
The POPDB component itself will be available as a free distribution (not
sure which copyright yet) shortly. Anyone interested is welcome to contact
me. POPDB is limited to a single machine, but is a lighter-weight solution
to the problem than is DRAC.
-----------------------------------------------------------------
Daniel Senie dts at senie dot com
Amaranth Networks Inc. http://www.amaranth.com
Date: Mon, 26 Nov 2001 18:26:38 -0800
From: Randall Gellens <randy at qualcomm dot com>
Subject: Re: PAM authentication failure (7) and more
At 3:04 PM -0800 11/22/01, Jens wrote:
>When I telnet to localhost 110 on the machine that qpopper is installed,
>everything seems ok. I enter 'user username' to which qpopper replies that a
>password is required. I then enter 'pass password' and after contemplating
>life for some time, qpopper tells me that there is a PAM authentication
>failure (7).
Try enabling debug tracing in Qpopper at least, and also in the
various PAM modules, if possible. This may at least give more
information.
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'.
--
--
Date: Tue, 27 Nov 2001 10:47:08 +0530
From: Anil Shewale <anil.shewale at timesgroup dot com>
Subject: Mail gets downloaded again on changing server.
Dear All
We are using qpopper and Sendmail as POP3 and SMTP service. We are
in process of changing server. We have copied all mail boxes on new
server, but when users do pop for new messages entire mail box (New and
Old Mails) gets downloaded on users pc. Since volume of users and Mail
Box is very high this will create problem for us. We keep messages on
server for webmail access, so users mail client (Netscape / Outlook
etc.) is configured to Leave messages on server.
Now how do i stop mails getting downloaded again whenever we change the server?
This is very critical for us as because of server installation has stopped.
Thank You
Anil Shewale
Times of India
Technical Support Cell
Times of India Building
Dr. D. N. Road, Fort,
Mumbai 400001
India
Tel. No. : Board - 2353535 Ext. 4109
Direct - 2354109
Fax. No. : Network - 2731101/02 Ext. 4109
Direct - 2731023
Last updated on 26 Nov 2001 by Pensive Mailing List Admin