[Next][Index][Thread]
No Subject
% maildirmake $HOME/Maildir
% echo ./Maildir/ > ~/.qmail
Sounds easy. But
1) Do I have to set up maildir for each user separately?
2) Can I set up maildir (under Linux) for new users by doing
% maildirmake /etc/skel/Maildir
% echo ./Maildir/ > /etc/skel/.qmail
I also need to set up maildir2mbox. I understand that
I need to set the variables MAILDIR, MAIL, MAILTMP. But
3) Does it matter if I set MAILDIR
MAILDIR=$HOME/Maildir
or
MAILDIR=$HOME/Maildir/
I am asking because the INSTALL.mbox page warns me not to leave off `/' from
the end of Maildir/ in the command
% echo ./Maildir/ > ~/.qmail
4) When, and how do I run maildir2mbox? Or it is automatically run
by qmail seeing the entry `./Maildir/' in $HOME/.qmail.
Thanks
Mate
Does somebody have a mbox2maildir script they can share?
Would be nice to have for converting to qmail.
BRUCE SPEYER
Elecomm Internet Applications Home of OBGYN.net
512-451-2842, FAX: 512-377-5626 Physician Directed Network
URL: http://www.elecomm.com http://www.obgyn.net
EMAIL: bruce.speyer@xxxxxxxxxxx bruce.speyer@xxxxxxxxx
A Texas HUB and QISV
> Does somebody have a mbox2maildir script they can share?
> Would be nice to have for converting to qmail.
>
http://www.qmail.org/convert-and-create
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
Bruce Speyer writes:
> Does somebody have a mbox2maildir script they can share?
http://www.qmail.org/convert-and-create
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
> Is this invocation of maildir2mbox for every message economical?
No. The way that maildir2mbox achieves reliability is by copying your
entire mbox, plus the new message, to a temporary file, and then moving
that on top of the old file.
If the mbox is about to be scanned by a mail reader, this isn't a big
deal. However, if you do it for each incoming message, it takes
quadratic time as the mbox fills up.
---Dan
Turn an 8MB 486 into a fast Linux mail relay. http://pobox.com/~djb/qmail.html
> > Is this invocation of maildir2mbox for every message economical?
>
> No. The way that maildir2mbox achieves reliability is by copying your
> entire mbox, plus the new message, to a temporary file, and then moving
> that on top of the old file.
>
> If the mbox is about to be scanned by a mail reader, this isn't a big
> deal. However, if you do it for each incoming message, it takes
> quadratic time as the mbox fills up.
>
Then what is the suggestion? Run maildir2mbox manually? As a cron job
in every 5 minutes?
Does xbiff support maildir? What MUA is known to support maildir?
Thanks
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
I wrote:
> 4) When, and how do I run maildir2mbox? Or it is automatically run
> by qmail seeing the entry `./Maildir/' in $HOME/.qmail.
This does not make sense, does it? Just keep the question:
4) When, and how do I run maildir2mbox?
I have qmail 091 and the man page for maildir2mbox does not give a
hint.
Thanks
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
Wierdl Mate writes:
> I'd like to set up maildir. In INSTALL.mbox, I am told only to do:
>
>
> % maildirmake $HOME/Maildir
> % echo ./Maildir/ > ~/.qmail
>
> Sounds easy. But
>
> 1) Do I have to set up maildir for each user separately?
You can specify that every user will be using maildir unless otherwise
instructed by a .qmail file. Do this by changing ALIAS_EMPTY in
conf-unusual.h to "./Maildir/\n".
Then you have to create the Maildir directories.
> 2) Can I set up maildir (under Linux) for new users by doing
> % maildirmake /etc/skel/Maildir
> % echo ./Maildir/ > /etc/skel/.qmail
Probably, although I haven't verified this, and it depends on which
Linux distribution you're using.
> I also need to set up maildir2mbox. I understand that
> I need to set the variables MAILDIR, MAIL, MAILTMP. But
>
> 3) Does it matter if I set MAILDIR
> MAILDIR=$HOME/Maildir
> or
> MAILDIR=$HOME/Maildir/
No.
> I am asking because the INSTALL.mbox page warns me not to leave off `/' from
> the end of Maildir/ in the command
> % echo ./Maildir/ > ~/.qmail
Right. That's because the file delivery mechanism delivers to a
Maildir if the file path ends in a slash, and an mbox otherwise.
> 4) When, and how do I run maildir2mbox? Or it is automatically run
> by qmail seeing the entry `./Maildir/' in $HOME/.qmail.
Um, like this?:
cat >.qmail <<EOF
./Maildir/
|maildir2mbox
EOF
But that's the same as:
cat >.qmail <<EOF
./Mailbox
EOF
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
> > 4) When, and how do I run maildir2mbox? Or it is automatically run
> > by qmail seeing the entry `./Maildir/' in $HOME/.qmail.
>
> Um, like this?:
>
> cat >.qmail <<EOF
> ./Maildir/
> |maildir2mbox
> EOF
>
> But that's the same as:
>
> cat >.qmail <<EOF
> ./Mailbox
> EOF
Well, not exactly. This is what INSTALL.mbox says
2. The trouble with mbox
The mbox format---the format of ~user/Mailbox, understood by BSD Mail
and lots of other MUAs---is inherently unreliable.
Think about it: what happens if the system crashes while a
program is appending a new message to ~user/Mailbox?
The message will be truncated.
.....................
Until your MUA supports maildir, you'll probably want
to convert maildir format to (gaaack) mbox format.
and then in the man page for maildir2mbox
maildir2mbox is reliable: it will not remove messages from
MAILDIR until the messages have been successfully appended
to MAIL.
We had two major power failures yesterday...
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
>>>>> "Wierdl" == Wierdl Mate <matyi@xxxxxxxxxxxxxxxxxxxxx> writes:
[...]
> maildir2mbox is reliable: it will not remove messages from MAILDIR
> until the messages have been successfully appended to MAIL.
But how is that different than qmail's internal queuing system? Isn't that
exactly the same as an Maildir?
> We had two major power failures yesterday...
Get a UPS or ten and hook up an auto-shutdown daemon.
Take care,
John
Wierdl Mate writes:
> > cat >.qmail <<EOF
> > ./Maildir/
> > |maildir2mbox
> > EOF
>
> So this would automatically invoke maildir2mbox *after* each message is
> deposited in Maildir/?
Yes.
> Is this invocation of maildir2mbox for every
> message economical?
No. It's fairly silly, actually. I just did it to point out that
qmail lets you do that.
> Do I have to set PATH to include the qmail bindir for this?
No. It's the same path that you set when you ran qmail-start. No
need for any qmail programs to modify it, since it's at the head of
the path.
> Does maildir2mbox *move* the messages from Maildir or just copies them
> to Mailbox?
Copy.
> So I guess the question is how to invoke maildir2mbox from the most common
> MUAs?
By running qail, pinq, and elq instead.
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
Wierdl Mate writes:
> #!/bin/sh
> # WARNING: This file was auto-generated. Do not edit!
> /var/qmail/bin/maildir2mbox && exec pine ${1+"$@"}
>
> Does this make maildir2mbox run whenever pine checks for new mail
> (every 5 minutes)?
No, but that is an interesting idea. Maybe pinq (and elq) could be a
shell script that runs maildir2mbox in the background every five
minutes as long as pine is still running. I don't have sufficient
shell hacker points to be able to program this. I suspect that it's
simple for a real shell hacker [hint, hint].
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
nelson@xxxxxxxxxx said:
>
> > #!/bin/sh
> > # WARNING: This file was auto-generated. Do not edit!
> > /var/qmail/bin/maildir2mbox && exec pine ${1+"$@"}
> >
> > Does this make maildir2mbox run whenever pine checks for new mail
> > (every 5 minutes)?
>
> No, but that is an interesting idea. Maybe pinq (and elq) could be a
> shell script that runs maildir2mbox in the background every five
> minutes as long as pine is still running. I don't have sufficient
> shell hacker points to be able to program this. I suspect that it's
> simple for a real shell hacker [hint, hint].
If this can be done, then (for me) the only remaining problem would be xbiff.
Mate
--
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
On 10 Nov 1996 nelson@xxxxxxxxxx wrote:
> Date: 10 Nov 1996 02:39:04 -0000
> From: nelson@xxxxxxxxxx
> To: djb-qmail@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: to set up maildir
>
> Wierdl Mate writes:
>
> > #!/bin/sh
> > # WARNING: This file was auto-generated. Do not edit!
> > /var/qmail/bin/maildir2mbox && exec pine ${1+"$@"}
> >
> > Does this make maildir2mbox run whenever pine checks for new mail
> > (every 5 minutes)?
>
> No, but that is an interesting idea. Maybe pinq (and elq) could be a
> shell script that runs maildir2mbox in the background every five
> minutes as long as pine is still running. I don't have sufficient
> shell hacker points to be able to program this. I suspect that it's
> simple for a real shell hacker [hint, hint].
>
> -russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
> Crynwr Software sells network driver support | PGP ok
> 521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
> Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
>
If someone has an idea on how to do this then this would be a most
excellant way to transition to maildir format.
David Wayne Summers "Linux: The choice of a GNU generation."
david@xxxxxxxxxxxxxxxxxxxx PGP Public Key available on request.
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
> > So I guess the question is how to invoke maildir2mbox from the most common
> > MUAs?
>
> By running qail, pinq, and elq instead.
For a few people the mailer is open all the time.
$ less /var/qmail/bin/pinq
shows
#!/bin/sh
# WARNING: This file was auto-generated. Do not edit!
/var/qmail/bin/maildir2mbox && exec pine ${1+"$@"}
Does this make maildir2mbox run whenever pine checks for new mail
(every 5 minutes)?
Last question:
For MH, is it enough to make a file like
#!/bin/sh
# begin inc
/var/qmail/bin/maildir2mbox
inc.bin
#end inc
where inc.bin is the original `inc' command?
Thanks again,
mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
> > 4) When, and how do I run maildir2mbox? Or it is automatically run
> > by qmail seeing the entry `./Maildir/' in $HOME/.qmail.
>
> Um, like this?:
>
> cat >.qmail <<EOF
> ./Maildir/
> |maildir2mbox
> EOF
So this would automatically invoke maildir2mbox *after* each message is
deposited in Maildir/?
Is this invocation of maildir2mbox for every
message economical?
Do I have to set PATH to include the qmail bindir for this?
Does maildir2mbox *move* the messages from Maildir or just copies them
to Mailbox? If it moves, then the above setup assumes that a user
either uses Maildir or Mailbox, but not both. (One could use several
MUAs for mail reading, some might support Maildir some may not).
So I guess the question is how to invoke maildir2mbox from the most common
MUAs? Like
mail
pine
elm
MH (For this, I just probably set up a wrapper for inc)
emacs
Thanks
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
>>>>> "Wierdl" == Wierdl Mate <matyi@xxxxxxxxxxxxxxxxxxxxx> writes:
> I wrote:
>> 4) When, and how do I run maildir2mbox? Or it is automatically run by
>> qmail seeing the entry `./Maildir/' in $HOME/.qmail.
> This does not make sense, does it?
The second part doesn't.
> Just keep the question:
> 4) When, and how do I run maildir2mbox? I have qmail 091 and the man
> page for maildir2mbox does not give a hint.
Manually. :-) You can automate it however you like. The 'man
maildir2mbox' (in v0.92 at least) has instructions on how to invoke it.
I basically gave up on maildirs until the various mailers that I use are
hacked/upgraded to support them.
Take care,
John
>> /krb5
Nope. That was a mistake, we've gotten better (krb5 has used
configure for a long time now, and I think it even defaults correctly;
certainly if you pass --prefix you've got full control, just like with
other configure-based tools.)
As for X11: I've looked at the possibility of converting it to
autoconf :-) It would help in a few places, but would be difficult in
a few others (I could talk about it *off this list* if anyone is
*really* interested, but given that the consortium is unlikely to be
interested, it's a lot of work for nothing... well, it might be worth
a usenix paper :-)
I have a hub site that will feed mail to a fair few uucp leaf
sites. The hub-site is fully connected. This mail discusses how I've
configure qmail to send mail to the leaf sites. I'm keen on getting
some feedback.
For those of you who've used sendmail for this, the easiest way is a
mailertable mapping and a selection of the uucp mailers depending on
the capabilities of the uucp site at the other end (some still want
bangified addresses, others can accept FQDNs) This is quite nice
because it means a single mailertable entry per domain/uucphost combo.
What I want to achieve with qmail is to create a scheme where I only
need to add a virtualdomains entry for each new site.
There is a single alias entry for each uucp mailertype. For now there
is uucpbang and uucpdom. For each uucp site all that's needed is a
virtualdomains entry like this domain:uucpdom-uuhost
An example is:
dec.com:uucpdom-decvax
Where decvax is the uucp name configured into the uucp system. Note
that:
dec.com:uucpdom-decvax
digital.com:uucpdom-decvax
is likewise valid. The main point being that the uucp hostname need
bear no relationship to the domain name.
The only two alias files are:
/var/qmail/alias/.qmail-uucpbang-default
/var/qmail/alias/.qmail-uucpdom-default
Now the bit that needs scrutiny. This is what I have inside the alias
file .qmail-uucpdom-default
|qsmhook uux - -r -a%g -gC `echo $EXT | cut -f2 -d-`!rmail \($EXT3@$HOST\)
Thus a mail to eric@xxxxxxx ultimately generates:
uux - -r -amarkd@xxxxxxxxxxx -gC decvax!rmail (eric@xxxxxxx)
Which is the desired result.
In case it's not obvious, the 'echo $EXT | cut' part is extracting the
uucpname from the extension and the '$EXT3@$HOST' part is
reconstructing the original recipient address. The '\(' business is
for uux parsing - ignore that.
And that's it! Now all I do is add a virtualdomains entry for each new
domain/uucphost combo.
I should be a happy vegemite, but I'm not. Here's why:
1. It seems downright ugly doing all that backquoting and
cutting to determine the uucpname. It's also a bit of a
process burner, the uucp sites don't receive vast amounts of
mail, so it's not really a problem, but it doesn't mean I like
it. A rough count suggests four execs and three forks per mail
delivery - ug.
2. I'm not sure whether $EXT3@$HOST is a bullet-proof way of
reconstructing the original recipient address.
3. I'm not certain that the use of these variables in this way is
secure. I've used qsmhook because I believe that $SENDER and
$UFLINE are vulnerable to use in a naive shell script such as
this.
As mentioned earlier, the main reason for these one-off contortions is
to avoid creating alias entries for each domain/uucphost combo. If I
did an alias per combo, then the entries would look like this:
echo dec.com:uucp-decvax >>/var/qmail/virtualdomains
and the alias file:
|qsmhook uux - -r -a%g -gC decvax!rmail \($EXT2@$HOST\)
Which much tidier with just two execs and one fork - good. But it
strikes me as messier and prone to finger trouble having to provide a
unique alias file with the uucpname encoded multiple times.
Thoughts people?
Oh. A final question. What do people think about putting the
Delivered-To: line on at this point? Misconfigured uucp software is
especially prone to forwarding unrecognized mail straight back to the
hub-site, creating loops.
Regards.
Qmail advocates,
Unfortunately, I've had to give up trying to use qmail along
with listproc 6.0c and have converted back to using sendmail.
I think it is really close but I am on a very tight schedule
and can not spend any more time on this.
I suspect the problem is due to listproc 6.0 (circa 1991-1993)
doing something that is not fully RFC 821 compliant. We had
suspected that it was not correctly terminating lines with a
'\r\n' sequence but I've confirmed that when compiled with
the -DUSE_CARRIAGE_RETURN_LINEFEED does indeed overwrite the
system default of writing just a '\n' and put out '\r\n's.
The challenge!
The mail system is probably my weakest area of expertise. If
somebody else wants to investigate this situation and can come
up with the fix then I will be most grateful and will then switch
back to qmail. It may be worth investigating because there is
always a possibility the problem is with qmail and not just listproc.
The source is at:
ftp://cs-ftp.bu.edu/pub/listserv/listproc6.0c.940712.0.sh.Z
In case anybody can spot the problem, here is a sample SMTP message
by listproc 6.0c (I added the >SMTP<tab> to the front of ech line)
>SMTP HELO
>SMTP MAIL From: <listproc>
>SMTP RCPT To: <bruces@xxxxxxxxxxx>
>SMTP RCPT To: <bruce>
>SMTP DATA
>SMTP Errors-To: bruce
>SMTP Reply-To: listproc
>SMTP Sender: listproc
>SMTP From: listproc
>SMTP To: bruces@xxxxxxxxxxx
>SMTP Cc: bruce
>SMTP Subject: REVIEW TEST-LIST
>SMTP X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
>SMTP X-Comment: OBGYN.net ListProcessor (managed by Elecomm Corporation)
>SMTP
>SMTP Here is the current list of non-concealed subscribers:
>SMTP
>SMTP BRUCE.SPEYER@xxxxxxxxxxx Bruce Speyer
>SMTP BRUCES@xxxxxxxxxxx Bruce Speyer
>SMTP Total number of subscribers: 2 (2 shown here)
>SMTP .
>SMTP QUIT
Thank you
BRUCE SPEYER
Elecomm Internet Applications Home of OBGYN.net
512-451-2842, FAX: 512-377-5626 Physician Directed Network
URL: http://www.elecomm.com http://www.obgyn.net
EMAIL: bruce.speyer@xxxxxxxxxxx bruce.speyer@xxxxxxxxx
A Texas HUB and QISV
At 09:17 PM 11/9/96 -0800, Heinz Wittenbecher wrote:
>Blank mail keeps coming.
Sorry, I believe there are four that went out. It is not
in a loop and will stop.
In my previous message I included some SMTP headers in the
message body. Even though I started them as >SMTP ...command...
Eudora 1.5.4 could not handle it and sent invalid messages to
sendmail 8.6.12 (not qmail) which passed on the blank messages.
Sigh
BRUCE SPEYER
Elecomm Internet Applications Home of OBGYN.net
512-451-2842, FAX: 512-377-5626 Physician Directed Network
URL: http://www.elecomm.com http://www.obgyn.net
EMAIL: bruce.speyer@xxxxxxxxxxx bruce.speyer@xxxxxxxxx
A Texas HUB and QISV
This is a maintenance release for people running systems that use
System V signals. If you have BSD, there is nothing new in here for you.
Thanks to Donnie Barnes and Marc Ewing for finding the problem.
Chael
--
Chael Hall, nowhere@xxxxxxxxxxxxxxxxxx
Making qmail 0.92 and Majordomo 1.94 coexist peacefully
=======================================================
This is version 1.0 of Chael Hall's mj+qmail patches
The release date is 11/10/96.
The latest version can be retrieved via the world-wide web at
http://www.chaos.taylored.com/pub/development/
or via anonymous ftp from
Host: ftp.chaos.taylored.com
Directory: /pub/development.
Filename: mj+qmail-current.tar.gz
These locations will always allow you to access the current version.
Earlier versions may be available as well.
Abstract
========
This is a set of patches to apply to majordomo 1.94 and
several small scripts to make setting up mailing lists
under qmail 0.92 easier. See the very end of this
document for copyright, distribution, and disclaimer.
Introduction
============
Since the two most important software packages on my system are
the list processor and the mailer, I have found it crucial that
they work together. Dan Bernstein's patches for majordomo 1.93
and qmail 0.76+ are fine for majordomo 1.93, but version 1.94
has been significantly redesigned.
Included with this package are patches for majordomo 1.94 that
parallel *most* of the things that Dan did for 1.93. Changes
to majordomo:
1. strip = yes is forced (comments will not be stored in list files.)
2. Addresses starting with anything other than letters and numbers
are rejected.
3. Addresses containing newlines, nulls, backslashes, pipe symbols,
or quotes are rejected.
4. Addresses that are not fully-qualified are rejected. The following
addresses would all be rejected:
joe
joe@xxxx
@host
Any address of the form joe@xxxxxxxxxxx will be accepted, however.
If you do not want this restriction, remove the following lines
from the resulting majordomo.pl file:
# throw out any addresses without FQDN's
if (! /\S+\@\S+\.\S+/ ) {
&main'bitch("UNQUALIFIED ADDRESS $_"); #'
return undef;
}
The following items will not be automatically affected by the patch
due to changes in majordomo:
5. File modes are no longer specified directly in majordomo. It now
stat's the original file to determine what the new file mode should
be. As long as you create your lists mode 0744 or 0740, they will
remain that way. If you choose to make them 0640, however, a line
can be added at the top to weed out people who attempt to post
directly to the outgoing mail alias. It would be *really* nice if
qmail implemented the "+list" format I've seen hacked into it which
would allow one to change the way a file is treated from that point
on to that of a file with mode 0744.
Miscellany
==========
Also included in this package are some scripts that help for setting up
new mailing lists and tips on reducing the risk of denial of service
attacks.
These patches are in no way official. If Dan chooses to release his own
for Majordomo 1.94, that is entirely up to him.
Please let me know if you have any questions, comments, or problems.
Chael Hall
PS - if you're a Majordomo user, keep an eye out on my web site for other
Majordomo patches. I'm currently testing six or seven patches that
enhance the functionality of Majordomo.
--
Chael Hall, nowhere@xxxxxxxxxxxxxxxxxx
Has anyone tried running more than one qmail queue on the same machine?
It wouldn't bother me to install two sets of binaries or to run the second
set of daemons with different environment variables. My situation is that
there are *lots* of overseas e-mail addresses subscribed to my mailing
lists. At least with 0.90 and 0.91 some of these deliveries just seem to
choke the queue for a long time. I'll have 200 messages that have been
sent to 95% of the recipients and are waiting on slow hosts. When I send
a personal e-mail, it takes a long time to go out. Incoming e-mail is
fine and very fast, of course.
What I would like to do is significantly improve the response time for
messages to majordomo (not the lists, but the request processor) and
individuals on my machine. It's going to be a few more weeks before I can
upgrade the machine physically, so this sounds like a reasonable
work-around.
Alternately, is there any good way to get these messages to stop clogging
up the queue. I want them to eventually deliver, but there's no reason
why they have to even be attempted right away if we've been having trouble
contacting the host.
Chael
--
Chael Hall, nowhere@xxxxxxxxxxxxxxxxxx
http://www.chaos.taylored.com/home/nowhere/
Wierdl Mate writes:
> nelson@xxxxxxxxxx said:
> >
> > > #!/bin/sh
> > > # WARNING: This file was auto-generated. Do not edit!
> > > /var/qmail/bin/maildir2mbox && exec pine ${1+"$@"}
> > >
> > > Does this make maildir2mbox run whenever pine checks for new mail
> > > (every 5 minutes)?
> >
> > No, but that is an interesting idea. Maybe pinq (and elq) could be a
> > shell script that runs maildir2mbox in the background every five
> > minutes as long as pine is still running. I don't have sufficient
> > shell hacker points to be able to program this. I suspect that it's
> > simple for a real shell hacker [hint, hint].
What about:
#!/bin/sh
/var/qmail/bin/maildir2mbox
while :; do sleep 300; /var/qmail/bin/maildir2mbox; done &
BGPID=$!
pine ${1+"$@"}
kill -9 $BGPID
This hasn't been tested.
Bert
> On Sun, 10 Nov 1996, Bert Gijsbers wrote:
>
> > What about:
> >
> > #!/bin/sh
> > /var/qmail/bin/maildir2mbox
> > while :; do sleep 300; /var/qmail/bin/maildir2mbox; done &
> > BGPID=$!
> > pine ${1+"$@"}
> > kill -9 $BGPID
>
> This is no good -- how is pine going to delete messages? The only way to
> make pine work with maildir is to change c-client to work with it.
> --
I am very confused: the man page for maildir2mbox says
DESCRIPTION
maildir2mbox moves mail from a maildir-format directory to
an mbox-format file.
I am assuming that this means once the message is in Mailbox, it is
removed from Maildir (though I got a reply saying only copying is
going on---a fact that would make maildir2mbox basically useless for
this purpose, since my mbox confined MUA could never remove a message).
Now, when I run the above script, I suppose I have no problem with
marking messages for deletion in pine. But then (you are suggesting) when
pine exits it will not be able to remove messages from Mailbox because
the `maildir2mbox process' is killed after pine's exit?
If pine does remove a message from Mailbox and maildir2mbox
previously removed it from Maildir, then where will the message
show up its ugly head?
Mate
M\'at\'e Wierdl
Department of Mathematical Sciences
University of Memphis,
E-mail: matyi@xxxxxxxxxxxxxxxxxxxxx
Small request: is it possible to maintain the list archive so that the
dates on the messages are also exhibited?
Thanks
Mate
On Sun, 10 Nov 1996, Bert Gijsbers wrote:
> What about:
>
> #!/bin/sh
> /var/qmail/bin/maildir2mbox
> while :; do sleep 300; /var/qmail/bin/maildir2mbox; done &
> BGPID=$!
> pine ${1+"$@"}
> kill -9 $BGPID
This is no good -- how is pine going to delete messages? The only way to
make pine work with maildir is to change c-client to work with it.
--
Tod MCQuillin
On Sun, 10 Nov 1996, Wierdl Mate wrote:
> I am very confused: the man page for maildir2mbox says
>
> DESCRIPTION
> maildir2mbox moves mail from a maildir-format directory to
> an mbox-format file.
>
> I am assuming that this means once the message is in Mailbox, it is
> removed from Maildir
I am sorry. I was wrong. maildir2mbox does in fact delete the messages
from the maildir, and appends them to the mbox. It is a move, not a copy.
As such, it will likely work fine in a wrapper around pine. I am sorry to
mislead you. Next time I'll be sure to drink more coffee.
--
Tod McQuillin
[ Wierdl Mate <matyi@xxxxxxxxxxxxxxxxxxxxx> 1996-11-10 10:51 -0600 ]
|---
| If this can be done, then (for me) the only remaining problem would be
| xbiff.
Elementary, my dear Watson.
Put this in your .qmail (don't forget to specify your maildir too):
|echo >> .newmail
Then have xbiff check .newmail instead of the presumed mailbox.
I run it as follows:
xbiff -xrm '*mailbox.file: .newmail' -xrm '*onceOnly: true'
Finally, let maildir2mbox be the script
#!/bin/sh
/var/qmail/bin/maildir2mbox && rm -f $HOME/.newmail
and make sure the shell script is ahead of the other maildir2mbox in
$PATH.
- Harald
Here's the announcement that I just made to the majordomo-users mailing
list. Since a bunch of people here use Majordomo with qmail, I thought it
might be appropriate:
I'm working on switching all of my mailing lists over from Majordomo 1.92
to version 1.94. In the process of making all of the changes to 1.94 that
I had made to 1.92, I decided to go ahead and make each one a patch.
Since these patches may be useful to others, I've put them together in a
package.
Here's the README information from the package:
Chael's Majordomo Patches
=========================
Version
=======
This is version 1.00 of Chael Hall's Majordomo patches
The release date is 11/10/96.
The latest version can be retrieved via the world-wide web at
http://www.chaos.taylored.com/pub/development/
or via anonymous ftp from
Host: ftp.chaos.taylored.com
Directory: /pub/development.
Filename: mj-patches-current.tar.gz
These locations will always allow you to access the current version.
Earlier versions may be available as well.
Table of Contents
=================
[1] Abstract
[2] Introduction
[3] Applying the Patches
[4] Copyright and Disclaimer
[5] Files
[1] Abstract
============
This is a set of patches to apply to Majordomo 1.94 that
add functionality or fix specific problems with the
software. See the very end of this document for
copyright, distribution, and disclaimer.
[2] Introduction
================
In the time that I have been running Majordomo, I have made
several changes to the software to make my life easier. Some
of the changes were requested by list members and others were
just my idea of a way to accomplish a specific goal. Most of
the patches in this package add non-standard features to
Majordomo that allow me to run my mailing lists the way I want
to (automatically!) without being constantly bombarded with
questions from the list members.
If you are running qmail and are interested in making Majordomo
and qmail work well together, please go to the web or FTP site
listed at the top of this document and retrieve the package
named 'mj+qmail.' That package includes patches to Majordomo,
suggestions for improving security, and scripts to help setup
new lists.
If you are running sendmail, smail or another mailer that
makes you tear your hair out, you might consider retrieving
qmail and trying it out. It's significantly faster than any
other mailer I have used and is very flexible. You can install
and play with it without affecting your other mailer's
environment. So give it a shot! qmail can be retrieved via
anonymous FTP from ftp://koobera.math.uic.edu/pub/software/.
The filename of the latest release should be 'qmail.tar.gz'
[3] Applying the Patches
========================
Backup the Majordomo files just to be safe. Then, assuming you have the
program 'patch', you can simply execute it with the patches file included
with this distribution on standard input:
% patch < guidelines/patch
I STRONGLY recommend that you read the accompanying README file for each
patch before you apply it.
[4] Copyright and Disclaimer
============================
I wrote these utilities for myself and thought that other
people might want to use them too. If they help you, great.
If they don't, write your own. Please send any patches to me at
nowhere@xxxxxxxxxxxxxxxxxx, but do NOT distribute these files
individually or in modified form. Despite the standard disclaimer
(which you all know and love, so I'm not going to repeat it here),
I reserve all rights to this software and this is the way I want
it. If you can't deal, delete it.
mj-patches-1.00
Copyright 1996 Chael Hall (nowhere@xxxxxxxxxxxxxxxxxx)
All rights are reserved. You are granted a non-exclusive license
to use and modify these files as long as you do not distribute
modified versions or any copy that does not contain all of the
files in this package.
majordomo 1.94
Copyright 1992 D. Brent Chapman
[5] Files
=========
The files included with this distribution are:
README - This file
commands/ - Patch to allow shortened forms of some
commands
commands/README - Instructions for applying this patch
commands/patch - Context diff patch for Majordomo
guidelines/ - Patch to allow multiple files to be
sent upon subscribing to a list
guidelines/README - Instructions for applying this patch
guidelines/patch - Context diff patch for Majordomo
redirection/ - Patch to redirect botched requests of the
form 'subscribe LIST DIGEST ...' to
'subscribe LIST-DIGEST ...'
redirection/README - Instructions for applying this patch
redirection/patch - Context diff patch for Majordomo
refuse/ - Patch to implement a blocking mechanism
in resend for addresses that should not
be allowed to post (a blacklist.)
refuse/README - Instructions for applying this patch
refuse/patch - Context diff patch for Majordomo
reply-to/ - Patch to make resend remove Reply-To:
headers IFF it will be adding its own
Reply-To: header to the message
reply-to/README - Instructions for applying this patch
reply-to/patch - Context diff patch for Majordomo
resend-fix/ - Patch to fix miscellaneous bugs in resend
resend-fix/README - Instructions for applying this patch
resend-fix/patch - Context diff patch for Majordomo
virtual-rewrite/ - Patch for resend to correctly rewrite
list addresses when dealing with virtual
domains
virtual-rewrite/README - Instructions for applying this patch
virtual-rewrite/patch - Context diff patch for Majordomo
--
Chael Hall, nowhere@xxxxxxxxxxxxxxxxxx
http://www.chaos.taylored.com/home/nowhere/
Has there been any discussion about a logo for QMail? IIRCC, this is
mentioned in one of QMail's future-directed documentation files but
I don't recall any other discussion of this.
Having a logo would be a help in making QMail look legitimate and all of
that marketing related rot. :-)
Methinks there should also be a "Powered by QMail" logo.
Take care,
John
At 09:46 PM 11/10/96 -0600, you wrote:
>> How about a wimpy-looking Q with an envelope in the center, like the
>> one you'd find on <URL:http://www.qmail.org>?
Not good enough if marketing is any consideration,
and you wish to sell the qmail "mystique", and push up subscribers.
When I say "sell" I don't necessarily mean for cash; selling the
concept to potential users who may not be as Internet/Sendmail savvy
as most current qmail advocates, who require more sizzle to pick up on it.
BRUCE SPEYER
Elecomm Internet Applications Home of OBGYN.net
512-451-2842, FAX: 512-377-5626 Physician Directed Network
URL: http://www.elecomm.com http://www.obgyn.net
EMAIL: bruce.speyer@xxxxxxxxxxx bruce.speyer@xxxxxxxxx
A Texas HUB and QISV
On 11 Nov 1996, John Mitchell wrote:
> Has there been any discussion about a logo for QMail? IIRCC, this is
> mentioned in one of QMail's future-directed documentation files but
> I don't recall any other discussion of this.
>
> Having a logo would be a help in making QMail look legitimate and all of
> that marketing related rot. :-)
>
> Methinks there should also be a "Powered by QMail" logo.
How 'bout a powerful looking Q with an envelope coming out of the center?
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@xxxxxxxxxxx flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================
Vince Vielhaber writes:
> How 'bout a powerful looking Q with an envelope coming out of the center?
How about a wimpy-looking Q with an envelope in the center, like the
one you'd find on <URL:http://www.qmail.org>?
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
On 11 Nov 1996 nelson@xxxxxxxxxx wrote:
[Logo]
> How about a wimpy-looking Q with an envelope in the center, like the
> one you'd find on <URL:http://www.qmail.org>?
Well, it IS consistent with KISS.
-Mike
Michael Brian Scher (MS683) | Anthropologist, Attorney, Part-Time Guru
http://www.tezcat.com/~strange/ | strange@xxxxxxxxxxxx
strange@xxxxxxxxxx | mbscher@xxxxxxxxxxxxxxxxxxx
I'm a legal anthropologist; what's an illegal anthropologist?
On Sun, 10 Nov 1996, Mike Scher wrote:
> On 11 Nov 1996 nelson@xxxxxxxxxx wrote:
> [Logo]
> > How about a wimpy-looking Q with an envelope in the center, like the
> > one you'd find on <URL:http://www.qmail.org>?
>
> Well, it IS consistent with KISS.
Yeah, but 'Kiss' would be ashamed of something that whimpy. :)
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@xxxxxxxxxxx flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================
Don't the docs say that the qmail logo is a shark?
Nope, THOUGHTS: qmail's logo is a dolphin.
Adam
--
"It is seldom that liberty of any kind is lost all at once."
-Hume
Vince Vielhaber <vev@xxxxxxxxxxx> writes:
> How 'bout a powerful looking Q with an envelope coming out of the center?
It should have quite a lot of envelopes flying out simultaneously!
--
Norm
On 10 Nov 1996, Norm Aleks wrote:
> Vince Vielhaber <vev@xxxxxxxxxxx> writes:
> > How 'bout a powerful looking Q with an envelope coming out of the center?
>
> It should have quite a lot of envelopes flying out simultaneously!
I like that, now have some more ideas...
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@xxxxxxxxxxx flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
==========================================================================
> > Vince Vielhaber <vev@xxxxxxxxxxx> writes:
> > > How 'bout a powerful looking Q with an envelope coming out of the center?
> >
> > It should have quite a lot of envelopes flying out simultaneously!
>
> I like that, now have some more ideas...
How about a big fat powerful Q with the slash replaced by a lightning
bolt. Put the word "mail" inside the lightning bolt. Have a flurry of
envelopes exploding out of where the lightning bolt strikes. :)
------------------
Brian R. Showalter
showalte@xxxxxxxx
I'm needing to use tcpserver (because inetd thinks an SMTP load is too
high), but I need to set RELAYCLIENT for some hosts. Can I use
tcp_wrappers? If not, should I use tcpserver "sh -c 'case
$TCPREMOTEHOST in; *.example.com) RELAYCLIENT="" ;;esac; /var/qmail/bin/qmail-smtpd;'"
-russ <nelson@xxxxxxxxxx> http://www.crynwr.com/~nelson
Crynwr Software sells network driver support | PGP ok
521 Pleasant Valley Rd. | +1 315 268 1925 voice | The more corrupt the state,
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | the more numerous the laws.
>
> |grep "^[#&]$SENDER$" ".qmail-$EXT" || (echo "You are not authorized to send mail to this list."; exit 1)
> &address
> &address
> ...
>
OK, I can't find any documentation on where $SENDER is set and to what exactly
Could $SENDER be "Timothy Hunt <qmail@xxxxxxxxxxxxxx>" ?
Or would it always be stripped to "qmail@xxxxxxxxxxxxxx" ?
Timothy
>
>
> >
> > |grep "^[#&]$SENDER$" ".qmail-$EXT" || (echo "You are not authorized to send mail to this list."; exit 1)
> > &address
> > &address
> > ...
> >
>
> OK, I can't find any documentation on where $SENDER is set and to what exactly
>
> Could $SENDER be "Timothy Hunt <qmail@xxxxxxxxxxxxxx>" ?
> Or would it always be stripped to "qmail@xxxxxxxxxxxxxx" ?
Hrm. I answered this myself by running printenv :o)
However, it appears it uses the envelope from: address which while more
secure than the header from: address, for various reasons
it's likely I'll want to use the header from: address (Yes, I admit
I'm doing some very simple rudimentary security)
Is there any simple way of getting hold of this, or am I going to have
to start thinking and write a program?
<grins>
Timothy