qmail Digest 25 Sep 2000 10:00:01 -0000 Issue 1134
Topics (messages 49328 through 49357):
Transforming a FROM address..
49328 by: Petricevich, Paul
49329 by: Peter van Dijk
Re: dotqmail scripting
49330 by: Magnus Bodin
49337 by: Raul Miller
Question about tcpserver!
49331 by: Mark Lo
49333 by: Johan Almqvist
qmail-mrtg - HOWTO?
49332 by: Robin S. Socha
Re: No Transport Provider Available
49334 by: Mark Walsh
SMTP stopping
49335 by: Bob Ross
49338 by: Chris Johnson
49340 by: Bob Ross
49348 by: Chris Johnson
tcpserver error
49336 by: Mark Lo
49339 by: Mark Lo
49350 by: Magnus Bodin
Re: comparison vmailmgr - inter7
49341 by: Sean Reifschneider
49342 by: Olivier M.
49345 by: Dale Miracle
qmail-scanner + which antivirus ?
49343 by: Olivier M.
49357 by: Martin Lesser
Re: spooled messages take too long to send
49344 by: Doug Balmer
Re: qmails queue and disk io
49346 by: John White
49347 by: John White
qmail + Majordomo???
49349 by: Ramzi S. Abdallah
49352 by: Robin S. Socha
49355 by: Scott D. Yelich
Using Mailman with Plesk and qmail
49351 by: Phil Barnett
Postfix: This release introduces DSN style notification of bounced or delayed mail, as
per RFC 1894.
49353 by: Olivier M.
49354 by: Adam McKenna
Re: mini-qmail
49356 by: oliver.koch.jk.uni-linz.ac.at
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
I've just spent the last day installing, configuring and generally trying to
come to grips with how qmail functions
I have qmail server setup to receive and then relay mail on from an internal
(exchange) mail server. Unfortunately a lot of our exchange users been set
up with user@<exchangehost>.domain.com as their reply-to address. Before
qmail attempts to send off these emails I want it to strip the
<exchangehost> part out of the from/reply-to (?) address, so the receipient
will only see the message as having come from [EMAIL PROTECTED] How would I
go about achieving this?
Thanks, and apologies if the answer is freakin obvious. I'm a newbie to
unix MTAs!
Paul.
Visit our new website www.acnielsen.co.nz for free ACNielsen market insights.
CAUTION - This message may contain privileged and confidential information intended
only for the use of the addressee(s) named above. If you are not the intended
recipient of this message you are hereby notified that any use, dissemination,
distribution or reproduction of this message is prohibited. If you have received this
message in error please notify ACNielsen (NZ) Ltd. immediately via email at
[EMAIL PROTECTED] Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of ACNielsen (NZ) Ltd.
On Sun, Sep 24, 2000 at 11:35:00PM +1200, Petricevich, Paul wrote:
> I've just spent the last day installing, configuring and generally trying to
> come to grips with how qmail functions
>
> I have qmail server setup to receive and then relay mail on from an internal
> (exchange) mail server. Unfortunately a lot of our exchange users been set
> up with user@<exchangehost>.domain.com as their reply-to address. Before
> qmail attempts to send off these emails I want it to strip the
> <exchangehost> part out of the from/reply-to (?) address, so the receipient
> will only see the message as having come from [EMAIL PROTECTED] How would I
> go about achieving this?
Since I gotta catch a train I'll be short: read part 5.5 of
/usr/src/qmail-1.03/FAQ. Replace the .qmail-fixup-default part with
something that fixes the header (perhaps some formail magic [formail is
part of the procmail package]).
Perhaps ofmipd from mess822 can be of use, but I've never looked at
that.
Greetz, Peter
--
dataloss networks
'/ignore-ance is bliss' - me
On Sat, Sep 23, 2000 at 06:44:37PM -0700, Eric Cox wrote:
>
>
> Peter Samuel wrote:
> >
> > On Thu, 21 Sep 2000, Eric Cox wrote:
> > >
> > > Mail is delivered to [EMAIL PROTECTED]
> > >
> > > ~alias/.qmail-user1 contains:
> > >
> > > |script that writes a username into ~alias/.qmail-user2
> > > &user2
> >
> > It would work but it's a woefully inefficient way to do it. Especially
> > as qmail comes with a mechanism to do just this - /var/qmail/bin/forward.
> >
> > ~alias/.qmail-user1 contains:
> >
> > | forward `some_script_that_generates_new_addess(es)`
> >
> > See the man page.
>
> The man page says that forward is a wrapper around qmail-queue.
> Doesn't that mean the message makes two complete trips into and
> out of the queue, while the method I described is handled
> completely within qmail-local?
>
> Granted I haven't looked at the source yet, but what have I
> missed?
You haven't missed anything. It could be faster.
And the order does not matter as all forwards are done last.
/magnus
On Thu, 21 Sep 2000, Eric Cox wrote:
> > > |script that writes a username into ~alias/.qmail-user2
> > > &user2
Peter Samuel wrote:
> > | forward `some_script_that_generates_new_addess(es)`
> > See the man page.
On Sat, Sep 23, 2000 at 06:44:37PM -0700, Eric Cox wrote:
> The man page says that forward is a wrapper around qmail-queue.
> Doesn't that mean the message makes two complete trips into and out of
> the queue, while the method I described is handled completely within
> qmail-local?
Your script has a race condition -- if two messages are being handled
simultaneously, and going to different users, what happens?
Also, the cost of putting a message in the queue is small compared to
the cost of running a shell script. By the time you deal with your race
condition, you've probably lost any "efficiency" gains.
Finally, your script should have read &myusername-user2, for the second
line.
--
Raul
|
Hi,
I would like to know what is
tcpserver 0 means ?
tcpserver 0 ---> what is 0 means in tcpserver, i
have gone throught all the documentations, but can't figure out what is 0
mean. Please help.
Thanks
Mark
|
On Sun, Sep 24, 2000 at 11:27:01PM +0800, Mark Lo wrote:
> Hi,
> I would like to know what is tcpserver 0 means ?
That depends on where you see that 0.
0 for port means use any free port
0 for address means bind to all addresses
0 elsewhere means other stuff (but I presume it was one of the above
you were looking for...)
-Johan
--
Johan Almqvist
Greetings,
I've searched the mail archive but didn't come up with something solving
my problem. Maybe this question would be better addressed on the
daemontools list. Anyway...
qmail-mrtg-0.1 assumes cyclog (which obviously was replaced by multilog)
and I don't have /var/log/qmail/send or something similar.
qmail-mrtg.1.0 gives me:
/usr/local/mrtg-2/bin/mrtg qmail.mrtg.cfg
) in CFG file (qmail.mrtg.cfg) does not make sense
I cannot claim to be an mrtg expert (au contraire, I don't understand it
at all), but I've nuked all ")" in this file for good measure and that
does not change anything, either.
Does anyone have a working setup and would share it, please?
Thanks in advance,
Robin (slightly unnerved now... ;-))
--
Robin S. Socha <http://socha.net/>
I am using Linux solely as a firewall and Mail server. Using QMAIL as the
sole mail server in the office. No NT or exchange server. We have an
AS/400 that is used solely within the company for order processing. That is
the only other server. All my clients are using the Outlook that came with
Office Pro 97. And the Internet Mail is the transport that is loaded.
When someone sends a mail, it immediately returns with no transport
available. I don't even see an error listed in the QMail or system logs.
-----Original Message-----
From: Charlie & [mailto:[EMAIL PROTECTED]]
Sent: Sunday, September 24, 2000 1:46 PM
To: Mark Walsh
Subject: Re: No Transport Provider Available
Are you using qmail solely for mail or does it sit in front of an Exchange
server ? What version of Outlook ? What mail transport do you have loaded
in the individual MAPI profiles ?
Alan
On Fri, Sep 22, 2000 at 05:55:14PM -0300, Mark Walsh wrote:
> I had someone put in a Linux Firewall with QMail as the Mail server.
> Lately, I had lost their support and I am at a bit of a loss. The
> problem that I have is that most of my company is on Microsoft
> Outlook. Most or all of the employees are experiencing difficulties
> in sending EMail. They attempt to send email, either locally or
> remotely and get the message
>
> There is No Transport Provider Available.
>
> Sometimes I can send mail, sometimes I can't. I had removed The
> Personal folders and accounts from individual computers and for a
> time it seemed to repair it. But now everyone is doing it? I
> starting to wonder if it is actually the QMAil. Where Do I start
> looking there?
>
> Mark Walsh
I have several domains that our users can use. Since I have added 18 more
they are down more than they are up.
For no reason, the mail just does not return or show up. Then after
restarting qmail-send a bunch of times it still does not work. Then all of a
sudden it will start working again.
Register4Less tells me it's my UPStream provider, MY upstream provider tells
me my SMTP is stopping.
I have TCP server set up with qmail.
The object is to allow our users to use any one or all of the 18 domain
names for their email.
I have all the domains listed in the following files. Did I find a
limitation to doing this, or am I really missing something.
defaultdomain
locals
me
plusdomain
rcpthosts
Any help with this would be great.
Thanks
Bob Ross
On Sun, Sep 24, 2000 at 11:32:19AM -0700, Bob Ross wrote:
> I have several domains that our users can use. Since I have added 18 more
> they are down more than they are up.
>
> For no reason, the mail just does not return or show up.
Return from where? Show up where? At remote sites? In your users' mailboxes?
> Then after restarting qmail-send a bunch of times it still does not work.
> Then all of a sudden it will start working again.
>
> Register4Less tells me it's my UPStream provider, MY upstream provider tells
> me my SMTP is stopping.
What has your own troubleshooting shown you? What do you see in your logs?
> I have TCP server set up with qmail.
>
> The object is to allow our users to use any one or all of the 18 domain names
> for their email.
>
> I have all the domains listed in the following files. Did I find a limitation
> to doing this, or am I really missing something.
>
> defaultdomain
> locals
> me
> plusdomain
> rcpthosts
Note that the names of two of these files are plural and the others aren't. You
shouldn't have more than one domain listed in the non-plural ones. See the man
pages for the roles these files play, rather than guessing.
What are the names of some of these domains?
Chris
Cris,
They are all local Domains on my server.
My users can use any one of them that they want to use. I had to be put in
all the files listed in order from everyone to be able to use them with out
me having to make many changes on this end.
All mail goes out with out a problem, most of the time it will not come
back. Right now they are all working but in another day or two most of these
will.
bullheadcityaz.net
chlorideaz.com
dolanspringsaz.com
fortmojaveaz.com
goldevvalleyaz.net
goldenvalleyaz.net
hackberryaz.com
lakehavasucityaz.net
meadviewaz.com
mohavecountyaz.net
mohavevalleyaz.net
oatmanaz.net
peachspringsaz.com
templebaraz.com
topockaz.com
truxtonaz.com
valentineaz.com
wikieupaz.com
yucca-az.com
----- Original Message -----
From: "Chris Johnson" <[EMAIL PROTECTED]>
To: "Bob Ross" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, September 24, 2000 12:28 PM
Subject: Re: SMTP stopping
> On Sun, Sep 24, 2000 at 11:32:19AM -0700, Bob Ross wrote:
> > I have several domains that our users can use. Since I have added 18
more
> > they are down more than they are up.
> >
> > For no reason, the mail just does not return or show up.
>
> Return from where? Show up where? At remote sites? In your users'
mailboxes?
>
> > Then after restarting qmail-send a bunch of times it still does not
work.
> > Then all of a sudden it will start working again.
> >
> > Register4Less tells me it's my UPStream provider, MY upstream provider
tells
> > me my SMTP is stopping.
>
> What has your own troubleshooting shown you? What do you see in your logs?
>
> > I have TCP server set up with qmail.
> >
> > The object is to allow our users to use any one or all of the 18 domain
names
> > for their email.
> >
> > I have all the domains listed in the following files. Did I find a
limitation
> > to doing this, or am I really missing something.
> >
> > defaultdomain
> > locals
> > me
> > plusdomain
> > rcpthosts
>
> Note that the names of two of these files are plural and the others
aren't. You
> shouldn't have more than one domain listed in the non-plural ones. See the
man
> pages for the roles these files play, rather than guessing.
>
> What are the names of some of these domains?
>
> Chris
>
On Sun, Sep 24, 2000 at 01:31:50PM -0700, Bob Ross wrote:
> They are all local Domains on my server.
>
> My users can use any one of them that they want to use. I had to be put in
> all the files listed in order from everyone to be able to use them with out
> me having to make many changes on this end.
It's fine for them all to be local domains. My point was that the files me,
plusdomain, and defaultdomain should only contain one entry. I don't think
having multiple entries will cause you any problems, but it's not really right.
> All mail goes out with out a problem, most of the time it will not come
> back. Right now they are all working but in another day or two most of these
> will.
So you think that the problem is with incoming SMTP connections. I just tried
connecting to the mail exchanger for a couple of these domains, and there
didn't seem to be a problem. The intermittent problem you're seeing could be
caused by any number of things: DNS problems and ISP problems (both of which
would probably manifest themselves in other ways too), resource problems on
your host, SMTP concurrency problems, etc. Without further details, it'll be
impossible for anyone to tell.
Chris
|
Hi,
I have just installed qmail with
tcpserver (following life with qmail), in my /var/log/qmail/smtpd/current file,
the errors messages stating that "tcpserver: fatal: unable to bind: address
already used." and this message keeps generating itself until filling up all of
the space. Please help me to point out for the error.
my startup script in
/var/qmail/supervise/qmail-smtpd/run file are as follows:
#!/bin/sh
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -u qmaild`
exec /usr/local/bin/softlimit -m 4000000
\
/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
-u
$QMAILDUID -g $NOFILESGID 0 smtp \
/var/qmail/bin/qmail-smptd 2>&1 > /dev/null &
Thank you so much for your help
Mark
|
|
In additions, I can see two tcpserver is running
under the command of ps-aux
1. tcpserver is running under user
"root"
2. tcpserver is running under user
"qmaild"
Is this the only reason that causes error
??
----- Original Message -----
Sent: Monday, September 25, 2000 3:04
AM
Subject: tcpserver error
Hi,
I have just installed qmail with
tcpserver (following life with qmail), in my /var/log/qmail/smtpd/current
file, the errors messages stating that "tcpserver: fatal: unable to bind:
address already used." and this message keeps generating itself until filling
up all of the space. Please help me to point out for the
error.
my startup script in
/var/qmail/supervise/qmail-smtpd/run file are as follows:
#!/bin/sh
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -u qmaild`
exec /usr/local/bin/softlimit -m 4000000
\
/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
-u
$QMAILDUID -g $NOFILESGID 0 smtp \
/var/qmail/bin/qmail-smptd 2>&1 > /dev/null &
Thank you so much for your help
Mark
|
On Mon, Sep 25, 2000 at 03:04:33AM +0800, Mark Lo wrote:
> Hi,
>
> I have just installed qmail with tcpserver (following life with qmail), in my
>/var/log/qmail/smtpd/current file, the errors messages stating that "tcpserver:
>fatal: unable to bind: address already used." and this message keeps generating
>itself until filling up all of the space. Please help me to point out for the error.
>
> my startup script in /var/qmail/supervise/qmail-smtpd/run file are as follows:
>
> #!/bin/sh
> QMAILDUID=`id -u qmaild`
> NOFILESGID=`id -u qmaild`
> exec /usr/local/bin/softlimit -m 4000000 \
> /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
> -u $QMAILDUID -g $NOFILESGID 0 smtp \
> /var/qmail/bin/qmail-smptd 2>&1 > /dev/null &
Have you checked inetd.conf? If inetd is listening on port 25 (SMTP), then
this will be the inevitable result. Comment SMTP out from inetd.conf and
restart the inetd daemon with a kill -HUP.
/magnus
--
http://x42.com/
As I have actually used both vmailmgr and vpopmail, I may be able to provide
some comparison information. It boils down to: I've switched to using
vpopmail these days.
vpopmail doesn't have an RPM, which kind of sucks. Making an RPM is hard
because vpopmail compiles the user ID of the "vpopmail" account into the
binary. I started on some patches to fix this, but ran out of time.
vmailmgr DOES work with RPMs. However, the CGI web interface that comes with
it is incomplete to the point of not functioning. Add undocumented... I
ended up having to dig through the code, and then modify the CGIs so I could
even use them... Virtual domains are set up under a user account. Domain
administration is done by providing that user's system password to the
CGI. Naughty...
vpopmail stores all the virtuals under a single "vpopmail" user home
directory (or optionally in another location). No system access is
required for virtual domains or their maintenance. Also, vpopmail
has a nifty option where you can set up virtual IPs for each domain and
vpopmail will resolve "user myname" correctly instead of requiring
"user [EMAIL PROTECTED]"...
>virtual users
vmailmgr: virtual domains are hosted under a particular user id.
Uses system password for CGI-access to virtual domain.
vpopmail: all virtuals stored under a single user ID/directory.
>databases for users and aliases
Yes for both.
>pop access
>imap access
I had no problems setting up POP or IMAP for either.
>quota support
I believe both support quotas but I haven't used them.
>html-mail-administration
vmailmgr: Non-functional demo CGIs provided, which require some time to
install and get working.
vpopmail: QMailAdmin is full-featured and works well. A separate package
from the main vpopmail distribution.
>webmail
I've had a hell of a time getting webmail going with vmailmgr. Most of
them are overly complex to set up or require either PHP4 or a boatload of
Perl modules. I've spent days trying out probably half a dozen or more
different packages. IMP has a fairly complex setup, and just fell on it's
face when I followed the install instructions. AeroMail isn't well
maintained, but is VERY simple and easy to use. I spent hours trying
to get a PHP4 RPM installed, and never could get one that was functional.
I was able to get vpopmail and sqwebmail up and running rather quickly.
I tried looking at getting sqwebmail to use the vmailmgr authentication
scheme, but didn't have any luck in the limited time I had to muck around
with it.
>I did not see webmail in the vmailmgr package, does sqwebmail run with the
>vmailmgr without problems?
I wasn't able to get it to do so. It reads mail directly out of the
Maildirs, so it doesn't use POP/IMAP for authentication. That means
it has to support the vmailmgr auth scheme, which as far as I can tell
it does not.
Sean
--
[...] who asked "Why do we do it, this science?" No one had an answer until
I stood up and said "Isn't there money in a Nobel?" -- Steve Martin
Sean Reifschneider, Inimitably Superfluous <[EMAIL PROTECTED]>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
On Sun, Sep 24, 2000 at 04:11:53PM -0600, Sean Reifschneider wrote:
> >html-mail-administration
>
> vmailmgr: Non-functional demo CGIs provided, which require some time to
> install and get working.
well, there are not only the included CGI's : there is also omail-admin
<http://omail.omnis.ch> and soon some python scripts.
> vpopmail: QMailAdmin is full-featured and works well. A separate package
> from the main vpopmail distribution.
I don't see forwarders, quotas, expiration support in vpopmail-qmailadmin...
On the other hand, mailing list support is missing in omail-admin.
> >webmail
>
> I've had a hell of a time getting webmail going with vmailmgr. Most of
> them are overly complex to set up or require either PHP4 or a boatload of
> Perl modules. I've spent days trying out probably half a dozen or more
> different packages. IMP has a fairly complex setup, and just fell on it's
There is omail-webmail <http://webmail.omnis.ch/omail.pl?action=about>
with a lots of happy users... :)
Regards,
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
PGP signature
Sean Reifschneider wrote:
>
> As I have actually used both vmailmgr and vpopmail, I may be able to provide
> some comparison information. It boils down to: I've switched to using
> vpopmail these days.
>
> vpopmail doesn't have an RPM, which kind of sucks. Making an RPM is hard
> because vpopmail compiles the user ID of the "vpopmail" account into the
> binary. I started on some patches to fix this, but ran out of time.
This can be solved, don't ask me how though. ;) Create a src rpm file,
then it will build and install in one step or how ever it is setup.
I have installed some programs on freebsd and openbsd with pkg_add (sort
of like a rpm type installer) and it does it all from start to finish.
I put pine on a openbsd box and used package add (pkg_add) it looked to
see if it was available local then went to pine's ftp site (and mirrors)
and fetched it, untar'd it made it, installed it and removed the .tar
file. You can set it not to remove the downloaded file if you want.
I imagine an RPM file could be setup the same way for vpopmail.
--
Dale Miracle
System Administrator
Teoi Virtual Web Hosting
Hello,
I'm currently trying to install qmail-scanner (antivirus)
on a server: basic installation seems to work well. Now I
need a virus scanner : on the homepage <http://qmail-scanner.sourceforge.net/>
the following are listed:
* Trend's Virus scanner
* Sophos's "sweep" virus scanner
* H+BEDV's antivir scanner
* AVP AVPLinux scanner
* MacAfee's (NAI's) virus scanner
* F-Secure Anti-Virus scanner
Just tried to use it with AVP and sweep : both returns a
X-Qmail-Scanner-0.90: corrupt scanner/resource problems - exit status 256
in the logfile...
If you are using qmail-scanner, could you please tell me which
program is working well, and if is free ? Thanks in advance,
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
PGP signature
"Olivier M." <[EMAIL PROTECTED]> writes:
> Just tried to use it with AVP and sweep : both returns a
> X-Qmail-Scanner-0.90: corrupt scanner/resource problems - exit status 256
> in the logfile...
>
> If you are using qmail-scanner, could you please tell me which
> program is working well, and if is free ? Thanks in advance,
I use AvpDaemon and it works very well after a little patch of
sub-avp.pl
Your problems seem to result of a perhaps misconfigured AvpLinux or
AvpDaemon. If you use the trial-version of avp you may run into problems
due to the "semi"-automatic tests done by avp.
Unfortunately avp is not free, the license-fee for a (linux) mail-server
is about 100$/year.
Martin
Someone replied but somehow I've lost the email...
I'm sending from host1 direct to host2's SMTP server ie
from host1 -> dougb-$i@host2
When I used the inject command, it completed instantly.
The command used was
echo "This is a test" | /var/qmail/bin/qmail-inject -fdougb-sender@host1 $s
Where $s is "dougb-1@host1 dougb-2@host1 dougb-3@host1 ... dougb-2500@host1"
So far it has delivered 1600 of the 2500 emails in over 2 days!
Thanks
> Hi,
>
> I'm just setting up some scripts to do some bulk mail
>
> I tested by sending to dougb-$[EMAIL PROTECTED] where $i goes from 1 to 2500
> from host2.domain which is on the same subnet (ie very close)
>
> Thats 2,500 emails, however, only 50 or so are delivered at a time in 40
> or so minute intervals.
>
> I really need these mails out quickly (breaking news emails etc). Can
> anyone help?
>
> I've looked at using ezmlm but I really need oracle connectivity and ProC
> programming is really not something I want to learn.
>
> Thanks
> Doug
>
On Fri, Sep 22, 2000 at 06:48:51AM -0400, Michael Cunningham wrote:
> I have a qmail server that is running on a Sun Netra T1
> (solaris 2.6). Its receiving about 300-500k emails per day.
>
> Unfortunatly it appears to be dieing a VERY quick death.
> The IO loads on the disk are huge and I need up performance
> quite a bit. The cpu and memory are fine but disk io is killing
> me. I was think about a couple possible solutions and I wanted
> your input (since you are qmail experts - at least compared to me:)
>
> 1. add a disk/filesystem for each queue subdirectory to reduce
> io load
> <snip>
> 2. create a 1+0 raid of at least 5 drives per stripe, and place
> the entire queue directory structure on this raid filesystem.
> If possible I will veritasfs instead of ufs for the filesystem
> and an a1000 to hold the drives (hardware raid).
1) Make sure you're using cyclog instead of splogger. splogger
uses syslog, which can definitely slow down your system.
2) putting the queue on a 1+0 raid is a good thing. What you
seem to be describing, two raid 0's mirrored, isn't 1+0 raid,
it's 0+1, and isn't as fast or safe. What you want is to
mirror pairs of disk drives, then create a stripe accross
the mirrored pairs. The best way to do this is with hardware
controllers, not a software solution like Veritas (I mention
this because you mention Vxfs). A great thing about hardware
controllers is that they generally come with battery backed
write-back cache, which will cache all of qmail's fsyncs.
With just a few mirrored pairs, you'll be writing information
to disk in chunks much smaller than the individual drives
write cache.
3) Someone mentioned using a solid state disk solution, like that
from Seek Systems. I own a Seek array, and have this comment:
I benchmarked the array's small block write performance with
128MB of write-back cache against a 128MB write-back cache
RAID 1+0 array. The latter blew the former away. The reason
is (as far as I can tell), that the Seek array ultimately uses
a large RAID 5 for it's back-end storage. RAID 1+0 is much
faster as a back-end which my benchmark showed. Perhaps Seek
might benefit from the fact that it's read cache is supposed
to use some advanced algorithmic methods to keep what you use
in the cache. I didn't see that benefit.
Buying an SSD disk from someone like Quantum is generally
prohibitively expensive vs. a good 1+0 RAID, and nowhere
near as safe.
John
On Sun, Sep 24, 2000 at 04:59:24PM -0700, John White wrote:
>
> 1) Make sure you're using cyclog instead of splogger. splogger
> uses syslog, which can definitely slow down your system.
Of course I meant multilog in the most recent daemontools package.
John
|
We have migrated from sendmail to qmail however we
kept the sendmail alias file and majordomo. Is anyone aware of any configuration
that works with our setup? all Majordomo aliases are stored in the alias
file.
Thanks
Ramzi
|
* Ramzi S. Abdallah <[EMAIL PROTECTED]> [000924 23:47]:
> We have migrated from sendmail to qmail however we kept the sendmail
> alias file and majordomo. Is anyone aware of any configuration that
> works with our setup? all Majordomo aliases are stored in the alias
> file.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD NO HTML IN EMAIL, DAMMIT/EN">
<body bgcolor="#0c74e3"><font face=dragonwick size=+7 color=red><blink>
<a href=http://ezmlm.org/faq-0.40/FAQ-15.html>RTFM</a><br>
<a href=http://www.eyrie.org/~eagle/faqs/mjqmail.html>RTFM</a>
</blink></font><body></html>
And would you kindly restrict your line width to something ~72
characters? Thanks.
On Mon, 25 Sep 2000, Robin S. Socha wrote:
> And would you kindly restrict your line width to something ~72
> characters? Thanks.
oh, please... please publically flame me too!
Scott
Using Mailman with Plesk (which uses qmail)
Base Configuration: RedHat 6.2 Server, AMD K6/2 CPU. Plesk 1.3,
Mailman 2.0b5
(If you just want to get qmail working with Mailman and you don�t
use Plesk, jump to Part 3)
Part 1. Getting Plesk and Mailman set up with Apache.
It is important to know that when you install Plesk, it installs it�s
own proprietary directory tree where all software it installs and
configures is located, i.e.: /usr/local/plesk. Also, Plesk rewrites
almost all of the configuration files on the fly, so if you don�t make
your modifications in the right place, you will lose your
modifications the next time someone uses the Plesk Administrator
web interface to make a virtual host change. While I found at first
that having Plesk put it�s files in an unexpected place to be
somewhat of a pain, I eventually found it to be of great benefit.
The directory used to configure Apache under Plesk is
/usr/local/plesk/apache/conf, and the files you want to modify are
httpsd.conf and httpsd.conf.def. The httpsd.conf.def file is a
template. It is used verbatim as the header of the httpsd.conf file
each time Plesk performs an update of the configuration files. The
easiest way to make sure that you are getting configured the way
you want is to change both files.
The first thing I found out was that there was no way to actually
use Mailman and Plesk on the same installation of Apache. Plesk
programmers are pretty good regarding security, so they run all cgi
under suexec. Since Mailman has it�s own cgi wrapper, there was
no easy way to get them working together. I spent days trying but
eventually I gave up on that track. I�m not sure it�s possible without
serious code hacking.
With that said, however, I found a way around it. This is Linux.
There�s always another way!
It is important to note that when I co-located my server, I received
10 IP addresses. While looking in the Plesk/Apache configuration
scripts, I found that the Plesk programmers left the default Apache
command �listen 80� in the httpsd.conf file. This means that Plesk
automatically took over every available IP on port 80. This was the
first thing I had to rectify. So, instead of letting Plesk/Apache listen
to port 80 on every IP, I commented out �listen 80� and manually
set up 9 of the IP addresses and left one out purposefully. The
command for this is �listen x.x.x.x:port� where x.x.x.x is the IP
address you want Apache to listen on and port is self explanatory.
They are additive, and you can use as many of them as you need.
After the Plesk installation, it looked like this:
Listen 80
Listen 443
BindAddress *
And now it looks like this:
Listen 206.132.232.91:80
Listen 206.132.232.92:80
Listen 206.132.232.93:80
Listen 206.132.232.94:80
Listen 206.132.232.95:80
Listen 206.132.232.96:80
Listen 206.132.232.97:80
Listen 206.132.232.98:80
Listen 206.132.232.99:80
Listen 443
BindAddress *
This leaves port 80 on 206.132.232.90 available for us to use in
another way.
What we are after here is Apache running just enough to take care
of the Mailman web interfaces. Now, back to having Plesk install
on it�s own directory tree and it being a benefit. We can now install
a stock Apache RPM and not hurt the Plesk installation one bit.
And, we are going to bind that installation quite specifically to
listen on one address and comment out Listen * and BindAddress
*. We won�t need any virtual hosts for this Apache install. Plesk
does that so well anyway, what would be the point in manually
configuring them?
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
#Listen *
Listen 206.132.232.90:80
#
# BindAddress: You can support virtual hosts with this option. This
directive
# is used to tell the server which IP address to listen to. It can
either
# contain "*", an IP address, or a fully qualified Internet domain
name.
# See also the <VirtualHost> and Listen directives.
#
#BindAddress *
Once this is all done, you can restart everything and you will have
3 copies of Apache running. One each for Plesk Virtual Accounts,
Plesk Administration and Mailman. Plesk only controls two of
them. To restart Plesk manually, you can issue the following
command:
/etc/rc.d/init.d/plesk restart
Part 2. Fixing up DNS.
Once again, Plesk dynamically rewrites the DNS configuration
files, and once again, they leave us a nice way to make
modifications permanent. The directory Plesk uses for this is
/usr/local/plesk/namedb and the files we need to modify are
named.conf and named.conf.def. At the end of named.conf.def and
at the end of named.conf, I added this:
zone "matrixlist.com"{
type master;
file "matrixlist.com";
};
In the same directory, I added a file named matrixlist.com, which contains:
$TTL 3600
@ IN SOA matrixlist.com. admin.matrixlist.com. (
965448528 ; serial
10800 ; refresh
3600 ; retry
604800 ; expire
86400 ) ; minimum
matrixlist.com. IN NS ns1.fiberhosting.net.
matrixlist.com. IN A 206.132.232.90
www.matrixlist.com. IN CNAME matrixlist.com.
mail.matrixlist.com. IN CNAME matrixlist.com.
matrixlist.com. IN MX 10 mail.matrixlist.com.
Restarting Plesk gets our new name service running on the IP of our choice.
To restart DNS under Plesk, issue the following command:
/etc/rc.d/init.d/plesk restart
Part 3. Getting Mailman installed and running.
Since we have a virgin copy of Apache running using a default installation provided by
an RPM, the Mailman installation instructions can be followed to the letter and you
get a beautiful install.
I�ll give you a time saver here. When you ./configure Mailman, you have to give it
some parameters to get it all working.
--with-mail-gid
--with-cgi-gid
You are definitely going to have to get this right to have a working installation, but
I just was never smart enough to figure out exactly what was needed until an operation
failed and gave me an error message. So, my sug
gestion is to not spend a whole lot of time here, but be prepared to recompile Mailman
a few times as you figure out what is what. At first, make a guess. If you get them
right, good for you. If you get them wrong, Mailma
n will throw an error message and tell you what to change! Don�t waste a lot of time
here. I labored over this trying to get it right and wasted a bunch of time.
Anyway, I ended up using:
./configure �set-mail-gid=10029 and �set-cgi-gid=99
make
make install
You may have to redo the above steps as you find out exactly which gid�s you need. I
found Mailman to be the easiest part of the installation once I found out that it
would tell me where I went wrong when I goofed things
up. If you do have to recompile, don�t forget to do a �make clean� first.
As you are following the steps in the INSTALL file in the Mailman install directory,
one of the things you will do is to bring up the web interface to see if it is
running. When you do this, if you got the �with-cgi-gid g
roup wrong, you will probably see an error message that says something like
Got gid=xxx expected yyy. Recompile to accept yyy?
This is Mailman�s way of telling you what you did wrong and how to get it right. Write
down the number it expected for your next compile.
When you start bringing up the qmail interface, you may encounter difficulties if you
got the �with-mail-gid setting wrong. If you look in the /home/mailman/logs directory
you will see a bunch of log files. Look in them I
f you got the mail gid wrong, one of them will be telling you a message like above,
got gid=xxx, expected yyy. Write it down for your next compile.
The good thing is that a ./configure and make clean;make;make install doesn�t seem to
disturb anything.
Part 4. Getting qmail to cooperate.
Under Plesk, qmail configuration files are in /usr/local/plesk/qmail/control. In that
directory, I modified two files.
In rcpthosts, I added:
matrixlist.com
In virtualdomains, I added:
matrixlist.com:mailman
If you followed the Mailman instructions, you created a user named mailman. This entry
redirects mail to that user.
With that done, you can restart qmail under Plesk by running:
/etc/rc.d/init.d/plesk restart
Part 5. Adding lists and aliases.
Now that the hard part is over, you should have a running Mailman installation and you
can add your first list. The Mailman instructions suggest a first list named test, and
I think that is a great idea. Add your test lis
t according to the instructions in the Mailman INSTALL file. Then, once you have done
that, you need to add the qmail aliases.
In the /home/mailman/bin directory, create a file named mailalias.sh and put the
following in it:
#!/bin/sh
if [ $# = 1 ]; then
i=$1
echo Making links to $i...
echo "|preline /home/mailman/mail/wrapper post $i" > .qmail-$i
echo "|preline /home/mailman/mail/wrapper mailowner $i" > .qmail-$i-admin
echo "|preline /home/mailman/mail/wrapper mailowner $i" > .qmail-$i-owner
echo "|preline /home/mailman/mail/wrapper mailowner $i" > .qmail-owner-$i
echo "|preline /home/mailman/mail/wrapper mailcmd $i" > .qmail-$i-request
fi
Now, move to the /home/mailman directory and run:
bin/mailalias.sh test
This will create the qmail aliases.
At this point, restart Plesk one last time and test out your installation. Everything
should be working.
Now, with all that said, I am no expert on qmail or Mailman. I depended heavily on the
mailing lists for those two respective projects. I asked stupid questions and argued
with people. I got some pretty good help from som
e of them. Mailing lists are what they are. Great benefit can be derived from mailing
lists if you don�t give up.
Happy Mail Listing.
Phil Barnett
[EMAIL PROTECTED]
--
Phil Barnett mailto:[EMAIL PROTECTED]
WWW http://www.the-oasis.net/
FTP Site ftp://ftp.the-oasis.net
As seen on freshmeat.net this morning...
Any chance so see such improvments to qmail comming?
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
On Mon, Sep 25, 2000 at 09:34:27AM +0200, Olivier M. wrote:
> As seen on freshmeat.net this morning...
> Any chance so see such improvments to qmail comming?
Depends on whether you actually consider this an "improvement" as opposed to
an invasion of privacy.
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> | "No matter how much it changes,
http://flounder.net/publickey.html | technology's just a bunch of wires
GPG: 17A4 11F7 5E7E C2E7 08AA | connected to a bunch of other wires."
38B0 05D0 8BF7 2C6D 110A | Joe Rogan, _NewsRadio_
On Fre, 22 Sep 2000, [EMAIL PROTECTED] wrote:
> On Fri, Sep 22, 2000 at 11:34:54AM +0200, [EMAIL PROTECTED] wrote:
> > Should I post the output of qmail-showctl?
>
> And give us a syscall trace of qmail inject, it's only 44 lines of output
> on a Solaris box.
So, here we go:
root@pool2-01:/var/qmail/bin > ./qmail-showctl
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 701, 702, 703, 0, 704, 705, 706, 707.
group ids: 701, 702.
defaultdomain: Default domain name is numa.uni-linz.ac.at.
defaulthost: Default host name is numa.uni-linz.ac.at.
idhost: Message-ID host name is pool2-01.
me: My name is mail.numa.uni-linz.ac.at.
plusdomain: Plus domain name is ac.at.
qmqpservers:
QMQP server: mail.numa.uni-linz.ac.at.
Everything else is default.
strace echo to: koch | /var/qmail/bin/qmail-inject
execve("/bin/echo", ["echo", "to:", "koch"], [/* 47 vars */]) = 0
brk(0) = 0x804a82c
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=35241, ...}) = 0
mmap(NULL, 35241, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40014000
close(3) = 0
open("/lib/libc.so.6", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0755, st_size=4060704, ...}) = 0
read(3,"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\213"..., 4096) = 4096
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,-1, 0) = 0x4001d000
mmap(NULL, 924892, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001e000
mprotect(0x400f8000, 31964, PROT_NONE) = 0
mmap(0x400f8000, 20480, PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED, 3, 0xd9000) =
0x400f8000
mmap(0x400fd000, 11484, PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1,
0) = 0x400fd000
close(3) = 0
munmap(0x40014000, 35241) = 0
getpid() = 8409
brk(0) = 0x804a82c
brk(0x804a864) = 0x804a864
brk(0x804b000) = 0x804b000
open("/usr/share/locale/locale.alias", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2265, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,-1, 0) = 0x40014000
read(3, "# Locale name alias data base.\n#"..., 4096) = 2265
brk(0x804c000) = 0x804c000
read(3, "", 4096) = 0
close(3) = 0
munmap(0x40014000, 4096) = 0
[open of different LOCALE-stuff, all OK]
open("/usr/share/locale/de_DE/LC_CTYPE", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=87756, ...}) = 0
mmap(NULL, 87756, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40108000
close(3) = 0
fstat(1, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40018000
write(1, "to: koch\n", 9) = 9
munmap(0x40018000, 4096) = 0
_exit(0) = ?
qmail-inject: fatal: qq unable to read configuration (#4.3.0)
Thanks so far,
--
Oliver Koch Registered Linux User 163952
Don't put off for tomorrow what you can do today, because if you enjoy
it today you can do it again tomorrow.
