qmail Digest 28 Mar 1999 11:00:01 -0000 Issue 593
Topics (messages 23552 through 23571):
poor documentation example
23552 by: Jay Soffian <[EMAIL PROTECTED]>
23553 by: Mark Delany <[EMAIL PROTECTED]>
23555 by: Russell Nelson <[EMAIL PROTECTED]>
23567 by: Russ Allbery <[EMAIL PROTECTED]>
23568 by: Jay Soffian <[EMAIL PROTECTED]>
23569 by: Vince Vielhaber <[EMAIL PROTECTED]>
23570 by: Russ Allbery <[EMAIL PROTECTED]>
23571 by: "Scott D. Yelich" <[EMAIL PROTECTED]>
pop3 "password rejected"
23554 by: "Chris Johnson" <[EMAIL PROTECTED]>
23556 by: Greg <[EMAIL PROTECTED]>
23558 by: Fabrice Scemama <[EMAIL PROTECTED]>
Aliases - silly newbie question but I can't figure it out
23557 by: Chris Green <[EMAIL PROTECTED]>
23564 by: Paul Farber <[EMAIL PROTECTED]>
serialmail & net
23559 by: Ralf Nagel <[EMAIL PROTECTED]>
23560 by: Fabrice Scemama <[EMAIL PROTECTED]>
23562 by: Ralf Nagel <[EMAIL PROTECTED]>
23563 by: Fabrice Scemama <[EMAIL PROTECTED]>
23565 by: Eric Dahnke <[EMAIL PROTECTED]>
Qmail + NFS
23561 by: Pedro Melo <[EMAIL PROTECTED]>
serialmail/qmail workaround needed
23566 by: Eric Dahnke <[EMAIL PROTECTED]>
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
"Scott" == Scott D Yelich <[EMAIL PROTECTED]> writes:
>> I've had tcpserver compile just fine even with HP's broken
>> compiler. It seems as if you're trying to find fault just to
>> try and prove your point. If you know/knew in advance of your
>> non-standard compiler setup you'd be prepared for it.
Scott> *sigh*
Scott> You just don't get it... do you.
Scott> I have a standard compiler set up. I have gcc. I do not
Scott> have cc.
Scott> I get 99% of my programs in source and they tell me to edit
Scott> the Make file and change the "cc" line to "gcc" or to type
Scott> ./Configure. Both of these get me to compile (maybe I have
Scott> to define solaris, etc.) just fine.
Scott> Then comes qmail, et al., does it use Makefile with CC=gcc?
Scott> no. Does it use ./Configure? no. It says "type make; make
Scott> config check; # that's all!"
Scott> BUT IT IS NOT ALL.
Scott> That's all (I'm trying to say).
Well, at least I agree with this. tcpserver is the ONLY package (well,
not including other djb packages which have this same breakage) I have
ever compiled where not even this works:
make CC=gcc
Also, none of djb's packages like the idea of compiling a program to
look in one place and installing it in another. We use depot for all
our package installes, so we compile packages to look in /usr/local,
but install them in /depot/col/<package_name>. All of djb's packages
require extra work to get them to install this way. For qmail, it
isn't that big a deal because we put it in /var/qmail, but for
tcpserver and other djb packages, we want them depotized. For pacakges
that use GNU autoconf, this is trivial. 'make install
prefix=/depot/col/<package_name>' and you're done. For all of djb's
stuff, you either install by hand or futz around with the various
conf-FOO files and make sure you preserve their timestamps when
editing them after you've built the package. blech.
But I'm sure djb knows his way is better, so this is all a waste of
breath now, isn't it.
j.
--
Jay Soffian <[EMAIL PROTECTED]> UNIX Systems Administrator
404.572.1941 Cox Interactive Media
>But I'm sure djb knows his way is better, so this is all a waste of
>breath now, isn't it.
So lemme get this right. Dan B. has written and made freely available an MTA
that many people like. Russell N. has set up a web site to help distribute
information about that MTA. Numerous others are running mirrors for the web
site and ftp archives all over the planet. Plenty of people have made
patches and alternative distributions freely available. Even more people
have provided thousands of hours of free support on this list and Dave S. is
running a free web site that archives this list for future prosperity.
And the best you have to offer is what? A sarcastic tirade?
A truly stunning contribution.
Regards.
Mark Delany writes:
> Even more people have provided thousands of hours of free support
> on this list
Your modesty becomes you. Mark D. is one of the people who provides
that support, and an excellent job you do, too.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
Jay Soffian <[EMAIL PROTECTED]> writes:
> Also, none of djb's packages like the idea of compiling a program to
> look in one place and installing it in another. We use depot for all our
> package installes, so we compile packages to look in /usr/local, but
> install them in /depot/col/<package_name>. All of djb's packages require
> extra work to get them to install this way. For qmail, it isn't that big
> a deal because we put it in /var/qmail, but for tcpserver and other djb
> packages, we want them depotized. For pacakges that use GNU autoconf,
> this is trivial. 'make install prefix=/depot/col/<package_name>' and
> you're done. For all of djb's stuff, you either install by hand or futz
> around with the various conf-FOO files and make sure you preserve their
> timestamps when editing them after you've built the package. blech.
make
make install
./install /depot/col/<package>/bin < BIN
./install /depot/col/<package>/man < MAN
If that's too much to type each time, make a local patch to Makefile that
gets the installatin locations from conf-instbin and conf-instman instead
and creates those files with the installation paths you want.
(Your package manager *does* seamlessly allow you to keep local patches to
a package, right?)
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
"Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
Russ> make
Russ> make install
Russ> ./install /depot/col/<package>/bin < BIN
Russ> ./install /depot/col/<package>/man < MAN
For what is that supposed to work? It doesn't work for ucspi-tcp-0.84.
j.
--
Jay Soffian <[EMAIL PROTECTED]> UNIX Systems Administrator
404.572.1941 Cox Interactive Media
On 28-Mar-99 Jay Soffian wrote:
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
>
> Russ> make
> Russ> make install
> Russ> ./install /depot/col/<package>/bin < BIN
> Russ> ./install /depot/col/<package>/man < MAN
>
> For what is that supposed to work? It doesn't work for ucspi-tcp-0.84.
# make
# make setup check
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Jay Soffian <[EMAIL PROTECTED]> writes:
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
> Russ> make
> Russ> make install
> Russ> ./install /depot/col/<package>/bin < BIN
> Russ> ./install /depot/col/<package>/man < MAN
> For what is that supposed to work? It doesn't work for ucspi-tcp-0.84.
0.80. *grumble* You're right, he changed the way install works. It used
to take input files BIN and MAN. Now it actually compiles the package
locations into everything. How annoying.
Dan, would you consider providing some way for the installation location
to be different than the final run location? Those of us who use AFS with
a reasonably large software installation *require* that; it's not possible
for us to install into the same location that users will run the binaries
from.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
On 27 Mar 1999, Russ Allbery wrote:
> Jay Soffian <[EMAIL PROTECTED]> writes:
> > "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
> > Russ> make
> > Russ> make install
> > Russ> ./install /depot/col/<package>/bin < BIN
> > Russ> ./install /depot/col/<package>/man < MAN
> > For what is that supposed to work? It doesn't work for ucspi-tcp-0.84.
> 0.80. *grumble* You're right, he changed the way install works. It used
> to take input files BIN and MAN. Now it actually compiles the package
> locations into everything. How annoying.
*rofl* I went and looked and said ``Gee, that's kinda nifty --
even if it's not documented anywhere'' ... but, alas, I couldn't
find heads or tails of that. I figured I was just *missing*
it again... and didn't say anything.
I talked to another admin tonight who just installed
qmail-popup. He complained that the install documentation
was pathetic. Hey, I'm just passing along what I hear.
> Dan, would you consider providing some way for the installation location
> to be different than the final run location? Those of us who use AFS with
> a reasonably large software installation *require* that; it's not possible
> for us to install into the same location that users will run the binaries
> from.
Just document it... whatever it is. Please.
Scott
> Hi, well I've got smtp relay working fine, but when I give a
> user a log in account on this box, to enable them to grab their
> mail, with a windoze client their password gets rejected,
> (although I can telnet in with it). ? please point me at some
> docs, as I don't recall seeing anything relating to this
What POP daemon are you using? If it's qmail-pop3d, how are you calling it?
Chris
I'm using qmail-pop3, re: calling it, I think i'm running the
daemon in "supervisor" mode, RH just set it all up, on the
install.
(I'm actually a "Slackware" fan, only had RH running a week to
check
it out also).
The problem appears to be fixed, I think it was to do with the
Mailbox format, as changing to /Maildir/ fixed it.
thanks
Chris Johnson wrote:
>
> > Hi, well I've got smtp relay working fine, but when I give a
> > user a log in account on this box, to enable them to grab their
> > mail, with a windoze client their password gets rejected,
> > (although I can telnet in with it). ? please point me at some
> > docs, as I don't recall seeing anything relating to this
>
> What POP daemon are you using? If it's qmail-pop3d, how are you calling it?
>
> Chris
--
Greg
ICQ# 17606315
Phone : +61 7 4125 1180
... and the box said "windows 95, or better", so I got Linux
_____________________________________________________________
Greg wrote:
>
> Hi, well I've got smtp relay working fine, but when I give a user
> a log in account on this box, to enable them to grab their mail,
> with a windoze client their password gets rejected, (although I
> can telnet in with it). ?
> please point me at some docs, as I don't recall seeing anything
> relating to this?
>
> thanks
> --
> Greg
> ICQ# 17606315
> Phone : +61 7 4125 1180
>
> ... and the box said "windows 95, or better", so I got Linux
> _____________________________________________________________
You might be using shadow then have authentification
problems with you pop3 daemon.
On Thu, Mar 25, 1999 at 10:27:58PM -0000, D. J. Bernstein wrote:
> > What I would really like to do is arrange that all mail for (regex)
> > '.*maxine.*@isbd.demon.co.uk' would go to maxine, is there a simple
> > way to do this?
>
> You could insert something like
>
> |case "_$LOCAL_" in _*maxine*_) forward maxine; esac
>
> at the top of your existing ~alias/.qmail-default.
>
Ah, that sounds ideal, thanks Dan.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Is there a web page or doc that has some more dot-qmail file examples?
Paul D. Farber II
Farber Technology
Ph. 570-628-5303
Fax 570-628-5545
[EMAIL PROTECTED]
On Sat, 27 Mar 1999, Chris Green wrote:
> On Thu, Mar 25, 1999 at 10:27:58PM -0000, D. J. Bernstein wrote:
> > > What I would really like to do is arrange that all mail for (regex)
> > > '.*maxine.*@isbd.demon.co.uk' would go to maxine, is there a simple
> > > way to do this?
> >
> > You could insert something like
> >
> > |case "_$LOCAL_" in _*maxine*_) forward maxine; esac
> >
> > at the top of your existing ~alias/.qmail-default.
> >
> Ah, that sounds ideal, thanks Dan.
>
> --
> Chris Green ([EMAIL PROTECTED])
> Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
> WWW: http://www.isbd.co.uk/
>
Hi,
I am running a small "masqueraded" network (4 linux-machines, 1 NT). The
mail (qmail of course) setup seems to be okay - everything works fine as
far as local and intranet traffic (linux -> linux) is concerned.
But how can I collect all outgoing mail on a central "mail server"
waiting for the next dial up connection for sending out? AND
How can I incorporate the NT-machine (intranet and outgoing)?
Thanks...Ralf
Ralf Nagel wrote:
>
> Hi,
>
> I am running a small "masqueraded" network (4 linux-machines, 1 NT). The
> mail (qmail of course) setup seems to be okay - everything works fine as
> far as local and intranet traffic (linux -> linux) is concerned.
> But how can I collect all outgoing mail on a central "mail server"
> waiting for the next dial up connection for sending out? AND
> How can I incorporate the NT-machine (intranet and outgoing)?
>
> Thanks...Ralf
using Fetchmail (for example), and launching it
with your /etc/ppp/ip-up.local (or whatever you call it).
Fabrice Scemama wrote:
>
> Ralf Nagel wrote:
> >
> > Hi,
> >
> > I am running a small "masqueraded" network (4 linux-machines, 1 NT). The
> > mail (qmail of course) setup seems to be okay - everything works fine as
> > far as local and intranet traffic (linux -> linux) is concerned.
> > But how can I collect all outgoing mail on a central "mail server"
> > waiting for the next dial up connection for sending out? AND
> > How can I incorporate the NT-machine (intranet and outgoing)?
> >
> > Thanks...Ralf
>
> using Fetchmail (for example), and launching it
> with your /etc/ppp/ip-up.local (or whatever you call it
Oh, my bad English, I suppose...
Fabrice, I am using fetchmail for my INCOMING mail!
I would like to put all my OUTGOING mail on a central server
(one of my own linux-machines) using the serialmail package for dial up
outbound.
But thanks for your quick response
Ralf
Ralf Nagel wrote:
>
> Fabrice Scemama wrote:
> >
> > Ralf Nagel wrote:
> > >
> > > Hi,
> > >
> > > I am running a small "masqueraded" network (4 linux-machines, 1 NT). The
> > > mail (qmail of course) setup seems to be okay - everything works fine as
> > > far as local and intranet traffic (linux -> linux) is concerned.
> > > But how can I collect all outgoing mail on a central "mail server"
> > > waiting for the next dial up connection for sending out? AND
> > > How can I incorporate the NT-machine (intranet and outgoing)?
> > >
> > > Thanks...Ralf
> >
> > using Fetchmail (for example), and launching it
> > with your /etc/ppp/ip-up.local (or whatever you call it
>
> Oh, my bad English, I suppose...
> Fabrice, I am using fetchmail for my INCOMING mail!
> I would like to put all my OUTGOING mail on a central server
> (one of my own linux-machines) using the serialmail package for dial up
> outbound.
> But thanks for your quick response
> Ralf
This seems to be working like that by default.
But you need a working DNS on your local SMTP.
Download the serialmail package. The instructions of how to queue all non-local
messages for outbound delivery via a Maildir are in the TOISP file within the
serialmail tar file.
chau - eric
> > Oh, my bad English, I suppose...
> > Fabrice, I am using fetchmail for my INCOMING mail!
> > I would like to put all my OUTGOING mail on a central server
> > (one of my own linux-machines) using the serialmail package for dial up
> > outbound.
> > But thanks for your quick response
> > Ralf
Hi!
I know that a lot of people here use Qmail + NFS to deliver into NetApp's and
boxes like that. My question is: does anybody here does NFS delivery via NFS to
a Linux-based NFS Server? Are you having any stability probs? Which kernel are
you using?
Thanks in advance
---
Pedro Melo <[EMAIL PROTECTED]>
IP - Engenharia de Rede <http://ip.pt/>
Av. Duque de Avila, 23, 1049-071 LISBOA - PORTUGAL
tel: +351 1 3166740/00 (24h/dia) - fax: +351 1 3166701
Hello List,
I've got a dialup client with a qmail/fetchmail/serialmail instalation
acting as their mailgateway. The client wants to restrict some of the
accounts to internal mail use only.
Question is, how can I keep such restricted users' messages from ending
up in serialmail's outgoing pppdir?
(obviously, the restricted user would never receive any external
messages, but he or she would be able to send to any external address
they like, no?)
- cheers eric
