qmail Digest 2 Mar 1999 11:00:01 -0000 Issue 567
Topics (messages 22547 through 22580):
Thanks! (ezmlm & remote mail problems)
22547 by: Mark E Drummond <[EMAIL PROTECTED]>
Setting up Maildir as default
22548 by: "D. Carlos Knowlton" <[EMAIL PROTECTED]>
22549 by: Chris Johnson <[EMAIL PROTECTED]>
22550 by: Mate Wierdl <[EMAIL PROTECTED]>
Pass on tcpserver environment variables to qmail-queue, possible?
22551 by: Franz Sirl <[EMAIL PROTECTED]>
22552 by: Mate Wierdl <[EMAIL PROTECTED]>
22553 by: Russell Nelson <[EMAIL PROTECTED]>
22554 by: Franz Sirl <[EMAIL PROTECTED]>
22555 by: Russell Nelson <[EMAIL PROTECTED]>
22556 by: Mate Wierdl <[EMAIL PROTECTED]>
22557 by: Franz Sirl <[EMAIL PROTECTED]>
22558 by: Franz Sirl <[EMAIL PROTECTED]>
22559 by: [EMAIL PROTECTED]
22560 by: Russell Nelson <[EMAIL PROTECTED]>
22561 by: Franz Sirl <[EMAIL PROTECTED]>
22562 by: Peter van Dijk <[EMAIL PROTECTED]>
22568 by: Mate Wierdl <[EMAIL PROTECTED]>
22569 by: Mate Wierdl <[EMAIL PROTECTED]>
Parsing all OUTGOING messages
22563 by: "Wil Boucher" <[EMAIL PROTECTED]>
22566 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22578 by: "Jacek Czerwinski" <[EMAIL PROTECTED]>
installing qmail on a free mail server
22564 by: Dave Sill <[EMAIL PROTECTED]>
22571 by: [EMAIL PROTECTED]
Filtering incoming messages
22565 by: "Guilherme Barile" <[EMAIL PROTECTED]>
22567 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
22570 by: Mate Wierdl <[EMAIL PROTECTED]>
(spam-) Tagging incoming mail (was: Pass on tcpserver environment variables to
qmail-queue, possible?)
22572 by: Jost Krieger <[EMAIL PROTECTED]>
testing on an isolated host.
22573 by: "D. Carlos Knowlton" <[EMAIL PROTECTED]>
22580 by: Anand Buddhdev <[EMAIL PROTECTED]>
MRTG && qmail
22574 by: "Mads E Eilertsen" <[EMAIL PROTECTED]>
vacation (yet again!)
22575 by: "Peter Samuel" <[EMAIL PROTECTED]>
22577 by: Samuel Dries-Daffner <[EMAIL PROTECTED]>
22579 by: "Peter Samuel" <[EMAIL PROTECTED]>
Odp: testing on an isolated host.
22576 by: "Jacek Czerwinski" <[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]
----------------------------------------------------------------------
Thanks for everyone's help. It looks like my new qmail mail gateway
w/ezmlm lists is ready for production. I just need to test relaying from
external sites and we will be good to go.
Cheers
--
_________________________________________________________________
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
Hey guys,
I'm trying to setup Maildir as the default for my new users. The
"INSTALL.maildir" file suggests that I do this by putting it in my new user
template. I'm running Linux 2.0.X can anyone tell me where this template
might be?
Thanks!
-ck
On Mon, Mar 01, 1999 at 09:03:46AM -0600, D. Carlos Knowlton wrote:
> Hey guys,
>
> I'm trying to setup Maildir as the default for my new users. The
> "INSTALL.maildir" file suggests that I do this by putting it in my new user
> template. I'm running Linux 2.0.X can anyone tell me where this template
> might be?
It may depend on which Linux distribution you're using, but my guess would be
/etc/skel. Just cd into that directory and use maildirmake to make a Maildir,
and any new user you create with adduser will have a Maildir.
But that doesn't make maildir the default delivery method. For that you should
change ./Mailbox to ./Maildir/ (note the trailing slash) in your /var/qmail/rc
file (or whatever file you use to start qmail-send).
Chris
On Mon, Mar 01, 1999 at 09:03:46AM -0600, D. Carlos Knowlton wrote:
> Hey guys,
>
> I'm trying to setup Maildir as the default for my new users. The
> "INSTALL.maildir" file suggests that I do this by putting it in my new user
> template. I'm running Linux 2.0.X can anyone tell me where this template
> might be?
/etc/skel
And make the Maildir with
maildirmake /etc/skel/Maildir.
Also, there is more to making maildir the default:
If you are using standard installation, do this
(cd /var/qmail/boot
sed 's%Mailbox%Maildir/%' home > mdir
cp mdir ../rc
)
If you are using the memphis rpm, do this
cp /var/qmail/defaultdelivery/mdir /var/qmail/defaultdelivery/rc
and restart qmail with
/etc/rc.d/init.d/qmail.init restart
Mate
--
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Hi,
is it somehow possible to pass on the environment variables set by
tcpserver to qmail-queue? I would like to autoreply (via bouncesaying or
vacation) to users sending via servers listed in ORBS. Some of them I have
to unblock cause they are customers of my company, but I would like to
annoy them, so they keep kicking their provider.
Thanks,
Franz.
Hi,
is it somehow possible to pass on the environment variables set by
tcpserver to qmail-queue? I would like to autoreply (via bouncesaying or
vacation) to users sending via servers listed in ORBS. Some of them I have
to unblock cause they are customers of my company, but I would like to
annoy them, so they keep kicking their provider.
Thanks,
Franz.
I wonder what the RBLSMTPD env var is for.
Mate---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Franz Sirl writes:
> is it somehow possible to pass on the environment variables set by
> tcpserver to qmail-queue?
In theory that's already happening.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
At 16:54 01.03.99 , Mate Wierdl wrote:
Hi,
is it somehow possible to pass on the environment variables
set by
tcpserver to qmail-queue? I would like to autoreply (via
bouncesaying or
vacation) to users sending via servers listed in ORBS. Some
of them I have
to unblock cause they are customers of my company, but I
would like to
annoy them, so they keep kicking their provider.
Thanks,
Franz.
I wonder what the RBLSMTPD env var is for.
I _want_ to receive the mail for the users here and _additionally_
autoreply to them via standard .qmail-* handling. Unfortunately the
environment variables are not passed on to qmail-queue so I can't check
for them in .qmail-* (unless I did something wrong here?).
Franz.
Franz Sirl writes:
> I _want_ to receive the mail for the users here and _additionally_
> autoreply to them via standard .qmail-* handling. Unfortunately the
> environment variables are not passed on to qmail-queue so I can't check for
> them in .qmail-* (unless I did something wrong here?).
qmail-queue *does* get the environment variables, but it does not
store them as such. If you want to get the IP address to do the ORBS
lookup, you should parse the Received: line.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
If you know the IP numbers, you can set RBLSMTPD to "", and then mail
is not blocked. (I wonder how antirbl could be used for similar
purpose; am I supposed to run antirbl for each not-to-be-blocked domain?).
Mate
At 16:48 01.03.99 , Russell Nelson wrote:
>Franz Sirl writes:
> > is it somehow possible to pass on the environment variables set by
> > tcpserver to qmail-queue?
>
>In theory that's already happening.
Hmm, but not here. I tried to use the following line in .qmail:
|condredirect [EMAIL PROTECTED] test -n "$UNBLOCKED"
This works if I call qmail-queue manually, but not if it is called via
qmail-smtpd (which gets $UNBLOCKED, I verified that).
Maybe I'm doing something wrong here, but I don't see it (being wrong was
my 1st thought, cause usually everything is so easy with qmail).
Franz.
At 17:11 01.03.99 , Mate Wierdl wrote:
>If you know the IP numbers, you can set RBLSMTPD to "", and then mail
>is not blocked. (I wonder how antirbl could be used for similar
>purpose; am I supposed to run antirbl for each not-to-be-blocked domain?).
I'm setting RBLSMTPD to "" and the whole rest of setup works as expected.
My problem is that I cannot check for RBLSMTPD or any other environment
variable set by tcpserver in a .qmail file.
Franz.
Mate Wierdl <[EMAIL PROTECTED]> writes on 1 March 1999 at 10:11:35 -0600
> If you know the IP numbers, you can set RBLSMTPD to "", and then mail
> is not blocked. (I wonder how antirbl could be used for similar
> purpose; am I supposed to run antirbl for each not-to-be-blocked domain?).
Look at the antirbl man page more closely; what you're supposed to do
is point it at a DNS domain that has records for d,c,b,a.domain.com
for each IP address a.b.c.d that you want to ANTI-block. For a single
system this sounds like more trouble than just, say, a CDB database,
but on the other hand for a large complex network it sounds very
convenient.
(You can also anti-block by setting rblsmtpd to be null using
tcpserver, which overrides rblsmtpd. This seems to be the most
convenient approach on a single system such as mine.)
--
David Dyer-Bennet [EMAIL PROTECTED]
http://www.ddb.com/~ddb (photos, sf) Minicon: http://www.mnstf.org/minicon
http://ouroboros.demesne.com/ The Ouroboros Bookworms
Join the 20th century before it's too late!
Franz Sirl writes:
> At 17:11 01.03.99 , Mate Wierdl wrote:
> >If you know the IP numbers, you can set RBLSMTPD to "", and then mail
> >is not blocked. (I wonder how antirbl could be used for similar
> >purpose; am I supposed to run antirbl for each not-to-be-blocked domain?).
>
> I'm setting RBLSMTPD to "" and the whole rest of setup works as expected.
> My problem is that I cannot check for RBLSMTPD or any other environment
> variable set by tcpserver in a .qmail file.
Right. That's because qmail-queue doesn't record that variable when
it queues the mail. qmail *always* queues the mail, so you have two
sets of processes that process the mail:
tcpserver | rblsmtpd | qmail-smtpd | qmail-queue
qmail-send | qmail-lspawn | qmail-local
Any variables that tcpserver may set don't make the jump.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
At 17:00 01.03.99 , Russell Nelson wrote:
>Franz Sirl writes:
> > I _want_ to receive the mail for the users here and _additionally_
> > autoreply to them via standard .qmail-* handling. Unfortunately the
> > environment variables are not passed on to qmail-queue so I can't check
> for
> > them in .qmail-* (unless I did something wrong here?).
>
>qmail-queue *does* get the environment variables, but it does not
>store them as such. If you want to get the IP address to do the ORBS
>lookup, you should parse the Received: line.
Yes, that's it. As Petr Novotny and Russell Nelson told me the delivery via
.qmail is done by qmail-local (it seems I'm still thinking to complicated
for qmail :-) ), and qmail-local doesn't see tcpserver's environment variables.
So my options are:
- parse the Received: header (anyone has a working regexp for that?) for
the IP address and do rblsmtpd again
- patch qmail-smtpd to conditionally add a message header if a certain
environment variable is set
- ??
Franz.
On Mon, Mar 01, 1999 at 05:51:02PM +0100, Franz Sirl wrote:
> At 17:00 01.03.99 , Russell Nelson wrote:
> >Franz Sirl writes:
> > > I _want_ to receive the mail for the users here and _additionally_
> > > autoreply to them via standard .qmail-* handling. Unfortunately the
> > > environment variables are not passed on to qmail-queue so I can't check
> > for
> > > them in .qmail-* (unless I did something wrong here?).
> >
> >qmail-queue *does* get the environment variables, but it does not
> >store them as such. If you want to get the IP address to do the ORBS
> >lookup, you should parse the Received: line.
>
> Yes, that's it. As Petr Novotny and Russell Nelson told me the delivery via
> .qmail is done by qmail-local (it seems I'm still thinking to complicated
> for qmail :-) ), and qmail-local doesn't see tcpserver's environment variables.
>
> So my options are:
> - ??
How about something like FAQ 5.5?
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:)
I'm setting RBLSMTPD to "" and the whole rest of setup works as expected.
My problem is that I cannot check for RBLSMTPD or any other environment
variable set by tcpserver in a .qmail file.
I see, what you are saying is true.
What is the extra functionality you cannot achieve by putting
1.2.3.4:allow,RBLSMTPD="-Fix yourself, Johnny"
in the tcprules file for rblsmtpd?
Mate
So my options are:
- parse the Received: header (anyone has a working regexp for that?) for
the IP address and do rblsmtpd again
You can use 822field for that (from the mess822 package by djb).
Mate
I want to either add a line to the bottom of every outgoing message or edit
the subject line of everyoutgoing message.
I want all incoming messages to be left alone,
Where should I place a program in the stream to parse all outoging messages
and edit the subject or maybe and an organization tag line to the end of a
message?
Any suggestions?
- "Wil Boucher" <[EMAIL PROTECTED]>:
| I want to either add a line to the bottom of every outgoing message
| or edit the subject line of everyoutgoing message.
|
| I want all incoming messages to be left alone,
What about messages where both source and destination are local? If
you want to edit those in the same way you edit outgoint messages, you
can replace qmail-inject by a program that edits the message and pipes
the result into the original qmail-inject.
Otherwise, you will need to run two queues. In your regular queue,
have a wildcard virtualdomain for all remote domains. The delivery
instructions for that virtualdomain would contain code to rewrite the
message and pipe to /var/qmail-outgoing/bin/forward. In the
qmail-outgoing queue, no domains should be local.
- Harald
> I want to either add a line to the bottom of every outgoing message or
edit
> the subject line of everyoutgoing message.
>
> I want all incoming messages to be left alone,
>
> Where should I place a program in the stream to parse all outoging
messages
> and edit the subject or maybe and an organization tag line to the end of
a
> message?
>
> Any suggestions?
I use a serialmail packet (www.qmail.org) like in 'howto' and parse &
rewrite all messages in normal ppp-alias Maildir (external loop in shell,
message parser in perl). Basic qmail structure is unmodified.
If You don't use serialmail, you need to modify qmail 'kernel' modules. If
You do, I am very interesting, please mail me. I think, DJB will don't like
it ;-)
[EMAIL PROTECTED] wrote:
>Hi,
>prev. sysadmin in my company left for me a server of free mail that uses
>sendmail ( Doh! )
>The server has ~30k of users soo this is the right place for the qmail.
>the 1[Q] is: is there any patches I should apply.
qmail works fine for me right out of the box. Others have
added/changed functionality to suit their needs. Browse www.qmail.org
for descriptions of the most popular patches.
>I simply can`t think of any decent strategy I should follow ...
If you've never run qmail before, you should set it up on a test
system. Once you've got it behaving there, you can start migrating it
to the production system. You can run both qmail and sendmail on the
system during the swap. Leave sendmail in /usr/lib/sendmail and run
qmail-smtp on a non-standard port. Once that's working, you can
configure qmail to handle the "sending" side by pointing
/usr/lib/sendmail at /var/qmail/bin/sendmail. Complete the transition
by killing the sendmail daemon and switching qmail-smtpd to port
25. Continue to run "sendmail -q" periodically until the sendmail
queue is flushed.
You should practice this on your test system to make sure things will
go smoothly, especially delivering to the right place in the right
format and handling .forward files.
>the server is
>already listed at ORBS hehe
>I do what to fix that situation and make it more difficult for spummers to use
>the server ...
>any advises?
qmail disables relaying by default. You can turn it back on for
selected hosts, if necessary. Once qmail-smtpd is handling port 25,
you can verify that relaying is disabled and petition the ORBS people
to remove your server from their list.
>the 2[Q] is: has anybody managed to launch imp using qmail?
Never heard of it.
-Dave
Dave Sill <[EMAIL PROTECTED]> writes on 1 March 1999 at 12:10:20 -0500
> [EMAIL PROTECTED] wrote:
> qmail disables relaying by default. You can turn it back on for
> selected hosts, if necessary. Once qmail-smtpd is handling port 25,
> you can verify that relaying is disabled and petition the ORBS people
> to remove your server from their list.
"By default" is sufficiently slippery that I want to sidestep that
issue. Since this is an area people seem to have trouble with (at
least they ask frequently), let me try some proactive relaying
prevention :-).
Qmail prevents relaying if and only if the file control/rcpthosts
exists (this file should contain the list of domains that your server
should accept email for delivery to). If all locally-originated email
is sent via qmail-inject (including via the qmail sendmail wrapper),
that's all you need to do. However, if some mail user agents submit
their mail via SMTP, and always if you have POP users, you need to
turn relaying on selectively for the IP addresses that those users
come from. This process is described in FAQ 5.4.
--
David Dyer-Bennet [EMAIL PROTECTED]
http://www.ddb.com/~ddb (photos, sf) Minicon: http://www.mnstf.org/minicon
http://ouroboros.demesne.com/ The Ouroboros Bookworms
Join the 20th century before it's too late!
I created an account called newsmaster ... and I want this account to
receive messages ONLY from people that are on a list ... is it possible?
(using Qmail 1.03)
- "Guilherme Barile" <[EMAIL PROTECTED]>:
| I created an account called newsmaster ... and I want this account to
| receive messages ONLY from people that are on a list ... is it possible?
| (using Qmail 1.03)
Yup. Let the first line in the account's .qmail file call a program.
That program will look up $SENDER in the list and exit with a suitable
exit status depending on the result (zero if the mail is to be
accepted, 99 to drop it silently on the floor, 100 to bounce, 111 for
a temporary problem with the lookup). RTFM qmail-command.
The remaining line(s) in the .qmail file should contain delivery
instructions to be followed if the sender is accepted.
If you want to base your decision on the From header field instead of
the envelope sender you have to work harder. You must parse the
sender address yourself (but look at Dan's mess822 package).
- Harald
I created an account called newsmaster ... and I want this account to
receive messages ONLY from people that are on a list ... is it possible?
(using Qmail 1.03)
Put, in ~newsmaster/.qmail, (on one line!)
|boncesaying "You cannot send messages here"
[ "`grep -i $SENDER list`" != "" ]
where list is the file with the allowed addresses in it. Then put
./Mailbox
or
./Maildir/
depending on what you use.
Mate
>>>>> "Peter" == Peter van Dijk <[EMAIL PROTECTED]> writes:
> How about something like FAQ 5.5?
Here there be dragons. (Also known as "Been there, done that").
For various reasons I can't reject spam on the incoming mailhost, but
I'd like to tag likely Mails with something like
X-Spam-Tag: type blacklist field From origin rzrub trigger
[EMAIL PROTECTED] action complain issuer sunu450.rz.ruhr-uni-bochum.de
I jumped onto 5.5, put
:allow,RELAYCLIENT="@UCEcheck",DENYMAIL="DNSCHECK"
into my rules file, and was happy for an hour.
Then I noticed that I just had started relaying for everyone.
Why do you think the env var is named "RELAYCLIENT" ?
I plugged this in the script, but someone used me to do
relay-rejecting spam :-(
I now see only two possibilities:
1. Two instances of qmail.
2. A patch to qmail-smtpd, introducing NORELAYCLIENT.
Actually I did 2., but I still have to check the effects ...
Anybody got a better idea?
Jost
--
| [EMAIL PROTECTED] Please help stamp out spam! |
| Postmaster, JAPH, resident answer machine am RZ der RUB |
| non sunt multiplicanda entia praeter necessitatem |
| William of Ockham (1285-1347/49) |
Hi,
I have just set up qmail on a Linux machine on the LAN (isolated from the
DNS, so it has no registered domain name.) I set my Hostname as 192.168.1.1
(is this okay?), and I get an error message when I try to send to any user
on this machine:
"delivery 22: deferral:
Sorry_I_couldn't_find_any_host_by_that_name._(#4.1.2)/"
my hostname is T1-MAST, and I tried that, and got the same message. I have
TCPserver running (I think it's running right) and various other services
running(i.e. ftp, smb, http, telnet, and RIP) could these be conflicting in
any way? Any help on this would be great!
-ck
On Mon, Mar 01, 1999 at 01:49:58PM -0600, D. Carlos Knowlton wrote:
That message you see is from qmail-remote. So qmail is trying to deliver
this message to host t1-mast. You must add this name in the control/locals
file for qmail to deliver to your host locally.
Also, qmail requires DNS. If you need to send mail out, then you will have
to either use virtualdomains and serialmail, or send out through a
smarthost at your ISP with an entry in control/smtproutes.
> Hi,
>
> I have just set up qmail on a Linux machine on the LAN (isolated from the
> DNS, so it has no registered domain name.) I set my Hostname as 192.168.1.1
> (is this okay?), and I get an error message when I try to send to any user
> on this machine:
> "delivery 22: deferral:
> Sorry_I_couldn't_find_any_host_by_that_name._(#4.1.2)/"
>
> my hostname is T1-MAST, and I tried that, and got the same message. I have
> TCPserver running (I think it's running right) and various other services
> running(i.e. ftp, smb, http, telnet, and RIP) could these be conflicting in
> any way? Any help on this would be great!
>
> -ck
>
--
Anand
System Administrator
Africa Online Ltd
http://www.anand.org
On 12 Feb 1999, Russell Nelson wrote:
> And qmail-mrtg follows:
Thanks for sharing it.
However, at least on my host, it always produces two lines of '0'.
A proper close of the matchup process makes zoverall happy! :-)
Mads
*** qmail-mrtg.orig Mon Mar 1 22:30:04 1999
--- qmail-mrtg Mon Mar 1 22:30:10 1999
***************
*** 33,48 ****
--- 33,49 ----
open(QA, "|$qa/matchup >/tmp/out.$$ 5>$holdingfile") or die;
while(<P>) { print QA; }
close(P);
while(<>) {
split;
next if ($_[0] < $start || $_[0] >= $stop);
print QA;
}
+ close(QA);
# analyze the last five minutes.
open(REP, "$qa/zoverall </tmp/out.$$|") or die;
while(<REP>) {
if (/^Completed messages: (\d+)/) {
print "$1\n";
if (!$1) {
print "0\n";
On Mon, 1 Mar 1999, Samuel Dries-Daffner wrote:
>
> Well, we had heavy debugging on during these tests and there is no
> indication of failure... its like the message gets piped to vacation and
> thats it...NO failures, nothing. Seems like the outgoing message is not
> generated at all, only for those selected email clients. When it
> works it works and when it doesn't it just disappears (or so it
> seems). Weird :>
>
> I'm not sure where to go from here...
You do realise that if vacation sends a successful reply it will not
send another one to the same address for a week. This is overridden by
the command line option -t. From the man page.
-tN Change the interval between repeat replies to the
same sender. The default is 1 week. A trailing s,
m, h, d, or w scales the number N to seconds,
minutes, hours, days or weeks respectively. For
example, to set the interval value to 3 days you
would specify -t3d. There should be no spaces
between the -t and N. This option is only useful
when specified in the ~/.qmail file.
So, if you're trying to generate a vacation message for every reply
then the lowest granularity you can have is one second.
What's in your .qmail file? If you use the default setup
| /usr/local/bin/vacation username
/home/psamuel/mailbox
you'll get replies once a week. If you use this
| /usr/local/bin/vacation -t1s username
/home/psamuel/mailbox
You'll get replies once per second.
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"
Yes, I have .qmail set as:
| /usr/local/bin/Qvacation -t30s teststud
/var/mail/teststud
where Qvacation is your program...so I understand this to mean a 30 second
time frame.
Samuel
On Tue, 2 Mar 1999, Peter Samuel wrote:
> On Mon, 1 Mar 1999, Samuel Dries-Daffner wrote:
>
> >
> > Well, we had heavy debugging on during these tests and there is no
> > indication of failure... its like the message gets piped to vacation and
> > thats it...NO failures, nothing. Seems like the outgoing message is not
> > generated at all, only for those selected email clients. When it
> > works it works and when it doesn't it just disappears (or so it
> > seems). Weird :>
> >
> > I'm not sure where to go from here...
>
> You do realise that if vacation sends a successful reply it will not
> send another one to the same address for a week. This is overridden by
> the command line option -t. From the man page.
>
> -tN Change the interval between repeat replies to the
> same sender. The default is 1 week. A trailing s,
> m, h, d, or w scales the number N to seconds,
> minutes, hours, days or weeks respectively. For
> example, to set the interval value to 3 days you
> would specify -t3d. There should be no spaces
> between the -t and N. This option is only useful
> when specified in the ~/.qmail file.
>
> So, if you're trying to generate a vacation message for every reply
> then the lowest granularity you can have is one second.
>
> What's in your .qmail file? If you use the default setup
>
> | /usr/local/bin/vacation username
> /home/psamuel/mailbox
>
> you'll get replies once a week. If you use this
>
> | /usr/local/bin/vacation -t1s username
> /home/psamuel/mailbox
>
> You'll get replies once per second.
>
> 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 Mon, 1 Mar 1999, Samuel Dries-Daffner wrote:
>
> Yes, I have .qmail set as:
>
> | /usr/local/bin/Qvacation -t30s teststud
> /var/mail/teststud
>
> where Qvacation is your program...so I understand this to mean a 30 second
> time frame.
Good. Just checking. So let me recap:
- using the .qmail file above, incoming mail from certain MUA
programs will generate a vacation message, but incoming mail from
other MUA programs will NOT generate a vacation message. An
finally, incoming mail from some MUA programs will somtimes
generate a vacation message and sometimes not.
Is the dbm file changing on each incoming message? You can do a sum on
the dbm file after each message to check. If you have SunOS or Solaris
you can run
makedbm -u .vacation
to see the contents of the file (note the lack of extension). This
will only work if perl stores dbm files with .pag and .dir extensions.
Otherwise, try this quick dbmlist program
#!/usr/local/bin/perl
require 'ctime.pl';
$file = shift;
$file = ".vacation" unless $file;
dbmopen(%DBM, "$file", 0644);
foreach $key (sort keys %DBM)
{
print "$key\n";
print " ", ctime(unpack("L", $DBM{$key}));
}
dbmclose(%DBM);
You should see the date change for each user. Let me know how you go.
Another thing to note is that vacation won't generate a reply if any
of the following conditions is true:
- The sender address includes the string -REQUEST@.
- The sender is you.
- The sender's name is any of:
daemon
postmaster
mailer-daemon
mailer
root
- The sender matches any of the mail addresses listed in the
optional files ~/.vacation.aliases and
~/.vacation.noreply. See the FILES section below for more
details on these files.
- There is a Precedence: bulk or Precedence: junk header.
- There is a Mailing-List: header.
- Your mail address, or any address you have listed in the
optional ~/.vacation.aliases file does not appear in either the
To: or Cc: headers. This feature can be disabled using the -j
option. See the OPTIONS section below for more details on this
option.
- An automatic reply has already been sent to the same address
during the last week. The timeout value may be changed using the
-t option. See the OPTIONS section below for more details on
this option.
- -n was specified on the command line and the user does not have
a ~/.vacation.msg file.
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"
qmail MUST have DNS (caching named plus LAN adresses ?), q. don't use
/etc/hosts.
----------
> Od: D. Carlos Knowlton <[EMAIL PROTECTED]>
> Do: Qmail Mailing List <[EMAIL PROTECTED]>
> Temat: testing on an isolated host.
> Data: 1 marca 1999 19:49
>
> Hi,
>
> I have just set up qmail on a Linux machine on the LAN (isolated from the
> DNS, so it has no registered domain name.) I set my Hostname as
192.168.1.1
> (is this okay?), and I get an error message when I try to send to any
user
> on this machine:
> "delivery 22: deferral:
> Sorry_I_couldn't_find_any_host_by_that_name._(#4.1.2)/"
>
> my hostname is T1-MAST, and I tried that, and got the same message. I
have
> TCPserver running (I think it's running right) and various other services
> running(i.e. ftp, smb, http, telnet, and RIP) could these be conflicting
in
> any way? Any help on this would be great!
>
> -ck
>
