qmail Digest 26 Feb 1999 11:00:00 -0000 Issue 563
Topics (messages 22466 through 22506):
ETRN with Qmail
22466 by: Pedro Melo <[EMAIL PROTECTED]>
22467 by: [EMAIL PROTECTED]
max nbr of mails in time
22468 by: Franky Van Liedekerke <[EMAIL PROTECTED]>
22469 by: Mark Delany <[EMAIL PROTECTED]>
22470 by: Van Liedekerke Franky <[EMAIL PROTECTED]>
22472 by: Frank DENIS <[EMAIL PROTECTED]>
Denial of service process table attacks
22471 by: Frank DENIS <[EMAIL PROTECTED]>
User directory permission requirements
22473 by: Chris Green <[EMAIL PROTECTED]>
22475 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22478 by: Mate Wierdl <[EMAIL PROTECTED]>
Beginner'Q : can't connect to port 25 - more infos
22474 by: Patrick Paysant <[EMAIL PROTECTED]>
22476 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
synchronous mount of qmail volume under Linux
22477 by: "Garry Thuna" <[EMAIL PROTECTED]>
Remote mail still not working
22479 by: Mark E Drummond <[EMAIL PROTECTED]>
22480 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22481 by: Mark E Drummond <[EMAIL PROTECTED]>
22482 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22483 by: Mark E Drummond <[EMAIL PROTECTED]>
22484 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22485 by: Mark E Drummond <[EMAIL PROTECTED]>
22488 by: Mark E Drummond <[EMAIL PROTECTED]>
Comments on DSN (was: ETRN with Qmail)
22486 by: Jason Haar <[EMAIL PROTECTED]>
vacation (yet again!)
22487 by: Samuel Dries-Daffner <[EMAIL PROTECTED]>
22495 by: "Peter Samuel" <[EMAIL PROTECTED]>
Qmail mailing list and ReplyTo:
22489 by: Peter van Dijk <[EMAIL PROTECTED]>
badmailfrom
22490 by: Ray Belleville <[EMAIL PROTECTED]>
22496 by: Chris Johnson <[EMAIL PROTECTED]>
:O)
22491 by: Peter van Dijk <[EMAIL PROTECTED]>
queue summary
22492 by: "Peter Samuel" <[EMAIL PROTECTED]>
22497 by: "Peter Samuel" <[EMAIL PROTECTED]>
Forwarding mail preserving extension from ~/alias to user
22493 by: "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>
22503 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
Bug? Alias problem.
22494 by: "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>
22498 by: Stefan Paletta <[EMAIL PROTECTED]>
22499 by: "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>
Qmail '|forward user-$DEFAULT' problem with ezmlm
22500 by: "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>
22504 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22506 by: "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>
all to the pppdir but for a domain...
22501 by: [EMAIL PROTECTED] (Giulio)
PLEASE HELP >>Virtual Domains<<
22502 by: Gianluca Baldo <[EMAIL PROTECTED]>
22505 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
On 24-Feb-99 Jason Haar wrote:
> On Wed, Feb 24, 1999 at 09:16:56AM +0100, Dimitri SZAJMAN wrote:
>> Hi.
>>
>> Does Qmail supports ETRN ? Do you have any link ?
>>
>
> No - which is a real pity...
>
> Most new MUAs (Outlook/Exchange, Netscape, MUTT) support DSN, and it doesn't
> matter if DSN isn't that great an idea - it's still there and people like
> getting receipts to important messages :-(
huhs??? He asked about ETRN... ETRN and DSN are not related. As far as ETRN is
concern, you can look at AutoTURN in qmail.1-03 that does the same thing but
with all the MTA's.
As far as DSN is concern, it's a MUA feature, that does not belong in the MTA.
You want to receive the receipt if the message get's to the recipient MUA's,
not the recipient MTA...
> I have to tell people when sending messages to "CC: [EMAIL PROTECTED]"
> - if the get a bounce, then their message was delivered to the site
> correctly ;-)
... but that does not assures you that the message was received by the
recipient. If DSN is taken care of in the MUA, you have it.
Also, check qreceipt man page for something similar.
---
Pedro Melo [EMAIL PROTECTED]
IP - Engenharia http://ip.pt/
Tel: +351-1-3166740 Av. Duque de Avila, 23
Fax: +351-1-3166701 1049-071 LISBOA - PORTUGAL
Linux: up 35 days and 9:58, 5 users, load average: 0.17, 0.07, 0.04
Hi,
There was a qmail-etrn patch originally on the qmail web site. I don't know if it is
still up there, but it did work well as I have found it invaluable for one of the
solutions I am working on
Regards,
David
On Thu, Feb 25, 1999 at 10:19:37AM +1300, Jason Haar wrote:
> On Wed, Feb 24, 1999 at 09:16:56AM +0100, Dimitri SZAJMAN wrote:
> > Hi.
> >
> > Does Qmail supports ETRN ? Do you have any link ?
> >
>
> No - which is a real pity...
>
> Most new MUAs (Outlook/Exchange, Netscape, MUTT) support DSN, and it doesn't
> matter if DSN isn't that great an idea - it's still there and people like
> getting receipts to important messages :-(
>
> I have to tell people when sending messages to "CC: [EMAIL PROTECTED]"
> - if the get a bounce, then their message was delivered to the site
> correctly ;-)
>
> --
> Cheers
>
> Jason Haar
>
> Unix/Network Specialist, Trimble NZ
> Phone: +64 3 3391 377 Fax: +64 3 3391 417
Hi,
is there a patch available for qmail to limit the number of mails a user
can send within a specific period of time, within the same smtp
connection or not within?
Now, a user can send millions of mails and so can block the whole
system.
Franky
At 01:07 PM 2/25/99 +0100, you wrote:
>Hi,
>
>is there a patch available for qmail to limit the number of mails a user
>can send within a specific period of time, within the same smtp
>connection or not within?
Not specifically. And you need to tell us how you plan to unequivocally
identify the user in question via SMTP. The protocol has no sure-fire
authentication mechanism.
>Now, a user can send millions of mails and so can block the whole
>system.
Now? As opposed to previously?
But yes. There has been obscure threads on this matter over time. Richard
Letts (sp?) along with others such as myself have discussed strategies for
evenly sharing resources across various characteristics, such as envelope
info, submittor uid, submittor IP address and so on. There are interesting
issues associated with this that make a general tool a dang tricky thing.
Regards.
I would not identify users, just use their ip adresses, as given by
tcpserver.
> ----------
> From: Mark Delany[SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, February 25, 1999 2:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re: max nbr of mails in time
>
> At 01:07 PM 2/25/99 +0100, you wrote:
> >Hi,
> >
> >is there a patch available for qmail to limit the number of mails a user
> >can send within a specific period of time, within the same smtp
> >connection or not within?
>
> Not specifically. And you need to tell us how you plan to unequivocally
> identify the user in question via SMTP. The protocol has no sure-fire
> authentication mechanism.
>
Franky Van Liedekerke wrote:
> is there a patch available for qmail to limit the number of mails a user
> can send within a specific period of time, within the same smtp
> connection or not within?
> Now, a user can send millions of mails and so can block the whole
> system.
IPLimit should solve your problem, too.
Just grab it from http://www.jedi.claranet.fr
Russ Allbery wrote:
> >> Correct. As long as you run all of your services via tcpserver.
> > Too bad similar protection isn't currently available for udp and RPC
> > services :-)
>
> Most UDP services run from inetd run with the "wait" option, which means
> that as long as new requests are coming in, the one forked daemon handles
> them all.
Right, and for per-host ratios, try IPLimit, available from
http://www.jedi.claranet.fr
-Frank.
I've asked this before and have forgotten what the answer was. :-(
I'm using Maildir and so each user has a Maildir directory. What are
qmail's requirements for permissions on the user's home directory and
on the Maildir directory itself?
I grepped through the /var/qmail/doc directory for anything I could
think of that was relevant but didn't come up with anything useful.
I *think* the requirements are that the users' home directories are
writeable only by themselves (i.e. owner) but can have general read
permission. Is the Maildir required to be only readable and writeable
by owner or is that just the default that maildirmake has set?
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
- Chris Green <[EMAIL PROTECTED]>:
| I've asked this before and have forgotten what the answer was. :-(
|
| I'm using Maildir and so each user has a Maildir directory. What are
| qmail's requirements for permissions on the user's home directory and
| on the Maildir directory itself?
On the maildir, the only requirements are the ones that must be
fulfilled for qmail-local to put the message there: It does no
separate checking. This means that the user must have full access
rights to the tmp/ and new/ subdirectories. Plus, of course, execute
priveleges on the path to the maildir.
For the home directory, it depends how qmail was compiled, but the
user must own the home dir, and normally, it should not be writable by
others (though in some incarnations, it is OK for the home to be group
writable).
- Harald
Use maildirmake as the user, and all will be well.
Mate
Harald Hanche-Olsen wrote:
> Try running telnet localhost 25. If you don't get a response, then
> there is a problem.
I try... and this is why I need help, it doesn't work. I can't even quit my
telnet session, I have to kill the xterm !
> That user needs a ~/qmail/ directory for mbox delivery to
> ./qmail/inbox to work.
Which user ? root ? there is a qmail/inbox with 755.
in /etc/aliases, all entry have an alias to root and root has
an alias to webmaster, and webmaster has a /qmail/inbox with 755.
> So your queue was messed up somehow. This never happens in regular
> qmail operation, so it must be a case of finger trouble or manually
> poking at the queue. Get Russell Nelons qmail-qsanity script (found
> at <URL:http://www.qmail.org/>) and run it to fix the problem.
> Complain to Russell if the script does not work. 8-)
Great, it works but they both say :
------------------------------
Warning: users/assign checking not implemented.
------------------------------
And I don't understand how to make this file. I try qmail-pw2u :
------------------------------
qmail-pw2u: fatal: unable to find alias user
------------------------------
SOB !!! Too sad. What is that alias user ?
> It's not trivial, no.
No, it's not !!!
> Some people find Dan's qmail pictures helpful.
I have great difficulties to access Dan's headquarter. Is there another
place where I can find them.
> Of course, we can all agree to that. But a Linux solution is not free
> either: You have to invest the time needed to understand the systems
> you are using. If your time is valuable, the initial cost may well be
> higher than for the NT solution, but Linux will pay off in the long
> run. (This is an indisputable religious fact.)
I'm a bit religious too :-)
> And good luck with this project! I'm sure you can too.
Thanks for your help.
Patrick
- Patrick Paysant <[EMAIL PROTECTED]>:
| Harald Hanche-Olsen wrote:
|
| > Try running telnet localhost 25. If you don't get a response, then
| > there is a problem.
|
| I try... and this is why I need help, it doesn't work. I can't even
| quit my telnet session, I have to kill the xterm !
Ah. Sure you can quit it: You need to type the telnet escape
character (usually ^], that is Control + right bracket) which will
give you the "telnet>" prompt. Then type the command "close".
As to why you get no response, that is a different question. You may
try running /var/qmail/bin/qmail-smtpd from the command line:
; /var/qmail/bin/qmail-smtpd
220 fiinbeck.math.ntnu.no ESMTP
quit
221 fiinbeck.math.ntnu.no
If it responds ok, then the problem must be with your tcpserver
setup. You could try running tcpserver interactively. In one xterm,
as root, run
/usr/local/bin/tcpserver -v -R -x/etc/tcprules.smtp.cdb -u5100 \
-g5151 0 smtp /var/qmail/bin/qmail-smtpd
(after killing off your nonfunctional tcpserver that is lurking in the
background), then try connecting to it from a second xterm and see
what kind of response you get in the first one.
| > That user needs a ~/qmail/ directory for mbox delivery to
| > ./qmail/inbox to work.
|
| Which user ? root ?
I don't know, because your log excerpt did not tell me what user the
delivery was for. It should say delivery 15: msg xxx to local user@...
| Great, it works but they both say :
| ------------------------------
| Warning: users/assign checking not implemented.
| ------------------------------
|
| And I don't understand how to make this file. I try qmail-pw2u :
Don't worry. You don't need it. Later, perhaps, when your basic
setup is working, you may wish to start playing with users/assign, but
leave it for now.
| > Some people find Dan's qmail pictures helpful.
|
| I have great difficulties to access Dan's headquarter. Is there
| another place where I can find them.
Dan's FTP server produces directory listings in a somewhat unusual
format which confuses some broken web browsers. Try a different
browser, or maybe the plain old FTP program itself.
- Harald
in conf-qmail the following recomendation is made
"Under Linux, make sure that all mail-handling filesystems are mounted with
synchronous metadata."
Can anyone help me understand how to do this and how to check if it is
already done. My man pages for mount refer to synchronous but not metadata.
============================================
Garry Thuna
Tactical Executive Systems
[EMAIL PROTECTED]
Howdy. OK, ingoring relaying et al for now, I still cannot get mail for
remote rcpts off my machine. Mail to local users, whether from local or
remote senders works just fine. But mail from a local user to a remote
rcpt just sits in the queue. _Nothing_ is logged, I have the fol in my
syslog.conf:
mail.* /var/log/maillog
TAB separated (I double checked :-) and syslog has been restarted. My
current setup is basically the default setup after an install. All
daemons are running as their appropriate users. Nothing has been
bounced. The mail to remote rcpts is just sitting in the queue. I am on
a Solaris 7 box, the install went without a hitch. No errors.
I need to get this fixed ASAP or my boss will make me go back to
sendmail. (Ack!) Any ideas folks?
--
_________________________________________________________________
Mark E Drummond Royal Military College of Canada
mailto:[EMAIL PROTECTED] Computing Services
Linux Uber Alles perl || die
The day Microsoft makes something that doesn't
suck is the day they start making vacuums
- Mark E Drummond <[EMAIL PROTECTED]>:
| Howdy. OK, ingoring relaying et al for now, I still cannot get mail
| for remote rcpts off my machine. Mail to local users, whether from
| local or remote senders works just fine. But mail from a local user
| to a remote rcpt just sits in the queue. _Nothing_ is logged,
| the fol in my syslog.conf:
|
| mail.* /var/log/maillog
Well, you clearly need to get logging enabled. Try this simple test:
; echo Testing | /var/qmail/bin/splogger
Does the word "Testing" show up in the logfile? (Don't forget that
syslog never creates log files. You must create them for it, then
send syslogd a HUP to make it use the new files.)
If you cannot get logging to work, you can at least run qmail in a
terminal window for a little while, to find out why remote mail is not
delivered. Just run qmail-start (as root) in the foreground, after
first having terminated the background daemon of course. Then all the
stuff that normally goes in the log file should show on the terminal.
Make sure to use an xterm with plenty of scrollback lines for the
test. To make qmail-send shut down gracefully after you are done
testing, use kill -TERM on it from a different terminal window, rather
than typing Ctrl-C at it.
In summary, we need more data. Go get it for us, and hopefully we can
pinpoint the problem for you.
- Harald
Harald Hanche-Olsen wrote:
>
> - Mark E Drummond <[EMAIL PROTECTED]>:
>
> | Howdy. OK, ingoring relaying et al for now, I still cannot get mail
> | for remote rcpts off my machine. Mail to local users, whether from
> | local or remote senders works just fine. But mail from a local user
> | to a remote rcpt just sits in the queue. _Nothing_ is logged,
> | the fol in my syslog.conf:
> |
> | mail.* /var/log/maillog
>
> Well, you clearly need to get logging enabled. Try this simple test:
>
> ; echo Testing | /var/qmail/bin/splogger
Got logging working. I guess Solaris doesn't like mail.*, I had to use
mail.info instead. Stupid admin trick. :-) Maybe now I will see what is
going on. I'll get back to you.
--
_________________________________________________________________
Mark E Drummond Royal Military College of Canada
mailto:[EMAIL PROTECTED] Computing Services
Linux Uber Alles perl || die
The day Microsoft makes something that doesn't
suck is the day they start making vacuums
- Mark E Drummond <[EMAIL PROTECTED]>:
| I'll get back to you.
OK, I am going home now, it being late in these parts of the world.
But I'll log in from home later, so if you have further questions I
may still be able to answer them.
- Harald
Harald Hanche-Olsen wrote:
>
> Did you try the direct splogger test I suggested?
Yep, now it is working per my other email.
> But how do you run it in the foreground? I meant to run simply
Actually I did `csh -cf '/var/qmail/rc'` without the &. However, all of
a sudden all the email that was waiting in the queue has been delivered!
Would qmail hold the mail while logging was not working?
--
_________________________________________________________________
Mark E Drummond Royal Military College of Canada
mailto:[EMAIL PROTECTED] Computing Services
Linux Uber Alles perl || die
The day Microsoft makes something that doesn't
suck is the day they start making vacuums
- Harald Hanche-Olsen <[EMAIL PROTECTED]>:
| OK, I am going home now
Ho hum. *Rats*, I need to teach Mew about mailing lists one of these
days. Sorry about the noise.
- Harald
Harald Hanche-Olsen wrote:
>
> - Mark E Drummond <[EMAIL PROTECTED]>:
>
> | I'll get back to you.
>
> OK, I am going home now, it being late in these parts of the world.
> But I'll log in from home later, so if you have further questions I
> may still be able to answer them.
>
> - Harald
Thanks for your help. Anyway, I am back to the basic post-install
config, with _just_ my "locals" "me" and "rcpthosts" set to the local
machine FQDN. Like I said, the email in the queue has been delivered
(well, actually only about half of the messages, I guess the others need
to wait for the next queue processing?), and I have no idea what
happened to make that mail be delivered. Logging is working now that I
have the correct entry in syslog.conf. Now I get to break it by trying
to integrate it with tcp_wrappers ... :-)
--
_________________________________________________________________
Mark E Drummond Royal Military College of Canada
mailto:[EMAIL PROTECTED] Computing Services
Linux Uber Alles perl || die
The day Microsoft makes something that doesn't
suck is the day they start making vacuums
Mate Wierdl wrote:
>
> The obvious question now is: what command starts qmail for you? Wold you
> mind copyying the approriate init file here?
>
Since I have just installed tcpserver, my /etc/init.d/qmail now has the
fol in it:
/usr/local/bin/tcpserver -c100 -x/etc/tcp.smtp.cdb -u51012 -g1005 0
smtp \
/var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd &
I am now testing it to see if it accepts mail both ways.
--
_________________________________________________________________
Mark E Drummond Royal Military College of Canada
mailto:[EMAIL PROTECTED] Computing Services
Linux Uber Alles perl || die
The day Microsoft makes something that doesn't
suck is the day they start making vacuums
On Thu, Feb 25, 1999 at 11:09:18AM -0000, Pedro Melo wrote:
> > Most new MUAs (Outlook/Exchange, Netscape, MUTT) support DSN, and it doesn't
> > matter if DSN isn't that great an idea - it's still there and people like
> > getting receipts to important messages :-(
>
> huhs??? He asked about ETRN... ETRN and DSN are not related.
Whoops - brain fart - I replied to the wrong message. :-}
> Also, check qreceipt man page for something similar.
I'm sorry??? qreceipt is Qmail-specific:
HARDLY ANYONE USES QMAIL (except all of us of course).
Most people in the world are sitting on PeeCees running M$ OSes. DSN is the
nearest thing to a standard the Internet has for acknowledging Email
delivery and the most used SMTP server in use today (sendmail) supports it.
I'm wanting to replace our sendmail environment with qmail, but the biggest
problem I have is that my users (sitting on an Exchange server no less) will
suddenly lose the ability to do delivery receipts - something they have to
rely on as they primarily send Email to other MS$ systems (which have a
habit of losing Email ;-).
It doesn't matter that this all sucks and we should be using something else
- as we all know - technical capability of solutions means little to modern
business these days - packaging and little sounds when you push buttons are
much more important.
[Hmmm, must be going to be a good day for me - better stay away from sharp
objects ;-)]
--
Cheers
Jason Haar
Unix/Network Specialist, Trimble NZ
Phone: +64 3 3391 377 Fax: +64 3 3391 417
Peter's vacation program works great. But we have a weird exception that
concerns me....
When mail is sent from pine or BSD mail off our IRIX box the feature works
great, but when we tested it from a user sending from Outlook the retrun
message was never delivered. I can't see any problem in the perl code of
Peter's program, so my guess is there are some funny interactions
when qmail is trying to get the $SENDER (or other?) variable from the
header.
This seems related to other discussions about return receipt and Microsoft
products?!
Any ideas?
TIA,
Samuel Daffner
Mills College ITS
------ this header works ....using pine --------
>From [EMAIL PROTECTED] Thu Feb 25 12:11:02 1999
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 6329229 invoked by uid 2504); 25 Feb 1999 12:04:49 -0800
Date: Thu, 25 Feb 1999 12:04:49 -0800 (PST)
From: Solomon Hill <[EMAIL PROTECTED]>
To: Test Student Account <[EMAIL PROTECTED]>,
Solomon Hill <[EMAIL PROTECTED]>
Subject: From ella test
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
print me
------ this header doesn't...from Outlook -------
>From [EMAIL PROTECTED] Thu Feb 25 12:16:23 1999
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 5375093 invoked from network); 25 Feb 1999 12:13:36 -0800
Received: from pc1311.mills.edu (144.91.45.132)
by ella.mills.edu with SMTP; 25 Feb 1999 12:13:36 -0800
Reply-To: <[EMAIL PROTECTED]>
From: "Solomon P. Hill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Third test of vacation
Date: Thu, 25 Feb 1999 12:11:18 -0800
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
we get this?
On Mon, 22 Feb 1999, Peter Samuel wrote:
> THIS is the reason I wrote (modified) the qmail-vacation package.
>
> Use my perl program, or write your own in C if you don't want to use
> ----------
> Peter Samuel [EMAIL PROTECTED]
On Thu, 25 Feb 1999, Samuel Dries-Daffner wrote:
>
> Peter's vacation program works great. But we have a weird exception that
> concerns me....
>
> When mail is sent from pine or BSD mail off our IRIX box the feature works
> great, but when we tested it from a user sending from Outlook the retrun
> message was never delivered. I can't see any problem in the perl code of
> Peter's program, so my guess is there are some funny interactions
> when qmail is trying to get the $SENDER (or other?) variable from the
> header.
$SENDER is set from the _envelope_ sender address, not from _any_ of the
message headers.
To see exactly what variables are being set, create a .qmail-env file
in a user's home directory. It will contain the following command:
| env | sort -f > /var/tmp/env.$$
It should have 644 permissions.
Then send mail from your various systems to user-env and examine the
/var/tmp/env.nnnnn files.
My guess is that the file created from the Outlook message will have a
strange $SENDER value. The examples below show different Return-Path:
values. Return-Path: is also derived from the _envelope_ sender
address:
The local message from pine had:
[EMAIL PROTECTED]
The remote message from Outlook had:
[EMAIL PROTECTED]
Is the missing ella component important to your setup? If it is, then
the Outlook system is misconfigured wrt your requirements.
Let me know what you see.
>
> This seems related to other discussions about return receipt and Microsoft
> products?!
I don't think so. It looks like a configuration issue to me.
>
> Any ideas?
>
> TIA,
>
> Samuel Daffner
> Mills College ITS
>
> ------ this header works ....using pine --------
> >>From [EMAIL PROTECTED] Thu Feb 25 12:11:02 1999
> Return-Path: <[EMAIL PROTECTED]>
>
> ....
>
> ------ this header doesn't...from Outlook -------
>
> >>From [EMAIL PROTECTED] Thu Feb 25 12:16:23 1999
> Return-Path: <[EMAIL PROTECTED]>
>
> ....
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
Uniq Professional Services, [EMAIL PROTECTED]
a division of X-Direct Pty Ltd
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 Fri, Feb 19, 1999 at 06:24:37PM -0500, Justin Bell wrote:
> On Fri, Feb 19, 1999 at 02:43:46PM -0600, [EMAIL PROTECTED] wrote:
> #
> # Exactly my point.. If you took your time and read (instead of scanning)
> # the message before replying, those "Ups I posted a private mail to the
> # mailing
> # list" mistakes wouldn't hapen with "Reply-To:" field set to the
> # mailinglist
> # address
> #
> # Using stock Unix /bin/mail, try to reply to this message without sending
> # yourself a copy. Take your time, and have fun.
> #
>
> how could he do that, he had to delete /bin/mail when he installed qmail
wuh? what? errrmm.
I still have my stock (Slackware Linux) /bin/mail, and it's working nicely. It sends
out mail when piped thru, haven't tried anything elso tho :)
Greetz, Peter.
--
.| Peter van Dijk | <mo|VERWEG> stoned worden of coden
.| [EMAIL PROTECTED] | <mo|VERWEG> dat is de levensvraag
| <mo|VERWEG> coden of stoned worden
| <mo|VERWEG> stonend worden En coden
| <mo|VERWEG> hmm
| <mo|VERWEG> dan maar stoned worden en slashdot lezen:)
Question
What exactly is this filtering on. The man says the envelope addresses, but is
that the From: Received: X-Sender Return-PATH.
Is there a way to deny mail that originated or crosses a specific relay server?
Thanks.
--
Ray Belleville
ISP Design and Support
Playground.net
E-Mail: [EMAIL PROTECTED]
This message was sent using Kmail for the KDE Desktop Environment
-----------------------------------------------------------------
On Thu, Feb 25, 1999 at 04:00:11PM -0500, Ray Belleville wrote:
> Question
>
> What exactly is this filtering on. The man says the envelope addresses, but is
> that the From: Received: X-Sender Return-PATH.
It looks at the envelope address, at the time it's provided during the SMTP
conversation.
> Is there a way to deny mail that originated or crosses a specific relay server?
If you're using tcpserver, you can either deny connections from that relay, or
bounce mail from that relay if you use Russ Nelson's BOUNCEMAIL patch. This
doesn't constitute denying mail that "originated or crosses" a particular
relay--you only block stuff coming directly from that relay.
Chris
On Wed, Feb 24, 1999 at 07:47:30PM +0100, Markus Stumpf wrote:
> On Wed, Feb 24, 1999 at 11:40:08AM -0600, Mate Wierdl wrote:
> > It is probably easy to pass laws regarding breaking rules for this
> > channel. The laws could me made international. If a country has no
> > laws or means to enforce the rules, they cannot use the channel.
>
> Onother nice (IMHO) approach was that a SMTP server only accepts eMails
> from the well known mail-servers of this domain.
> E.g. someone with a sender address @aol.com will be rejected unless
> it is from an AOL mailserver.
> This will require of course a lot of "overhead" for ISPs, but maybe
> one could add also "trusted" mailservers that may speak for other
> domains, too.
> LDAP could be our friend in this topic.
Arrrghhh! Don't start those threads again!
Greetz, Peter.
--
.| Peter van Dijk | <mo|VERWEG> stoned worden of coden
.| [EMAIL PROTECTED] | <mo|VERWEG> dat is de levensvraag
| <mo|VERWEG> coden of stoned worden
| <mo|VERWEG> stonend worden En coden
| <mo|VERWEG> hmm
| <mo|VERWEG> dan maar stoned worden en slashdot lezen:)
On Wed, 24 Feb 1999, Van Liedekerke Franky wrote:
> Hi,
>
> is there a tool available to give a summary of what's in the queue?
> Something like:
> x mails queued for first.domain
> xx mails queued for second.domain
> yy mails deferred for third.domain
>
> If not, I'll write one myself (using perl of course)
>
> Franky
>
Just wrote one for a client. It's called whereto and it lists local
and remote domains and the number of bytes still to be sent. It parses
the output of qmail-qread and output looks like this:
Local Domains: 0 Local Recipients: 0
Remote Domains: 17 Remote Recipients: 29
porterhouse.merrion.nua.net: 1 recips 35532 bytes
mgw.com.au: 1 recips 2528 bytes
flash.theglobe.com: 1 recips 7692 bytes
sal.emailmedia.com: 1 recips 675 bytes
citysearc.com: 1 recips 3451 bytes
hotail.com: 1 recips 1944 bytes
aljan.com.au: 1 recips 2588869 bytes
smtp.emailserv.com: 1 recips 4273 bytes
freesex.net: 1 recips 10202 bytes
koha.net: 1 recips 1749 bytes
cavalier.com.au: 1 recips 1119 bytes
ruralink.com.au: 1 recips 7925 bytes
consult.com.au: 1 recips 2192 bytes
mega.com.au: 1 recips 554 bytes
ctbiz.canberratimes.com.au: 1 recips 4252 bytes
klever.net.au: 2 recips 146917 bytes
corona.dailysex.net: 12 recips 81127 bytes
Code follwas at end.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
Uniq Professional Services, [EMAIL PROTECTED]
a division of X-Direct Pty Ltd
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
###########################################################################
#!/usr/local/bin/perl -w
# Where is mail going?
use strict;
my($locals) = 0;
my($remotes) = 0;
my($bytes) = 0;
my(%remote);
my(%local);
my(%remotebytes);
my(%localbytes);
open(QREAD, "/var/qmail/bin/qmail-qread |");
while(<QREAD>)
{
my(@d);
my(@f);
chomp;
@f = split(' ');
if (/\sGMT\s/)
{
$bytes = $f[6];
}
if ($f[0] eq "remote")
{
@d = split(/\@/, $f[1]);
$d[1] = lc($d[1]);
++$remote{$d[1]};
++$remotes;
$remotebytes{$d[1]} += $bytes;
}
if ($f[0] eq "local")
{
@d = split(/\@/, $f[1]);
$d[1] = lc($d[1]);
++$local{$d[1]};
++$locals;
$localbytes{$d[1]} += $bytes;
}
}
print "Local Domains:\t", scalar keys %local;
print "\tLocal Recipients:\t$locals\n";
foreach (sort lnumerically keys %local)
{
print "$_:\t$local{$_} recips\t$localbytes{$_} bytes\n";
}
print "Remote Domains:\t", scalar keys %remote;
print "\tRemote Recipients:\t$remotes\n";
foreach (sort rnumerically keys %remote)
{
print "$_:\t$remote{$_} recips\t$remotebytes{$_} bytes\n";
}
sub lnumerically
{
$local{$a} <=> $local{$b};
}
sub rnumerically
{
$remote{$a} <=> $remote{$b};
}
On Fri, 26 Feb 1999, Mark Delany wrote:
> Can I suggest printf's with %20s formating rather than \t
>
> \t tends to look a bit ugly when, eg, domain names spread the stuff out over
> multiple plages.
>
> > print "$_:\t$remote{$_} recips\t$remotebytes{$_} bytes\n";
> printf("%40s: %d recips, ...
>
> Or even be very clever and note the length of the longest domain name.
Everyone's a critic :) Good idea. I'll make it so. New code at end.
I've also got a couple of other utils that you might like.
qstatus - show continually updating (10 second cycle time) snapshot
of the system (and it uses printf :) Example output (the leading /
character rotates with each cycle, just so you can see things
changing)
queue recipients processes tcpto load
processed/unprocessed local/remote local/remote ips avg
/ 38 0 0 46 0 4 6 0.74
recips - shows how many local and remote recipients there are:
messages in queue: 38
messages in queue but not yet preprocessed: 0
0 local recipients
45 remote recipients
tcpto - attempts to resolve IP addresses from qmail-tcpto. Requires
dnsptr from the qmail distribution:
hominet1.ruralco.com.au timed out 962 seconds ago; # recent timeouts: 1
m5.c2.telstra-mm.net.au timed out 443 seconds ago; # recent timeouts: 2
203.35.240.247 timed out 882 seconds ago; # recent timeouts: 1
gruyere.camtech.net.au timed out 762 seconds ago; # recent timeouts: 1
194.247.211.194 timed out 366 seconds ago; # recent timeouts: 1
igate1.mckinsey.com timed out 236 seconds ago; # recent timeouts: 1
fs-cls99.msl.com.au timed out 174 seconds ago; # recent timeouts: 1
I'll package them up and put them on an ftp site soon.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
Uniq Professional Services, [EMAIL PROTECTED]
a division of X-Direct Pty Ltd
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
###########################################################################
#!/usr/local/bin/perl -w
# Where is mail going?
use strict;
my $bytes = 0;
my $locals = 0;
my %local;
my %localbytes;
my $remotes = 0;
my %remote;
my %remotebytes;
my $newchars = 0;
my $oldchars = 0;
open(QREAD, "/var/qmail/bin/qmail-qread |");
while(<QREAD>)
{
my @d;
my @f;
chomp;
@f = split(' ');
if (/\sGMT\s/)
{
$bytes = $f[6];
}
if ($f[0] eq "remote")
{
@d = split(/\@/, $f[1]);
$d[1] = lc($d[1]);
++$remote{$d[1]};
++$remotes;
$remotebytes{$d[1]} += $bytes;
$newchars = length($d[1]);
$oldchars = $newchars if ($newchars > $oldchars);
}
if ($f[0] eq "local")
{
@d = split(/\@/, $f[1]);
$d[1] = lc($d[1]);
++$local{$d[1]};
++$locals;
$localbytes{$d[1]} += $bytes;
$newchars = length($d[1]);
$oldchars = $newchars if ($newchars > $oldchars);
}
}
print "Local Domains:\t", scalar keys %local;
print "\tLocal Recipients:\t$locals\n";
foreach (sort lnumerically keys %local)
{
printf("%-${oldchars}.${oldchars}s %4d recips %9d bytes\n",
$_, $local{$_}, $localbytes{$_});
}
print "\nRemote Domains:\t", scalar keys %remote;
print "\tRemote Recipients:\t$remotes\n";
foreach (sort rnumerically keys %remote)
{
printf("%-${oldchars}.${oldchars}s %4d recips %9d bytes\n",
$_, $remote{$_}, $remotebytes{$_});
}
sub lnumerically
{
$local{$a} <=> $local{$b};
}
sub rnumerically
{
$remote{$a} <=> $remote{$b};
}
I have a line such as:
Mydomain.com:alias-mydomain
In my virtualusers... then in the ~/alias directory, I have normal
.qmail-mydomain-xxx files. I need a way to forward all mail to a
[EMAIL PROTECTED], to the local user (much like &user), BUT preserving
the extension. So mail to:
[EMAIL PROTECTED] -> alias-user -> user
[EMAIL PROTECTED] -> alias-user-test (something to rewrite to) ->
user-test
Is there a special forward type that will rewrite and forward for .qmail
files? I need to have control of the domain account (thus having it in
~/alias), but I want users to be able to customize their extensions (for
ezmlm, etc).
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
- "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>:
| I have a line such as:
|
| Mydomain.com:alias-mydomain
|
| In my virtualusers... then in the ~/alias directory, I have normal
| .qmail-mydomain-xxx files. I need a way to forward all mail to a
| [EMAIL PROTECTED], to the local user (much like &user), BUT
| preserving the extension. So mail to:
|
| [EMAIL PROTECTED] -> alias-user -> user
| [EMAIL PROTECTED] -> alias-user-test (something to rewrite to) ->
| user-test
|
| Is there a special forward type that will rewrite and forward for
| .qmail files? I need to have control of the domain account (thus
| having it in ~/alias), but I want users to be able to customize
| their extensions (for ezmlm, etc).
echo '|forward "${EXT2}@local.domain"' > ~alias/.qmail-mydomain-default
RTFM qmail-send, qmail-command, forward
- Harald
I have my main mail server name in control/me, and no other files except
virtualhosts and rcpthosts (removed defaultdomain, locals, plusdomain for my
no default host setup).
I have the following .qmail files in ~/alias:
.qmail-domain-root // for domain.com
.qmail-anotherdom-root // for anotherdom.com
domain.com is the name of the mail server (mail.domain.com located in
control/me)
Ok, mail to [EMAIL PROTECTED] works as expected. But mail to
[EMAIL PROTECTED] bounces! Why? I have it handled here I thought. It must
have something to do with the fact that my control/me file says
"mail.domain.com", and it messes up the .qmail-domain-root file.
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
Robert Wojciechowski Jr. wrote/schrieb/scribsit:
> .qmail-domain-root // for domain.com
> .qmail-anotherdom-root // for anotherdom.com
>
> Ok, mail to [EMAIL PROTECTED] works as expected. But mail to
> [EMAIL PROTECTED] bounces!
You do have a line
domain.com:alias-domain
in virtualdomains?
What does the bounce message say why the address failed?
Stefan
Stefan,
I have the setup you described. I found out that it only happens if I do
not feed a complete e-mail address, duh.
Mail to "root" for example, does not know which domain to go to. I added a
.qmail-root file, to forward to .qmail-domain-root (cause that is my main
account), and all is fine.
So, I have:
.qmail-root
.qmail-domain-root
to cover all of them.
Mail now works to "root", "[EMAIL PROTECTED]", etc.
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
-----Original Message-----
From: Stefan Paletta [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 25, 1999 11:55 PM
To: [EMAIL PROTECTED]
Subject: RE: Bug? Alias problem.
Robert Wojciechowski Jr. wrote/schrieb/scribsit:
> .qmail-domain-root // for domain.com
> .qmail-anotherdom-root // for anotherdom.com
>
> Ok, mail to [EMAIL PROTECTED] works as expected. But mail to
> [EMAIL PROTECTED] bounces!
You do have a line
domain.com:alias-domain
in virtualdomains?
What does the bounce message say why the address failed?
Stefan
Hello,
I have my setup almost complete! Phew. Just a problem with forwarding. I
have the following setup:
- control/me
mail.host.com
- control/virtualdomains:
domain.com:alias-domain
- alias/.qmail-domain-user
&localuser
- alias/.qmail-domain-user-default
|forward localuser-$DEFAULT
Ok, I setup ezmlm, and I receive an error on a send to
[EMAIL PROTECTED]:
<[EMAIL PROTECTED]>:
ezmlm-manage: fatal: I do not accept messages at this address (#5.1.1)
If I put "mail.host.com" into my ~localuser/list/inhost and it works. But I
do not want to have each list, and each user to have to do this!
Why is it being rewritten to [EMAIL PROTECTED] ?
I want to keep it at [EMAIL PROTECTED]
Any solutions?
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
- "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>:
| - control/me
| mail.host.com
|
| - control/virtualdomains:
| domain.com:alias-domain
|
| - alias/.qmail-domain-user
| &localuser
|
| - alias/.qmail-domain-user-default
| |forward localuser-$DEFAULT
|
| Ok, I setup ezmlm, and I receive an error on a send to
| [EMAIL PROTECTED]:
|
| <[EMAIL PROTECTED]>:
| ezmlm-manage: fatal: I do not accept messages at this address (#5.1.1)
|
| If I put "mail.host.com" into my ~localuser/list/inhost and it
| works. But I do not want to have each list, and each user to have
| to do this!
|
| Why is it being rewritten to [EMAIL PROTECTED] ?
It's just how your virtualdomains setup works: By forwarding to the
new domain.
| I want to keep it at [EMAIL PROTECTED]
|
| Any solutions?
You could employ the users/assign mechanism instead of files in
~alias. If you cause the following to be in users/assign:
=domain-user:user:123:456:/home/user:::
+domain-user-:user:123:456:/home/user:-::
(replace 123:456 by the user's uid:gid and /home/user by the user's
real home dir) and remember to run qmail-newu, then the mail will be
delivered directly. You will want to write a script that does this
automatically, of course.
- Harald
Is there any other way to handle this without using users/assign? (with
standard .qmail files)
Perhaps another forward program (a lower level one, if one exists).
I wonder if that is even possible. Thank for the help so far.
Robert S. Wojciechowski Jr.
[EMAIL PROTECTED]
-----Original Message-----
From: Harald Hanche-Olsen [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 26, 1999 2:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Qmail '|forward user-$DEFAULT' problem with ezmlm
- "Robert Wojciechowski Jr." <[EMAIL PROTECTED]>:
| - control/me
| mail.host.com
|
| - control/virtualdomains:
| domain.com:alias-domain
|
| - alias/.qmail-domain-user
| &localuser
|
| - alias/.qmail-domain-user-default
| |forward localuser-$DEFAULT
|
| Ok, I setup ezmlm, and I receive an error on a send to
| [EMAIL PROTECTED]:
|
| <[EMAIL PROTECTED]>:
| ezmlm-manage: fatal: I do not accept messages at this address (#5.1.1)
|
| If I put "mail.host.com" into my ~localuser/list/inhost and it
| works. But I do not want to have each list, and each user to have
| to do this!
|
| Why is it being rewritten to [EMAIL PROTECTED] ?
It's just how your virtualdomains setup works: By forwarding to the
new domain.
| I want to keep it at [EMAIL PROTECTED]
|
| Any solutions?
You could employ the users/assign mechanism instead of files in
~alias. If you cause the following to be in users/assign:
=domain-user:user:123:456:/home/user:::
+domain-user-:user:123:456:/home/user:-::
(replace 123:456 by the user's uid:gid and /home/user by the user's
real home dir) and remember to run qmail-newu, then the mail will be
delivered directly. You will want to write a script that does this
automatically, of course.
- Harald
I've set-up qmail1.03 on a Linux box as per djb instructions and faq.
I have
:alias-ppp
as the last line of virtualdomains to queue in a maildir all mail to be sent to my ISP
via
maildirsmtp.
All is ok.
But I want that mail, say for @mydomain.dom, be sent directly to another machine of my
lan. Weren't for the "alias-ppp" line I could use smtproutes, but having to use
alias-ppp,
how can I do that? With the last ":alias-ppp" all mail is considered as "local".
I could set up another maildir to queue the mail for @mydomain.dom and send it with
maildirsmtp too, but I don't like this approach.
Suggestions?
Thanks.
--
Giulio
[EMAIL PROTECTED]
I'm new to qmail and I need to set up a server before the end of this
week and I need help :-)
dixitcom.com is the server (***all @dixitcom.com email addresses work
fine***).
On the same machine I have (as an Apache Virtual Server with different
IP) also truchos.com.
MX record for mail.truchos.com points to another IP on the same
dixitcom.com host.
I tried to set up e-mail address for truchos.com doing the following:
1. I created a POP user truchos
2. I added truchos.com:truchos to control/virtualdomains
3. truchos.com is in my control/locals and in my control/rcpthosts
4. I added (to have [EMAIL PROTECTED])
=truchos-webmaster:truchos:uid:gid:/home/truchos:luca::
to users/assign, meaning that truchos has charge for
[EMAIL PROTECTED] and that the .qmail file
is /home/truchos/.qmail-webmaster (I tried a
"&[EMAIL PROTECTED]" to start).
uid and gid are the user ID and the group ID for truchos.
5. I did qmail-newu
6. .qmail-webmaster has owner truchos:popusers and mod 0700
7. >>I restarted the machine<<
If I try to send a message to [EMAIL PROTECTED] I get (in
/var/log/maillog)
>>Sorry, no mailbox here by that name<<
It looks like qmailignores the "truchos.com:truchos" directive in
users/assign at all.
Has somebody has an idea of what am I doing wrong?
Many thanks in advance to anyone...
Gianluca Baldo
_______________________________________________________
Gianluca Baldo [EMAIL PROTECTED]
DIXIT COMUNICACION - Passatge Milans,1 2n. - 08907 L'HOSPITALET
Tel.932611040 - Fax. 933371699 - http://www.dixitcom.com_
- Gianluca Baldo <[EMAIL PROTECTED]>:
| 4. I added (to have [EMAIL PROTECTED])
| =truchos-webmaster:truchos:uid:gid:/home/truchos:luca::
| to users/assign, meaning that truchos has charge for
| [EMAIL PROTECTED] and that the .qmail file
| is /home/truchos/.qmail-webmaster
No. That line says the .qmail file is
/home/truchos/.qmailluca
(you set the `dash' for this address to luca).
You probably want
=truchos-webmaster:truchos:uid:gid:/home/truchos:-:webmaster:
or just plain
+truchos-:truchos:uid:gid:/home/truchos:-::
which is equivalent to
=truchos-FOO:truchos:uid:gid:/home/truchos:-:FOO:
for every value of FOO.
- Harald
