qmail Digest 1 Oct 1999 10:00:01 -0000 Issue 776

Topics (messages 31077 through 31120):

qmail-send single threaded
        31077 by:  Van Liedekerke Franky
        31085 by:  Dave Sill
        31086 by:  B. Engineer
        31089 by:  Dave Sill
        31090 by:  David Harris

Filter mail from when Qmail is a SMTP router ?
        31078 by:  Herwin Jan Steehouwer

Re: please, some help to block spam
        31079 by:  farber.admin.f-tech.net

%
        31080 by:  olli
        31084 by:  Dave Sill

Return message problem.
        31081 by:  Super-User
        31082 by:  Van Liedekerke Franky

Linking perl and DJB libraries?
        31083 by:  David Harris
        31114 by:  Russ Allbery

Re: Daemontools?
        31087 by:  Dave Sill
        31092 by:  Jos Backus

qmail-queue was killed?
        31088 by:  Fred backman
        31091 by:  Harald Hanche-Olsen
        31093 by:  Fred backman
        31094 by:  Harald Hanche-Olsen
        31095 by:  Fred backman
        31096 by:  Stefaan A Eeckels

Fixed it -- thanks!! (Re: qmail-queue was killed?)
        31097 by:  Fred backman

1) No Nameserver  2) Triple Bounce
        31098 by:  jarrid jeeby

RFC 822 Complience
        31099 by:  Eric Davis

Re: rewrite From: header
        31100 by:  Balazs Nagy

Re: 2) Triple Bounce
        31101 by:  Markus Stumpf
        31107 by:  jarrid jeeby
        31109 by:  Markus Stumpf
        31110 by:  jarrid jeeby
        31116 by:  jarrid jeeby

.qmail-"alias" files
        31102 by:  Tony Wade
        31103 by:  Russell Nelson

.qmail alias files
        31104 by:  Tony Wade
        31105 by:  Fred Lindberg

Re: big-todo patch +queue-fix
        31106 by:  Eric Huss
        31108 by:  Matthew Harrell

limit user mail?
        31111 by:  B. Engineer
        31113 by:  Sam

qmail-tcpto and non-authoritative DNS
        31112 by:  Fred Lindberg

New features in qmLogsort
        31115 by:  Monte Mitzelfelt

Re: How good is RBL at filtering spam?
        31117 by:  Markus Stumpf

A record vs MX
        31118 by:  Fred Lindberg

FROM line
        31119 by:  Franklin A Hays

Mail Relay
        31120 by:  Emmanuel Nee

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To bug my human owner, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


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


Hi,

I'm experiencing serious problems (slow queue processing) with qmail (sol
2.6), and I think the bottleneck is qmail-send. When I do a truss on this
process I see (truss -c):

hercules(root)/var/qmail/queue/intd> truss -c -p 19880 
^Csyscall      seconds   calls  errors 
read             .01     106 
write            .02     645 
open             .04      84 
close            .00      82 
unlink           .03      59     36 
time             .00      48 
stat             .01      88     63 
lseek            .00      11 
fstat            .00      36 
fdsync           .01      24 
poll             .00      12 
                ----     ---    --- 
sys totals:      .12    1195     99 
usr time:        .00 
elapsed:        4.48 
 


Now these are a lot of writes for one process to handle (especially single
threaded). From the INTERNALS file I see that qmail-send is a very important
process (creates the info/, remote/ or local/, removes the todo/ and the
intd/ files for each message).
Is there a way I can boost the performance of qmail send?
Or can it be made multi-threaded?

Franky




Van Liedekerke Franky <[EMAIL PROTECTED]> wrote:

>Is there a way I can boost the performance of qmail send?

Faster hardware, especially the queue disk, will help, of course. A
solid state "disk" would really speed things up.

>Or can it be made multi-threaded?

You can run multiple installations of qmail on the system--preferrably 
using queues on different controllers. The trick is evenly dividing
the labor.

-Dave




On Thu, 30 Sep 1999, Dave Sill wrote:

> You can run multiple installations of qmail on the system--preferrably 
> using queues on different controllers. The trick is evenly dividing
> the labor.

Hmmm..
I would be interested in hearing more on this. I would have thought that 
it would not be possible as it needs to bind to port 25 but I can't argue 
with the author of lwq.

Anybody currently doing this?

Burzin




"B. Engineer" <[EMAIL PROTECTED]> wrote:

>On Thu, 30 Sep 1999, Dave Sill wrote:
>
>> You can run multiple installations of qmail on the system--preferrably 
>> using queues on different controllers. The trick is evenly dividing
>> the labor.
>
>I would be interested in hearing more on this. I would have thought that 
>it would not be possible as it needs to bind to port 25 but I can't argue 
>with the author of lwq.

Sure, you can argue with me. I'm just another qmail user. I'm even
wrong now and then. :-)

You're right that port 25 can only be serviced by a single
installation (at a time), but there can be any number of installations 
processing locally-injected messages or messages rerouted by the
installation listening to port 25.

For a very busy mail hub, one approach would be two installations: one 
handling messages coming in via port 25, another handling messages
injected by qmail-inject/sendmail.

For a very busy mail generator (list server, opt-in "spammer", etc.),
multiple installations can be used for locally injected messages by
having different sending processes use different copies of
qmail-inject.

An insanely busy hub could have multiple installations take turns
listening to port 25, or have the listening installation reroute to
other installations. But at this level of load, it makes more sense to 
use multiple boxes and MX's.

-Dave





B. Engineer [mailto:[EMAIL PROTECTED]] wrote:
> > You can run multiple installations of qmail on the system--preferrably
> > using queues on different controllers. The trick is evenly dividing
> > the labor.
>
> Hmmm..
> I would be interested in hearing more on this. I would have thought that
> it would not be possible as it needs to bind to port 25 but I can't argue
> with the author of lwq.

I think people were talking about using multiple queues when sending lots of
e-mail to the world, so the just placed e-mail in all four queues from their
programs.

If you want to receive lots of e-mail, setup multiple qmail installations
(hopefully with disks on different queues/controllers) and setup daemontools to
randomly run one of the four qmail-smtp programs for each incoming connection.

Write a simple c program that takes multiple arguments and simple exec's one of
the arguments randomly, and you are set.

 - David Harris
   Principal Engineer, DRH Internet Services






Hi,

I have 2 questions:

1) Can i filter mail that QMail reroute with smtproute ? eg. mail bigger
the 5mb will be bounched etc ?

2) Can i monitor/log the number of spam attacks and for no. 1 the ammount
of mail ( inc from: etc ) bounced ?

tanx


Herwin Jan Steehouwer
  KPMG Management services/KPMG CT                    
  Churchilplein 6
  2517 JW  Den Haag
  (+31)70 338 2 471





True.  The spam may just que on a server somewhere for a few days then
die.

But you still need to process the mail up to a point to the badmailfrom
check and deny the mail.

Personal preference I would guess.

Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph  570-628-5303
Fax 570-628-5545

On 30 Sep 1999, Michael Graff wrote:

>  <[EMAIL PROTECTED]> writes:
> 
> > By the time the packet hits badmail from you've already done a lot of work
> > to just reject the connection.
> > 
> > Filter it as soon as possible.  BEFORE it get to you SMTP port.... so you
> > don't have to spawn an ident child, then a qmail-smtpd then reject the
> > packet. I'm not sure of exactly how far up the chain you would go to
> > finally get to the badmailfrom file..... but it has to be slower than
> > ipfwadm.
> 
> However, rejecting the mail explicitly rather than appearing to be
> dead is often better.
> 
> If you reject the mail, perhaps a postmaster somewhere else on some
> open relay mail server will get a full mailbox instead.  That's the
> quickest way to get an open relay shut down.
> 
> --Michael
> 






On Thu, 30 Sep 1999, Herwin Jan Steehouwer wrote:

I got that for my qmail "%" & "@" are diffrent & % is treated as a part of
name , not the user & domain delimiter in emails . exim & sendmail are
treating `%` as a delimiter.. Is it normal that my qmail won't??

I.e.: [EMAIL PROTECTED] is not the same as sysop%domain.com for my qmail.

Should I leave all as is or do somthing? & what should I read in this
case?

Bye.Olli.
                //System administrator of "Russia Young" internet group.

Any info around "Russia Young" & Boris Nemtsov:
http://www.rosmol.ru , http://www.nemtsov.ru , http://www.boris.nemtsov.ru





olli <[EMAIL PROTECTED]> wrote:

>I got that for my qmail "%" & "@" are diffrent & % is treated as a part of
>name , not the user & domain delimiter in emails . exim & sendmail are
>treating `%` as a delimiter.. Is it normal that my qmail won't??
>
>I.e.: [EMAIL PROTECTED] is not the same as sysop%domain.com for my qmail.
>
>Should I leave all as is or do somthing? & what should I read in this
>case?

% and @ are not interchangable in e-mail addresses. Sendmail invented
its own syntax for relaying addresses: user%hostb@hosta, which means
"send to user@hostb via hosta". qmail supports this mechanism if
control/percenthack is used.

You probably shouldn't change anything.

-Dave




Hi,

        I would like to force to return the message after two days, if qmail
is not able to delivery, not to wait 6 days as is set by default. How can
I solve this problem?


        Maros BOJKO.





The control file queuelifetime does this for you. Place in there the number
of seconds you want a message to stay in the queue (default = 604800 = one
week).

Franky

> ----------
> From:         Super-User[SMTP:[EMAIL PROTECTED]]
> Reply To:     Super-User
> Sent:         Thursday, September 30, 1999 4:01 PM
> To:   [EMAIL PROTECTED]
> Subject:      Return message problem.
> 
> Hi,
> 
>       I would like to force to return the message after two days, if qmail
> is not able to delivery, not to wait 6 days as is set by default. How can
> I solve this problem?
> 
> 
>       Maros BOJKO.
> 





Has anybody had any success linking perl and DJB libraries? I actually want to
embed some of his code from the fastforward package, to exact, in a Perl module
using XS.

I've used XS before to embed C in Perl, but I'm not sure about what possible
issues might arise for the DJB libraries. For example, does he trounce on names
used by glibc? Can anyone who knows more about c compiler stuff offer any
insight?

Thanks.

 - David Harris
   Principal Engineer, DRH Internet Services






David Harris <[EMAIL PROTECTED]> writes:

> I've used XS before to embed C in Perl, but I'm not sure about what
> possible issues might arise for the DJB libraries. For example, does he
> trounce on names used by glibc? Can anyone who knows more about c
> compiler stuff offer any insight?

I haven't seen anything in DJB's code that would make me think it would
break embedded Perl.  Bear in mind though that qmail is a bunch of small
programs and embedded Perl tends to be large, so it's easy to seriously
hurt performance.

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




Derek Harkness <[EMAIL PROTECTED]> wrote:

>Is there any real advantage to upgrading to daemontools >= 0.60?  I'm
>using 0.53 now which is working great.

0.61 is "better" than 0.53, but, as you say, 0.53 works great. If you
have 0.53 installed, configured, and running, I wouldn't recommend
switching to 0.61 unless you just have nothing better to do with your
time.

For a new installation, if you don't need LWQ-like handholding, 0.61
is probably the way to go. The svscan mechanism is nice.

One downside to 0.61 is that its tai65n timestamps are incompatible
with qmailanalog.

-Dave




On Thu, Sep 30, 1999 at 11:01:10AM -0400, Dave Sill wrote:
> One downside to 0.61 is that its tai65n timestamps are incompatible
> with qmailanalog.

Just for info: I use the following to make 0.61 work with qmailanalog-0.70:

        (
        test -f pending && cat pending
        (
        cd /service/qmail/log/main
        for f in @* current
        do
          case $f in
            *.gz) zcat $f;;
            *) cat $f;;
          esac
        done
        ) | tai64n2time \
        ) | between $YESTERDAY $TODAY | matchup > qmailmatchup.out 5> pending

between is

        #!/usr/local/bin/perl

        (my $program=$0)=~s%.*/%%;

        die "usage: $program from to\n" unless @ARGV >= 2;

        my $from = shift;
        my $to = shift;

        while (<>) {
          if (/^(\d+)/) {
            print if $from <= $1 && $1 <= $to;
            next;
          }
          print;
        }

        exit 0;

and tai64n2time is

        #!/usr/local/bin/perl

        while (<>) {
          if (my($s,$t,$rest)=/^\@.(\w{15})(\w{8})(.*)/) {
            $s = hex($s);
            $t = hex($t); $t =~ s/500$//;
            $_ = "$s.$t$rest\n";
          }
        } continue {
          print;
        }

        exit 0;

-- 
Jos Backus                          _/ _/_/_/  "Reliability means never
                                   _/ _/   _/   having to say you're sorry."
                                  _/ _/_/_/             -- D. J. Bernstein
                             _/  _/ _/    _/
[EMAIL PROTECTED]  _/_/  _/_/_/      use Std::Disclaimer;




My mail server has been working okay until recently, and I cannot figure out why it's 
not working. This is what I get when I try to send a message locally:

# echo bollox | /var/qmail/bin/qmail-inject
qmail-inject: fatal: qmail-queue was killed

Nothing shows up in the syslog. Nothing in the mail queue.

Sending to the "bollox" account via smtp works just fine! Any ideas?

cheers
TB
_______________________________________________________
The Web's BEST free email.......
Get your FREE account at http://www.pmail.net

My Pmail address is: 
Fred backman <[EMAIL PROTECTED]>






+ Fred backman <[EMAIL PROTECTED]>:

| My mail server has been working okay until recently, and I cannot
| figure out why it's not working. This is what I get when I try to
| send a message locally:
| 
| # echo bollox | /var/qmail/bin/qmail-inject
| qmail-inject: fatal: qmail-queue was killed
| 
| Nothing shows up in the syslog. Nothing in the mail queue.
| 
| Sending to the "bollox" account via smtp works just fine! Any ideas?

As a first try, you could try to present a valid message to
qmail-inject:

# echo to: bollox | /var/qmail/bin/qmail-inject

If it still fails, turn on process tracing (if your system allows it)
and see what happens to the process.

- Harald




----- Original Message ----- >
> As a first try, you could try to present a valid message to
> qmail-inject:
>
> # echo to: bollox | /var/qmail/bin/qmail-inject

Sorry, that was a typo. I did exactly the line you suggested.

> If it still fails, turn on process tracing (if your system allows it)
> and see what happens to the process.

Do you mean I should trace qmail-queue? If so, how do I do that when
qmail-queue is invoked from qmail-inject?

I tried tracing qmail-inject but I couldn't figure out why qmail-queue was
killed. Here's the tail of the trace. Any further ideas?

# echo to: bollox | truss /var/qmail/bin/qmail-inject > & junk
# tail junk
close(4)                                        = 0
write(6, " F r o o t @ c r a p .".., 67)      = 67
write(6, "\0", 1)                               = 1
close(6)                                        = 0
    Received signal #18, SIGCLD, in wait() [default]
      siginfo: SIGCLD CLD_KILLED pid=2415 status=0x000B
wait()                                          = 2415 [0x000B]
qmail-inject: fatal: qmail-queue was killed
write(2, " q m a i l - i n j e c t".., 44)      = 44
_exit(111)





+ "Fred Backman" <[EMAIL PROTECTED]>:

| > If it still fails, turn on process tracing (if your system allows it)
| > and see what happens to the process.
| 
| Do you mean I should trace qmail-queue? If so, how do I do that when
| qmail-queue is invoked from qmail-inject?

You seem to be on a Solaris system.  Then use truss -f to trace the
children.  (You can also use -o filename to redirect the trace
output.)  Since qmail-queue is a setuid program you have to be root to
do this, but then I believe it will work.

- Harald




----- Original Message ----- 
From: Harald Hanche-Olsen <[EMAIL PROTECTED]>
> | Do you mean I should trace qmail-queue? If so, how do I do that when
> | qmail-queue is invoked from qmail-inject?
> 
> You seem to be on a Solaris system.  Then use truss -f to trace the
> children.  (You can also use -o filename to redirect the trace
> output.)  Since qmail-queue is a setuid program you have to be root to
> do this, but then I believe it will work.

Thanks for the advice, Harald! Ok, here's what I get now using -f flag:

(first what seems to be "normal" trace output, and then around line 100)
....
2761:   close(6)                                        = 0
2761:   fcntl(3, F_GETFL, 0x00000000)                   = 2
2761:   ioctl(3, I_FIND, "sockmod")                     = 0
2761:   close(0)                                        = 0
2761:   fcntl(3, F_DUPFD, 0x00000000)                   = 0
2761:   close(3)                                        = 0
2761:   fcntl(5, F_GETFL, 0x00000000)                   = 2
2761:   ioctl(5, I_FIND, "sockmod")                     = 0
2761:   close(1)                                        = 0
2761:   fcntl(5, F_DUPFD, 0x00000001)                   = 1
2761:   close(5)                                        = 0
2761:   execve("bin/qmail-queue", 0x0002F1DC, 0xEFFFF91C)  argc = 1
2761:       *** SUID: ruid/euid/suid = 0 / 1129 / 1129  ***
2761:   open("/dev/zero", O_RDONLY)                     Err#13 EACCES
2761:   open("/dev/zero", O_RDONLY)                     Err#13 EACCES
...
(*thousands* of these EACCES error messages, and then the tail)
...
2761:   open("/dev/zero", O_RDONLY)                     Err#13 EACCES
2761:       Incurred fault #6, FLTBOUNDS  %pc = 0xEF7E6D8C
2761:         siginfo: SIGSEGV SEGV_MAPERR addr=0xEF7FFFE8
2761:       Received signal #11, SIGSEGV [default]
2761:         siginfo: SIGSEGV SEGV_MAPERR addr=0xEF7FFFE8
2760:       Received signal #18, SIGCLD, in wait() [default]
2760:         siginfo: SIGCLD CLD_KILLED pid=2761 status=0x000B
2760:   wait()                                          = 2761 [0x000B]
qmail-inject: fatal: qmail-queue was killed
2760:   write(2, " q m a i l - i n j e c t".., 44)      = 44
2760:   _exit(111)
2761:           *** process killed ***







On 30-Sep-99 Fred Backman wrote:
>  2761:   open("/dev/zero", O_RDONLY)                     Err#13 EACCES
>  2761:   open("/dev/zero", O_RDONLY)                     Err#13 EACCES
>  ...
Check the privileges on /devices/pseudo/mm@0:zero, they should be
something like:
crw-rw-rw-   1 root     sys       13, 12 Oct 23  1998 /devices/pseudo/mm@0:zero

Stefaan
-- 

PGP key available from PGP key servers (http://www.pgp.net/pgpnet/)
___________________________________________________________________
  In a world where everyone uses an alias, one's real identity is
  the best disguise.




Just for the record:
The problem with "qmail-queue was killed" turned out to be bogus permission
mode on the root directory (which somehow affected qmail-queue's access to
/dev/zero).

# ls -ld /
drwx---r-x  35 root     root        1536 Sep  4 08:47 //
should obviously have been
drwxr-xr-x  35 root     root        1536 Sep  4 08:47 //

Extra special thanks to Harald Hanche-Olsen for helping me! :-)

cheers
Fred





What is the format of smtproutes if I were to temporarily disable my 
nameserver?  Will adding "-Hl my.fqdn.com" to my tcpserver qmail-smtpd also 
be required to enable all the functionality of qmail without a nameserver?

Currently my smtprutes reads:
:my.full.ip.address 25


** Veterans of qmail should stop reading here to avoid hairloss over reading 
the same problems time and time again...


Additionaly I wondered what possible causes are there for the message:

failure: Soory,_no_mailbox_here_by_that_name._(#5.1.1)/

... Specifically when the recepient *does* exist as a /etc/passwd user 
AND/OR as a vchkpw /home/popusers/user user.

This error occurs for everyone, including the bounce to postmaster, and is 
eventually discarded as a triple bounce.  The recepient address is 
[EMAIL PROTECTED] or [EMAIL PROTECTED]  I am sending the message 
from a telnet 25 so I do not receive anything back worth mentioning.

defaultdomain = domain.com
locals = host.domain.com & domain.com
me = host.domain.com
plusdomain = domain.com
rcpthosts = domain.com & host.domain.com
virtualdomains = host.domain.com:domain.com

users/assign (as cdb) reads:
+host.domain.com:popmail:1007:1001:/home/popusers/users:-::
.

where uid 1007 = vpopmail
and gid 1001 = vchkpw

/home/popusers/users/vpasswd reads:
someuser:b.bRztEXdHXZo:1:0:POP User:/home/popusers/users/someuser:NOLOGIN

/home/popusers/users/someuser was created with vadduser an has the 
appropriate vpopmail/vchkpw ownership with a Maildir.

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




Is there a way to allow qmail to accept message that violate 822bis
section 2.3 at all?  It causes qmail to generate the following link:
ftp://koobera.math.uic.edu/www/docs/smtplf.html

This was sent from a Groupwise mail server.

In my SMTP log file I have:
 38709482.754801 5932 < Mime-Version: 1.0
 38709482.754942 5932 < Content-Type: text/plain; charset=US-ASCII
 38709482.755111 5932 < Content-Transfer-Encoding: quoted-printable
938709482.755275 5932 < Conten+
 38709482.755520 5932 < t-Disposition: inline
 38709482.755666 5932 < 
938709482.755782 5932 <  
 38709482.755902 5932 < my first message had a "dot" after the net.
 38709482.756067 5932 < 
+38709482.756183 5932 < sorry,
 38709482.757235 5932 > 451 See http://pobox.com/~djb/docs/smtplf.html.
938709482.758056 tcpserver: end 5932 status 256
938709482.758238 tcpserver: status: 0/40
938709482.758504 5932 > [EOF]

Thank you for any help with this.

-Eric Davis
[EMAIL PROTECTED]




On Thu, 26 Aug 1999, Dave Sill wrote:

> "x" <[EMAIL PROTECTED]> wrote:
> 
> >  Send to mail on W/S:  
> >
> >      From: header = "user-1" <[EMAIL PROTECTED]>          (on F/S)
> >
> >  How to  change From: header  into :   "user-1" <[EMAIL PROTECTED]>
> 
> The best way to do this is to inject messages with the desired From
> field. See the qmail-inject man page for various ways to accomplish
> that. Your mailer may/should also let you configure the From field.

You have two choices:
1| You send the mail locally.
   You can set environment variables such USER and HOST (or QMAILUSER,
   QMAILHOST).
2| You use SMTP service.
   MUAs have the header writing feature and you don't have to do header
   rewriting.

Basically, Dave Sill is right.  The question isn't "how to rewrite" but "how
can i solve it".
-- 
Regards: Kevin (Balazs)





On Thu, Sep 30, 1999 at 09:33:38AM -0700, jarrid jeeby wrote:
> virtualdomains = host.domain.com:domain.com
>
> users/assign (as cdb) reads:
> +host.domain.com:popmail:1007:1001:/home/popusers/users:-::

Your virtualdomains should probably contain two lines:
domain.com:domain.com
host.domain.com:domain.com

This says that email for
   @domain.com  and  @host.domain.com
should be handled by the user "domain.com".
Mail addresses get then "translated" from
   [EMAIL PROTECTED]       to      [EMAIL PROTECTED]
   [EMAIL PROTECTED]  to      [EMAIL PROTECTED]

In virtualdomains you could use for the second line also
.domain.com:domain.com
so you wouldn't have to list each host separately.

Your users/assign should read:
+domain.com-:popmail:1007:1001:/home/popusers/users:-::

This is a wildcard match for users with names starting with
   "domain.com-"
This part is then stripped of and the delivery is in control of a file
   /home/popusers/users/.qmail-joe
or of course
   /home/popusers/users/.qmail-default


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




>Your virtualdomains should probably contain two lines:
>domain.com:domain.com
>host.domain.com:domain.com

ok

>In virtualdomains you could use for the second line also
>.domain.com:domain.com
>so you wouldn't have to list each host separately.

great

>Your users/assign should read:
>+domain.com-:popmail:1007:1001:/home/popusers/users:-::

removed host name, replaced "-" which I had removed, updated cdb file

>This part is then stripped of and the delivery is in control of a file
>    /home/popusers/users/.qmail-joe
>or of course
>    /home/popusers/users/.qmail-default

Interesting part...
My .qmail-default reads: (as documented)

| /home/popusers/bin/vdelivermail

I have created the .qmail-someuser which reads "someuser" on one line, 
however I had thought this was not neccessary with vchkpw.

The only other file in users/ is .qmail-postmaster which reads:

&[EMAIL PROTECTED]

The bounces remain.  In fact, the only was I can get the word "success" to 
appear in the log is to use "rcpt to:" with no recepient (which obviously 
cannot be that successful).

[EMAIL PROTECTED]

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




On Thu, Sep 30, 1999 at 11:25:29AM -0700, jarrid jeeby wrote:
> Interesting part...
> My .qmail-default reads: (as documented)
> 
> | /home/popusers/bin/vdelivermail
> 
> I have created the .qmail-someuser which reads "someuser" on one line, 
> however I had thought this was not neccessary with vchkpw.

.qmail-default  is a "wildcard". Is controls all addresses that do not
have explicit .qmail-someuser files.
So having a .qmail-default with "| /home/popusers/bin/vdelivermail"
should be ok.


> The only other file in users/ is .qmail-postmaster which reads:
> 
> &[EMAIL PROTECTED]
> 
> The bounces remain.  In fact, the only was I can get the word "success" to 
> appear in the log is to use "rcpt to:" with no recepient (which obviously 
> cannot be that successful).

>> where uid 1007 = vpopmail                                             
>> and gid 1001 = vchkpw

Hmmm ...
Are all the directories on the (real) path to
    /home/popusers/users
accessible by uid 1007 ?

I once had a similar problem where the destination directory was a
link to  /mount/some/disk/destdir  and the "disk" directory was
    drwx------ root
so qmail could not access destdir.

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




>Hmmm ...
>Are all the directories on the (real) path to
>     /home/popusers/users
>accessible by uid 1007 ?

uid 1007 = vpopmail
gid 1001 = vchkpw

/                       drwxr-xr-x 20 root     root
/home                   drwxr-xr-x  4 root     root
/home/popusers          drwxr-xr-x  4 vpopmail vchkpw
/home/popusers/vpasswd  -rw-------  1 vpopmail vchkpw
/home/popusers/bin      drwxr-xr-x  2 vpopmail vchkpw
/home/popusers/users    drwxr-xr-x  3 vpopmail vchkpw

users/.qmail-default    -rw-r--r--  1 vpopmail vchkpw
users/.qmail-postmaster -rw-r--r--  1 vpopmail vchkpw

users/someuser          drw-------  3 vpopmail vchkpw
users/someuser/Maildir  drw-------  3 vpopmail vchkpw
...same for cur, new, tmp dirs


[EMAIL PROTECTED]



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




Just a note to all those following my progress:

I can smtp out, in, pickup with pop3, accept restricted relays, and setup 
virtual domains!  qmail is great!  ... eventually!  :-)

I'd also like to take this opportunity to thank Markus for going far out of 
his way and helping me get things right.  All of the list members I 
encountered have been very helpful and I'm sure this goes a long way to help 
make qmail what it is.

My next challenges are:

1. Setting up fetchmail temporarily and getting it to remember the rcpt to: 
field of all the mail it picks up so it can be delivered to the appropriate 
vchkpw user.

2. Correct a problem I have with local to local deliveries where the rcpt 
to: field is only a the account name.  ie. Mail to "joe" gets delivered as 
"[EMAIL PROTECTED]".  I'd like it to be delivered to "[EMAIL PROTECTED]", 
else fix my setup to allow "host.domain.com" to work.

3. The /home/popusers/users/.qmail-postmaster successfully forwards all mail 
for the post master to the address specified, HOWEVER bounced mail that is 
redirected to the postmaster is not sent to the .qmail-postmaster address.  
This appears to be a result of issue #2 above.... the bounce is redirected 
to [EMAIL PROTECTED] instead of [EMAIL PROTECTED]  Better get 
the host working right?

Thanks again,

[EMAIL PROTECTED]

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




Hi all, 

I am about 2 hours away from killing our sendmail server and Replacing it
with Qmail. 

In the .qmail-"alias" files does one have to have &[EMAIL PROTECTED]
weather it is a single alias in the file or when there is more than one
alias in the file ? 

ta

Tony Wade (Postmaster)
The Internet Solution
Tel:    (+27 11) 283 5483
Fax:    (+27 11) 283 5401
E-mail: [EMAIL PROTECTED] 
Web:    http://www.is.co.za
Life would be so much easier if we could just look at the source code.
        -- Dave Olson





Tony Wade writes:
 > In the .qmail-"alias" files does one have to have &[EMAIL PROTECTED]
 > weather it is a single alias in the file or when there is more than one
 > alias in the file ? 

Neither.  &[EMAIL PROTECTED] means the same thing as
[EMAIL PROTECTED]  That is, the default interpretation is '&'.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://russnelson.com
Crynwr sells support for free software  | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




Hi again, 

Sorry for the double post but after reading my mail, i noticed that i may
not have been clear on what i was asking.

in /var/qmail/alias

.qmail-postmaster 
twade
root

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

should it be 

&twade
&root 

or is it fine to have it as is ? 

ta

 
Tony Wade (Postmaster)
The Internet Solution
Tel:    (+27 11) 283 5483
Fax:    (+27 11) 283 5401
E-mail: [EMAIL PROTECTED] 
Web:    http://www.is.co.za
Life would be so much easier if we could just look at the source code.
        -- Dave Olson





On Thu, 30 Sep 1999 20:14:28 +0200, Tony Wade wrote:

>should it be 
>
>&twade
>&root 
>
>or is it fine to have it as is ? 

man dot-qmail | grep relevant_info:

            qmail-local  takes  the  rest  of  the line as a mail
            address; it uses qmail-queue to forward  the  message
            to  that  address.   The address must contain a fully
            qualified domain name;  it  must  not  contain  extra
            spaces, angle brackets, or comments:

                 # the following examples are WRONG
                 &me@new
                 &<[EMAIL PROTECTED]>
                 & [EMAIL PROTECTED]
                 &[EMAIL PROTECTED] (New Address)

            If  the  address  begins with a letter or number, you
            may leave out the ampersand:

                 [EMAIL PROTECTED]


-Sincerely, Fred

(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)






> just wondering if, after I applied the big-todo patch, I can still use the
> queue-fix program?
> 
> Franky
> 

Matthew Harrell gave me the following patch.  I have not tried it.

-Eric

--- queue-fix-1.4/queue-fix.c-ori       Tue Aug 17 09:43:58 1999
+++ queue-fix-1.4/queue-fix.c   Tue Aug 17 09:52:16 1999
@@ -445,9 +445,9 @@
                        if(rename_mess("info/",part,new_part,d->d_name,inode)) { 
closedir(dir); return -1; }
                        if(rename_mess("local/",part,new_part,d->d_name,inode)) { 
closedir(dir); return -1; }
                        if(rename_mess("remote/",part,new_part,d->d_name,inode)) { 
closedir(dir); return -1; }
+                       if(rename_mess("intd/",part,new_part,d->d_name,inode)) { 
+closedir(dir); return -1; }
+                       if(rename_mess("todo/",part,new_part,d->d_name,inode)) { 
+closedir(dir); return -1; }
 
-                       if(rename_mess("intd","","",d->d_name,inode)) { closedir(dir); 
return -1; }
-                       if(rename_mess("todo","","",d->d_name,inode)) { closedir(dir); 
return -1; }
                        if(rename_mess("bounce","","",d->d_name,inode)) { 
closedir(dir); return -1; }
                }
        }
@@ -513,9 +513,9 @@
                if(clean_tmp("info/",name_num)) return -1;
                if(clean_tmp("local/",name_num)) return -1;
                if(clean_tmp("remote/",name_num)) return -1;
+               if(clean_tmp("intd/",name_num)) return -1;
+               if(clean_tmp("todo/",name_num)) return -1;
        }
-       if(clean_tmp("intd","")) return -1;
-       if(clean_tmp("todo","")) return -1;
        if(clean_tmp("bounce","")) return -1;
 
        return 0;
@@ -553,19 +553,19 @@
        if(check_item(check_dir.s,qmails_uid,qmail_gid,0700,'d',0)) return -1;
        if(check_splits(check_dir.s,qmails_uid,qmail_gid,0700,qmail_gid,0600)) return 
-1;
 
-       /*check the others*/
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"todo")) die_nomem();
        if(!stralloc_0(&check_dir)) die_nomem();
        if(check_item(check_dir.s,qmailq_uid,qmail_gid,0750,'d',0)) return -1;
-       if(check_files(check_dir.s,qmailq_uid,-1,0644)) return -1;
+       if(check_splits(check_dir.s,qmailq_uid,qmail_gid,0750,qmail_gid,0600)) return 
+-1;
 
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"intd")) die_nomem();
        if(!stralloc_0(&check_dir)) die_nomem();
        if(check_item(check_dir.s,qmailq_uid,qmail_gid,0700,'d',0)) return -1;
-       if(check_files(check_dir.s,qmailq_uid,-1,0644)) return -1;
+       if(check_splits(check_dir.s,qmailq_uid,qmail_gid,0750,qmail_gid,0644)) return 
+-1;
 
+       /*check the others*/
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"bounce")) die_nomem();
        if(!stralloc_0(&check_dir)) die_nomem();
@@ -684,16 +684,14 @@
        if(!stralloc_cats(&check_dir,"remote")) die_nomem();
        if(check_stray_parts()) return -1;
 
-
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"todo")) die_nomem();
-       if(!stralloc_0(&check_dir)) die_nomem();
-       if(check_strays(check_dir.s)) return -1;
+       if(check_stray_parts()) return -1;
 
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"intd")) die_nomem();
-       if(!stralloc_0(&check_dir)) die_nomem();
-       if(check_strays(check_dir.s)) return -1;
+       if(check_stray_parts()) return -1;
+
 
        if(!stralloc_copy(&check_dir,&queue_dir)) die_nomem();
        if(!stralloc_cats(&check_dir,"bounce")) die_nomem();




:> just wondering if, after I applied the big-todo patch, I can still use the
:> queue-fix program?

: Matthew Harrell gave me the following patch.  I have not tried it.

Yeah, I use that patch and it seems to work fine for me.  Let me know if you
have any problems.

-- 
  Matthew Harrell                          You're just jealous because the
  Bit Twiddlers, Inc.                       voices only talk to me.
  [EMAIL PROTECTED]




Hello:
        Is there a way in qmail to limit new (incoming or outgoing) messages 
per user in a day? 
I figure if I can control that number globally (ability to override it 
for some users would be great) then my free mail service will be less 
attractive to spammers. 

Any ideas?

Regards
Burzin





B. Engineer writes:

> Hello:
>       Is there a way in qmail to limit new (incoming or outgoing) messages 
> per user in a day? 
> I figure if I can control that number globally (ability to override it 
> for some users would be great) then my free mail service will be less 
> attractive to spammers. 
> 
> Any ideas?

Put a fixed .qmail file in every recipient account, which runs a small C
program followed by a delivery instruction to the default mailbox.

The C program will keep track of number of messages received per day for
this account, and print an error message and terminate with the appropriate
exit code for accounts that go over the daily limit.

-- 
Sam





Hi,

I have a mailing list host with many subscribers unreachable due to
internet cable problem. Those for which there is authoritative DNS
available go into the tcp timeout table and are not retried for 1 h.

Those for which authoritative DNS is not available (all on the other
side of the break) will be retried and hog a "concurrency" until DNS
times out. Those for which no DNS also yield the same result.

Thus, I have several 100 list messages in the queue all constantly
retrying the same set of addresses, all of which clog the system
waiting for DNS replies. This adversely affects deliveries to reachable
addresses.

Would it make sense to have a similar table (or put into the same
table) also host for which authoritative DNS is not available? Usually,
this is due to a network problem (as for the tcpto entries) and it
affects all messages to the host (same as for tcpto table entries). If
the failure is transient, a 1h delay would be acceptable.

The host with complete DNS failure are more difficult, since it would
require storing the host name or a hash thereof, so there it may make
more sense to just keep retrying.

Of course, increasing concurrency would be a solution. However, the
system runs at an average concurrency of 5 normally and due to the
network problems it is now pegged at 120.

Thanks!

-Sincerely, Fred

(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)







Tell and seek functions have been added to qmLogsort.  This allows
searches to be started at particular places in the log file.  --tell
prints the starting file position of each record it prints, and --seek
allows you to start searchs at the positions listed by --tell.  The perl
script is at:
  http://www.gonefishing.org/techstuff/qmLogsort

Thanks,
Monte Mitzelfelt
New Mexico Technet, Inc.






On Mon, Sep 20, 1999 at 04:24:06PM -0400, David Harris wrote:
> > I'll run this for a few days and let the list know what I find.

While we're on some statistics:
I use the patch that denies MAIL FROM when the domain cannot be
resolved. I have modified tha patch a bit so it logs the denial and
the reason. I have grepped though the logfiles of one of our servers of
the last couple of days and counted the number of lines that contain
"tcpcontrol: ok" (still using and elder version; this should give a
fairly good approximation on injected mails via smtp), the number of
lines with permanent DNS rejects (address doesn't have an A or MX record
or does not exists). "soft" rejects (server errors, not auth) are not
included. The last column is the number of rejects due to MAPS rbl
(I'm using only this one).

  day       tcpcontrol ok   DNS perm rejects   RBL rejects
1999/10/23      21161         74                63
1999/10/24      20077         69                78
1999/10/25      65771         25                76
1999/10/26      37812         28                34
1999/10/27      22373        102                31
1999/10/28      50850        315                52
1999/10/29      22800         79                41
1999/10/30      23521         89                38

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





lists.mysql.com is the sole MX for www2.analytikerna.se and set up as
a virtual domain for mailing lists. THe owners want to also direct
http://lists.mysql.com to the same host.

Obviously, doing this with a CNAME will screw up mail due to canonicalization
at sending MTAs. Is there a problem with adding an A record for
lists.mysql.com pointing to the same IP as www2.analytikerna.se? Any risk
that a sender will rewrite it after an MX lookup? I think so, but I'm
not sure.

The reverse lookup yields www2.analytikerna.se which is the HELO name that
qmail uses.

Thanks!

-- 

-Sincerely, Fred

Fred Lindberg, Inf. Dis., WashU, St. Louis, MO, USA





this is a problem I have found several times in the archive yet i haven't
been able to find an actual solution.  the From line is missing on my
outgoing messages.  I understand qmail-inject adds the appropriate
information to the header, yet how do i set the 'appropriate information'?
i have read the man page, any other help?  Is there someplace I can
manually set the From field?  why isn't qmail-inject build the From
field for the user, me, invoking it?

am i approaching the problem wrong?  any help is appreciated.

-frank
------------------------------------------------------------------------------- 
[EMAIL PROTECTED]
http://spin.biochem.okstate.edu/~frank
-------------------------------------------------------------------------------





Hi,

I've a pop server in Zurich (headquater) which we cuurently point our
mail to. The problem is that larger mail attachment take a long time to
download into the local drive though we have a lease line connected.
This mail server configuration I do not have previledge to change. How
can I make use of a local mail server to download all mail from my users
and then local we retrive that to our local workstation. I want to make
this as transparent as possible. Hope that someone can help.

Emmanuel



Reply via email to