qmail Digest 19 Oct 1999 10:00:01 -0000 Issue 794
Topics (messages 31800 through 31831):
Mailing lists and virtual domains
31800 by: Paulo Jan
Re: Wrong date when qmail is called from /bin/mail
31801 by: farber.admin.f-tech.net
Re: Problems with trigger? (was: Re: qmail only delivers when restarted)
31802 by: David Dyer-Bennet
31806 by: David Villeger
31819 by: Todd A. Jacobs
31820 by: David Dyer-Bennet
Re: Qmail and DNS failures
31803 by: Eric Davis
qmail w/ U of W imapd
31804 by: Ben Beuchler
31809 by: Magnus Bodin
31818 by: Ben Beuchler
31821 by: Ian McNish
31823 by: David Harris
31829 by: Mirko Zeibig
Help: VERY strange problem
31805 by: Alex Povolotsky
31807 by: Markus Stumpf
qmail tutorial at ISPF
31808 by: Russell Nelson
Re: qmail only delivers when restarted
31810 by: David Villeger
Re: mail appliance
31811 by: Florian G. Pflug
31812 by: Markus Wuebben
31813 by: Jon Rust
31815 by: Ken Jones
31817 by: Jon Rust
www.qmail.org news.
31814 by: Russell Nelson
31830 by: Mirko Zeibig
Retraction
31816 by: Russell Nelson
Changing the default directory in qmail doesn't work
31822 by: Steve Quezadas
31825 by: Russell Nelson
ezmlm mailing lists
31824 by: Haifeng Guo
Re: Problems with trigger?
31826 by: Rogerio Brito
Virtual domain problems
31827 by: Hennie Rautenbach
31828 by: Magnus Bodin
Help! allowed rcpthosts
31831 by: Assela Pathirana
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 all:
I used to have a virtual domain, let's call it dominio.com, hosted at
our mail server. It was listed both in "locals" and "rcpthosts" (don't
ask why), and I had created a mailing list for it with the @dominio.com
domain, using EZML ([EMAIL PROTECTED]). Now I've decided to turn
that domain into a "real" virtual domain, so I deleted them from
"locals" and added them to "virtualdomains":
dominio.com:vuser
And I created the right .qmail files in the home directory of the user
"vuser". The problem now is that I don't know how to migrate the mailing
list to the new setup; is it enough to create .qmail-list-dominio in the
"vuser" directory to catch the messages sent to the list? Would I need
to re-create the list under the "vuser" directory? Or what else?
(Sorry, BTW, for not putting the "real" domain and list name here, but
neither the customer nor my PHB would be very happy if I did so; plus, I
believe that the domain or virtual user names aren't really that
relevant here (correct me if I'm wrong)).
Paulo Jan.
DDnet.
I don't know.
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Sun, 17 Oct 1999, Todd A. Jacobs wrote:
> On Sun, 17 Oct 1999 [EMAIL PROTECTED] wrote:
>
> > /bin/mail is not putting the headers on your mail.. the MTA/MUA is (ie
> > sendmail/qmail and pine).
>
> But it used to when running under sendmail. Someone else told me that
> qmail defaults to using zulu. Is there a way to force it to use local
> time, instead of GMT?
>
> --
> Todd A. Jacobs
> Network Systems Engineer
>
>
>
Chris Green <[EMAIL PROTECTED]> writes on 18 October 1999 at 09:21:03 +0100
> On Sun, Oct 17, 1999 at 05:10:38PM -0400, David Villeger wrote:
> > I am convinced this problem is caused by people who try to copy /var/qmail
> > and don't do it right.
> >
> That was certainly how I managed to screw it up. I upgraded from
> Linux RedHat 5.2 to Mandrake 6.1, I had a new drive to install on so
> just mounted the old RedHat drive on the new system so I could copy
> files across and so on.
>
> I copied the qmail installation basically by doing:-
> cp -R /oldvar/qmail/* /var/qmail
Okay, that makes sense. I'm in the habit of using "cp -a" when I try
to move stuff from one place to another. The man page seems to say
this would work -- at least it says -a preserves ownerships and
permissions (when run as root, at least :-) ).
I was really uncomfortable having this fairly frequent error not
understood (at least by me).
--
David Dyer-Bennet [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
At 08:48 AM 10/18/99 -0500, David Dyer-Bennet wrote:
>Chris Green <[EMAIL PROTECTED]> writes on 18 October 1999 at 09:21:03 +0100
> >
> > I copied the qmail installation basically by doing:-
> > cp -R /oldvar/qmail/* /var/qmail
>
>Okay, that makes sense. I'm in the habit of using "cp -a" when I try
>to move stuff from one place to another. The man page seems to say
On Solaris, I think it's "cp -p". However, it doesn't preserve symlinks
(that is, it follows the links and copies the files instead of the links
themselves).
As a rule I always use:
tar cf - . | (cd /new_dir; tar xvf -)
or equivalent (using ssh or using ufsdump if the pathnames are really long,
etc...). It gives me flexibility and makes exact copies.
David.
On Mon, 18 Oct 1999, David Dyer-Bennet wrote:
> > I copied the qmail installation basically by doing:-
> > cp -R /oldvar/qmail/* /var/qmail
Hmmm. I tarred my qmail directory and moved it to another
partition. Doesn't tar preserve permissions by default?
--
Todd A. Jacobs
Network Systems Engineer
Todd A. Jacobs <[EMAIL PROTECTED]> writes on 18 October 1999 at 14:28:10 -0700
> On Mon, 18 Oct 1999, David Dyer-Bennet wrote:
>
> > > I copied the qmail installation basically by doing:-
> > > cp -R /oldvar/qmail/* /var/qmail
>
> Hmmm. I tarred my qmail directory and moved it to another
> partition. Doesn't tar preserve permissions by default?
I thought it did if you were root, anyway. However, the obvious entry
in the info file doesn't make any mention of that behavior; maybe it
only does it when requested. (GNU tar)
`--preserve-permissions'
`--same-permissions'
`-p'
When `tar' is extracting an archive, it normally subtracts the
users' umask from the permissions specified in the archive and
uses that number as the permissions to create the destination
file. Specifying this option instructs `tar' that it should use
the permissions directly from the archive. *Note Writing::.
--
David Dyer-Bennet [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
> TEMPFAIL means exactly what it means, a temporary failure, so the
> message gets rescheduled for another delivery attempt.
>
> This particular situation is very common when a domain has been shut
> down before the expiration date of the domain's registration with
> Internic. The hotmial.com zone was purged from these servers a long
> time ago, so when they get a query for hotmial.com, they know nothing
> about it, so they go to the root nameservers, which then tell them
> that they themselves are indeed authoritative for the zone. Some
> domain name servers will simply fail to return an answer to the query,
> in this situations, and some domain name server will return a
> TEMPFAIL. Either way, DNS resolvers interpret this as a temporary
> failure.
>
> If you were to investigate each one of your problem domains, you will
> reach more or less the same conclusion every time. The response to
> the DNS query either times out, or returns something other than
> NXDOMAIN, so the message gets temporarily bumped.
>
> If a domain really does not exist, the root name servers will return
> NXDOMAIN.
I just wanted to post a thank you personally to everyone who answered
my question (even though in looking back at it I see how it's not a
qmail issue really) and pointing me in the right direction to why I
was seeing what I was seeing.
-Eric Davis
[EMAIL PROTECTED]
The adventures with IMAP continue.
I just installed the U of W imapd. Apparently there are no configuration
options for this server. My understanding is that it uses whatever mailbox
setup is currently being used by Linux. So... I set up a .qmail file in a
users ("charlie") home directory containing the line "/home/charlie/mbox" and
sent a half dozen messages to that user. I viewed his mbox file with less just
to confirm it did indeed contain the messages. Then I set up an account for
charlie in Outlook 98 and attempted to view his messages. Outlook connected
just fine, but didn't indicate that there was any mail to be read in his folder!
Am I missing something?
Ben
--
Powered by Linux. And pizza.
On Mon, Oct 18, 1999 at 09:43:12AM -0500, Ben Beuchler wrote:
> The adventures with IMAP continue.
>
> I just installed the U of W imapd. Apparently there are no configuration
> options for this server. My understanding is that it uses whatever mailbox
> setup is currently being used by Linux. So... I set up a .qmail file in a
> users ("charlie") home directory containing the line "/home/charlie/mbox" and
> sent a half dozen messages to that user. I viewed his mbox file with less just
> to confirm it did indeed contain the messages. Then I set up an account for
> charlie in Outlook 98 and attempted to view his messages. Outlook connected
> just fine, but didn't indicate that there was any mail to be read in his folder!
>
> Am I missing something?
Yes. Use Maildir delivery, and David Harris fine patch-FIXES for the
qmail-imap-patches. Everything is nicely wrapped up here:
http://www.davideous.com/imap-maildir/
--
magnus
-- MOST useless 1998 * http://x42.com/
Is it absolutely necessary to do this? I would like to at least get it
functioning with 'mbox' support before I start messing with patches. is there
anything else I need to do first? I have a nasty suspicion that if it's not
working now, with it's 'most favored' mailbox format, it's going to work even
less well with a patched mailbox format.
Ben
> > I just installed the U of W imapd. Apparently there are no configuration
> > options for this server. My understanding is that it uses whatever mailbox
> > setup is currently being used by Linux. So... I set up a .qmail file in a
> > users ("charlie") home directory containing the line "/home/charlie/mbox" and
> > sent a half dozen messages to that user. I viewed his mbox file with less just
> > to confirm it did indeed contain the messages. Then I set up an account for
> > charlie in Outlook 98 and attempted to view his messages. Outlook connected
> > just fine, but didn't indicate that there was any mail to be read in his folder!
> >
> > Am I missing something?
>
> Yes. Use Maildir delivery, and David Harris fine patch-FIXES for the
> qmail-imap-patches. Everything is nicely wrapped up here:
>
> http://www.davideous.com/imap-maildir/
>
---
Powered by Linux. And pizza.
Ben Beuchler wrote:
>
> Is it absolutely necessary to do this? I would like to at least get it
> functioning with 'mbox' support before I start messing with patches. is there
> anything else I need to do first? I have a nasty suspicion that if it's not
> working now, with it's 'most favored' mailbox format, it's going to work even
> less well with a patched mailbox format.
>
> Ben
>
> > > I just installed the U of W imapd. Apparently there are no configuration
> > > options for this server. My understanding is that it uses whatever mailbox
> > > setup is currently being used by Linux. So... I set up a .qmail file in a
> > > users ("charlie") home directory containing the line "/home/charlie/mbox" and
> > > sent a half dozen messages to that user. I viewed his mbox file with less just
> > > to confirm it did indeed contain the messages. Then I set up an account for
> > > charlie in Outlook 98 and attempted to view his messages. Outlook connected
> > > just fine, but didn't indicate that there was any mail to be read in his folder!
> > >
> > > Am I missing something?
> >
> > Yes. Use Maildir delivery, and David Harris fine patch-FIXES for the
> > qmail-imap-patches. Everything is nicely wrapped up here:
UW imapd, by default pulls mail from /var/mail or /var/spool/mail.
qmail, on the other hand, delivers to a users home dir. you need to
either configure qmail to deliver to /var/mail or configure imapd to use
mailboxes in the users home dir. NOTE: the authors of qmail spent time
finding good ways of avoiding /var/mail, so i'd recommend you not go
there.
there are instructions with qmail (read INSTALL.vsm) for configuring
qmail to deliver to /var/mail, and there are instructions with the UW
imap package (at least v4.5 and 4.6 in docs/CONFIG) for how to modify
imapd to read from a users home dir.
both of these options will allow you to continue to use the mbox
format.
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
> there are instructions with qmail (read INSTALL.vsm) for configuring
> qmail to deliver to /var/mail, and there are instructions with the UW
> imap package (at least v4.5 and 4.6 in docs/CONFIG) for how to modify
> imapd to read from a users home dir.
If you want to make UW IMAP read from the Mailbox file in the user's home
directory, you can just apply the imap-4.5-qmail.patch from my
davideous.com/imap-maildir/ site. This patch causes the Mbox driver to look for
the INBOX in the standard qmail location of ~/Mailbox instead of in the system
mail spool (which is /var/spool/mail/$USER on my system).
- David Harris
Principal Engineer, DRH Internet Services
Hello Ben,
I had some problems with (the RedHat-binary-version) of imapd 4.5 and
delivery to $HOME/mbox and deletion of messages (not if I explicitely marked
them for deletion but if I moved them to another mailfolder and they were
marked as deleted by imapd automatically).
In version 4.6 imapd first does look for $HOME/mbox (or $HOME/mbx) if it is
there and the deletion-problem was gone as well.
Regards
Mirko
--
mailto: [EMAIL PROTECTED]
privat: http://sites.inka.de/picard
commerce: http://www.webideal.de
qmail, ldap, serialfax, rh-isdn: http://www.webideal.de/#downloads
Hello!
I've set up qmail for several virtual domains, using FreeBSD 3.3-RELEASE,
and everything went just fine, until...
I've set up inbound dialup.
I've tested all day today, I have 100% correlation, if ppp0 is up and
assigned, qmail-smtp crashes with signal 11 in constmap called from
rcpthosts called from addrallowed called from smtp_rcpt.
Also, attempt to send mail to remote host fails with VERY strange error
(host structure in qmail-remote gets _OVERWRITTEN_!!! somewhere in ipme_init).
I've tried to rebuild qmail (1.03), it doesn't help at all.
I've read all manuals and sources I was able to understand, but still
understands nothing. I need some help befor my head will be cut off...
Alex.
P.S. Any details including coredumps are available on request.
Alex.
On Mon, Oct 18, 1999 at 07:32:37PM +0400, Alex Povolotsky wrote:
> I've set up qmail for several virtual domains, using FreeBSD 3.3-RELEASE,
> and everything went just fine, until...
Did you read the 3.3R/errata ??
I'm just guessing ...
but there are two problems, one with lo0 and one with ppp(8) ... maybe
there is some strange correlation with qmail?
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
By the way, I will be giving a tutorial November 15th on qmail at
ISPF III. See http://www.ispf.com for more information.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free 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!
At 06:17 PM 10/17/99 -0500, David Dyer-Bennet wrote:
>Todd A. Jacobs <[EMAIL PROTECTED]> writes on 17 October 1999 at 15:43:35
-0700
> > On Sun, 17 Oct 1999, David Dyer-Bennet wrote:
> >
> > > > Check the permissions on /var/qmail/queue/lock/trigger. They
should look like
> > > > this:
> > > >
> > > > prw--w--w- 1 qmails qmail 0 Oct 16 17:39 trigger
> >
> > That was definitely the problem in my case. I'm not sure how it changed,
> > though. If I find out, I promise you'll be the second one to know. :)
> >
> > I couldn't find any info on the trigger file. Can you explain how qmail is
> > using this named pipe, and why it has to be world-writable?
>
>I haven't examined this bit of source just recently, but very roughly,
>qmail-inject uses this to alert the central q-management process that
>there's new business waiting. Since qmail-inject runs as any user
>sending mail, the trigger needs to be world-writable. I'm sure the
>process on the other end of that pipe is *very* careful what it does
>with whatever comes through it!
I don't think qmail-send does anything with what comes through the pipe.
The pipe is a trigger. When qmail-queue injects a message in the queue, it
writes a byte in the FIFO.
Qmail-send keeps listening to the FIFO (through a select() call so that it
doesn't waste cpu time). When the byte is written, the select() call "wakes
up" and qmail-send knows there is something is the queue.
If the FIFO has wrong permissions, qmail-queue can't write to it and
qmail-send never knows there is mail waiting to be processed. However,
qmail-send wakes itself up every 20 minutes (?) by sending an ALRM signal.
This is why people see the queue processed in batches every 20 minutes.
David.
On Sun, Oct 17, 1999 at 02:43:38PM -0700, Jon Rust wrote:
> I'm trying to build a mail "appliance" that I can install for
> customers who know nothing about UNIX and/or qmail. I suppose webmin
> will do for adding users, though a bit clumsy. Even so, that still
> leaves forwarding and vacation messages out. I'll try to write some
> scripts of my own for this purpose, but if someone wants to share,
> that would be great. Just looking for some no-frills, perl/shell CGI.
I have written a few shell scripts.
They are based on the tip given on the qmail-homepage on how to make qmail
work for a lot of different domains & users without an os-user for every
account (by using users/assign & virtualdomains).
This script can
.) create domains (on the fly - with a suid-c-programm that send sighup to
qmail.
.) create users in the domains
.) set the pop-password
.) define forwards
.) protect users & domains from being deleted
.) supports "notifying" users with pop-account of new mail by sending them a
finger for the user nm_notifymail.
The whole thing is quite usable, but I fear itīs no very portable - one
could even say "dirty design"... ;-)
greetings, Florian Pflug
On Sun, 17 Oct 1999, Jon Rust wrote:
> I'm trying to build a mail "appliance" that I can install for
> customers who know nothing about UNIX and/or qmail. I suppose webmin
> will do for adding users, though a bit clumsy. Even so, that still
> leaves forwarding and vacation messages out. I'll try to write some
> scripts of my own for this purpose, but if someone wants to share,
> that would be great. Just looking for some no-frills, perl/shell CGI.
>
Check this out:
http://www.inter7.com/qmailadmin/
Later,
Markus
> thanks,
> jon
>
--
(Products & Development)
___________________________________________________
IP-PRO GmbH http://www.id-pro.de
Open for the better ...
___________________________________________________
qmailadmin does not handle management of local accounts. It only
handles management of virtuals. Not too bad really, but that requires
you to have a pop prefix. Trying to avoid that...
jon
At 8:33 PM +0200 10/18/99, Markus Wuebben wrote:
>On Sun, 17 Oct 1999, Jon Rust wrote:
>
>> I'm trying to build a mail "appliance" that I can install for
>> customers who know nothing about UNIX and/or qmail. I suppose webmin
>> will do for adding users, though a bit clumsy. Even so, that still
>> leaves forwarding and vacation messages out. I'll try to write some
>> scripts of my own for this purpose, but if someone wants to share,
>> that would be great. Just looking for some no-frills, perl/shell CGI.
>>
>
>
>Check this out:
>
>
>http://www.inter7.com/qmailadmin/
>
>
>
>Later,
>Markus
You can setup your local accounts as a virtual domain and hence use
qmailadmin without requiring a pop prefix. you can also avoid the
vpopmail popname syntax of user%virtualdomain by linking the
vpopmail directory for the domain to the vpopmail/users directory.
Ken Jones
Jon Rust wrote:
>
> qmailadmin does not handle management of local accounts. It only
> handles management of virtuals. Not too bad really, but that requires
> you to have a pop prefix. Trying to avoid that...
>
> jon
>
> At 8:33 PM +0200 10/18/99, Markus Wuebben wrote:
> >On Sun, 17 Oct 1999, Jon Rust wrote:
> >
> >> I'm trying to build a mail "appliance" that I can install for
> >> customers who know nothing about UNIX and/or qmail. I suppose webmin
> >> will do for adding users, though a bit clumsy. Even so, that still
> >> leaves forwarding and vacation messages out. I'll try to write some
> >> scripts of my own for this purpose, but if someone wants to share,
> >> that would be great. Just looking for some no-frills, perl/shell CGI.
> >>
> >
> >
> >Check this out:
> >
> >
> >http://www.inter7.com/qmailadmin/
> >
> >
> >
> >Later,
> >Markus
At 2:00 PM -0500 10/18/99, Ken Jones wrote:
>You can setup your local accounts as a virtual domain and hence use
>qmailadmin without requiring a pop prefix. you can also avoid the
>vpopmail popname syntax of user%virtualdomain by linking the
>vpopmail directory for the domain to the vpopmail/users directory.
>
>Ken Jones
Hey, cool trick! Thanks.
Jon
I'm now extracting the updated sections of www.qmail.org into
http://www.qmail.org/news.html.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free 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 Mon, Oct 18, 1999 at 02:54:09PM -0400, Russell Nelson wrote:
> I'm now extracting the updated sections of www.qmail.org into
> http://www.qmail.org/news.html.
Hello Russel,
good idea (though (ooh, always complaining ;-)) I would do the link to the
news-page a little bigger, but that's just a matter of style.
Best regards
Mirko
Sorry, it turns out that I'm NOT giving a tutorial at ISPF. However,
if I can get together enough people who wish to attend such, I'm sure
I can convince the ISPF management to run one. It would be on Sunday
the 14th.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free 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!
I am trying to change the default directory of Qmail. I don't like
having the Mailbox mixed in with the other end user's crap in his home
directory. Ideally, I would like it to be delivered to ~/Mailbox in file
"Inbox" insted of just ~ in file Mailbox. So I went into the rc file and
changed the line to read:
qmail-start ./Mailbox/Inbox splogger qmail
However, when I restart qmail, the directory does not automatically get
created and the message is never received in teh user's home mail
directory. SO I checke the syslogs and this is what I get:
Oct 18 12:49:05 LinuxServer qmail: 940276145.358374 delivery 4:
deferral: Unable_to_open_./Mailbox/Inbox:_file_does_not_exist._(#4.2.1)/
Is there any way to have qmail automatically create the subdirectory if
it does not already exist or do I have to manually create a "Mailbox"
directory with each and every user?
- Steve
Steve Quezadas writes:
> qmail-start ./Mailbox/Inbox splogger qmail
> do I have to manually create a "Mailbox" directory with each and
> every user?
Yup.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free 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!
Hi guys:
I have install qmail and ezmlm+ezmlm-idx on my server,I have two server for
mailing list,one is m1.a.com and the other is m2.a.com, and I want the
mailing lists on both of the server can use the name a.com for sub ,unsub
and send mail(for example: on the m1.a.com has a mailing list vb and on the
m2.a.com has a mailing list vb ,I wish both of them can use [EMAIL PROTECTED] and
[EMAIL PROTECTED] ,how to setup this,just like egroups.com),thanks.
On Oct 18 1999, David Villeger wrote:
> As a rule I always use:
> tar cf - . | (cd /new_dir; tar xvf -)
> or equivalent (using ssh or using ufsdump if the pathnames are really long,
> etc...). It gives me flexibility and makes exact copies.
If you use GNU's cp, you could use the -a option.
[]s, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hi there,
I followed the instructions in the FAQ w.r.t. how to set up a virtual
domain and have mail forwarded there. I used the "nowhere.mil:bob"
example. However, the FAQ seems a bit vague about non-local addresses.
I want to have "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" (which doesn't
exist as local accounts to be forwarded to [EMAIL PROTECTED] and
[EMAIL PROTECTED] respectively.
How do I set up forwarding of these addresses ?
Looking forward to any advice.
Hennie
--
=======================================================================
Hennie Rautenbach Work: http://www.sabinet.co.za
SABINET Online Play: http://www.overland.co.za
082-556-1191 Mail: [EMAIL PROTECTED]
"Live as if you were to die tomorrow. Learn as if you were to live
forever" -- Mahatma Gandhi
=======================================================================
On Tue, Oct 19, 1999 at 08:13:34AM +0200, Hennie Rautenbach wrote:
> Hi there,
>
> I followed the instructions in the FAQ w.r.t. how to set up a virtual
> domain and have mail forwarded there. I used the "nowhere.mil:bob"
> example. However, the FAQ seems a bit vague about non-local addresses.
>
> I want to have "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" (which doesn't
> exist as local accounts to be forwarded to [EMAIL PROTECTED] and
> [EMAIL PROTECTED] respectively.
>
> How do I set up forwarding of these addresses ?
The "nowhere.mil:bob" in virtualdomains alternative
===================================================
If you use the "nowhere.mil:bob" in virtualdomains, then all mail is
delivered to the user bob.
This effectively mean that mail for [EMAIL PROTECTED] is delivered to
~bob/.qmail-info if it exists, and otherwise to ~bob/.qmail
If you want to forward the mail form "[EMAIL PROTECTED]" to
"[EMAIL PROTECTED]", then put the line
&[EMAIL PROTECTED]
in ~bob/.qmail-info (no leading spaces).
(repeat with help, etc. One .qmail-file for each.)
Other alternatives are:
The "nowhere.mil:alias-nowhere" in virtualdomains alternative
=============================================================
This is better if bob also is a normal user, and he and the system
administrator wants to keep the nowhere.mil mail out of his user
account.
The mail is delivered to the .qmail-files ~alias/.qmail-nowhere-*
This means that mail for [EMAIL PROTECTED] is delivered to
~alias/.qmail-nowhere-info
Thus, put the line
&[EMAIL PROTECTED]
into ~alias/.qmail-nowhere-info and you are all set for this forwarding.
(Repeat with help, etc. One .qmail-file for each.)
The forward-all-to-another-domain-alternative
=============================================
This is when you want to forward <anything>@nowhere.mil to
<anything>@elsewhere.co.za, i.e. when every forward goes to
the same "otherhost".
Put "nowhere.mil:alias-nowhere" into virtualdomains.
Then put this line into ~alias/.qmail-nowhere
| forward ${DEFAULT}@elsewhere.co.za
Now will all mail be forwarded to the domain elsewhere.co.za.
Every username will however be intact.
If you want to override this for just some user, then create an own
.qmail-file for just that alias, e.g. .qmail-nowhere-support, and put
your own forward in there.
The fastforward-alternative
===========================
This is the best alternative for a bigger virtual domain.
Put "nowhere.mil:alias-nowhere" in virtualdomains
and install the fastforward package
<http://www.qmail.org/koobera/www/fastforward.html>.
Then put every alias for nowhere.mil in /etc/aliases
like this:
[EMAIL PROTECTED]:[EMAIL PROTECTED]
[EMAIL PROTECTED]:[EMAIL PROTECTED]
Finally put the line
| fastforward -d /etc/aliases.cdb
in ~alias/.qmail-nowhere
(Compile the aliases file with /var/qmail/bin/newaliases)
--
magnus
-- MOST useless 1998 * http://x42.com/
Hi,
I am new to this list.
I have installed qmail in two Solaris machines. They can access proper name
servers. Massegaes to local users can be delivered from local host and from
outside. Mail can be injected to any remote user by using qmail-inject.
Problem:
I can not use smtp dialog to send mail to any remote recipients.
Can anybody give me a hand?
Thanks
Assela
------------------------------------------------------------------------------------------------
(1) rcpthosts file has the single entry:
axel.iis.u-tokyo.ac.jp (which is the machine name)
------------------------------------------------------------------------------------------------
(2) Here's the smtp dialog
Escape character is '^]'.
220 axel.iis.u-tokyo.ac.jp ESMTP
helo dude
250 axel.iis.u-tokyo.ac.jp
mail <[EMAIL PROTECTED]>
250 ok
rcpt <[EMAIL PROTECTED]>
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
------------------------------------------------------------------------------------------------
(3) Here's the qmail-showctl response.
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 7790, 7791, 7792, 0, 7793, 7794, 7795, 7796.
group ids: 2108, 2107.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is axel.iis.u-tokyo.ac.jp.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is iis.u-tokyo.ac.jp.
defaulthost: (Default.) Default host name is axel.iis.u-tokyo.ac.jp.
doublebouncehost: (Default.) 2B recipient host: axel.iis.u-tokyo.ac.jp.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is axel.iis.u-tokyo.ac.jp.
helohost: (Default.) SMTP client HELO host name is axel.iis.u-tokyo.ac.jp.
idhost: (Default.) Message-ID host name is axel.iis.u-tokyo.ac.jp.
localiphost: (Default.) Local IP address becomes axel.iis.u-tokyo.ac.jp.
locals:
Messages for localhost are delivered locally.
Messages for axel.iis.u-tokyo.ac.jp are delivered locally.
me: My name is axel.iis.u-tokyo.ac.jp.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is ac.jp.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
rcpthosts:
SMTP clients may send messages to recipients at axel.iis.u-tokyo.ac.jp.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 axel.iis.u-tokyo.ac.jp.
smtproutes: (Default.) No artificial SMTP routes.
timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.
virtualdomains: (Default.) No virtual domains.
defaultdelivery: I have no idea what this file does.
--
_______________________________________________
Assela Pathirana
Water Resource Engineering Laboratory, 5th dept.,
IIS, University of tokyo,
Building No. C,4-6-1, Komaba,Meguro-ku
Tokyo 153-8505
Tel. +81 (3) 03-5452-6440 (Home: +81 (44) 955-9995)
Fax. +81 (3) 03-5452-6476
URL: http://www.iis.u-tokyo.ac.jp/~assela
