qmail Digest 20 Jun 1999 10:00:01 -0000 Issue 677
Topics (messages 26898 through 26934):
Qmail's queue directory & Linux
26898 by: "Peter van der Landen" <[EMAIL PROTECTED]>
26902 by: Petri Kaukasoina <[EMAIL PROTECTED]>
Newbie Question - Please Read!
26899 by: "Alex Miller" <[EMAIL PROTECTED]>
26901 by: Chris Johnson <[EMAIL PROTECTED]>
26906 by: "Alex Miller" <[EMAIL PROTECTED]>
26909 by: "Robin Bowes" <[EMAIL PROTECTED]>
Pine, Mutt, and Maildir
26900 by: "Alex Miller" <[EMAIL PROTECTED]>
26904 by: [EMAIL PROTECTED]
26910 by: "Adam D. McKenna" <[EMAIL PROTECTED]>
26911 by: Scott Schwartz <[EMAIL PROTECTED]>
26913 by: "Adam D. McKenna" <[EMAIL PROTECTED]>
26914 by: [EMAIL PROTECTED]
26917 by: Scott Schwartz <[EMAIL PROTECTED]>
Imap
26903 by: Chris Bond <[EMAIL PROTECTED]>
26912 by: Russ Steffen <[EMAIL PROTECTED]>
qmail/dns resolution
26905 by: Adam Rothschild <[EMAIL PROTECTED]>
26907 by: Mikko Hyvarinen <[EMAIL PROTECTED]>
26908 by: Adam Rothschild <[EMAIL PROTECTED]>
The Maildir format
26915 by: [EMAIL PROTECTED]
26919 by: Russ Steffen <[EMAIL PROTECTED]>
Killing qmail - is it safe?
26916 by: [EMAIL PROTECTED]
Quota proposal.
26918 by: "Sam" <[EMAIL PROTECTED]>
26922 by: Aaron Nabil <[EMAIL PROTECTED]>
qmail problem
26920 by: "Radu Malica" <[EMAIL PROTECTED]>
26921 by: "Alex Miller" <[EMAIL PROTECTED]>
26927 by: Russ Allbery <[EMAIL PROTECTED]>
Web Based E-Mail
26923 by: Gentry L. Williams <[EMAIL PROTECTED]>
26924 by: Robbie Walker <[EMAIL PROTECTED]>
26925 by: "Alex Miller" <[EMAIL PROTECTED]>
26926 by: Chris Bond <[EMAIL PROTECTED]>
SAMBA and Memphis RPM
26928 by: "Alex Miller" <[EMAIL PROTECTED]>
ANNOUNCE: imap-maildir
26929 by: "David Harris" <[EMAIL PROTECTED]>
26932 by: "Alex Miller" <[EMAIL PROTECTED]>
imap with single-uid setup? (was: ANNOUNCE: imap-maildir)
26930 by: Michael Legart <[EMAIL PROTECTED]>
26931 by: "David Harris" <[EMAIL PROTECTED]>
Memphis RPM Pop3d
26933 by: "Alex Miller" <[EMAIL PROTECTED]>
alias problem
26934 by: Clayton Weaver <[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]
----------------------------------------------------------------------
L.S,
The following section is from the Installing & Configuring page of the Cyrus
IMAP server:
>8.LINUX SYSTEMS ONLY: Set the configuration, user, quota, and partition
>directories to update synchronously.
> Failure to do this may lead to data corruption and/or loss of mail
>after a system crash.
>
> cd /var/imap
> chattr +S . user quota
> chattr +S /var/spool/imap
>
> Also set the queue directory of the mail daemon to update
>synchronously. The following example is for sendmail:
>
> /sbin/chattr +S /var/spool/mqueue
Should I conclude from this that somehow Linux is extra vulnerable to queue
corruption (there's no such instruction for other OS'es). If so, why doesn't
Dan (who I know as a very careful person) recommend this?
Is it a good idea to apply this +S attribute to the Qmail queue directory?
Would it have a high impact on performance?
Best regards,
Peter van der Landen
On Sat, Jun 19, 1999 at 12:07:11PM +0200, Peter van der Landen wrote:
> > Also set the queue directory of the mail daemon to update
> >synchronously. The following example is for sendmail:
> >
> > /sbin/chattr +S /var/spool/mqueue
>
> Should I conclude from this that somehow Linux is extra vulnerable to queue
> corruption (there's no such instruction for other OS'es). If so, why doesn't
> Dan (who I know as a very careful person) recommend this?
>
> Is it a good idea to apply this +S attribute to the Qmail queue directory?
> Would it have a high impact on performance?
In Linux, in case of power loss you can lose the mail that you received in
the last 30 seconds.
The chattr trick was suggested a year ago on this list. I tried it but it
didn't help at all in case of directories. I guess the attribute only works
for files which are opened, not for directories where files are opened. I
have no idea if something has changed after that.
But there's a little shared library which adds extra fsync() system calls
and which should make qmail on Linux reliable:
ftp://elektroni.ee.tut.fi/pub/qmail_linux_metadata_message
(the included patch for the kernel is not needed any longer)
well, if you have Redhat Linux like I do here has been my experience.
I installed QMail using the tarball, running through each step carefully by
hand, and with help from members on this list, finally got it to work. I
could send mail out (unlike you) but I couldn't recieve remote email. I was
sure that I had done something wrong with the remove sendmail steps since my
system did not have things configured exactly as described in the INSTALL,
and I wasn't that confident in my guesses.
So last night I took down the RPM's (a whole bunch of them, and set the
whole thing up, deleting my qmail install, rpm'ing the src, then rpming the
required preinstall stuff, and finally rpming qmail).
When I rebooted it worked and was very different. There was a whole new
qmail process running when I did ps-aux, there was no /var/qmail/rc file at
all, there was a whole slew of extra .qmail-*** files in my alias folder,
and lo and behold it worked, in particular, I could now send myself mail
from the outside world.
So my feeling is that Redhat systems are sufficiently different from the
norm that their own unique install of QMail is required and the only way to
get that right now, is by using RPM's.
Alex Miller
> -----Original Message-----
> From: gene Campbell [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 19, 1999 1:25 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Newbie Question - Please Read!
>
>
> I just tried this howto. It is the best one yet for helping understand
> this system. But, I still can't get smtp to work. That is if I send from
> another place to my system with qmail, it is bouced back. I get this
>
> ___
> Hi. This is the qmail-send program at mail.surfup.com.
> I'm afraid I wasn't able to deliver your message to the following
> addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> <[EMAIL PROTECTED]>:
> Sorry. Although I'm listed as a best-preference MX or A for that host,
> it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)
> ---
>
> I feel like I'm getting somewhere with this. But, I have no idea how I'm
> going to get POP mail working.
>
> - gene
>
>
> At 1:06 AM -0400 6/19/99, Dale Miracle wrote:
> >> Kevin King wrote:
> >>
> >> I recently got my RH Linux box working wtith Qmail (with a huge amount
> >> of help from Dave Sill). When I installed Qmail setup the following
> >> files as such:
> >>
> >
> >I found this web site tonight that might help some people. I am also
> >trying to setup qmail my self because sendmail's virtual mail setup is
> >EVIL..I hate m4 and makemap <shudder>. Any how here is the link
> >http://www.flounder.net/qmail/qmail-howto.html
> >
> >I found it while searching through many howto's and web pages trying to
> >make sense of the hundreds of interpretations of the qmail doc's. I
> >read it all the way through and it sounds pretty good...to bad I found
> >it at 1 am :( I have been staring at this monitor of mine for over 3
> >hours now. I think I am just going to remove what I have and install
> >qmail fresh tomorrow.
> >I hope this help's, I know it made more sense to me...
> > Later,
> >--
> >
> >Dale Miracle
> > System Administrator
> > Teoi Net
>
>
>
>
On Sat, Jun 19, 1999 at 08:04:04AM -0400, Alex Miller wrote:
> well, if you have Redhat Linux like I do here has been my experience.
>
> I installed QMail using the tarball, running through each step carefully by
> hand, and with help from members on this list, finally got it to work. I
> could send mail out (unlike you) but I couldn't recieve remote email. I was
> sure that I had done something wrong with the remove sendmail steps since my
> system did not have things configured exactly as described in the INSTALL,
> and I wasn't that confident in my guesses.
>
> So last night I took down the RPM's (a whole bunch of them, and set the
> whole thing up, deleting my qmail install, rpm'ing the src, then rpming the
> required preinstall stuff, and finally rpming qmail).
>
> When I rebooted it worked and was very different. There was a whole new
> qmail process running when I did ps-aux, there was no /var/qmail/rc file at
> all, there was a whole slew of extra .qmail-*** files in my alias folder,
> and lo and behold it worked, in particular, I could now send myself mail
> from the outside world.
>
> So my feeling is that Redhat systems are sufficiently different from the
> norm that their own unique install of QMail is required and the only way to
> get that right now, is by using RPM's.
Redhat systems are no different from anything else, and there's nothing to
preclude installing qmail from the tarball. I've installed qmail on several
Redhat boxes, always from the tarball. You follow the qmail installation
instructions, remove (or at least disable the script that starts) sendmail, and
start your qmail stuff from some script that runs at bootup, and you're in
business. This is exactly how it's installed on any system.
You do, of course, have to know a little about how things start up at boot time
on a Redhat system, but you'd have to know that about any system.
Chris
I don't think that's entirely accurate. That is, if Redhat (mine is Linux
Mandrake - Redhat + KDE) systems are no different than other systems then
the documentation would be written slightly differently.
For example:
The /var/qmail/doc/INSTALL file says:
16. Set up qmail-smtpd in /etc/inetd.conf (all on one line):
smpt stream tcp nowait qmaild /var/qmail/bin/tcp-env
tcp-env /var/qmail/bin/qmail-smtpd
This is what I did when I installed using the tarball, despite the warning
near the old commented out smtp line claiming that smtp is set in the
sendmail scripts (later steps about that). However I could not recieve mail
and when I ran telnet 127.0.0.1 25 I got a disconnected host.
When I did the RPM install, it works, I can recieve mail, but nowhere in my
/etc/inetd.conf is SMTP configured.
However, in /etc/rc.d/init.d there are several new files which are not
mentioned at all in the tarball INSTALL like qmail-pop3d.init,
qmail-qmpqpd.init, qmail-qmpt.init, qmail-smtpd.init, qmail.init and they
each have pointers in the /etc/rc.d/rc#.d files.
This is just one example of differences (there are quite a few others) that
I noticed from the effect of using the RPM install vs. the tarball RTFM
install. But of course the really important difference for me is that the
RPM install resulted in the successful ability to recieve mail, whereas my
careful tarball installation did not.
Alex Miller
> -----Original Message-----
> From: Chris Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 19, 1999 8:24 AM
> To: Alex Miller
> Cc: gene Campbell; Qmail
> Subject: Re: Newbie Question - Please Read!
>
>
> On Sat, Jun 19, 1999 at 08:04:04AM -0400, Alex Miller wrote:
> > well, if you have Redhat Linux like I do here has been my experience.
> >
> > I installed QMail using the tarball, running through each step
> carefully by
> > hand, and with help from members on this list, finally got it to work. I
> > could send mail out (unlike you) but I couldn't recieve remote
> email. I was
> > sure that I had done something wrong with the remove sendmail
> steps since my
> > system did not have things configured exactly as described in
> the INSTALL,
> > and I wasn't that confident in my guesses.
> >
> > So last night I took down the RPM's (a whole bunch of them, and set the
> > whole thing up, deleting my qmail install, rpm'ing the src,
> then rpming the
> > required preinstall stuff, and finally rpming qmail).
> >
> > When I rebooted it worked and was very different. There was a whole new
> > qmail process running when I did ps-aux, there was no
> /var/qmail/rc file at
> > all, there was a whole slew of extra .qmail-*** files in my
> alias folder,
> > and lo and behold it worked, in particular, I could now send myself mail
> > from the outside world.
> >
> > So my feeling is that Redhat systems are sufficiently different from the
> > norm that their own unique install of QMail is required and the
> only way to
> > get that right now, is by using RPM's.
>
> Redhat systems are no different from anything else, and there's nothing to
> preclude installing qmail from the tarball. I've installed qmail
> on several
> Redhat boxes, always from the tarball. You follow the qmail installation
> instructions, remove (or at least disable the script that starts)
> sendmail, and
> start your qmail stuff from some script that runs at bootup, and you're in
> business. This is exactly how it's installed on any system.
>
> You do, of course, have to know a little about how things start
> up at boot time
> on a Redhat system, but you'd have to know that about any system.
>
> Chris
>
Alex Miller wrote:
>
> When I did the RPM install, it works, I can recieve mail, but nowhere in my
> /etc/inetd.conf is SMTP configured.
Aha. That's because you're using the memphis RPM which controls qmail
from...
>
> However, in /etc/rc.d/init.d there are several new files which are not
> mentioned at all in the tarball INSTALL like qmail-pop3d.init,
> qmail-qmpqpd.init, qmail-qmpt.init, qmail-smtpd.init, qmail.init and they
> each have pointers in the /etc/rc.d/rc#.d files.
...a set of scripts that use djb's daemontools!
> > > So my feeling is that Redhat systems are sufficiently different from the
> > > norm that their own unique install of QMail is required and the only way to
> > > get that right now, is by using RPM's.
> >
> > Redhat systems are no different from anything else, and there's nothing to
> > preclude installing qmail from the tarball. I've installed qmail
> > on several Redhat boxes, always from the tarball. You follow the qmail installation
> > instructions, remove (or at least disable the script that starts)
> > sendmail, and start your qmail stuff from some script that runs at bootup, and
>you're in
> > business. This is exactly how it's installed on any system.
This is exactly *one* way to install on any system. It is the the
*default* installation method.
I think the problem here is one of mis-understanding just what an RPM
distribution is. There is no "official" RPM distribution of qmail.
There are a couple of contributed RPMs which result in a qmail
installation that is setup and configured according to the personal
preferences of the RPM author.
Mate Wierdl (who does the memphis RPM) chooses to not start qmail from
inetd and uses daemontools and a very nice set of rc scripts. I was so
impressed with this approach that I replicated it on our FreeBSd boxes
at work.
So, in summary, there's more than one way to skin a cat; or install a
qmail in this case!
R.
--
Two rules to success in life:
1. Don't tell people everything you know.
-- Sassan Tat
Ok, thanks Scott
but pardon my stupidity, where should I set this, rc.local with a set
command? I have Redhat, and am not clear on setting environment variables. I
know this is the kind of thing I should know but I've been puzzled by
setting environment variables for a while now, all the reference books seem
to assume more experience with environment variables than I have.
I presume that other people who want to use Mutt with Maildir must also need
to do this.
Alex Miller
> -----Original Message-----
> From: Scott Schwartz [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 19, 1999 2:07 AM
> To: Qmail
> Subject: Re: Pine, Mutt, and Maildir
>
>
> "Alex Miller" <[EMAIL PROTECTED]> writes:
> | However, Mutt seems to be looking for the Mailbox, and I can't
> see an option
> | for setting it to use Maildirs.
>
> Set $MAIL to point to your maildir.
>
> But... is it my imagination or does mutt read the whole maildir, and
> then write it back? That's just awful to contemplate. One of the big
> advantages of maildir (and mh) is that you don't have to write the
> whole thing back just to update a few messages.
>
>
Recently, Alex Miller had the following to say about RE: Pine, Mutt, and Maildir:
> Ok, thanks Scott
>
> but pardon my stupidity, where should I set this, rc.local with a set
> command? I have Redhat, and am not clear on setting environment variables. I
> know this is the kind of thing I should know but I've been puzzled by
> setting environment variables for a while now, all the reference books seem
> to assume more experience with environment variables than I have.
>
Here's what I use in my .muttrc file to use Maildirs:
set mbox_type="Maildir"
set mbox="$HOME/Maildir/"
set spoolfile="$HOME/Maildir/"
This does the trick for me. This .muttrc file is in my $HOME
directory. To make it system wide, you'd need to put it in your Muttrc file,
the system-wide mutt configuration file which, on my system, is located in
my /etc directory. However, I have never done this system-wide. I have only
done it for myself as almost all my shell users use Pine, not Mutt.
Hope that helps,
Fred
--
Fred B. Ringel -- Rivertown.Net Internet Access
Systems Administrator -- http://www.rivertown.net
and General Fixer Upper -- Voice/Fax/Support: +1.914.478.2885
E-mail: [EMAIL PROTECTED] for current my public key
Wasn't there something about a PASCAL programmer knowing the value of
everything and the Wirth of nothing?
I used mutt with a large (>1500 message) mailbox file once and the performance
was way worse than with large maildirs.
--Adam
----- Original Message -----
From: Scott Schwartz <[EMAIL PROTECTED]>
To: Qmail <[EMAIL PROTECTED]>
Sent: Saturday, June 19, 1999 2:06 AM
Subject: Re: Pine, Mutt, and Maildir
: "Alex Miller" <[EMAIL PROTECTED]> writes:
: | However, Mutt seems to be looking for the Mailbox, and I can't see an
option
: | for setting it to use Maildirs.
:
: Set $MAIL to point to your maildir.
:
: But... is it my imagination or does mutt read the whole maildir, and
: then write it back? That's just awful to contemplate. One of the big
: advantages of maildir (and mh) is that you don't have to write the
: whole thing back just to update a few messages.
:
:
"Adam D. McKenna" <[EMAIL PROTECTED]> writes:
| I used mutt with a large (>1500 message) mailbox file once and the performance
| was way worse than with large maildirs.
So mutt has two problems, then. Neither bsd mail nor mh has difficulty
with much bigger inboxes.
Maybe, but I wouldn't really compare mutt to either of those.. Those are both
low-feature command line mail readers no?
mutt is still faster than pine for mbox.. and it handles maildir format
(much) faster than mbox.
--Adam
----- Original Message -----
From: Scott Schwartz <[EMAIL PROTECTED]>
To: Qmail <[EMAIL PROTECTED]>
Sent: Saturday, June 19, 1999 2:07 PM
Subject: Re: Pine, Mutt, and Maildir
: "Adam D. McKenna" <[EMAIL PROTECTED]> writes:
: | I used mutt with a large (>1500 message) mailbox file once and the
performance
: | was way worse than with large maildirs.
:
: So mutt has two problems, then. Neither bsd mail nor mh has difficulty
: with much bigger inboxes.
:
:
<<< multipart/signed; boundary=STPqjqpCrtky8aYs; micalg=pgp-md5;protocol="application/pgp-signature": Unrecognized >>>
"Adam D. McKenna" <[EMAIL PROTECTED]> writes:
| Maybe, but I wouldn't really compare mutt to either of those.. Those are both
| low-feature command line mail readers no?
They're high-feature command line readers with high-feature GUI
wrappers available.
Hi,
I've been trying to implement a web based email system using imp. To do this
imap is required, I'm currenting using 4.6BETA (4.5 does the same tho) with the
maildir patches in the contributed area.
There seems to be serveral bugs (or features!) that seem to break certain parts
of imp, the first is that it never seems to be able to get the status correctly
for new mails, etc. The second i've noticed is that Create new folders, it
does not create ~user/dir with all its subdirectories! Has anybody made a
patch that fixes this or has plans to?
It would be really great to see qmail-imap by Dan & Co as part of qmail 1.04,
is they any plans for this?
Regards,
Chris
--
--==== Chris Bond ====--
[EMAIL PROTECTED]
--================--
On 19 Jun 1999, Chris Bond wrote:
> Hi,
>
> I've been trying to implement a web based email system using imp. To do this
> imap is required, I'm currenting using 4.6BETA (4.5 does the same tho) with the
> maildir patches in the contributed area.
I have done exactly this. Well, almost exactly. We are using IMAP 4.5, but
the only patch I have applied is an "INBOX is $HOME/Mailbox" tweak. As
this implies, we are using mbox, not Maildir format. As it stands now,
there is no imap server that supports maildirs well enough to use in a
production environment now.
> There seems to be serveral bugs (or features!) that seem to break certain parts
> of imp, the first is that it never seems to be able to get the status correctly
> for new mails, etc. The second i've noticed is that Create new folders, it
> does not create ~user/dir with all its subdirectories! Has anybody made a
> patch that fixes this or has plans to?
First of all, make sure you have the latest version of imp (2.0.7,
released 6/14/99), as that version specifically fixed problems getting and
setting IMAP status flags.
The other problem you are seeing is a result of the imap-maildir patch
being far from complete. It has several known issues including :
-- new maildir folders are deformed
-- can't copy between maildirs and mbox format folders
The only two alternatives that I saw were to abandon maildirs or use
something like Cyrus imap. I chose to abandon maildirs, as that made it
pretty easy to migrate to maildirs at some later date if a better imap
server shows up.
> It would be really great to see qmail-imap by Dan & Co as part of qmail 1.04,
> is they any plans for this?
We can only hope so.
> Regards,
> Chris
> --
> --==== Chris Bond ====--
> [EMAIL PROTECTED]
> --================--
>
Russ
--
Russ Steffen
[EMAIL PROTECTED]
Lame question time...
qmail stopped delivering outbound mail, and is echoing error messages like
this:
Jun 19 09:26:08 fromagerie qmail: 929798768.674689 delivery 1307:
deferral: Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/
However, all the nameservers defined in resolv.conf on this box *are* able
to resolve this properly. Any advice/insight would be greatly
appreciated.
Thanks,
-a
Adam Rothschild wrote:
>
> Lame question time...
>
> qmail stopped delivering outbound mail, and is echoing error messages like
> this:
>
> Jun 19 09:26:08 fromagerie qmail: 929798768.674689 delivery 1307:
> deferral: Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/
>
> However, all the nameservers defined in resolv.conf on this box *are* able
> to resolve this properly. Any advice/insight would be greatly
> appreciated.
chmod o+r /etc/resolv.conf maybe?
-Mikko Hyv�rinen
On Sat, Jun 19, 1999 at 03:02:46PM +0000, Mikko Hyvarinen wrote:
> chmod o+r /etc/resolv.conf maybe?
Already done.
-a
<<< multipart/signed; boundary=GV0iVqYguTV4Q9ER; micalg=pgp-md5;protocol="application/pgp-signature": Unrecognized >>>
On Sat, 19 Jun 1999 [EMAIL PROTECTED] wrote:
> Hello,
>
> where can I read up on the specifics on the Maildir format? That is, an
> actual specification suitable if you want to programatically manipulate
> Maildirs.
Try 'man maildir' on a qmail-installed system.
--
Russ Steffen
[EMAIL PROTECTED]
<<< multipart/signed; boundary=IbVRjBtIbJdbeK1C; micalg=pgp-md5;protocol="application/pgp-signature": Unrecognized >>>
For some time I've been racking my brains about various ways to implement
Maildir quotas in situations where you cannot use filesystem-based quotas
-- such as when you use a virtual domain manager where all Maildirs have
the same uid/gid.
Before I waste any more time on this, I'm going to wait for a while and
give people a chance to poke holes in what I've came up with.
Here's what I'm thinking: http://www.concentric.net/~mrsam/maildirpp.html
It's a bit rough, needs to be rewritten in a more formal way, and cleaned
up a bit.
QMAIL-LDAP has native quota support that works very well, it could
easily be stripped out and used stand-alone.
Sam writes...
>For some time I've been racking my brains about various ways to implement
>Maildir quotas in situations where you cannot use filesystem-based quotas
>-- such as when you use a virtual domain manager where all Maildirs have
>the same uid/gid.
>
>Before I waste any more time on this, I'm going to wait for a while and
>give people a chance to poke holes in what I've came up with.
>
>Here's what I'm thinking: http://www.concentric.net/~mrsam/maildirpp.html
>
>It's a bit rough, needs to be rewritten in a more formal way, and cleaned
>up a bit.
--
Aaron Nabil
I' ve installed RedHat 6 and Qmail. I followed strictly the
instructions there and i have some problems with ~alias/ directory permissions
and .qmail files in there. Some files in bin/ were installed with root owner. Is
this okay? I can't manage to do a thing with the ~alias directory. i wanted that
user news' mail to be forwarded to joker on local machine, i created
~alias/.qmail-news and wrote in that file 'joker'. Nothing happens. I get some
errors like : Could not chdir Maildir. cannot write to /var/qmail/alias
permission denied
Please help me
The
user you want to be to set up the qmail files is alias
Assuming you have created an alias user (and all the other required qmail
users)
su
alias
cd alias
touch .qmail-postmaster
touch .qmail-mailer-daemon
touch .qmail-root
If you
decide to use Maildirs eventually each of those .qmail files must contain the
line ./Maildir/ and you must have created the Maildir directory using the
maildirmake executable that is in /var/qmail/bin
Ironically, I have installed using the RPM and I cannot perform the
command su alias because the alias user has no shell specified, I don't know why
it was set that way.
Alex
Miller
I' ve installed RedHat 6 and Qmail. I followed strictly
the instructions there and i have some problems with ~alias/ directory
permissions and .qmail files in there. Some files in bin/ were installed
with root owner. Is this okay? I can't manage to do a thing with the ~alias
directory. i wanted that user news' mail to be forwarded to joker on local
machine, i created ~alias/.qmail-news and wrote in that file 'joker'.
Nothing happens. I get some errors like : Could not chdir Maildir. cannot
write to /var/qmail/alias permission denied
Please help me
Alex Miller <[EMAIL PROTECTED]> writes:
> Assuming you have created an alias user (and all the other required
> qmail users)
> su alias
> cd alias
> touch .qmail-postmaster
> touch .qmail-mailer-daemon
> touch .qmail-root
It works just fine to have root own the files in ~alias.
> Ironically, I have installed using the RPM and I cannot perform the
> command su alias because the alias user has no shell specified, I don't
> know why it was set that way.
Because alias is a special user and probably shouldn't own any files or
have a valid shell. There's no reason for it to.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
I am looking for suggestion on an open-source Web based e-mail system.
TIA
-Gentry-
GarfNet Internet Service Provider
Check out SQwebmail. It's working great for us.
http://www.inter7.com/sqwebmail/
At 05:37 PM 6/19/99 , you wrote:
>I am looking for suggestion on an open-source Web based e-mail system.
>
>TIA
>-Gentry-
>GarfNet Internet Service Provider
Robbie Walker
===============================
Denial-Of-Service Attacks will
never go out of style...
"Computer, compute to the last
digit the value of pi"
-- Spock (Wolf in the Fold)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.5.2
iQA/AwUBN2wanzrJV5JQYcnnEQLj1gCgwlvClUp0MVAPDiXqSXHY7c0l+ZMAn3Rd
mzy7FbHkSmhpSTSKNg07wsMu
=vX+e
-----END PGP SIGNATURE-----
If you want a serious web-based solution to anything, start with the robust.
Go to www.php.net
PHP is a server-side scripting language that, among many other things, can
talk to a wide variety of databases. Unlike iHTML, or Allaire's Cold Fusion,
or ASP, it is open-source, and I would say far superior.
Currently, I use w-agora for user forums and it is very very good. At my
work I use Cold Fusion all the time and I think PHP is much much better.
There are many open source projects listed on www.php.net including a few
web-based email systems that use IMAP since PHP has IMAP functions built-in.
So, by setting up PHP, IMAP, and one of those open source projects you will
be standing on solid ground as you try to make improvements and enhance it
for the rest of us (of course you will).
One snag you might run into. There has been a lot of talk back and forth
about how well IMAP works with Maildirs so that could be a snag.
Alex Miller
> -----Original Message-----
> From: Gentry L. Williams [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 19, 1999 5:37 PM
> To: [EMAIL PROTECTED]
> Subject: Web Based E-Mail
>
>
> I am looking for suggestion on an open-source Web based e-mail system.
>
> TIA
> -Gentry-
> GarfNet Internet Service Provider
>
IMP is wrote completely with PHP, but can use mysql and other databases as a
backend for perferences and contact lists.
Chris
Quoting Alex Miller <[EMAIL PROTECTED]>:
> If you want a serious web-based solution to anything, start with the
> robust.
> Go to www.php.net
>
> PHP is a server-side scripting language that, among many other things, can
> talk to a wide variety of databases. Unlike iHTML, or Allaire's Cold
> Fusion,
> or ASP, it is open-source, and I would say far superior.
>
> Currently, I use w-agora for user forums and it is very very good. At my
> work I use Cold Fusion all the time and I think PHP is much much better.
>
> There are many open source projects listed on www.php.net including a few
> web-based email systems that use IMAP since PHP has IMAP functions
> built-in.
>
> So, by setting up PHP, IMAP, and one of those open source projects you will
> be standing on solid ground as you try to make improvements and enhance it
> for the rest of us (of course you will).
>
> One snag you might run into. There has been a lot of talk back and forth
> about how well IMAP works with Maildirs so that could be a snag.
>
> Alex Miller
>
> > -----Original Message-----
> > From: Gentry L. Williams [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, June 19, 1999 5:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: Web Based E-Mail
> >
> >
> > I am looking for suggestion on an open-source Web based e-mail system.
> >
> > TIA
> > -Gentry-
> > GarfNet Internet Service Provider
> >
>
>
--
--==== Chris Bond ====--
[EMAIL PROTECTED]
--================--
I think I may have figured out why I couldn't get QMAIL to work fromt the
tarball but I could make it work with the Memphis RPM.
I was using Samba. Any windows user on my network (just 2 machines) that has
the same username and password as their user account on my LINUX machine
could access their files.
Now that I have installed the Memphis RPM of QMail I no longer can access
Linux files from Windows.
But with the tarball, I could not run telnet 127.0.0.1 25 without a
disconnect.
So I think that the TCP/IP handling that SAMBA was doing prevented QMail
from accepting mail but that the new ucsp-tcpi rpm from the Memphis RPM is
allowing QMail to work but not Samba.
Alex Miller
ANNOUNCE: imap-maildir
imap-maildir: production quality UW-imap server Maildir support
http://www.davideous.com/imap-maildir/
Quick Summary:
The University of Wisconsin IMAP server by Mark Crispin, one of the most
popular IMAP servers, does not have built-in Maildir support. There is a
patch which adds in a Maildir driver, but it falls short of a workable
solution in a few ways. This page details a few patches which clean up a few
issues and make the UW-IMAP server fully workable with Maildirs and qmail.
This gets around the problem (to my satisfaction) in the maildir driver
where you can't copy between maildir folders and non-maildir folders. The
solution is to make users which have a maildir INBOX only use maildir
folders: new folders are created as maildirs and only maildir folders are
returned by the IMAP LIST command.
Included on the web page are all the patches to build your own, or an RPM
file for RedHat-based Linux users.
- David Harris
Principal Engineer, DRH Internet Services
Gee David,
an imap-maildir solution? are you sure people really want one, he he he, ha
ha ha.
Just kidding.
Thank you David :-)
> -----Original Message-----
> From: David Harris [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, June 19, 1999 9:27 PM
> To: Qmail
> Subject: ANNOUNCE: imap-maildir
>
>
>
> ANNOUNCE: imap-maildir
>
> imap-maildir: production quality UW-imap server Maildir support
>
> http://www.davideous.com/imap-maildir/
>
> Quick Summary:
>
> The University of Wisconsin IMAP server by Mark Crispin, one of the most
> popular IMAP servers, does not have built-in Maildir support. There is a
> patch which adds in a Maildir driver, but it falls short of a workable
> solution in a few ways. This page details a few patches which
> clean up a few
> issues and make the UW-IMAP server fully workable with Maildirs and qmail.
>
> This gets around the problem (to my satisfaction) in the maildir driver
> where you can't copy between maildir folders and non-maildir folders. The
> solution is to make users which have a maildir INBOX only use maildir
> folders: new folders are created as maildirs and only maildir folders are
> returned by the IMAP LIST command.
>
> Included on the web page are all the patches to build your own, or an RPM
> file for RedHat-based Linux users.
>
> - David Harris
> Principal Engineer, DRH Internet Services
>
>
>
Hi!
>>>>> "David" == David Harris <[EMAIL PROTECTED]> writes:
David> up a few issues and make the UW-IMAP server fully workable
David> with Maildirs and qmail.
Would it be possible to imap with a single-uid pop3 setup? We would
like to use IMP on a mailserver running this setup, but I can't figure
out if it is possible?
--
michael legart, [EMAIL PROTECTED]
sysadmin, http://wiktor.dk
public gnupg/pgp keys at http://wiktor.dk/~badpixel/pgp/
Yes, it's possible. But it's not very simple as the IMAP server was not
setup to have a new authentication method just plug in cleanly like the
qmail-pop3d setup. You also have to deal with the fact that the IMAP server
is happy to allow the user to open folders not in their home directory, but
relies on the UNIX uid permissions.
If you don't mind mucking around in the source code, then go for it. The
file you wan to start in is "src/osdep/unix/env_unix.c". It's about a
thousand lines and from my understanding of the code, you should be able to
do all the modifications in just that file.
My partner and I are developing an in-house solution to allow each virtual
domain user to setup virtual POP/IMAP accounts under one uid, but that is
going to be proprietary. Developing it was how I ended up doing the Maildir
patch.
- David Harris
Principal Engineer, DRH Internet Services
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Michael Legart
Sent: Saturday, June 19, 1999 9:41 PM
To: Qmail
Subject: imap with single-uid setup? (was: ANNOUNCE: imap-maildir)
Hi!
>>>>> "David" == David Harris <[EMAIL PROTECTED]> writes:
David> up a few issues and make the UW-IMAP server fully workable
David> with Maildirs and qmail.
Would it be possible to imap with a single-uid pop3 setup? We would
like to use IMP on a mailserver running this setup, but I can't figure
out if it is possible?
--
michael legart, [EMAIL PROTECTED]
sysadmin, http://wiktor.dk
public gnupg/pgp keys at http://wiktor.dk/~badpixel/pgp/
I've installed the Memphis RPM. I didn't even know that at first. I just
took thought it was the RPM listed at the top of www.qmail.org.
Well, looking at the file Installing Qmail on Redhat Linux at
http://qmail-docs.surfdirect.com.au/docs/redhat.html
it says the following.
/etc/rc.d/init.d/qmail-qmail-pop3d.init is provided to manage a POP daemon.
However, this is untested and needs to modified in order to work.
Ok, that's true, it doesn't work. Does anyone know what modifcations he is
referring to? Should I remove the qmil-pop3d.init file and start pop-3
myself in my qmail startup script?
Also, should it work like this?
I have a user account alex with a password.
If I specify my hostname (what is returned when I execute hostname),
username, and password in a normal pop account, I should be able to connect
and read my mail, right?
Alex Miller
qmail-1.0.1
linux-2.0.36
libc-5.4.33
gcc-2.7.2.1
binutils-2.8.1.0.18
I have .qmail-aliasname alias files in ~/alias. user alias has an
account, a home dir with the alias files in it, etc.
.qmail-postmaster, for example, has
&real_user@local_domain
.qmail-news, for another example, is exactly the same (same user, same
domain, same permissions, same separator character). Likewise for
.qmail-webmaster, .qmail-operator, blah, blah.
Dir permissions for ~alias are 0700, .qmail-aliasname files are 0644.
The odd thing is that mail to postmaster@local_domain is redirected
to the real_user mentioned in ~alias/.qmail-postmaster, but mail
to news@local_domain, operator@local_domain, webmaster@local_domain,
and apparently all of the rest of them bounce, despite having the
same redirect in those other .qmail-aliasname files.
My only guess is that it isn't looking there first for the redirect,
it's looking in /etc/aliases.cdb. The qmail-start line that starts
the daemon is
/path/to/qmail/bin/qmail-start '|fastforward -d /etc/aliases.cdb' \
/path/to/cyclog /var/log/mail &
(that's exactly how it reads, in /etc/rc.inet2).
/etc/aliases has lines like
mailer-daemon: real_user
MAILER-DAEMON: real_user
Mailer-Daemon: real_user
postmaster: real_user
operator: real_user
webmaster: real_user
and so on.
So if it can find postmaster's redirect, whether it's using
~/alias/.qmail-postmaster or fastforward and /etc/aliases.cdb,
why can't it find webmaster's redirect (or news or operator or
any of the other half-dozen that I just tried). These aren't
real accounts, ie there is no user account on the machine called webmaster
for example, although that doesn't seem to make a difference.
(I noticed the problem when I started getting bounce messages
from root cron jobs, meaning it was failing to redirect root@local_domain
from cron to real_user@local_domain. This used to work. I put up
with no root mail for awhile, using qmsmac, then made a
~alias/.qmail-root file with &real_user@local_domain, messed around
with the directory permissions a little, and voila', mail to root got
redirected, and my mailbox stopped filling up with bounce messages from
cron. For a reason that is not apparent, it has reverted to previous
behavior.)
If none of the aliases got redirected, that would be reasonable, there
is something objectionable about the directory or file permissions
probably. But to have one alias get through and none of the others that
only differ in username without differing in how mail to that username
is handled in the config files is bizarre. postmaster is not the first
alias in aliases.cdb, it's like 3rd or 4th or something (ie fastforward is
not reading the first entry and failing to find any others).
Regards,
Clayton Weaver
<mailto:[EMAIL PROTECTED]>
(Seattle)
"Everybody's ignorant, just in different subjects." Will Rogers
