qmail Digest 2 Aug 1999 10:00:01 -0000 Issue 716
Topics (messages 28430 through 28453):
autoconf?
28430 by: "D. J. Bernstein" <[EMAIL PROTECTED]>
28438 by: Russ Allbery <[EMAIL PROTECTED]>
imap with vmailmgr ? (...imp)
28431 by: "Olivier M." <[EMAIL PROTECTED]>
unable to bind
28432 by: Ryan Cleary <[EMAIL PROTECTED]>
28435 by: Frederik Lindberg <[EMAIL PROTECTED]>
28439 by: Robert <[EMAIL PROTECTED]>
Vchkpw
28433 by: Vignesa Moorthy <[EMAIL PROTECTED]>
28436 by: Ken Jones <[EMAIL PROTECTED]>
Maildir support for Pine 4.10
28434 by: [EMAIL PROTECTED]
28443 by: Faried Nawaz <[EMAIL PROTECTED]>
ezmlm web based search of archives
28437 by: Ken Jones <[EMAIL PROTECTED]>
M$ Exchange -> qmail
28440 by: "Olivier M." <[EMAIL PROTECTED]>
28441 by: Thomas Neumann <[EMAIL PROTECTED]>
28442 by: "Olivier M." <[EMAIL PROTECTED]>
28447 by: Thomas Neumann <[EMAIL PROTECTED]>
28448 by: Ira Abramov <[EMAIL PROTECTED]>
tcpserver and imapd
28444 by: Adam H <[EMAIL PROTECTED]>
Eliding quotes in envelope?
28445 by: Scott Schwartz <[EMAIL PROTECTED]>
Internet draft for VERP
28446 by: Scott Schwartz <[EMAIL PROTECTED]>
serial mail
28449 by: [EMAIL PROTECTED]
baboo.smtp does not work by using qmail.
28450 by: Ferhat Doruk <[EMAIL PROTECTED]>
ezmlm response
28451 by: "Peter Samuel" <[EMAIL PROTECTED]>
delivery question
28452 by: Van Liedekerke Franky <[EMAIL PROTECTED]>
unable to exec qq
28453 by: "Petr Novotny" <[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]
----------------------------------------------------------------------
Russ Allbery writes:
> Furthermore, with a fixed Makefile, how do you intend to optionally
> include or exclude portions of a build tree from the build?
You can't. A Makefile specifies a list of source files for each target
file. The make program reads these lists and rebuilds any targets that
may be out of date. It doesn't understand that the lists in turn might
depend on other variable sources, such as your build-selection option.
The usual workaround is a manual two-step configure-and-build process,
first creating Makefile from whatever source files, then running make.
Unfortunately, if the sources of Makefile are changed, the user has to
run the first step again, then recreate every target; the make program
still has no idea how the targets depend on the Makefile source files.
My project-management tools eliminate this problem by using a top-down
build strategy with what one might call ``just-in-time dependencies'';
but it will take some work to clean these tools up for widespread use.
Fortunately, static Makefiles are adequate for all the qmail packages.
> scripting switches to configure is a hell of a lot easier than
> keeping and automatically applying patches to a bunch of conf-* files.
How so? It seems to me that ``echo /opt/foo > conf-home;make'' is just
as easy as ``./configure --prefix=/opt/foo;make''. What's the problem?
> Also note that Dan is reinventing parts of autoconf in his build process;
Well, actually, autoconf is reinventing ideas that were popularized by
the sysconf tool in my yabbawhap package in comp.sources.unix in early
1991. But don't allow the historical facts to cloud your judgment. :-)
---Dan
D J Bernstein <[EMAIL PROTECTED]> writes:
> My project-management tools eliminate this problem by using a top-down
> build strategy with what one might call ``just-in-time dependencies'';
> but it will take some work to clean these tools up for widespread use.
I'd love to see this stuff; that would be great.
>> scripting switches to configure is a hell of a lot easier than keeping
>> and automatically applying patches to a bunch of conf-* files.
> How so? It seems to me that ``echo /opt/foo > conf-home;make'' is just
> as easy as ``./configure --prefix=/opt/foo;make''. What's the problem?
Hm. That's a very good point; I hadn't thought of it in that fashion
before. (Not sure why, as it's a much better method than what I was
thinking of.) I'd still say that autoconf is easier to use, though,
primarily because of ./configure --help (which could be duplicated as a
file in the tarball, but that command is a lot more universal than the
documentation format for such things), the output it produces (which I've
used to notice and isolate problems before the build on not a few
occasions -- if I know what the answers to autoconf questions should be
and I see something else, that's a good warning sign), and because it's
easier to use than conf-* files that contain multiple values where you
can't just do an echo.
>> Also note that Dan is reinventing parts of autoconf in his build
>> process;
> Well, actually, autoconf is reinventing ideas that were popularized by
> the sysconf tool in my yabbawhap package in comp.sources.unix in early
> 1991. But don't allow the historical facts to cloud your judgment. :-)
Heh. :) I was thinking more of the specific tests than the ideas; the
ideas have been independently reinvented any number of times (cf
metaconfig as well), but currently autoconf has probably the largest
library of tests and portability tweaks of any of those tools.
autoconf is really two separate things rolled into one; it's a library of
tests and a build process generator. The latter could probably be
improved on in any number of ways; I'd love to see better build processes
that can leverage off the same library of tests.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
Hello,
I'm maintaining a webmail server using imp ( http://horde.org/imp ) and
a standard qmail installation, using the UW-IMAP patches from David Harris
( http://www.davideous.com/imap-maildir/ ).
Everything is fine so far. Now, I'd like to create new IMAP mailboxes
for different domains, without having to create new Unix users
(adduser, etc...). I'm currently using vmailmgr for pop and forwarding
accounts : is there a way to use vmailmgr mailboxes (
/home/domain.ch/users/username/new|cur|tmp
directories ) via IMAP ? I guess it wouldn't be impossible : is anybody working
on it ?
Cheers,
Olivier
Sam wrote:
> B) What is listening on the same port. netstat will show you that. Don't
> forget to use the -a option to netstat.
netstat -ap --inet
will also show you (with the -p flag) what process ID's are listening to
each port.
Hunt it down and kill it!
--Ryan Cleary
I bet $0.02 that you have a smtp line in /etc/inetd.conf
-Sincerely, Fred
Frederik Lindberg, Inf. Dis, WashU, St. Louis, MO
I really appreciate all the help and suggestions everyone has made here.
I finally got the smtp server working!!!!!! For the record and for the
mail archives in case anyone in the future has this problem. It appears
that on BSDI 4.01, even if you comment out all references to sendmail in
the boot scripts it still somehow reserves that port. I'm very new to
BSDI(but not unix in general), so I'm not certain as to how and why it
does this. I solved the problem by moving /etc/sendmail*
/somewhere/else and rebooted, and it worked fine.
I did run ps ax | grep senmail and nothing showed up. I spent about an
hour learning all the nifty options to netstat and tried running it with
several different switches, and it always showed it was listening on
port 25.
The really sad part to all this is, with all the tinkering and
experimenting I've done, I've somehow managed to bring down the pop3
daemon. ugggggggggg Will it ever end?? I'm getting the following error
in my /var/log/qmail/qmail-pop3d log:
Aug 1 14:16:05 kong qmail: xxxxxxx.xxxx alert: oh no! lost spawn
connection! dying...
Any suggestions?? My first thought was to drop it out the window, but I
think I'd get into a little hot water over that one.
Thank you,
Robert
[EMAIL PROTECTED] wrote:
>
> On Sat, 31 Jul 1999, Robert wrote:
>
> > Hello,
> > I recently install qmail on a BSDI 4.01 server, and I'm having a really
> > bad time trying to get it running. I read the HOWTO located here
> > http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
> > explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
> >
> > xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used
>
> are you sure sendmail isn't running?
> ps ax | fgrep sendmail
>
> RjL
I have installed the Vchkpw package. However, when used to add new users,
it creates the Maildir folder, but it does not add the .qmail file to the
users root directory.
Is there a something i need to configure. Or is there a way to automate the
creation of the .qmail file in the users root directory.
By the way, I am using Maildirs.
Thank you
Vignesa Moorthy wrote:
>
> I have installed the Vchkpw package. However, when used to add new users,
> it creates the Maildir folder, but it does not add the .qmail file to the
> users root directory.
>
> Is there a something i need to configure. Or is there a way to automate the
> creation of the .qmail file in the users root directory.
>
> By the way, I am using Maildirs.
>
> Thank you
vchkpw does not create .qmail files for users added with the
vadduser command. It does not need to.
If you are using it
with a virtual domain, the virtual domains main directory
contains a .qmail-default file which starts up the vdelivermail
program which will deliver the mail into sub directories for
each pop user.
If you are using it with a local domain, vadduser will create
an entry in ~users/assign to point the mail to a sub directory
in the ~vpopmail/users. There is no need for a .qmail file.
If you are trying to add a local user which is in /etc/passwd,
then vadduser should not be used.
--
Ken Jones
mailto:[EMAIL PROTECTED]
http://www.inter7.com/qmailadmin/ - web based qmail adminstration
Faried Nawaz writes:
> [EMAIL PROTECTED] writes:
>
> I hate replying to a mailing list just to correct someone, when it has
> nothing to do with the mailing list. But oh well.
>
> [...]
>
> Pine can not read Maildir which is the format "I" am using on my system to
> be compatible (and stable).
>
> The original person that posted this email to the list was asking for a
> patch for Pine to read Maildir. If there was such a patch, I was unaware
> and wanted more information.
>
> But a patch is not available for Pine to read Maildir formats. Therefore
> another discussion came up talking about installing IMAP to use Maildir
> support. Unfortantly there seems to be no clean way to install these
> patches to IMAP.
>
> As pointed out elsewhere in this thread, thare are multiple patches that
> let pine read maildir folders. Check the qmail web site.
>
>
> Why is this patch for IMAP important? Pine can read IMAP just fine.
> Therefore, you WANT to install IMAP on a server using Maildir to get Pine
> to work on the system.
>
> No, you don't.
Yes you do if you are using vchkpw and all popusers Maildirs are
owned/groupped via vchkpw's UID. Therefore making Pine in accessable to
these files because of permisisons. I am sure you may could create the
owner of each mailbox to match each user and place the vchkpw group into a
group to read. But who has the time to re-write all of those scripts,
qmailadmin, and new scripts to create this upon new addusers?
I'd rather install IMAP and be done.
Eric
President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
Yes you do if you are using vchkpw and all popusers Maildirs are
owned/groupped via vchkpw's UID.
Which, by the say, is a somewhat atypical setup depending on your
environment.
If you're using vchkpw, you'd not only need an IMAP server with Maildir
support, but a well-hacked IMAP server that understands vchkpw's directory
structure.
In just about all other cases where you have qmail and pine installed on
the same machine, you want Maildir support in pine.
I'd rather install IMAP and be done.
In your environment, it makes sense. Not in everyone else's.
Peter Janett wrote:
Sorry if this is not the place to post..
We need to setup a web based search of ezmlm mailing lists.
Does anyone have recommendations on any open software that
does this?
I've looked at glimpse and MHonArc and Wilma
http://www.oac.uci.edu/indiv/ehood/mhonarc.html
It shows support for majordomo based lists, but nothing
specific to ezmlm
--
Ken Jones
mailto:[EMAIL PROTECTED]
http://www.inter7.com/qmailadmin/ - web based qmail adminstration
I have a friend which has an Microsoft Exchange Mail server ("main" server)
always connected to the internet, and there are a few (about 10)
other MS-Exchange servers which are connecting directely to the main
mailserver every hour using ISDN-dialin (ppp).
Now, we'd like to replace the NT server with a linux/qmail server, which
will most probably need fewer reboots. Problem : the other client servers
will still use Exchange : will the communication between the systemes
work fine ?
I guess that an Exchange server don't simply use STMP to communicate
with another exchange server. What kind of protocol is it, and is it
possible to emulate it using qmail tools ? I looked on the qmail
homepage and in some other places, and didn't found much details
about that : maybe you know a little bit more ? I'm just looking
for some more docs (url...) and why not qmail/exchange configuration
examples.
Thanks in advance,
Olivier, with soon one more unix server :)
PS: btw, when will the O'Reilly Qmail book be for sale ? :)
"Olivier M." <[EMAIL PROTECTED]> writes:
>
> I guess that an Exchange server don't simply use STMP to communicate
> with another exchange server. What kind of protocol is it, and is it
> possible to emulate it using qmail tools ? I looked on the qmail
> homepage and in some other places, and didn't found much details
> about that : maybe you know a little bit more ? I'm just looking
> for some more docs (url...) and why not qmail/exchange configuration
> examples.
I'm not an expert on M$ Exchange by any means, but I know
for sure that Exchange can run an SMTP server for itself,
and this is where you can hook up to. Just have all customer
mail delivered into Maildirs on your new qmail machine
(one Maildir per customer), then you can use a small program
to fetch the mail using POP3 from the qmail machine to the
Windows machines running Exchange, where you re-inject them
into the local SMTP server offered by Exchange. I do the
same for a bunch of customers running Lotus Notes SMTP
servers behind dialup lines.
I think Exchange can also use ETRN to tell another SMTP
server that it wants it to send queued mail, but ETRN
is even worse, being incredibly insecure and qmail doesn't
support it w/o a patch anyway, so stay away from it.
-t
Thanks for your answer Thomas,
On Sun, Aug 01, 1999 at 11:47:27PM +0200, Thomas Neumann wrote:
> I'm not an expert on M$ Exchange by any means, but I know
> for sure that Exchange can run an SMTP server for itself,
> and this is where you can hook up to. Just have all customer
> mail delivered into Maildirs on your new qmail machine
> (one Maildir per customer), then you can use a small program
> to fetch the mail using POP3 from the qmail machine to the
> Windows machines running Exchange, where you re-inject them
> into the local SMTP server offered by Exchange. I do the
One maildir per user or per domain ? If it is per domain,
then it should be possible to use serialmail to send the mails
from the linux server to the NT client: it's good documented.
> I think Exchange can also use ETRN to tell another SMTP
> server that it wants it to send queued mail, but ETRN
> is even worse, being incredibly insecure and qmail doesn't
> support it w/o a patch anyway, so stay away from it.
okay... didn't found anything about ETRN on the qmail
homepage. then I'll make some tests using only smtp.
Thanks for your hints!
Olivier
"Olivier M." <[EMAIL PROTECTED]> writes:
> On Sun, Aug 01, 1999 at 11:47:27PM +0200, Thomas Neumann wrote:
> > I'm not an expert on M$ Exchange by any means, but I know
> > for sure that Exchange can run an SMTP server for itself,
> > and this is where you can hook up to. Just have all customer
> > mail delivered into Maildirs on your new qmail machine
> > (one Maildir per customer), then you can use a small program
> > to fetch the mail using POP3 from the qmail machine to the
> > Windows machines running Exchange, where you re-inject them
> > into the local SMTP server offered by Exchange. I do the
> One maildir per user or per domain ? If it is per domain,
> then it should be possible to use serialmail to send the mails
> from the linux server to the NT client: it's good documented.
Per (customer-) domain. You need to find a method to trigger
serialmail on the qmail server once the Exchange machine is logged in,
and this needs to be secure (password protected or whatever). All in
all this will not be easier than the POP3 solution I outlined.
-t
On Sun, 1 Aug 1999, Olivier M. wrote:
> I have a friend which has an Microsoft Exchange Mail server ("main" server)
> always connected to the internet, and there are a few (about 10)
> other MS-Exchange servers which are connecting directely to the main
> mailserver every hour using ISDN-dialin (ppp).
if the dial-in is done by the exchange server itself, i.e. not an ISDN
router, then ETRN is easy to config for the Exchange's dialer and on the
Qmail side I'd implement Autorun which I read is very effective as an ETRN
replacement (and it does indeed work with serialmail and maildir2smtp. all
documented). I'm working for a fairly large ISP, and the above is the way
I'll convert us to work soon.
I have the UW Imapd running with tcpserver -- just one problem. It
authenticates and logs in fine (using IMP) but it seems to be reading
user root's directory.. as when I click on folders it basiaclly show s a
directory of /root
very weird.
I am running imapd as the qmaild users.. It doesn't work if ran as root.
Any ideas on why it may be doing this?
Thanks,
Adam
"D. J. Bernstein" <[EMAIL PROTECTED]> writes:
| That's the QSBMF encoding, which is line-delimited and has no special
| quoting characters. Why do you think the QSBMF encoding should be the
| same as the SMTP encoding?
Why invent a new, incompatable scheme which looks a lot like the old
standard one? Principle of least surprise, again.
"D. J. Bernstein" <[EMAIL PROTECTED]> writes:
| QMAILSUSER=schwartz+dsn
| What's the problem?
That you didn't substantively respond to the message you just replied
to.
It's better to fix bugs than to work around them.
| If your conf-break is +, you might have a mailing list called
|
| [EMAIL PROTECTED]
That looks like a weak attempt at insult, which, unfortunately, doesn't
address the issue:
qmail-inject's verp flags silently turn valid envelopes into invalid
ones iff someone uses a different configuration than the author and
doesn't take otherwise unnecessary evasive action.
If sendmail or postfix did that, you'd flame about it constantly.
If you don't want to fix the problem, then please adjust the
documentation to say so, and why.
Hi all,
I have a strange problem on my serial mail,
It was working well and now suddenly it gives this error
on my client side (narada.col7.metta.lk)
#!/bin/sh
PATH=/var/qmail/bin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
export PATH
/usr/local/bin/maildirsmtp ~alias/pppdir alias-ppp- 204.143.107.46 dhamma.metta.lk
serialsmtp: fatal: network read error: timed out
serialsmtp: fatal: network read error: timed out
serialsmtp: fatal: network read error: timed out
maildirserial: fatal: making no progress, giving up
in /var/log/messages
======================
Aug 1 21:42:47 narada identd[1872]: Connection from dhamma.metta.lk
Aug 1 21:42:47 narada identd[1872]: from: 204.143.107.46 ( dhamma.metta.lk ) for:
1057, 25
Aug 1 21:42:47 narada identd[1872]: Returned: 1057 , 25 : NO-USER
Aug 1 21:43:02 narada identd[1873]: Connection from dhamma.metta.lk
Aug 1 21:43:02 narada identd[1873]: from: 204.143.107.46 ( dhamma.metta.lk ) for:
1058, 25
Aug 1 21:43:02 narada identd[1873]: Returned: 1058 , 25 : NO-USER
Suggestions are very welcome
Jacob
Thanks Fred, it worked.
-----Original Message-----
From: Fred Lindberg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 29, 1999 4:24 PM
To: Ferhat Doruk; [EMAIL PROTECTED]
Subject: Re: baboo.smtp does not work by using qmail.
On Wed, 28 Jul 1999 14:37:29 +0300, Ferhat Doruk wrote:
>which sends mail by using smtp.dll (bamboo.smtp). These ASP pages does not
A guess would be that this _is_ a Microsoft bug and that it is the bare
LF one. A problem in the SMTP dialog from "bamboo" would give you the
differential symptoms you describe. Log tcpserver output. There are
also notes in the mailing list archives on how to log qmail-smtpd info.
Personally, I'd just try the bare-LF patch and see if it helps.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
On 1 Aug 1999 Ken Jones <[EMAIL PROTECTED]> wrote:
>
> Peter Janett wrote:
>
> Sorry if this is not the place to post..
>
> We need to setup a web based search of ezmlm mailing lists.
>
> Does anyone have recommendations on any open software that
> does this?
>
> I've looked at glimpse and MHonArc and Wilma
> http://www.oac.uci.edu/indiv/ehood/mhonarc.html
>
> It shows support for majordomo based lists, but nothing
> specific to ezmlm
I use MHonArc with a number of ezmlm lists. There's nothing special
about MHonArc that ties it to majordomo.
This is what I do. This assumes that you have a list called "itforum"
and its directory is in ~alias/ITFORUM. Modify the values below to
suit your lists. These are real examples, cut and pasted from a real
system.
- create an alias for the list archive. This will contain delivery
instructions for archiving each message on the list:
cat << EOF > ~alias/.qmail-itforum-archive
# ITForum Mailing List. Archive these messages for viewing on the web
| mhonarc -umask 022 -quiet -add -reverse -treverse -outdir
|/var/local/mail-archives/itforum
EOF
- ensure the file has the correct permissions
chown alias ~alias/.qmail-itforum-archive
chgrp qmail ~alias/.qmail-itforum-archive
chmod 644 ~alias/.qmail-itforum-archive
- subscribe the archive user to the list
ezmlm-sub ~alias/ITFORUM [EMAIL PROTECTED]
- make the appropriate mods to your web server so that the archive
page can be seen. Eg for apache I have this in srm.conf
Alias /archives/mail /var/local/mail-archives
Alias /archives/mail/ /var/local/mail-archives/
and in /var/local/mail-archives/index.html I have
<li> IT Forum Discussions
<ul>
<li> <a href="itforum/threads.html">Threaded</a>
<li> <a href="itforum/maillist.html">By Date</a>
</ul>
I'm sure other web based archive systems could be treated in the same
manner.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
Hi,
when I see in my qmail logfile the line:
933356713.693024 info msg 298536: bytes 1566 from <[EMAIL PROTECTED]> qp 3602
uid 1008
933356713.821501 starting delivery 95162: msg 298536 to local
[EMAIL PROTECTED]
933356713.821579 status: local 1/120 remote 0/120
933356713.945498 delivery 95162: success: did_1+0+0/
933356713.968847 status: local 0/120 remote 0/120
933356713.969326 end msg 298536
Does this mean the mail has been succesfully inserted into the users
maildir, or has been handed to another program that does the real delivery?
In other words, does this give me 100% absolute certainty that the user has
this mail in his maildir?
Franky
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > What does "file /var/qmail/bin/qmail-queue" say? What happens if you run
> > qmail-queue as a normal user with no parameters or input? (Be careful,
> > you might have a hard time killing it off.)
>
> Boy, you were right on that one ;-) Ok, when I ran qq as root, it said
> nothing.
> I guess it just started running until I telneted in on another session
> and killed
> it. If I ran it as admin (default login) it told me:
>
> bash: ./qmail-queue: Operation not permitted
> -rws--x--x 1 qmailq qmail 22136 Jul 20 15:00 qmail-queue
> It is the *only* file in the /var/qmail/bin directory that has those
> owners/permissions. The other are all root/qmail and either 755, 711 or
> 700 To me that seems kind of strange. I would think that they should be
> owned by one of the qmail users or the qmail group.
What system (with what patches) are you running? I would think
that it doesn't allow SUID binaries in world writable directories.
BTW, paranoid as I am, I would consider everything inside
/var/qmail/bin compromised, delete it and reinstall. Only if you're
sure that noone has logged onto your computer...
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBN6V2XVMwP8g7qbw/EQIGWwCfehNj0G25o9097AsnrEiZVoix3B4An3DG
YFCiXGbUzxbCGXwgxFtFrTsy
=laEV
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
