qmail Digest 24 Jun 1999 10:00:00 -0000 Issue 681

Topics (messages 27055 through 27115):

re-relaying mail for a a user
        27055 by: "james" <[EMAIL PROTECTED]>
        27060 by: "james" <[EMAIL PROTECTED]>

Qmail's queue directory & Linux
        27056 by: Russell Nelson <[EMAIL PROTECTED]>
        27072 by: Petri Kaukasoina <[EMAIL PROTECTED]>
        27115 by: "Peter van der Landen" <[EMAIL PROTECTED]>

trouble injecting bounce message
        27057 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>

wildcards in locals
        27058 by: Franky Van Liedekerke <[EMAIL PROTECTED]>
        27062 by: Russell Nelson <[EMAIL PROTECTED]>

virtual domains question
        27059 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>

Auto-reply after delivery
        27061 by: Giles Lean <[EMAIL PROTECTED]>

qmail doesn't start properly
        27063 by: Mate Wierdl <[EMAIL PROTECTED]>

What is *really* going on?
        27064 by: Dave Sill <[EMAIL PROTECTED]>
        27068 by: Russell Nelson <[EMAIL PROTECTED]>
        27069 by: Roy Rapoport <[EMAIL PROTECTED]>
        27074 by: Russell Nelson <[EMAIL PROTECTED]>
        27075 by: Dave Sill <[EMAIL PROTECTED]>
        27080 by: Dave Sill <[EMAIL PROTECTED]>
        27082 by: "Paul J. Schinder" <[EMAIL PROTECTED]>
        27083 by: "Richard Shetron" <[EMAIL PROTECTED]>
        27084 by: [EMAIL PROTECTED]
        27085 by: "Scott D. Yelich" <[EMAIL PROTECTED]>
        27086 by: Justin Bell <[EMAIL PROTECTED]>
        27099 by: "Alex Miller" <[EMAIL PROTECTED]>

Virtual Domains and Capital Letters
        27065 by: Adam H <[EMAIL PROTECTED]>
        27066 by: "Varga Robert <[EMAIL PROTECTED]>" <[EMAIL PROTECTED]>
        27067 by: [EMAIL PROTECTED]

qmail newbie question
        27070 by: "Tetsu Ushijima" <[EMAIL PROTECTED]>

routing mails depending on their size? is this possible?
        27071 by: [EMAIL PROTECTED]

When does qmail-users run?
        27073 by: 
        27076 by: Dave Sill <[EMAIL PROTECTED]>

Unsubbing...
        27077 by: Dave Sill <[EMAIL PROTECTED]>
        27091 by: Mark Turner <[EMAIL PROTECTED]>

qmail-smtp and MUA's speed
        27078 by: Bill Parker <[EMAIL PROTECTED]>
        27079 by: Dave Sill <[EMAIL PROTECTED]>
        27094 by: "Scott D. Yelich" <[EMAIL PROTECTED]>
        27095 by: Dave Sill <[EMAIL PROTECTED]>
        27096 by: Scott Schwartz <[EMAIL PROTECTED]>

running pop3d with a custom passwd backend
        27081 by: Kiril Mitev <[EMAIL PROTECTED]>
        27110 by: Anand Buddhdev <[EMAIL PROTECTED]>

Better UI's (was: What is *really* going on?)
        27087 by: Dave Sill <[EMAIL PROTECTED]>
        27088 by: Tommi Virtanen <[EMAIL PROTECTED]>

qmail-local
        27089 by: Marcel Dan <[EMAIL PROTECTED]>

uucp
        27090 by: Kevin Waterson <[EMAIL PROTECTED]>
        27111 by: Anand Buddhdev <[EMAIL PROTECTED]>

failure notice
        27092 by: Christian Pinheiro <[EMAIL PROTECTED]>

Queue owner
        27093 by: Christian Pinheiro <[EMAIL PROTECTED]>

qmail-pop3d.init errors
        27097 by: "Alex Miller" <[EMAIL PROTECTED]>

Pico - "Incomplete termcap entry" and Memphis RPM
        27098 by: "Alex Miller" <[EMAIL PROTECTED]>
        27103 by: Chris Johnson <[EMAIL PROTECTED]>

Implementation of Virtual Domains
        27100 by: "Alex Miller" <[EMAIL PROTECTED]>

Help with receiving mail
        27101 by: Sienna <[EMAIL PROTECTED]>
        27104 by: Chris Johnson <[EMAIL PROTECTED]>
        27105 by: "Alex Miller" <[EMAIL PROTECTED]>

Important! FW: IT WORKS! - Anyone who is stuggling might benefit from this ...
        27102 by: "Alex Miller" <[EMAIL PROTECTED]>

Virtual Domains.
        27106 by: "Alex Miller" <[EMAIL PROTECTED]>

Almost there.. thanks.  Need some more help
        27107 by: Sienna <[EMAIL PROTECTED]>
        27108 by: Chris Johnson <[EMAIL PROTECTED]>
        27109 by: "Alex Miller" <[EMAIL PROTECTED]>

kill mail from remote user
        27112 by: olli <[EMAIL PROTECTED]>
        27113 by: [EMAIL PROTECTED]
        27114 by: Anand Buddhdev <[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]


----------------------------------------------------------------------


hi
    i have qmail setup in our office to relay internet mail for users and to
deliver
local mail to the users pop account on the same server. the problem is that
one
of our users is in a remote office, so i need his mail (outgoing form our
office here)
 to be deliverd via a different smtp server (our isp's server).
    so what i would like is that any mail for [EMAIL PROTECTED] is "re-relayed"
to a remote
smtp server but mail to [EMAIL PROTECTED] is deliverd localy with out
a dial up

i would very grateful for an answer as i have been banging my head against
the
wall on this one for a week now

j






>>hi
> >    i have qmail setup in our office to relay internet mail for users and
>>  to
>> deliver
>> local mail to the users pop account on the same server. the problem is
>> that one of our users is in a remote office, so i need his mail (outgoing
>> form our office here)
>>  to be deliverd via a different smtp server (our isp's server).
>>     so what i would like is that any mail for [EMAIL PROTECTED] is
>>     "re-relayed"
>> to a remote
>> smtp server but mail to [EMAIL PROTECTED] is deliverd localy with
>> out a dial up

>Simply:
>
>If bobo is a local user (and you're not using qmail-users
>mechanism), put
>&[EMAIL PROTECTED]
>into ~bobo/.qmail
>
>If he's not local, do the same with ~alias/.qmail-bobo
>If you're using fastworward (aliases), put it there
>If you're using qmail-users mechanism, simply point bobo to the
>right .qmail file containing the line above

mm..i not sure if it is that i'm explaining it wrong or that i don't fully
the solution above. both our users here and our guy in the remote
office have the same address suffix ie @bobo.com. our linux server
is set up to "trap" any mail going to [EMAIL PROTECTED] and deliver it to
users local pop a/c because the  guy in the remote office has no
access to "our" linux server he gets no mail from our office.
    he recives his mail direct from our internet pop a/c ...

maybe this makes more sense as to the problem ... but from the
solution that was suggested it seems that .qmail files or ailias's
only work for mail going to a different domain ie it would forward
mail for [EMAIL PROTECTED] to [EMAIL PROTECTED] but this is not what i
want

j








Petri Kaukasoina writes:
 > On Wed, Jun 23, 1999 at 08:04:53AM +0200, Peter van der Landen wrote:
 > > The Cyrus documentation suggests using chattr -R +S on the queue directories
 > > as well as the mailboxes. Would that be less effective than using a
 > > sync-mounted filesystem?
 > 
 > Dan fsyncs explicitely all the _files_ when needed, so there's no problem
 > with them. But in Linux the metadata, e.g. the directory entries are not
 > written synchronously by default. Suppose qmail receives a mail message,
 > writes it to the queue, fsyncs it and reports mail received. In case of
 > power failure at this point the file was written ok but its directory entry
 > was not on disk yet. After bootup fsck puts the message to /lost+found
 > where you can find it but it is not in the qmail queue.
 > 
 > The solution that Linus proposed was to fsync the _directory_ too in
 > addition to the _file_ and that is what my shared library does. Actually it
 > fsyncs the directories every time when link, unlink, open and rename system
 > calls are used (they update directory entries), needed or not.

Right.  That's because it's a stupid idea to fsync metadata.  A
directory is just another file -- why should it automatically be
fsynced just because a different file got fsynced?  You want your
directories written to disk, you fsync them.

No, I don't worship Karels, et al.  The Berkeley CSRG made some
mistakes.  Instead of perpetuating these mistakes, as if they were
physical properties handed to us by God (186K miles/sec -- not just a
good idea, it's the law), Linus is trying to fix them.  Yes, it's
another "gratuitious" incompatibility, but it has serious efficiency
ramifications.

Just like Dan is introducing "gratuitious" incompatibilities.  :)
Only difference is that, unlike vendor gratuitious incompatibilities,
I *like* Dan's incompatibilities.  I wish Dan had the time to put
together a Linux distribution.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




On Wed, Jun 23, 1999 at 10:48:39AM +0300, Petri Kaukasoina wrote:
> 7.  ../testprog
> 8.  switch off the power
> 9.  switch on the power
> 10. after fsck look for the file "testfile" in the directories testdir and 
>     lost+found (under the mount point of the file system)
>     
> If the chattr trick worked you would have "testfile" in "testdir". Otherwise
> you would find it in lost+found.

I got home and tried it myself. To my surprise, the "chattr +S" trick did
work. If testdir had the "S" attribute, testfile was in testdir after reboot
but if the directory didn't have the attribute, fsck put the file in
lost+found. It worked in Linux versions 2.0.37 and 2.2.10. Either something
has changed in the kernel since I tried it last time or I did some mistake
then.

So, it seems that it's enough to
chattr +S /var/qmail/queue/{bounce,info/*,intd,local/*,mess/*,remote/*,todo}
and the same for the new and cur subdirectories in every maildir.





-----Original Message-----
From: Petri Kaukasoina <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, June 23, 1999 6:24 PM
Subject: Re: Qmail's queue directory & Linux


>On Wed, Jun 23, 1999 at 10:48:39AM +0300, Petri Kaukasoina wrote:

>
>I got home and tried it myself. To my surprise, the "chattr +S" trick did
>work. If testdir had the "S" attribute, testfile was in testdir after
reboot
>but if the directory didn't have the attribute, fsck put the file in
>lost+found. It worked in Linux versions 2.0.37 and 2.2.10. Either something
>has changed in the kernel since I tried it last time or I did some mistake
>then.
>
>So, it seems that it's enough to
>chattr +S
/var/qmail/queue/{bounce,info/*,intd,local/*,mess/*,remote/*,todo}
>and the same for the new and cur subdirectories in every maildir.

Ah, that's a relief. It saves me from having to rearrange my partitions.

Thanks for checking...

Regards,
Peter van der Landen






+ Allen Versfeld <[EMAIL PROTECTED]>:

| 1999-06-23 10:59:28.533289 warning: trouble injecting bounce message,
| will try later

| It sounds fairly straightforward, but *which* bounce message, to whom,
| etc?  

Run qmail-qread and look for a large message.  Large enough, in all
likelihood, for a second copy of the message to be too big for the
free disk space.

In such circumstances, I have usually resorted to shutting down qmail
and removing the offending message by hand, then sending mail to the
message's sender and intended recipient explaining what happened and
why.

Perhaps you should consider creating /var/qmail/control/databytes to
avoid this happening again (RTFM qmail-smtpd for a description).

- Harald




Hi,

I know rcpthosts can have wildcards (something like .YYY.ZZZ to allow
all domains ending on YYY.ZZZ to relay) but does the control file locals
also support this?

Franky





Franky Van Liedekerke writes:
 > Hi,
 > 
 > I know rcpthosts can have wildcards (something like .YYY.ZZZ to allow
 > all domains ending on YYY.ZZZ to relay) but does the control file locals
 > also support this?

No.  If that's really what you want, catch it with a virtualdomains,
and forward it to a local host.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




+ Varga Robert <[EMAIL PROTECTED]>:

| If I make a virtualdomains file, and make the usual .qmail-... files
| in the given user's home directory, as forwarding to a real user of
| the system,then the mail arrives in order to the expected place.
| 
| The mail envelope is the following:

First, allow me to correct your terminology:
That is not the envelope.  That is the header.
The distinction is important.

| From [EMAIL PROTECTED] Fri Jun 04 15:02:08 1999
| Return-Path: <[EMAIL PROTECTED]>
| Delivered-To: [EMAIL PROTECTED]
| Received: (qmail 15472 invoked by uid 514); 4 Jun 1999 15:02:08 -0000
| Delivered-To: [EMAIL PROTECTED]
| Received: (qmail 15469 invoked by uid 0); 4 Jun 1999 15:02:08 -0000
| Date: 4 Jun 1999 15:02:08 -0000
| Message-ID: <[EMAIL PROTECTED]>
| From: [EMAIL PROTECTED]
| to: [EMAIL PROTECTED]
| 
| 
| However, it is ugly to see a lot of delivered to lines with the real
| user address [EMAIL PROTECTED], and even
| [EMAIL PROTECTED] in the envelope.

I don't think ugliness is a suitable criterion for deciding what to do
here.  Those lines are an important part of qmail's loop detection and
avoidance algorithm.  Mess with them at your own risk.

| How can I set up the system, so that qmail does not put these lines
| in the envelope, or only one of it, and that containing the virtual
| domain address [EMAIL PROTECTED]?

If you absolutely must, have the mail go through a filter at some
point in the delivery chain to edit and/or remove the offending header
fields.  But please, don't do it unless you know what you're doing.
And don't do it even if you do.

- Harald





On Tue, 22 Jun 1999 14:36:26 +0200  "Joaquim Homrighausen" wrote:

> Is this possible by using just qmail? If so, how? If not, what are the
> preferred packages.. ?

Needs an add on.  See the qmail page or:

http://www.nemeton.com.au/sw/autoreply/

Giles






I hate to ask, but did you hit RETURN after `\' in 

tcpserver -v -u 503 -g 502 0 smtp /var/qmail/bin/qmail-smtpd \
2>&1 | /var/qmail/bin/splogger smtpd 3 &

or just copied the entry from the FAQ?

If you did then:

Is qmail.init executable by all?  What is the output of 

ps auxww |grep qmail


after bootup?  What do the logs say?  Which service(s) does not start?   

What Linux distr are you using?  Is it sysV (like RedHat)?


Mate









Russell Nelson <[EMAIL PROTECTED]> wrote:
>Dave Sill writes:
> > "Scott D. Yelich" <[EMAIL PROTECTED]> wrote:
> > >
> > >You know, one big bad@$$ computer company is where it is now because it
> > >allowed any such idiot to install software by simply clicking the little
> > >"ok" box.
> > 
> > DJB should emulate Microsoft? Har, har.
>
>Recognition  is easier than  remembering  any day.  I don't see why one
>must be a monopolist to  recognize  that.  Maybe you just  forgot ?

I forget lots, Russ, but I have no idea what you're trying to say
here. What do recognition and remembering have to do with whether DJB
should dumb down qmail?

-Dave




Dave Sill writes:
 > Russell Nelson <[EMAIL PROTECTED]> wrote:
 > >Dave Sill writes:
 > > > "Scott D. Yelich" <[EMAIL PROTECTED]> wrote:
 > > > >
 > > > >You know, one big bad@$$ computer company is where it is now because it
 > > > >allowed any such idiot to install software by simply clicking the little
 > > > >"ok" box.
 > > > 
 > > > DJB should emulate Microsoft? Har, har.
 > >
 > >Recognition  is easier than  remembering  any day.  I don't see why one
 > >must be a monopolist to  recognize  that.  Maybe you just  forgot ?
 > 
 > I forget lots, Russ, but I have no idea what you're trying to say
 > here. What do recognition and remembering have to do with whether DJB
 > should dumb down qmail?

The value of a GUI is not that it's graphical, nor that it's colorful,
nor that it uses the whole screen.  It's that it allows the user to
merely recognize the right answer rather than having to recollect it.
Command completion, originally used in tops-20, and most often seen in
kermit, and cisco routers these days, is a reasonable compromise
between a full gui and the typical incompetent command line most
Unices use.

Every user interface should be dumbed down, so we can use our
intelligence to solve other problems.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




On Wed, 23 Jun 1999, Russell Nelson wrote:
> Every user interface should be dumbed down, so we can use our
> intelligence to solve other problems.

Ugh.

I'm not sure that, as a 27-year old person who never surfed the ARPANET, I
can reasonably do the "when I was young" thing, but ...

I have Cisco routers and switches that come with a web GUI.  I'm taking a
Firewall-1 class this week and learning the pretty GUI.  I hear there's a
GUI management interface for Solaris coming out soon.

But you know, in the end I don't know any GUI that I've ever used for
administration that lets me do all the things I can do through a CLI or
lets me do everything quicker.  In general, GUIs disempower me.  You simply
cannot take a complex system (whether it's a router, switch, UNIX
workstaiton, or MTA) and dumb the UI down without losing features or
ability to change behavior.  

I'm not an NT administrator.  I don't expect my products to behave like NT
workstations.  I want a CLI, and I want to be able to do everything via a
CLI, and I'm quite content to have to actually spend some time *learning*
how to use my systems.  

-roy





Roy Rapoport writes:
 > On Wed, 23 Jun 1999, Russell Nelson wrote:
 > > Every user interface should be dumbed down, so we can use our
 > > intelligence to solve other problems.
 > 
 > But you know, in the end I don't know any GUI that I've ever used for
 > administration that lets me do all the things I can do through a CLI or
 > lets me do everything quicker.

I'm not defending GUIs.  I'm offending recollection interfaces.

 > I'm not an NT administrator.  I don't expect my products to behave like NT
 > workstations.  I want a CLI, and I want to be able to do everything via a
 > CLI, and I'm quite content to have to actually spend some time *learning*
 > how to use my systems.  

Of course you have to learn how to use your system.  Your system can
help you with that, by presenting opportunities to recognize, not
recollect, the right solution.  For example, qmail requires you to
remember concurrencyremote (and spell it right!), instead of merely
looking in control/ and seeing concurrencyremote.  Why rely on an
nonexistent or empty file meaning "use the default" instead of putting
the documentation for the variable in the tail of the file, and
leaving the first line blank?

It'd just plain silly to expect people to have to memorize the answer, 
then spit it back, as if computers were some sort of elementary school 
test.  They weren't fun then, and they aren't fun now.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




Russell Nelson <[EMAIL PROTECTED]> wrote:
>
>Of course you have to learn how to use your system.  Your system can
>help you with that, by presenting opportunities to recognize, not
>recollect, the right solution.  For example, qmail requires you to
>remember concurrencyremote (and spell it right!), instead of merely
>looking in control/ and seeing concurrencyremote.  Why rely on an
>nonexistent or empty file meaning "use the default" instead of putting
>the documentation for the variable in the tail of the file, and
>leaving the first line blank?

Why not just learn that "man qmail-control" has all that information?
If you can remember that /var/qmail/control is where control files go, 
surely you can remember the name of the man page.

I like the current approach, where every file in my control directory
represents a true setting, not a default. I don't have to read each
file to see which values are set and which are defaulted. And
qmail-showctl relies on this, though it could be modified to support
your suggested method.

-Dave




Russell Nelson <[EMAIL PROTECTED]> wrote:
>
>The value of a GUI is not that it's graphical, nor that it's colorful,
>nor that it uses the whole screen.  It's that it allows the user to
>merely recognize the right answer rather than having to recollect it
>Command completion, originally used in tops-20, and most often seen in
>kermit, and cisco routers these days, is a reasonable compromise
>between a full gui and the typical incompetent command line most
>Unices use.

Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
shame VMS didn't incorporate command completion. I'm also suprised
nobody's retrofitted it to Linux via readline. Precious few programs
even use readline. How handy would filename completion and command
recall be in an ftp client?

>Every user interface should be dumbed down, so we can use our
>intelligence to solve other problems.

I don't think "dumbed down" is the right term. Perhaps "improved" or
"streamlined".

There's no reason one couldn't layer an improved UI over qmail: either 
a web GUI (some of which has already been done) or a CLI-based
"qmail-ctl" shell with command completion.

In fact, I think it would be *better* to layer such an interface on
top, than to incorporate it into qmail, because that's more in keeping
with the modular nature of qmail.

-Dave




On Wed, Jun 23, 1999 at 02:49:41PM -0400, Dave Sill wrote:
} 
} Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
} shame VMS didn't incorporate command completion. I'm also suprised
} nobody's retrofitted it to Linux via readline. Precious few programs
} even use readline. How handy would filename completion and command
} recall be in an ftp client?

ncftp already incorporates both in an ftp client, and tcsh does both
using in a shell.  Both run under Linux as well as other Unices, and
come with the distributions I use. It is very useful.  I use them both
on LinuxPPC, HP-UX, and SunOS.

} 
} -Dave

-- 
--------
Paul J. Schinder
NASA Goddard Space Flight Center
[EMAIL PROTECTED]




[snip]

> Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
> shame VMS didn't incorporate command completion. I'm also suprised
> nobody's retrofitted it to Linux via readline. Precious few programs
> even use readline. How handy would filename completion and command
> recall be in an ftp client?

tcsh does commandline completion, press TAB to tell it to complete and
if unique, it will, otherwise it beeps at you.


-- 
Richard Shetron  [EMAIL PROTECTED] [EMAIL PROTECTED]
                 What is the Meaning of Life?
There is no meaning,
It's just a consequence of complex carbon based chemistry; don't worry about it
The Super 76, "Free Aspirin and Tender Sympathy", Las Vegas Strip.




Dave Sill <[EMAIL PROTECTED]> writes on 23 June 1999 at 14:49:41 -0400
 > Russell Nelson <[EMAIL PROTECTED]> wrote:
 > >
 > >The value of a GUI is not that it's graphical, nor that it's colorful,
 > >nor that it uses the whole screen.  It's that it allows the user to
 > >merely recognize the right answer rather than having to recollect it
 > >Command completion, originally used in tops-20, and most often seen in
 > >kermit, and cisco routers these days, is a reasonable compromise
 > >between a full gui and the typical incompetent command line most
 > >Unices use.
 > 
 > Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
 > shame VMS didn't incorporate command completion. I'm also suprised
 > nobody's retrofitted it to Linux via readline. Precious few programs
 > even use readline. How handy would filename completion and command
 > recall be in an ftp client?

Bash does command completion and filename completion and username
completion (in ~name constructs).  Bash is the default shell on
Linux.  This doesn't give you the depth that TOPS-20 did; a program
that used the COMND jsys for the command line interface knew the type
of each parameter and could supply appropriate assistance, whereas in
BASH a command line is always assumed to refer to files, and that's
really all it can help you with.

(I worked with tops-20 from 1977 to 1985, and worked for DEC in
Marlboro doing TOPS-20 layered product development from '81 to '85).

Remember kermit, the file transfer program that would move data over
terminal lines from a desktop system to *anything*?  Its command
interface was patterned after TOPS-20.  It always felt very homey to
me. 
-- 
David Dyer-Bennet                                              [EMAIL PROTECTED]
http://www.ddb.com/~ddb (photos, sf) Minicon: http://www.mnstf.org/minicon
http://ouroboros.demesne.com/ The Ouroboros Bookworms
Join the 20th century before it's too late!




-----BEGIN PGP SIGNED MESSAGE-----



On Wed, 23 Jun 1999, Richard Shetron wrote:
> tcsh does commandline completion, press TAB to tell it to complete and
> if unique, it will, otherwise it beeps at you.

I wrote to dave privately... I wsan't goin to write the list --
everyone's mentioning tcsh as a shell that does completion...
many do... even csh will do it

set filec
type the name and then ESC-ESC

Scott


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBN3ExFB4PLs9vCOqdAQEYwgQAt0cDerx21FkcZfbJYkFpvuX0opaXsENC
8oVrBgkz9kTRzLDsuPCc8+PF8t43TvEYT834Fz0d1L9bNzglLA2OiuH6qilmomOS
SdICOZLeDMkEZueV3sk8YP1Geb/xEYwGC5LVWSQSWMaCAFMweqos8QJyC9/YGcW6
yW4meveKJlk=
=fq9E
-----END PGP SIGNATURE-----





On Wed, Jun 23, 1999 at 03:07:50PM -0400, Richard Shetron wrote:
# [snip]
# 
# > Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
# > shame VMS didn't incorporate command completion. I'm also suprised
# > nobody's retrofitted it to Linux via readline. Precious few programs
# > even use readline. How handy would filename completion and command
# > recall be in an ftp client?
# 
# tcsh does commandline completion, press TAB to tell it to complete and
# if unique, it will, otherwise it beeps at you.

or if you set autolist, if not unique those files/commands/users are all
listed.

-- 
/- [EMAIL PROTECTED] --------------- [EMAIL PROTECTED] -\
|Justin Bell  NIC:JB3084| Time and rules are changing.         |
|Pearson                | Attention span is quickening.        |
|Developer              | Welcome to the Information Age.      |
\-------- http://www.superlibrary.com/people/justin/ ----------/




> -----Original Message----
> From: Dave Sill [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 22, 1999 3:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: What is *really* going on?
>
>
> "Scott D. Yelich" <[EMAIL PROTECTED]> wrote:
> >
> >Right, but remember... you must know approximately 80% of qmail just to
> >make it useful for you -- whereas the number was quoted to be about 20%
> >for sendwhale.
>
> Hogwash. These 20%/80% numbers are pulled from thin air. Even if they
> were accurate, though, 20% of sendmail is probably on the same order
> of complexity as 80% of qmail.

I have been studying sendmail for a while now, I bought that expensive
O'Reilly book. After reading that, studying it, and reading about QMail, it
was apparent that to do any of the things I wanted to do, virtual hosting,
particularly, I should use QMail.

Although I have been having a bear of a time getting the basic, "send an
email", "recieve an email", "get an email from the outside world" working
with QMail and QMail pop3d, once got QMail itself running (due to the
Memphis RPM) it took me very little time to set up a host for my Linux box
"cybergood.net", several virtual hosts, "vmail.cybergood.net",
"virtual.cybergood.net", "creativepeople.cybergood.net",
"hatewatch.cybergood.net". I have set up several autoforwded emails for
people, that both collect mail (in a Maildir) and forward them along.

This configuration is very straightforward, simple, and direct. The same
kinds of things (well, maybe not the autoforwarding) are very difficult in
sendmail. This is the stuff I WANT to be straightforward and easy. This is
the liberating part of email I want and want to provide to others.

>
> >You know, one big bad@$$ computer company is where it is now because it
> >allowed any such idiot to install software by simply clicking the little
> >"ok" box.

The problem with Microsoft's easy installation is not the fact that any
idiot can do it, it's that NO GENIUS can properly undo it. Configuration
management and control is practically impossible in Windows, everything
leaks, users aren't separated properly, and the standard of reliability is
lower than that Jr. High School science projects.

I have been struggling for 2 weeks reading, learning, and experimenting with
email setups, not because the damn struggle is good for my mind but because
I know the on my LINUX box the end result will be worth the effort, and I
will be FREE to provide email services to my friends, and not-for-profit
groups I support, with a reliable and flexible system.

That has NEVER been true in my struggles with Windows. It's always been a
waste of my valuable time.

>
> DJB should emulate Microsoft? Har, har.
>
> -Dave
>





It seems the vchkpw package is cap sensitive.  Wondering if anyone has a
workaround so it's not?

Thanks!
Adam








On Wed, 23 Jun 1999, Adam H wrote:

> It seems the vchkpw package is cap sensitive.  Wondering if anyone has a
> workaround so it's not?

There is a patch on the homepage of the package... separately for the
released (3.1.2) and the beta (3.5.x) versions.

Robert Varga





On Wed, Jun 23, 1999 at 10:55:54AM -0400, Adam H wrote:
> It seems the vchkpw package is cap sensitive.  Wondering if anyone has a
> workaround so it's not?
> 
> Thanks!
> Adam

Yes. http://www.inter7.com/qmail/vchkpw-3.4.1.tar.gz

For a pop auth before relay try 
http://www.inter7.com/qmail/vchkpw-3.4.2kj.tar.gz

The author has a patch on the main vchkpw site for the
new version, but it is missing a few cases where the
case needs to be fixed

Ken Jones
Inter7




Gerald Willmann writes:
> Under sendmail I could mail people at other stanford hosts by simply using
> someone@hostname as the address, without .stanford.edu. How can I achieve
> the same with qmail?  
> 
> Finally I saw in the FAQ how to configure pine to use qmail-inject instead
> of SMTP - what are the pros and cons?

With qmail-inject, you can use someone@hostname instead of
[EMAIL PROTECTED], provided that
control/defaultdomain is set up properly.

With SMTP (qmail-smtpd), messages headers are not rewritten.
So it is up to Pine to complete these abbreviated addresses.

-- 
Tetsu Ushijima




hi everybody,

qmail is cool!!
but i am missing one feature: i want to route mails depending on their
size.
i see 2 ways:

1. way: playing around with some shell-scripts which are called from
.qmail-xyz
but i do not like this way, you have to create a lot of processes....

2. way: working with environment variables: i would prefer this to the
first way. can 
anybody tell how to modify qmail so i got a env variable MESSAGESIZE.
using this env variable it would be easy to create things like

| condredirect [EMAIL PROTECTED] `test $MESSAGESIZE -gt 200000`

in .qmail-xy

any hints welcome!!!

jodok






For discussion's sake, please consider the following excerpt from
PIC.rem2local:

qmail-send      Look at envelope recipient, [EMAIL PROTECTED]
     |          Is heaven.af.mil in locals? Yes.
    |          Deliver locally to [EMAIL PROTECTED]
     V

qmail-lspawn ./Mailbox

     |          Look at mailbox name, joe.
     |          Is joe listed in qmail-users? No.    <== My concern is
here (1)
     |          Is there a joe account? Yes.
     |          Is joe's uid nonzero? Yes.
     |          Is ~joe visible to the qmailp user? Yes.
     |          Is ~joe owned by joe? Yes.
     |          Give control of the message to joe.
     |          Run qmail-local.
     V

Is Step (1) implemented by qmail-users? If so, does qmail-users run
automatically once /var/qmail/users/cdb has been created with
(qmail-pw2u and) qmail-newu?

If there is no /var/qmail/users/cdb, is Step (1) implemented by
qmail-getpw?

If /var/qmail/users/cdb exists and qmail-users cannot access account
info, is qmail-getpw automatically used as a last resort?
- - - - - - - - - - - - - - - - - - - - - - -
Peeter Pirn,  Sys Admin, FWI Internet, 219-426-7701 x17






[EMAIL PROTECTED] wrote:
>
>For discussion's sake, please consider the following excerpt from
>PIC.rem2local:
>
>qmail-send      Look at envelope recipient, [EMAIL PROTECTED]
>     |          Is heaven.af.mil in locals? Yes.
>    |          Deliver locally to [EMAIL PROTECTED]
>     V
>
>qmail-lspawn ./Mailbox
>
>     |          Look at mailbox name, joe.
>     |          Is joe listed in qmail-users? No.    <== My concern is
>here (1)
>     |          Is there a joe account? Yes.
>     |          Is joe's uid nonzero? Yes.
>     |          Is ~joe visible to the qmailp user? Yes.
>     |          Is ~joe owned by joe? Yes.
>     |          Give control of the message to joe.
>     |          Run qmail-local.
>     V
>
>Is Step (1) implemented by qmail-users?

No, it's done by qmail-lspawn, as the PIC file says.

>If so, does qmail-users run
>automatically once /var/qmail/users/cdb has been created with
>(qmail-pw2u and) qmail-newu?

qmail-lspawn looks for users/cdb. If it's there, it looks up the
user.

>If there is no /var/qmail/users/cdb, is Step (1) implemented by
>qmail-getpw?

No. If users/cdb isn't there, the lookup automatically fails.

>If /var/qmail/users/cdb exists and qmail-users cannot access account
>info, is qmail-getpw automatically used as a last resort?

If users/cdb exists, that *is* the account info. If account
information isn't available when qmail-pw2u is run, then users/assign
isn't updated and qmail-newu shouldn't be re-run.

No qmail-users programs are run at delivery time. users/cdb is updated 
only when qmail-newu is re-run by the admin, either manually, as
part of adduser script, or via a cron job.

See:

    http://Web.InfoAve.Net/~dsill/lwq.html#qmail-users

-Dave




Harald Hanche-Olsen <[EMAIL PROTECTED]> wrote:
>+ Dave Sill <[EMAIL PROTECTED]>:
>| Harald Hanche-Olsen <[EMAIL PROTECTED]> wrote:
>| >
>| >You will need to send your unsubscription request from the address
>| >of your subscription.
>| 
>| Ooh, so close. Actually, he'll need to send the message to:
>| 
>|     [EMAIL PROTECTED]
>| 
>| where [EMAIL PROTECTED] is his subscription address, to unsubscribe.
>
>Well, if we are going to split hairs, he doesn't *need* to, but it may
>be more convenient if he doesn't have a good way to set his
>(envelope?) sender address on outgoing mail.

It's not hair-splitting. ezmlm uses the envelope return path, not the
>From header field as the address to be operated upon. I don't know
about your MUA, but I'm not aware of any that change the return path
to match the From field.

-Dave




Yep, still here!

....here's my header....I still want to get off. 
Even though it's not that bad being tied to the best list on the net!

Return-Path: 
                            
<[EMAIL PROTECTED]>
                   Received: 
                             from muncher.math.uic.edu
([131.193.178.181]) by server1.sia.net.au
                             (Post.Office MTA v3.5.3 release 223 ID#
525-59253U6000L600S0V35)
                             with SMTP id au for <[EMAIL PROTECTED]>;
Sat, 19 Jun 1999 20:23:55
                             +1000
                   Received: 
                             (qmail 4011 invoked by uid 1002); 19 Jun
1999 10:06:51 -0000
                Mailing-List: 
                             contact [EMAIL PROTECTED]; run by
ezmlm
                 Precedence: 
                             bulk
               Delivered-To: 
                             mailing list [EMAIL PROTECTED]
                   Received: 
                             (qmail 8676 invoked from network); 19 Jun
1999 10:06:49 -0000
                   Received: 
                             from alastor.frg.eur.nl
([EMAIL PROTECTED]) by
                             muncher.math.uic.edu with SMTP; 19 Jun 1999
10:06:49 -0000
                   Received: 
                             (qmail 20026 invoked from network); 19 Jun
1999 10:07:15 -0000
                   Received: 
                             from wyst.frg.eur.nl (HELO wyst)
(130.115.137.25) by alastor.frg.eur.nl
                             with SMTP; 19 Jun 1999 10:07:15 -0000
                 Message-ID: 
                             <025501beba3b$7f8c71e0$19897382@wyst>
                       From: 
                             "Peter van der Landen" <[EMAIL PROTECTED]>
                          To: 
                             <[EMAIL PROTECTED]>
                     Subject: 
                             Qmail's queue directory & Linux
                        Date: 
                             Sat, 19 Jun 1999 12:07:11 +0200
              MIME-Version: 
                             1.0
              Content-Type: 
                             text/plain; charset="iso-8859-1"
 Content-Transfer-Encoding: 
                             7bit
                  X-Priority: 
                             3
          X-MSMail-Priority: 
                             Normal
                    X-Mailer: 
                             Microsoft Outlook Express 4.72.2106.4
                 X-MimeOLE: 
                             Produced By Microsoft MimeOLE V4.72.2106.4
            X-Mozilla-Status: 
                             0000
          X-Mozilla-Status2: 
                             00000000
                     X-UIDL: 
                             [EMAIL PROTECTED]





I dunno if anyone saw this message, but I was asking if adding -t5 to
my tcpserver line would speed up access to users sending get/send
requests through Outlook Express clients (I know, wintendo)

>
>At 03:02 PM 6/15/99 -0400, you wrote:
>>Bill Parker <[EMAIL PROTECTED]> wrote:
>>>
>>>     I am running qmail with tcpserver, and want to know if there is
>>>any way to make qmail respond faster to smtp/pop3d requests other than
>>>going through a DNS lookup...
>>
>>Huh? How would going through a DNS lookup speed this up?
>>
>>Disabling identd lookups, using the "-R" flag to tcpserver might
>>help. Or possibly just shortening the timeout via "-t".
>>
>
>Well, here is my qmail startup script for smtp and pop3...
>
>Stuff above deleted to save space...
>
>case "$1" in
>  start)
>        echo -n "Starting: "
>        env - PATH="/var/qmail/bin:/usr/local/bin" \
>        qmail-start ./Maildir/ splogger qmail &
>        echo -n "qmail "
> 
>        env - PATH="/var/qmail/bin:/usr/local/bin" \
>        tcpserver -H -R -x /etc/tcp.smtp.cdb -c20 -u7791 -g2108 0 smtp \
>        /var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
>        echo -n "smtp "
> 
>        env - PATH="/var/qmail/bin:/usr/local/bin" \
>        tcpserver -H -R -b30 -c10 0 pop3 \
>        /var/qmail/bin/qmail-popup odie.donbest.com \
>        /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
>        echo "pop3d"
>
>stuff below deleted to save space...
>
>Now, I do have the -R flag going to tcpserver (as shown above), will
>adding -t5 (for a max 5 seconds) help, or are they mutually exclusive?
>
>>
>>If your DNS is slow, you'll see delays all over the place, and, yes,
>>running your own caching nameserver will help.
>
>I bought a copy of the ORA DNS/Bind book 3rd edition, which I am
>going over now...<slow reading..heh>...
>
>-Bill






Bill Parker <[EMAIL PROTECTED]> wrote:
>At 03:02 PM 6/15/99 -0400, you wrote:
>>
>>Disabling identd lookups, using the "-R" flag to tcpserver might
>>help. Or possibly just shortening the timeout via "-t".
>
>Well, here is my qmail startup script for smtp and pop3...
>
>Stuff above deleted to save space...
>
>        env - PATH="/var/qmail/bin:/usr/local/bin" \
>        tcpserver -H -R -x /etc/tcp.smtp.cdb -c20 -u7791 -g2108 0 smtp \
>        /var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
>        echo -n "smtp "
> 
>        env - PATH="/var/qmail/bin:/usr/local/bin" \
>        tcpserver -H -R -b30 -c10 0 pop3 \
>        /var/qmail/bin/qmail-popup odie.donbest.com \
>        /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
>        echo "pop3d"
>
>Now, I do have the -R flag going to tcpserver (as shown above), will
>adding -t5 (for a max 5 seconds) help, or are they mutually exclusive?

It won't help to shorten the timeout for identd lookups since you're
not doing identd lookups.

-Dave




-----BEGIN PGP SIGNED MESSAGE-----


> It won't help to shorten the timeout for identd lookups since you're
> not doing identd lookups.

Is or does some part of the qmail system doing identd lookups? I now
send mail through a firewall that doesn't allow incoming identd and
qmail is taking 10-25 seconds, or so, to accept each incoming message.

my current inetd.conf config is this:
smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env 
/var/qmail/bin/qmail-smtpd

I use to run rblsmtpd but I lost the command to start it up and I can't
recreated the long pipe command to get it to restart.


Thanks.
Scott

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBN3F5Th4PLs9vCOqdAQEfMQQAx2lVD5F6MhFPbOSPXe4oSMiATVxYjbWw
iN4+vnjKUS5kTh+HpFSnlhXXeJWs4k7VlX84yqkllYsRSe7ltd6NhXagH4N1AsUa
frNhlDY5bmHbSusTj0GdVFhO+KjC+wUt4MH1ua3pbLUnxNGrialIRowr4qVlSFRB
GDAplDm5gmU=
=ZnL8
-----END PGP SIGNATURE-----





"Scott D. Yelich" <[EMAIL PROTECTED]> wrote:
>
>Is or does some part of the qmail system doing identd lookups?

No. tcpserver does identd, but it's not part of qmail, and you're not
using it.

>I now
>send mail through a firewall that doesn't allow incoming identd and
>qmail is taking 10-25 seconds, or so, to accept each incoming message.
>
>my current inetd.conf config is this:
>smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env 
>/var/qmail/bin/qmail-smtpd

Maybe tcp_wrappers (tcpd) does identd. You could trace it to see where 
it's spending its time.

>I use to run rblsmtpd but I lost the command to start it up and I can't
>recreated the long pipe command to get it to restart.

It's not *that* hard.

-Dave




Dave Sill <[EMAIL PROTECTED]> writes:
| "Scott D. Yelich" <[EMAIL PROTECTED]> wrote:
| >Is or does some part of the qmail system doing identd lookups?
| 
| No. tcpserver does identd, but it's not part of qmail, and you're not
| using it.

Yes. tcp-env does identd, and it's in the qmail INSTALL document, 
and he is using it.

This must be in the unoffical FAQs: always use -R.

(Talk about bad defaults!)





Dear All

here is the problem:
i have setup a virtual host delivery system as per
Paul Greg's instructions :-)


he uses a checkpoppasswd program to read a 'custom' password
file and do the authentication. i need to do something very similar
but use my own authentication backend.

it all *almost* works, but only "almost". i compared the preliminary setup
done by checkpoppasswd and my checkpop.pl and they both seem to 
be supplying an identical environment to qmail-pop3d.

however, when i use my password checker, qmail-pop3d complains
that the user 'does not have a /Maildir/', the famous
-ERR this user has no $HOME/Maildir
error....

to double-check, this is what i have done. i changed checkpassword
to execvp() a small script that dumps the environment around it
back to the network connection. i changed my program to do 
the same, and compared the two. looks identical!
the environment dumper then exec's qmail-pop3d

please help/suggest/whatever if you can...


here is the TELNET session of a connection made using Paul Greg's setup:

# telnet 0 pop3
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user tester
+OK
pass testpw
checkpoppass.... about to exec!         <<this is output by checkpoppasswd>>
                                                                 << from here onwards 
output is by showenv >>
SHOWENV: BLOCKSIZE=[K]
SHOWENV: HOME=[/var/qmail/popboxes/ideaglobal-com/tester]
SHOWENV: MAIL=[/var/mail/root]
SHOWENV: PATH=[/root/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin]
SHOWENV: SHELL=[/sbin/nologin]
SHOWENV: TERM=[su]
SHOWENV: USER=[popuser]
SHOWENV: 
inetd_dummy=[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
SHOWENV:
SHOWENV: uids are 888 and 888
SHOWENV: ARGV = /var/qmail/bin/qmail-pop3d Maildir
SHOWENV: -----------------------------

                                                                 << showenv is done >>
+OK
quit
+OK
                                                                 << those 3 lines are 
output by qmail-pop3d >>
                                                                 << at this point i 
could use LIST and RETR >>
                                                                 << and it works >>
Connection closed by foreign host.
                                                                << message courtesy of 
/usr/bin/telnet >>

**** And here is the session of a connection made to my passwd program

# telnet 0 pop3      
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user tester
+OK
pass tester
                                                          << showenv starts >>
SHOWENV: HOME=[/var/qmail/popboxes/ideaglobal-com/tester]
SHOWENV: SHELL=[/sbin/nologin]
SHOWENV: USER=[popuser]
SHOWENV:
SHOWENV: uids are 888 and 888
SHOWENV: ARGV = /var/qmail/bin/qmail-pop3d Maildir
SHOWENV: -----------------------------
                                                          << showenv ends >>
-ERR this user has no $HOME/Maildir
                              << -ERR comes from qmail-pop3d >>
Connection closed by foreign host.
                                                                << message courtesy of 
/usr/bin/telnet >>


= = = = = = 

as you can see, the environment variables HOME/USER/SHELL are identical
in both cases, the real and effective uids are set to 888 in both cases
and the ARGV line which is used to exec() qmail-pop3d is identical


what the hell am i doing wrong ????

Kiril




On Wed, Jun 23, 1999 at 07:46:59PM +0100, Kiril Mitev wrote:

Since we don't know what your code looks like, this is just a wild guess:
In your own auth program, do you have code to do a chdir to the directory
containing the Maildir? qmail-pop3d starts by checking for the presence of
a Maildir, and then tries to chdir into it, using a relative path. If these
2 calls fail, it dies complains that the user has no Maildir.

> Dear All
> 
> here is the problem:
> i have setup a virtual host delivery system as per
> Paul Greg's instructions :-)
> 
> 
> he uses a checkpoppasswd program to read a 'custom' password
> file and do the authentication. i need to do something very similar
> but use my own authentication backend.
> 
> it all *almost* works, but only "almost". i compared the preliminary setup
> done by checkpoppasswd and my checkpop.pl and they both seem to 
> be supplying an identical environment to qmail-pop3d.
> 
> however, when i use my password checker, qmail-pop3d complains
> that the user 'does not have a /Maildir/', the famous
> -ERR this user has no $HOME/Maildir
> error....
> 
> to double-check, this is what i have done. i changed checkpassword
> to execvp() a small script that dumps the environment around it
> back to the network connection. i changed my program to do 
> the same, and compared the two. looks identical!
> the environment dumper then exec's qmail-pop3d
> 
> please help/suggest/whatever if you can...
> 
> 
> here is the TELNET session of a connection made using Paul Greg's setup:
> 
> # telnet 0 pop3
> Trying 0.0.0.0...
> Connected to 0.
> Escape character is '^]'.
> +OK <[EMAIL PROTECTED]>
> user tester
> +OK
> pass testpw
> checkpoppass.... about to exec!         <<this is output by checkpoppasswd>>
>                                                                << from here onwards 
>output is by showenv >>
> SHOWENV: BLOCKSIZE=[K]
> SHOWENV: HOME=[/var/qmail/popboxes/ideaglobal-com/tester]
> SHOWENV: MAIL=[/var/mail/root]
> SHOWENV: PATH=[/root/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin]
> SHOWENV: SHELL=[/sbin/nologin]
> SHOWENV: TERM=[su]
> SHOWENV: USER=[popuser]
> SHOWENV: 
>inetd_dummy=[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
> SHOWENV:
> SHOWENV: uids are 888 and 888
> SHOWENV: ARGV = /var/qmail/bin/qmail-pop3d Maildir
> SHOWENV: -----------------------------
> 
>                                                                << showenv is done >>
> +OK
> quit
> +OK
>                                                                << those 3 lines are 
>output by qmail-pop3d >>
>                                                                << at this point i 
>could use LIST and RETR >>
>                                                                << and it works >>
> Connection closed by foreign host.
>                                                               << message courtesy of 
>/usr/bin/telnet >>
> 
> **** And here is the session of a connection made to my passwd program
> 
> # telnet 0 pop3      
> Trying 0.0.0.0...
> Connected to 0.
> Escape character is '^]'.
> +OK <[EMAIL PROTECTED]>
> user tester
> +OK
> pass tester
>                                                         << showenv starts >>
> SHOWENV: HOME=[/var/qmail/popboxes/ideaglobal-com/tester]
> SHOWENV: SHELL=[/sbin/nologin]
> SHOWENV: USER=[popuser]
> SHOWENV:
> SHOWENV: uids are 888 and 888
> SHOWENV: ARGV = /var/qmail/bin/qmail-pop3d Maildir
> SHOWENV: -----------------------------
>                                                         << showenv ends >>
> -ERR this user has no $HOME/Maildir
>                               << -ERR comes from qmail-pop3d >>
> Connection closed by foreign host.
>                                                               << message courtesy of 
>/usr/bin/telnet >>
> 
> 
> = = = = = = 
> 
> as you can see, the environment variables HOME/USER/SHELL are identical
> in both cases, the real and effective uids are set to 888 in both cases
> and the ARGV line which is used to exec() qmail-pop3d is identical
> 
> 
> what the hell am i doing wrong ????
> 
> Kiril

-- 
System Administrator
See complete headers for address, homepage and phone numbers




"Paul J. Schinder" <[EMAIL PROTECTED]> wrote:
>On Wed, Jun 23, 1999 at 02:49:41PM -0400, Dave Sill wrote:
>} 
>} Ah, TOPS-20. My first job, back in '85, was admin'ing a DEC 20. It's a 
>} shame VMS didn't incorporate command completion. I'm also suprised
>} nobody's retrofitted it to Linux via readline. Precious few programs
>} even use readline. How handy would filename completion and command
>} recall be in an ftp client?
>
>ncftp already incorporates both in an ftp client, and tcsh does both
>using in a shell.

I wasn't aware that ncftp did had them; thanks for the tip. Bash has
them both, and I've been using it for 10+ years now.

But filename completion and command recall are only the tip of the
iceberg that was TOPS-20 command completion. At any point on the
command line, you could hit a key and get an immediate list of
possible values. E.g., at an empty line, you'd get a list of all
available commands. Type a letter, hit the key, and you get a list of
all commands starting with that letter. So far, this is exactly like
most UNIX shell filename completion. Now say you've entered a complete 
command name, followed by space, and you hit the completion key. You
get a list of command's options. Type an option that requires a
parameter, hit the key, get a list (or description) of the value the
option requires. Requires a great deal of cooperation between the
shell and the command. Under TOPS-20, each command had to register its 
options and arguments via a system call that made them available to
the CLI.

Here's a hypothetical example, where escape is the completion key:

    # qmail-[ESC]
    qmail-clean          qmail-popup          qmail-rspawn
    qmail-getpw          qmail-pw2u           qmail-send
    qmail-inject         qmail-qmtpd          qmail-showctl
    qmail-local          qmail-qread          qmail-smtpd
    qmail-lspawn         qmail-qstat          qmail-smtpd-wrapper
    qmail-newu           qmail-queue          qmail-start
    qmail-pop3d          qmail-remote         qmail-tcpto
    # qmail-inject [ESC]
    (Injects a mail message into the qmail system)
    [ -nNaAhH ] [ -fsender ] [ recip ...  ] <stdin
    # qmail-inject -f[ESC]
    sender (e-mail address to go in envelope return path)
    # qmail-inject [EMAIL PROTECTED] [ESC]
    recipient (e-mail address of message recipient)
    # qmail-inject [EMAIL PROTECTED] [EMAIL PROTECTED] [ESC]
    [ additional recipients ]
    [ < message-file ]
    # qmail-inject [EMAIL PROTECTED] [EMAIL PROTECTED] <mess
    #

-Dave




On Wed, Jun 23, 1999 at 03:48:21PM -0400, Dave Sill wrote:
> But filename completion and command recall are only the tip of the
> iceberg that was TOPS-20 command completion. At any point on the
> command line, you could hit a key and get an immediate list of
> possible values. E.g., at an empty line, you'd get a list of all

        Many in the GNU camp have pondered making getopt
        handle one specific argument itself, outputting
        the possible options in some syntax, and exitting.
        A shell might in some way detect the programs that
        support this and ask them what options they accept
        (and cache that). No one has hacked it yet; the
        biggest disadvantage would be the detection of what
        programs support this special option and what don't.

        Some shells (zsh comes to mind, maybe tcsh) support
        programmable completion, which can do all you described.
        Setting it up is a pain though..
-- 
Havoc Consulting | unix, linux, perl, mail, www, internet, security consulting
+358 50 5486010  | software development, unix administration, training




Hi,
I am unsure of how to change the default route of qmail for the entire
server.  I am using qmail with vchkpw so the domain is not virtual but
the users are and the message gets delivered by defualt into a users
/home/directory (which doesn't exist).  Everything else is working so
that I can upload messages and relay...etc.
I sincerely apprectiate any information/help.

Marcel




Can qmail handle uucp?
How is this acheved?

Kevin

--
      _    _
     / /  (_)__  __ ____  __           [EMAIL PROTECTED]
    / /__/ / _ \/ // /\ \/ /           Systems Administator
   /____/_/_//_/\_,_/ /_/\_\  ...... http://www.oceania.net ......







On Thu, Jun 24, 1999 at 09:00:23AM +1000, Kevin Waterson wrote:

FAQ #2.3 for outgoing uucp. Look at www.qmail.org for incoming uucp.

> Can qmail handle uucp?
> How is this acheved?

-- 
System Administrator
See complete headers for address, homepage and phone numbers






http://www.ornl.gov/its/archives/mailing-lists/qmail/1997/06/msg00034.html


I saw in the link above there was more than one person with the same
problem as mine.

I've tried all the solutions, but It does not fix my problem.

I have a LDAP server, and I'm tring to set up 2 machines to act as
SMTP/POP servers,
looking for LDAP, and mounting the mailboxes directories as NFS mounts.

By example, 

1) the machine A has the LDAP database, and qmail 
2) The machine B has qmail running.
3) The qmail was compiled in machine A, because B has no gcc or other
compiler (is a production machine)
4) The qmail in machine A runs fine
5) The qmail in machine B (which is installed with the tar file of the
qmail-1.0.3 compiled package) has problem to receive/send emails. The
problem is the same of the link above. Owner of the queue
directories/files. I tried the queue-fix and others solutions.


Does anybody has one solution for that?



Error messages:

deferral:Sorry,_message_has_wrong_owner._(#4.3.5)

In log:

Jun 23 20:03:33 andromeda qmail: 930179013.394619 delivery 150:
deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/
-- 
Christian M. C. Pinheiro                              
System Administrator - VeritelNet 
<[EMAIL PROTECTED]>





http://www.ornl.gov/its/archives/mailing-lists/qmail/1997/06/msg00034.html


I saw in the link above there was more than one person with the same
problem as mine.

I've tried all the solutions, but It does not fix my problem.

I have a LDAP server, and I'm tring to set up 2 machines to act as
SMTP/POP servers,
looking for LDAP, and mounting the mailboxes directories as NFS mounts.

By example, 

1) the machine A has the LDAP database, and qmail 
2) The machine B has qmail running.
3) The qmail was compiled in machine A, because B has no gcc or other
compiler (is a production machine)
4) The qmail in machine A runs fine
5) The qmail in machine B (which is installed with the tar file of the
qmail-1.0.3 compiled package) has problem to receive/send emails. The
problem is the same of the link above. Owner of the queue
directories/files. I tried the queue-fix and others solutions.


Does anybody has one solution for that?



Error messages:

deferral:Sorry,_message_has_wrong_owner._(#4.3.5)

In log:

Jun 23 20:03:33 andromeda qmail: 930179013.394619 delivery 150:
deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/
-- 
Christian M. C. Pinheiro                              
System Administrator - VeritelNet 
<[EMAIL PROTECTED]>




Stewart,

You get the big reward for coming up with the solution to "most" of my
pop-3d problems. What I don't understand is this. If the Memphis RPM
automatically places in the directory /etc/rc3.d/ as K<n>qmail-pop3d.init
instead of S<a>qmail-pop3d.init, how is it that the Memphis install works on
any system? Is it random chance? For me the effect is clear. If I switch to
S, reboot, I can get my mail through Pop (from my windows computer on my
network using outlook). If I switch back to K, reboot, it fails. So your
solution clearly works, but why is it apparently not necessary on most
systems, since people do get the Memphis RPM to work without doing that.

Now, I have a wierder problem with Pop3, which I really don't understand. I
can get my mail fine now using outlook on a computer on my network using pop
(due to your solution). However, when I go to work and attempt to get my
mail, using the same settings in MS Outlook, I get a failure to connect to
the server!

The only difference is wether I am coming from the outside, or I'm using my
own network. Am I missing something?

Feel free to try to use pop3. My mail server is mail.cybergood.net (an
alias), username: guest, password: guest. Leave the messages on the server,
if you can.

It is vaguely possible that it works now. I have no way of knowing. Since I
got home from work, I've poured throught the emails and have deleted the
ypbind server rpm.

Alex Miller

> -----Original Message-----
> From: Stewart Jeacocke [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, June 20, 1999 10:48 AM
> To: [EMAIL PROTECTED]
> Subject: qmail-pop3d.init errors
>
>
> Some people seem to have had problems getting the qmail-pop3d daemon to
> work using the qmail-pop3d.init script which the qmail srpm on
> www.qmail.org installs. I have successfully got this to work as follows
>
> First off you must install the checkpassword rpm
>
> Now you have to make qmail-pop3d run at boot
> Go to /etc/rc.d/rc3.d/ (or whatever runlevel you normally boot into)
> You should find that in this directory there is a link called
> K<n>qmail-pop3d.init , where <n> is a two digit number
> Now look for the link S<N>qmail.init, where <N> is another two digit
> number
> Rename K<n>qmail-pop3d.init to S<a>qmail-pop3d.init , where <a> is any
> two digit number you like as long as it is larger than <N>
> Restart or equivalent
>
> To summarize the rpm installs symbolic links to the qmail-pop3d.init
> script in the rc.d subdirectories. However it gives them numbers lower
> than the qmail.init script. This means that the pop3d script executes
> before the rest of qmail. Since it depends on other parts of the qmail
> system it fails.
>
> I am relatively new to Linux so any comments are welcome
>
> Stewart
>
>





This is not directly related to qmail but the only thing I have been
attempting to accomplish for the past week is qmail and ezmlm so I was
wondering if anyone else has had this problem.

All of a sudden, when I dial in rempotely using telnet, and I attempt to run
pico, I get an error "Incomplete termcap entry"

Now, if I am simply using my Linux box this doesn't happen.

Now, it's not really a problem for me, since I can use vi if I need to, but
it is a big problem for some of the people who are starting to use shell
access onto my Linux box and want to do editing. One of them is a 15 year
old, who I just taught how to use telnet and pico to edit a web page.

All of a sudden, pico is broken.

Two things seem to have been affected adversely upon installing the Memphis
RPM. One is that my Samba setup failed. That is, I used my Samba connection
to print some files before installing the Memphis RPM and after I installed
it, SAMBA had broken.

I am somewhat suspicious of the Memphis RPM because it doesn't just install
QMail, it installs some tcpserver init scripts which I assume must affect
TCP which would have some relation to Samba and telnet.

I know that pico worked on a remote telnet session earlier in the day when I
installed the Memphis RPM, and today was my first attempt since then.

Alex Miller





On Wed, Jun 23, 1999 at 10:07:22PM -0400, Alex Miller wrote:
> This is not directly related to qmail but the only thing I have been
> attempting to accomplish for the past week is qmail and ezmlm so I was
> wondering if anyone else has had this problem.
> 
> All of a sudden, when I dial in rempotely using telnet, and I attempt to run
> pico, I get an error "Incomplete termcap entry"

This is not only not directly related to qmail, it's not even remotely
indirectly related to qmail.

If you're using the Windows telnet client (which is, not surprisingly, junk),
try typing this at a prompt and then running pico again:

export TERM=vt100

Another solution is to get a better telnet (or ssh) client, such as those
you'll find at http://www.vandyke.com.

> Now, if I am simply using my Linux box this doesn't happen.
> 
> Now, it's not really a problem for me, since I can use vi if I need to, but
> it is a big problem for some of the people who are starting to use shell
> access onto my Linux box and want to do editing. One of them is a 15 year
> old, who I just taught how to use telnet and pico to edit a web page.
> 
> All of a sudden, pico is broken.
> 
> Two things seem to have been affected adversely upon installing the Memphis
> RPM. One is that my Samba setup failed. That is, I used my Samba connection
> to print some files before installing the Memphis RPM and after I installed
> it, SAMBA had broken.
> 
> I am somewhat suspicious of the Memphis RPM because it doesn't just install
> QMail, it installs some tcpserver init scripts which I assume must affect
> TCP which would have some relation to Samba and telnet.

tcpserver doesn't "affect TCP," whatever that might mean. I'd be very reluctant
to believe that the Memphis RPM affected Samba in any way. Nobody else has ever
reported it, and it's just plain unlikely that anyone could put together an RPM
in such a way that he inadvertantly disabled a totally unrelated service. If
Samba's breaking was coincident with your installing the Memphis RPM, then it's
probably just a coincidence. You should try to determine whether smbd is
running, and if not, why not. Never having used the Memphis RPM, I can almost
guarantee you that it has nothing to do with your Samba problems. I can
absolutely guarantee you that it has nothing to do with your telnet problems.

Sorry to sound so harsh, but rather than grasp at straws and make vague
inferences about various unrelated parts of your system interfering with each
other, you might sit down and try to figure out just exactly how all those
init.d scripts and rcX.d links work. Trace what happens when your system boots
up. Read the init (8) man page. Read the /etc/rc.d/rc script and try to follow
what's happening. Take a look at rc.local and realize that you can use it if
you don't want to deal with the the whole Sys V init thing. And try installing
qmail from the tarball again. If it doesn't work, figure out why and try to fix
it; don't assume that Redhat requires some kind of special magic--it doesn't.
What's required is a clear understanding of what each of qmail's various parts
does, which things are long-running daemons and which are executed per
connection, and an understanding of your own system so you can get everything
running at bootup that needs to be running. (My advice: forget about all those
init.d scripts for now, and launch everything from rc.local.)

If you do this, you'll realize that the Memphis RPM and tcpserver don't affect
Samba, and they certainly don't cause "incomplete termcap" problems.

Chris




> >2) Are there any drawbacks to the single-uid/virtualdomains approach?
>
> Users can't manage their own virtual domains without elaborate,
> privileged, homegrown web-sql-telnet-gui interfaces.
>
> -Dave

This is true. I find that the .qmail prepend notion is very powerful. Each
user has his/her own way of creating "new" mail addresses, especially new
mailinglists with ezmlm.

But there is also the value of 1 administrator handling the mail accounts of
many users. For example, if I give a create a domain
warrenjuniorhighschool.org it might make sense to have one or a few trusted
administrators handling the creation and administration of all these email
addresses.

So the question is:

Can QMail be configured to use both approaches, the single-uid virtual
domain approach and the many UID - independent user approach?

Alex Miller


> -----Original Message-----
> From: Dave Sill [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 22, 1999 3:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Implementation of Virtual Domains
>
>
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> >
> >Regarding the below instructions, I realize that the use of
> .qmail-* files
> >is how Qmail was "designed". But I find them to be rather clumsy.
>
> First, qmail wasn't "designed", it was designed.
>
> Second, you're entitled to your opinions, of course. I find them
> pretty elegant, myself.
>
> >For example, what if you have mail coming in to
> >
> >     .qmail-name1
> >     .qmail-name2
> >     .qmail-name3
> >
> >Unless most of them are forwarding, aren't we going to have to create
> >multiple stores, as in ./Maildir1, ./Maildir2, ... in the users home
> >directory?
>
> No. You can either save them to a common store, or individual
> stores. It's up to the user to decide. Want them all to go to
> ~/Maildir? Put "~/Maildir/" in all three files. Want them to go to
> ~MaildirN? Put "~/Maildir1/" in .qmail-name1, "~/Maildir2/" in
> .qmail-name2, etc.
>
> >(I'm assuming that the entry in "assign" is a wildcard, as:
> >
> >     +domain.com:popuser:888:888:/usr/qmail/popboxes/domain.com:-::)
> >
> >The implementation I prefer is specifying EVERY domain in
> "virtualdomains",
> >such as:
> >
> >     domain1.com:domain1.com
> >     domain2.com:domain2.com
> >
> >Then every user gets a private home directory and .qmail file (for
> >convenience, organized by domain):
> >
> >     /usr/qmail/popboxes/domain1.com/name1/.qmail
> >     /usr/qmail/popboxes/domain1.com/name1/Maildir/
> >
> >and there is a separate "assign" entry for each recipient of each domain:
> >
> >
> =domain1.com-name1:popuser:888:888:/usr/qmail/popboxes/domain1.com/name
> >1:-::
> >
> =domain1.com-name2:popuser:888:888:/usr/qmail/popboxes/domain1.com/name
> >2:-::
> >
> =domain2.com-name1:popuser:888:888:/usr/qmail/popboxes/domain1.com/name
> >1:-::
>
> YUCK. So every time Podunk, Inc., wants to add a new user, you have to
> update users/assign and rebuild users/cdb? What about wildcards?
>
> >We're an ISP, and it seems that Qmail was designed for a system with a
> >bunch of local users and that we're sort of having to "coerce"
> Qmail into
> >serving our needs.
>
> Not at all. qmail is designed to allow user-administered virtual
> domains and mailing lists. This is ISP-friendly behavior...unless
> you've got lots of spare time for handling petty user requests like
> this or automating the process.
>
> >I realize that the .qmail-* approach makes sense from a Unix
> point of view,
> >allowing all maildrops for that "user"
>
> "domain administrator"
>
> >to reside in a common directory. But
> >that implementation doesn't seem like it would scale well to
> large systems
> >with many domains as does the single-uid/virtualdomains approach.
>
> Why not? Where does it break down?
>
> >(Keep in
> >mind that we have automated the creation, deletion, forwarding,
> passwords,
> >etc of all accounts via a Telnet interface which we have linked
> through a
> >Visual Basic gui [coupled via a Sql Server database] that all our phone
> >reps can access, and we plan to put support for all these
> services on a web
> >page soon).
>
> If it's all automated, how does diddling users/assign and various
> .qmail files scale better than just diddling various .qmail files?
>
> >With  the single-uid/virtualdomains approach, every mail drop
> >can be manipulated with the same, automated interface.
>
> I fail to see where the "single-box domains" approach, as you call it,
> prevents that.
>
> >2) Are there any drawbacks to the single-uid/virtualdomains approach?
>
> Users can't manage their own virtual domains without elaborate,
> privileged, homegrown web-sql-telnet-gui interfaces.
>
> -Dave
>





Receive 

After installing qmail I can send out mail ok but I can't receive mail.
When I telnet to the local machine on port 25 and type anything, I get:
502 unimplemented (#5.5.1) 

Can anyone advise on how to fix this problem?

The local tests did not work either.  The log showed the message was sent
but there was no mail in the box.

Also, we did not have sendmail previously installed, however; I installed
the qmail-smtpd daemon.  

Thanks in advance.  Sienna





On Wed, Jun 23, 1999 at 11:06:18PM -0700, Sienna wrote:
> Receive 
> 
> After installing qmail I can send out mail ok but I can't receive mail.
> When I telnet to the local machine on port 25 and type anything, I get:
> 502 unimplemented (#5.5.1) 

That's not surprising. If you type just anything, it's unlikely that it's a
SMTP command. You should expect that whatever it is you typed is not
implemented in SMTP.

> Can anyone advise on how to fix this problem?
> 
> The local tests did not work either.  The log showed the message was sent
> but there was no mail in the box.
> 
> Also, we did not have sendmail previously installed, however; I installed
> the qmail-smtpd daemon.  
> 
> Thanks in advance.  Sienna
> 




On the local to local test.

When you installed you were given a choice between Mailboxes and Maildirs.
If you went with the Maildir approach you must make a Maildir for each user
using maildirmake in /var/qmail/bin and you must route the mail to that
maildir in the .qmail file for that user. The .qmail file must have
./Maildir/ in it to route to the Maildir. You will have to make sure that
/var/qmail/rc (not in my setup actually I used the Memphis RPM after using
the tarball) use maildir, (one of the install steps in install.MAILDIR

If you chose the Mailbox approach (I didn't) you will have to make sure that
var/qmail/rc uses mailbox.

As for your telnet connection failing. I was never able to get smtp to work
from the tarball. I only got it working after using the Memphis RPM, but
since then my Samba setup stopped working and pico doesn't work using remote
telnet (I suspect it is the tcpserver that was installed)

Alex Miller

> -----Original Message-----
> From: Sienna [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 24, 1999 2:06 AM
> To: [EMAIL PROTECTED]
> Subject: Help with receiving mail
>
>
> Receive
>
> After installing qmail I can send out mail ok but I can't receive mail.
> When I telnet to the local machine on port 25 and type anything, I get:
> 502 unimplemented (#5.5.1)
>
> Can anyone advise on how to fix this problem?
>
> The local tests did not work either.  The log showed the message was sent
> but there was no mail in the box.
>
> Also, we did not have sendmail previously installed, however; I installed
> the qmail-smtpd daemon.
>
> Thanks in advance.  Sienna
>
>





> I can't send mail from a mail client (Eudora) on my mac with my new mail
> server.  But, I'm betting I can figure out why.  (If anyone know's why,
> please let me know.)

You can only send mail from a mail client (using SMTP) to the hosts listed
in /var/qmail/rcpthosts. They are at least localhost and your hostname.
Those are the hosts you will relay to when calling in from a remote client.

I don't know how you allow a client to relay to the whole world. The problem
with that is that if you do, a spammer can take advantage of that and use
your computer for evil.

There were some postings on selective relaying. I believe that is allowing
certain trusted computers to have world send capability, but I'm not sure.

So, when you have an ISP email account that let's you send mail from
wherever you are, as long as you have the username and password, these ISP's
are subjecting their computers to potential spam attacks.

> -----Original Message-----
> From: Alex Miller [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 22, 1999 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: Important! FW: IT WORKS! - Anyone who is stuggling might
> benefit from this ...
>
>
>
>
> -----Original Message-----
> From: gene Campbell [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 22, 1999 3:12 AM
> To: [EMAIL PROTECTED]
> Cc: Stewart Jeacocke
> Subject: IT WORKS! - Anyone who is stuggling might benefit from this ...
>
>
> ... and might not.
>
> It took 3 painfull, grueling, days, and I'm still not sure what I did.
> But, it works.  What works?  I installed qmail on Linux 5.1 using the
> Memphis RPM.  I had tried this once before with the html version of the
> install docs: http://yoda.cs.ru.ac.za/~keith/redhat.html#memphis.  That
> didn't work.  I read at least 3 mails in this group that read that it
> works.  So, I tried again.  This time I followed the directions in the ftp
> directory:  ftp://moni.msci.memphis.edu/pub/qmail/README
>
> There was a part in there that read
>
>       The daemontools and ucspi-tcp packages install with /usr/local
>       prefix.
> and
>       Make sure that you are installing the daemontools and ucspi-tcp
>       package from this directory!!
>
> I'm not too sure what this means.  But, I moved to /usr/local, and did the
> rpm -Uvh's from there.  Can't say if this made any difference, but it
> worked.
>
> I also followed the advice from Stewart - See Stewart's advice below - to
> get pop3 working.
>
> I can't send mail from a mail client (Eudora) on my mac with my new mail
> server.  But, I'm betting I can figure out why.  (If anyone know's why,
> please let me know.)
>
> I also set up maildir.  Don't know what that really means.  But, it all
> works as expected.
>
> WHAT A RELIEF!  Thanks for all the help directly and indirectly.  It would
> have taken much much longer without you folks!!
>
> Gene Campbell
> mailto:[EMAIL PROTECTED]
> mailto:[EMAIL PROTECTED]
>
>
> ---  Stewart's advice  ---- Stewart Jeacocke
> <[EMAIL PROTECTED]>
>
> Some people seem to have had problems getting the qmail-pop3d daemon to
> work using the qmail-pop3d.init script which the qmail srpm on
> www.qmail.org installs. I have successfully got this to work as follows
>
> First off you must install the checkpassword rpm
>
> Now you have to make qmail-pop3d run at boot
> Go to /etc/rc.d/rc3.d/ (or whatever runlevel you normally boot into)
> You should find that in this directory there is a link called
> K<n>qmail-pop3d.init , where <n> is a two digit number
> Now look for the link S<N>qmail.init, where <N> is another two digit
> number
> Rename K<n>qmail-pop3d.init to S<a>qmail-pop3d.init , where <a> is any
> two digit number you like as long as it is larger than <N>
> Restart or equivalent
>
> To summarize the rpm installs symbolic links to the qmail-pop3d.init
> script in the rc.d subdirectories. However it gives them numbers lower
> than the qmail.init script. This means that the pop3d script executes
> before the rest of qmail. Since it depends on other parts of the qmail
> system it fails.
>
> I am relatively new to Linux so any comments are welcome
>
> Stewart
>
>
>
>





Method 1: (the host method)

In /var/qmail/rcpthosts put
supermall.dk
pcnet.dk
netpizza.dk
(this assumes that you have DNS entries already for these)

In /var/qmail/locals put
supermall.dk
pcnet.dk
netpizza.dk

Now the user martin will recieve mail addressed to [EMAIL PROTECTED],
[EMAIL PROTECTED], and [EMAIL PROTECTED]

Any user on your system will recieve mail at any of these 3 hosts.

Method 2: (better) (the virtual method)

In /var/qmail/rcpthosts put
supermall.dk
pcnet.dk
netpizza.dk
(this assumes that you have DNS entries already for these)

In /var/qmail/virtualdomains put
supermall.dk
pcnet.dk
netpizza.dk

Create 3 special users:
supermall.dk
pcnet.dk
netpizza.dk

in ~supermall.dk put the file .qmail containing &martin
in ~pcnet.dk put the file .qmail containing &martin
in ~netpizza.dk put the file .qmail containing &martin
(this assumes that martin is a user that can recieve mail)

The really interesting thing is that you can NOT user .qmail-default in the
~supermall.dk, ~pcnet.dk, and ~netpizza.dk directories to allow bounces on
misspellings.

Reserve the .qmail-default functionality for 3 additinal virtualhosts
virtual.supermall.dk, virtual.pcnet.dk, and virtual.netpizza.dk so
[EMAIL PROTECTED], [EMAIL PROTECTED], and
[EMAIL PROTECTED] will be captured if it is not specified by
another .qmail-addressname

Pretty cool, huh?

Alex Miller

> -----Original Message-----
> From: Martin Rehr [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 21, 1999 8:49 AM
> To: [EMAIL PROTECTED]
> Subject: Virtual Domains.
>
>
> Hello.
>
> I would like to know how to configure qmail to use virtual domains.
>
> My goal is making my qmail server responsible for the maildelivery for
> serveral domains.
>
> The problem is I don't know how to configure it.
>
> It is requered that:
>
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> Is 3 different email accounts.
>
> How should that be configured.
>
> It would be nice if someone could send me an description and maybe the
> configuration filses.
>
> Regards.
>     Martin Rehr / Supermall APS
>
> -------------------------------------------------------------------
> -- Linus
> Torvalds:
> --
> --
> --
> -- I don't think Microsoft is evil in
> itself;                                      --
> -- I just think that they make really crappy operating systems.     --
> -------------------------------------------------------------------
>
>
>





mail/mail notification is not working 

Thank you for your replies to the other questions which worked but now
having trouble getting the above thing to work.

Now I can receive mail but when I type "mail", It shows I have no mail in
my inbox.  However; if I go to the new mail under maildir I can see the
mail.  Also, the log file shows the delivery of the mail. 

Any suggestions?  Thanks again.

Sienna







On Thu, Jun 24, 1999 at 12:13:51AM -0700, Sienna wrote:
> mail/mail notification is not working 
> 
> Thank you for your replies to the other questions which worked but now
> having trouble getting the above thing to work.
> 
> Now I can receive mail but when I type "mail", It shows I have no mail in
> my inbox.  However; if I go to the new mail under maildir I can see the
> mail.  Also, the log file shows the delivery of the mail. 

The program called "mail" doesn't know about maildirs; it also doesn't know to
look in home directories for a mailbox. It's looking in /var/spool/mail (or
something similar). You'll need a maildir-aware MUA, like mutt or a
maildir-patched pine.

Chris




Mail is a mail client. I don't think there is a version of it that works
with Maildirs (yet).
Mutt is another mail client. To make Mutt work with maildirs do the
following:

in /etc/bashrc add the lines
MAIL=~/Maildir
export MAIL

This will let Mutt know to use Maildirs for every user. If you want some
users to use mailbox (bleh) then this command should be placed in the users
own .bashrc

The fact that Mutt already can handle Maildirs (the new way) with just an
environment variable is a sign of quality, btw.

Then at the user login just type mutt and there will all your mail be :-)

Of course if you aren't using bash then you have to set your environment
variables according to whatever shell you do use, but if your using LINUX
you are most likely using bash.

There is also pine. You would need to replace your current version of pine
with one that is patched for Maildir support.

I don't think the pine patch does that great a job since it still creates a
mailbox for it's sent folders.

But people who have shell access will probably already know about Pine and
it is easier on the beginner.

Alex Miller

> -----Original Message-----
> From: Sienna [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 24, 1999 3:14 AM
> To: [EMAIL PROTECTED]
> Subject: Almost there.. thanks. Need some more help
>
>
> mail/mail notification is not working
>
> Thank you for your replies to the other questions which worked but now
> having trouble getting the above thing to work.
>
> Now I can receive mail but when I type "mail", It shows I have no mail in
> my inbox.  However; if I go to the new mail under maildir I can see the
> mail.  Also, the log file shows the delivery of the mail.
>
> Any suggestions?  Thanks again.
>
> Sienna
>
>
>
>





Hi.

We all at our office were tired of one person emailing us.. After a quick
look in FAQ I added his email to /var/qmail/control/badmailfrom . Is it
enough to stop receiving mails from this guy , or I mess somth.? Any
better solutions?

Bye.Olli.





this should be ok!
do not forget to send a -HUP to qmail-send after editing the badmailfrom
file!

jodok


> -----Urspr�ngliche Nachricht-----
> Von:  olli [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Donnerstag, 24. Juni 1999 17:43
> An:   [EMAIL PROTECTED]
> Betreff:      kill mail from remote user
> 
> Hi.
> 
> We all at our office were tired of one person emailing us.. After a
> quick
> look in FAQ I added his email to /var/qmail/control/badmailfrom . Is
> it
> enough to stop receiving mails from this guy , or I mess somth.? Any
> better solutions?
> 
> Bye.Olli.




On Thu, Jun 24, 1999 at 10:45:04AM +0200, [EMAIL PROTECTED] wrote:

control/badmailfrom is read by qmail-smtpd, each time it starts up. No need
to HUP qmail-send.

> this should be ok!
> do not forget to send a -HUP to qmail-send after editing the badmailfrom
> file!
> 
> jodok
> 
> 
> > -----Urspr�ngliche Nachricht-----
> > Von:        olli [SMTP:[EMAIL PROTECTED]]
> > Gesendet am:        Donnerstag, 24. Juni 1999 17:43
> > An: [EMAIL PROTECTED]
> > Betreff:    kill mail from remote user
> > 
> > Hi.
> > 
> > We all at our office were tired of one person emailing us.. After a
> > quick
> > look in FAQ I added his email to /var/qmail/control/badmailfrom . Is
> > it
> > enough to stop receiving mails from this guy , or I mess somth.? Any
> > better solutions?
> > 
> > Bye.Olli.

-- 
Anand


Reply via email to