qmail Digest 8 Sep 1999 10:00:01 -0000 Issue 753

Topics (messages 29938 through 29988):

limiting the file size of bounces ?
        29938 by: Jedi/Sector One <[EMAIL PROTECTED]>

queue problem
        29939 by: Enrico Mangano <[EMAIL PROTECTED]>
        29969 by: Dave Sill <[EMAIL PROTECTED]>

.qmail - deliveries and bounces
        29940 by: Robert Varga <[EMAIL PROTECTED]>
        29976 by: Russell Nelson <[EMAIL PROTECTED]>

Security Issue on qmail
        29941 by: Anand Buddhdev <[EMAIL PROTECTED]>
        29973 by: "Peter Samuel" <[EMAIL PROTECTED]>

restarting qmail
        29942 by: [EMAIL PROTECTED]

a bug again?
        29943 by: Marcin Jaskowiak <[EMAIL PROTECTED]>
        29944 by: Ira Abramov <[EMAIL PROTECTED]>
        29945 by: "Petr Novotny" <[EMAIL PROTECTED]>
        29946 by: Marcin Jaskowiak <[EMAIL PROTECTED]>
        29947 by: "Petr Novotny" <[EMAIL PROTECTED]>

Try this problem...
        29948 by: "Kurt Hindenburg" <[EMAIL PROTECTED]>

Any ideas?
        29949 by: Dave Sill <[EMAIL PROTECTED]>
        29971 by: Dave Sill <[EMAIL PROTECTED]>

qmail won't start
        29950 by: "Scott MacDonald" <[EMAIL PROTECTED]>
        29951 by: Dave Sill <[EMAIL PROTECTED]>
        29954 by: "Scott MacDonald" <[EMAIL PROTECTED]>
        29967 by: Dave Sill <[EMAIL PROTECTED]>

Problems getting started
        29952 by: Mate Wierdl <[EMAIL PROTECTED]>

fastforward: wildcards
        29953 by: Ira Abramov <[EMAIL PROTECTED]>

qmail and > 4,000 users ?
        29955 by: "Stephen C. Comoletti" <[EMAIL PROTECTED]>
        29965 by: "Robin Bowes" <[EMAIL PROTECTED]>

Virtual Domains
        29956 by: "Keith From" <[EMAIL PROTECTED]>
        29957 by: "Adam D . McKenna" <[EMAIL PROTECTED]>
        29958 by: Sam <[EMAIL PROTECTED]>
        29959 by: "Keith From" <[EMAIL PROTECTED]>

tcprules for qmail-pop3d
        29960 by: Damon Parker <[EMAIL PROTECTED]>
        29961 by: "Petr Novotny" <[EMAIL PROTECTED]>

single-UID setup problem
        29962 by: Giorgio Bozio <[EMAIL PROTECTED]>

daemontools 0.61 and qmailanalog?
        29963 by: Sebastian Andersson <[EMAIL PROTECTED]>

Maildir and Pine-4.10
        29964 by: Kai MacTane <[EMAIL PROTECTED]>
        29974 by: James Smallacombe <[EMAIL PROTECTED]>

Pine 4.10 and Qmail 1.03
        29966 by: Josh Pennell <[EMAIL PROTECTED]>

Can I allow relaying for a single _user_?
        29968 by: "Aijaz A. Ansari" <[EMAIL PROTECTED]>
        29983 by: Chris Johnson <[EMAIL PROTECTED]>

REQUEST: Correct /var/qmail/rc for IRIX (binm?+df)?
        29970 by: Dave Sill <[EMAIL PROTECTED]>

bare line feed?
        29972 by: "Michael Boyiazis" <[EMAIL PROTECTED]>

RAID 5 and queue restore
        29975 by: [EMAIL PROTECTED]

Maildirmake
        29977 by: [EMAIL PROTECTED]
        29978 by: James Smallacombe <[EMAIL PROTECTED]>

maildirsmtp won't send procmailed messages
        29979 by: "Claudiu Balciza" <[EMAIL PROTECTED]>

Potential hole?
        29980 by: Dmitry Niqiforoff <[EMAIL PROTECTED]>
        29981 by: Sebastian Andersson <[EMAIL PROTECTED]>
        29988 by: Robert Varga <[EMAIL PROTECTED]>

web messaging
        29982 by: "Ilya Krel" <[EMAIL PROTECTED]>
        29984 by: Simon Woodward <[EMAIL PROTECTED]>

relaying based on MX records
        29985 by: "Jan Stanik" <[EMAIL PROTECTED]>
        29986 by: "Petr Novotny" <[EMAIL PROTECTED]>

bare lf generation
        29987 by: Simon Rae <[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]


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


Van Liedekerke Franky wrote:
> their is a patch available for limitting bounce sizes. Maybe it is still on
> the qmail pages, otherwise search in the mailarchives (someone recently
> posted it again).

  I upchucked the patch at the following URL :

http://www.jedi.claranet.fr/qmail-bounce.patch

  Anyway, it would be kewl if it was added to the Qmail home page (as a
local copy because that URL will soon disappear) .

  Best regards,
-- 
         Frank DENIS aka Jedi/Sector One aka DJ Chrysalis <[EMAIL PROTECTED]>
                -> Software : http://www.jedi.claranet.fr <-
                 -> Music : http://www.mp3.com/chrysalis <-




Hello guys!!
I have a Debian 2.1 with kernel 2.0.34, qmail 1.03, serialmail 0.75,
ucspi_tcp 0.84
and mutt 0.95.
I think i have a problem with serialmail.
I created the maildir pppdir with maildirmake in
/var/qmail/alias/ and my script to send emails is this:

#!/bin/sh
DIR=/var/qmail/alias/pppdir
PREFIX=alias-ppp-
IP=mail.iol.it
HELOHOST=`hostname --fqdn`
/usr/local/bin/maildirsmtp $DIR $PREFIX $IP $HELOHOST

So, when i write a message with mutt and i send it, the message doesn't
queue up the pppdir directory so that i pratically can't send  it with
my script.
__
Thank you in advance,
                    Enrico Mangano.







Enrico Mangano <[EMAIL PROTECTED]> wrote:

>I have a Debian 2.1 with kernel 2.0.34, qmail 1.03, serialmail 0.75,
>ucspi_tcp 0.84
>and mutt 0.95.
>I think i have a problem with serialmail.
>I created the maildir pppdir with maildirmake in
>/var/qmail/alias/ and my script to send emails is this:
>
>#!/bin/sh
>DIR=/var/qmail/alias/pppdir
>PREFIX=alias-ppp-
>IP=mail.iol.it
>HELOHOST=`hostname --fqdn`
>/usr/local/bin/maildirsmtp $DIR $PREFIX $IP $HELOHOST
>
>So, when i write a message with mutt and i send it, the message doesn't
>queue up the pppdir directory so that i pratically can't send  it with
>my script.

What are you doing to cause messages to go to /var/qmail/alias/pppdir?

-Dave






On Tue, 7 Sep 1999, Markus Stumpf wrote:
> 
> ~alias/.qmail-joe:
> &[EMAIL PROTECTED]
> | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
> 
> (which I thought already worked, doesn't any longer) only a bounce
> message is delivered.
> However if I use
> 
> ~alias/.qmail-joe:
> |forward [EMAIL PROTECTED]
> | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
> 
> it works as expected.
> 
> WHY? :-)) and are the few messages I had in my box "an accident" ?

Because forward deliveries (&) are always processed at last, and exit code
100 means permanent failure which prevents all not processed deliveries,
which includes all forwards, because the failing delivery was a program
delivery, so all forwards were to be processed. 

If you use 99, then it will process all previous delivery instructions in
file order, so even if they were forwards, but no deliveries of the unread
part of the .qmail file. This imitates the mentioned behaviour most
closely, but this does not give an error message. Or of course you can use
exit 0.

See more at the end of the manpage of dot-qmail.


Robert Varga






Markus Stumpf writes:
 > I want to create a bounce message for accounts of ppl that no longer
 > work here, but I also want to drop the mail into a valid users mailbox.
 > 
 > ~alias/.qmail-joe:
 > &[EMAIL PROTECTED]
 > | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
 > 
 > (which I thought already worked, doesn't any longer) only a bounce
 > message is delivered.

No, it never worked.

 > However if I use
 > 
 > ~alias/.qmail-joe:
 > |forward [EMAIL PROTECTED]
 > | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
 > 
 > it works as expected.

Right.  That's because program deliveries are handled in order, while
forwards ('&' deliveries) are done all at once at the end.  Actually,
what you're doing in the second version is unreliable in the general
case.  What if the second program delivery sometimes succeeded,
sometimes exited 100 and sometimes 111 (depending on the contents of
the email message, say).  Well, every time it exited 111, the |forward 
delivery would be re-executed and you'd get mail duplication.

The reliable way to do two program deliveries is to do one of them in
one .qmail file, and the other in another.  Like this:

cat > ~alias/.qmail-joe <<EOF
|forward [EMAIL PROTECTED]
&joe-bounce
EOF
cat > ~alias/.qmail-joe-bounce <<EOF
|cat NO-WORKER.TXT; exit 100
EOF

BTW, you don't need to put those commands in parens -- those two
commands don't need to be executed by the same shell invocation.
Also, the current directory for a program delivery in a .qmail is the
controlling user's home directory.

-- 
-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 Tue, Sep 07, 1999 at 05:39:15PM +0800, [EMAIL PROTECTED] wrote:

> Hello,
> 
> I am a rookie on using qmail, but I can feel the power of it, really
> amazing.
> 
> I have several questions about the implementation of qmail. If possible,
> please give me some advice. Thanks.
> 
> (1) Anti-relay Issue
> 
> Any security risk about Mail Relaying? If I really want to get rid of
> relay, which module or file is required to be modified? According to Mr.
> Peter Samuel's qmail tutorial at the recent SAGE-AU '99 conference, he
> states that qmail can be configured to prevent mail relaying by specifying
> valid incoming domains in /var/qmail/control/rcpthosts. Is it the case?

Yes. man qmail-smtpd for more info.

> (2) EXPN and VRFY Issue
> 
> Any security risk about EXPN and VRFY? I can't find any information about
> them on qmail released notes. Is that mean I can ignore these issues? Is it
> enabled as default on qmail?

qmail-smtpd does not support EXPN, and always gives a positive response
to VRFY. You can quit worrying about them.

-- 
See complete headers for more info




On Tue, 7 Sep 1999 [EMAIL PROTECTED] wrote:

> Hello,
> 
> I am a rookie on using qmail, but I can feel the power of it, really
> amazing.
> 
> I have several questions about the implementation of qmail. If possible,
> please give me some advice. Thanks.
> 
> (1) Anti-relay Issue
> 
> Any security risk about Mail Relaying? If I really want to get rid of
> relay, which module or file is required to be modified? According to Mr.
> Peter Samuel's qmail tutorial at the recent SAGE-AU '99 conference, he
> states that qmail can be configured to prevent mail relaying by specifying
> valid incoming domains in /var/qmail/control/rcpthosts. Is it the case?

It certainly is :) If you are using qmail-smtpd and you wish to avoid
being an open relay, create the file

    /var/qmail/control/rcpthosts

This file contains the list of mail domains for which you are happy to
RECEIVE mail. I'll repeat that as it seems to be a common error
amongst new qmail admins. The list of domains in rcpthosts are the
domains for which you will RECEIVE mail, they are NOT the list of
domains to which you want to SEND mail.

Now, if someone sends you mail and the envelope RCPT TO: component is
does NOT contain a mail domain listed in your rcpthosts file, then
qmail-smtpd will reject that address. Voila, you have now closed
relaying.

Read the qmail-smtpd man page, also see Dave Sill's excellent "Life
with qmail" pages.

PS This section was covered quite well during the tutorial session
itself - however the notes by themselves don't always convey the
complete discussions. That's why people pay to go to those
conferences :)

PPS Even though I'm now approaching 40 I still can't get used to being
called Mr :)

> 
> (2) EXPN and VRFY Issue
> 
> Any security risk about EXPN and VRFY? I can't find any information about
> them on qmail released notes. Is that mean I can ignore these issues? Is it
> enabled as default on qmail?

As Annand has already stated, VRFY and EXPN are not supported by
qmail-smtpd, so there are NO security issues with these SMTP commands.

Regards
Peter
----------
Peter Samuel                                [EMAIL PROTECTED]
Technical Consultant                        or at present:
eServ. Pty Ltd                              [EMAIL PROTECTED]
Phone: +61 2 9206 3410                      Fax: +61 2 9281 1301

"If you kill all your unhappy customers, you'll only have happy ones left"





On Sat, 4 Sep 1999, Stephen Berg wrote:

> I just added a new virtual domain to a qmail server and am curious as
> to the best/easiest way to restart qmail so it will see the changes
> in the rcpthosts and virtualdomains file under /var/qmail/control. 

For information on which program reads which control file, try 
"man qmail-control".  This will tell you that qmail-smtpd reads rcpthosts.
As it's a transient daemon, the next invocation will read a fresh copy; no
problem.  Virtualhosts is read by qmail-send.  As the man-page for
qmail-send says, send it a HUP and it will re-read virtualhosts (and
locals).

> So far a kill -ALRM does not seem to get qmail-send to reread the
> virtualdomains file.
> 
>                             Stephen Berg
> //-    USAF Instructor  -/-  Reluctant NT User -/- Web Designer    -//
> //-                 Home = [EMAIL PROTECTED]                   -//
> //-               Work = [EMAIL PROTECTED]               -//
> //-     http://iceberg.3c0x1.com/   -/-   http://www.3c0x1.com     -//     
> 
> 
> 

-- 
"Life is much too important to be taken seriously."
Thomas Erskine        <[EMAIL PROTECTED]>        (613) 998-2836





Hi,

I have two problems with qmail... first it seems that it doesn't use
aliases in user's home directories (e.g.
/home/john/alias/.qmail-john:doe).
The second is that qmail's pop3d server doesn't use aliases (in
/var/qmail/alias/.qmail-*) when downloading mails... :

user john.doe
pass blurp

it end's with error (but there is a /var/qmail/alias/.qmail-john:doe
file!).

Is that normal? I really need both of these things...

Greetings,
Marcin Jaskowiak






On Tue, 7 Sep 1999, Marcin Jaskowiak wrote:

> I have two problems with qmail... first it seems that it doesn't use
> aliases in user's home directories (e.g.
> /home/john/alias/.qmail-john:doe).

that's not in the user's homedir, that's a subdir "alias" that you
invented. if you create ~john/.qmail-john:doe you will be able to de\irect
messages to [EMAIL PROTECTED] with the file. the ~/alias/
directory is not an option, I donno why you tried it.

> The second is that qmail's pop3d server doesn't use aliases (in
> /var/qmail/alias/.qmail-*) when downloading mails... :

why would it use an alias as a user? how would it authenticate it anyway?
RTFM... this is basic Email stuff, not even Qmail specific.


-- 
Ira Abramov | Internet Zahav | Linux Guru and T-Shirt collector
Ixnay on the IcrosoftMay | please write to me only in English!
[EMAIL PROTECTED]       | it's hard to read Hebrew left to right





-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I have two problems with qmail... first it seems that it doesn't use
> aliases in user's home directories (e.g.
> /home/john/alias/.qmail-john:doe).

You seem confused what the .qmail files do. BTW - what is 
/home/john/alias? It is a subdirectory of john's home? That's not 
the right way. There's a system-wide user called alias, his home is 
probably /var/qmail/alias, and .qmail-john:doe should come in THAT 
directory.

The "aliases" in home directories would only control the part after 
the dash, like "john-sumething" is controlled by
/home/john/.qmail-something (notice no alias subdirectory)

> The second is that qmail's pop3d server doesn't use aliases (in
> /var/qmail/alias/.qmail-*) when downloading mails... :
> 
> user john.doe
> pass blurp
> 
> it end's with error (but there is a /var/qmail/alias/.qmail-john:doe
> file!).

And what do you think is john.doe's password? You should supply 
your own checkpassword if you want it to know aliases - or look for 
vchkpw(?) package (URL anyone?).

> Is that normal? I really need both of these things...

First try to understand how it is supposed to work. And yes, 
everything works as documented in qmail, you're not too likely to 
find new bugs in basic setups. :-) [I used to be a novice too.]

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBN9UQgVMwP8g7qbw/EQKdiQCgnhWLbNagb745Dohku8bnp/dvH+cAoN4i
hH4dHJk+ujm2EWG+mRxfgNZ+
=vDHH
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
                                                             [Tom Waits]





On Tue, 7 Sep 1999, Petr Novotny wrote:

> You seem confused what the .qmail files do. BTW - what is 
> /home/john/alias? It is a subdirectory of john's home? That's not 
> the right way. There's a system-wide user called alias, his home is 
> probably /var/qmail/alias, and .qmail-john:doe should come in THAT 
> directory.

i got that, but if you want for example to make the aliases automatically
by a program you'll need the rights to write to /var/qmail/alias.

> The "aliases" in home directories would only control the part after 
> the dash, like "john-sumething" is controlled by
> /home/john/.qmail-something (notice no alias subdirectory)

if i put .qmail-john:doe in homedir of john with content 'john@somehost'
it will not work (of course it works well when put in /var/qmail/alias).

> And what do you think is john.doe's password? You should supply 
> your own checkpassword if you want it to know aliases - or look for 
> vchkpw(?) package (URL anyone?).

yes, that is what i wanted to know ;) just wondering if there is other way
than modyfying checkpassword code.

thanks,
Marcin Jaskowiak






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> > You seem confused what the .qmail files do. BTW - what is 
> > /home/john/alias? It is a subdirectory of john's home? That's not 
> > the right way. There's a system-wide user called alias, his home is
> > probably /var/qmail/alias, and .qmail-john:doe should come in THAT
> > directory.
> 
> i got that, but if you want for example to make the aliases automatically
> by a program you'll need the rights to write to /var/qmail/alias.

Exactly. That's for security's for. If you want new aliases with 
sendmail, you need to write /etc directory. Simply, noone should 
be able to change aliases other than a privileged used.

If you need automatic change, make a script that reads users' 
demands, analyzes them (resolves conflicts) and created aliases. 
Run this script from cron as root or alias, and be sure you haven't 
left in some security hole.

> > The "aliases" in home directories would only control the part after the
> > dash, like "john-sumething" is controlled by /home/john/.qmail-something
> > (notice no alias subdirectory)
> 
> if i put .qmail-john:doe in homedir of john with content 'john@somehost'
> it will not work (of course it works well when put in /var/qmail/alias).

It will. Just send e-mail to john-john.doe@somehost. That's the 
address your .qmail file controls. Got it?

> yes, that is what i wanted to know ;) just wondering if there is other way
> than modyfying checkpassword code.

Downloading a ready-made package :-) Have a look around 
www.qmail.org.

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBN9UUS1MwP8g7qbw/EQJ20QCaA3Z6pS8nGqbHCP+meGVkvZ/b0JYAoKzv
6xiBvOtvLIyRlUPJMGmeK32u
=ru87
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
                                                             [Tom Waits]





I'm running qmail 1.03 on RH6.0 on a single dial-up ppp
machine.  I have had no problems for weeks and now
when I try to send to [EMAIL PROTECTED] or
[EMAIL PROTECTED] I get the following
in the mail log:

Sep  7 07:44:29 cherrycoke qmail: 936704669.009694 starting delivery 77: msg 
159
827 to remote [EMAIL PROTECTED]
Sep  7 07:44:29 cherrycoke qmail: 936704669.009932 status: local 0/10 remote 
1/20
Sep  7 07:44:29 cherrycoke qmail: 936704669.010049 starting delivery 78: msg 
159
826 to remote [EMAIL PROTECTED]  7 07:44:29 cherrycoke qmail: 
936704669.009932 status: local 0/10 remote 1/20
Sep  7 07:44:29 cherrycoke qmail: 936704669.010049 starting delivery 78: msg 
159
826 to remote [EMAIL PROTECTED]
Sep  7 07:44:29 cherrycoke qmail: 936704669.010150 status: local 0/10 remote 
2/20
Sep  7 07:44:30 cherrycoke qmail: 936704670.413031 delivery 77: deferral: 
Connected_to_131.193.178.181_but_connection_died._(#4.4.2)/
Sep  7 07:44:30 cherrycoke qmail: 936704670.413264 status: local 0/10 remote 
1/20
Sep  7 07:44:30 cherrycoke qmail: 936704670.503024 delivery 78: deferral: 
Connected_to_131.193.178.181_but_connection_died._(#4.4.2)/
Sep  7 07:44:30 cherrycoke qmail: 936704670.503209 status: local 0/10 remote 
0/20

/var/qmail/bin/qmail-qread :
7 Sep 1999 11:38:19 GMT  #159827  389  <[EMAIL PROTECTED]>
        remote  [EMAIL PROTECTED]
6 Sep 1999 22:09:08 GMT  #159826  414  <[EMAIL PROTECTED]>
        remote  [EMAIL PROTECTED]

Any ideas??
  Kurt

I could not even post to the list this question...argh!!

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com




[EMAIL PROTECTED] wrote:

>On Sun, Sep 05, 1999 at 12:09:14AM -0400, Russell Nelson wrote:
>> Dave Sill writes:
>>  > >: The qmail logs show remote concurrency over any given time period.
>>  > 
>>  > Not directly, as far as I can tell. Anyone have a script that'll parse 
>>  > a log and chart concurrency?
>> 
>> No, but you could do it pretty easily with my mrtg scripts and
>> configuration.  http://www.crynwr.com/mrtg/ .  The two scripts are in
>> qmail-mrtg and qmail-mrtg1 in that directory.
> 
>I have to point out that at least in MY unpatched qmail setup, the
>qmail logs quite clearly point out both the local and remote concurrency
>which qmail is reaching:
>
>936506732.264512 starting delivery 780: msg 179819 to local [EMAIL PROTECTED]
>936506732.264626 status: local 1/5 remote 0/50
>                         ^^^^^^^^^^^^^^^^^^^^^
>I'm wondering how "directly" they need to be showed.  :)

Well, for starters, qmail 1.01 should log that concurrency logging
wouldn't happen until qmail 1.03. I've still got a 1.01 system that's
working fine, so I haven't bothered upgrading it. It's now on my to-do 
list. :-)

-Dave




Matthew Harrell <[EMAIL PROTECTED]> wrote:

>Actually, these two cases are similiar machines but the first has one
>processor and the second two.   That's probably the difference you're
>seeing here.  They are running the same kernel revision except one is
>compiled for SMP.

That doesn't explain why the vmstat output was so different.

>I don't seem to have iostat on my machine.  What's a good replacement?

I couldn't find one under Red Hat 6. /proc/scsi/somethingorother shows 
cumulative stats. Don't know about IDE. Don't know if there's a
command that front-ends this. This isn't a qmail question.

-Dave




Hi,
 
I am trying to install qmail on a RedHat 6.0/2.2.10 box and I have followed the life with qmail directions up to the Section 2.8 where you are supposed to first try and start qmail, and RedHat won't even recognize the qmail binary as a binary? When I try to start it with the script or by manually, it just says, "no such file or directory". I have read through the documentation but only found troubleshooting information on once it is installed and you can run it. Can someone help? Thanks in advance.
 
Scott




"Scott MacDonald" <[EMAIL PROTECTED]> wrote:

>I am trying to install qmail on a RedHat 6.0/2.2.10 box and I have
>followed the life with qmail directions up to the Section 2.8 where
>you are supposed to first try and start qmail, and RedHat won't even
>recognize the qmail binary as a binary? When I try to start it with
>the script or by manually, it just says, "no such file or
>directory".

Exactly what command are you entering, and what is the exact error
message?

-Dave




Here is the part from the "Life with Qmail" I got hung up on.

#!/bin/sh

# Using stdout for logging
# Using control/defaultdelivery from qmail-local to deliver messages by
default

exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "`cat /var/qmail/control/defaultdelivery`" accustamp
Use your editor to create the above /var/qmail/rc, then execute these
commands:

    chmod 755 /var/qmail/rc
    mkdir /var/log/qmail

When I did this, it just hung there. It tried to execute it, and wouldn't
give me a prompt back untill I ctrl-c 'd it. I even got up and left it there
for over 5 min, and it was still hung. Then I downloaded the script in the
next section and tried to start the other part of qmail. I got the script
from the webpage link at:

http://Web.InfoAve.net/~dsill/qmail-script.txt.

I made it excecutible, and tried to run it. It gave me an error, "Cannot
find file or directory". But the script was there? It was the weirdest
thing.

So then I went for the heck of it to the /var/qmail/bin/ and tried the
qmail-start, and that gave the same, "cannot find file or directory" error."

Is there anything I need to do differently that you know of to make this run
on a RedHat 6.0 box?

Thanks again for the response.

Scott


-----Original Message-----
From: Dave Sill <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, September 07, 1999 9:40 AM
Subject: Re: qmail won't start


>"Scott MacDonald" <[EMAIL PROTECTED]> wrote:
>
>>I am trying to install qmail on a RedHat 6.0/2.2.10 box and I have
>>followed the life with qmail directions up to the Section 2.8 where
>>you are supposed to first try and start qmail, and RedHat won't even
>>recognize the qmail binary as a binary? When I try to start it with
>>the script or by manually, it just says, "no such file or
>>directory".
>
>Exactly what command are you entering, and what is the exact error
>message?
>
>-Dave
>





"Scott MacDonald" <[EMAIL PROTECTED]> wrote:

>Here is the part from the "Life with Qmail" I got hung up on.
>
>#!/bin/sh
>
># Using stdout for logging
># Using control/defaultdelivery from qmail-local to deliver messages by
>default
>
>exec env - PATH="/var/qmail/bin:$PATH" \
>qmail-start "`cat /var/qmail/control/defaultdelivery`" accustamp
>Use your editor to create the above /var/qmail/rc, then execute these
>commands:
>
>    chmod 755 /var/qmail/rc
>    mkdir /var/log/qmail
>
>When I did this, it just hung there.

When you did what? Created the /var/qmail/rc script? Chmod'd it?
Mkdir'd /var/log/qmail?

>It tried to execute it, and wouldn't
>give me a prompt back untill I ctrl-c 'd it. I even got up and left it there
>for over 5 min, and it was still hung.

When a command seems to hang:

1) Open another window and run top. Is it using lots of CPU? If so,
   skip to step 3.

2) Hit Control-D. Did anything happen? If so, the command was waiting
   for input. Figure out why (script typo or usage error).

3) Hit Control-C. Run the command again using trace/strace/truss/par.
   The resulting system call trace should provide useful debugging
   information.

>Then I downloaded the script in the
>next section and tried to start the other part of qmail. I got the script
>from the webpage link at:
>
>http://Web.InfoAve.net/~dsill/qmail-script.txt.
>
>I made it excecutible, and tried to run it. It gave me an error, "Cannot
>find file or directory". But the script was there? It was the weirdest
>thing.

1) Always provide exact copies of error messages. Paraphrases are
   usually useless.

2) When a script provides such an error, the cause is usually due to a
   ``shebang'' error, i.e., the first line of the script points to a
   command that's supposed to run the script. If that command doesn't
   exist, well, the script can't run. Look at the first line of your
   qmail script. It should say "#!/bin/sh", your system should have a
   file named /bin/sh, and it should be executable.

>So then I went for the heck of it to the /var/qmail/bin/ and tried the
>qmail-start, and that gave the same, "cannot find file or directory"
>error."

Did you do "qmail-start" or "./qmail-start"?

PLEASE PLEASE PLEASE cut and paste your commands and error messages!
Or use the "script" command if you aren't using X.

-Dave




I'd add 2 as a runlevel qmail should run at.

Mate




On Mon, 6 Sep 1999, Kush wrote:

> I have a mail gateway and it forwards email to specific mail hosts in my
> network. I have a few mailing lists on these mail hosts, but the mail
> gateway (with fastforward) is unable to forward any email destined to
> the ezmlm list email addresses.
> 
>  I have `noc:@shell.blah.com` in my aliases file

why do you use fastforward to forward the Emails then? if the servers
inside the firewall are of the format YYY.blah.com and the mail is infact
destined for [EMAIL PROTECTED] then use smtproutes. if it is a single
domain that you split to departmental mail servers, I sugest using a
fastforward file for the flat aliases, and a .qmail-aliasname-default for
aliases that may have extensions.


> This doesn't happen because noc-subscribe@ isnt in the alias file. Is
> there
> anyway I can specify a wildcard in the alias files? perhaps:
>   noc::@shell.blah.com? (I heard ":" could be a wildcard in qmail?)

you heard wrong. : is used in .qmail filenames to replace dots (some
security reason, forgot right now)

also, I don't believe "@hostname" as the right parameter is a legal
format.

what you want:

cd ~alias
echo "| forward $[EMAIL PROTECTED]" > .qmail-noc
ln -s .qmail-noc .qmail-noc-default


-- 
Ira Abramov | Internet Zahav | Linux Guru and T-Shirt collector
Ixnay on the IcrosoftMay | please write to me only in English!
[EMAIL PROTECTED]       | it's hard to read Hebrew left to right






Actually, there are about 9k of them in the default domain, and virtual domain
support was done via alias/fastforward (leftover from an old sun setup qmail by

another admin). So 9k in one vpasswd right now. I'm pushing them out into
individual vpasswd files one at a time as each customer has to change settings
on
their end to access mail after converted.. It runs fine with 9k users in a
single file so far.

Regards,

Steve

Robin Bowes wrote:

> > Vchkpw handles 10k users just fine in it's current version. I'm running
> 200
> > virtual domains totaling about 10k pop accounts on a p2/300 with 256mb
> ram,
>
> I'm speculating here (I know, I know... :o) but if you have 200 virtual
> domains with 10k users total, that's an average of 50 users per vpasswd
> file.  If there is only 1 virtual domain (as in the example) then there
> would be 10k users in vpasswd.
>
> > a couple scsi-2 drives, Apache 1.3.4, SQWebmail 0.20 on FreeBSD 3.1 and it
> > runs like a top. No complaints in the slightest from here as far as
> > performance goes. I was thinking of looking at hacking vchkpw to handle a
> > cdb style password file instead of flat text however. While I'm doing fine
> > now, the business is growing and I want to be sure I can continue when I
> > hit 15k+.
>
> Sounds like this may be a useful patch to have.
>
> R.
>
> > Steve
> >
> > Robin Bowes writes:
> > > This isn't an answer to the original question - just some thoughts...
> > >
> > > How would vchkpw perform in this situation?
> (http://www.inter7.com/vchkpw/)
> > > Presumably, the vpasswd file would be the bottleneck?  Is it possible to
> use
> > > vchkpw with a DB of some sort, eg CDB?  Presumably, this would involve
> > > hacking vchkpw appropriately?
> > >
> > > R.
> > >
> > > Chris McCarthy <[EMAIL PROTECTED]> wrote in message
> > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > > My company wants to provide users on the internet with a free email
> > > > service ([EMAIL PROTECTED]). We'll be starting off with about
> > > > 3,000 users, potentially growing up to 10,000 in the next 12 months.
> > > >
> > > > How feasible is it to create a passwd/shadow entry for each user,
> > > > providing them with POP/IMAP access ? (or maybe just pop if imap puts
> > > > too much load on the server).
> > > >
> > > > With the passwd and shadow files containing so many entries, will the
> > > > password lookups take forever ?
> > > >
> > > > Our current server spec is a PIII 400, 256M, but we'll replace it with
> a
> > > > high spec server if/when needed.
> > > >
> > > > Does this sound OK, or should we look at buying (or developing)
> hotmail
> > > > style software instead ?
> > > >
> > > >
> > > > Any ideas/comments appreciated,
> > > > .Chris.
> > > >
> > > >
> > >
> > >
> >

--
Stephen Comoletti
Systems Administrator
Delanet, Inc.  http://www.delanet.com
ph: (302) 326-5800 fax: (302) 326-5802







> Actually, there are about 9k of them in the default domain, and virtual
domain
> support was done via alias/fastforward (leftover from an old sun setup
qmail by
> another admin). So 9k in one vpasswd right now. I'm pushing them out into
> individual vpasswd files one at a time as each customer has to change
settings on
> their end to access mail after converted.. It runs fine with 9k users in a
> single file so far.

Ah, that answers my questions.

R.





I have read and read and read the man pages, online
resources, and anything else i could get my hands
on to try and resolve this problem on my own. Now I
turn to the masses for assistance.
 
my mail server is: mail.cbssol.com
I have all my local mail running just fine.
 
I created a new user like this:
useradd brian
userpasswd brian
*********
*********
su brian -c '/var/qmail/bin/maildirmake ~/Maildir'
 
In /var/qmail/control/virtualdomains I added the line:
laiken.com:brian
 
In /var/qmail/control/rcpthosts I added the line:
laiken.com
 
I then did:
killall -1 qmail-send
to restart qmail.
 
When I send a mail to [EMAIL PROTECTED] it bounces back to me with this:
Hi. This is the qmail-send program at mail.cbssolutions.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. (#5.1.1)
 
When I send the message to [EMAIL PROTECTED] it is delivered to [EMAIL PROTECTED]
 
I do not understand......
Thank you in advance for all of your help.
Keith From
 




Does Brian have a .qmail-default file in his homedir?

--Adam

On Tue, Sep 07, 1999 at 11:21:59AM -0500, Keith From wrote:
> I have read and read and read the man pages, online
> resources, and anything else i could get my hands
> on to try and resolve this problem on my own. Now I
> turn to the masses for assistance.
> 
> my mail server is: mail.cbssol.com
> I have all my local mail running just fine. 
> 
> I created a new user like this:
> useradd brian
> userpasswd brian
> *********
> *********
> su brian -c '/var/qmail/bin/maildirmake ~/Maildir'
> 
> In /var/qmail/control/virtualdomains I added the line:
> laiken.com:brian
> 
> In /var/qmail/control/rcpthosts I added the line:
> laiken.com
> 
> I then did:
> killall -1 qmail-send 
> to restart qmail.
> 
> When I send a mail to [EMAIL PROTECTED] it bounces back to me with this:
> Hi. This is the qmail-send program at mail.cbssolutions.com.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> 
> <[EMAIL PROTECTED]>:
> Sorry, no mailbox here by that name. (#5.1.1)
> 
> When I send the message to [EMAIL PROTECTED] it is delivered to [EMAIL PROTECTED]
> 
> I do not understand......
> Thank you in advance for all of your help.
> Keith From
> 




Keith From writes:

> I have read and read and read the man pages, online
> resources, and anything else i could get my hands
> on to try and resolve this problem on my own. Now I
> turn to the masses for assistance.
> 
> my mail server is: mail.cbssol.com
> I have all my local mail running just fine. 
> 
> I created a new user like this:
> useradd brian
> userpasswd brian
> *********
> *********
> su brian -c '/var/qmail/bin/maildirmake ~/Maildir'
> 
> In /var/qmail/control/virtualdomains I added the line:
> laiken.com:brian
> 
> In /var/qmail/control/rcpthosts I added the line:
> laiken.com
> 
> I then did:
> killall -1 qmail-send 
> to restart qmail.
> 
> When I send a mail to [EMAIL PROTECTED] it bounces back to me with this:

Your configuration rewrites '[EMAIL PROTECTED]' as
'[EMAIL PROTECTED]'.  Therefore '[EMAIL PROTECTED]' gets rewritten
as '[EMAIL PROTECTED]'.  It follows that in order for this
address to be deliverable, you must create ~brian/.qmail-brian containing
your delivery instructions.

-- 
Sam





GOT IT.........
thanks for everyones help.
Keith


----- Original Message -----
From: Sam <[EMAIL PROTECTED]>
To: Keith From <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 07, 1999 11:30 AM
Subject: Re: Virtual Domains


> Keith From writes:
>
> > I have read and read and read the man pages, online
> > resources, and anything else i could get my hands
> > on to try and resolve this problem on my own. Now I
> > turn to the masses for assistance.
> >
> > my mail server is: mail.cbssol.com
> > I have all my local mail running just fine.
> >
> > I created a new user like this:
> > useradd brian
> > userpasswd brian
> > *********
> > *********
> > su brian -c '/var/qmail/bin/maildirmake ~/Maildir'
> >
> > In /var/qmail/control/virtualdomains I added the line:
> > laiken.com:brian
> >
> > In /var/qmail/control/rcpthosts I added the line:
> > laiken.com
> >
> > I then did:
> > killall -1 qmail-send
> > to restart qmail.
> >
> > When I send a mail to [EMAIL PROTECTED] it bounces back to me with this:
>
> Your configuration rewrites '[EMAIL PROTECTED]' as
> '[EMAIL PROTECTED]'.  Therefore '[EMAIL PROTECTED]' gets rewritten
> as '[EMAIL PROTECTED]'.  It follows that in order for this
> address to be deliverable, you must create ~brian/.qmail-brian containing
> your delivery instructions.
>
> --
> Sam
>
>





Can someone tell me what the correct syntax for the qmail-pop3d.cdb is, or 
where to look to find the syntax and possible commands.

I can't get the pop3d to run through anything other than inetd,  when I try 
to run it through the tcp wrapper I get a 'hard-error.'  The only thing I 
can figure is that my pop3d rules are incorrect somehow.


Damon Parker

[EMAIL PROTECTED]
www.siliconsys.com
voice 512.478.1669
data/fax 512.478.1627
mobile 512.750.9793





-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 7 Sep 99, at 11:41, Damon Parker wrote:

> Can someone tell me what the correct syntax for the qmail-pop3d.cdb is, or
> where to look to find the syntax and possible commands.

What is qmail-pop3d.cdb? You mean the database for tcpserver, or 
something else I'm not aware of?

> I can't get the pop3d to run through anything other than inetd,  when I
> try to run it through the tcp wrapper I get a 'hard-error.'  The only
> thing I can figure is that my pop3d rules are incorrect somehow.

What line did you exactly use to invoke pop3d through - as you 
say - tcp wrapper (do you mean tcpserver?)?

FYI, my "rules" file for pop3 contains these lines:
195.250.137.225-238:allow
:deny
(ie. I am allowing pop3 access only for a few known hosts and 
noone else).

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBN9VPo1MwP8g7qbw/EQIPhgCgkH7WrtAVocc+5pibrvxnXhViTKcAn1IL
tbTeuM9v+gNbsdJ3rF68o2oq
=ur/U
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
                                                             [Tom Waits]




hello,
I have installed qmail some months ago deciding to configure it to work
with a system user per mailbox; now I'm trying to configure a single UID
setup for a virtual domain we have. I followed stricly the "Single-UID
based POP3 box HOWTO" by Paul Gregg but I wasn't able to get it working. It
seems that qmail-lspawn doesn't read the users/assign file.
this is the users/assign file:

arredonet-com-giordi:popuser:888:888:/var/qmail/popboxes/arredonet-com/giord
i:::
.

this is a maillog excerpt:
....
Sep  7 18:50:23 srv1 qmail: 936723023.574492 new msg 1571562
Sep  7 18:50:23 srv1 qmail: 936723023.574978 info msg 1571562: bytes 533
from <[EMAIL PROTECTED]> qp 1933 uid 82
Sep  7 18:50:23 srv1 qmail: 936723023.674622 starting delivery 210: msg
1571562 to local [EMAIL PROTECTED]
Sep  7 18:50:23 srv1 qmail: 936723023.675368 status: local 1/10 remote 0/20
Sep  7 18:50:23 srv1 qmail: 936723023.682072 delivery 210: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
Sep  7 18:50:23 srv1 qmail: 936723023.727420 status: local 0/10 remote 0/20
Sep  7 18:50:23 srv1 qmail: 936723023.848955 bounce msg 1571562 qp 1936
Sep  7 18:50:23 srv1 qmail: 936723023.873658 end msg 1571562
Sep  7 18:50:23 srv1 qmail: 936723023.936704 new msg 1571563
Sep  7 18:50:23 srv1 qmail: 936723023.937121 info msg 1571563: bytes 1069
from <> qp 1936 uid 87
Sep  7 18:50:24 srv1 qmail: 936723024.032461 starting delivery 211: msg
1571563 to local [EMAIL PROTECTED]
Sep  7 18:50:24 srv1 qmail: 936723024.033151 status: local 1/10 remote 0/20
Sep  7 18:50:24 srv1 qmail: 936723024.148640 delivery 211: success:
did_0+1+0/qp_1939/
....

Currently I have setup several other virtual domains all with mails to
system users and they work fine. I double checked file owners and
priviligies, all seem correct. I certenly missed something, can anyone help
me?

thank you
Ciao,
Giorgio





Since daemontools now produces hexadecimal TAI64N labels and the
qmailanalog programs want decimal TAI64N labels, they need to be
converted somewhere. Are there any patches to matchup that does that
already?

/Sebastian




Text written by Josh Pennell at 08:53 PM 9/6/99 -0700:
>
>I downloaded the patched pine src from
>http://3.am/pine4.10.maildir.tar.gz and built it on an Intel Solaris 2.6
>box.

This is eerily reminiscent of my troubles with the same version of Pine,
building on a Red Hat Linux 5.1 (Intel) box.

>What I have tried to get pine to read Maildir:
>
>// edits to the ~/.pinerc file
>inbox-path=~/Maildir           (didn't work)
>inbox-path=$HOME/Maildir       (didn't work)
>inbox-path=~/Maildir/          (didn't work)
>inbox-path="inbox"             (didn't work)
>
>It just always reads 0 messages in inbox :(  

I tried a few other variations on this and always got "can't open
/home/kmactane/Maildir: not a selectable folder".

I checked in with James Smallacombe about it, too, but he didn't have any
ideas aside from making sure the .qmail file has a trailing slash (which it
does).

In case it will help, here are a few more details on my system (don't
laugh; it serves stuff):

Intel Pentium 75 MHz
32 MB RAM
1 IDE HD

running RHL 5.1 (2.0.34 kernel)
shadow passwords
qmail 1.03
daemontools 0.53

Let me know if any other details would help.

-----------------------------------------------------------------
                             Kai MacTane
                         System Administrator
                      Online Partners.com, Inc.
-----------------------------------------------------------------
>From the Jargon File: (v4.0.0, 25 Jul 1996)

examining the entrails /n./ 

The process of grovelling through a core dump or hex image in an
attempt to discover the bug that brought a program or system down.
The reference is to divination from the entrails of a sacrified
animal. Compare runes, incantation, black art, desk check.






I was a little curious about this, so I went and downloaded the very same
file (to make sure I didn't tar the wrong source tree or something) and
built the thing agoin on my Solaris 2.5 (sparc) box and it works fine.

It also works fine on the box I'm typing this from (FreeBSD 3.2).  I use
$HOME/Maildir (without the trailing slash) as my pine inbox-path, I have
./Maildir/ in my .qmail file, and my env is:

[richard2 james james]$ echo $MAIL
/usr/home/james/Maildir

Kai speculated that it might have something to do with the Linux shadow
support but I have no idea what the deal is with the Solaris box, except
that it's Intel, and I don't see any mention of Intel Solaris in the
pine-ports file (not that it should have to...).

Anybody else have any success with it?  Platform?

On Tue, 7 Sep 1999, Kai MacTane wrote:

> Text written by Josh Pennell at 08:53 PM 9/6/99 -0700:
> >
> >I downloaded the patched pine src from
> >http://3.am/pine4.10.maildir.tar.gz and built it on an Intel Solaris 2.6
> >box.
> 
> This is eerily reminiscent of my troubles with the same version of Pine,
> building on a Red Hat Linux 5.1 (Intel) box.
> 
> >What I have tried to get pine to read Maildir:
> >
> >// edits to the ~/.pinerc file
> >inbox-path=~/Maildir         (didn't work)
> >inbox-path=$HOME/Maildir     (didn't work)
> >inbox-path=~/Maildir/                (didn't work)
> >inbox-path="inbox"           (didn't work)
> >
> >It just always reads 0 messages in inbox :(  
> 
> I tried a few other variations on this and always got "can't open
> /home/kmactane/Maildir: not a selectable folder".
> 
> I checked in with James Smallacombe about it, too, but he didn't have any
> ideas aside from making sure the .qmail file has a trailing slash (which it
> does).
> 
> In case it will help, here are a few more details on my system (don't
> laugh; it serves stuff):
> 
> Intel Pentium 75 MHz
> 32 MB RAM
> 1 IDE HD
> 
> running RHL 5.1 (2.0.34 kernel)
> shadow passwords
> qmail 1.03
> daemontools 0.53
> 
> Let me know if any other details would help.
> 
> -----------------------------------------------------------------
>                              Kai MacTane
>                          System Administrator
>                       Online Partners.com, Inc.
> -----------------------------------------------------------------
> From the Jargon File: (v4.0.0, 25 Jul 1996)
> 
> examining the entrails /n./ 
> 
> The process of grovelling through a core dump or hex image in an
> attempt to discover the bug that brought a program or system down.
> The reference is to divination from the entrails of a sacrified
> animal. Compare runes, incantation, black art, desk check.
> 
> 






Hello,

I downloaded the patched for Maildir version of pine-4.10 and built it
on a Solaris 2.6 intel box.

I have tried the following to try to get pine to read my Maildir inbox

// edits to the ~/.pinerc file
inbox-path="inbox"
inbox-path=~/Maildir
inbox-path=~/Maildir/
inbox-path=$HOME/Maildir
inbox-path=/export/home/joshp/Maildir

Any other ideas to get this beast working?  Pine seems to think it can
open the folder when I set inbox-path to "inbox" but there are no
messages to be viewed.  I telneted to port 110 and did a STAT on my
account and I had 75 msg's available.

Thanks for your time and help,


Josh




Hello, all.

I'm running qmail 1.03 on Red Hat 5.2 with a slightly modified (for use
with cucipop) version of smtp-poplock to allow for relaying after a
successful POP authentication.  All users are using Mailbox and not
Maildir.

There is one user who insists that checking for email before sending it
would be too much trouble and would like to have relaying set
unconditionally for him.

I don't know if he has a static IP address, so I don't know if I can allow
relaying for a certain IP address (if I can, I know how to do that).

So my question is: Is there any way to allow relaying for a certain user?
In other words, is there any way to enable relaying based upon the SMTP
envelope From header?

I don't know much about all this, but it seems to me that this is not a
trivial thing (not to mention prudent).  Can I insert a custom-built
program in the smtp 'chain of programs' that looks for the SMTP header?

This is my smtp entry in inetd.conf (without the \<return>s):
smtp stream tcp nowait qmaild /usr/sbin/tcpd \
                              /var/qmail/bin/tcp-env \
                              /usr/src/smtp-poplock/relaylock \
                              /var/qmail/bin/qmail-smtpd

[relaylock sets the RELAYCLIENT env var for authorized IP addresses]

I'd appreciate any help you can give me.  I tried looking in the FAQ and
list archives but couldn't find an answer.

Thanks in advance,

Aijaz A. Ansari.





On Tue, Sep 07, 1999 at 02:35:58PM -0500, Aijaz A. Ansari wrote:
> Hello, all.
> 
> I'm running qmail 1.03 on Red Hat 5.2 with a slightly modified (for use with
> cucipop) version of smtp-poplock to allow for relaying after a successful POP
> authentication.  All users are using Mailbox and not Maildir.
> 
> There is one user who insists that checking for email before sending it would
> be too much trouble and would like to have relaying set unconditionally for
> him.
> 
> I don't know if he has a static IP address, so I don't know if I can allow
> relaying for a certain IP address (if I can, I know how to do that).
> 
> So my question is: Is there any way to allow relaying for a certain user?  In
> other words, is there any way to enable relaying based upon the SMTP envelope
> From header?
> 
> I don't know much about all this, but it seems to me that this is not a
> trivial thing (not to mention prudent).  Can I insert a custom-built program
> in the smtp 'chain of programs' that looks for the SMTP header?

It's not a prudent thing since it's trivial to forge the envelope sender. But
if you want to do it, here's a patch:
http://www.palomine.net/qmail/relaymailfrom.patch

Chris




"Jay D. Dyson" <[EMAIL PROTECTED]> wrote:

>       I've set up everything find, but the rc script to use has me
>befuddled.  I want the mail to be written to /var/spool/mail and all, but
>when I try most every invocation as supplied, I get large errors and the
>mail isn't delivered.

What invocations have you tried? What "large" errors resulted? Be
precise.

-Dave




Greetings,
   I log smtp connects to a file and at certain times one user will seem to
be getting pounded with mail from a particular IP.  When I check the
maildir there is nothing new there.  There are no errors going to the
syslog.

Could this be the bare linefeed issue?

Would that cause the chatter between my server and the sender's?

If this is a linefeed issue, would adding the fixcr program to the tcpserver
line for smtp program handle that without putting undo strain on the box to
deal with just a few hosts that send out garbage?

Thanks,
   mike.

________________________________________________________
NetZero - We believe in a FREE Internet.  Shouldn't you?
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html




On Mon, Sep 06, 1999 at 01:22:08PM -0500,  wrote:
> Suppose I was running a DPT RAID 5 controller and the mail queue was
> stored on this RAID array. What will happen to the inode structure of
> the queue if one of the disks fails, I replace it and the controller
> rebuilds it?

Nothing.  You're covered at the inode level.

But that doesn't mean the RAID 5 is good to use.  Use 1+0 instead. 

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






Hey everyone- I am just ready to put my Qmail server running under FreeBSD
3.2-Stable on line, but I'm having one minor problem.  I created an account
for myself and used "maildirmake" to created my home directory's maildir-
but now I am trying to add the rest of my users, but I get an error when
trying to use "maildirmake" the following is what I entered and what the
error was:

$/var/qmail/bin/maildirmake /usr/home/boudin/Maildir/.
maildirmake: fatal: unable to mkdir /usr/home/boudin/Maildir/.: file does
not exist


what could be the problem here...my director is still working fine...

please help!!

Thanks in advance,
Bernie Courtney

Bernard Courtney
Z100 New York Radio Engineering
mailto:[EMAIL PROTECTED]






On Tue, 7 Sep 1999 [EMAIL PROTECTED] wrote:

> Hey everyone- I am just ready to put my Qmail server running under FreeBSD
> 3.2-Stable on line, but I'm having one minor problem.  I created an account
> for myself and used "maildirmake" to created my home directory's maildir-
> but now I am trying to add the rest of my users, but I get an error when
> trying to use "maildirmake" the following is what I entered and what the
> error was:
> 
> $/var/qmail/bin/maildirmake /usr/home/boudin/Maildir/.
> maildirmake: fatal: unable to mkdir /usr/home/boudin/Maildir/.: file does
                                                               ^
Take out that dot.





I use a dial-up (offline) mail server qmail-1.0.3 + serialmail-0.75+safecat
on RedHat Linux
It works great.
The offline mailser just stores the outgoing mail into a maildir and
maildirsmtp sends it when invoked.
But when I filter the outgoing mail through procmail+safecat, maildirsmtp
just ignores it.

The only difference I noticed about filtered messages is the name.
The original ones are #########.#####.digital.altex.ro
while the procmailed ones are #########.##########.digital.altex.ro

why is that ? (and how can I solve it ?)

Claudiu

here's my .procmailrc

----------- .procmailrc -------------
PATH=/bin:/usr/bin:/usr/local/bin:/var/qmail/bin
MAILDIR=$HOME/pppdir
DEFAULT=$HOME/$USER
LOGFILE=$HOME/MAILLOG
LOGABSTRACT=all
VERBOSE=no
LOCKTIMEOUT=1
SHELL=/bin/sh
UMASK=022
ORGMAIL=$HOME
COMSAT=no

EXITCODE=99
:0
* !^From:.*mail-supervisor@altex\.ro
! [EMAIL PROTECTED]
#| formail -k -X From: -X Sender: -X Return-Path: | qmail-inject
[EMAIL PROTECTED]

EXITCODE=99
:0w
| safecat $HOME/pppdir/tmp $HOME/pppdir/new
-------------------------------------






Hello!

  Yesterday I found that any user are able to start any program at
server with .qmail file. This could be potentially dangerous, AFAIU. As
an example: I denied TELNET access (disabled the service in inetd.conf),
but any user can put "|in.telnetd" in their .qmail file (ofcourse, there
should be not only in.telnetd to work correctly).
  Also, any user are able to get our /etc/passwd file. It is not
dengerous because there is no passwords, but it is possible to a) find
out where user homedir is, and b) get total list of the users which can
be later used for, lets say, spamming.
  Your imagination is the only limit for this.

  Is there any suggestions about how to avoid all the potential
problems?

________________________________________________________
  Regards, Dmitry Niqiforoff      [tel. +7 8462 427427]
  Kraft-S, Ltd.
  Samara, Russia







On Wed, Sep 08, 1999 at 11:24:45AM +0500, Dmitry Niqiforoff wrote:
>   Is there any suggestions about how to avoid all the potential
> problems?

Yes.
1) Hack qmail-local to deny | usage for your users (check the gid?).

2) Prevent the users from creating .qmail files. Our users homedirs are
owned by someone else. We give them subdirectories to use. Any dot file
that we allow them to use are a symbolic link to a normal file in a sub
directory. That way we don't have to worry about all other possible dot
files that might give them the right to run something. We use a simple
web page that let them configure forwarding, instead of letting them
modify the files.

3) Hack qmail-local to chroot to the users' homedirs before running any
commands. That way you can limit the damage the user may do and still let
them run some programs. We do this for our users cgi programs. Don't forget
resource limits if you follow this path...

/Sebastian






On Wed, 8 Sep 1999, Sebastian Andersson wrote:

> On Wed, Sep 08, 1999 at 11:24:45AM +0500, Dmitry Niqiforoff wrote:
> >   Is there any suggestions about how to avoid all the potential
> > problems?

What is the problem? They run programs with their uid and gid.
They would not be able to run in.telnetd I think... or am I wrong?

Robert Varga





Is something hotmail-like possible for QMail? are there programs which allow
it?





Last I heard Hotmail actually uses qmail to operate ... when MS took over
hotmail, they tried to replace everything with NT, but it just couldnt hack it.

On 08-Sep-99 at 07:48:39, Ilya Krel muttered something like:

> Is something hotmail-like possible for QMail? are there programs which allow
> it?





Hi,

        In Sendmail, I can define the feature "relay based on MX". Is it 
possible configure qmail to  work similar way?
 
--
  Jan Stanik
[EMAIL PROTECTED]
Telenor Internet,s.r.o




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8 Sep 99, at 10:52, Jan Stanik wrote:
>  In Sendmail, I can define the feature "relay based on MX". Is it 
> possible configure qmail to  work similar way?

It is possible, I would think. It means you need to read the RCPT 
TO: part, get the "remote host" part and check if you're and mx for 
that host. A few lines in qmail-smtpd should solve that.

I would not consider this an option though: You have no control 
whatsoever about individuals listing you as their backup MX. Very 
simple DoS (overfilling the queue partition) are straightforward - I'll 
list you as my secondary MX, shut down my primary MX and get 
many e-mails sent to me (from many places). Your queue overfills.

Human control is desirable. It's not too difficult to put a line in 
rcpthosts (or morercpthosts and rebuild).

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBN9Yz8FMwP8g7qbw/EQIyPQCePoJrLbIIULEZlxxm5vKfNoqyIUcAoMVG
PpCtYENwknSXPCFYntgerLcd
=c7bT
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
                                                             [Tom Waits]




Can anyone tell me if they've experienced bare lfs being generated by an
MTA rather than the client end?

I've noticed that if I send a message with an attachment using our qmail
1.03 server it goes through ok, but if I send it using our old NTMail3
box as a relay, it gets bounced after so many days with the following
entries appearing in the NTMail log file.

POST 7 Sep 99 13:38:57 F 2128 3925 waiting 10038 mailhost.howden.com
POST 7 Sep 99 13:38:57 F 2135 3925 reschedule db026471.mbx to 13:50:57
(53290, [EMAIL PROTECTED])
POST 7 Sep 99 13:44:25 F 2128 3926 waiting 10038 mailhost.howden.com
POST 7 Sep 99 13:44:25 F 2135 3926 reschedule eb026472.mbx to 13:56:25
(53322, [EMAIL PROTECTED])
POST 7 Sep 99 13:47:02 F 2128 3927 waiting 10038 mailhost.howden.com
POST 7 Sep 99 13:47:02 F 2135 3927 reschedule ia026528.mbx to 13:59:02
(53337, [EMAIL PROTECTED])

and occasionally

POST 7 Sep 99 22:36:38 F 2155 4092 temporary failed mailhost.howden.com
"451 See http://pobox.com/~djb/docs/smtplf.html."

This only seems to happen to mail with attachments. I suspect NTMail is
broken, but it seems odd that this only happens to mail destined for our
qmail server sent using a variety of clients (Netscape Messenger,
Outlook).

Simon





Reply via email to