qmail Digest 26 Sep 2000 10:00:01 -0000 Issue 1135
Topics (messages 49358 through 49436):
forwarding the subject of an incoming mail to another address
49358 by: pgracia.amira.es
qmail behind a firewall
49359 by: Jos Okhuijsen
Accounts and redirect
49360 by: J.J.Gallardo
49375 by: David Dyer-Bennet
49378 by: J.J.Gallardo
49379 by: Dave Sill
49406 by: David Dyer-Bennet
49435 by: J.J.Gallardo
Re: mini-qmail
49361 by: Raul Miller
49436 by: Oliver Koch
Re: qmail-mrtg - HOWTO?
49362 by: Peter Green
49365 by: Robin S. Socha
49366 by: Peter Green
49380 by: Robin S. Socha
Re: lock file error's
49363 by: Philip Priest
Re: Postfix: This release introduces DSN style notification of bounced or delayed
mail, as per RFC 1894.
49364 by: Peter van Dijk
49369 by: Michael T. Babcock
49376 by: Stephen Bosch
49377 by: Michael T. Babcock
49385 by: Raul Miller
49389 by: Dave Sill
49391 by: Michael T. Babcock
49394 by: Raul Miller
49410 by: Michael T. Babcock
49414 by: Raul Miller
Re: Help with Local Relaying
49367 by: Dave Sill
Re: dotqmail scripting
49368 by: Dave Sill
daemontools
49370 by: Frans Haarman
49372 by: Marc Knoop
49381 by: Dave Sill
49382 by: Dave Sill
49386 by: Felix von Leitner
49392 by: Andy Bradford
49393 by: Marc Knoop
49395 by: Bruno Wolff III
49398 by: Vince Vielhaber
49418 by: Stephen Bosch
49420 by: Ben Beuchler
Re: tcpserver error
49371 by: Dave Sill
qmail + LDAP + IMAP
49373 by: Pierre-Julien Grizel
49399 by: Alexander Jernejcic
Converting to vpopmail?
49374 by: Albert Hopkins
Re: qmail-scanner + which antivirus ?
49383 by: Rainer Link
49432 by: Martin Lesser
Re: spooled messages take too long to send
49384 by: Dave Sill
Auto Responder
49387 by: Mike Jimenez
49390 by: Mike Jimenez
49396 by: Mike Jimenez
49401 by: Dave Sill
49402 by: Robin S. Socha
49403 by: Aaron L. Meehan
49424 by: Mike Jimenez
49425 by: markd.bushwire.net
Re: double bounce policy
49388 by: Bruno Wolff III
Installing autoresponder
49397 by: Allama Hicham
Some troubles
49400 by: Gustavo Schroeder
49407 by: dG
49409 by: Gustavo Schroeder
49412 by: Charles Cazabon
49415 by: Chris Johnson
Re: Completely removing qmail and reinstalling again
49404 by: Brian Reichert
Re: Some troubles]
49405 by: Gustavo Schroeder
maildir problem
49408 by: Luis Bezerra
49413 by: Andy Bradford
Qmail, vpop, and MySQL
49411 by: Andy Abshagen
49417 by: Daniel Augusto Fernandes
delivery to ( /var/spool/mail/$USER ) mbox when $HOME is unavailable
49416 by: Matt Howell
Internal DNS issues/550 cannot route to sender
49419 by: John P
49422 by: markd.bushwire.net
49423 by: John P
Re: qmail + Majordomo???
49421 by: Ramzi Abdallah
qmail internals documentation
49426 by: Ihnen, David
49427 by: Peter van Dijk
49428 by: markd.bushwire.net
49429 by: Peter van Dijk
49430 by: Ihnen, David
urgent help required
49431 by: reach_prashant.zeenext.com
urgent help required (fwd)
49433 by: reach_prashant.zeenext.com
49434 by: reach_prashant.zeenext.com
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 use qmail+vpopmail+qmailadmin. What I am trying to do is to set up an email account [EMAIL PROTECTED] so when it receives a new mail, it extracts the subject and forwards it to another mail address [EMAIL PROTECTED] (mail to sms gateway).
I have a .qmail-user file with the following line (that works in the console):
| /bin/grep -e From -e Subject | /var/qmail/bin/qmail-inject [EMAIL PROTECTED]
but this is what I am getting
969880946.483051 delivery 193: deferral: qmail-inject:_fatal:_read_error/
969880946.483064 status: local 0/10 remote 0/20
What am I doing wrong?
--------------------------------------------------------------------------------
Paco Gracia
Director Técnico
Amira Sistemas
|
Hi there,
We run qmail on a box behind a firewall,
another, lower priority, external smtp server knows it's way
through and can deliver to our machine,
bounces however
go to the return adress, and double
bounce.
The DNS MX priority is 10 for the machine behind the
firewall, and 20 for the public machine.
The return address is always behindSmpt.domain.com,
both using SMTPserver behind the firewall as well as
an
SMTPserver in the public.
Questions: Is the return-address always constructed
from
the MX records in the DNS?
Is there a way to fix the returnaddress to point to the
beforeFirewall box? (other than fixing the DNS)
Jos
|
Hello,
I need to manage one virtual-domains (domain1.com) in this way:
1) All the accounts *master (postmaster,hostmaster,webmaster,...)
redirect to [EMAIL PROTECTED]
(No problem with .qmail-postmaster, etc)
2) Any other account (mike, support, ..etc) route via 'smtproutes' to a
specific host
But if smtproutes contain --> domain1.com:machine.domain1.com , then all
incoming mail, include *master are queued to send to
machine.domain1.com. Any ideas?
J.J.Gallardo <[EMAIL PROTECTED]> writes on 25 September 2000 at 14:41:22 +0200
> Hello,
>
> I need to manage one virtual-domains (domain1.com) in this way:
> 1) All the accounts *master (postmaster,hostmaster,webmaster,...)
> redirect to [EMAIL PROTECTED]
> (No problem with .qmail-postmaster, etc)
> 2) Any other account (mike, support, ..etc) route via 'smtproutes' to a
> specific host
> But if smtproutes contain --> domain1.com:machine.domain1.com , then all
> incoming mail, include *master are queued to send to
> machine.domain1.com. Any ideas?
You want some treated as local, and some not. This is slightly
tricky.
I see two approaches.
#1, can you use smtproutes to send everything to the other machine,
and then on *that* machine grab the *master accounts and forward them
back?
#2, you can use .qmail-default to grab everything that isn't
specifically handled by other .qmail files and have it delivered to a
maildir. Then use maildirsmtp (or maildirqmtp) in cron to send those
on over to the actual destination machine.
I haven't needed to split a domain this way, so I could be overlooking
a better option; hasn't sprung to mind yet though.
--
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Photos: http://dd-b.lighthunters.net/
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/
David Dyer-Bennet escribió:
> I see two approaches.
>
> #1, can you use smtproutes to send everything to the other machine, and then
> on *that* machine grab the *master accounts and forward them back?
With this option my boss can kill me. He doesn't aprobe that one mail can go
out and come back (because this domain is trought a isdn line and always look
for cost and price for the client, also, too many spammer send mail to *master
accounts and i want to take the control of them to stop it), but may be a
solution.
> #2, you can use .qmail-default to grab everything that isn't specifically
> handled by other .qmail files and have it delivered to a maildir. Then use
> maildirsmtp (or maildirqmtp) in cron to send those
> on over to the actual destination machine.
I can't find "maildirsmtp" command on my Linux (Suse 6.4-2.2.14). What do this
command?
I'm searching for a solution in the .qmail-default that route the other mails
(no *master) like a smtproute file, but at this moment i can get it.
Thanks so.
"J.J.Gallardo" <[EMAIL PROTECTED]> wrote:
>I need to manage one virtual-domains (domain1.com) in this way:
>1) All the accounts *master (postmaster,hostmaster,webmaster,...)
>redirect to [EMAIL PROTECTED]
>(No problem with .qmail-postmaster, etc)
>2) Any other account (mike, support, ..etc) route via 'smtproutes' to a
>specific host
Add virtualdomains entries like:
[EMAIL PROTECTED]:domain1
[EMAIL PROTECTED]:domain1
[EMAIL PROTECTED]:domain1
>But if smtproutes contain --> domain1.com:machine.domain1.com , then all
>incoming mail, include *master are queued to send to
>machine.domain1.com. Any ideas?
The first three lines in the virtualdomains file above create virtual
*users*. There's no reason to make all of the domain virtual if you
only want to handle a few users.
-Dave
J.J.Gallardo <[EMAIL PROTECTED]> writes on 25 September 2000 at 18:41:18 +0200
> David Dyer-Bennet escribió:
>
> > I see two approaches.
> >
> > #1, can you use smtproutes to send everything to the other machine, and then
> > on *that* machine grab the *master accounts and forward them back?
>
> With this option my boss can kill me. He doesn't aprobe that one mail can go
> out and come back (because this domain is trought a isdn line and always look
> for cost and price for the client, also, too many spammer send mail to *master
> accounts and i want to take the control of them to stop it), but may be a
> solution.
>
> > #2, you can use .qmail-default to grab everything that isn't specifically
> > handled by other .qmail files and have it delivered to a maildir. Then use
> > maildirsmtp (or maildirqmtp) in cron to send those
> > on over to the actual destination machine.
>
> I can't find "maildirsmtp" command on my Linux (Suse 6.4-2.2.14). What do this
> command?
> I'm searching for a solution in the .qmail-default that route the other mails
> (no *master) like a smtproute file, but at this moment i can get it.
Dave Sill, who remembered a useful fact about smtproutes that I had
forgotten, has given you a better suggestion, but for completeness,
maildirsmtp is part of the serialmail package from Dan Bernstein.
--
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Photos: http://dd-b.lighthunters.net/
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/
Dave Sill escribió:
> Add virtualdomains entries like:
>
> [EMAIL PROTECTED]:domain1
> [EMAIL PROTECTED]:domain1
> [EMAIL PROTECTED]:domain1
>
> The first three lines in the virtualdomains file above create virtual
> *users*. There's no reason to make all of the domain virtual if you only
> want to handle a few users.
OK. Tested and running :
I have domain2.com as virtual with accounts (including *master redirect to
[EMAIL PROTECTED] with files .qmail-*)
My "/var/qmail/control/virtualdomains" file :
domain2.com:domain2.com
[EMAIL PROTECTED]:domain2.com
[EMAIL PROTECTED]:domain2.com
My "/var/qmail/control/smtproutes" file:
domain1.com:othermac.domain1.com
Any mail to ""*master""@domain1.com goes to "[EMAIL PROTECTED]
Any mail to ""mike,support,.... @domain1.com"" goes to machine
othermac.domain1.com.
Thank you to all who helps me. (specially to Dave Sill and David Dyer-Bennet)
On Mon, Sep 25, 2000 at 09:50:10AM +0200, [EMAIL PROTECTED] wrote:
> write(1, "to: koch\n", 9) = 9
> munmap(0x40018000, 4096) = 0
> _exit(0) = ?
> qmail-inject: fatal: qq unable to read configuration (#4.3.0)
Ok, so this is happening on the server side.
But, this is a qmail-qmqmc error.
Do you have qmail-qmqpc installed on the server side? That sounds
like your problem. Re-install qmail-queue on the server side.
--
Raul
On Mon, 25 Sep 2000, Raul Miller wrote:
> On Mon, Sep 25, 2000 at 09:50:10AM +0200, [EMAIL PROTECTED] wrote:
> > write(1, "to: koch\n", 9) = 9
> > munmap(0x40018000, 4096) = 0
> > _exit(0) = ?
> > qmail-inject: fatal: qq unable to read configuration (#4.3.0)
>
> Ok, so this is happening on the server side.
>
> But, this is a qmail-qmqmc error.
>
> Do you have qmail-qmqpc installed on the server side? That sounds
> like your problem. Re-install qmail-queue on the server side.
I found a mini-qmail installation kit on
http://www.din.or.jp/~ushijima/mini-qmail-kit.html. Using this kit
gives me a working mini-qmail and is really painless.
After comparing the two installations I saw that it was my fault, I
put the servers name into qmqpservers, not its IP.
Sorry for bothering you with such a stupid misconfiguration, and
thanks for your help,
--
Oliver Koch Registered Linux User 163952
The debate rages on: Is PL/I Bachtrian or Dromedary?
> qmail-mrtg.1.0 gives me:
> /usr/local/mrtg-2/bin/mrtg qmail.mrtg.cfg
> ) in CFG file (qmail.mrtg.cfg) does not make sense
> I cannot claim to be an mrtg expert (au contraire, I don't understand it
> at all), but I've nuked all ")" in this file for good measure and that
> does not change anything, either.
What version of MRTG are you running? I've got this working with 2.8.12;
I've attached my qmail.mrtg.cfg off-list. (Incidentally, it worked basically
out of the box...I'm curious as to the problems you are seeing...)
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
> Is there any hope for me? Am I just thick? Does anyone remember the
> Rubiks Cube, it was easier!
I found that the Rubiks cube and Linux are alike. Looks real confusing
until you read the right book. :-)
(Seen on c.o.l.misc, about the "Linux Learning Curve")
WorkDir: /usr/local/web/docs/admin/mrtg-qmail-two
#############################################################
Title[messages]: ais.cx - Qmail (throughput)
MaxBytes[messages]: 100
AbsMax[messages]: 10000
Options[messages]: gauge
Target[messages]: `/usr/local/bin/qmail-mrtg -4 < /var/log/qmail/current`
PageTop[messages]: <font face=arial size=3><B>ais.cx</B> - Qmail (throughput)</font>
ShortLegend[messages]: Messages
YLegend[messages]: Messages
Legend1[messages]: Total messages
LegendI[messages]: Deliveries:
LegendO[messages]: Attempts:
WithPeak[messages]: ymwd
#-------------------------------------------------------------------
Title[queue-size]: ais.cx - Qmail (queue size)
MaxBytes[queue-size]: 1000
AbsMax[queue-size]: 10000
Options[queue-size]: gauge
Target[queue-size]: `/usr/local/bin/qmail-mrtg-queue`
PageTop[queue-size]: <font face=arial size=3><B>ais.cx</B> - Qmail (queue size)</font>
ShortLegend[queue-size]: Messages
YLegend[queue-size]: Messages
Legend1[queue-size]: Messages
LegendI[queue-size]: Messages:
LegendO[queue-size]: Unprocessed Messages:
WithPeak[queue-size]: ymwd
#-------------------------------------------------------------------
Title[concurrency]: ais.cx - Qmail (concurrency)
MaxBytes[concurrency]: 1000
AbsMax[concurrency]: 10000
Options[concurrency]: gauge
Target[concurrency]: `/usr/local/bin/qmail-mrtg -3 < /var/log/qmail/current`
PageTop[concurrency]: <font face=arial size=3><B>ais.cx</B> - Qmail
(concurrency)</font>
ShortLegend[concurrency]: Concurrency
YLegend[concurrency]: Concurrency
Legend1[concurrency]: Concurrency
LegendI[concurrency]: Local:
LegendO[concurrency]: Remote:
WithPeak[concurrency]: ymwd
#-------------------------------------------------------------------
Title[messstatus]: ais.cx - Qmail (Success/Failures)
MaxBytes[messstatus]: 1000
AbsMax[messstatus]: 10000
Options[messstatus]: gauge
Target[messstatus]: `/usr/local/bin/qmail-mrtg -1 < /var/log/qmail/current`
PageTop[messstatus]: <font face=arial size=3><B>ais.cx</B> - Qmail
(Success/Failures)</font>
ShortLegend[messstatus]: Messages
YLegend[messstatus]: Messages
Legend1[messstatus]: Messages
LegendI[messstatus]: Success:
LegendO[messstatus]: Failures:
WithPeak[messstatus]: ymwd
#-------------------------------------------------------------------
Title[bytes]: ais.cx - Qmail (Bytes Transfered)
MaxBytes[bytes]: 1000
AbsMax[bytes]: 100000000
Options[bytes]: gauge
Target[bytes]: `/usr/local/bin/qmail-mrtg -2 < /var/log/qmail/current`
PageTop[bytes]: <font face=arial size=3><B>ais.cx</B> - Qmail (Bytes
Transfered)</font>
ShortLegend[bytes]: kB
YLegend[bytes]: kB
Legend1[bytes]: kB
LegendI[bytes]: kB:
LegendO[bytes]: kB:
WithPeak[bytes]: ymwd
#-------------------------------------------------------------------
* Peter Green <[EMAIL PROTECTED]> [000925 09:03]:
> > qmail-mrtg.1.0 gives me:
> > /usr/local/mrtg-2/bin/mrtg qmail.mrtg.cfg
> > ) in CFG file (qmail.mrtg.cfg) does not make sense
> > I cannot claim to be an mrtg expert (au contraire, I don't understand it
> > at all), but I've nuked all ")" in this file for good measure and that
> > does not change anything, either.
>
> What version of MRTG are you running?
mrtg-2.8.12
> I've got this working with 2.8.12;
I cannot compile qmail-mrtg under OpenBSD 2.7:
(root@purgatory):(/usr/local/src/Qmail/qmail-mrtg.1.0)# gcc --version
2.95.2
(root@purgatory):(/usr/local/src/Qmail/qmail-mrtg.1.0)# gcc -o
qmail-mrtg qmail-mrtg.c
qmail-mrtg.c: In function `main':
qmail-mrtg.c:81: too few arguments to function `strncmp'
qmail-mrtg.c:110: too few arguments to function `strncmp'
qmail-mrtg.c:116: too few arguments to function `strncmp'
qmail-mrtg.c:120: too few arguments to function `strncmp'
qmail-mrtg.c:126: too few arguments to function `strncmp'
> I've attached my qmail.mrtg.cfg off-list.
Thanks.
> (Incidentally, it worked basically out of the box...I'm curious as to
> the problems you are seeing...)
I'm cursed. Honest. Now trying this out under Linux...
also sprach rsocha:
> * Peter Green <[EMAIL PROTECTED]> [000925 09:03]:
> > I've got this working with 2.8.12;
>
> I cannot compile qmail-mrtg under OpenBSD 2.7:
> (root@purgatory):(/usr/local/src/Qmail/qmail-mrtg.1.0)# gcc --version
> 2.95.2
> (root@purgatory):(/usr/local/src/Qmail/qmail-mrtg.1.0)# gcc -o
> qmail-mrtg qmail-mrtg.c
> qmail-mrtg.c: In function `main':
> qmail-mrtg.c:81: too few arguments to function `strncmp'
Ick, *really* sloppy programming by the author. He used strncmp (``compare
the first N characters of two strings'') without providing the length
(``N''). Try the attached patch (untested, but believed functional).
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
I hope if dogs ever take over the world and they choose a king, they don't
just go by size, because I bet there are some Chihuahuas with some good
ideas.
(Jack Handey)
--- qmail-mrtg.c.orig Mon Sep 25 09:41:50 2000
+++ qmail-mrtg.c Mon Sep 25 09:42:28 2000
@@ -78,7 +78,7 @@
}
}
- if(!strncmp(argv[1],"-v")) {
+ if(!strncmp(argv[1],"-v",2)) {
printf("%lu.%lu ",seconds, nanoseconds);
printf("%s\n",buff);
}
@@ -107,23 +107,23 @@
}
}
}
- if(!strncmp(argv[1],"-1")) {
+ if(!strncmp(argv[1],"-1",2)) {
printf("%i\n",success);
printf("%i\n",failure);
printf("\n");
printf("\n");
}
- if(!strncmp(argv[1],"-2")) {
+ if(!strncmp(argv[1],"-2",2)) {
printf("%i\n",bytes/1024);
printf("%i\n",bytes/1024);
}
- if(!strncmp(argv[1],"-3")) {
+ if(!strncmp(argv[1],"-3",2)) {
printf("%i\n",local);
printf("%i\n",remote);
printf("\n");
printf("\n");
}
- if(!strncmp(argv[1],"-4")) {
+ if(!strncmp(argv[1],"-4",2)) {
printf("%i\n",success);
printf("%i\n",failure+success);
printf("\n");
* Peter Green <[EMAIL PROTECTED]> [000925 09:46]:
> also sprach rsocha:
> > * Peter Green <[EMAIL PROTECTED]> [000925 09:03]:
> > > I've got this working with 2.8.12;
> >
> > I cannot compile qmail-mrtg under OpenBSD 2.7:
> Ick, *really* sloppy programming by the author. He used strncmp (``compare
> the first N characters of two strings'') without providing the length
> (``N'').
Yup.
> Try the attached patch (untested, but believed functional).
You rule supreme. It finally works. Way cool!
Thanks!
Robin
running qmail 1.03 on redhat 6.2.
im getting these lock file errors:
supervise fatal: unable to acquire log/supervise/lock: temporary failure
supervise fatal: unable to acquire qmail/send/supervise/lock: temporary
failure
supervise fatal: unable to acquire qmail-smtpd/supervise/lock: temporary
failure
any pointers as to why this is occuring? did i miss a step in the
install??
phil
On Mon, Sep 25, 2000 at 09:34:27AM +0200, Olivier M. wrote:
> As seen on freshmeat.net this morning...
> Any chance so see such improvments to qmail comming?
No, because DSN is not an improvement. It's a bug. It is a misdesigned
fix for a problem that can be solved much better with VERP.
Greetz, Peter.
--
[ircoper] [EMAIL PROTECTED] - Peter van Dijk / Hardbeat
[student] Undernet:#groningen/wallops | IRCnet:/#alliance
[developer] EFnet:#qmail _____________
[disbeliever - the world is backwards] (__VuurWerk__(--*-
> On Mon, Sep 25, 2000 at 09:34:27AM +0200, Olivier M. wrote:
> > As seen on freshmeat.net this morning...
[ed. (Postfix now uses notifications as per RFC 1894) -- because of long
Subject: ]
> > Any chance so see such improvments to qmail comming?
>
> Depends on whether you actually consider this an "improvement" as opposed
to
> an invasion of privacy.
Please explain why you feel that RFC 1894 describes an invasion of privacy
(or, to be fair, a potential one).
Part of 1894 is to try and track failed deliveries on mailing lists (in a
less efficient way than Dan's solution, mind you).
A major part of the goals of 1894 from my reading of it is to allow the
reporting of potential error conditions from different mailing
infrastructures operating on the other side of SMTP gateways (which there
are a lot of).
Peter van Dijk wrote:
> On Mon, Sep 25, 2000 at 09:34:27AM +0200, Olivier M. wrote:
> > As seen on freshmeat.net this morning...
> > Any chance so see such improvments to qmail comming?
>
> No, because DSN is not an improvement. It's a bug. It is a misdesigned
> fix for a problem that can be solved much better with VERP.
What is DSN, anyway? Can someone explain?
/sarcasm
WHAT AM I MISSING?
sarcasm/
-Stephen-
Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
pages at least).
Basically it tries to solve issues that VERP does not. It doesn't solve the
bouncing issue as well as VERP, but it tries to establish a standard way to
communicate between MTAs and MUAs about whether a message has been
successful and, if it was not, why and according to which MTA.
> Peter van Dijk wrote:
>
> > On Mon, Sep 25, 2000 at 09:34:27AM +0200, Olivier M. wrote:
> > > As seen on freshmeat.net this morning...
> > > Any chance so see such improvments to qmail comming?
> >
> > No, because DSN is not an improvement. It's a bug. It is a misdesigned
> > fix for a problem that can be solved much better with VERP.
>
> What is DSN, anyway? Can someone explain?
On Mon, Sep 25, 2000 at 12:30:03PM -0400, Michael T. Babcock wrote:
> Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
> pages at least).
>
> Basically it tries to solve issues that VERP does not. It doesn't solve the
> bouncing issue as well as VERP, but it tries to establish a standard way to
> communicate between MTAs and MUAs about whether a message has been
> successful and, if it was not, why and according to which MTA.
The right way to support this, in qmail, would be to write a small little
program you can drop into your .qmail file, to report successful delivery.
--
Raul
Raul Miller <[EMAIL PROTECTED]> wrote:
>On Mon, Sep 25, 2000 at 12:30:03PM -0400, Michael T. Babcock wrote:
>> Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
>> pages at least).
>>
>> Basically it tries to solve issues that VERP does not. It doesn't solve the
>> bouncing issue as well as VERP, but it tries to establish a standard way to
>> communicate between MTAs and MUAs about whether a message has been
>> successful and, if it was not, why and according to which MTA.
>
>The right way to support this, in qmail, would be to write a small little
>program you can drop into your .qmail file, to report successful delivery.
Something like qreceipt?
-Dave
> On Mon, Sep 25, 2000 at 12:30:03PM -0400, Michael T. Babcock wrote:
> > Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
> > pages at least).
>
> The right way to support this, in qmail, would be to write a small little
> program you can drop into your .qmail file, to report successful delivery.
Part of the point seems to be having a standardised notification system,
which, if its functional, is a good idea. About a third of the way down the
RFC they have a nice ASCII drawing of what happens if you have a mail system
running behind a gateway and how the message notifications are handled if
the necessary hosts support DSN.
It seems somewhat bulky (lots of long fields -- looks a lot like a message
header), but (fairly) functional.
I'd like to see some of it implemented just to be able to say that qmail
continues to adhere to the useful RFCs ...
On Mon, Sep 25, 2000 at 12:30:03PM -0400, Michael T. Babcock wrote:
> > > Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
> > > pages at least).
[response]:
> > The right way to support this, in qmail, would be to write a small little
> > program you can drop into your .qmail file, to report successful delivery.
On Mon, Sep 25, 2000 at 01:54:41PM -0400, Michael T. Babcock wrote:
> Part of the point seems to be having a standardised notification
> system, which, if its functional, is a good idea.
Maybe.
> About a third of the way down the RFC they have a nice ASCII drawing
> of what happens if you have a mail system running behind a gateway
> and how the message notifications are handled if the necessary hosts
> support DSN.
This diagram indicates that if qmail supports DSN, it would support
DSN at the interface between qmail and some non-smtp compliant MTA.
If that's really the case, it's not a qmail issue at all.
--
Raul
> On Mon, Sep 25, 2000 at 12:30:03PM -0400, Michael T. Babcock wrote:
> > Read http://www.faqs.org/rfcs/rfc1894.html (honestly, read the first few
> > pages at least).
>
> The right way to support this, in qmail, would be to write a small little
> program you can drop into your .qmail file, to report successful delivery.
Part of the point seems to be having a standardised notification system,
which, if its functional, is a good idea. About a third of the way down the
RFC they have a nice ASCII drawing of what happens if you have a mail system
running behind a gateway and how the message notifications are handled if
the necessary hosts support DSN.
It seems somewhat bulky (lots of long fields -- looks a lot like a message
header), but (fairly) functional.
I'd like to see some of it implemented just to be able to say that qmail
continues to adhere to the useful RFCs ...
On Mon, Sep 25, 2000 at 01:46:23PM -0400, Dave Sill wrote:
> Something like qreceipt?
Similar, yes. But for proper DSN you need to be talking to
a remote mail gateway, and the response needs to say whether
or not the remote gateway accepted the message.
--
Raul
"Edward Carr" <[EMAIL PROTECTED]> wrote:
>Here are my config files ... Edited for anonymity ...
>
>/var/qmail/control/defaultdomain:
>domain.net
Gimme a break...
>/etc/init.d/qmail:
>---- snip! ----
> if [ -x /usr/local/bin/tcpserver ]; then
> /usr/local/bin/tcpserver -x /etc/tcp.smtp.cdb -v -u 7001 -g
>7001 0 smtp \
> /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger
>smtpd 3 &
> echo "qmail starting"
> fi
>---- snip! ----
>
>Any Ideas ???
Yeah: qmail isn't running. Your startup script doesn't run
qmail-start, so the messages coming in via SMTP are just sitting in
the queue.
-Dave
Eric Cox <[EMAIL PROTECTED]> wrote:
>Peter Samuel wrote:
>>
>> On Thu, 21 Sep 2000, Eric Cox wrote:
>> >
>> > Mail is delivered to [EMAIL PROTECTED]
>> >
>> > ~alias/.qmail-user1 contains:
>> >
>> > |script that writes a username into ~alias/.qmail-user2
>> > &user2
>>
>> It would work but it's a woefully inefficient way to do it. Especially
>> as qmail comes with a mechanism to do just this - /var/qmail/bin/forward.
>>
>> ~alias/.qmail-user1 contains:
>>
>> | forward `some_script_that_generates_new_addess(es)`
>>
>> See the man page.
>
>The man page says that forward is a wrapper around qmail-queue.
>Doesn't that mean the message makes two complete trips into and
>out of the queue, while the method I described is handled
>completely within qmail-local?
>
>Granted I haven't looked at the source yet, but what have I
>missed?
You missed the fact that qmail-local calls qmail-queue to handle
forwards.
-Dave
I see constant disk activity when using daemontools to
monitor qmail.
Is this bad for my hd ? Someone told me changes
of my disks dying with constat disk activity are
much higher!
regards
--Frans
On Mon, 25 Sep 2000, Frans Haarman wrote:
> I see constant disk activity when using daemontools to
> monitor qmail.
> Is this bad for my hd ? Someone told me changes
> of my disks dying with constat disk activity are
> much higher!
Funny you mentioned that. I just noticed the same thing! The HD activity
light blips every one or two seconds. I restarted the box without loading
svscan (which loads dnscache, tinydns and qmail) - all is quiet. In the
previous week, I had not installed qmail, and there was much less disk activity.
And I don't even have any users configured in qmail yet - in fact, a message
hasn't even gone through yet!
Can anyone tell me what it's doing?
../mk
[EMAIL PROTECTED] wrote:
>Funny you mentioned that. I just noticed the same thing! The HD activity
>light blips every one or two seconds. I restarted the box without loading
>svscan (which loads dnscache, tinydns and qmail) - all is quiet.
svscan polls the service directory every five seconds.
>And I don't even have any users configured in qmail yet - in fact, a message
>hasn't even gone through yet!
What about DNS activity? dnscache does lots of logging.
-Dave
"Frans Haarman" <[EMAIL PROTECTED]> wrote:
>I see constant disk activity when using daemontools to
>monitor qmail.
>Is this bad for my hd ?
Yeah, the same way running your car's engine is bad for it. If you
want your disk drive to last forever, you'll need to power it off. :-)
>Someone told me changes
>of my disks dying with constat disk activity are
>much higher!
Well, yeah, that's true too. The more you drive your car, the faster
the engine wears out.
Luckily, disks are way cheaper than cars. :-)
-Dave
> I see constant disk activity when using daemontools to
> monitor qmail.
I don't.
Get yourself a real operating system where the disk cache actually
works. svscan does read-only accesses to /services or wherever you
configured it to look. If that touches your disk each time, your OS
sucks or you have way too little RAM in your machine.
I suggest Linux.
Felix
On Mon, 25 Sep 2000 16:33:21 +0200, "Frans Haarman" wrote:
> I see constant disk activity when using daemontools to
> monitor qmail.
It is possible that the programs being spawned are exiting, in which
case supervise will start another copy. This could be due to any
number of things. For example, if it is unable to lock the directory it
will die and then start another. Unless you start svscan from the
command line you will probably not see these error message since they
get sent to stdout/stderr. One thing you could do is run "ps -ef" and
watch to see if your daemons such as dnscache, tinydns, qmail-send are
already running before starting svscan. Launch svscan from the command
line and not a script, etc... If they are already running it is likely
that another copy is trying to start up ad infinitum.
Andy
On Mon, 25 Sep 2000, Felix von Leitner wrote:
> > I see constant disk activity when using daemontools to
> > monitor qmail.
>
> I don't.
>
> Get yourself a real operating system where the disk cache actually
> works. svscan does read-only accesses to /services or wherever you
> configured it to look. If that touches your disk each time, your OS
> sucks or you have way too little RAM in your machine.
Well, as I mentioned earlier, the blipping of the HDD activity light began only
after I installed qmail (was fine with dnscache & tinydns before). I can't see
it being a config issue, as I have only installed the base services as per the
inter7.com documentation.
I was under the impression that FreeBSD was a decent OS and that 256MB of RAM
would do the trick for the few services I am running. What are you running
Frans?
../mk
On Mon, Sep 25, 2000 at 04:33:21PM +0200,
Frans Haarman <[EMAIL PROTECTED]> wrote:
> I see constant disk activity when using daemontools to
> monitor qmail.
> Is this bad for my hd ? Someone told me changes
> of my disks dying with constat disk activity are
> much higher!
If they are making noise because log files are getting updated, than something
might not be working properly. You might want to look at what processes
are running and see if supervise is constantly trying to restart something
(e.g. multilog, dnscache) every few seconds.
On Mon, 25 Sep 2000, Felix von Leitner wrote:
> > I see constant disk activity when using daemontools to
> > monitor qmail.
>
> I don't.
>
> Get yourself a real operating system where the disk cache actually
> works. svscan does read-only accesses to /services or wherever you
> configured it to look. If that touches your disk each time, your OS
> sucks or you have way too little RAM in your machine.
Not necessarily. I had constant disk activity[1] and after digging thru
the logs of the various services I found an unable to bind problem with
one of the services. I had missed an alias in my startup scripts - had
nothing to do with ram or a bad os.
> I suggest Linux.
I don't.
Vince.
[1] a cycling of disk activity to be more precise.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net
128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Andy Bradford wrote:
>
> On Mon, 25 Sep 2000 16:33:21 +0200, "Frans Haarman" wrote:
>
> > I see constant disk activity when using daemontools to
> > monitor qmail.
>
> It is possible that the programs being spawned are exiting, in which
> case supervise will start another copy. This could be due to any
> number of things. For example, if it is unable to lock the directory it
> will die and then start another. Unless you start svscan from the
> command line you will probably not see these error message since they
> get sent to stdout/stderr. One thing you could do is run "ps -ef" and
> watch to see if your daemons such as dnscache, tinydns, qmail-send are
> already running before starting svscan. Launch svscan from the command
> line and not a script, etc... If they are already running it is likely
> that another copy is trying to start up ad infinitum.
*sounds familiar*
Okay... my turn!
All together now...
"What do the logs say?"TM
(svscan ails silently... =) )
-Stephen-
On Mon, Sep 25, 2000 at 03:49:14PM -0600, Stephen Bosch wrote:
> *sounds familiar*
>
> Okay... my turn!
>
> All together now...
>
> "What do the logs say?"TM
>
> (svscan ails silently... =) )
I recommend whoever it is that is doing the lovely qmail shirts (I'll be
ordering mine shortly!) should do one that says "What Do The Logs
Say?(tm)". I know I would buy one...
Ben
--
Ben Beuchler [EMAIL PROTECTED]
MAILER-DAEMON (612) 321-9290 x101
Bitstream Underground www.bitstream.net
"Mark Lo" <[EMAIL PROTECTED]> wrote:
>my startup script in /var/qmail/supervise/qmail-smtpd/run file are as follows:
>
>#!/bin/sh
>QMAILDUID=`id -u qmaild`
>NOFILESGID=`id -u qmaild`
>exec /usr/local/bin/softlimit -m 4000000 \
> /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
> -u $QMAILDUID -g $NOFILESGID 0 smtp \
> /var/qmail/bin/qmail-smptd 2>&1 > /dev/null &
^
The '&' doesn't belong there. ----------------------|
-Dave
Hi,
I currently use qmail + ldap + qmail-pop3d very intensively using NRG4U
patch.
I'd like, however, to open an IMAP access to my server.
Does anyone have IMAP+LDAP solutions ?....
Thanks,
P.-J.
hi,
> Does anyone have IMAP+LDAP solutions ?....
try http://www.inter7.com/courierimap/
;) a
==============================================
Alexander Jernejcic
email:[EMAIL PROTECTED]
begin LOVE-LETTER-UND-NIX-DAZUGELERNT.txt.vbs
I am a Signature, not a Virus!
end
==============================================
I just wanted to see what your opinions are on converting a virtual domain
to vpopmail.
I while back I was given the task of setting up a virtual domain, we'll call
virtual.domain.com. I was fairly new to Qmail, so this is what I did.
Created a unix account 'virtual'.
For each 'user' in virtual, create an account virtual.user. Create file
~virtual/.qmail-user with contents 'virtual.user'
This works fine (well, actually there are some issues, for example Linux's
chown doesn't like '.' in usernames). However I recently found out about
vpopmail and I think it might be more ideal than having a lot of user
accounts on our system.
The problem is that I'd like to convert virtual.domain.com. There's a lot
of accounts to convert, and I'm just trying to get an idea what the
difficulties/gotchas are. I don't want to have to change anything on the
clients. Is this possible/practical?
--albert
Martin Lesser wrote:
> > Just tried to use it with AVP and sweep : both returns a
> > X-Qmail-Scanner-0.90: corrupt scanner/resource problems - exit status 256
> > in the logfile...
> >
> > If you are using qmail-scanner, could you please tell me which
> > program is working well, and if is free ? Thanks in advance,
Well, several ppl reported problems with AVP/Linux and AvpDaemon to the
AMaViS-user mailinglist. We discovered problems when
/lib/libnss_compat.so.1 is missing (it comes with nssv1.rpm on SuSE
Linux, which should be installed to execute glibc 2.0 programs in glibc
2.1 environments). And I was in contact with the developer regarding
this problem.
>
> I use AvpDaemon and it works very well after a little patch of
> sub-avp.pl
Martin, you should send it to Jason :)
> Your problems seem to result of a perhaps misconfigured AvpLinux or
> AvpDaemon. If you use the trial-version of avp you may run into problems
> due to the "semi"-automatic tests done by avp.
Well, Martin, some more details on this issue could be useful? (what are
"semi"-automatic tests)
Jason, if you need more information, please feel free to contact me :-)
cheers, Rainer
--
Rainer Link | Member of Virus Help Munich (www.vhm.haitec.de)
[EMAIL PROTECTED] | Developer of A Mail Virus Scanner (amavis.org)
[EMAIL PROTECTED] | Founder of Linux AntiVirus Project (lavp.sourceforge.net)
Rainer Link <[EMAIL PROTECTED]> writes:
> > I use AvpDaemon and it works very well after a little patch of
> > sub-avp.pl
> Martin, you should send it to Jason :)
Done - some weeks ago :-) The patch concerned the behaviour of
AvpDaemon, not AvpLinux.
> > Your problems seem to result of a perhaps misconfigured AvpLinux or
> > AvpDaemon. If you use the trial-version of avp you may run into problems
> > due to the "semi"-automatic tests done by avp.
>
> Well, Martin, some more details on this issue could be useful? (what are
> "semi"-automatic tests)
If you start scanning a file|directory without a valid
registration-key-file you are prompted "Cancel scan process" and have to
type "No" to continue. If you have a valid key-file the scan is done
without this question.
Martin
Doug Balmer <[EMAIL PROTECTED]> wrote:
>Someone replied but somehow I've lost the email...
http://www.ornl.gov/its/archives/mailing-lists/qmail/2000/09/msg01488.html
>I'm sending from host1 direct to host2's SMTP server ie
>from host1 -> dougb-$i@host2
How? Your script on host1 talks SMTP directly to host2?
>When I used the inject command, it completed instantly.
>The command used was
>
>echo "This is a test" | /var/qmail/bin/qmail-inject -fdougb-sender@host1 $s
>
>Where $s is "dougb-1@host1 dougb-2@host1 dougb-3@host1 ... dougb-2500@host1"
>
>So far it has delivered 1600 of the 2500 emails in over 2 days!
I repeat: On host1, What Do The Logs Say? (tm) Any clues as to why
deliveries aren't happening faster? What's the typical delay between
receipt of a message from host2 and local delivery?
Also, what MTA is host1 running? What is concurrencyremote on host2?
How many qmail-remote processes do you have running while these
messages are being delivered?
-Dave
Hello
Im trying to setup an Autoresponder and it does not work
I add this line into my .qmail-crusstars
And then my mail does not get delivered to the email box and no auto
responder.
| /usr/local/bin/autorespond 10000 20 crusstars autolog
Is this the right way to setup autoresonder or are there differrent
ways.
Thanks
Mike
Hello
Im trying to setup an Autoresponder and it does not work
I add this line into my .qmail-crusstars
And then my mail does not get delivered to the email box and no auto
responder.
| /usr/local/bin/autorespond 10000 20 crusstars autolog
Is this the right way to setup autoresonder or are there differrent
ways.
Thanks
Mike
Is there anyone that can help us out?
Thanks
Mike
Subject:
RE: Auto Responder
Date:
Mon, 25 Sep 2000 14:04:27 -0400
From:
"Solapurkar, Sudheer" <[EMAIL PROTECTED]>
To:
"'Mike Jimenez'" <[EMAIL PROTECTED]>
Hi Mike,
If you successfully resolve this, can you let me know the solution ? I
have
the same problem.
Thanks.
Sudheer
> -----Original Message-----
> From: Mike Jimenez [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, September 25, 2000 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: Auto Responder
>
> Hello
> Im trying to setup an Autoresponder and it does not work
> I add this line into my .qmail-crusstars
> And then my mail does not get delivered to the email box and no auto
> responder.
>
> | /usr/local/bin/autorespond 10000 20 crusstars autolog
>
>
> Is this the right way to setup autoresonder or are there differrent
> ways.
> Thanks
> Mike
>
Mike Jimenez <[EMAIL PROTECTED]> wrote:
>Im trying to setup an Autoresponder and it does not work
>I add this line into my .qmail-crusstars
>And then my mail does not get delivered to the email box and no auto
>responder.
>
>| /usr/local/bin/autorespond 10000 20 crusstars autolog
>
>Is this the right way to setup autoresonder or are there differrent
>ways.
That depends upon what the autorespond script does...
-Dave
* Mike Jimenez <[EMAIL PROTECTED]> [000925 15:04]:
> Is there anyone that can help us out?
I use http://qmail.wwwservice.to/autoreply_1.1.tar.gz and it works. Nice
webinterface, too.
*clicketyclick*
http://em.ca/~bruceg/qmail-autoresponder/current/qmail-autoresponder-0.93.tar.gz
works, too.
*clicketyclick*
And so does http://www.netmeridian.com/e-huss/autorespond.tar.gz (MySQL
does not work with my version of MySQL under OpenBSD, though :-().
*What* exactly are you using?
Quoting Mike Jimenez ([EMAIL PROTECTED]):
> Is there anyone that can help us out?
> Thanks
I don't know, what did you do, set up an auto-sender instead to flood
the list with requests? It seems like your auto-sender defaults to
sending the same thing every 15 minutes if no reply is received, so
I'll help out and respond.
> > | /usr/local/bin/autorespond 10000 20 crusstars autolog
My psychic powers are lagging today, probably not enough coffee!
For the life of me I can't seem to find out the contents of
/usr/local/bin/autorespond.
> > Is this the right way to setup autoresonder or are there differrent
Hmm, I'm also having trouble fetching your logfiles from the ether.
It's very likely the reason they aren't being delivered are in there,
if only we hadn't run out of Columbian coffee :-/
Aaron
In refference to my message earlier about setting up my auto responder
.I have had 0 luck in finding anyone that can seem to help. I was
wondering if there was someone who could lead me in the right direction
to finding some good documentation on how to set these things up.
Thanks
Mike
> -----Original Message-----
> From: Mike Jimenez [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, September 25, 2000 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: Auto Responder
>
> Hello
> Im trying to setup an Autoresponder and it does not work
> I add this line into my .qmail-crusstars
> And then my mail does not get delivered to the email box and no auto
> responder.
>
> | /usr/local/bin/autorespond 10000 20 crusstars autolog
>
>
> Is this the right way to setup autoresonder or are there differrent
> ways.
> Thanks
> Mike
>
On Mon, Sep 25, 2000 at 03:51:29PM -0700, Mike Jimenez wrote:
> In refference to my message earlier about setting up my auto responder
> .I have had 0 luck in finding anyone that can seem to help. I was
> wondering if there was someone who could lead me in the right direction
> to finding some good documentation on how to set these things up.
It would be kinda helpful if:
a) You stated what you wanted the autoresponder to do
b) You stated what your autorepond program currently does
c) What documentation you relied on to write your autorespond program
(eg, did you read the manpage for dot-qmail, qmail-command and qmail-local?
d) What symptoms you are getting when you deliver to your autoresponder
(hit, the logs will say something when deliveries to programs fail)
Without all of this information we'd be guessing. My guess is that it's
not working...
Oh. I guess it's possible that your /usr/local/bin/autorespond is some
standard program. It's certaintly not part of qmail though so you may need
to find what support is available via the documentation for that program.
Mark.
> Thanks
> Mike
>
>
> > -----Original Message-----
> > From: Mike Jimenez [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, September 25, 2000 1:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: Auto Responder
> >
> > Hello
> > Im trying to setup an Autoresponder and it does not work
> > I add this line into my .qmail-crusstars
> > And then my mail does not get delivered to the email box and no auto
> > responder.
> >
> > | /usr/local/bin/autorespond 10000 20 crusstars autolog
> >
> >
> > Is this the right way to setup autoresonder or are there differrent
> > ways.
> > Thanks
> > Mike
> >
>
>
>
By far most double bounces I see are spam with bogus return addresses
listed for old email addresses here. Those I ignore. Some are for broken
list servers, some of which don't accept bounce messages. Sometimes I
write filter rules for those to forward future crap to their postmaster
and list administrator addresses. Occasionally I spot bad forward files
(that system runs sendmail) that need to be fixed and do something to them
so that mail will get delivered. Sometimes I see stuff where it looks like
a misconfigured browser is being used. I haven't had much luck explaining
that to the end users when I have been able to figure out who was sending
the mail, so I usually don't bother to tell them about it anymore.
On Sat, Sep 23, 2000 at 12:06:13AM +0300,
Jos Okhuijsen <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> What is your policy for double bounces?
> Users come and go, and always seem to leave subscriptions open, and produce bounces.
> Most of these bounces doublebounce.
> Do you write to the postmaster of these domains? (Seems to have no effect. )
> Or just blacklist? (and possible handicap other users?)
> Or just accept the fact that return-addresses usually don't work?
>
> Jos
Hi everyone,
I'm using qmail and POP3 and Unix.
I'don't know how can I' install qmail-autoresponder!
Please help me:)
Allama.
Hy there palls
i'm new to qmail, and you can find this stupid, but anyway there it
goes.
I've sucessfuly installed qmail. it is running properly, and i can send
mail trough the host. but when i try to receive mail (pop3) the problems
begin.
when i initialize the qmail-pop3d it gives me the following message:
[root@localhost]# /etc/rc.d/init.d/qmail-pop3d.init start
hard error
Starting qmail-pop3d...done
the process is there, running.
but when i try to receive mail via netscape (pop3 requisition) the
program returns
the following:
"this user has no $HOME/Maildir"
and while reading the INSTALL.maildir doc, i've found something
interesting.
the doc says
"The system administrator can set up Maildir as the default for
everybody
by creating a maildir in the user home directory and replacing
./Mailbox with ./Maildir/ in /var/qmail/rc. Here's how to set up qmail
to use maildir for your incoming mail:
[root@localhost]# maildirmake /home/user/Maildir
[root@localhost]# echo ./Maildir/ > ~/.qmail
[root@localhost]# chown -R user.user /home/user/Maildir
[root@localhost]# chmod -R 755 /home/user/Maildir
I do ask:
1) for the proper working of qmail-pop3d shouldn't I edit
/var/qmail/defaultdelivery/rc
instead of /var/qmail/rc ?
[root@localhost]# cat /var/qmail/defaultdelivery/rc
#Using qmail-local to deliver messages to ~/Mailbox by default
./Mailbox
[root@localhost]# cat /var/qmail/rc
#!/bin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Mailbox splogger qmail
2) How can i correctly setup qmail-pop3d using Maildir format?
3) What's the difference between Maildir and mbox format? Wich one
is better?
Thanks in advance
Gustavo Schroeder
System Administrator
>
> the process is there, running.
> but when i try to receive mail via netscape (pop3 requisition) the
> program returns
> the following:
> "this user has no $HOME/Maildir"
Run the following command to make the Maildir:
$ /var/qmail/bin/maildirmake /home/username/Maildir
If you don't su to username to run this command then you need to run:
$ chown -R user.user /home/username/Maildir
Ok, now i've the following situation
i've switched both scripts /var/qmail/rc and
/var/qmail/defaultdelivery/rc
-----------------------------------------------------------------------------
[root@localhost]# cat /var/qmail/rc
#!/bin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox [now Maildir] by
default.
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ splogger qmail
------------------------------------------------------------------------------
[root@localhost]# cat /var/qmail/defaultdelivery/rc
# Using qmail-local to deliver messages to ~/Mailbox [now Maildir] by
default.
./Maildir/
------------------------------------------------------------------------------
And i've created the user Maildir with
-----------------------------------------------
[root@localhost]# maildirmake /home/user/Maildir (directory created)
[root@localhost]# echo ./Maildir/>~/.qmail (tree directories created -
cur, new and tmp)
I have restarted the qmail program.
Now when i send a message to a existing user, the qmail-local delivers
the message
to /home/user/Maildir/new/
example of the directory above
-rwx------ 1 guto guto 452 Sep 25 16:32
969910320.1778.anonymous
-rw------- 1 guto guto 422 Sep 25 16:51
969911500.2074.anonymous
-rw------- 1 guto guto 942 Sep 25 16:58
969911898.2135.anonymous
the message is there, and now i've seen the big difference between mbox
format and
Maildir format [wich is a lot better :)]
But, when i ask for netscape to retrieve messages for the user above, it
returns me
the message "this user has no $HOME/Maildir".
I just don't understand. The messages are there in the directory
/home/user/Maildir/new , but why qmail-pop3d returns me that message?
Any help will be apreciated
Thanks in advance
Gustavo Schroeder
System Administrator
Gustavo Schroeder <[EMAIL PROTECTED]> wrote:
> "this user has no $HOME/Maildir"
[...]
> [root@localhost]# cat /var/qmail/defaultdelivery/rc
> #Using qmail-local to deliver messages to ~/Mailbox by default
> ./Mailbox
qmail-pop3d requires Maildir delivery in user home directories. You are
currently using mbox delivery under user home directories. Yes, create
new Maildirs for each user (owned by them, not group-writable), and then
change your default delivery instruction.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
On Mon, Sep 25, 2000 at 05:49:55PM -0300, Gustavo Schroeder wrote:
> But, when i ask for netscape to retrieve messages for the user above, it
> returns me
> the message "this user has no $HOME/Maildir".
> I just don't understand. The messages are there in the directory
> /home/user/Maildir/new , but why qmail-pop3d returns me that message?
How exactly are you running your POP service?
Chris
On Fri, Sep 22, 2000 at 10:12:24AM -0400, Dave Sill wrote:
> "Wagner R. Landgraf" <[EMAIL PROTECTED]> wrote:
>
> >Anybody can tell me how to completely qmail from Linux system, so I
> >can be sure that it's not there anymore?
>
> rm -rf /var/qmail
Note: this will not
- put sendmail back,
- remove the UIDs/GIDs that qmail wants
- remove any user's .qmail files (except ~alias, implicitly).
Hypothetically, if you installed qmail via an RPM, and that RPM's
'uninstall' scripts are up to sniff, it might undo everything.
But that's a very big 'if'.
None of these should be an issue, if it's your intent to put it back...
>
> -Dave
>
--
Brian 'you Bastard' Reichert [EMAIL PROTECTED]
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
Hy there palls
i'm new to qmail, and you can find this stupid, but anyway there it
goes.
I've sucessfuly installed qmail. it is running properly, and i can send
mail trough the host. but when i try to receive mail (pop3) the problems
begin.
when i initialize the qmail-pop3d it gives me the following message:
[root@localhost]# /etc/rc.d/init.d/qmail-pop3d.init start
hard error
Starting qmail-pop3d...done
the process is there, running.
but when i try to receive mail via netscape (pop3 requisition) the
program returns
the following:
"this user has no $HOME/Maildir"
and while reading the INSTALL.maildir doc, i've found something
interesting.
the doc says
"The system administrator can set up Maildir as the default for
everybody
by creating a maildir in the user home directory and replacing
./Mailbox with ./Maildir/ in /var/qmail/rc. Here's how to set up qmail
to use maildir for your incoming mail:
[root@localhost]# maildirmake /home/user/Maildir
[root@localhost]# echo ./Maildir/ > ~/.qmail
[root@localhost]# chown -R user.user /home/user/Maildir
[root@localhost]# chmod -R 755 /home/user/Maildir
I do ask:
1) for the proper working of qmail-pop3d shouldn't I edit
/var/qmail/defaultdelivery/rc
instead of /var/qmail/rc ?
[root@localhost]# cat /var/qmail/defaultdelivery/rc
#Using qmail-local to deliver messages to ~/Mailbox by default
./Mailbox
[root@localhost]# cat /var/qmail/rc
#!/bin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Mailbox splogger qmail
2) How can i correctly setup qmail-pop3d using Maildir format?
3) What's the difference between Maildir and mbox format? Wich one
is better?
Thanks in advance
Gustavo Schroeder
System Administrator
Hello everyone
I use Maildir in my configuration and i receveid this message when I
check my messages:
Unable to open local messages
I verified in my server that the messages are located in in the
Maildir/cur directory.
Are the messages Locked?
What is this mean?
thanks in advance!!!!
Lu'is Bezerra
On Mon, 25 Sep 2000 17:27:17 -0300, Luis Bezerra wrote:
> Unable to open local messages
>
> I verified in my server that the messages are located in in the
> Maildir/cur directory.
What MUA (mail reader) are you using? Most likely it doesn't
understand the Maildir method for storing emails. Please provide more
details.
Andy
OK. I'm starting the process of setting up Qmail to have MySQL as the
background for all mail accounts. The first thing that I need to know
though is can all virtuals point to MySQL? Or is it something that can't be
done? I'm talking like 400+ domains so I need some easier way to manage
users etc without using the flat files.
Thanks in advance.
Andy Abshagen
System Administrator
Data-Vision, Inc.
219-243-8625, 888-925-8625
[EMAIL PROTECTED]
Andy Abshagen wrote:
>
> OK. I'm starting the process of setting up Qmail to have MySQL as the
> background for all mail accounts. The first thing that I need to know
> though is can all virtuals point to MySQL? Or is it something that can't be
> done? I'm talking like 400+ domains so I need some easier way to manage
> users etc without using the flat files.
You should take a look at the qmail+vpopmail package:
http://www.inter7.com/vpopmail/
It has a good virtual support and mysql authentication!
--------------------------------------------------------------------
Daniel Augusto Fernandes (DAF tm) [EMAIL PROTECTED]
GCSNet http://www.gcsnet.com.br/
--------------------------------------------------------------------
Se você não encontra
o sentido das coisas
é porque este não
se encontra, se cria.
Antoine Saint-Exupéry
Is there a nice way to tell qmail-local to deliver to a user's
mbox (/var/spool/mail/$USER) when the user's home directory
($HOME) is unavailable? I was able to make it work by using
qmail-newu and changing the homedir's in /var/qmail/users/assign
but I think that's unmaintainable/unfunctional. I.e., have to run
script for each new user and doesn't use $HOME/dot-qmail files
when $HOME is available...
(I can also see how to change qmail-getpw.c to enable this but
I'd prefer to work within the existing model.)
Thx,
Matt.
PS - User home directories are on their machines and NFS mounted;
when a machine is off for too long (or in an unmountable OS) mail
bounces (after retrying).
PPS - I know I could move everyone's home directories to be local
on the server, but...
I am setting up Qmail, but I'm having some problems delivering to external
sites, (550 errors etc) so I just want to check what I'm doing is possible!
Our domain, ourdomain.com, is setup by our ISP + works fine for WWW. The MX
record will point to 'office.ourdomain.com' which will be the address of our
masquerading firewall, which port-forwards to our Qmail server, as well as
provides net access for a group of 6 Windows PC's. The Qmail server works
fine sending to and from users on the mail machine as well as SMTP/Pop3 from
all 'internal' PC's, as well as providing DNS.
However, I am getting something like '550 cannot route to sender
[EMAIL PROTECTED]' errors when I try to e-mail external sites.
I think this is because our IP is not yet setup and so our internal network
is online through a temporary IP address that doesn't correspond to
'office.ourdomain.com' .. is this the problem? However, even when it is set
up, the machine mail.office.ourdomain.com will not be resolvable from the
internet - only office.ourdomain.com and below. Will this be a problem?
When our IP address is permanent I propose to let internal users access the
mailserver via it's internal hostname, and for external clients to send +
receive mail via the external address of the masq box
'office.ourdomain.com'.
To this end I have given the Qmail box the FQDN of
'mail.office.ourdomain.com' and addr. 10.0.0.6, with BIND set to not
distribute these addresses, so does it matter what FQDN I choose?
Finally, I want everything to come from '[EMAIL PROTECTED]' and so put
ourdomain.com into defaulthost, however local mail is still from
'[EMAIL PROTECTED]' have I done something wrong? Could this tie
in with the 550 problem?
OK That's it, please tell me if I'm heading in the right direction - my
previous *nix experience did not really delve into setting up servers :-)
Many many thanks
John
On Mon, Sep 25, 2000 at 11:05:06PM +0100, John P wrote:
> I am setting up Qmail, but I'm having some problems delivering to external
> sites, (550 errors etc) so I just want to check what I'm doing is possible!
>
> Our domain, ourdomain.com, is setup by our ISP + works fine for WWW. The MX
John.
We need to see unadulterated logs.
> record will point to 'office.ourdomain.com' which will be the address of our
> masquerading firewall, which port-forwards to our Qmail server, as well as
> provides net access for a group of 6 Windows PC's. The Qmail server works
> fine sending to and from users on the mail machine as well as SMTP/Pop3 from
> all 'internal' PC's, as well as providing DNS.
>
> However, I am getting something like '550 cannot route to sender
No. We don't want to hear "I am getting something like", we want to see
unadulterated logs.
> [EMAIL PROTECTED]' errors when I try to e-mail external sites.
> I think this is because our IP is not yet setup and so our internal network
> is online through a temporary IP address that doesn't correspond to
> 'office.ourdomain.com' .. is this the problem? However, even when it is set
> up, the machine mail.office.ourdomain.com will not be resolvable from the
> internet - only office.ourdomain.com and below. Will this be a problem?
Can't tell. Since you're hiding the domain we cannot see what the DNS
says.
> When our IP address is permanent I propose to let internal users access the
> mailserver via it's internal hostname, and for external clients to send +
> receive mail via the external address of the masq box
> 'office.ourdomain.com'.
>
> To this end I have given the Qmail box the FQDN of
> 'mail.office.ourdomain.com' and addr. 10.0.0.6, with BIND set to not
> distribute these addresses, so does it matter what FQDN I choose?
>
> Finally, I want everything to come from '[EMAIL PROTECTED]' and so put
> ourdomain.com into defaulthost, however local mail is still from
> '[EMAIL PROTECTED]' have I done something wrong? Could this tie
> in with the 550 problem?
Can't tell. We have no log entries to look at.
> OK That's it, please tell me if I'm heading in the right direction - my
> previous *nix experience did not really delve into setting up servers :-)
Did your previous experience tell you that log files can be a mine of
information?
Regards.
> > Our domain, ourdomain.com, is setup by our ISP + works fine for WWW. The
MX
>
> We need to see unadulterated logs.
> No. We don't want to hear "I am getting something like", we want to see
> unadulterated logs.
>
OK I get the idea :-)
No logs ATM since I am at home spending the (whole) evening looking up
domains and Qmail info, when I get to work tomorrow I will get the logs
together. I just thought I'd check with the list first to make sure I was
heading in the right direction (eg with domains etc)
Cheers
John
Sorry, Outlook like any other Microsoft product never works properly.
Quoting "Scott D. Yelich" <[EMAIL PROTECTED]>:
>
> On Mon, 25 Sep 2000, Robin S. Socha wrote:
> > And would you kindly restrict your line width to something ~72
> > characters? Thanks.
>
>
> oh, please... please publically flame me too!
>
> Scott
>
>
--------
||Ramzi S. Abdallah
||IT Administrator
||The Australian Centre for Languages
||157 - 161 Gloucester Street
||The Rocks - Sydney 2000
||Australia
||
||Phone: +61 2 9252 3788
||Fax: +61 2 9252 3799
Hay, guys.
I want to make sure I don't email djb without having a real legitimate
question.
Are any of you aware of qmail internal data structure/logic documentation
for the qmail programs?
It sure works nicely, but its a desert in there when you gain your
sustenance from comments so you have a clue what each function is recieving,
doing, and returning.
>From my browsing I have determined there is some extensive array data
structure in memory whose definition is not quite obvious. (to me at least)
So why would I ask such an absurd question?
I'd like to show some people with cranial-rectal syndrome that are busily
reinventing the mail delivery wheel that the back end they already have
programmed can be inserted into qmail's processing.
Instead of going straight from reciept to the delivery queue, it would go
into a processing queue, and hopefully in a manner similar to
qmail-remote/qmail-local rules, a qmail-process queue would then kick off a
various processing filters based on a number of rules. The messages may or
may not be returned to qmail for delivery after processing.
Do you think its possible to insert such logic without changing the whole
flow of qmail?
Its important that I maintain the original envelope, which to my knowledge
will be lost if I try to use .qmail sorts of mail processing functionality.
performance is relevant, so circumventing local delivery would probably be a
good thing as well.
Thoughts? Derision? Encouragement?
David
David Ihnen
Integration Engineer
myCIO
503-670-4018
On Mon, Sep 25, 2000 at 04:08:08PM -0700, Ihnen, David wrote:
> I want to make sure I don't email djb without having a real legitimate
> question.
Don't email djb with qmail questions *ever*. That's what this list is
for.
> Are any of you aware of qmail internal data structure/logic documentation
> for the qmail programs?
There's INTERNALS, and "The big qmail picture" somewhere at
www.nrg4u.com (link is on www.qmail.org).
> It sure works nicely, but its a desert in there when you gain your
> sustenance from comments so you have a clue what each function is recieving,
> doing, and returning.
You need to get the hang of djb's coding style. Once you're into it,
it's very workable.
> From my browsing I have determined there is some extensive array data
> structure in memory whose definition is not quite obvious. (to me at least)
>
> So why would I ask such an absurd question?
>
> I'd like to show some people with cranial-rectal syndrome that are busily
> reinventing the mail delivery wheel that the back end they already have
> programmed can be inserted into qmail's processing.
That's usually possible, yes :)
> Instead of going straight from reciept to the delivery queue, it would go
> into a processing queue, and hopefully in a manner similar to
> qmail-remote/qmail-local rules, a qmail-process queue would then kick off a
> various processing filters based on a number of rules. The messages may or
> may not be returned to qmail for delivery after processing.
>
> Do you think its possible to insert such logic without changing the whole
> flow of qmail?
Just replace qmail-local with your program? What's wrong with .qmail,
perhaps?
> Its important that I maintain the original envelope, which to my knowledge
> will be lost if I try to use .qmail sorts of mail processing functionality.
Fix your knowledge. qmail protects envelope information with it's life.
Envelope information is *relevant*, and it's still there in .qmail.
Greetz, Peter
--
dataloss networks
'/ignore-ance is bliss' - me
> Instead of going straight from reciept to the delivery queue, it would go
I'm not sure I understand this sentence. Mail goes from the delivery queue
to the recipient, not around the other way...
> into a processing queue, and hopefully in a manner similar to
> qmail-remote/qmail-local rules, a qmail-process queue would then kick off a
> various processing filters based on a number of rules. The messages may or
> may not be returned to qmail for delivery after processing.
>
> Do you think its possible to insert such logic without changing the whole
> flow of qmail?
>
> Its important that I maintain the original envelope, which to my knowledge
> will be lost if I try to use .qmail sorts of mail processing functionality.
Nope. No envelope info is lost by .qmail processing. Quite the opposite. .qmail
processing especially makes envelope information easily available to a program.
> performance is relevant, so circumventing local delivery would probably be a
> good thing as well.
I would measure the cost before assuming the circumventing local delivery is
going to give you a big performance win.
> Thoughts? Derision? Encouragement?
I'd be very surprised if you couldn't achieve your results without resorting
to the internals of qmail. Probably the externals - all of which are documented
- will be all you need.
You would need to explain what sort of rules you want to have and what they
do to the email? What do the rules apply to? All mail sent thru the system? Only
remote mail? Only local mail? How is that mail first injected? Solely by processes
on that system or across the network via, eg, SMTP?
It sure is trivial to set up a qmail that accepts all mail from local and remote
connections and feeds it thru a default .qmail which can do anything you want
based on your filtering code. Especially note how easy it is to have a program
that drops or forwards a mail with the exit codes documented in the qmail-command
man page.
Here's one possible scenario.
On your filter system you install two instances of qmail. The first handles
the filtering and accepts mail from where you choose. It has a catch-all
virtualdomain entry, something like:
echo :alias-catchall >/var/qmail/control/virtualdomains
In ~alias/.qmail-catchall-default you have something like:
| yourfilteringprograms
| /var/qmail2/bin/forward "$EXT..."
Where:
yourfilteringprograms
Makes judicious use of exit(0), exit(99) and exit(1);
Note that the forwarding uses a second instance of qmail which does not
have a catchall alias.
Remember that qmail reliably places the mail in a queue for processing, if
you don't need that reliability, writing your own thing may well be a win.
If you do need that reliability, you may find that avoiding the qmail queue
and thus inventing your own is a lot more trouble than it's worth.
Regards.
On Mon, Sep 25, 2000 at 04:48:26PM -0700, [EMAIL PROTECTED] wrote:
> > Instead of going straight from reciept to the delivery queue, it would go
>
> I'm not sure I understand this sentence. Mail goes from the delivery queue
> to the recipient, not around the other way...
He's saying "receipt" which probably means incoming SMTP, or at least a
qmail-queue invocation.
Greetz, Peter
--
dataloss networks
'/ignore-ance is bliss' - me
> > Are any of you aware of qmail internal data structure/logic
> > documentation for the qmail programs?
>
> There's INTERNALS, and "The big qmail picture" somewhere at
> www.nrg4u.com (link is on www.qmail.org).
Hm, I'll be sure to read those.
> > Instead of going straight from reciept to the delivery
> > queue, it would go into a processing queue, and hopefully
> > in a manner similar to qmail-remote/qmail-local rules, a
> > qmail-process queue would then kick off various processing
> > filters based on a number of rules. The messages may or
> > may not be returned to qmail for delivery after processing.
> >
> > Do you think its possible to insert such logic without
> > changing the whole flow of qmail?
>
> Just replace qmail-local with your program? What's wrong with .qmail,
> perhaps?
Well, There are two stages of queuing in my modification proposal - the
processing I do, and the delivery. In existing qmail there is only one
stage - if it makes it to the queue, it gets delivered according to
configuration.
Hence, if ALL messages get sent to qmail-local, well, ALL messages get sent
to qmail-local. If qmail-local finishes with them and they are to be
delivered to the SAME RECIPIENT as they came in with, thus reintroducing the
envelope for delivery into the queue, it would then be processed as any new
message - and with ALL messages, get sent to qmail-local again. This means
I will have to have some logic to separate messages that are processed from
messages that are for delivery. Two queues makes sense to me...
I hope to make it an insertion into the current processing of mail that
could be used by anybody for just about anything to run rules/processing on
all mail regardless of recipient.
Am I wrong?
David
hello friends
i am using qmail 1.03 with qmail-ldap-2000601.patch on IBM AIX ,
yesterday my boss came with one intresting requirements like
(1) changing priority of any queued/deffered messages
(2) changing lifetime of defered/queued message
(3) restricting no of simultanious SMTP sessions from single IP address
( i am running qmail-smtpd under tcpserver it allows me to rstrict total no
of SMTP simultanious sessions but not simultanious smtp sessions from
single ip address
friends i am supposed to do above things today itself , i have tried
searching wwws for these but didt found some stuff which can help me to
implement above features ,
please help me ASAP
thanks and regards
Prashant Desai
hello friends
i am using qmail 1.03 with qmail-ldap-2000601.patch on IBM AIX ,
yesterday my boss came with one intresting requirements like
(1) changing priority of any queued/deffered messages
(2) changing lifetime of defered/queued message
(3) restricting no of simultanious SMTP sessions from single IP address
( i am running qmail-smtpd under tcpserver it allows me to rstrict total no
of SMTP simultanious sessions but not simultanious smtp sessions from
single ip address
friends i am supposed to do above things today itself , i have tried
searching wwws for these but didt found some stuff which can help me to
implement above features ,
please help me ASAP
thanks and regards
Prashant Desai
hello friends
i am using qmail 1.03 with qmail-ldap-2000601.patch on IBM AIX ,
yesterday my boss came with one intresting requirements like
(1) changing priority of any queued/deffered messages
(2) changing lifetime of defered/queued message
(3) restricting no of simultanious SMTP sessions from single IP address
( i am running qmail-smtpd under tcpserver it allows me to rstrict total no
of SMTP simultanious sessions but not simultanious smtp sessions from
single ip address
friends i am supposed to do above things today itself , i have tried
searching wwws for these but didt found some stuff which can help me to
implement above features ,
please help me ASAP
thanks and regards
Prashant Desai
