qmail Digest 16 Nov 1999 11:00:01 -0000 Issue 821

Topics (messages 33046 through 33123):

Steps Done but not receiving mails in qmail
        33046 by: john

..No mailbox here by that name...
        33047 by: Edward Castillo-Jakosalem
        33048 by: Magnus Bodin
        33050 by: Ricardo Cerqueira
        33052 by: Edward Castillo-Jakosalem
        33053 by: Magnus Bodin

Upgraded RedHat from 5.2 to 6.1, qmail 1/2 broken.
        33049 by: Troy Frericks

Re: RCPT aggregation
        33051 by: Mark Evans
        33054 by: Sam
        33090 by: Joe Kelsey
        33093 by: Sam
        33095 by: Joe Kelsey
        33099 by: Russell Nelson
        33101 by: Bruce Guenter

Re: 550  cannot route to sender
        33055 by: Nagy Balazs

Re: Large message killing system
        33056 by: Ruben van der Leij

Qmail and Email virus protection
        33057 by: Deon Stoltz

Re: Don't seem to be receiving any mails - CheckPassword, Vpopmail question
        33058 by: Ken Jones

Re: TCPSERVER RUNNING with manual keying in of Script & But problem with VPOPMail
        33059 by: Dave Sill

Re: Not receiving mails into the qmail server but the mail goes through
        33060 by: Dave Sill

qmail-send hogging resources on upgraded FreeBSD system
        33061 by: Chris Hardie
        33065 by: Jos Backus

log rotation scripts
        33062 by: Peter Green

open relay report
        33063 by: Mate Wierdl
        33064 by: James Raftery
        33077 by: dd
        33078 by: Greg Moeller
        33079 by: Delanet Administration
        33081 by: Bruno Wolff III
        33117 by: dd

Re: qmail-send hogging resources on upgraded FreeBSD system (resolved)
        33066 by: Chris Hardie
        33067 by: Jos Backus

Limiting incoming connections
        33068 by: Michael Cunningham
        33069 by: Peter Green
        33071 by: Rohit Khamkar
        33073 by: Russell Nelson
        33074 by: Michael Cunningham
        33088 by: Sam
        33100 by: waskita adijarto

Does locals allow to hide hosts ?
        33070 by: Aaron Optimizer Digulla
        33075 by: Russell Nelson

elementary rblsmtpd question
        33072 by: Mate Wierdl
        33076 by: Timothy L. Mayo

Re: Sorting incoming mail.
        33080 by: Tristan Hannover
        33089 by: Sam
        33107 by: Tristan Hannover
        33123 by: Subba Rao

adding site-wide signatures to all outgoing emails ?
        33082 by: mfischer.josefine.ben.tuwien.ac.at
        33106 by: Magnus Bodin
        33111 by: Alex at Star

Re: dot-qmail files and running programs
        33083 by: Geoff Roberts

Duplicate messages.
        33084 by: Andy Bradford
        33085 by: Rohit Khamkar
        33086 by: Andy Bradford
        33097 by: Russell Nelson
        33098 by: Andy Bradford

webmin qmail-module problems
        33087 by: Marco Leeflang

Man pages
        33091 by: Steve Kapinos
        33094 by: Robbie Walker
        33119 by: dd

Anti-Virus wrapper for QMAIL and AVP
        33092 by: JHanna.cproject.com

User has no Maildir?
        33096 by: Peter Cavender

Re: qmail remote delivery logic
        33102 by: Bruce Guenter

Filtering email content
        33103 by: Phil Crooker
        33104 by: Andy Bradford
        33105 by: Bruce Guenter

Re: pop3 How To
        33108 by: Marco Leeflang
        33109 by: Benjamin de los Angeles Jr.

Re: qmail-tcpto and non-authoritative DNS
        33110 by: D. J. Bernstein

Re: why setgid directories
        33112 by: D. J. Bernstein

Re: Beware when patching Solaris machines
        33113 by: D. J. Bernstein

Re: getting qmail to retry
        33114 by: D. J. Bernstein

Re: qmail dies 2 times a day, at least
        33115 by: D. J. Bernstein

Re: methods for ETRN
        33116 by: D. J. Bernstein
        33122 by: Georgi Kupenov

Re: No mailbox error...sometimes on large distributions
        33118 by: D. J. Bernstein

Re: Big DNS-patch also for t-online.de required
        33120 by: D. J. Bernstein
        33121 by: Frank Tegtmeyer

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]


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


Let me be clear what I am trying to say :
 
I am using Red Hat ver 6.1 and am trying to setup my mail server with qmail.
 
I installed
1. qmail-1.03.tar.gz
2. ucspi-tcp-o.84
3. daemontool0.53
 
I am using Dave Sill's "Life with Qmail" as my reference to do the installation.
 
4. I installed first qmail-1.03 with the installation instructions given --- while doing ./congif I encountered and error finding the domain, so I went to linuxconf and set my domain name, then did a ./config-fast FQDN - and the installation went on successful.
5. Secondly - I installed ucspi-tcp and it went on successfully
6. Thirdly - I installed daemontools-0.53
 
Note: All these three files are residing in /usr/local/src/qmail
 
7.Then I created the rc file accordingly under /var/qmail/
 
and created the ./Maildir/ format and set it up in the defaultdelivery file
 
8. Then I went about writing the sript file (qmail) since the one I downloaded from the site did not work many times during boot up and infact even now I need to manually start it. by /usr/local/bin/qmail start.
 
9. But now after writing the script on my own from "LWQ" i was atleast able to start the file using the /usr/local/bin/qmail start command.
 
10.The only thing I never did before this is after killing sendmail I did not link the
     ln -s /var/qmail/bin/sendmail  /usr/lib
     ln -s /var/qmail/bin/sendmail  /usr/sbin
 
but apart from the above 2 steps the prior 3 steps shown below I completed it
 
mv /usr/lib/sendmail /usr/lib/sendmail.old
mv /usr/sbin/sendmail /usr/sbin/sendmail.old
chmod 0 /usr/lib/sendmail.old /usr/sbin/sendmail.old
 
11. Then I did an echo to .qmail-root, .qmail-postmaster and so on... so forth
 
12. Later I found it was difficult for me to understand adding the users through qmail so I installed VPOPMail, checkpassword and ezmlm, autorespond
 
13. I created the users in the user directory /home/vpopmail/users/
 
14. I tried to echo To: john@mydomainname | /var/qmail/bin/qmail-inject but I don't seem to have received any mails into  it.
 
15. So i tried adding the tcpserver in the qmail script so to start the tcpserver and also pop3d.
 
16 I linked the pop3d file.
 
17 My tcpserver and pop3d seems to be started and working but I don't seem to receive incoming mails
 
18 I tried to do a ps -ax to check the processes running and this is what I get below
 
PID TTY      STAT   TIME COMMAND
    1 ?        S      0:04 init [3]
    2 ?        SW     0:00 [kflushd]
    3 ?        SW     0:00 [kupdate]
    4 ?        SW     0:00 [kpiod]
    5 ?        SW     0:00 [kswapd]
    6 ?        SW<    0:00 [mdrecoveryd]
  274 ?        S      0:00 portmap
  329 ?        S      0:00 syslogd -m 0
  340 ?        S      0:00 klogd
  356 ?        S      0:00 /usr/sbin/atd
  372 ?        S      0:00 crond
  392 ?        S      0:00 inetd
  408 ?        S      0:00 lpd
  430 ?        S      0:00 gpm -t ps/2
  446 ?        S      0:00 httpd
  450 ?        S      0:00 httpd
  451 ?        S      0:00 httpd
  452 ?        S      0:00 httpd
  453 ?        S      0:00 httpd
  454 ?        S      0:00 httpd
  455 ?        S      0:00 httpd      
 454 ?        S      0:00 httpd
  455 ?        S      0:00 httpd
  456 ?        S      0:00 httpd
  457 ?        S      0:00 httpd
  458 ?        S      0:00 httpd
  459 ?        S      0:00 httpd
  473 ?        S      0:00 xfs -droppriv -daemon -port -1
  511 tty1     S      0:00 login -- root
  512 tty2     S      0:00 /sbin/mingetty tty2
  513 tty3     S      0:00 /sbin/mingetty tty3
  514 tty4     S      0:00 /sbin/mingetty tty4
  515 tty5     S      0:00 /sbin/mingetty tty5
  516 tty6     S      0:00 /sbin/mingetty tty6
  519 tty1     S      0:00 -bash
  565 tty1     S      0:00 supervise /var/supervise/qmail/send /var/qmail/rc
  566 tty1     S      0:00 cyclog /var/log/qmail
  567 tty1     S      0:00 supervise /var/supervise/qmail/smtpd tcpserver -v -x/
  568 tty1     S      0:00 accustamp
  569 tty1     S      0:00 cyclog /var/log/qmail/smtpd
  570 tty1     S      0:00 tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup ma
  571 tty1     S      0:00 /var/qmail/bin/splogger pop3d
  572 tty1     S      0:00 tcpserver -v -x/etc/tcp.smtp.cdb -u504 -g503 0 smtp /
  573 tty1     S      0:00 qmail-send
  576 tty1     S      0:00 accustamp   
  577 tty1     S      0:00 qmail-lspawn ./Maildir/
  578 tty1     S      0:00 qmail-rspawn
  579 tty1     S      0:00 qmail-clean
  747 ?        R      0:00 in.telnetd
  748 pts/0    S      0:00 login -- john
  749 pts/0    S      0:00 -bash
  762 pts/0    S      0:00 su
  763 pts/0    S      0:00 bash
  766 ?        S      0:00 in.identd -e -o
  767 ?        S      0:00 in.identd -e -o
  768 ?        S      0:00 in.identd -e -o
  769 ?        S      0:00 in.identd -e -o
  770 ?        S      0:00 in.identd -e -o
  771 ?        S      0:00 in.identd -e -o
  772 ?        S      0:00 in.identd -e -o
  773 ?        S      0:00 in.identd -e -o
  774 ?        S      0:00 in.identd -e -o
  775 ?        S      0:00 in.identd -e -o
  776 ?        S      0:00 in.identd -e -o
  785 tty1     S      0:00 /var/qmail/bin/qmail-popup mail.dnet.com.sg /bin/chec
  787 pts/0    R      0:00 ps -ax      
 
Could anyone help me out. I am a newbie and want to set it up and am wondering what could go wrong
 
Its very urgent as I need to get the server up by tomorrow the latest.
 
Thanks for your help in advance.
 
John Francis
 
 
 






Hi to all!
Sorry about this question but I can't locate the message regarding this
one in my archive of qmail emails.

I get this "..no mailbox here by that name" messages when sending an email
to a local account. This account exists alright but why doesn't qmail
recognize it?

Thanks again! 



Regards,

Edward Castillo Jakosalem






On Mon, Nov 15, 1999 at 07:55:45PM +0800, Edward Castillo-Jakosalem wrote:
> 
> 
> Hi to all!
> Sorry about this question but I can't locate the message regarding this
> one in my archive of qmail emails.
> 
> I get this "..no mailbox here by that name" messages when sending an email
> to a local account. This account exists alright but why doesn't qmail
> recognize it?

How is your domain configurated? 

do a "grep '' /var/qmail/control/*" and post the output, please.

/magnus

--
MOST useless 1998 * http://x42.com/




On Mon, Nov 15, 1999 at 01:03:22PM +0100, Magnus Bodin wrote:
> On Mon, Nov 15, 1999 at 07:55:45PM +0800, Edward Castillo-Jakosalem wrote:
> > 
> > 
> > Hi to all!
> > Sorry about this question but I can't locate the message regarding this
> > one in my archive of qmail emails.
> > 
> > I get this "..no mailbox here by that name" messages when sending an email
> > to a local account. This account exists alright but why doesn't qmail
> > recognize it?
> 

A common cause for that are wrong permissions in the user's home. Check if it's owned 
by that user, and if it's not world-writeable.

                                        Regards;
                                                Ricardo

-- 
+-------------------
| Ricardo Cerqueira  -  [EMAIL PROTECTED]
| PGP Key fingerprint  -  B7 05 13 CE 48 0A BF 1E  87 21 83 DB 28 DE 03 42 
| FCCN/RCCN  -  Fundacao para a Computacao Cientifica Nacional 
| Av. Brasil, 101 / 1700-066 Lisboa / Portugal *** Tel: (+351) 218440100




Here it is:

/var/qmail/control/concurrencylocal:20
/var/qmail/control/concurrencyremote:100
/var/qmail/control/defaultdomain:access.net.ph
/var/qmail/control/locals:localhost
/var/qmail/control/locals:access2.access.net.ph
/var/qmail/control/locals:qmail.access.net.ph
/var/qmail/control/locals:doods.com
/var/qmail/control/me:access2.access.net.ph
/var/qmail/control/plusdomain:net.ph
/var/qmail/control/rcpthosts:localhost
/var/qmail/control/rcpthosts:access2.access.net.ph
/var/qmail/control/rcpthosts:qmail.access.net.ph
/var/qmail/control/rcpthosts:super.net.ph
/var/qmail/control/rcpthosts:access2.access.net.ph
/var/qmail/control/rcpthosts:access1.access.net.ph
/var/qmail/control/rcpthosts:access.net.ph
/var/qmail/control/rcpthosts:doods.com
/var/qmail/control/smtpgreeting:WELCOME TO ACCESS2'S QMAIL!!!
/var/qmail/control/virtualdomains:doods.com:doods.com


Magnus Bodin wrote:

> On Mon, Nov 15, 1999 at 07:55:45PM +0800, Edward Castillo-Jakosalem wrote:
> >
> >
> > Hi to all!
> > Sorry about this question but I can't locate the message regarding this
> > one in my archive of qmail emails.
> >
> > I get this "..no mailbox here by that name" messages when sending an email
> > to a local account. This account exists alright but why doesn't qmail
> > recognize it?
>
> How is your domain configurated?
>
> do a "grep '' /var/qmail/control/*" and post the output, please.
>
> /magnus
>
> --
> MOST useless 1998 * http://x42.com/

--

Edward Castillo-Jakosalem






On Mon, Nov 15, 1999 at 08:26:39PM +0800, Edward Castillo-Jakosalem wrote:
> Here it is:
> 
> /var/qmail/control/concurrencylocal:20
> /var/qmail/control/concurrencyremote:100
> /var/qmail/control/defaultdomain:access.net.ph
> /var/qmail/control/locals:localhost
> /var/qmail/control/locals:access2.access.net.ph
> /var/qmail/control/locals:qmail.access.net.ph
> /var/qmail/control/locals:doods.com
> /var/qmail/control/me:access2.access.net.ph
> /var/qmail/control/plusdomain:net.ph
> /var/qmail/control/rcpthosts:localhost
> /var/qmail/control/rcpthosts:access2.access.net.ph
> /var/qmail/control/rcpthosts:qmail.access.net.ph
> /var/qmail/control/rcpthosts:super.net.ph
> /var/qmail/control/rcpthosts:access2.access.net.ph
> /var/qmail/control/rcpthosts:access1.access.net.ph
> /var/qmail/control/rcpthosts:access.net.ph
> /var/qmail/control/rcpthosts:doods.com
> /var/qmail/control/smtpgreeting:WELCOME TO ACCESS2'S QMAIL!!!
> /var/qmail/control/virtualdomains:doods.com:doods.com


You are violating the number 1 rule, that a domain (doods.com in this case)
are not allowed to appear BOTH in virtualdomains and in locals. 

But the host should be able to receive and deliver mail for e.g. 

[EMAIL PROTECTED]

I cannot find an MX record for doods.com in the DNS either, but on the other
hand a NS for doods.com is not in a root-dns-server near me.

Ergo: Both dns and configuration problem.

/magnus




I just upgraded my email server from RedHat 5.2 to RedHat 6.1, I have
several virtual domains plus some local users, and qmail is WORKING FINE
EXCEPT two things (that were working before the upgrade)...

1) splogger stopped working:
The statement      echo test|/var/qmail/bin/splogger qmail
yields nothing in the /var/log/maillog file.  The only things in this log
are ipop3d messages.  The contents of my /etc/syslog.conf are listed at the
end of this email (and use TABs for white space rather than spaces as is
required).

2) Message logging stopped working: 
I had been getting some complaints about bounces several months ago, so I
implemented message logging.  From the FAQ: "Set QUEUE_EXTRA to "Tlog\0"
and QUEUE_EXTRALEN to 5 in extra.h.  Recompile qmail. Put ./msg-log into
~alias/.qmail-log."  This plain stopped working.  I have included the
/etc/rc.d/init.d/qmail script and the line from /etc/inetd.conf for qmail
at the end of this email.

I've spent the past two days searching the list archives and the web for
any incompatibilities with RedHat 6.1, and had not found any.  I did see
some insignificant changes to /etc/syslog.conf had fixed a similar problem
for someone, so I tried that, and it did not work (switched mail.* and
mail.none lines)

Any assistance is GREATLY appreciated.
Troy.

(Below are the scripts referenced above)

=========================

# more syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.*                                                 /dev/console

# Log all the mail messages in one place.
mail.*                                                  /var/log/maillog

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none                          /var/log/messages

# The authpriv file has restricted access.
authpriv.*                                              /var/log/secure


# Everybody gets emergency messages, plus log them on another
# machine.
*.emerg                                                 *

# Save mail and news errors of level err and higher in a
# special file.
uucp,news.crit                                          /var/log/spooler

# Save boot messages also to boot.log
local7.*                 

==============================

# grep qmail inetd.conf
smtp    stream  tcp     nowait  qmaild  /usr/sbin/tcpd
/var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd

==================================

# more /etc/rc.d/init.d/qmail
echo -n "Starting qmail: "
### removed 13-nov-99 in an attempt to fix timezone entry into log (or just
do something different to try to get it working).
#env - PATH="/var/qmail/bin:$PATH" \
#csh -cf 'qmail-start ./Mailbox splogger qmail &'

env - PATH="/var/qmail/bin:$PATH" TZ=CST6CDT \
qmail-start ./Mailbox splogger qmail &

echo
sync

=================================

###





> 
> With all the recent discussion about aggregating RCPTs for the same MX,
> I took a look at qmail's code.
> 
> It became clear quite fast that general aggregation was quite impossible
> given the architecture.

Especially since the it's quite possible for the same machine to exist in
the MX record sets of more that one recipient address, but with a different
preference value.

> What is feasible is this : for a given message, aggregate by
> domain. I.e, a mail to
>               [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
>                       [EMAIL PROTECTED], [EMAIL PROTECTED]
> can be dispatched as three mails,
> one to                [EMAIL PROTECTED], [EMAIL PROTECTED]
> one to                [EMAIL PROTECTED], [EMAIL PROTECTED]
> and one to    [EMAIL PROTECTED]
> 
> As it stands, most of qmail's architecture happily keeps all the
> recipients together. qmail-smtpd, qmail-inject and qmail-queue deal with
> a multi-RCPT message as one entity ; qmail-remote can send a single mail
> to multiple recipients on the same mailhost. Only qmail-send and
> qmail-rspawn are special-cased : qmail-rspawn is designed to only accept
> one recipient, and of course qmail-send actually does the breaking up.

This assumes that the recieving MTA will process multiple RCPT messages
in exactly the same way as those with a single RCPT. e.g. the MTA might
impose progressive delays in the transaction for every RCPT given to it
or attempt to deliver a message with multiple RCPT's at a lower priority.

Since the usual case is likely to be one RCPT it makes sense for recieving
MTA's to optimise for this case. (Also to treat messages with large numbers
of RCPT's as potential spam.)

Also you must handle the case where the the receiving MTA says "no more
RCPT's please".

-- 
Mark Evans
St. Peter's CofE High School
Phone: +44 1392 204764 X109
Fax: +44 1392 204763




On Mon, 15 Nov 1999, Mark Evans wrote:

> This assumes that the recieving MTA will process multiple RCPT messages
> in exactly the same way as those with a single RCPT. e.g. the MTA might
> impose progressive delays in the transaction for every RCPT given to it
> or attempt to deliver a message with multiple RCPT's at a lower priority.

This is silly.  Originally, batching multiple RCPTs for the same domain
WAS the default behavior of all the MTAs on the Internet.

> Since the usual case is likely to be one RCPT it makes sense for recieving
> MTA's to optimise for this case. (Also to treat messages with large numbers
> of RCPT's as potential spam.)

Nope.  The "usual" case is a mail server that batches multiple RCPTs
together.  That's the way most mail servers work.  Qmail is an exception.

> Also you must handle the case where the the receiving MTA says "no more
> RCPT's please".

An appropriate RFC specifies the minimum number of RCPTs that are
permissible.  The limit is sufficient enough in most cases.

--
Sam





Sam writes:
 > On Mon, 15 Nov 1999, Mark Evans wrote:
 > 
 > > This assumes that the recieving MTA will process multiple RCPT messages
 > > in exactly the same way as those with a single RCPT. e.g. the MTA might
 > > impose progressive delays in the transaction for every RCPT given to it
 > > or attempt to deliver a message with multiple RCPT's at a lower priority.
 > 
 > This is silly.  Originally, batching multiple RCPTs for the same domain
 > WAS the default behavior of all the MTAs on the Internet.

And just exactly what evidence do you base this unfounded conclusion on?
Please enumerate the MTA's which had this "orogonal" behavior and what
period of time they existed.  Make sure that you are not able to name a
single counter-example for that time period, otherwise your statement is
a blatant lie.

/Joe




On 16 Nov 1999, Joe Kelsey wrote:

> Sam writes:
>  > On Mon, 15 Nov 1999, Mark Evans wrote:
>  > 
>  > > This assumes that the recieving MTA will process multiple RCPT messages
>  > > in exactly the same way as those with a single RCPT. e.g. the MTA might
>  > > impose progressive delays in the transaction for every RCPT given to it
>  > > or attempt to deliver a message with multiple RCPT's at a lower priority.
>  > 
>  > This is silly.  Originally, batching multiple RCPTs for the same domain
>  > WAS the default behavior of all the MTAs on the Internet.
> 
> And just exactly what evidence do you base this unfounded conclusion on?

A little program called "sendmail".  Perhaps you've heard of it.

> Please enumerate the MTA's which had this "orogonal" behavior and what
> period of time they existed.

RFC 821 is dated...  Aug 13, 1982.  Sendmail was actually born way before
then, but it should be pretty safe to state that, on that date, SMTP as we
know it was the de-facto standard for E-mail delivery on what we now call
the Internet, with sendmail hauling, pretty much, 100% of the traffic.

--
Sam





Sam writes:
 > On 16 Nov 1999, Joe Kelsey wrote:
 > 
 > > Sam writes:
 > >  > On Mon, 15 Nov 1999, Mark Evans wrote:
 > >  > 
 > >  > > This assumes that the recieving MTA will process multiple RCPT messages
 > >  > > in exactly the same way as those with a single RCPT. e.g. the MTA might
 > >  > > impose progressive delays in the transaction for every RCPT given to it
 > >  > > or attempt to deliver a message with multiple RCPT's at a lower priority.
 > >  > 
 > >  > This is silly.  Originally, batching multiple RCPTs for the same domain
 > >  > WAS the default behavior of all the MTAs on the Internet.
 > > 
 > > And just exactly what evidence do you base this unfounded conclusion on?
 > 
 > A little program called "sendmail".  Perhaps you've heard of it.

When sendmail was first written it did *not* do RCPT aggregation.

That was implemented later, as an optimization.

In 1982 sendmail was by far and away in the *minority* of MTA's in
operation on the Internet.

The rapid spread of 4.2BSD UNIX systems (1983) soon changed that.

/Joe




Joe Kelsey writes:
 > In 1982 sendmail was by far and away in the *minority* of MTA's in
 > operation on the Internet.

Hence the enshrinement of Tenex's CRLF in RFC821 instead of Unix's
newline (what a botch that was).

-- 
-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 Sun, Nov 14, 1999 at 09:53:58PM +0000, Frederik Lindberg wrote:
> > > It became clear quite fast that general aggregation was quite impossible
> > > given the architecture.
> > 
> > Note that this is due to the architecture of both qmail and SMTP.  One
> > of the problems with aggregation when using qmail is VERPs which change
> > the envelope sender based on the destination address.  This requires
> > that each recipient be delivered seperately when using SMTP, and I am
> > aware of no protocol that can deal with this adequately, never mind a
> > MTA that can handle it.
> 
> QMTP would work fine. The VERP would be generated at the host translating
> the QMTP message to SMTP messages (or local delivery). QMQP as well. Thus,
> if you aggregate or a QMQP/QMTP server, you just leave the envelope sender
> alone.

This, of course, presumes that all QMQP/QMTP servers are going to
support VERPs identically to qmail.  Of course, this is a safe
assumption right now since the only QMQP/QMTP servers run qmail.  The
QMTP spec itself does not appear to deal with the issue of VERPs.

The most general solution (that I was thinking of when I said that no
protocol was adequate) is to allow each message to be sent with an
envelope that consists of a list of _pairs_ of sender and recipient
addresses, but this is overkill if all you want is VERPs.
-- 
Bruce Guenter <[EMAIL PROTECTED]>                       http://em.ca/~bruceg/




On Mon, 15 Nov 1999 [EMAIL PROTECTED] wrote:

> On Sun, Nov 14, 1999 at 10:01:29PM +0100, Nagy Balazs wrote:
> 
> >  The only record in the internet DNS
> > zone have to be an MX record for your autoturn server.
> 
> Could you kindly give an example

It seems the problem is solved now:
;; ANSWER SECTION:
col7.metta.lk.          17h46m59s IN MX  10 metta.lk.
col7.metta.lk.          16h53m38s IN NS  server1.tradenetsl.lk.
col7.metta.lk.          16h53m38s IN NS  dhamma.metta.lk.

The problem was an A record which pointed a 172.16.x.x address.

> > I'm sorry but the question shows you missed the point.
> 
> Sorry to be dumb, but I do not quite understand what I have missed,
> Kindly explain or direct me to a paper.

The problem was the A record.  Other MTAs searched a dns record about your
host, and they found an A record.  Maybe an MX record too.  Then they
happily tried to send to the A record's address, but every modem filters
local IPs out from the public network, and MTAs got no route to network (or
no route to host) error.
-- 
Regards: Kevin (Balazs) @ synergon





On Sun, Nov 14, 1999 at 02:37:00PM -0700, [EMAIL PROTECTED] wrote:

> Instead of speculating, why don't you run "vmstat 1" and inject a
> 10 MB message?  You should be able to tell quickly if you are
> running out of memory.

I have a little more powerfull system (K6 200, 128Mb, no swap) and did just
that. 3 messages, 80 Mb binary, to myself. My load is 3.16 at the moment,
and I'm typing this message while qmail is churning away at over 300Mb of
mail on a system without swap. 

I can type this message without problems, delay between typing and character
appearing in Eterm is noticable, but minimal. Did I mention I've got X
running, with a bunch of apps?

Load peaked at 3.50, and is decreasing now. The first message has arrived,
in a minute or two, and I expect the other to finish within seconds.

Let's send this baby out before everything is done, just for fun.

  1:54pm  up 10 days, 17:38,  3 users,  load average: 2.58, 2.51, 1.34

qmaill    1207  0.0  0.0  1128   84 ?        S    Nov04   0:00 cyclog 
qmails    1211  0.0  0.1  1164  172 ?        S    Nov04   0:02 qmail-send
qmaill    1226  0.0  0.0  1112   68 ?        S    Nov04   0:00 accustamp
qmaill    1227  0.0  0.0  1128   72 ?        S    Nov04   0:00 cyclog 
qmaild    1228  0.0  0.0  1380  112 ?        S    Nov04   0:00 tcpserver
qmaill    1252  0.0  0.0  1112   80 ?        S    Nov04   0:00 accustamp qmail
root      1253  0.0  0.0  1132  120 ?        S    Nov04   0:01 qmail-lspawn
qmailr    1254  0.0  0.0  1132   76 ?        S    Nov04   0:00 qmail-rspawn
qmailq    1255  0.0  0.0  1124   88 ?        S    Nov04   0:00 qmail-clean
ruben    32544  0.1  0.2  1140  364 ?        S    13:54   0:00 bin/qmail-local
ruben    32545 34.0  0.1  1140  248 ?        R    13:54   0:03 bin/qmail-local 


-- 

Ruben




I need an urgent solution using Amavis and Qmail on Linux.

I have had a look at the patches that Christopher Seawood
<[EMAIL PROTECTED]>  has supplied but I get errors.
Has anyone successfully applied these patches?
 I get a "malformed header on line 5"
( # - if "do_log" is set to "yes"                #)

------  Found this from the archives  -----

On Thu, 28 Oct 1999, Gordon Smith wrote:

> If anyone has had any success with Amavis, I'd be interested to see
how you did
> it. With the latest (pre6) qmail passes the message to the script,
which checks
> the message for viruses, but the script never passes the message back.
Aargh! I
> get a "no local delivery program available" error.
> I think that basename is not returning the calling program id
correctly, but
> I'm not sure. If anyone has already fixed this, please let me know.
Otherwise
> I'll post a fix here once I figure out whats going on  :-)

The default qmail setup for amavis was slightly horked.  You'll need to
apply the attached patch & configure it with: --enable-qmail
--enable-x-header=no.  Once you have it installed, do:

cd /var/qmail/bin
mv qmail-remote qmail-remote-real
mv qmail-local qmail-local-real
ln -s /usr/sbin/scanmails qmail-remote
ln -s /usr/sbin/scanmails qmail-local

This will allow you to scan all incoming and outgoing mail for viruses.
If you do not feel comfortable moving the binaries around, you can just
add:
| /usr/sbin/scanmails $SENDER $RECEIPIENT
to /var/qmail/defaultdelivery/rc .

The attached patch fixes the following problems:

1. Should check $sender & $receiver against $SENDER & $RECEIPIENT
instead
of $2 & $7.
2. Do not attempt to log to the logfile if $do_log != 'yes'.
3. Since qmail doesn't use the default $deliver program, do not check
for
$deliver when attempting to pass on the mail.

I'm not sure why using formail to add the X-AntiVirus: header doesn't
work so always I disabled it.  I think the proper step may be to
reinvoke
qmail-inject but I'm not sure how that would work.

- cls


--- amavis-0.2.0-pre6/src/scanmails/scanmails.in.cls    Tue Jul 20
12:28:52 1999
+++ amavis-0.2.0-pre6/src/scanmails/scanmails.in        Mon Oct 25
13:16:01 1999
@@ -103,6 +103,7 @@
 # - if "do_log" is set to "yes"                #
 ################################################
 var_log=@var_log@
+systemlogdir=${var_log}/scanmails/
 do_log=@do_log@
 do_syslog=@do_syslog@
 syslog_level=@syslog_level@
@@ -242,11 +243,11 @@
 receiver=`echo ${RECEIPIENT} | ${sed} -e "s/[\\\`\\\\\$\(\)]//g"`
 sender=`echo ${SENDER} | ${sed} -e "s/[\\\`\\\\\$\(\)]//g"`
<snip>
------ End ------





> john wrote:
> 
> Hi,
> 
> I setup everything and i managed to start the tcpserver and pop3d in
> RH6.1 but I don't seem to be
> receiving mails in the maildirectory which is under
> /home/vpopmail/users/
> 
> Should I install ezmlm and also autorespond so that it works fine ?
>


Depends where your users and virtual domain users are. 

Did you add any? How did you do it?

What do your smtp and pop3 startup lines look like?

Ken Jones
Inter7




"john" <[EMAIL PROTECTED]> wrote:

>I finally managed to get the TCPSERVER running in my Qmail. But there
>is one thing that everyone should note. The script in the website and
>what is given in Dave Sills hardcopy is different.

I just diff'ed them, and they're identical.

Note that you might need to strip carriage returns added by the
InfoAve web server. If you do:

    head -1 qmail-script.txt |od -c

And you get:

0000000   #   !   /   b   i   n   /   s   h  \r  \n
0000013

(Note the \r.)

Then you need to do:

    tr -d '\015' <qmail-script.txt >foo
    mv foo qmail-script.txt

I'll add a note about this to LWQ.

-Dave




"john" <[EMAIL PROTECTED]> wrote:

>I started TCPSERVER AND POP3D services But I don't seem to receive
>mails.

You mean they're nto showing up in your Maildir/new, or you're not
able to retrieve them via POP? Big difference.

>Look at my processes running and let me know why
>
> PID TTY      STAT   TIME COMMAND
>  570 tty1     S      0:00 tcpserver -v -R 0 pop-3 /var/qmail/bin/qmail-popup ma

That "ma" at the end of the line looks suspicious. It should be "Ma",
if you're specifying "Maildir" on the command line. (An old version of 
LWQ had a typo showing "maildir" there.)

-Dave





Howdy.  We've been successfully and happily running qmail for a while
now.  This weekend we upgraded our system from FreeBSD 2.2.8 to FreeBSD
3.3.  Since the upgrade (which went smoothly, thanks), the qmail-send
process has been constantly running "at full steam", taking up as much CPU
time as it can get.

USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED      TIME COMMAND
qmails   12849 95.6  0.8   820  464  p6  R    11:57AM 1234:39.21 qmail-send

It's not really *doing* anything, though.  There's very low mail volume,
no repeating SMTP connections, and generally nothing to do.  So I can't
figure out why it's running in that manner.  

I realize this could be fixed with a call to ulimit in the rc file, but I
hope to understand the problem before fixing it like that, especially
since it's never behaved this way before.

Any ideas?

Thanks,
Chris

-- Chris Hardie -----------------------------
----- mailto:[EMAIL PROTECTED] ----------
-------- http://www.summersault.com/chris/ --





On Mon, Nov 15, 1999 at 09:47:05AM -0500, Chris Hardie wrote:
> USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED      TIME COMMAND
> qmails   12849 95.6  0.8   820  464  p6  R    11:57AM 1234:39.21 qmail-send

What does

        # cd /var/tmp; ktrace -p 12849; sleep 10; ktrace -C; kdump | less

say about what qmail-send is doing?

(Don't forget to ``rm /var/tmp/ktrace.out'' afterwards.)

I have a feeling that you will need to do

        rm -f `cat TARGETS`
        make
        make setup check

in the qmail source directory

(or ``cd /usr/ports/mail/qmail; make deinstall reinstall clean'' if you are
using the port.)

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




I have a couple of scripts that you may or may not find useful. The first,
'archive-maillogs' runs once an hour out of cron. (Adjust the time for the
business of your server.) When invoked as:

  /usr/local/bin/archive-maillogs /var/log/qmail

it will process all completed logfiles in /var/log/qmail and stick them in
/usr/local/logs/qmail-$MONTH.gz. All processed logs will be deleted. It can
also be used to split a master logfile; if you have
'/var/log/archive/qmail-10' as a huge logfile of all October qmail logs, you
can invoke:

  /usr/local/bin/archive-maillogs /var/log/archive

(provided qmail-10 is the only logfile in there) to split the logs into
by-day logfiles. (Our monthly logs were between 100-200MB gzip'd, which was
totally unusable.)

The second script, 'process-maillogs', is run once per day (here, at
12:15am). This mails a report on RBL hits, DUL hits, and overall stats (from
qmailanalog). This one is probably not as useful for people not using these
services, but whatever.

If you have any questions about these scripts, please feel free to ask!

/pg
-- 
Peter Green
Gospel Communications Network, SysAdmin
[EMAIL PROTECTED]
#!/usr/bin/perl

my ( $archivedir,  # where to store archived logs
     $tailocal,    # where does tailocal reside?
     $gzip,        # where does gzip reside?
     $ext,         # file extension for archived logs
     $dir,         # name of dir we're processing
     $base,        # basename to archive log (qmail, qmail-smtpd, &c.)
     %to,          # hash of file handles
     $date,        # placeholder for log entry date
     @files,       # array of input file names
     $f,           # one file at a time...
   );

# stick all archived logs in this dir
$archivedir = "/usr/local/logs";

# use the first if you need to run the logfile through tailocal; the
# second if you don't
$tailocal = "/usr/local/bin/tailocal";
#$tailocal = "/bin/cat";

# COMPRESSION
# GZIP
$gzip = "/bin/gzip -9c";
$ext = ".gz";
# COMPRESS
#$gzip = "/usr/bin/compress -c";
#$ext = ".Z";
# NONE
#$gzip = "/bin/cat";
#$ext = "";

# get the directory from the command line
$dir = shift;
die "Invalid dir $dir: $!\n"
  if (!-d "$dir");

# get the base logname from the directory
#   if   dir  = /var/log/qmail
#   then base = qmail
$base = $2 if ($dir =~ /^(\/[^\/]+)+\/(.+)$/);
die "Can't determine base (got $base from $dir)\n"
  if ($base eq "" || $base =~ /\//);

# get a list of files in directory that do NOT have the
# user write permission bit on
opendir (D,$dir) || die "Can't open dir $dir: $!\n";
@files = grep { !((stat("$dir/$_"))[2] & 00200) } readdir(D);
closedir (D);

chdir "$dir" or die "Can't change to dir $dir: $!\n";

foreach $f (@files) {
  open (FROM,"/bin/cat $f | $tailocal |")
    or die "Can't open logfile: $!\n";
  while (<FROM>) {

    # slurp the date from the logfile; use it to split archive
    # logs based on date
    $date = $1 if (/^(.*?) /);
    $date =~ s/[^\d]//g;

    # if something's wrong, date will be '1969-12-31'; dump these
    if ($date !~ /^1969/) {

      # have we opened this file already? if not, open it and stick
      # the filehandle in our %to hash of filehandles
      if (!exists($to{$date})) {
        open (TO,"|$gzip >> $archivedir/$base-$date$ext")
          or die "Can't open archive: $!\n";
        $to{$date} = *TO;
      }

      # add the line to the logfile
      print { $to{$date} } $_;
    }
  }
  close FROM;
  unlink $f;
}
#!/usr/bin/perl

use strict;

$ENV{PATH} = "/bin:/usr/bin:/usr/local/bin:/usr/local/qmailanalog/bin";

my ( $RBLlist,    # big list of individual RBL offenses
     $DULlist,    # big list of individual DUL offenses
     %rbl,        # hash of RBL hosts, number of offenses
     %dul,        # hash of DUL hosts, number of offenses
     %dnscache,   # map IP => hostname
     $rcnt,       # total number of RBL offenses
     $dcnt,       # total number of DUL offenses
     $hostip,     # IP address of offending site
     $hostip2,    # second IP address for verification
     $hostname,   # hostname of offending site
     $pid,        # PID of process where offense occurred
     $pid2,       # second PID for verification
     $type,       # RBL or DUL?
     $now,        # today's date
     $then,       # last log to keep (e.g., 21 days ago)
     $thistime,   # timestamp of offense
     $logfile,    # name of log file to process
     $mailto,     # who shall I mail the report to?
     $dir,        # which directory are the logs in?
     $rbldulfile, # name of file to put individual RBL/DUL offenses
     $whoami,     # userID running the script
     $whereami,   # host where the script is running
   );

$RBLlist = "";
$DULlist = "";
%rbl = ( );
%dul = ( );
%dnscache = ( );
$rcnt = $dcnt = 0;
$dir = "/usr/local/logs";
$rbldulfile = "rbldul";
$mailto = "pcg\@gospelcom.net";
chomp ($whoami = `whoami`);
chomp ($whereami = (split /\./,`hostname`)[0]);

chdir "$dir"
  or die "Can't change to dir $dir: $!\n";

#chomp ($now = `date +"%Y%m%d"`);
chomp ($now = `date +"%Y%m%d" --date="1 day ago"`);
#$now = "19991108";
open (F,"gzip -dc qmail-smtpd-$now.gz |")
  or die "Can't open logfile qmail-smtpd-$now.gz: $!\n";

while (<F>) {
  if (/tcpserver: ok (\d+) [\w\:\.]+ ([\w\-\.]*):(\d+(\.\d+){3}):/) {
    $pid = $1;
    $hostname = $2;
    $hostip = $3;
  }
  elsif (/(\d+:\d+:\d+).+ rblsmtpd: pid (\d+): 451 (S|B)/) {
    $thistime = $1;
    $pid2 = $2;
    $type = $3;
    if ($pid == $pid2) {
      $thistime =~ s/[^\d]//g;
      $hostip .= " " while (length($hostip) < 15);
      $dnscache{$hostip} = $hostname unless (exists($dnscache{$hostip}));
      if ($type eq "B") {
        $rcnt++;
        $hostip2 = (split '\?')[1];
        $hostip2 =~ s/[^0-9\.]//g;
        if ($hostip == $hostip2) {
          $RBLlist .= "RBL  $thistime $hostip ($hostname)\n";
          if (exists($rbl{$hostip})) {
            $rbl{$hostip}++;
          } else {
            $rbl{$hostip} = 1;
          }
        }
        else {
          # $hostip != $hostip2; something's wrong; skip
        }
      }
      else { # $type eq "S"
        $DULlist .= "DUL  $thistime $hostip ($hostname)\n";
        $dcnt++;
        if (exists($dul{$hostip})) {
          $dul{$hostip}++;
        }
        else {
          $dul{$hostip} = 1;
        }
      }
    }
    else {
      # $pid != $pid2; something's wrong; skip
    }
  }
  else {
    # ignore this line
  }
}
close F;

# open mail pipe
open (MAIL,"|/var/qmail/bin/sendmail -t")
  or die "Can't mail: $!\n";
select (MAIL);

# print mail headers
print "From: $whoami\@$whereami\n";
print "To: $mailto\n";
print "Subject: Failed relays on $whereami for $now\n\n";

# Print overall summary
open (SUM,"gzip -dc qmail-$now.gz | localtai | matchup | zoverall |")
  or die "Can't produce summary: $!\n";
print while (<SUM>);
close SUM;

print "\n*************\n\n";

# Print RBL/DUL summaries
print "Summary of DUL Offenses ($dcnt total):\n";
printf "%4s %-15s %8s\n", "Off.", "Host IP", "Hostname";
foreach (sort {$dul{$b} <=> $dul{$a}} keys %dul) {
  printf "%-4d %-15s (%s)\n", $dul{$_}, $_, $dnscache{$_};
}
print "\n";
print "Summary of RBL Offenses ($rcnt total):\n";
printf "%4s %-15s %8s\n", "Off.", "Host IP", "Hostname";
foreach (sort { $rbl{$b} <=> $rbl{$a} } keys %rbl) {
  printf "%-4d %-15s (%s)\n", $rbl{$_}, $_, $dnscache{$_};
}
print "\n";
print "See $whereami:$dir/$rbldulfile-$now.gz for individual listings.\n";

# all done; mail it off
close MAIL;

# let's not mail the (mostly useless) individual offenses; just
# archive 'em in a file
open (RBLDUL,"|gzip -9c > $rbldulfile-$now.gz")
  or die "Cannot create RBL/DUL file: $!\n";
select (RBLDUL);

# Print individual offenses
print "Listing of Individual Offenses:\n";
printf "%4s %6s %15s %s\n", "Type", "Time", "Host IP", "Hostname";
print $DULlist;
print "\n";
print $RBLlist;

# close it up
close RBLDUL;
select (STDOUT);

# remove the archived log and RBL/DUL file from 21 days ago
chomp ($then = `date +"%Y%m%d" --date="21 days ago"`);
unlink "qmail-smtpd-$then.gz","$rbldulfile-$then.gz","qmail-$then.gz";
#print "unlinking qmail-smtpd-$then $rbldulfile-$then qmail-smtpd-$then\n";




What do you guys do when you find an open relay?
(I already sent a message to postmaster with no response)

Is there a forum to report this?

I just got spammed through mailadm.gdl.up.mx.  My relay attempt is:

telnet mailadm.gdl.up.mx 25
Trying 192.100.179.1...
Connected to mailadm.gdl.up.mx.
Escape character is '^]'.
220 mailadm.gdl.up.mx ESMTP Sendmail 8.9.3/8.8.8; Mon, 15 Nov 1999
09:18:39 -0600 (CST)
mail from: [EMAIL PROTECTED]
r250 [EMAIL PROTECTED] Sender ok
rcpt to: [EMAIL PROTECTED]
250 [EMAIL PROTECTED] Recipient ok
data
354 Enter mail, end with "." on a line by itself
To: [EMAIL PROTECTED]
Subject: open relay

test
.
250 JAA20164 Message accepted for delivery
quit
221 mailadm.gdl.up.mx closing connection
Connection closed by foreign host.

Apology for offtopic.

Mate




On Mon, Nov 15, 1999 at 09:28:17AM -0600, Mate Wierdl wrote:
> What do you guys do when you find an open relay?
> (I already sent a message to postmaster with no response)

I usually let the upstream connectivity provider know aswell.

james
-- 
James Raftery (JBR54) - Programmer Hostmaster   IE Domain Registry
Preferred Contact by Email: [EMAIL PROTECTED]   UCD Computing Services
Web: http://www.domainregistry.ie/              Computer Centre
Tel: (+353 1) 7062375 Fax: (+353 1) 7062862     Belfield, Dublin 4, IE





> What do you guys do when you find an open relay?
> (I already sent a message to postmaster with no response)
> 
> Is there a forum to report this?

generally mail sent to postmaster go to a mailbox which is never checked,
some ppl even redirect those mails to /dev/null. try informing the root
about this... 

dd 





> 
> generally mail sent to postmaster go to a mailbox which is never checked,
> some ppl even redirect those mails to /dev/null. try informing the root
> about this... 
>
The staff at our installation tries to check postmaster mail, but with between 
1000 and 11000 Email usually in it, it takes a little while to wade through.

(and that builds up over only a couple of days)

Greg






I usually just cc postmaster and send mail to admin/abuse. It gets a response
more often that way I find. Or lookup the tech contact for the domain and ignore
postmaster.

Greg Moeller wrote:

> >
> > generally mail sent to postmaster go to a mailbox which is never checked,
> > some ppl even redirect those mails to /dev/null. try informing the root
> > about this...
> >
> The staff at our installation tries to check postmaster mail, but with between
> 1000 and 11000 Email usually in it, it takes a little while to wade through.
>
> (and that builds up over only a couple of days)
>
> Greg

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







On Mon, Nov 15, 1999 at 08:55:08PM +0200,
  dd <[EMAIL PROTECTED]> wrote:
> 
> > What do you guys do when you find an open relay?
> > (I already sent a message to postmaster with no response)
> > 
> > Is there a forum to report this?
> 
> generally mail sent to postmaster go to a mailbox which is never checked,
> some ppl even redirect those mails to /dev/null. try informing the root
> about this... 

If they aren't reading postmaster email, they probably aren't reading root
email (if there is even a root account) either.

I usually just report the server to the orbs.





> > generally mail sent to postmaster go to a mailbox which is never checked,
> > some ppl even redirect those mails to /dev/null. try informing the root
> > about this... 
> 
> If they aren't reading postmaster email, they probably aren't reading root
> email (if there is even a root account) either.


errm, again "generally" mail sent to root is fwd'ed to admin's account.
if not, this is a sign of carelessness to me.

love, peace and stuff,
dd





On Mon, 15 Nov 1999, Jos Backus wrote:

> I have a feeling that you will need to do
> 
>       rm -f `cat TARGETS`
>       make
>       make setup check
> 
> in the qmail source directory

This seems to have fixed things, thanks.

> What does
> 
>       # cd /var/tmp; ktrace -p 12849; sleep 10; ktrace -C; kdump | less
> 
> say about what qmail-send is doing?

It was basically this kind of "stuff" over and over again:

 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  select(0x9,0xbfbfde14,0xbfbfddf4,0,0xbfbfdde0)
 12849 qmail-send RET   select 1
 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  close(0x8)
 12849 qmail-send RET   close 0
 12849 qmail-send CALL  open(0x6070,0x4,0xbfbfdcc4)
 12849 qmail-send NAMI  "lock/trigger"
 12849 qmail-send RET   open 8
 12849 qmail-send CALL  stat(0x4262,0xbfbfdc60)
 12849 qmail-send NAMI  "todo"
 12849 qmail-send RET   stat 0
 12849 qmail-send CALL  open(0x4262,0x4,0xffffffff)
 12849 qmail-send NAMI  "todo"
 12849 qmail-send RET   open 9
 12849 qmail-send CALL  fstat(0x9,0xbfbfdc60)
 12849 qmail-send RET   fstat 0
 12849 qmail-send CALL  fcntl(0x9,0x2,0x1)
 12849 qmail-send RET   fcntl 0
 12849 qmail-send CALL  getdirentries(0x9,0x18000,0x1000,0x11174)
 12849 qmail-send RET   getdirentries 512/0x200
 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  select(0x9,0xbfbfde14,0xbfbfddf4,0,0xbfbfdde0)
 12849 qmail-send RET   select 1
 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  select(0x9,0xbfbfde14,0xbfbfddf4,0,0xbfbfdde0)
 12849 qmail-send RET   select 1
 12849 qmail-send CALL  gettimeofday(0xbfbfddb4,0)
 12849 qmail-send RET   gettimeofday 0
 12849 qmail-send CALL  getdirentries(0x9,0x18000,0x1000,0x11174)
 12849 qmail-send RET   getdirentries 0
 12849 qmail-send CALL  lseek(0x9,0,0,0,0)
 12849 qmail-send RET   lseek 0
 12849 qmail-send CALL  close(0x9)
 12849 qmail-send RET   close 0 

Primitive observation tells me it was something to do with the trigger
file and it's relationship with the upgrade kernel and system binaries,
but I'll leave the final analysis to the more qmail-knowledgable.

Thanks for your help.

Chris

-- Chris Hardie -----------------------------
----- mailto:[EMAIL PROTECTED] ----------
-------- http://www.summersault.com/chris/ --





On Mon, Nov 15, 1999 at 11:26:39AM -0500, Chris Hardie wrote:
> This seems to have fixed things, thanks.

Great.

> Primitive observation tells me it was something to do with the trigger
> file and it's relationship with the upgrade kernel and system binaries,
> but I'll leave the final analysis to the more qmail-knowledgable.

At one point I was seeing the exact same thing (I think it was after moving
the default system binary format from a.out to ELF). It had nothing to do with
the trigger perms (which is the usual culprit).  Rebuilding/reinstalling qmail
fixed things.

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




My boss would like me to find out if it is possible
to limit the number of incoming connections qmail will accept
to a specific number? Bandwidth is a huge issue here and incoming
smtp connections are sucking a lot of it. Unfortunatly we dont have
a lot of bucks to upgrade right now.. thus we need to figure out how
we can control incoming smtp connections.
 
Any ideas?
 
Thanks.. Mike




On Mon, Nov 15, 1999 at 11:54:29AM -0500, Michael Cunningham wrote:
> My boss would like me to find out if it is possible
> to limit the number of incoming connections qmail will accept 
> to a specific number? Bandwidth is a huge issue here and incoming
> smtp connections are sucking a lot of it. Unfortunatly we dont have
> a lot of bucks to upgrade right now.. thus we need to figure out how
> we can control incoming smtp connections. 
> 
> Any ideas? 

man tcpserver

/pg
-- 
Peter Green
Gospel Communications Network, SysAdmin
[EMAIL PROTECTED]




I am trying to set up a mailing list on one of the servers using qmail
and ezmlm packages. I have come to a point where in I have installed
qmail on the machine where I want the mailing list. I tested qmail using
qmail-inject and sendmail  and it can send mails from this machine. Now
this machine , lets call it A, is behind a firewall. I am just using
this machine to send mails and not to receive mails.  I have set the
sendmail.cf configuration as follows: I have only changed the relay line
as pointing to localhost. Now for some reason I cannot receive mails on
the same machine. I can send it to other locations. Could you point out
how the system might be configured in order of this to work . Any help
would be appreciated,

Thanks
Rohit









Michael Cunningham writes:
 > My boss would like me to find out if it is possible
 > to limit the number of incoming connections qmail will accept 
 > to a specific number? Bandwidth is a huge issue here and incoming
 > smtp connections are sucking a lot of it. Unfortunatly we dont have
 > a lot of bucks to upgrade right now.. thus we need to figure out how
 > we can control incoming smtp connections. 

If you reject incoming smtp connections, they'll just be back later,
and you'll be out the bandwidth it took to reject them in the first
place.  Unless you have a reason to believe that bandwidth later (as
in: hours later) is cheaper than bandwidth now, you'd do better to
accept the message the first time.

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




Thanks:) I guess I have a case of the monday morning stupids..

Mike

> > Any ideas? 
> 
> man tcpserver
> 
> /pg
> -- 
> Peter Green
> Gospel Communications Network, SysAdmin
> [EMAIL PROTECTED]
> 





Russell Nelson writes:

> Michael Cunningham writes:
>  > My boss would like me to find out if it is possible
>  > to limit the number of incoming connections qmail will accept 
>  > to a specific number? Bandwidth is a huge issue here and incoming
>  > smtp connections are sucking a lot of it. Unfortunatly we dont have
>  > a lot of bucks to upgrade right now.. thus we need to figure out how
>  > we can control incoming smtp connections. 
> 
> If you reject incoming smtp connections, they'll just be back later,
> and you'll be out the bandwidth it took to reject them in the first
> place.  Unless you have a reason to believe that bandwidth later (as
> in: hours later) is cheaper than bandwidth now, you'd do better to
> accept the message the first time.

Well, when you get suddenly hit with a crapload of connections from the
same source, dropping them makes a lot of sense.  Most MTAs will dutifully
try again later, at which point you hope you won't be as busy as you are
now.

tcpserver will, of course, limit the total number of sessions overall.  My
tcp daemon, assuming that I've correctly implemented asynchronous zombie
reaping, can also limit the maximum number of connections from the same C
block, or from the same IP address.  It is included in courier-IMAP, but
can perfectly function all by itself, replacing all of tcpserver's
functionality.

-- 
Sam





On Mon, 15 Nov 1999, Michael Cunningham wrote:

> Date: Mon, 15 Nov 1999 11:54:29 -0500
> From: Michael Cunningham <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Limiting incoming connections
> 
> My boss would like me to find out if it is possible
> to limit the number of incoming connections qmail will accept 
> to a specific number? Bandwidth is a huge issue here and incoming
> smtp connections are sucking a lot of it. Unfortunatly we dont have
> a lot of bucks to upgrade right now.. thus we need to figure out how
> we can control incoming smtp connections. 

limiting number of parallel incoming connections may reduce bandwith
used by incoming mail ( or may not ? ).

if you really want to limit bandwith usage, use 'bandwidth manager'. one I
know is 'DUMMYNET'. it can limit bandwith usage by a set of IP, or a set
of protocols .. 

-w-






I have several zillion machines here for which one is the mail delivery
system (it puts the mails into mboxes which are distributed by NFS).
Now the question: When I put unix.do.main into locals, will
hostXXX.unix.do.main be delivered locally or do I have to add
every single host in localsi ?

The latter would render qmail useless and in fact, this is the
main reason why I seek a replacement for sendmail (our setup
here is so horribly complicated that I still don't know if I
should touch it at all :-( )

-- 
Dipl. Inf. (FH) Aaron "Optimizer" Digulla     Tel: +41-1-229 27 18
"(to) optimize: Make a program faster by      EMail: [EMAIL PROTECTED]
improving the algorithms rather than by       
buying a faster machine."                     




Aaron Optimizer Digulla writes:
 > I have several zillion machines here for which one is the mail delivery
 > system (it puts the mails into mboxes which are distributed by NFS).
 > Now the question: When I put unix.do.main into locals, will
 > hostXXX.unix.do.main be delivered locally or do I have to add
 > every single host in localsi ?

Well, yes, if you use locals you do.  But you can use a wildcard in
virtualdomains, and forward the mail to the local host.

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




I now realized, I do not understand how rbl(smtpd) works. 

Is it correct to say that rblsmtpd checks the rbl database only for
the (most recently) connecting host?  In particular, suppose I run
rblsmtpd on A and I do not run it on B.  If I have a .qmail file on B,
with

mw@A

in it, and a spam is sent to this .qmail file from an rbl'd site, mw@A
will get the message.

Thx

Mate




On Mon, 15 Nov 1999, Mate Wierdl wrote:

> I now realized, I do not understand how rbl(smtpd) works. 
> 
> Is it correct to say that rblsmtpd checks the rbl database only for
> the (most recently) connecting host?  In particular, suppose I run
> rblsmtpd on A and I do not run it on B.  If I have a .qmail file on B,
> with
> 
> mw@A
> 
> in it, and a spam is sent to this .qmail file from an rbl'd site, mw@A
> will get the message.

Correct.  rblsmtpd checks the IP making the connection against the DNS
table and responds based on that lookup.  Inserting another host into the
chain that does not itself run rblsmtpd or equivalent means the check is
performed against the wrong host.

This is one of the main arguments AGAINST using a secondary MX.  They ALL
must use the same anti-spam measures or the anti-spam measures are
useless.

> 
> Thx
> 
> Mate
> 

---------------------------------
Timothy L. Mayo                         mailto:[EMAIL PROTECTED]
Senior Systems Administrator
localconnect(sm)
http://www.localconnect.net/

The National Business Network Inc.      http://www.nb.net/
One Monroeville Center, Suite 850
Monroeville, PA  15146
(412) 810-8888 Phone
(412) 810-8886 Fax





Hello,

I have done that, it works now, but the mail is delivered to
/var/mail...

How can I squeeze ./Mailbox in there somehow?

Thanks,
T

Sam wrote:
> 
> On Fri, 12 Nov 1999, Tristan Hannover wrote:
> 
> > Hello,
> >
> > I was curious if anyone uses maildrop (or equivalents) to sort incoming
> > mail to various folders (depending on subject, from, to), or even
> > rewrite various headers on demand.
> > And if so, would anyone please show me the correct to integrate maildrop
> > into qmail?  Maildrop's homepage shows its setup for sendmail, but makes
> > no references for qmail.
> >
> > I tried to use the procmail startup files, and when replaced procmail
> > with maildrop string (for piping incoming messages to it), my qmail no
> > longer receives any mail.
> 
> Use the startup command in Qmail's INSTALL, except replace ./Maildir with
> '| /usr/local/bin/maildrop', including the single quotes.




Tristan Hannover writes:

> Hello,
> 
> I have done that, it works now, but the mail is delivered to
> /var/mail...
> 
> How can I squeeze ./Mailbox in there somehow?

[root@ny root]# cat /etc/maildroprc
DEFAULT="./Maildir"
[root@ny root]# 

./Mailbox wil work just as well.  Alternatively, edit maildrop/config.h,
and stick it into the define for DEFAULT_DEF.  

-- 
Sam





Thanks for your awesome help!

One last question, how would I go about rewriting certain headers, (like
subject, etc)?

Thank you,
Tris

Sam wrote:
> 
> Tristan Hannover writes:
> 
> > Hello,
> >
> > I have done that, it works now, but the mail is delivered to
> > /var/mail...
> >
> > How can I squeeze ./Mailbox in there somehow?
> 
> [root@ny root]# cat /etc/maildroprc
> DEFAULT="./Maildir"
> [root@ny root]#
> 
> ./Mailbox wil work just as well.  Alternatively, edit maildrop/config.h,
> and stick it into the define for DEFAULT_DEF.
> 
> --
> Sam




On  0, Sam <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Nov 1999, Tristan Hannover wrote:
> 
> > Hello,
> > 
> > I was curious if anyone uses maildrop (or equivalents) to sort incoming
> > mail to various folders (depending on subject, from, to), or even
> > rewrite various headers on demand.
> > And if so, would anyone please show me the correct to integrate maildrop
> > into qmail?  Maildrop's homepage shows its setup for sendmail, but makes
> > no references for qmail.
> > 
> > I tried to use the procmail startup files, and when replaced procmail
> > with maildrop string (for piping incoming messages to it), my qmail no
> > longer receives any mail.  
> 
> Use the startup command in Qmail's INSTALL, except replace ./Maildir with
> '| /usr/local/bin/maildrop', including the single quotes.
> 
> 

Should this be the contents of ~/.qmail or some other file? I am having
the exact same problem. Curently, I am using "deliver-maildir", which has
no filtering capabilities.
 
Subba Rao
[EMAIL PROTECTED]
http://pws.prserv.net/truemax/




        Hi,

Is it possible to add a signature (static, dynamic via shell
script) to add to all outgoing emails through qmail ? I'm not
sure if this work would belong to qmail but it looks like.

kind regards,
        Markus

-- 
Markus Fischer,  http://josefine.ben.tuwien.ac.at/~mfischer/
EMail:         [EMAIL PROTECTED]
PGP Public  Key: http://josefine.ben.tuwien.ac.at/~mfischer/C2272BD0.asc
PGP Fingerprint: D3B0 DD4F E12B F911 3CE1  C2B5 D674 B445 C227 2BD0




On Mon, Nov 15, 1999 at 10:39:50PM +0100, [EMAIL PROTECTED] wrote:
> 
> Is it possible to add a signature (static, dynamic via shell
> script) to add to all outgoing emails through qmail ? I'm not
> sure if this work would belong to qmail but it looks like.

David Harris posted a suggestion patch too qmail-smtpd on the 
14th of September:

http://x42.com/qmail/patches/drh-outgoing-footer-qmail-smtpd.diff


/magnus

--
MOST useless 1998 * http://x42.com/




Davids patch was for a web site where you could control the 
format of the mail sent. It will add a plain footer text directly to the end of 
emails, 
so its only appropriate for mails that aren't using multipart mime,
are encoded using 7 (and perhaps 8) bit mime, and are of type text/plain.
(and probably some other restrictions as well).



-----Original Message-----
From: Magnus Bodin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 16 November 1999 05:05
Subject: Re: adding site-wide signatures to all outgoing emails ?


On Mon, Nov 15, 1999 at 10:39:50PM +0100, [EMAIL PROTECTED] wrote:
> 
> Is it possible to add a signature (static, dynamic via shell
> script) to add to all outgoing emails through qmail ? I'm not
> sure if this work would belong to qmail but it looks like.

David Harris posted a suggestion patch too qmail-smtpd on the 
14th of September:

http://x42.com/qmail/patches/drh-outgoing-footer-qmail-smtpd.diff


/magnus

--
MOST useless 1998 * http://x42.com/
________________________________________________________________________________
This message has been checked for all known viruses by the Star Screening System
http://academy.star.co.uk/public/virustats.htm


________________________________________________________________________________
This message has been checked for all known viruses by the Star Screening System
http://academy.star.co.uk/public/virustats.htm




>The "commands" in the dot-qmail are delivery instructions.
>qmail-local follows each instruction in turn.
>
>The lines are not chained together in some sort of pipe, so each line gets
>THE SAME MESSAGE.
>
>If you want to do piping, then do everything on one single line with pipes.

   So that means I can't do:
   |command .... |./Maildir/

   to write out to a maildir after some commands as the ./Maildir/ needs to
be on a line by itself.

   How could I do this instead?

   Thanks again.

   Geoff






Is it possible to configure qmail to not send multiple copies of the same
message if your name appears in two sets of aliases in /etc/aliases?
Andy

-
                +----- Andy ------- [EMAIL PROTECTED] -----+
                |   Great minds discuss ideas;                |
                |         Average minds discuss events;       |
                |               Small minds discuss people.   |
                +------ http://www.xmission.com/~bradipo -----+





I have sendmail working on my system but qmail wont work. Could you possibly
tell me why. When I do a ./config , the name of the machine is not a fully
qualified domain name but the sendmail works on that. Can anyone tell how and
what to configure for this?


Andy Bradford wrote:

> Is it possible to configure qmail to not send multiple copies of the same
> message if your name appears in two sets of aliases in /etc/aliases?
> Andy
>
> -
>                 +----- Andy ------- [EMAIL PROTECTED] -----+
>                 |   Great minds discuss ideas;                |
>                 |         Average minds discuss events;       |
>                 |               Small minds discuss people.   |
>                 +------ http://www.xmission.com/~bradipo -----+





On Mon, 15 Nov 1999, Rohit Khamkar wrote:

>I have sendmail working on my system but qmail wont work. Could you possibly
>tell me why. When I do a ./config , the name of the machine is not a fully
>qualified domain name but the sendmail works on that. Can anyone tell how and
>what to configure for this?
Thanks, but this has nothing to do with what I asked - not to mention the
fact that you sent it twice... :)  
Cheers.
Andy

-
                +----- Andy ------- [EMAIL PROTECTED] -----+
                |   Great minds discuss ideas;                |
                |         Average minds discuss events;       |
                |               Small minds discuss people.   |
                +------ http://www.xmission.com/~bradipo -----+





Andy Bradford writes:
 > Is it possible to configure qmail to not send multiple copies of the same
 > message if your name appears in two sets of aliases in /etc/aliases?

Yes: http://www.qmail.org/eliminate-dups .

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




Thus said Russell Nelson on Mon, 15 Nov 1999 22:12:42 EST:

> Andy Bradford writes:
>  > Is it possible to configure qmail to not send multiple copies of the same
>  > message if your name appears in two sets of aliases in /etc/aliases?
> 
> Yes: http://www.qmail.org/eliminate-dups .
Excellent... thanks.  I initially thought that it would be part of the 
fastforward package.
Andy
-- 
        +====== Andy ====== TiK: garbaglio ======+
        |    Linux is about freedom of choice    |
        +== http://www.xmission.com/~bradipo/ ===+






I trying to config qmail with webmin and the qmail module written by
Vyacheclav Ignatuk.
Setup/config of this module is easy and after this it's very easy with
the webmin interface to add/delete/change users/alias etc.
I change my startscripts to use the checkpoppasswd written/changed by
Paul Gregg.
Whatever i try i can't authenticate popusers with this checkpoppasswd.
When i change the entry in poppasswd with a test entry, testid/testpw,
explained in the "Single-UID based POP3 box HOWTO" i can validate the
testid user en read mail waiting in his Maildir.
The poppasswd files generated by the qmail webmin module produced a
different layout.
What's going wrong, checkpoppasswd/webmin-qmail module not the right
choise??

I've also test qmail setup with vpopmail en qmailadmin, works fine but i
like the webmin interface, very modular

greetings,
marco Leeflang





What command is supposed to install the man pages for qmail?

After setup, all the .0 files are in my source dir, but they have not been
moved to the man dirs or added to the indexes.

Are they supposed to be installed during 'make setup check'?

-Steve




they are in /var/qmail/man
You'll probably need to adjust your MANPATH


At 07:30 PM 11/15/99 , you wrote:
>What command is supposed to install the man pages for qmail?
>
>After setup, all the .0 files are in my source dir, but they have not been
>moved to the man dirs or added to the indexes.
>
>Are they supposed to be installed during 'make setup check'?
>
>-Steve







> What command is supposed to install the man pages for qmail?
> 
> After setup, all the .0 files are in my source dir, but they have not been
> moved to the man dirs or added to the indexes.

[...]

god, this was the question of the year. thx Steve <:}} this is sth
which isn't explained anywhere (if it was, i wasn't able to see it) and 
also i'd like to know which ones the right directories are. "make
setup check" or sth else should copy them to their proper places, i think.


love, peace etc,
dd





There is new Anti-Virus option for qmail users. I apologize that it's 
the first release and only minimally tested, but is functional.

Download the archive at
 http://www.grmi.org/~jhanna/qmail-avp.0.1.tgz
and AVP for Linux or FreeBSD from www.avp.com or www.avp.ru or 
www.kaspersky.ru

The qmail-avp wrapper is free under the GPL and AVP is currently a 
freebeta for Linux or FreeBSD.

Have fun.
John




When I try to check my mail, my MUA gives me the following error:

$-ERR this user has no $HOME/Maildir

What privs should the user's home and maildir have (not group or 
world writable..?)?  What else needs to be in the user's home 
directory, just .qmail containing "./Maildir/" ?  Thanks.




On Sun, Nov 14, 1999 at 08:50:33AM +0000, Frederik Lindberg wrote:
> Was looking for something optimized to low bandwidth settings.

*slaps self*  I'm pretty forgetful some times.  So let me ask some more
questions:

> > > 2a. if -l: compare host name of envelope recipients. If same as local host
> > > name, deliver locally with qmail-local.
> > > 2b. deliver multi-recipient message remotely (concurrent with 2a). If -l:
> > > remove all recipients with host part matching the local host (me).

Any suggestions on how to do concurrent deliveries correctly (ie even
under error conditions)?

> > > 3. Generate one bounce message per local recipient. Generate pre-VERP
> > > bounce if one of more remote recipients are not accepted.

What do you mean by "pre-VERP"?

> The discussion was multi-recipient messages, where qmail isn't optimal
> under these conditions.

Especially when all the recipients are guaranteed to go to the same
single smarthost.

> Yes, starting with a qmail queue would be one way. Maybe waiting for
> qmail-2.0 is another ;-)

And nobody should bet their business on something that doesn't exist
yet, no matter how good the reputation.
-- 
Bruce Guenter <[EMAIL PROTECTED]>                       http://em.ca/~bruceg/




Mr Bernstein will think this inappropriate behaviour, but....

I've _really_ trying to keep an NT box out of the mail stream by maybe
creating a quickie attachment filter -- something that rejects mpeg,
avi, exe attachments, etc.

Following Bruce Guenter's lead, I'm trying to insert a program between
qmail-smptd and qmail-queue.  I would like to take the file, decode any
attachment, see what file type it is, if OK, then pass it on to
qmail-queue.  

With initial testing I can interrupt the flow -- I can say write it to a
file, but can't use this file as input for qmail-queue without screwing
up the header.  I don't know how qmail-queue (or qmail-remote for that
matter) takes it's input.

Could anyone help?

-- 
Phil Crooker                    [EMAIL PROTECTED]
UNIX SysAdmin                   61 8 8443 6844
ORIX Australia                  61 8 8443 6955 (fax)




Thus said Phil Crooker on Tue, 16 Nov 1999 15:04:57 +1030:

> With initial testing I can interrupt the flow -- I can say write it to a
> file, but can't use this file as input for qmail-queue without screwing
> up the header.  I don't know how qmail-queue (or qmail-remote for that
> matter) takes it's input.
I don't know much about the code itself but have setup ezmlm and it can be 
configured to delete any content that isn't text/plain.  You might have a 
look at the code for ezmlm-idx
Andy
-- 
        +====== Andy ====== TiK: garbaglio ======+
        |    Linux is about freedom of choice    |
        +== http://www.xmission.com/~bradipo/ ===+






On Tue, Nov 16, 1999 at 03:04:57PM +1030, Phil Crooker wrote:
> With initial testing I can interrupt the flow -- I can say write it to a
> file, but can't use this file as input for qmail-queue without screwing
> up the header.  I don't know how qmail-queue (or qmail-remote for that
> matter) takes it's input.

qmail-queue reads a mail message from FD0 and the envelope from FD1.  To
run qmail-queue, you will at minimum need to open up one pipes to FD0
and make sure that FD1 does not get touched.  Then, make sure (if you
accept the message) that you copy the input bit-for-bit into the pipe
and close it.  qmail-queue will then read FD1 (which you've preserved)
and exit.  Trap the return code and exit with the same code.
-- 
Bruce Guenter <[EMAIL PROTECTED]>                       http://em.ca/~bruceg/




Do you have an example of the run script in the supervise dir.

marco leeflang

"Benjamin de los Angeles Jr." wrote:

> The scripts are now in
>
> http://members.surfshop.net.ph/~bench/qmail/
>
> On Thu, 11 Nov 1999, Doug Lumpkin wrote:
>
> > Please do post...
> >
> > --
> > Doug Lumpkin
> > [EMAIL PROTECTED]
> > ----- Original Message -----
> > From: Benjamin de los Angeles Jr. <[EMAIL PROTECTED]>
> > To: john <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Thursday, November 11, 1999 8:43 PM
> > Subject: Re: pop3 How To
> >
> >
> > >
> > > Install daemontools-0.61 and qmail's pop3d.
> > > I have a modified qmail and pop3d init scripts derived from Dan Sill's
> > > example which works with ucspi-tcp-0.84 and daemontools-0.61.
> > > Message me if you want the scripts, and I will be post it on my
> > > homepage.
> > >
> >
> >






I just updated my Qmail page, the scripts are there now.

On Tue, 16 Nov 1999, Marco Leeflang wrote:

> Do you have an example of the run script in the supervise dir.
> 
> marco leeflang
> 
> "Benjamin de los Angeles Jr." wrote:
> 
> > The scripts are now in
> >
> > http://members.surfshop.net.ph/~bench/qmail/
> >
> 





Fred Lindberg writes:
> Would it make sense to have a similar table (or put into the same
> table) also host for which authoritative DNS is not available?

DNS caching is the responsibility of your local name server. Old servers
supported only ``positive caching''; new servers also support ``negative
caching,'' which includes caching temporary failures.

---Dan




[EMAIL PROTECTED] writes:
> But what I am curious about is why installing ucspi (the package tcpserver
> comes in) put sgid bits in some of my directories:

There are three basic methods to automatically set the gid of a new
file: the BSD method, the useless method, and the SVR4 method.

The BSD method is to copy the gid from the directory. This turns groups
into a helpful administrative tool.

The useless method is to copy the gid from the effective gid of the
process. This turns groups into an administrative nightmare.

The SVR4 method is the same as the useless method, except that it
switches to the BSD method if the directory is setgid.

---Dan




Harald Hanche-Olsen writes:
> Now, one or more of these patches "upgraded" /usr/lib/sendmail (was a
> symlink to /var/qmail/bin/sendmail, became a "real" sendmail).

/etc/mta was designed to solve this problem:

   http://cr.yp.to/etc-mta.html

The standard qmail 2 installation will support /etc/mta. I expect other
MTAs to support /etc/mta too; it's in the interests of everybody except
Eric Allman.

---Dan




> http://www.ietf.org/internet-drafts/draft-ietf-drums-smtpupd-10.txt

See http://cr.yp.to/smtp/klensin.html for a list of problems with
smtpupd-10, including some serious interoperability failures.

Implementors who want documentation of how SMTP actually works should
try my reference manual at http://cr.yp.to/smtp.html.

---Dan




Gustavo V G C Rios writes:
>  31966 qmail-lspawn PSIG  SIGHUP SIG_DFL

Don't send qmail-lspawn a SIGHUP.

Some systems will automatically send a SIGHUP in certain situations if
you didn't follow step 14 of the installation instructions. The solution
is to follow the instructions.

---Dan




[EMAIL PROTECTED] writes:
> Some of our clients use ETRN to get their mail. I'm wondering what are
> my choices of solutions to implement this feature into qmail.

Install serialmail, and enable AutoTURN for authorized clients. An ETRN
client will receive its mail after it makes a connection.

---Dan




"D. J. Bernstein" wrote:

> [EMAIL PROTECTED] writes:
> > Some of our clients use ETRN to get their mail. I'm wondering what are
> > my choices of solutions to implement this feature into qmail.
>
> Install serialmail, and enable AutoTURN for authorized clients. An ETRN
> client will receive its mail after it makes a connection.
>
> ---Dan

So, if the ETRN client connects to the ISP and forces its queue
via the ISP's mail server (relaying allowed),
the AutoTURN will "wake up" and force all the mail for it.
Is that correct?


begin:vcard 
n:Kupenov;Georgi
tel;work:(359-2)963-0641
x-mozilla-html:FALSE
org:ProLink Ltd.;Sofia
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;0
fn:Georgi Kupenov
end:vcard




Hammond, James T.S. writes:
> sometimes a few will bounce with claims of not having a mailbox by
> that name.

This problem is most often caused by an automounter bug. You can
eliminate the problem by turning on the qmail-users mechanism.

---Dan




Frank Tegtmeyer writes:
> They now also (like AOL) exceed the 512Byte margin in DNS replies and 
> generate the well known "CNAME lookup failed temporarily".

Seems to be fixed now. And it also seems to be fixed at AOL.

---Dan





> Seems to be fixed now. And it also seems to be fixed at AOL.
Yes, you are right. Surprising ...

Regards, Frank


Reply via email to