Re: Modifying qmail-remote

[Bruce Guenter]

On Wed, May 31, 2000 at 08:24:08AM +0200, Jean-Baptiste Jacquemard wrote:
> I have moved qmail-remote to qmail-remote.real
> I made a shell script named qmail-remote, with the same permissions
> which contains:
> 
> #!/bin/sh
> exec /var/qmail/bin/qmail-remote.real "$*"
> 
> But when I try to send a message, I got this from Mailer Daemon:
> <[EMAIL PROTECTED]>:
> Unable to run qmail-remote.
> 
> Any idea?
> For information:
> dns:/var/qmail/bin# ls -l qmail-remote qmail-remote.real
> -rwx--x--x   1 root root  112 May 31 08:11 qmail-remote*
> -rwx--x--x   1 root root21796 May 30 14:34
> qmail-remote.real*

IIRC, qmail-remote is executed as user "qmailr", which doesn't have read
permission on your new shell script.  Shell scripts require read
permission to execute.
-- 
Bruce Guenter <[EMAIL PROTECTED]>   http://em.ca/~bruceg/

Re: DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)

[Russ Allbery]

Magnus Bodin <[EMAIL PROTECTED]> writes:

> Isn't the general shift nowadays (since 1994 and forward) from news to
> mailinglists just because of the big problem with
> spam-address-collectors on usenet?

If that's the case, you're all already doomed; this mailing list has been
gated to two or three different newsgroups for years now.  I've noticed
because my messages to it keep showing up in Deja.  That's common for most
large mailing lists.

In my personal experience, Usenet is slightly more of a harvesting risk
than large and well-known mailing lists but it isn't *that* significant.
Pretty much everything pales in comparison to web harvesting now,
actually.  (And of late, I get a reasonable amount of Chinese spam and
almost no other spam; I'm down to averaging around five pieces of spam a
day and I do essentially no filtering.  But .edu addresses seem to have a
very different spam pattern than .com addresses.)

I'm a huge fan of Usenet for a lot of things, and an advocate of Usenet,
but it's also my experience that technical fora tend to start as either
newsgroups or mailing lists and generally don't move well from one to
another.  You couldn't turn, say, comp.unix.programmer into a mailing list
without losing a lot of the strong points of the group, and similarly I
don't think this mailing list would convert to a newsgroup well.  And I
don't think there's enough qmail discussion to really warrant both this
mailing list and a Big Eight newsgroup.

-- 
Russ Allbery ([EMAIL PROTECTED]) 

Re: Modifying qmail-remote

[Jean-Baptiste Jacquemard]

Yes, it works now.
Thank you for your help, and thanks to Peter Samuel too.

Bruce Guenter wrote:

> IIRC, qmail-remote is executed as user "qmailr", which doesn't have read
> permission on your new shell script.  Shell scripts require read
> permission to execute.
> --
> Bruce Guenter <[EMAIL PROTECTED]>   http://em.ca/~bruceg/

--
Jean-Baptiste Jacquemard

J. POLLAK & Cie SNC
4, rue de la Bourse
75002 PARIS

Re: Help adding taglines to relayed messages.

[clemensF]

> Dave Potter:

> Rather than modify configurations on each of the local servers, I'm trying
> to figure out the best way to have qmail on the relay machine call a
> custom program which will append to the body of a message a tagline that
> looks similar to Yahoo/Hotmail's taglines.

that's not difficult:  put

"| ( cat; cat  ) | qmail-inject"

into the appropriate .qmail.  the parenthezised expression takes the
original message on stdin and appends some file to it, piping the result
into qmail-inject.

-- 
clemens

Re: Modifying qmail-remote

[Peter Samuel]

On Wed, 31 May 2000, Peter Samuel wrote:
> 
> I too have a simple Pierl qmail-queue wrapper. Let me tidy it up and
> I'll post it to the list. It currently does nothing, but can be used
> to do whatever wrapping you feel is appropriate (provided you can
> write the code to do it).

I have attached qmail-queue-wrapper.pl. It is a generic qmail-queue
wrapper. It currently does nothing to a message except add an extra
header of the form

Received: (qmail-queue-wrapper 24590 invoked from network);
31 May 2000 07:16:44 -

It then simply hands the message over to the real qmail-queue.

If you know perl, you can modify it to do whatever you want - just
don't come crying to me if it doesn't work after you've modified it.

To install:

install perl if you haven't got it on your system
choose a non production system to test this on
choose a quiet time
save the perl file in /var/qmail/bin/qmail-queue-wrapper.pl
stop qmail-smtpd
stop qmail-qmqpd
stop qmail

cd /var/qmail/bin
vi qmail-queue-wrapper.pl

change the first line

#!/pkgs/bin/perl -w

to reflect where your perl binary really lives

chown root qmail-queue-wrapper.pl
chgrp qmail qmail-queue-wrapper.pl
chmod 755 /tmp/qmail-queue-wrapper.pl
# The wrapper program should NOT be setuid!!!
mv qmail-queue qmail-queue.orig; mv qmail-queue-wrapper.pl qmail-queue

start qmail
start qmail-qmqpd
start qmail-smtpd

There is a small chance that mail injected into the queue via
qmail-inject (and it's friends sendmail and datemail) will attempt to
call qmail-queue between the "mv" commands above. That's
why you should choose a quiet time.

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

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


#!/pkgs/bin/perl -w
#
# $Id: qmail-queue-wrapper.pl,v 1.1 2000/05/31 07:20:37 psamuel Exp $
#
# qmail-queue wrapper program.
#
# This program should be used when you wish to manipulate a mail
# message BEFORE it is placed in the queue. Possible uses include:
#
#- header rewriting
#- Firstname.Lastname replacements
#- virus scanning
#- anything else you can think of
#
# There are at least 2 ways of using this program:
#
#1) Replace the original qmail-queue with this program:
#
#   mv /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig
#   cp qmail-queue-wrapper /var/qmail/bin/qmail-queue
#
#Change the value of $qmailqueue below, to reflect the new name of
#the original qmail-queue program. For example
#
#   my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
#
#2) Recompile qmail with Bruce Guenter's QMAILQUEUE patch. (See
#http://www.qmail.org/qmailqueue-patch). Then any program that
#needs to use this program can be called with the environment
#variable QMAILQUEUE set to /var/qmail/bin/qmail-queue-wrapper
#
# How does it work? The interface to the real qmail-queue is simple:
#
# - the body of the message is read from file descriptor 0
# - the envelope details are read from file descriptor 1.
#
# qmail-queue-wrapper also adheres to the same interface. After doing
# whatever manipulations are necessary, it calls the real qmail-queue
# and provides the message body on file descriptor 0 and the envelope
# details on file descriptor 1.
#
# Exit codes conform to those mentioned in the qmail-queue(8) manual page.
#
###

require 5;
use strict;

my $child;
my $debug = 0;
my $envelope;
my %errors;
my @months;
my $new_received_header;
my $qmailqueue = "/var/qmail/bin/qmail-queue.orig";
my @recipients;
my $sender;

###

&initialise();

if ($child = fork())
{
# Parent

my $timeout = 86400;# See qmail-queue.c, line 20

alarm($timeout);

&fatal(82) unless close MESSAGE_READER;
&fatal(82) unless close ENVELOPE_READER;

&process_message();
&process_envelope();

# Wait for the child to terminate

waitpid($child, 0);

# Return with the exit status of the child

exit($? % 255);
}
elsif (defined $child)
{
# Child

&fatal(82) unless close MESSAGE_WRITER;
&fatal(82) unless close ENVELOPE_WRITER;

&fatal(82) unless defined open(STDIN, "<&MESSAGE_READER");
&fatal(82) unless defined open(STDOUT, "<&ENVELOPE_READER");

if ($debug)
{
&debug_message("$$: Reading message from STDIN\n\n");

while ()
{
&debug_message("$$: $_");
}

&fatal(82) unless cl

Re: Modifying qmail-remote

[Peter Samuel]

On Wed, 31 May 2000, Jean-Baptiste Jacquemard wrote:

> Yes, it works now.
> Thank you for your help, and thanks to Peter Samuel too.

It will also teach me to READ things more carefully. I thought you were
talking about qmail-queue. In fact I thought you were the person
taling about adding taglines to all messages.

Repeats to himself

"I must read things carefully"
"I must read things carefully"
"I must read things carefully"
...

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

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

pop3 Log file?

[Marco Benetton]

Hi, 
I haven't a file where there are the pop3 log.
This is the configuration in the /etc/inetd.conf file


pop-3   stream  tcp nowait  root/var/qmail/bin/qmail-popup
qmail-popup dns.protec.it /bin/checkpassword /var/qmail/bin/qmail-pop3d
Maildir

Any suggestion?
Thanks

-- 

-
Marco

Re: pop3 Log file?

[Petr Novotny]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 31 May 00, at 10:50, Marco Benetton wrote:

> Hi, 
> I haven't a file where there are the pop3 log.

What kind of log do you need/expect?

> This is the configuration in the /etc/inetd.conf file
> 
> 
> pop-3   stream  tcp nowait  root/var/qmail/bin/qmail-popup
> qmail-popup dns.protec.it /bin/checkpassword
> /var/qmail/bin/qmail-pop3d Maildir
> 
> Any suggestion?

No log is getting created this way (except that if 
/bin/checkpassword is PAMified, it reports failed authentication 
attempts).

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

iQA/AwUBOTTDjVMwP8g7qbw/EQKnfgCfRs4PC3uYCt+64baMorOYTieUeZ8AniSE
EbY2GCZV12QEIVeTHWfJtG9Z
=A3LG
-END PGP SIGNATURE-
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
 [Tom Waits]

qmail Server

[Nguyen Hong Son]

Dear all
I found in this Mailing list about many features of qmail. Can I have some 
questions about using qmail for making a mail server.
_ Is qmail one of a complete solution for making a mail server for Internet 
Services Provider (Creat and Manage user account, deliver quota for each 
mailbox, mail relay .v.v..) or only a Mail Transport Agent (MTA) ?
_ I've got qmail-1.03, do I need some more patches for the complete solution 
?
Thank for advance

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

qmail Digest 31 May 2000 10:00:01 -0000 Issue 1018

[qmail-digest-help]

qmail Digest 31 May 2000 10:00:01 - Issue 1018

Topics (messages 42469 through 42528):

Scanning outgoing attachments
42469 by: Jean-Baptiste Jacquemard

Re: vpopmail + qmail
42470 by: Christian Wiese
42478 by: clemensF
42481 by: Christian Wiese

MDaemon delivery "protocol timeout"
42471 by: Lee Haw Ling

Re: A good book for qmail
42472 by: qmail.col7.metta.lk
42473 by: Ali Sahin
42474 by: Peter van Dijk

Re: qmail-smtp problem
42475 by: Greg Owen

re:re: qmail-smtp problem
42476 by: Tore Micaelsen

Re: A Good Book On Qmail
42477 by: Rodney Edwards
42490 by: Russ Allbery
42492 by: John R. Levine

Re: help - very slow POP3 mail retrieval
42479 by: clemensF
42485 by: chuck
42487 by: Greg Jorgensen

Re: qmail + vpopmail error
42480 by: Christian Wiese

qmail-smtpd and stunnel
42482 by: Johan Almqvist

Backup logs
42483 by: Paul Aviles
42484 by: J. I. Sendoro
42486 by: clemensF
42488 by: Paul Aviles

Re: Qpopper 2.53 remote problem,  user can gain  gid=mail (fwd)
42489 by: Russ Allbery
42494 by: John Gonzalez/netMDC admin

Re: i-love-you-letter - Claus Farber.
42491 by: Russ Allbery

DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)
42493 by: Darren Wyn Rees
42496 by: Peter van Dijk
42508 by: Russ Allbery
42511 by: Peter van Dijk
42512 by: Magnus Bodin
42521 by: Russ Allbery

How to achieve better logging
42495 by: Kost, Kathy

This is strange..
42497 by: Vince Vielhaber
42498 by: Peter van Dijk
42500 by: Vince Vielhaber
42502 by: Peter van Dijk
42509 by: clemensF
42514 by: Rogerio Brito

Qmail: problems with SMTP e Qmailadmin
42499 by: Edilmar Alves

Migrating to Qmail, Maildir issues
42501 by: net admin
42510 by: clemensF

How to pipe qmail into another program
42503 by: Steve Quezadas
42504 by: Peter van Dijk

Re: Binary distribution
42505 by: Mate Wierdl

doc tarballs
42506 by: Mate Wierdl

Help adding taglines to relayed messages.
42507 by: Dave Potter
42513 by: Peter Samuel
42523 by: clemensF

How to install virtualdomains in qmail
42515 by: Rupak Joshi

Modifying qmail-remote
42516 by: Jean-Baptiste Jacquemard
42518 by: Peter Samuel
42520 by: Bruce Guenter
42522 by: Jean-Baptiste Jacquemard
42524 by: Peter Samuel
42525 by: Peter Samuel

qmail features
42517 by: Dung Nguyen
42519 by: Peter Samuel

pop3 Log file?
42526 by: Marco Benetton
42527 by: Petr Novotny

qmail Server
42528 by: Nguyen Hong Son

Administrivia:

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

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

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

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


--



Hello,
I would like to scan all outgoing traffic and log the attachments file
names, and accessory, the size of the attached file.
Please help me, I don't know how to do that.

--
Jean-Baptiste Jacquemard

J. POLLAK & Cie SNC
4, rue de la Bourse
75002 PARIS







Hi Toni,
please tell us what kind of qmail package and what Linux distribution
do you use.
On some systems the POP3 service in /etc/services is called pop3, but
qmail-pop3d uses pop-3.
So please have a look at the /etc/services and check out what is writen
there under port 110.
If there is an entry like pop3 change it to pop-3 and try to run your
qmail-pop3d server again.
e.g. /etc/services
---
pop-3   
110/tcp pop-3  
# POP version 3
pop-3   
110/udp    pop-3
---
Greetings
Christian
Toni schrieb:

Hi, I
have a problem, I have a Linux server with qmail-smtp and vpopmail-pop3.When
I restart the server, the pop3 server is not running and I must stop the
smtp service, start the pop3 service and restart the smtp service.But,
the system don't give me any error, only I execute netstat -l and the pop3
service is not in the list of the active services. Have
you a solution for this error?






> Christian Wiese:

> please tell us what kind of qmail package and what Linux distribution do
> you use.
> On some systems the POP3 service in /etc/services is called pop3, but
> qmail-pop3d uses pop-3.
> So please have a look at the /etc/services and check out what is writen
> there under port 110.
> If there is an entry like pop3 change it to pop-3 and try to run your
> qmail-pop3d server again.

wow!  you almost had me there, mr. wiese.  barely had i finished reading
your posting, w

SMTP SIZE command revisited (new patch)

[Will Harris]

I've extended the little patch I wrote earlier to make qmail fully RFC
1870 compliant, including the extended MAIL FROM ... SIZE syntax.

You can also get it from my website, http://will.harris.ch.

regards,
Will


*** qmail-smtpd.c.orig  Mon May 29 11:54:41 2000
--- qmail-smtpd.c   Wed May 31 11:44:21 2000
***
*** 52,57 
--- 52,58 
  void err_bmf() { out("553 sorry, your envelope sender is in my badmailfrom list 
(#5.7.1)\r\n"); }
  void err_nogateway() { out("553 sorry, that domain isn't in my list of allowed 
rcpthosts (#5.7.1)\r\n"); }
  void err_unimpl() { out("502 unimplemented (#5.5.1)\r\n"); }
+ void err_size() { out("552 sorry, that message size exceeds my databytes limit 
+(#5.3.4)\r\n"); }
  void err_syntax() { out("555 syntax error (#5.5.4)\r\n"); }
  void err_wantmail() { out("503 MAIL first (#5.5.1)\r\n"); }
  void err_wantrcpt() { out("503 RCPT first (#5.5.1)\r\n"); }
***
*** 197,202 
--- 198,239 
return 1;
  }
  
+ int sizelimit(arg)
+ char *arg;
+ {
+   int i;
+   long r;
+   unsigned long sizebytes = 0;
+ 
+   if (r < 0) return 0;
+   
+   i = str_chr(arg,'<');
+   if (arg[i])
+ arg += i + 1;
+   else {
+ arg += str_chr(arg,':');
+ if (*arg == ':') ++arg;
+ while (*arg == ' ') ++arg;
+   }
+ 
+   arg += str_chr(arg,' ');
+   if (*arg == ' ') while (*arg == ' ') ++arg;
+   else return 1;
+ 
+   i = str_chr(arg,'=');
+   arg[i] = 0;
+   if (case_equals(arg,"SIZE")) {
+ arg += i;
+ while (*++arg && *arg > 47 && *arg < 58) {
+   sizebytes *= 10;
+   sizebytes += *arg - 48;
+ }
+ r = databytes - sizebytes;
+ if (r < 0) return 0;
+   }
+   return 1;
+ }
+ 
  int bmfcheck()
  {
int j;
***
*** 227,235 
smtp_greet("250 "); out("\r\n");
seenmail = 0; dohelo(arg);
  }
  void smtp_ehlo(arg) char *arg;
  {
!   smtp_greet("250-"); out("\r\n250-PIPELINING\r\n250 8BITMIME\r\n");
seenmail = 0; dohelo(arg);
  }
  void smtp_rset()
--- 264,279 
smtp_greet("250 "); out("\r\n");
seenmail = 0; dohelo(arg);
  }
+ char size_buf[FMT_ULONG];
+ void smtp_size()
+ {
+   size_buf[fmt_ulong(size_buf,(unsigned long) databytes)] = 0;
+   out("250 SIZE "); out(size_buf); out("\r\n");
+ }
  void smtp_ehlo(arg) char *arg;
  {
!   smtp_greet("250-"); out("\r\n250-PIPELINING\r\n250-8BITMIME\r\n");
!   smtp_size();
seenmail = 0; dohelo(arg);
  }
  void smtp_rset()
***
*** 240,245 
--- 284,290 
  void smtp_mail(arg) char *arg;
  {
if (!addrparse(arg)) { err_syntax(); return; }
+   if (!sizelimit(arg)) { err_size(); return; }
flagbarf = bmfcheck();
seenmail = 1;
if (!stralloc_copys(&rcptto,"")) die_nomem();

Re: doc tarballs

[Felix von Leitner]

> I made four tarballs from the docs found at cr.yp.to.  The tarballs
> are

> ftp://moni.msci.memphis.edu/pub/doc/daemontools-0.70-doc-0.01.tar.gz
> ftp://moni.msci.memphis.edu/pub/doc/dnscache-1.00-doc-0.01.tar.gz
> ftp://moni.msci.memphis.edu/pub/doc/publicfile-0.52-doc-0.01.tar.gz
> ftp://moni.msci.memphis.edu/pub/doc/ucspi-tcp-0.88-doc-0.01.tar.gz

> They all install the way it is suggested by the instructions for the
> dnscache doc tarball, so you will get 

> commands.html, libraries.html and packages.html

> The file 

> ftp://moni.msci.memphis.edu/pub/doc/README.doc

> tells you about the tools in the tarballs you can use to update these
> docs.

Is anyone willing to help port the djb docs to man pages?
I have started writing man pages for my libdjb project, specifically the
DNS resolver routines, but in my humble opinion it would be much better
to have the documentation for the user programs as man pages, too.  Just
a few days ago I was installing a bastion host for a firewall system,
and of course I didn't have Internet access until everything was set up,
so I couldn't read the documentation.

Luckily I had my laptop with a mirror of cr.yp.to with me, but that
should not be mandatory.

Felix

Caveat - Re: SMTP SIZE command revisited (new patch)

[Will Harris]

 >I've extended the little patch I wrote earlier to make qmail fully RFC
 >1870 compliant, including the extended MAIL FROM ... SIZE syntax.
 >
 >You can also get it from my website, http://will.harris.ch.

Just a quick caveat - using this patch assumes that you *do* have a 
databytes file... otherwise any server supplying a SIZE parameter will have 
the mail rejected.

To fix this, in case you for some reason want the patch but don't want a 
databytes file (wierd!), change the following added line in the patch from

 >  void smtp_mail(arg) char *arg;
 >  {
 >if (!addrparse(arg)) { err_syntax(); return; }
 >+   if (!sizelimit(arg)) { err_size(); return; }

to

 >+   if (databytes && !sizelimit(arg)) { err_size(); return; }

That'll provide some extra security... I've made the change on the patch on 
my web page too.

Will
__

  "I was going to be a Neo-Deconstructivist, but Mom wouldn't let me..."

multimedia laboratorium  [EMAIL PROTECTED]
institut fuer informatik(pgp id)F703D035
der universitaet zuerich(office) +41  1 635 4346
winterthurerstr. 190(fax)+41  1 635 6809
ch-8057 zuerich (mobile) +41 76 372 0913
switzerland www.ifi.unizh.ch/~harris
__

Re: DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)

[Russell Nelson]

Russ Allbery writes:
 > Darren Wyn Rees <[EMAIL PROTECTED]> writes:
 > 
 > > Below, I've quoted a DRAFT RFD proposal for comp.mail.qmail.
 > 
 > I'm not sure this is a good idea, mostly because I don't see the
 > distinction between the newsgroup and this mailing list and I also don't
 > expect the people using the mailing list to really want to move to a
 > newsgroup.  Without the core of people on this mailing list that know
 > qmail very well and answer most of the questions, the newsgroup is
 > unlikely to be all that useful, and I haven't heard much indication that
 > those people would really prefer a newsgroup.

I agree with you in general, Russ.  The only benefit I can see to
comp.mail.qmail is that there is also a comp.mail.sendmail.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://russnelson.com
Crynwr sells support for free software  | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | do for you..."  -Perry M.

Amavis and QMail ?

[Marco Cintolesi]

Hi all,
anyone have a minimal documentation for setting amavis under QMail ?

Thanks for now
Marco

FYI - Yahoos mail servers seem to be failing again.

[Bryan White]

I have not dug into it yet but on the surface it looks like it did a couple
of months ago.  Back then a yahoo server would stop responding in the middle
of a mail connection, leaving qmail to wait for a time out.  It tends to tie
up large numbers of remotes.  Right now yahoo is consuming 80% of my qmail
remotes and the queue is growing.

Last time it took them 4 or 5 days to get it straightened out.

Re: Amavis and QMail ?

[Erwin Hoffmann]

Hi, 

check 

http://satan.oih.rwth-aachen.de/AMaViS/

cheers.
eh.

At 16:06 31.5.2000 +0200, Marco Cintolesi wrote:
>Hi all,
>anyone have a minimal documentation for setting amavis under QMail ?
>
>Thanks for now
>Marco
>
>
+---+
|  fffhh http://www.fehcom.deDr. Erwin Hoffmann |
| ff  hh|
| ffeee     ccc   ooomm mm  mm   Wiener Weg 8   |
| fff  ee ee  hh  hh   cc   oo   oo  mmm  mm  mm 50858 Koeln|
| ff  ee eee  hh  hh  cc   oo oo mm   mm  mm|
| ff  eee hh  hh   cc   oo   oo  mm   mm  mm Tel 0221 484 4923  |
| ff      hh  hhccc   ooomm   mm  mm Fax 0221 484 4924  |
+---+

Re: DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)

[Timothy L. Mayo]

On Wed, 31 May 2000, Russell Nelson wrote:

> Russ Allbery writes:
>  > Darren Wyn Rees <[EMAIL PROTECTED]> writes:
>  > 
>  > > Below, I've quoted a DRAFT RFD proposal for comp.mail.qmail.
>  > 
>  > I'm not sure this is a good idea, mostly because I don't see the
>  > distinction between the newsgroup and this mailing list and I also don't
>  > expect the people using the mailing list to really want to move to a
>  > newsgroup.  Without the core of people on this mailing list that know
>  > qmail very well and answer most of the questions, the newsgroup is
>  > unlikely to be all that useful, and I haven't heard much indication that
>  > those people would really prefer a newsgroup.
> 
> I agree with you in general, Russ.  The only benefit I can see to
> comp.mail.qmail is that there is also a comp.mail.sendmail.
> 

I seem to recall having this discussion 4 years ago and we decided at that
point that comp.mail.qmail was not a good idea. :)  Oh well, here we go
again.

-
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- Phone
(412) 810-8886 Fax

a couple of things: MX stuff and filtering

[Keith Warno]

Greetings.  I have a couple of requests for suggestions, the first related
to MX lookups (and how to avoid them) and the second related to filtering of
mail.

1) I have a small cluster of Linux boxes (4), all of which are running qmail
1.03.  One of these boxes is listed as the mail exchanger for the domain
that all four boxes are in.  This MX box allows relaying for all of its
friends on the same net.  The users of the 4 different linux boxes would
like to be able to send mail to the users of the other linux boxes,
bypassing the MX box if possible.  The only method I have come up with is to
maintain control/smtproutes on each box.  Eg:

box1.linux.net:box1.linux.net
box2.linux.net:box2.linux.net
box3.linux.net:box3.linux.net
box4.linux.net:box4.linux.net


This is silly, but otherwise we get bounces like:

Sorry. Although I'm listed as a best-preference MX or A for that host,
it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)


Methinks of letting all the mail go through the MX anyway, and throw a
control/smtproutes on the MX box only.  A new issue arises.  Some of the
linux boxes have aliases (eg, CNAMES).  My users interchange the real names
with the CNAMES depending on their mood, the phase of the moon, and how much
alcohol is in their blood.  The issue is best illustrated by example (the
attached text file).  I am not sure if the issue is normal behavior; please
take a look and I would appreciate your comments.


2) Filtering.  Dave Sill had a suggestion posted somewhere (the URL escapes
me...) about how to implement filtering (ie virus scanning, etc) of
messages.  The suggestion involved installing qmail twice on the same
machine.  I would like to do filtering (at least of incoming messages) using
two installations of qmail, each installation being on one of two separate
machines.  The first machine would do the filtering and then send the
message off to the second for final delivery if everything is "OK".  If
everyting is not "OK", do something else.  From what I understand this is
common practice out there in coporate land.

Trouble is I an very unclear as to how to attack this, considering that the
filter box would be relaying mail for multiple domains for which it would be
an MX.  Any pointers on where to begin would be appreciated greatly!

Thanks much,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/



The issue is that two "deliveries" are required to deliver one message when the 
message is sent
to an address that has, as the host, a CNAME and control/smtproutes contains route 
info for
the host using its real name (as opposed to the CNAME).

Some notes:

0)   Line numbers in square brackets (in mail log stuff below) inserted for 
readability.
1)   develop.muao-inc.net is an alias (CNAME) for muao-inc.net.
2)   The MX box (mx.muao-inc.net, which is the same physical box as smtp.muao-inc.net)
 has in its control/smtproutes:

 muao-inc.net:muao-inc.net

3)   I sent a message from my window$ box to ``[EMAIL PROTECTED]'' via 
smtp.muao-inc.net [03]
4)   Line 12 is where I say "erf?"  Why is the MX connecting to itself?  I assume a 
lookup was done
 on develop.muao-inc.net and someone noticed that it's really muao-inc.net and so 
a new delivery
 is started.  Is this correct?
5)   The second "delivery" is avoided if control/smtproutes contains, in addition to 
that in (2),

 develop.muao-inc.net:develop.muao-inc.net

 This makes sense but I'd hate to have to throw every alias in there for every 
machine to avoid the
 extra tcpserver work as seen in [12].  Argh... a tradeoff.

Opions/comments as to what would be "proper" for this sort of situation are welcome.  
Should we just throw
in the real names and let tcpserver do some extra work, or throw in every name & alias?


[01]May 31 12:20:06 curly smtp: 959790006.155003 tcpserver: status: 1/40
[02]May 31 12:20:06 curly smtp: 959790006.155684 tcpserver: pid 19753 from 10.1.10.158
[03]May 31 12:20:06 curly smtp: 959790006.158461 tcpserver: ok 19753 
smtp.muao-inc.net:10.1.10.213:25 keith.muao-inc.net:10.1.10.158::1194
[04]May 31 12:20:06 curly qmail: 959790006.183068 new msg 30605
[05]May 31 12:20:06 curly qmail: 959790006.183228 info msg 30605: bytes 730 from 
<[EMAIL PROTECTED]> qp 19754 uid 203
[06]May 31 12:20:06 curly smtp: 959790006.185391 tcpserver: end 19753 status 0
[07]May 31 12:20:06 curly smtp: 959790006.185829 tcpserver: status: 0/40
[08]May 31 12:20:06 curly qmail: 959790006.202205 starting delivery 7724: msg 30605 to 
remote [EMAIL PROTECTED]
[09]May 31 12:20:06 curly qmail: 959790006.202376 status: local 0/10 remote 1/20
[10]May 31 12:20:06 curly smtp: 959790006.251671 tcpserver: status: 1/40
[11]May 31 12:20:06 curly smtp: 959790006.252497 tcpserver: pid 19756 from 10.1.10.210
[12]May 31 12:20:06 curly smtp: 959790006.254918 tcpserver: ok 19756 
mx.muao-inc.net:10.1.10.210:25 mx.muao-inc.net:10.1.10.210::4246
[13]May 31 12:20:06 curly qmail: 959790006.2647

Re: Amavis and QMail ?

[Rainer Link]

On Wed, 31 May 2000, Marco Cintolesi wrote:

> Hi all,
> anyone have a minimal documentation for setting amavis under QMail ?

Please see http://dev.amavis.org 

HTH

best regards,
Rainer Link

Recipe For A Good Book On Qmail

[David L. Nicol]

Here I go stating the obvious again, but it seems what we are saying is
that the archives of this list, plus the documentation that already is
in existence, makes up a "book" for those who can access it, ergo

what is required might not be an _author_ to create a new, comprehensive
restatement but rather an __editor__ to select from the documentation
which exists (man pages, LWQ, FAQ lists, et cetera) and compile a compendium.

This editor would preferably _NOT_ be someone who "knows a lot about qmail"
they would be a quality technical writer with perhaps gardening background.

This editor would be assigned the task, they would have to start from zero
(zero being a PC with the debian potato installed on it by someone else)
and configure and maintain, telling their story and including the documents
they find most helpful (with permission of the various authors).  That's the
first half, in which Linda Potter goes from zero to MTA administrator.

For the second half, Linda Potter (our fictionalized hero) builds on the
experiences in the first half, going on to install custom patches, to do 
what exactly?  Maybe the first half is all that is needed.

Potato to qmail+EZMLM in five or six short chapters.


I addition to people participating in this thread on the qmail list,
I am CCing a retired technical writer who teaches at UMKC in case this
project might appeal to them for collaboration later this summer.




Russ Allbery wrote:
> 
> Rodney Edwards <[EMAIL PROTECTED]> writes:
> 
> > Qmail & ezmlm is now getting so popular that someone has to get their
> > arse in gear and get a book to print. The Idea is a certain winner so
> > com'on O'reilly, Que, or Sam's if your listening in get your finger out
> > guys where drowning out here.
> 
> I don't believe that publisher interest is the hold-up.  To publish a
> book, someone has to write it first, and one would hope that the people
> doing so would actually know a decent amount about qmail.  :)  Those
> people are somewhat rare; qmail hasn't been around for that long yet.
> 
> --
> Russ Allbery ([EMAIL PROTECTED]) 

-- 
  David Nicol 816.235.1187 [EMAIL PROTECTED]
  find / -name core|perl -ne'chomp;unlink'

Re: Recipe For A Good Book On Qmail

[Chin Fang]

I would say a reasonable thing to do is to make a survey on the list
and see the scope of such a book, if one is ever written.

I say this because I believe that for any intellectual project
(writing a book definitely falls in this category), it's always a
fruitful exercise to define the scope of the project first, before
spending further effort.  You wan to be clear what you would like to
accomplish in a project.  This is one of the basics of any project
management I suppose.

To set up qmail for a home system and to set it up for say millions of
active users require quite a different level of effort and
understanding.  The latter of course is much more demanding.  So, what
audience the book intends to address?  Once the scope of the book is
defined, no one can come back and say "this is a lousy book, it
doesn't talk about this or that... etc".

Regards,

Chin Fang
[EMAIL PROTECTED]

> 
> Here I go stating the obvious again, but it seems what we are saying is
> that the archives of this list, plus the documentation that already is
> in existence, makes up a "book" for those who can access it, ergo
> 
> what is required might not be an _author_ to create a new, comprehensive
> restatement but rather an __editor__ to select from the documentation
> which exists (man pages, LWQ, FAQ lists, et cetera) and compile a compendium.
> 
> This editor would preferably _NOT_ be someone who "knows a lot about qmail"
> they would be a quality technical writer with perhaps gardening background.
> 
> This editor would be assigned the task, they would have to start from zero
> (zero being a PC with the debian potato installed on it by someone else)
> and configure and maintain, telling their story and including the documents
> they find most helpful (with permission of the various authors).  That's the
> first half, in which Linda Potter goes from zero to MTA administrator.
> 
> For the second half, Linda Potter (our fictionalized hero) builds on the
> experiences in the first half, going on to install custom patches, to do 
> what exactly?  Maybe the first half is all that is needed.
> 
> Potato to qmail+EZMLM in five or six short chapters.
> 
> 
> I addition to people participating in this thread on the qmail list,
> I am CCing a retired technical writer who teaches at UMKC in case this
> project might appeal to them for collaboration later this summer.
[...]

Re: DRAFT RFD - comp.mail.qmail - Comments Sought

[John R. Levine]

>I agree with you in general, Russ.  The only benefit I can see to
>comp.mail.qmail is that there is also a comp.mail.sendmail.

I suppose it might work with a two-way gateway between the newsgroup and
this list, and registration to post as it is now.  I've been doing that
for [EMAIL PROTECTED] for a while and it works
reasonably well.

But I do agree that other than the moderately greater visibility on
usenet, there's not much benefit to be gained.  In years past, the
volume of traffic on a usenet group would swamp any plausible mail
server.  Now, with almost free computrons and fast mail software like
qmail, that's much less of an issue.


-- 
John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869
[EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, 
Member, Provisional board, Coalition Against Unsolicited Commercial E-mail

Re: DRAFT RFD - comp.mail.qmail - Comments Sought

[Guillermo Villasana Cardoza]

I know this is not a qmail question... but I've been trying to get my
hands on an news server address as I have none from where to see any
newsgroups. Would someone please ... give me one :) if it is not much
trouble 

Thanks a lot

Guillermo 
"John R. Levine" wrote:
> 
> >I agree with you in general, Russ.  The only benefit I can see to
> >comp.mail.qmail is that there is also a comp.mail.sendmail.
> 
> I suppose it might work with a two-way gateway between the newsgroup and
> this list, and registration to post as it is now.  I've been doing that
> for [EMAIL PROTECTED] for a while and it works
> reasonably well.
> 
> But I do agree that other than the moderately greater visibility on
> usenet, there's not much benefit to be gained.  In years past, the
> volume of traffic on a usenet group would swamp any plausible mail
> server.  Now, with almost free computrons and fast mail software like
> qmail, that's much less of an issue.
> 
> --
> John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869
> [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl,
> Member, Provisional board, Coalition Against Unsolicited Commercial E-mail

Re: Recipe For A Good Book On Qmail

[David L. Nicol]

"John R. Levine" wrote:
> 
> >This editor would preferably _NOT_ be someone who "knows a lot about qmail"
> >they would be a quality technical writer with perhaps gardening background.
> 
> Having written quite a lot of technical books, I can say that's not
> likely to work, especially with an editor who doesn't know the
> material.  The qmail list is a swell way to get specific questions
> answered, but it's a lousy way to get introduced to qmail, and also
> not a very good way to get answers to questions that aren't phrased
> concretely.

I left out that the "book" would have to go through a beta period
of sorts, with public comment, and a "find the bugs" program with
money for the first to discover an inaccuracy or make an incremental
improvement.  It could be The First Bazaar-Style Technical Manual.

-- 
  David Nicol 816.235.1187 [EMAIL PROTECTED]
  JAPH

How to pipe messages

[Steve Quezadas]

I am trying to pipe the messages in qmail to go 
into another program called dmail. I am trying to pipe it in the rc file, but it 
is not working. Here is my rc file as it is right now. 
 
exec env - PATH="/var/qmail/bin:$PATH" 
\qmail-start ./Mailbox splogger qmail
 
This works. But if I change the second line 
to:
# qmail-start | /bin/dmail splogger 
qmail
 
It does NOT work. I am a bit confused about what 
this line does. What exactly is "splogger"? I can 
technically pipe dmail by altering the dot-qmail files, but I need this program 
to be invoked with EVERY new account that comes in. 
 
Any suggestions?
- Steve

Re: Recipe For A Good Book On Qmail

[clemensF]

> Chin Fang:

> I would say a reasonable thing to do is to make a survey on the list
> and see the scope of such a book, if one is ever written.
> 
> To set up qmail for a home system and to set it up for say millions of
> active users require quite a different level of effort and
> understanding.  The latter of course is much more demanding.  So, what
> audience the book intends to address?  Once the scope of the book is
> defined, no one can come back and say "this is a lousy book, it
> doesn't talk about this or that... etc".

this is a good idea.  i'd say the book should serve the maintainer of a
collaborating group of five individuals, who share a computer for email-
exchange, annotated for scalability problems where applicable.

-- 
clemens

Re: Recipe For A Good Book On Qmail

[Chin Fang]

Also,

I think an inspiring author(s) also need to consider the depth of the
coverage.  For instance, in general, qmail processes are quite small in
size, but improperly used, they can be really bloated.  

An example (which Dr. Bernstein has waned in qmail-smtpd man page in
subtle ways): qmail-smtpd in general is quite small - 1.5 MB or less.
However, if a newbie ISP admin comes in and slaps up a big rcpthosts
(rather than a morercpthosts in cdb format), then qmail-smtpd can be
as big as say 10MB or bigger, combined with high CPU utliization!

To understand this, one needs to read the source code of both
qmail-smtpd.c and control.c, and see what control_readfile() (a linear
search) does.

But, how many people would run into this, and whether it's fruitful to
cover such topics need to be carefully considered. Compromises have to
be made somewhere..

Regards,

Chin Fang
[EMAIL PROTECTED]

> > To set up qmail for a home system and to set it up for say millions of
> > active users require quite a different level of effort and
> > understanding.  The latter of course is much more demanding.  So, what
> > audience the book intends to address?  Once the scope of the book is
> > defined, no one can come back and say "this is a lousy book, it
> > doesn't talk about this or that... etc".
> 
> this is a good idea.  i'd say the book should serve the maintainer of a
> collaborating group of five individuals, who share a computer for email-
> exchange, annotated for scalability problems where applicable.
> 
> -- 
> clemens
> 

Re: Recipe For A Good Book On Qmail

[clemensF]

> Chin Fang:

> An example (which Dr. Bernstein has waned in qmail-smtpd man page in
> subtle ways): qmail-smtpd in general is quite small - 1.5 MB or less.
> However, if a newbie ISP admin comes in and slaps up a big rcpthosts
> (rather than a morercpthosts in cdb format), then qmail-smtpd can be
> as big as say 10MB or bigger, combined with high CPU utliization!
> 
> But, how many people would run into this, and whether it's fruitful to
> cover such topics need to be carefully considered. Compromises have to
> be made somewhere..

yes, but not here.  every aspect of configuration has to be outlined in the
book.  your own example makes it clear:  in light of the trouble a newbie
should avoid, the reader has to be told why there are two controls in
different formats, but covering the same purpose.

-- 
clemens

Re: DRAFT RFD - comp.mail.qmail - Comments Sought

[Russ Allbery]

Guillermo Villasana Cardoza <[EMAIL PROTECTED]> writes:

> I know this is not a qmail question... but I've been trying to get my
> hands on an news server address as I have none from where to see any
> newsgroups. Would someone please ... give me one :) if it is not much
> trouble

 will let you purchase basic Usenet access using
your own ISP for Internet access for some fairly low price (something like
$30 a year).  You can also use  for free, but the
interface sucks.

-- 
Russ Allbery ([EMAIL PROTECTED]) 

SMTP e Qmailadmin problems

[Edilmar Alves]

Hi all,

I'd like to solve the following problems:
1. SMTP: I configured tcp.smtp like this, to accept
e-mails only for these IP subnets:
192.168.0.:allow,RELAYCLIENT=""
192.168.1.:allow,RELAYCLIENT=""
200.241.184.:allow,RELAYCLIENT=""
However, I entered from other ISP, with
address 200.212.255.25 and SMTP sents
my email. I boot Linux but the same behaviour
continues to occurr.
2. QMailAdmin: for 10, 20, 50 users, I think
QMailAdmin is very nice. However, I already
have more than 600 users, and when I enter
with postmaster, to administer the email accounts,
I have to spent more than FIVE minutes, using
Netscape. I'm using the "graphical interface" from
lynx, cause performance !!!
Is there a way to change the HTML skeleton pages
to show only the buttons, NOT the users list. I think
the access may be faster than.
2. QMailAdmin II: I created some users (+/- 103 users)
into a domain. All Maildir folders was created into
.../domains/fes.br/ (fes.br is my domain). After these 103,
folders like 0/, 1/, ... was created automatically by QMail.
At this point, no problems!
However, if one of these new users created into these folders
try to use QMailAdmin to change password, the system arises
an exception talking about "There already is a user logged with
postmaster" (something like this) and the new doesnt get to
change your password. I have to change password user per
user, with postmaster account.
The major users were created with QMailAdmin and some with
vadduser. Both users arises the exception.
The strange is: the first users created get to change password
into Web QMailAdmin...

Re: DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)

[Russ Allbery]

Darren Wyn Rees <[EMAIL PROTECTED]> writes:
> On Tue, May 30, 2000 at 10:18:39PM -0700, Russ Allbery wrote:

>> I'm not sure this is a good idea, mostly because I don't see the
>> distinction between the newsgroup and this mailing list
>   ^^^

> Funnily enough, I don't see much of a distinction between comp.mail.mutt
> and [EMAIL PROTECTED] Maybe it's a "usenet thing".

> What do you think ?

Not reading those, I'm not sure.  Usenet tends to attract more basic
questions from beginners, at least at first, and mailing lists tend to
have slightly more in-depth discussions, at least for most of the
technical topics I'm aware of where I read both the newsgroups and the
mailing list (comp.lang.perl.* vs. perl5-porters is a great example).

If we were swamped by basic questions that might have better been dealt
with in Usenet, I could see the point of that sort of distinction, but it
really doesn't feel to me like that's currently the case here.

-- 
Russ Allbery ([EMAIL PROTECTED]) 

Rumours (was: Re: Recipe For A Good Book On Qmail)

[Markus Stumpf]

On Wed, May 31, 2000 at 03:36:32PM -0700, Chin Fang wrote:
> An example (which Dr. Bernstein has waned in qmail-smtpd man page in
> subtle ways): qmail-smtpd in general is quite small - 1.5 MB or less.
> However, if a newbie ISP admin comes in and slaps up a big rcpthosts
> (rather than a morercpthosts in cdb format), then qmail-smtpd can be
> as big as say 10MB or bigger, combined with high CPU utliization!
> 
> To understand this, one needs to read the source code of both
> qmail-smtpd.c and control.c, and see what control_readfile() (a linear
> search) does.

Ok, we have a "huge" rcpthosts file (no "morercpthosts")
   about 21,700 lines, 350 KB
This makes about 10,000 domains, 2 lines for each domain, usual setup.
The smtpd has a RSS of about 1.5 MB.
To go for 10 MB the rcpthosts file would hold about 2.5 million domains.
Not a task for a single machine and a newbie ISP admin I'd say.

We have about 45,000 - 50,000 incoming smtp connects per day.
Each incoming messages generates an extra local delivery to an awk
script to log additional accounting information.

The machine is a P686/300MHz, 128 MB RAM running FreeBSD 2.2.2-R
and besides SMTP relay (this is a "dispatcher" mailer) it also runs
"dial smtp" deliveries for some 50 hosts every 3 minutes via serialsmtp
(and yes, we have ETRN also).

I have just checked the monitoring data for the last month and the CPU
load is rarely, really rarely higher than 1.5 in a 15 minutes average
(taken from "uptime", monitored every 3 minutes).

So please, measure, don't speculate.

\Maex

-- 
SpaceNet GmbH |   http://www.Space.Net/   | Stress is when you wake
Research & Development| mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 |  Tel: +49 (89) 32356-0| realize you haven't
D-80807 Muenchen  |  Fax: +49 (89) 32356-299  | fallen asleep yet.

Re: SMTP e Qmailadmin problems

[Markus Stumpf]

On Wed, May 31, 2000 at 07:22:00PM -0300, Edilmar Alves wrote:
> I'd like to solve the following problems:
> 1. SMTP: I configured tcp.smtp like this, to accept
> e-mails only for these IP subnets:
> 192.168.0.:allow,RELAYCLIENT=""
> 192.168.1.:allow,RELAYCLIENT=""
> 200.241.184.:allow,RELAYCLIENT=""
> However, I entered from other ISP, with
> address 200.212.255.25 and SMTP sents
> my email. I boot Linux but the same behaviour
> continues to occurr.

1a) you probably want an additional line
:allow
in tcp.smtp
1b) you have compiled tcp.smtp into a CDB file using tcprules?
1c) you have told tcpserver to use this CDB via the -x switch?

Can't say anything to the other questions, as I don't use that tool.

\Maex

-- 
SpaceNet GmbH |   http://www.Space.Net/   | Stress is when you wake
Research & Development| mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 |  Tel: +49 (89) 32356-0| realize you haven't
D-80807 Muenchen  |  Fax: +49 (89) 32356-299  | fallen asleep yet.

Internet mail survey: How to get info about large email site ?

[Le Dinh Long]

Hello,
I'm making a survey about internet mail (focus on number of large sites): 
which kind of servers used, amount of accounts hosted, etc. I don't know 
how to get this info, the only thing I can is look into the full header of 
the mails. I don't know that info either critical or not. Anybody here can 
point me where and how to find some pieces of info for this ? If you are 
administrators of that sites, can you give me some advices ?
I'm working for an ISP which would like to switch from Netscape Messaging 
to qmail.

Thanks in advance.