qmail Digest 13 Jul 1999 10:00:00 -0000 Issue 696

Topics (messages 27697 through 27749):

fetchmail+sendmail+procmail = qmail?
        27697 by: Yan Seiner <[EMAIL PROTECTED]>
        27715 by: Yan Seiner <[EMAIL PROTECTED]>

Source Routing Relaying
        27698 by: Dave Sill <[EMAIL PROTECTED]>

lwq/serialmail
        27699 by: Dave Sill <[EMAIL PROTECTED]>

nested aliases
        27700 by: Dave Sill <[EMAIL PROTECTED]>

Forwarding to variable username
        27701 by: Russell Nelson <[EMAIL PROTECTED]>
        27734 by: "Jim Gilliver" <[EMAIL PROTECTED]>

About mailing lists
        27702 by: Tero Niemi <[EMAIL PROTECTED]>
        27703 by: Dave Sill <[EMAIL PROTECTED]>
        27705 by: "Soffen, Matthew" <[EMAIL PROTECTED]>
        27706 by: Anand Buddhdev <[EMAIL PROTECTED]>

wrapping qmail-inject - can I?
        27704 by: Anand Buddhdev <[EMAIL PROTECTED]>

Acknowledgement ?
        27707 by: "Tarkan Hocaoglu" <[EMAIL PROTECTED]>
        27708 by: Dave Sill <[EMAIL PROTECTED]>
        27714 by: "Sam" <[EMAIL PROTECTED]>

lwq/pop3d
        27709 by: "Jacob (Mettavihari)" <[EMAIL PROTECTED]>
        27710 by: Dave Sill <[EMAIL PROTECTED]>

autoconf?
        27711 by: Russell Nelson <[EMAIL PROTECTED]>
        27716 by: "Sam" <[EMAIL PROTECTED]>
        27740 by: Russ Allbery <[EMAIL PROTECTED]>

headers.
        27712 by: [EMAIL PROTECTED]
        27713 by: Dave Sill <[EMAIL PROTECTED]>

cleaning out queue.
        27717 by: "Tony D'Andrade" <[EMAIL PROTECTED]>
        27721 by: Dave Sill <[EMAIL PROTECTED]>
        27729 by: "Tony D'Andrade" <[EMAIL PROTECTED]>
        27731 by: "Aaron L. Meehan" <[EMAIL PROTECTED]>
        27746 by: Chris Johnson <[EMAIL PROTECTED]>

Qmailanalog, want per msg information
        27718 by: Eric Dahnke <[EMAIL PROTECTED]>
        27720 by: Dave Sill <[EMAIL PROTECTED]>

periodic cleanup of email
        27719 by: Diego Puertas <[EMAIL PROTECTED]>

does pine use qmail-inject?
        27722 by: Robert Varga <[EMAIL PROTECTED]>
        27725 by: Richard Letts <[EMAIL PROTECTED]>
        27726 by: Robert Varga <[EMAIL PROTECTED]>
        27735 by: Richard Letts <[EMAIL PROTECTED]>
        27736 by: "Sam" <[EMAIL PROTECTED]>
        27738 by: Robert Varga <[EMAIL PROTECTED]>

info
        27723 by: "Alex Miller" <[EMAIL PROTECTED]>

pine does NOT use qmail-inject (uses /usr/sbin/sendmail)
        27724 by: Robert Varga <[EMAIL PROTECTED]>
        27737 by: "Sam" <[EMAIL PROTECTED]>

Using qmail with CGI feedback form - needing reference
        27727 by: "Dan Poynor" <[EMAIL PROTECTED]>
        27728 by: "Reid Sutherland" <[EMAIL PROTECTED]>
        27730 by: Markus Stumpf <[EMAIL PROTECTED]>
        27733 by: [EMAIL PROTECTED]
        27743 by: "Dan Poynor" <[EMAIL PROTECTED]>
        27745 by: "Reid Sutherland" <[EMAIL PROTECTED]>
        27748 by: Sergei Kolobov <[EMAIL PROTECTED]>
        27749 by: Stefan Paletta <[EMAIL PROTECTED]>

Aliasing using fastforward
        27732 by: Chris Galanos <[EMAIL PROTECTED]>

A Re-Explanation of my aliasing problem
        27739 by: "Chris Galanos" <[EMAIL PROTECTED]>

Problem running qmail-pop3d under tcpserver
        27741 by: "Alvaro Escobar" <[EMAIL PROTECTED]>
        27742 by: Keith Burdis <[EMAIL PROTECTED]>

child exited 127 () (fwd)
        27744 by: [EMAIL PROTECTED] (IBRIC - International Buddhist Research & Info. 
Center)

Virus scanning with qmail+amavis (Take 2)
        27747 by: Christopher Seawood <[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]


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


I am new to this list and to qmail.  I am trying to set up a more secure
server so I am in the process of dumping sendmail.  

Here's the present setup:

our email is collected by our ISP and deposited in a single mailbox (3
domains, two dozen users).

Fetchmail collects our email and forwards to the local postmaster
account.  The postmaster account has a .procmailrc file, which then
invokes procmail.  The procmail recipes simply look at the recipient and
send the proper email to the proper place.  No fancy recipes are used at
all; just straight forwarding based on address.  EG:  [EMAIL PROTECTED]
gets forwarded to [EMAIL PROTECTED]

I feel that I am using a cannon to squash a mouse - and I keep thinking
that there must be some simpler way to do what I am doing.

I've been reading through the archives, and fetchmail has received its
share of getting trashed, but there's also recommendations to use it.

>From reading the docs, it seems that I may be able to get rid of
procmail in my setup?  Can qmail forward to different users based on
address?  

Is fetchmail the way to go to collect POP3 mail or should I be looking
elsewhere?

I am looking for general recommendations and pointers on how to set this
up.  I can read docs; I just need some help on which docs to read :-)

Yan
-- 

           __      __
          | /      /
           /------/
       -- / \    / \ --
     /   /\  \  /  /\   \
    |   /  |  \/--|--    |
     \    /        \    /
       ~~            ~~

"The older I get, the faster I was."




(Sorry if this is repost)

I am new to this list and to qmail.  I am trying to set up a more secure
server so I am in the process of dumping sendmail.  

Here's the present setup:

our email is collected by our ISP and deposited in a single mailbox (3
domains, two dozen users).

Fetchmail collects our email and forwards to the local postmaster
account.  The postmaster account has a .procmailrc file, which then
invokes procmail.  The procmail recipes simply look at the recipient and
send the proper email to the proper place.  No fancy recipes are used at
all; just straight forwarding based on address.  EG:  [EMAIL PROTECTED]
gets forwarded to [EMAIL PROTECTED]

I feel that I am using a cannon to squash a mouse - and I keep thinking
that there must be some simpler way to do what I am doing.

I've been reading through the archives, and fetchmail has received its
share of getting trashed, but there's also recommendations to use it.

>From reading the docs, it seems that I may be able to get rid of
procmail in my setup?  Can qmail forward to different users based on
address?  

Is fetchmail the way to go to collect POP3 mail or should I be looking
elsewhere?

I am looking for general recommendations and pointers on how to set this
up.  I can read docs; I just need some help on which docs to read :-)

Yan
-- 

           __      __
          | /      /
           /------/
       -- / \    / \ --
     /   /\  \  /  /\   \
    |   /  |  \/--|--    |
     \    /        \    /
       ~~            ~~

"The older I get, the faster I was."




Bruno Wolff III <[EMAIL PROTECTED]> wrote:

>I think this is related to a question I asked a while back. If the recipient
>address has a null local part, the message is silently rejected.

It's not rejected, it's delivered to the specified (null) recipient.

-Dave




"Jacob (Mettavihari)" <[EMAIL PROTECTED]> wrote:
>
>Could you kindly suggest a way of making
>serialmail work with your script
>
>the part of your script that starts up qmail-smtpd
>--------------------------------------------------
>    echo -n " qmail-smtpd"
>    supervise /var/supervise/qmail/smtpd tcpserver -v -x/etc/tcp.smtp.cdb
>\
>        -u$QMAILDUID -g$NOFILESGID 0 smtp \
>        /var/qmail/bin/qmail-smtpd-wrapper 2>&1 | setuser qmaill accustamp
>| \
>        setuser qmaill cyclog /var/log/qmail/smtpd &
>
>    echo "."
>
>the part from the faq for your easy access
>------------------------------------------
>3. Replace
>
>      /var/qmail/bin/qmail-smtpd
>
>   with
>
>      sh -c '
>        /var/qmail/bin/qmail-smtpd
>        cd /var/qmail/autoturn
>        exec setlock -nx $TCPREMOTEIP/seriallock \
>        maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP
>AutoTURN
>      '
>
>   in the tcpserver invocation in your boot scripts. Reports from
>   maildirsmtp will be sent to the same place as reports from tcpserver.

Just change /var/qmail/bin/qmail-smtpd-wrapper from:

#!/bin/bash
ulimit -d 1024
exec /var/qmail/bin/qmail-smtpd ${1+"$@"}

to:

#!/bin/bash
ulimit -d 1024
/var/qmail/bin/qmail-smtpd ${1+"$@"}
cd /var/qmail/autoturn
exec setlock -nx $TCPREMOTEIP/seriallock \
    maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN

-Dave




Rachelle DuBey <[EMAIL PROTECTED]> wrote:

>I am trying to do nested aliases using qmail - we recently switched over 
>from sendmail to qmail running on a redhat 6.0 box.
>I want to have nested aliases where jjones is a member or engineering and 
>then engineering is a member of allhands.
>It worked fine in sendmail.
>Is the best bet fast-forward or what are the suggestions?

What happens when you do the obvious? E.g., put &jjones in
~alias/.qmail-engineering and &engineering in ~alias/.qmail-allhands?

-Dave




Jim Gilliver wrote:
 > I've written a small C program that will take a single string and match it
 > to the most likely user account in /etc/passwd.  Obviously, this is to ease

Matching, and bouncing the email with a corresponding report, is fine.
Forwarding it to potentially the wrong party is not.

-- 
-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!




> > I've written a small C program that will take a single string and match
it
> > to the most likely user account in /etc/passwd.  Obviously, this is to
ease
>
>Matching, and bouncing the email with a corresponding report, is fine.
>Forwarding it to potentially the wrong party is not.


We have thought about this, obviously, but there are checks in the program
itself to avoid that sort of thing happening.  It's not likely to be
foolproof by any stretch, but if the name doesn't match closely enough to
any of our users (and there are very few) then it just defaults back to the
original administration address.

Jim






I want to create a mailing list which only sends messages to users from
the listkeeper. So I don't want
anyone to be able to reply to list.   So: How to create announcement
list with qmail?





Tero Niemi <[EMAIL PROTECTED]> wrote:

>I want to create a mailing list which only sends messages to users from
>the listkeeper. So I don't want
>anyone to be able to reply to list.   So: How to create announcement
>list with qmail?

If you want users to be able to subscribe and unsubscribe themselves,
you should use an MLM like ezmlm.

For a quick 'n' dirty list, install mess822 and create a
~alias/.qmail-listname containing:

|if echo "`/usr/local/bin/822field From`" |grep -q "listowner@listdomain" ; then exit 
|0; else echo "you're not authorized to send to this address"; exit 100; fi
&user@host
&user2@host2
etc.

And you can populate >~alias/.qmail-listname-owner to redirect
bounces.

-Dave




Another sneaky solution is to make the return address on the mailing
list the unsubscribe address.

Its eliminated people trying to post for me *eg*

Matt

> -----Original Message-----
> From: Dave Sill [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, July 12, 1999 9:53 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: About mailing lists
> 
> Tero Niemi <[EMAIL PROTECTED]> wrote:
> 
> >I want to create a mailing list which only sends messages to users
> from
> >the listkeeper. So I don't want
> >anyone to be able to reply to list.   So: How to create announcement
> >list with qmail?
> 
> If you want users to be able to subscribe and unsubscribe themselves,
> you should use an MLM like ezmlm.
> 
> For a quick 'n' dirty list, install mess822 and create a
> ~alias/.qmail-listname containing:
> 
> |if echo "`/usr/local/bin/822field From`" |grep -q
> "listowner@listdomain" ; then exit 0; else echo "you're not authorized
> to send to this address"; exit 100; fi
> &user@host
> &user2@host2
> etc.
> 
> And you can populate >~alias/.qmail-listname-owner to redirect
> bounces.
> 
> -Dave




On Mon, Jul 12, 1999 at 04:30:20PM +0300, Tero Niemi wrote:

> I want to create a mailing list which only sends messages to users from
> the listkeeper. So I don't want
> anyone to be able to reply to list.   So: How to create announcement
> list with qmail?

In ~alias/.qmail-list, put:

|bouncesaying 'Not allowed' [ "$SENDER" != "listkeeper@domain" ]
&address1
&address2
&address3
....

Now you can send to list@domain to make your announcement.

Note however, that someone could still send mail to this list by forging
the listkeeper's address. For better security and easier management,
install ezmlm, also available from
ftp://koobera.math.uic.edu/pub/software/ezmlm-0.53.tar.gz

-- 
Anand




On Mon, Jul 12, 1999 at 01:09:24PM +0200, Varga Robert wrote:

new-inject from DJB's mess822 package is supposed to do something like
this. You may want to investigate it before writing your own.

> I would like to set up centrally managed user masquaradeing for my virtual
> domains.
> 
> For this I thought that I read MAILUSER, MAILNAME and MAILHOST from a
> central file, in a wrapper of qmail-inject.
> 
> The question is whether I can do this? Or perhaps is there an already
> established mechanism for that?

-- 
Anand




Hi qmailers,

I would like to know if qmail allows mail acknowledgement because, when I
choose "acknowledge" option in my mailer I have no return.

Morever, Netscape messenger says that Qmail does not support
acknowledgement.

I want to know if there is a patch.

Thanks.

Regards.

Tarkan.






"Tarkan Hocaoglu" <[EMAIL PROTECTED]> wrote:

>I would like to know if qmail allows mail acknowledgement because, when I
>choose "acknowledge" option in my mailer I have no return.

See "man qreceipt".

>Morever, Netscape messenger says that Qmail does not support
>acknowledgement.

I don't know if qreceipt will work with Messenger, but it's easy to
test.

-Dave




Tarkan Hocaoglu writes:

> Hi qmailers,
> 
> I would like to know if qmail allows mail acknowledgement because, when I
> choose "acknowledge" option in my mailer I have no return.
> 
> Morever, Netscape messenger says that Qmail does not support
> acknowledgement.
> 
> I want to know if there is a patch.

No, there is no patch.  This is called a Delivery Status Notification, and
this is not really a quick patch.  It is a rather elaborate and extensive
procedure.

-- 
Sam







On Mon, 12 Jul 1999, Dave Sill wrote:

> Just change /var/qmail/bin/qmail-smtpd-wrapper from:
> 
> #!/bin/bash
> ulimit -d 1024
> exec /var/qmail/bin/qmail-smtpd ${1+"$@"}
> 
> to:
> 
> #!/bin/bash
> ulimit -d 1024
> /var/qmail/bin/qmail-smtpd ${1+"$@"}
> cd /var/qmail/autoturn
> exec setlock -nx $TCPREMOTEIP/seriallock \
>     maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN

Thank you very much.


>From faq 5.3.
------------
If you have tcpserver installed, skip the inetd step, and set up (on two
lines)

   tcpserver 0 pop3 /var/qmail/bin/qmail-popup YOURHOST \
   /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &

replacing YOURHOST with your host's fully qualified domain name. See
question 5.1 for more details on tcpserver.

Where do I install this line? 
I presume it will have to be a separate
script to start the popd server in /etc/rc.d/init.d/qmail-pop3d

Thanks 
Jacob





"Jacob (Mettavihari)" <[EMAIL PROTECTED]> wrote:

>Thank you very much.

You're welcome.

>From faq 5.3.
>------------
>If you have tcpserver installed, skip the inetd step, and set up (on two
>lines)
>
>   tcpserver 0 pop3 /var/qmail/bin/qmail-popup YOURHOST \
>   /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
>
>replacing YOURHOST with your host's fully qualified domain name. See
>question 5.1 for more details on tcpserver.
>
>Where do I install this line? 
>I presume it will have to be a separate
>script to start the popd server in /etc/rc.d/init.d/qmail-pop3d

You *could* put it in the qmail startup script, but it's probably
cleaner to give it its own script. Don't forget to link it to the
appropriate rcN.d directories. Just use the qmail links as a guide.

-Dave




Russ Allbery writes:
 > autoconf most certainly is not monolithic.  It *generates* a monolithic
 > shell script, precisely because that shell script is performing
 > workarounds for things that Dan doesn't deal with and is producing output
 > in a form that Dan doesn't use.

Right.  Dan doesn't do it that way because it's wrong.  Dan's insight
is simply that make consults a database called a filesystem.  So
instead of having a shell script create its own database, and from
that a Makefile, he has a fixed Makefile create database entries.  As
a consequence, ``making'' a package consists of running make, instead
of:

libtoolize --copy --force
aclocal include
autoheader
automake --add-missing
autoconf
./configure
make


Which process is simpler?


-- 
-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 writes:

> Russ Allbery writes:
>  > autoconf most certainly is not monolithic.  It *generates* a monolithic
>  > shell script, precisely because that shell script is performing
>  > workarounds for things that Dan doesn't deal with and is producing output
>  > in a form that Dan doesn't use.
> 
> Right.  Dan doesn't do it that way because it's wrong.  Dan's insight
> is simply that make consults a database called a filesystem.  So
> instead of having a shell script create its own database, and from
> that a Makefile, he has a fixed Makefile create database entries.  As
> a consequence, ``making'' a package consists of running make, instead
> of:
> 
> libtoolize --copy --force
> aclocal include
> autoheader
> automake --add-missing
> autoconf
> ./configure
> make
> 
> 
> Which process is simpler?

One command versus six commands is not much of an issue, when you have to
do it only once per project.

Besides, I'm not exactly sure whether this supposed framework comes even
close to offering the same flexibility as autoconf/automake.

We already know that you can't do VPATH builds or build-root installs here.
 Yes, you can manually patch some installation files to achieve the same
thing, but this is exactly what you're complaining about here.

Furthermore, I see no way of, say, easily embed one package within another
one. The other day I wrote some code to run HMAC key digests using
arbitrary hash functions.  I already had a completely separate, standalone
package that builds an MD5 hash library, and I had a second package doing
the same with the SHA1 hash function.

Without altering a single byte in the configuration script and the
makefile, both packages were simply added as a subpackage of the HMAC
library, and make dist in the top level now builds a single distribution
tarball, including the contents of both subdirectories containing the hash
functions.

I have a library that does RFC821 header parsing, and another library to do
RFC2045 MIME parsing on the message.

Both libraries are used in three separate projects, two of which are
publicly available.  Unless you have both sets of source code, you would
not be aware that the subdirectories are really separate subprojects,
maintained completely separately.  You'd assume that they were integrated
parts of the main project.


-- 
Sam





Russell Nelson <[EMAIL PROTECTED]> writes:

> Right.  Dan doesn't do it that way because it's wrong.  Dan's insight is
> simply that make consults a database called a filesystem.  So instead of
> having a shell script create its own database, and from that a Makefile,
> he has a fixed Makefile create database entries.

Try building config.cache files for known platforms and then using them to
choose the right parameters when cross-compiling using Dan's scheme.
Actually, try cross-compiling at all with Dan's scheme.  Or try doing
anything that has to be based on the architecture rather than on tests
(the autoconf suite supports both).

Furthermore, with a fixed Makefile, how do you intend to optionally
include or exclude portions of a build tree from the build?  Like
including your own libz but using the system libz if one was found during
configure.

And while I can see the merits in using conf-* files vs. using
command-line switches for configure, I can assure you that when you're
trying to automate the builds of hundreds of software packages on a dozen
platforms, scripting switches to configure is a hell of a lot easier than
keeping and automatically applying patches to a bunch of conf-* files.

All of these are, of course, fixable in Dan's approach with work.  And
what you'd end up with after you fixed them all is something that looked
quite a bit like autoconf.

-- 
Russ Allbery ([EMAIL PROTECTED])         <URL:http://www.eyrie.org/~eagle/>




I find that the mails that I get, including ones sent locally, only have

the date, from and subject field.

Is there a way I could control which fields should be shown?

What if I also like to see the "to" field?


Chitta




[EMAIL PROTECTED] wrote:

>I find that the mails that I get, including ones sent locally, only have
>
>the date, from and subject field.
>
>Is there a way I could control which fields should be shown?
>
>What if I also like to see the "to" field?

This isn't really a qmail question. If your MUA isn't showing you the
header fields you want to see, there's nothing qmail can do to make
them visible. If the messages don't have these fields, the sender will 
have to configure his MUA to add them. You don't want qmail to try to
guess what should be in missing fields.

-Dave





How do i clean out the queue. I want all the messages erased from it.  Do
I just erase /var/qmail/queue/mess direcotry ?  Also what program do I
used to read the mail from the prompt ?  I normally use Pine with
Sendmail but it does not work with qmail.


thanks
td





"Tony D'Andrade" <[EMAIL PROTECTED]> wrote:

>How do i clean out the queue. I want all the messages erased from it.  Do
>I just erase /var/qmail/queue/mess direcotry ?

No. First, stop qmail. Next, delete all the files from the queue
directories: bounce, mess, info, local, intd, todo, and remote. Now
restart qmail. If you installed qmail using "Life with qmail", that
could be accomplished by doing:

    /usr/local/sbin/qmail stop
    find /var/qmail/queue/mess -type f -exec rm {} \;
    find /var/qmail/queue/info -type f -exec rm {} \;
    find /var/qmail/queue/local -type f -exec rm {} \;
    find /var/qmail/queue/intd -type f -exec rm {} \;
    find /var/qmail/queue/todo -type f -exec rm {} \;
    find /var/qmail/queue/remote -type f -exec rm {} \;
    /usr/local/sbin/qmail start

>Also what program do I
>used to read the mail from the prompt ?  I normally use Pine with
>Sendmail but it does not work with qmail.

qmail comes with "pinq" and "qail" wrappers for "pine" and
"mail". Even better is "mutt" (www.mutt.org).

-Dave





Hi I tried that. Now I get the following error when I try to mail someone.

        qmail-inject: fatal: qq trouble creating files in queue (#4.3.0)

I erased:
        queue/mess/*
        queue/info/*
        queue/local/*
        queue/intd/*
        queue/todo/*
        queue/remote/*

And restarted qmail.    

The last time I got this error. I re-installed qmail. Now Im going to
re-install it again. However I think the mailq is filling up because I
have cronjobs running and root is not getting the mail.  I su to root and
ran:
         maildirmake Maildir

in root directory.  But I still could not receive mail messages from root.
No mail shows up in ~root/Maildir/new.  All the messages are in queue.  On
the other hand when I create a regular user and his "Maildir", then mail
him a message his message arrives no problem.

how do i get root his mail ? any ideas ? 

> "Tony D'Andrade" <[EMAIL PROTECTED]> wrote:
> 
> >How do i clean out the queue. I want all the messages erased from it.  Do
> >I just erase /var/qmail/queue/mess direcotry ?
> 
> No. First, stop qmail. Next, delete all the files from the queue
> directories: bounce, mess, info, local, intd, todo, and remote. Now
> restart qmail. If you installed qmail using "Life with qmail", that
> could be accomplished by doing:
> 
>     /usr/local/sbin/qmail stop
>     find /var/qmail/queue/mess -type f -exec rm {} \;
>     find /var/qmail/queue/info -type f -exec rm {} \;
>     find /var/qmail/queue/local -type f -exec rm {} \;
>     find /var/qmail/queue/intd -type f -exec rm {} \;
>     find /var/qmail/queue/todo -type f -exec rm {} \;
>     find /var/qmail/queue/remote -type f -exec rm {} \;
>     /usr/local/sbin/qmail start
> 
> >Also what program do I
> >used to read the mail from the prompt ?  I normally use Pine with
> >Sendmail but it does not work with qmail.
> 
> qmail comes with "pinq" and "qail" wrappers for "pine" and
> "mail". Even better is "mutt" (www.mutt.org).
> 
> -Dave
> 

Tony D'Andrade Systems Administrator
VisiNet Systems
67 Yonge St
Toronto, Ontario
Phone:(416) 363-4788  
http://www.visinet.net





Quoting Tony D'Andrade ([EMAIL PROTECTED]):
> I erased:
>       queue/mess/*
>       queue/info/*
>       queue/local/*
>       queue/intd/*
>       queue/todo/*
>       queue/remote/*

Dave wrote [attribution added]:
> >     /usr/local/sbin/qmail stop
> >     find /var/qmail/queue/mess -type f -exec rm {} \;
> >     find /var/qmail/queue/info -type f -exec rm {} \;
> >     find /var/qmail/queue/local -type f -exec rm {} \;
> >     find /var/qmail/queue/intd -type f -exec rm {} \;
> >     find /var/qmail/queue/todo -type f -exec rm {} \;
> >     find /var/qmail/queue/remote -type f -exec rm {} \;
> >     /usr/local/sbin/qmail start

Oops, you know Dave didn't say to delete _everything_ within those
directories!  The find commands above finds all regular files and
deletes those.  If what you say above is true, then you've deleted a
whole bunch of directories contained within.  Run 'make setup' from
the qmail source directory again.

Aaron




On Mon, Jul 12, 1999 at 04:43:30PM -0400, Tony D'Andrade wrote:
> The last time I got this error. I re-installed qmail. Now Im going to
> re-install it again. However I think the mailq is filling up because I have
> cronjobs running and root is not getting the mail.  I su to root and ran:
>        maildirmake Maildir
> 
> in root directory.  But I still could not receive mail messages from root.
> No mail shows up in ~root/Maildir/new.  All the messages are in queue.  On
> the other hand when I create a regular user and his "Maildir", then mail him
> a message his message arrives no problem.
> 
> how do i get root his mail ? any ideas ? 

Reread the INSTALL document, especially the bit that says:

5. Read INSTALL.alias. Minimal survival command:
       # (cd ~alias; touch .qmail-postmaster .qmail-mailer-daemon .qmail-root)

Chris




I'll try this again,

I'm looking to provide a daily report which shows who sent what and to
whom.

perhaps something like this:

10:01    FROM: [EMAIL PROTECTED]   ==>>   TO: [EMAIL PROTECTED]
10:01    FROM: [EMAIL PROTECTED]       ==>>   TO: [EMAIL PROTECTED]
14:02    FROM: [EMAIL PROTECTED]      ==>>   TO: [EMAIL PROTECTED]

I downloaded someone's perl script which advertised this functionality,
but it just gave me raw maillog data as output. And qmailanalog won't
give an output like I'm needing (at least I can't figureout how to get
something like the above out of it.)

Anyone?



many thx - eric




Eric Dahnke <[EMAIL PROTECTED]> wrote:

>I'm looking to provide a daily report which shows who sent what and to
>whom.
>
>perhaps something like this:
>
>10:01    FROM: [EMAIL PROTECTED]   ==>>   TO: [EMAIL PROTECTED]
>10:01    FROM: [EMAIL PROTECTED]       ==>>   TO: [EMAIL PROTECTED]
>14:02    FROM: [EMAIL PROTECTED]      ==>>   TO: [EMAIL PROTECTED]
>
>I downloaded someone's perl script which advertised this functionality,
>but it just gave me raw maillog data as output. And qmailanalog won't
>give an output like I'm needing (at least I can't figureout how to get
>something like the above out of it.)

Did you look at the output of the "matchup" script? It's got all the
information you need, and then some. A little perl script could
generate the output you want pretty easily.

-Dave




Dinesh Punjabi wrote:

> Is there any program/package that will
> periodically remove/clear email older than a
> certain period of time ?
>
> I will be running this process on a daily
> basis to automatically delete messages out of
> a Mailbox file that are 1-2 weeks older than
> today's date.
>
> Thanks!

I have made that script in perl, but It only works with mbox. I will
send it to Dinesh as an atachment.

I don't know if it's ethic to send an atachment to the list, please
somebody tell me if it is. If so, I will gladly  send it to the list,
for those who care.






I tried to install a wrapper around qmail-inject...

It had a call to id, with the output redirected to a file
It also had an echo writing to stdout in it..

It also had exported variables overwriting 
QMAILUSER, QMAILNAME, QMAILHOST, QMAILINJECT, QMAILDEFAULTHOST

However when I tried to use pine sending a letter, it did work, however
the received mail did not have any of the fields rewritten.
The file with the redirected output of id did not show up anywhere.
The echo did not show up in the log nor anywhere else.

I also tried exporting the variables in a shell before
starting pine (from the same shell...). That also did not work.

I injected a letter through the wrapper, it did work that way.

What does pine use for sending a letter, and how can I rewrite fields
written by pine? 


Robert Varga





On Mon, 12 Jul 1999, Robert Varga wrote:

> 
> I tried to install a wrapper around qmail-inject...
> 
> It had a call to id, with the output redirected to a file
> It also had an echo writing to stdout in it..

I use qmail's sendmail replacement:
sendmail-path=/var/qmail/bin/sendmail -oem -t -oi

no QMAIL* variables set.

pine 4.10 allows me to set any/all of the headers I'd wish to (including
allowing me to edit the From: and automatically switching between roles.

RjL
==================================================================
The problems of the world    ||  Fax:   +44 870 0521198        
can't be solved by fixing    ||  Email: [EMAIL PROTECTED]
the working -- C. Daniluk    ||  Phone: +44 385 275 394







On Mon, 12 Jul 1999, Richard Letts wrote:

> > 
> > I tried to install a wrapper around qmail-inject...
> > 
> > It had a call to id, with the output redirected to a file
> > It also had an echo writing to stdout in it..
> 
> I use qmail's sendmail replacement:
> sendmail-path=/var/qmail/bin/sendmail -oem -t -oi
> 
> no QMAIL* variables set.
> 
> pine 4.10 allows me to set any/all of the headers I'd wish to (including
> allowing me to edit the From: and automatically switching between roles.

That is exactly what I want to override...

I want to do address rewriting for my users the same way it can be done
with the generics table in sendmail. That is, I want to ensure that my
users do not try to send mail in someone else's name.

Robert Varga






On Mon, 12 Jul 1999, Robert Varga wrote:

> That is exactly what I want to override...
> 
> I want to do address rewriting for my users the same way it can be done
> with the generics table in sendmail. That is, I want to ensure that my
> users do not try to send mail in someone else's name.

you're on a hiding to nothing. as long as they have any form of access to
SMTP they can forge mail from whoever they like. you need to look at
enforcing the use of cryptographic sugnatures.





Robert Varga writes:

> What does pine use for sending a letter, and how can I rewrite fields
> written by pine? 

Pine uses whatever you configure Pine to use.  Pine can use qmail-inject,
or Pine can talk SMTP, it's up to you to configure Pine the way you want
to.


-- 
Sam







On Mon, 12 Jul 1999, Richard Letts wrote:

> On Mon, 12 Jul 1999, Robert Varga wrote:
> 
> > That is exactly what I want to override...
> > 
> > I want to do address rewriting for my users the same way it can be done
> > with the generics table in sendmail. That is, I want to ensure that my
> > users do not try to send mail in someone else's name.
> 
> you're on a hiding to nothing. as long as they have any form of access to
> SMTP they can forge mail from whoever they like. you need to look at
> enforcing the use of cryptographic sugnatures.
> 

It is not as problematic as that...

They are not really computer-specialists... they might know a thing about
setting a few options in pine, but I don't think they will be able to use
my SMTP port if I don't want to.

What I want to ensure, is that they can't use a MUA on my machine to forge
email if I don't want to.

If they use an SMTP server anywhere else, then it is not my fault.
They won't be able to use my server for relaying. And I won't allow them
to use pine or other MUAs to make SMTP connections. 

This way if they use an MUA on my machine, they will be under control.

This is all that is achieved in sendmail, too...

Robert Varga






yep,

as I said later in the same email.

"Of course it was rejected because of a misspelling, not because it is not
included in the command set."

The point I was trying to make was that misspellings always will occur, but
the statement the auto-message that says approximately, "I understand the
following...list of commands" is incomplete. It should have been completed
to include the other commands. I took the absence of
"[EMAIL PROTECTED]" as confirming it's
absence, not my misspelling.

I was making a comment on a way of improving the content of the response
mailing.

Alex Miller

> -----Original Message-----
> From: Dave Sill [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 07, 1999 8:32 AM
> To: [EMAIL PROTECTED]
> Subject: RE: info
>
>
> "Alex Miller" <[EMAIL PROTECTED]> wrote:
> >
> >Oh, I tried it last night before I sent him the message, as at test.
> >I subscribed [EMAIL PROTECTED]
> >then I sent the command
> >[EMAIL PROTECTED]
>               ^^
> >
> >It failed, saying:
> >
> ><snip>
> >
> >The message I received wasn't sent to any of my command addresses.
>
> You misspelled "unsubscribe" in the address.
>
> -Dave
>






How can I do address rewriting with qmail's sendmail replacement?
Since pine uses /usr/sbin/sendmail, it does not heed the QMAILUSER and co.
variables...

How can I make pine to use qmail-inject, or /usr/sbin/sendmail (qmail's
sendmail) to do address rewriting?

Robert Varga





Robert Varga writes:

> How can I make pine to use qmail-inject, or /usr/sbin/sendmail (qmail's
> sendmail) to do address rewriting?

Edit your global pine.conf file.


-- 
Sam





Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail' seems
to work fine. No symbolic links necessary. Maybe your symbolic links are
mandatory for other processes?

I am surprised I can't locate documentation referencing use of form mail
with qmail.

Cheers,
DAN


-----Original Message-----
From: Markus Stumpf [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 11, 1999 2:43 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Using qmail with CGI feedback form - needing reference


On Sun, Jul 11, 1999 at 11:39:03PM +0200, Markus Stumpf wrote:
> I have a symb.link (which is kinda mandatory for systems running qmail)
> from /usr/sbin/sendmail -> /var/qmail/sendmail

*ARGL*
That should read
    /var/qmail/bin/sendmail
              ****
of course :/

        \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  |





As per the qmail install doc, you must link /usr/lib/sendmail to
/var/qmail/bin/sendmail.
(ln -s /var/qmail/bin/sendmail /usr/lib/sendmail)
I've used multiple form mailers, and they all work fine with qmail's
sendmail replacement.



Reid Sutherland
Network Administrator
ISYS Technology Inc.
http://www.isys.ca
Fingerprint: 1683 001F A573 B6DF A074  0C96 DBE0 A070 28BE EEA5

-----Original Message-----
From: Dan Poynor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, July 12, 1999 4:29 PM
Subject: RE: Using qmail with CGI feedback form - needing reference


>Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail' seems
>to work fine. No symbolic links necessary. Maybe your symbolic links are
>mandatory for other processes?
>
>I am surprised I can't locate documentation referencing use of form mail
>with qmail.
>
>Cheers,
>DAN
>
>
>-----Original Message-----
>From: Markus Stumpf [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, July 11, 1999 2:43 PM
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: Using qmail with CGI feedback form - needing reference
>
>
>On Sun, Jul 11, 1999 at 11:39:03PM +0200, Markus Stumpf wrote:
>> I have a symb.link (which is kinda mandatory for systems running qmail)
>> from /usr/sbin/sendmail -> /var/qmail/sendmail
>
>*ARGL*
>That should read
>    /var/qmail/bin/sendmail
>       ****
>of course :/
>
> \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  |
>
>





On Mon, Jul 12, 1999 at 01:16:49PM -0700, Dan Poynor wrote:
> Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail' seems
> to work fine. No symbolic links necessary. Maybe your symbolic links are
> mandatory for other processes?

Yes, for every Unix process using /usr/sbin/sendmail to inject eMails.

> I am surprised I can't locate documentation referencing use of form mail
> with qmail.

With the symbolic link there is nothing special about configuring from
mail for 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  |




On Mon, Jul 12, 1999 at 01:16:49PM -0700, Dan Poynor wrote:
> Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail' seems
> to work fine. No symbolic links necessary. Maybe your symbolic links are
> mandatory for other processes?
> 
> I am surprised I can't locate documentation referencing use of form mail
> with qmail.
 
It's pretty simple, actually.  Send your text to a qmail-inject process.

man qmail-inject 

-- 
John White     johnjohn
             at
               triceratops.com
PGP Public Key: http://www.triceratops.com/john/public-key.pgp




I nuked anything that smelled of sendmail. Trying to avoid it's ghost also.
qmails Sendmail requirements seem redundant to me. That is I don't want to
create sendmail symbolic links when it's not necessary.

Perhaps a future FAQ item could mention form mail sending injects to
/var/qmail/bin/sendmail.

Now I see someone is saying it should be /var/qmail/bin/qmail-inject. Are
these the same thing?

Thanks,
DAN


-----Original Message-----
From: Reid Sutherland [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 12, 1999 1:28 AM
To: [EMAIL PROTECTED]
Subject: Re: Using qmail with CGI feedback form - needing reference


As per the qmail install doc, you must link /usr/lib/sendmail to
/var/qmail/bin/sendmail.
(ln -s /var/qmail/bin/sendmail /usr/lib/sendmail)
I've used multiple form mailers, and they all work fine with qmail's
sendmail replacement.



Reid Sutherland
Network Administrator
ISYS Technology Inc.
http://www.isys.ca
Fingerprint: 1683 001F A573 B6DF A074  0C96 DBE0 A070 28BE EEA5

-----Original Message-----
From: Dan Poynor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, July 12, 1999 4:29 PM
Subject: RE: Using qmail with CGI feedback form - needing reference


>Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail' seems
>to work fine. No symbolic links necessary. Maybe your symbolic links are
>mandatory for other processes?
>
>I am surprised I can't locate documentation referencing use of form mail
>with qmail.
>
>Cheers,
>DAN
>
>
>-----Original Message-----
>From: Markus Stumpf [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, July 11, 1999 2:43 PM
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: Using qmail with CGI feedback form - needing reference
>
>
>On Sun, Jul 11, 1999 at 11:39:03PM +0200, Markus Stumpf wrote:
>> I have a symb.link (which is kinda mandatory for systems running qmail)
>> from /usr/sbin/sendmail -> /var/qmail/sendmail
>
>*ARGL*
>That should read
>    /var/qmail/bin/sendmail
>       ****
>of course :/
>
> \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  |
>
>






Linking /var/qmail/bin/sendmail ensures backwards capatibility with older
programs / scripts that use the old sendmail. Using /var/qmail/bin/sendmail
in your script is the same as the link /usr/lib/sendmail.


Reid Sutherland
Network Administrator
ISYS Technology Inc.
http://www.isys.ca
Fingerprint: 1683 001F A573 B6DF A074  0C96 DBE0 A070 28BE EEA5

-----Original Message-----
From: Dan Poynor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, July 12, 1999 11:40 PM
Subject: RE: Using qmail with CGI feedback form - needing reference


>I nuked anything that smelled of sendmail. Trying to avoid it's ghost also.
>qmails Sendmail requirements seem redundant to me. That is I don't want to
>create sendmail symbolic links when it's not necessary.
>
>Perhaps a future FAQ item could mention form mail sending injects to
>/var/qmail/bin/sendmail.
>
>Now I see someone is saying it should be /var/qmail/bin/qmail-inject. Are
>these the same thing?
>
>Thanks,
>DAN
>
>
>-----Original Message-----
>From: Reid Sutherland [mailto:[EMAIL PROTECTED]]
>Sent: Monday, July 12, 1999 1:28 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Using qmail with CGI feedback form - needing reference
>
>
>As per the qmail install doc, you must link /usr/lib/sendmail to
>/var/qmail/bin/sendmail.
>(ln -s /var/qmail/bin/sendmail /usr/lib/sendmail)
>I've used multiple form mailers, and they all work fine with qmail's
>sendmail replacement.
>
>
>
>Reid Sutherland
>Network Administrator
>ISYS Technology Inc.
>http://www.isys.ca
>Fingerprint: 1683 001F A573 B6DF A074  0C96 DBE0 A070 28BE EEA5
>
>-----Original Message-----
>From: Dan Poynor <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Monday, July 12, 1999 4:29 PM
>Subject: RE: Using qmail with CGI feedback form - needing reference
>
>
>>Setting my CGI form variable to $mailprog = '/var/qmail/bin/sendmail'
seems
>>to work fine. No symbolic links necessary. Maybe your symbolic links are
>>mandatory for other processes?
>>
>>I am surprised I can't locate documentation referencing use of form mail
>>with qmail.
>>
>>Cheers,
>>DAN
>>
>>
>>-----Original Message-----
>>From: Markus Stumpf [mailto:[EMAIL PROTECTED]]
>>Sent: Sunday, July 11, 1999 2:43 PM
>>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>Subject: Re: Using qmail with CGI feedback form - needing reference
>>
>>
>>On Sun, Jul 11, 1999 at 11:39:03PM +0200, Markus Stumpf wrote:
>>> I have a symb.link (which is kinda mandatory for systems running qmail)
>>> from /usr/sbin/sendmail -> /var/qmail/sendmail
>>
>>*ARGL*
>>That should read
>>    /var/qmail/bin/sendmail
>>       ****
>>of course :/
>>
>> \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  |
>>
>>
>
>
>





Dan Poynor wrote:
> Now I see someone is saying it should be /var/qmail/bin/qmail-inject. Are
> these the same thing?

/var/qmail/bin/sendmail is actually a wrapper around qmail-inject.
So you can slightly modify the script to use it instead of 
/var/qmail/bin/sendmail if you want to be 100% sendmail-free ;)

--sgk




Dan Poynor wrote/schrieb/scribsit:
> I nuked anything that smelled of sendmail. Trying to avoid it's ghost also.
> qmails Sendmail requirements seem redundant to me. That is I don't want to
> create sendmail symbolic links when it's not necessary.

/usr/{lib,sbin}/sendmail is _the_ API for mail injection on UNIX systems.
 
> Perhaps a future FAQ item could mention form mail sending injects to
> /var/qmail/bin/sendmail.

Now, why should they? With symlinks in /usr/lib and /usr/sbin, nothing
must be changed, which is a Good Thing. qmail's native API for mail
injection is the qmail-queue interface.
 
> Now I see someone is saying it should be /var/qmail/bin/qmail-inject. Are
> these the same thing?

No, /var/qmail/bin/sendmail implements the sendmail API. It knows how
to execute qmail-inject or qmail-smtpd [1] with appropriate parameters
depending on its invocation.

Stefan
[1] exec'ing qmail-smtpd to emulate sendmail's 'SMTP-on-stdin' mode
is pretty damn elegant, BTW




Here is the problem I am having, and I would appreciate any help that
ya'll might could give me:

The domains that needed aliasing equivalent to sendmail's virtusertable
I setup in /etc/aliases using the fastforward package.  Fastforward is
setup under ~alias/qmail-default.. Obviously as you know, if the domain
is in locals, it will send to the local user before it looks at
/etc/aliases for a possible alias (sendmail didn't do this).

Now, I can setup all these [EMAIL PROTECTED]:        chris .. in
/etc/aliases but, if something.com is in locals, it will send directly
to the local user something unless it doesn't exist.  If it doesn't
exist it then sends to chris.  Well here is the problem.  We have a
bunch of virtual domains.  I need to initiate quite a few aliases like
so:

[EMAIL PROTECTED]:        cgalanos
[EMAIL PROTECTED]:    cgalanos

etc, etc.  The problem is that if the local user exists it won't send to
cgalanos unless I put a .qmail file in that dir.  Therefore /etc/aliases
is not acting like sendmail's.  Now, here's the dilemma.  I can put the
.qmail files in the home dir's if I have to BUT if I have those 2
addresses above in /etc/aliases I need the rest of whatever
@something.com to go to the local users.

In other words, if I have something.com:alias in virtualdomains, and
then use the fastforward program, everything else besides chris and
something doesn't go anywhere.

I need each domain to have like its own info@ user... well if I put
[EMAIL PROTECTED]:        someusername,
it will dump [EMAIL PROTECTED] to the local user info instead of the
other username.  You can see how I'm getting mixed around here.

Does anyone know how to cure this?  If so please let me know.  For now I
think I will have to add something.com also to locals, then make sure
the user doesn't exist locally so that it will then call the aliases
file and send to where it needs to be.  Any help with this woudl be
appreciated.

Last time I did this, I did it like this.

In virtualdomains, each domain would have a user account that managed
it.  Now this would be great, and I coudl put .qmail-username file's in
that user's home dir.  But then, is there a way to make .qmail-default
to send to local users.

In other words.. say I had comp.org.

in virtualdomains:

comp.org:filtercomp

in ~filtercomp..

.qmail-chris  (which has cgalanos in it)

well [EMAIL PROTECTED] will now go to cgalanos, but say someone sends to
[EMAIL PROTECTED], I want that .qmail-default to check for a something
local user, and send to it if it exists.. can I do this?

Thanks for listening,

Chris





I believe that I was probably a little too loquacious in the earlier message.  Let me get down to the core of the problem here.
 
I'm going to have a file full of virtualdomains in the format:
 
domain1.com:filtdomain1
domain2.com:filtdomain2
 
so on and so forth.  The user filtdomain1 and 2 will both have .qmail-usernames for the username's of people that should receive mail under this domain.  In other words, if I have .qmail-chris, [EMAIL PROTECTED] will get messages.  This is very simple obviously.  Here is my problem:
 
I want to be able to setup a .qmail-default for each domain that will search my local machine for that particular username, and if it exists send the message to them.  Why I want to do this?  The class of all of our users is not recorded, so I have some that I know of that need a [EMAIL PROTECTED] and some that have just been added to the system but also receive at domain1.com under our old sendmail system.  Therefore, if someone email's [EMAIL PROTECTED], and there is no .qmail-john under the filtdomain1 user directory, I would like to create a a qmail-default file that will pick these up and dish them to the local users.  Therefore, since john doesn't exist, it will see if he is on the local system, and if so send to that user.  If not it will obviously bounce a message back.  I hope this make sense.  Any help would be appreciated.  The problem arose because on my sendmail server everything was treated as a local.  So any user on my system @anydomainwehost.com could be accessed.
 
Chris




I have Linux 2.0.36. I installed qmail. It is working fine.
I am running qmail-smtpd under tcpserver and qmail-pop3d under inetd. I can see my e-mails from any Windows station with Outlook Express.
I would like to have qmail-pop3d running under tcpserver too.
I put the following line in my rc.local:
 
tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup ns1.integral.com.co \
/bin/checkpasswd /var/qmail/bin/qmail-pop3d maildir 2>&1 | \
/var/qmail/bin/splogger pop3d &

However when I intent to see my e-mail from any Windows station with Outlook Express, I get the following message: �ERR authorization failed�.

Thanks.

 





On Mon 1999-07-12 (19:05), Alvaro Escobar wrote:
> 
>    I have Linux 2.0.36. I installed qmail. It is working fine.
>    
>    I am running qmail-smtpd under tcpserver and qmail-pop3d under inetd.
>    I can see my e-mails from any Windows station with Outlook Express.
>    
>    I would like to have qmail-pop3d running under tcpserver too.
>    
>    I put the following line in my rc.local:
>    
>    
>    
>    tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup ns1.integral.com.co
>    \
>    
>    /bin/checkpasswd /var/qmail/bin/qmail-pop3d maildir 2>&1 | \
>    
>    /var/qmail/bin/splogger pop3d &
    
Your tcpserver line appears to be fine. Perhaps maildir should be Maildir
though.

>    However when I intent to see my e-mail from any Windows station with
>    Outlook Express, I get the following message: �ERR authorization
>    failed�.

I suspect checkpassword is your problem. Mark Delany's checkpassword test at
the top of the "Alternative Checkpassword Implementations" on www.qmail.org
should help. (Just a note though that on my system id is in /usr/bin).

  - Keith
-- 
Keith Burdis - MSc (Com Sci) - Rhodes University, South Africa  
Email   : [EMAIL PROTECTED]
WWW     : http://www.rucus.ru.ac.za/~keith/
IRC     : Panthras                                          JAPH

"Any technology sufficiently advanced is indistinguishable from a perl script"

Standard disclaimer.
---




>In one of the latest versions of mutt was a bug causing the same error.
>Mutt searched for "sendmail" (i.e. not real sendmail but a wrapper to
>actually installed MTA) in wrong place. 
>Possible solutions were:
> o     tell mutt to search in a real place with the command in
>       /etc/Muttrc (or ~/.muttrc): set sendmail="/path/to/sendmail"


Thank you for this.

I changed some settings in /etc/Muttrc and it worked.
I have set /etc/Muttrc to ./Mailbox
and some ~/.muttrc to use ./Maildir/ and it works.

thanks agian
Jacob

International Buddhist Research & Information Center (IBRIC).
380/9  Sarana Road, Colombo 00700, Sri Lanka.
Telephone - +94 1 68 9388 email - [EMAIL PROTECTED]
http://www.transmillennium.net/IBRIC/
http://www.metta.lk/IBRIC/





On Mon, 12 Jul 1999, Troy Morrison wrote:

> I'm not claiming that this is better or worse; just pointing out that
> there's more than one way to do it.

Right.  Sorry, I didn't mean to imply that the method I described was
better than any of the others mentioned.  To the contrary, I am interested
in hearing if there are any fundamental problems with this method.  Some
of our users here complained that mail was being slowed down tremendously
(after they were told about the scanner) but in just about every case,
the problem turned out be elsewhere.

Regards,
Christopher
-----
Christopher Seawood
That Linux Guy, 
Aureate Media Corporation





Reply via email to