qmail Digest 29 Nov 2000 11:00:00 -0000 Issue 1198
Topics (messages 52957 through 53015):
rblsmtpd and firewall
52957 by: Roberto Samarone Araujo \(RSA\)
52958 by: Chris Johnson
52959 by: Roberto Samarone Araujo \(RSA\)
52960 by: Chris Johnson
Re: qmail-ldap-mysql
52961 by: Henning Brauer
qmail imapd?
52962 by: achim.venus
52963 by: Peter Green
Re: Henning Brauer's reply
52964 by: Henning Brauer
Re: Please Help me: supervise:fatal
52965 by: Charles Cazabon
Handling To: entries (defaulthost?)
52966 by: Wolfgang Zeikat
52967 by: Frank Tegtmeyer
52990 by: Wolfgang Zeikat
Re: pop3 question??
52968 by: markd.bushwire.net
creating an aliases.cdb without newaliases?
52969 by: Collin B. McClendon
52982 by: Alex Pennace
qmail startup error --xrealloc: cannot reallocate...
52970 by: Trey Nolen
smtp auth over sasl
52971 by: achim.venus
The whole mail puts into the local queue?
52972 by: eric yu
52973 by: Peter Samuel
52974 by: Kris Kelley
52978 by: Peter Samuel
52979 by: Kris Kelley
52980 by: Peter Samuel
qmail startup error --xrealloc: cannot reallocate..
52975 by: Trey Nolen
qmail-pop3d
52976 by: Antonio S. Martins Jr.
Blocking qmails by subject
52977 by: Roberto Samarone Araujo \(RSA\)
virtual domains
52981 by: Rick Glunt
52996 by: Alex Pennace
Install and communicate two qmail servers is possible?
52983 by: Ould
52986 by: markd.bushwire.net
unable to control /var/qmail/supervise/qmail-send
52984 by: Silberman, Malcolm (BHR)
52987 by: markd.bushwire.net
52991 by: Silberman, Malcolm (BHR)
52992 by: Silberman, Malcolm (BHR)
52994 by: markd.bushwire.net
52995 by: Robin S. Socha
52998 by: Silberman, Malcolm (BHR)
qmail logging
52985 by: Chris Olson
Error messages - what do they mean?
52988 by: Johan Almqvist
52989 by: markd.bushwire.net
52993 by: Johan Almqvist
How to use qmail to get mails of a different domaine?
52997 by: Ould
qmail capasity ?
52999 by: Are Haugsdal
53000 by: Thorkild Stray
Re: Amazon says the book will be out next month. Russ?
53001 by: Russell Nelson
Re: ORBS helps hackers to break into srevers
53002 by: Russell Nelson
53009 by: Piotr Kasztelowicz
more than 65535 accounts on one mail server
53003 by: corvus.vadept.com
53005 by: Sean Reifschneider
53006 by: Henning Brauer
Re: secrets and lies
53004 by: Russell Nelson
newbie question
53007 by: suresh
53008 by: Henning Brauer
53012 by: suresh
53013 by: Henning Brauer
Relaying Question (Wait! I read the FAQ and searched the archives)
53010 by: corvus.vadept.com
53011 by: Alex Pennace
(no subject)
53014 by: Ismail YENIGUL
IsoQlog Qmail Log Analyzer
53015 by: Ismail YENIGUL
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 turned on my firewall and I looked at my logs when I found this message:
smtpd: 975401579.539737 tcpserver: fatal: unable to figure out
port number for /usr/local/bin/rblsmtpd
What's the port number and protocol(TCP or UDP) that rblsmtpd use ?
thanks,
Roberto Samarone Araujo
On Tue, Nov 28, 2000 at 09:00:04AM -0300, Roberto Samarone Araujo (RSA) wrote:
> I turned on my firewall and I looked at my logs when I found this message:
>
> smtpd: 975401579.539737 tcpserver: fatal: unable to figure out
> port number for /usr/local/bin/rblsmtpd
>
> What's the port number and protocol(TCP or UDP) that rblsmtpd use ?
Your startup script is messed up. Post it and someone will tell you how to fix
it.
Chris
>
> Your startup script is messed up. Post it and someone will tell you how to
fix
> it.
>
Ok ...
I put in my qmail.rc this :
/usr/local/bin/tcpserver -b 64 -c 64 -x/etc/tcp.smtp.cdb -g 82 -u 82 -t 600
0 /usr/local/bin/rblsmtpd /var/qmail/bin/qmail-smtpd 2>&1 |
/var/qmail/bin/splogger smtpd &
thanks
Roberto Samarone Araujo
On Tue, Nov 28, 2000 at 09:37:40AM -0300, Roberto Samarone Araujo (RSA) wrote:
> /usr/local/bin/tcpserver -b 64 -c 64 -x/etc/tcp.smtp.cdb -g 82 -u 82 -t 600
> 0 /usr/local/bin/rblsmtpd /var/qmail/bin/qmail-smtpd 2>&1 |
> /var/qmail/bin/splogger smtpd &
You're missing the port argument. You need to put "smtp" between "0" and
"/usr/local/bin/rblsmtpd."
Chris
Am Dienstag, 28. November 2000 13:26 schrieb suresh:
> Hi
> I have configured ldap-mysql,
I don't know about ldap-mysql, and most of the others won't, too. You are on
the wrong list.
> I am trying to setup qmailldap patch
> I am trying to get started .
> what db/tables do i need to create on the mysql ,are there any docs about
> this
> I am tryng to use the schema from ftp://ftp.eyeo.com/qmail/qmail.schema
>
> thanx in advance
> Suresh
> Mithi.com Pvt. Ltd.
> ------------------------------------------
> Send and receive mail in Indian languages
> Register free at http://www.mailjol.com
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
hello list,
i'm new to qmail.
i've installed successfully qmail, qmail-smtpd and qmail-pop3d.
i would like to know if there's an imap server - working together with
qmail - too?
regards
achim
* achim@venus <[EMAIL PROTECTED]> [001128 08:37]:
> hello list,
>
> i'm new to qmail.
Welcome! You ought to know about the qmail home page, chalked full of useful
links and whatnot. <http://www.qmail.org/>
> i've installed successfully qmail, qmail-smtpd and qmail-pop3d.
> i would like to know if there's an imap server - working together with
> qmail - too?
(pcg@micah) ~> lynx -dump http://www.qmail.org/top.html | grep -ic imap
22
22 hits on that qmail page for IMAP... :)
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
So in the future, one 'client' at a time or you'll be spending CPU time with
lots of little 'child processes'.
(Kevin M. Bealer, commenting on the private life of a Linux nerd.)
Am Dienstag, 28. November 2000 07:28 schrieb Chris Olson:
> > > You should have read a least the documentation before wasting bandwidth
> > > and our time.
> > I did read the documentation, but this was something I could not find
> > any documentation on, or else I didn't know where to look. I found all
> > sorts of documentation on qmail configuration, but nothing on it's
> > startup scripts. I happen to be new to the Linux OS, and new to qmail,
> > so please excuse my ignorance.
http://cr.yp.to/ucspi-tcp/rblsmtpd.html
> Chris
Some words were a bit hard, I'm sorry for that. I got a bit angry about
another post on qmail-ldap's list. I shouldn't have mixed that with this mail
- afterwards it's always easy to say "i should have".
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
Ould <[EMAIL PROTECTED]> wrote:
>
> I'm using strictely "Live With Qmail" instructions. When I
> stop and run qmail script (in /etc/rc.d/inet.d/), I got the
> following error:
> "supervise:fatal:unable to start qmail-smptd/run: exec
> format error".
I would say you've got a typo in your qmail-smtpd run script. Either download
a new copy from Dave Sill's site (rather than trying to type it manually),
or post your current script here so we can see what's wrong with it.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
we have lately gotten tons of mails from external senders with weird To:
entries based on various email client address books with commas,
semicolons, whitespaces and such.
so i now want to *stop* qmail from automatically expanding
"To: whatever" into "To: [EMAIL PROTECTED]"
so that only intact [EMAIL PROTECTED] entries in To: fields will be
handled -
and reject the others.
how can i do that? just set defaulthost to something like "defaulthost"
?
and is it possible to have different handling for incoming and outgoing
mails?
current settings are:
# more /var/qmail/control/me
mail.webseek.de
# more /var/qmail/control/defaulthost
webseek.de
> we have lately gotten tons of mails from external senders with weird To:
> so i now want to *stop* qmail from automatically expanding
> "To: whatever" into "To: [EMAIL PROTECTED]"
This has nothing to do with the To: header. Somehow you get the mail
through SMTP (external senders?) - Then only the envelope receiver is
used.
About qmail-smtpd:
Envelope recipient addresses without @ signs are
always allowed through.
To avoid this you would have to patch qmail-smtpd.
I doubt that the sender is really external - you wouldn't get the mail
through SMTP because of missing MX records. I think there is a wild
running script or a buggy SMTP client inside your network.
Regards, Frank
Frank Tegtmeyer schrieb:
> I doubt that the sender is really external - you wouldn't get the mail
> through SMTP because of missing MX records.
good point
> I think there is a wild
> running script or a buggy SMTP client inside your network.
>
> Regards, Frank
you were right, i found the bad guy: one of our users had entries like
"display name: Name, Firstname" in their netscape address book, and the
external people had replied to his mails using "Reply To All" *sigh*
thanks
wolfgang
On Tue, Nov 28, 2000 at 12:01:48PM +0200, tag wrote:
> Hi ALL,
>
> Is it possible to simulate pop3 conections to a mail server and
> authenticate the user and tell that user that he has no mail ??
>
> The reasoning behind this is I want a temp backup server that can take
> the pop3 strain while I make some modifications to the main mail server
> ??
Yes it is. And quite easy too. All you need to do is replace checkpassword
with an dummy program that changes to an innocuous home directory that has
an empty Maildir (assuming the usual Maildir in home).
A good idea is to have a look at the existing checkpassword.c, but essentially
all you need your replacement checkpassword to do is:
#! /bin/sh
cd /home/dummy
exec $*
And that's it! Of course you need an empty Maildir in /home/dummy.
This replacement checkpassword simply ignores the user and password retreived
by qmail-popup - but do you care whether they get their password right or
wrong during this maintenance period? They only see an empty mailbox regardless.
As an added precaution, you should also setuid and setgid away from root,
but you can achieve this by having a different invocation of tcpserver.
Regards.
I've looked and not found much so here goes:
I have used newaliases on several systems, however it only creates an
aliases.db.
Perhaps I'm overlooking something simple. I've gotten the cdb source, used
cdbmake, doesn't
seem compatible, cdbmake-12 does the same thing. I end up with a .cdb file
however
printforward won't read it.
Any help would be greatly appreciated,
Collin
On Tue, Nov 28, 2000 at 10:46:04AM -0500, Collin B. McClendon wrote:
> I've looked and not found much so here goes:
> I have used newaliases on several systems, however it only creates an
> aliases.db.
The man page for newaliases indicates otherwise.
> Perhaps I'm overlooking something simple. I've gotten the cdb source, used
> cdbmake, doesn't
> seem compatible, cdbmake-12 does the same thing. I end up with a .cdb file
> however
> printforward won't read it.
cdbs are application dependant. A cdb for fastforward won't work for
tcpserver, for example.
PGP signature
|
I'm running a Debian system with Qmail 1.03.
Everything has been working
fine, until yesterday the server quit accepting
connections on port 25. I
checked and qmail-send, qmail-lspawn,
qmail-rspawn, and qmail-clean are all
running fine, but the tcpserver for
qmail is not running. I stopped it
using the init scripts, and tried
restarting. On restart, I get this error:
Starting mail-transfer agent:
qmail./qmail: xrealloc: cannot reallocate 512
bytes (0 bytes
allocated)
I know my tcpserver is OK because I'm using it to run
qmail-pop3d, which is
working fine. My command to start the
tcpserver for qmail is:
/usr/bin/tcpserver -- -x /etc/tcp.smtp.cdb
\
-g65534
-u64011 0 smtp
\
/usr/sbin/qmail-smtpd 2>&1 | logger -t qmail -p mail.notice
&
I checked to make sure that the user and group numbers were
correct, and
they are. I know the tcp.smtp.cdb database is OK, since it
works with
qmail-pop3d. Does anyone have any ideas as to what could be
causing that
error?
Trey Nolen
|
hello,
does anyone know about an sasl patch for qmail?
or are there builtin features for sasl smntp auth i haven't found yet?
thanks in advance
achim.
Dear all,
Does anyone experienced that part or whole of the mail has been put piece by piece in
the qmail queue's local directory (/var/qmail/queue/local/23/57890) rather than just
the receiver's mail address??
Any problems that may leads to this symptom???
thanks and regards,
Eric
--
_______________________________________________
Get your free email from http://freemail.asiamail.com
On Wed, 29 Nov 2000, eric yu wrote:
> Dear all,
>
> Does anyone experienced that part or whole of the mail has been put piece by piece
>in the qmail queue's local directory (/var/qmail/queue/local/23/57890) rather than
>just the receiver's mail address??
>
> Any problems that may leads to this symptom???
>
Eric, based on the problem you were having yesterday with qmail-smtpd,
and now this one, it sounds like you have a seriously corrupted qmail
install. I'd suggest recompiling from scratch.
--
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
> Does anyone experienced that part or whole of the mail has been put piece
by
> piece in the qmail queue's local directory
(/var/qmail/queue/local/23/57890)
> rather than just the receiver's mail address??
This is how qmail normally operates. All messages are first placed in the
queue before being sent out, in case the machine crashes before the SMTP
transaction is complete.
People have suggested ways around this when speed is an issue; check the
list archives.
---Kris Kelley
On Tue, 28 Nov 2000, Kris Kelley wrote:
> > Does anyone experienced that part or whole of the mail has been put piece
> by
> > piece in the qmail queue's local directory
> (/var/qmail/queue/local/23/57890)
> > rather than just the receiver's mail address??
>
> This is how qmail normally operates. All messages are first placed in the
> queue before being sent out, in case the machine crashes before the SMTP
> transaction is complete.
No it isn't. qmail-queue puts only the local recipient addresses in
/var/qmail/queue/local/*/*. The message itself is placed in
/var/qmail/queue/mess/*/*.
Eric's problem is that the message is being placed in
/var/qmail/queue/local/*/* rather than just the local recipient
addresses.
I think his qmail install is severely corrupted.
--
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
Peter Samual wrote:
> > This is how qmail normally operates. All messages are first placed in
the
> > queue before being sent out, in case the machine crashes before the SMTP
> > transaction is complete.
>
> No it isn't. qmail-queue puts only the local recipient addresses in
> /var/qmail/queue/local/*/*. The message itself is placed in
> /var/qmail/queue/mess/*/*.
Whoops, read too quickly. Apologies.
> I think his qmail install is severely corrupted.
Sounds like it. Makes me wonder what kind of corruption can cause that.
---Kris Kelley
On Tue, 28 Nov 2000, Kris Kelley wrote:
> Peter Samual wrote:
> ...
> > No it isn't. qmail-queue puts only the local recipient addresses in
> > /var/qmail/queue/local/*/*. The message itself is placed in
> > /var/qmail/queue/mess/*/*.
>
> Whoops, read too quickly. Apologies.
>
> > I think his qmail install is severely corrupted.
>
> Sounds like it. Makes me wonder what kind of corruption can cause that.
Some weird patches incorrectly applied is my guess.
--
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
Phone: +1 613 368 4398 Fax: +1 613 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
"If you kill all your unhappy customers, you'll only have happy ones left"
|
I'm running a Debian system with Qmail 1.03.
Everything has been working
fine, until the other day the server quit
accepting connections on port 25. I
checked and qmail-send,
qmail-lspawn, qmail-rspawn, and qmail-clean are all
running fine, but the
tcpserver for qmail is not running. I stopped it
using the init
scripts, and tried restarting. On restart, I get this error:
Starting
mail-transfer agent: qmail./qmail: xrealloc: cannot reallocate 512
bytes (0
bytes allocated)
I know my tcpserver is OK because I'm using it to run
qmail-pop3d, which is
working fine. My command to start the
tcpserver for qmail is:
/usr/bin/tcpserver -- -x /etc/tcp.smtp.cdb
\
-g65534
-u64011 0 smtp
\
/usr/sbin/qmail-smtpd 2>&1 | logger -t qmail -p mail.notice
&
I checked to make sure that the user and group numbers were
correct, and
they are. I know the tcp.smtp.cdb database is OK, since it
works with
qmail-pop3d. Does anyone have any ideas as to what could be
causing that
error?
Trey Nolen
|
Hi,
We had a mail server running Qmail 1.03 with the paths to authenticate
against the MySQL DB. We use maildir. We had qmail-pop3d running on it.
But some of our users can't receive their email via pop3. They use Outlook
or Netscape, and when there are many messages (20 or more) or bigger
messages (1Mb), the client stops receiving and indicate that: "The POP3
server cannot respond in 60 sec., wait?"
If the user wait or cancel, he can't receive his email. But he still
connected and can browse the web without problems!
Are anything I can do to debug it? And are anything I can do to alter
the pop3d behaviour to actualy delete a message after that message are
read, without wait to do that after all the messages are read? Becouse on
the current way, if a user had 60 messages and the pop3d stops on the
message 59, he needs to download all the messages again!
Thanks in advance,
Antonio.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Antonio S. Martins Jr. - System Analist | "Only The Shadow Knows |
| WorldNet Internet Maringa - PR - Brasil | what evil lurks in the |
| E-Mail: [EMAIL PROTECTED] | Heart of Men!" |
| [EMAIL PROTECTED] | !!! Linux User: 52392 !!! |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This e-mail message is 100% Microsoft free!
/"\
\ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
/ \
Hi,
I would like to know how can I block emails by subject. Is it
possible to do with qmail ?? How can I do that ?
thanks,
Roberto Samarone Araujo
|
I have a mail server running qmail and accepting
mail for a virtual domain via fastforward (all mail addressed to @mydomain.com
is sent to a user). Mail coming into this server for the virtual domain is
being sent to the users mailbox just fine.
Now I want to use this users mailbox as a multidrop
box. Another server (running qmail) connects to the mailbox and retrieves
all the mail but then logs messages indicating that the messages retrieved
already have a 'delivered_to". When the messages are put in the users
mailbox on the first server the delivered to lines are added thus causing the
problem.
How can I get this to work?
Thanks,
Rick
|
On Tue, Nov 28, 2000 at 02:17:35PM -0500, Rick Glunt wrote:
> I have a mail server running qmail and accepting mail for a virtual domain via
>fastforward (all mail addressed to @mydomain.com is sent to a user). Mail coming
>into this server for the virtual domain is being sent to the users mailbox just fine.
Wow. Seems everyone handles mail for mydomain.com.
> Now I want to use this users mailbox as a multidrop box. Another server (running
>qmail) connects to the mailbox and retrieves all the mail but then logs messages
>indicating that the messages retrieved already have a 'delivered_to". When the
>messages are put in the users mailbox on the first server the delivered to lines are
>added thus causing the problem.
This is an FAQ, which you should have read prior to posting
here. <http://cr.yp.to/qmail/faq/outgoing.html#serialmail>
PGP signature
Hi,
I want helps of anyone already running qmail or at least
having a simple idea on how configurating both local server
(which is in my LAN, behind a firewall, not visible to
internet)and a second server(in my DMZ region, visible by
internet but well serve only for sinding to and receiving
mails of my mail local server, it is also behind a second
firewall but having an internet IP).
I want to use qmail on each server and communacte them, but
never seen any docs talking about how this configuration
can be made.
Thanks for any helps.
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
On Tue, Nov 28, 2000 at 11:39:33AM -0800, Ould wrote:
> Hi,
>
> I want helps of anyone already running qmail or at least
> having a simple idea on how configurating both local server
> (which is in my LAN, behind a firewall, not visible to
> internet)and a second server(in my DMZ region, visible by
> internet but well serve only for sinding to and receiving
> mails of my mail local server, it is also behind a second
> firewall but having an internet IP).
Sure. Plenty of people have done that and there is plenty
of discussion archived (www.qmail.org has a pointer). You'll want
to search on smtproutes.
Your external server will have an smtproutes entry for your domain,
pointing to your internal server. Your internal server will be
configured in the standard way and will not need to be aware
of the external system.
Regards.
I have installed Qmail a few times on Mandrake OS, and it worked fine. I go
exactly according to Qmail how to by Adam McKenna. Now I tried to install on
RedHat7 (and posted ome questions last week). I cameup with a dead end, so
droped down to 6.2, but still I getthe following;
svc: warning: unable to control /var/qmail/supervise/qmail-send: file does
not exist
svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file does
not exist
qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
file does not exist
svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
does not exist
logging.
Does anyone have any ideas on hat I ight be doing wrong. I have checked
through a wide number of nes groups and have found this toic come up, but no
certain answers. The messages just don't make sense to me. I have tried
running the rc and un scripts by hand and they seem to work fine. I have
checked that svc and suprvise are in my path /usr/local/bin and they are.
Thanks
This e-mail and any files transmitted with it are intended for, and should only be
read by, the intended addressee. Its contents are confidential and if you are not the
intended addressee, please notify the sender immediately and delete all records of the
message from your computer. Any reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this message without the prior
written consent of the sender are strictly prohibited. The contents of this
communication represent the sender's personal views and opinions, which do not
necessarily reflect those of Bass Hotels & Resorts, Inc.
On Tue, Nov 28, 2000 at 02:34:37PM -0500, Silberman, Malcolm (BHR) wrote:
> I have installed Qmail a few times on Mandrake OS, and it worked fine. I go
> exactly according to Qmail how to by Adam McKenna. Now I tried to install on
> RedHat7 (and posted ome questions last week). I cameup with a dead end, so
> droped down to 6.2, but still I getthe following;
> svc: warning: unable to control /var/qmail/supervise/qmail-send: file does
> not exist
>
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file does
> not exist
> qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
> file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
> does not exist
> logging.
Post the output of: ls -lR /var/qmail
Regards.
I have attched the output of ls -lR /var/qmail
hope it helps, thanks for your help!
Regards
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 28, 2000 3:06 PM
To: QMail Mailing List
Subject: Re: unable to control /var/qmail/supervise/qmail-send
On Tue, Nov 28, 2000 at 02:34:37PM -0500, Silberman, Malcolm (BHR) wrote:
> I have installed Qmail a few times on Mandrake OS, and it worked fine. I
go
> exactly according to Qmail how to by Adam McKenna. Now I tried to install
on
> RedHat7 (and posted ome questions last week). I cameup with a dead end, so
> droped down to 6.2, but still I getthe following;
> svc: warning: unable to control /var/qmail/supervise/qmail-send: file does
> not exist
>
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file
does
> not exist
> qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
> file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
> does not exist
> logging.
Post the output of: ls -lR /var/qmail
Regards.
This e-mail and any files transmitted with it are intended for, and should only be
read by, the intended addressee. Its contents are confidential and if you are not the
intended addressee, please notify the sender immediately and delete all records of the
message from your computer. Any reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this message without the prior
written consent of the sender are strictly prohibited. The contents of this
communication represent the sender's personal views and opinions, which do not
necessarily reflect those of Bass Hotels & Resorts, Inc.
Starting mail-transport-agent:svc: warning: unable to control
/var/qmail/supervise/qmail-send: file does not exist
svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file does not exist
qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log: file does
not exist
svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file does not
exist
logging.
oops wrong file attached....
here it is
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 28, 2000 3:06 PM
To: QMail Mailing List
Subject: Re: unable to control /var/qmail/supervise/qmail-send
On Tue, Nov 28, 2000 at 02:34:37PM -0500, Silberman, Malcolm (BHR) wrote:
> I have installed Qmail a few times on Mandrake OS, and it worked fine. I
go
> exactly according to Qmail how to by Adam McKenna. Now I tried to install
on
> RedHat7 (and posted ome questions last week). I cameup with a dead end, so
> droped down to 6.2, but still I getthe following;
> svc: warning: unable to control /var/qmail/supervise/qmail-send: file does
> not exist
>
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file
does
> not exist
> qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
> file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
> does not exist
> logging.
Post the output of: ls -lR /var/qmail
Regards.
This e-mail and any files transmitted with it are intended for, and should only be
read by, the intended addressee. Its contents are confidential and if you are not the
intended addressee, please notify the sender immediately and delete all records of the
message from your computer. Any reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this message without the prior
written consent of the sender are strictly prohibited. The contents of this
communication represent the sender's personal views and opinions, which do not
necessarily reflect those of Bass Hotels & Resorts, Inc.
/var/qmail:
total 64
drwxr-sr-x 2 alias qmail 4096 Nov 28 12:39 alias
drwxr-xr-x 2 root qmail 4096 Nov 28 12:35 bin
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 boot
drwxr-xr-x 2 root qmail 4096 Nov 28 12:35 control
-rwx------ 1 root root 421 Nov 28 12:15 create
-rwx------ 1 root root 443 Nov 28 12:41 create2
-rwx------ 1 root root 421 Nov 28 12:39 create2~
-rwxr-xr-x 1 root root 409 Nov 28 12:14 create~
drwxr-xr-x 3 root qmail 4096 Nov 28 12:34 doc
drwxr-xr-x 10 root qmail 4096 Nov 28 12:18 man
-rwxr-xr-x 1 root root 1119 Nov 28 13:02 qmail
drwxr-x--- 11 qmailq qmail 4096 Nov 28 12:18 queue
-rwxr-xr-x 1 root root 95 Nov 28 13:14 rc
drwxr-xr-x 4 root root 4096 Nov 28 12:41 supervise
-rwxr-xr-x 1 root root 1297 Nov 28 13:01 svscan
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 users
/var/qmail/alias:
total 0
/var/qmail/bin:
total 848
-rwxr-xr-x 1 root qmail 9248 Nov 28 12:18 bouncesaying
-rwxr-xr-x 1 root qmail 15404 Nov 28 12:18 condredirect
-rwxr-xr-x 1 root qmail 126 Nov 28 12:18 datemail
-rwxr-xr-x 1 root root 28176 Nov 28 12:35 dot-forward
-rwxr-xr-x 1 root qmail 114 Nov 28 12:18 elq
-rwxr-xr-x 1 root qmail 9184 Nov 28 12:18 except
-rwxr-xr-x 1 root root 23876 Nov 28 12:34 fastforward
-rwxr-xr-x 1 root qmail 14380 Nov 28 12:18 forward
-rwxr-xr-x 1 root qmail 19212 Nov 28 12:18 maildir2mbox
-rwxr-xr-x 1 root qmail 8860 Nov 28 12:18 maildirmake
-rwxr-xr-x 1 root qmail 17384 Nov 28 12:18 maildirwatch
-rwxr-xr-x 1 root qmail 179 Nov 28 12:18 mailsubj
-rwxr-xr-x 1 root root 24796 Nov 28 12:34 newaliases
-rwxr-xr-x 1 root root 22756 Nov 28 12:34 newinclude
-rwxr-xr-x 1 root qmail 115 Nov 28 12:18 pinq
-rwxr-xr-x 1 root qmail 13020 Nov 28 12:18 predate
-rwxr-xr-x 1 root qmail 13240 Nov 28 12:18 preline
-rwxr-xr-x 1 root root 11608 Nov 28 12:34 printforward
-rwxr-xr-x 1 root root 11544 Nov 28 12:34 printmaillist
-rwxr-xr-x 1 root qmail 115 Nov 28 12:18 qail
-rwxr-xr-x 1 root qmail 11908 Nov 28 12:18 qbiff
-rwx--x--x 1 root qmail 10260 Nov 28 12:18 qmail-clean
-rwx--x--x 1 root qmail 5792 Nov 28 12:18 qmail-getpw
-rwxr-xr-x 1 root qmail 34748 Nov 28 12:18 qmail-inject
-rwx--x--x 1 root qmail 33944 Nov 28 12:18 qmail-local
-rwx------ 1 root qmail 17256 Nov 28 12:18 qmail-lspawn
-rwx------ 1 root qmail 14352 Nov 28 12:18 qmail-newmrh
-rwx------ 1 root qmail 11584 Nov 28 12:18 qmail-newu
-rwxr-xr-x 1 root qmail 18988 Nov 28 12:18 qmail-pop3d
-rwx--x--x 1 root qmail 11344 Nov 28 12:18 qmail-popup
-rwx--x--x 1 root qmail 15880 Nov 28 12:18 qmail-pw2u
-rwxr-xr-x 1 root qmail 13016 Nov 28 12:18 qmail-qmqpc
-rwxr-xr-x 1 root qmail 13888 Nov 28 12:18 qmail-qmqpd
-rwxr-xr-x 1 root qmail 21128 Nov 28 12:18 qmail-qmtpd
-rwxr-xr-x 1 root qmail 15348 Nov 28 12:18 qmail-qread
-rwxr-xr-x 1 root qmail 371 Nov 28 12:18 qmail-qstat
-rws--x--x 1 qmailq qmail 12708 Nov 28 12:18 qmail-queue
-rwx--x--x 1 root qmail 25288 Nov 28 12:18 qmail-remote
-rwx--x--x 1 root qmail 13444 Nov 28 12:18 qmail-rspawn
-rwx--x--x 1 root qmail 39492 Nov 28 12:18 qmail-send
-rwxr-xr-x 1 root qmail 15956 Nov 28 12:18 qmail-showctl
-rwxr-xr-x 1 root qmail 26108 Nov 28 12:18 qmail-smtpd
-rwx------ 1 root qmail 5548 Nov 28 12:18 qmail-start
-rwxr-xr-x 1 root qmail 9248 Nov 28 12:18 qmail-tcpok
-rwxr-xr-x 1 root qmail 10356 Nov 28 12:18 qmail-tcpto
-rwxr-xr-x 1 root qmail 21724 Nov 28 12:18 qreceipt
-rwxr-xr-x 1 root qmail 11344 Nov 28 12:18 qsmhook
-rwxr-xr-x 1 root qmail 9588 Nov 28 12:18 sendmail
-rwxr-xr-x 1 root root 15136 Nov 28 12:34 setforward
-rwxr-xr-x 1 root root 12332 Nov 28 12:34 setmaillist
-rwx--x--x 1 root qmail 6544 Nov 28 12:18 splogger
-rwxr-xr-x 1 root qmail 17464 Nov 28 12:18 tcp-env
/var/qmail/boot:
total 40
-rwxr-xr-x 1 root qmail 347 Nov 28 12:18 binm1
-rwxr-xr-x 1 root qmail 431 Nov 28 12:18 binm1+df
-rwxr-xr-x 1 root qmail 316 Nov 28 12:18 binm2
-rwxr-xr-x 1 root qmail 400 Nov 28 12:18 binm2+df
-rwxr-xr-x 1 root qmail 314 Nov 28 12:18 binm3
-rwxr-xr-x 1 root qmail 398 Nov 28 12:18 binm3+df
-rwxr-xr-x 1 root qmail 204 Nov 28 12:18 home
-rwxr-xr-x 1 root qmail 292 Nov 28 12:18 home+df
-rwxr-xr-x 1 root qmail 223 Nov 28 12:18 proc
-rwxr-xr-x 1 root qmail 309 Nov 28 12:18 proc+df
/var/qmail/control:
total 20
-rw-r--r-- 1 root root 10 Nov 28 12:35 defaultdomain
-rw-r--r-- 1 root root 14 Nov 28 12:35 locals
-rw-r--r-- 1 root root 14 Nov 28 12:35 me
-rw-r--r-- 1 root root 10 Nov 28 12:35 plusdomain
-rw-r--r-- 1 root root 14 Nov 28 12:35 rcpthosts
/var/qmail/doc:
total 116
-rw-r--r-- 1 root qmail 23412 Nov 28 12:18 FAQ
-rw-r--r-- 1 root qmail 2534 Nov 28 12:18 INSTALL
-rw-r--r-- 1 root qmail 2049 Nov 28 12:18 INSTALL.alias
-rw-r--r-- 1 root qmail 1638 Nov 28 12:18 INSTALL.ctl
-rw-r--r-- 1 root qmail 2912 Nov 28 12:18 INSTALL.ids
-rw-r--r-- 1 root qmail 2475 Nov 28 12:18 INSTALL.maildir
-rw-r--r-- 1 root qmail 2420 Nov 28 12:18 INSTALL.mbox
-rw-r--r-- 1 root qmail 1849 Nov 28 12:18 INSTALL.vsm
-rw-r--r-- 1 root qmail 1272 Nov 28 12:18 PIC.local2alias
-rw-r--r-- 1 root qmail 1550 Nov 28 12:18 PIC.local2ext
-rw-r--r-- 1 root qmail 1447 Nov 28 12:18 PIC.local2local
-rw-r--r-- 1 root qmail 1265 Nov 28 12:18 PIC.local2rem
-rw-r--r-- 1 root qmail 1709 Nov 28 12:18 PIC.local2virt
-rw-r--r-- 1 root qmail 1297 Nov 28 12:18 PIC.nullclient
-rw-r--r-- 1 root qmail 300 Nov 28 12:18 PIC.relaybad
-rw-r--r-- 1 root qmail 1127 Nov 28 12:18 PIC.relaygood
-rw-r--r-- 1 root qmail 1333 Nov 28 12:18 PIC.rem2local
-rw-r--r-- 1 root qmail 552 Nov 28 12:18 REMOVE.binmail
-rw-r--r-- 1 root qmail 1278 Nov 28 12:18 REMOVE.sendmail
-rw-r--r-- 1 root qmail 3105 Nov 28 12:18 SENDMAIL
-rw-r--r-- 1 root qmail 3787 Nov 28 12:18 TEST.deliver
-rw-r--r-- 1 root qmail 1309 Nov 28 12:18 TEST.receive
-rw-r--r-- 1 root qmail 2469 Nov 28 12:18 UPGRADE
drwxr-xr-x 2 root root 4096 Nov 28 12:34 fastforward
/var/qmail/doc/fastforward:
total 4
-rw-r--r-- 1 root root 3079 Nov 28 12:34 ALIASES
/var/qmail/man:
total 32
drwxr-xr-x 2 root qmail 4096 Nov 28 12:35 cat1
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 cat5
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 cat7
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 cat8
drwxr-xr-x 2 root qmail 4096 Nov 28 12:35 man1
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 man5
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 man7
drwxr-xr-x 2 root qmail 4096 Nov 28 12:18 man8
/var/qmail/man/cat1:
total 96
-rw-r--r-- 1 root qmail 1658 Nov 28 12:18 bouncesaying.0
-rw-r--r-- 1 root qmail 1610 Nov 28 12:18 condredirect.0
-rw-r--r-- 1 root root 6880 Nov 28 12:35 dot-forward.0
-rw-r--r-- 1 root qmail 756 Nov 28 12:18 except.0
-rw-r--r-- 1 root root 3425 Nov 28 12:34 fastforward.0
-rw-r--r-- 1 root qmail 871 Nov 28 12:18 forward.0
-rw-r--r-- 1 root qmail 1520 Nov 28 12:18 maildir2mbox.0
-rw-r--r-- 1 root qmail 516 Nov 28 12:18 maildirmake.0
-rw-r--r-- 1 root qmail 827 Nov 28 12:18 maildirwatch.0
-rw-r--r-- 1 root qmail 901 Nov 28 12:18 mailsubj.0
-rw-r--r-- 1 root root 11007 Nov 28 12:34 newaliases.0
-rw-r--r-- 1 root root 2476 Nov 28 12:34 newinclude.0
-rw-r--r-- 1 root qmail 1536 Nov 28 12:18 preline.0
-rw-r--r-- 1 root root 697 Nov 28 12:34 printforward.0
-rw-r--r-- 1 root root 678 Nov 28 12:34 printmaillist.0
-rw-r--r-- 1 root qmail 811 Nov 28 12:18 qbiff.0
-rw-r--r-- 1 root qmail 1032 Nov 28 12:18 qreceipt.0
-rw-r--r-- 1 root root 6666 Nov 28 12:34 setforward.0
-rw-r--r-- 1 root root 2039 Nov 28 12:34 setmaillist.0
-rw-r--r-- 1 root qmail 1733 Nov 28 12:18 tcp-env.0
/var/qmail/man/cat5:
total 84
-rw-r--r-- 1 root qmail 8314 Nov 28 12:18 addresses.0
-rw-r--r-- 1 root qmail 11173 Nov 28 12:18 dot-qmail.0
-rw-r--r-- 1 root qmail 6456 Nov 28 12:18 envelopes.0
-rw-r--r-- 1 root qmail 7375 Nov 28 12:18 maildir.0
-rw-r--r-- 1 root qmail 6720 Nov 28 12:18 mbox.0
-rw-r--r-- 1 root qmail 3775 Nov 28 12:18 qmail-control.0
-rw-r--r-- 1 root qmail 8436 Nov 28 12:18 qmail-header.0
-rw-r--r-- 1 root qmail 10236 Nov 28 12:18 qmail-log.0
-rw-r--r-- 1 root qmail 3096 Nov 28 12:18 qmail-users.0
-rw-r--r-- 1 root qmail 1935 Nov 28 12:18 tcp-environ.0
/var/qmail/man/cat7:
total 12
-rw-r--r-- 1 root qmail 4077 Nov 28 12:18 forgeries.0
-rw-r--r-- 1 root qmail 1226 Nov 28 12:18 qmail-limits.0
-rw-r--r-- 1 root qmail 2126 Nov 28 12:18 qmail.0
/var/qmail/man/cat8:
total 136
-rw-r--r-- 1 root qmail 567 Nov 28 12:18 qmail-clean.0
-rw-r--r-- 1 root qmail 4172 Nov 28 12:18 qmail-command.0
-rw-r--r-- 1 root qmail 3118 Nov 28 12:18 qmail-getpw.0
-rw-r--r-- 1 root qmail 8934 Nov 28 12:18 qmail-inject.0
-rw-r--r-- 1 root qmail 2704 Nov 28 12:18 qmail-local.0
-rw-r--r-- 1 root qmail 1650 Nov 28 12:18 qmail-lspawn.0
-rw-r--r-- 1 root qmail 1704 Nov 28 12:18 qmail-newmrh.0
-rw-r--r-- 1 root qmail 1413 Nov 28 12:18 qmail-newu.0
-rw-r--r-- 1 root qmail 1387 Nov 28 12:18 qmail-pop3d.0
-rw-r--r-- 1 root qmail 2043 Nov 28 12:18 qmail-popup.0
-rw-r--r-- 1 root qmail 5230 Nov 28 12:18 qmail-pw2u.0
-rw-r--r-- 1 root qmail 1107 Nov 28 12:18 qmail-qmqpc.0
-rw-r--r-- 1 root qmail 990 Nov 28 12:18 qmail-qmqpd.0
-rw-r--r-- 1 root qmail 1141 Nov 28 12:18 qmail-qmtpd.0
-rw-r--r-- 1 root qmail 901 Nov 28 12:18 qmail-qread.0
-rw-r--r-- 1 root qmail 673 Nov 28 12:18 qmail-qstat.0
-rw-r--r-- 1 root qmail 4369 Nov 28 12:18 qmail-queue.0
-rw-r--r-- 1 root qmail 5897 Nov 28 12:18 qmail-remote.0
-rw-r--r-- 1 root qmail 824 Nov 28 12:18 qmail-rspawn.0
-rw-r--r-- 1 root qmail 8059 Nov 28 12:18 qmail-send.0
-rw-r--r-- 1 root qmail 514 Nov 28 12:18 qmail-showctl.0
-rw-r--r-- 1 root qmail 5905 Nov 28 12:18 qmail-smtpd.0
-rw-r--r-- 1 root qmail 2459 Nov 28 12:18 qmail-start.0
-rw-r--r-- 1 root qmail 790 Nov 28 12:18 qmail-tcpok.0
-rw-r--r-- 1 root qmail 1066 Nov 28 12:18 qmail-tcpto.0
-rw-r--r-- 1 root qmail 1502 Nov 28 12:18 splogger.0
/var/qmail/man/man1:
total 92
-rw-r--r-- 1 root qmail 1028 Nov 28 12:18 bouncesaying.1
-rw-r--r-- 1 root qmail 978 Nov 28 12:18 condredirect.1
-rw-r--r-- 1 root root 4540 Nov 28 12:35 dot-forward.1
-rw-r--r-- 1 root qmail 377 Nov 28 12:18 except.1
-rw-r--r-- 1 root root 2065 Nov 28 12:34 fastforward.1
-rw-r--r-- 1 root qmail 495 Nov 28 12:18 forward.1
-rw-r--r-- 1 root qmail 905 Nov 28 12:18 maildir2mbox.1
-rw-r--r-- 1 root qmail 224 Nov 28 12:18 maildirmake.1
-rw-r--r-- 1 root qmail 455 Nov 28 12:18 maildirwatch.1
-rw-r--r-- 1 root qmail 528 Nov 28 12:18 mailsubj.1
-rw-r--r-- 1 root root 7053 Nov 28 12:34 newaliases.1
-rw-r--r-- 1 root root 1570 Nov 28 12:34 newinclude.1
-rw-r--r-- 1 root qmail 907 Nov 28 12:18 preline.1
-rw-r--r-- 1 root root 367 Nov 28 12:34 printforward.1
-rw-r--r-- 1 root root 352 Nov 28 12:34 printmaillist.1
-rw-r--r-- 1 root qmail 484 Nov 28 12:18 qbiff.1
-rw-r--r-- 1 root qmail 585 Nov 28 12:18 qreceipt.1
-rw-r--r-- 1 root root 4591 Nov 28 12:34 setforward.1
-rw-r--r-- 1 root root 1394 Nov 28 12:34 setmaillist.1
-rw-r--r-- 1 root qmail 1064 Nov 28 12:18 tcp-env.1
/var/qmail/man/man5:
total 68
-rw-r--r-- 1 root qmail 6101 Nov 28 12:18 addresses.5
-rw-r--r-- 1 root qmail 7376 Nov 28 12:18 dot-qmail.5
-rw-r--r-- 1 root qmail 4847 Nov 28 12:18 envelopes.5
-rw-r--r-- 1 root qmail 5183 Nov 28 12:18 maildir.5
-rw-r--r-- 1 root qmail 4788 Nov 28 12:18 mbox.5
-rw-r--r-- 1 root qmail 1935 Nov 28 12:18 qmail-control.5
-rw-r--r-- 1 root qmail 5531 Nov 28 12:18 qmail-header.5
-rw-r--r-- 1 root qmail 5850 Nov 28 12:18 qmail-log.5
-rw-r--r-- 1 root qmail 2002 Nov 28 12:18 qmail-users.5
-rw-r--r-- 1 root qmail 1274 Nov 28 12:18 tcp-environ.5
/var/qmail/man/man7:
total 12
-rw-r--r-- 1 root qmail 2958 Nov 28 12:18 forgeries.7
-rw-r--r-- 1 root qmail 799 Nov 28 12:18 qmail-limits.7
-rw-r--r-- 1 root qmail 1252 Nov 28 12:18 qmail.7
/var/qmail/man/man8:
total 112
-rw-r--r-- 1 root qmail 273 Nov 28 12:18 qmail-clean.8
-rw-r--r-- 1 root qmail 2732 Nov 28 12:18 qmail-command.8
-rw-r--r-- 1 root qmail 2118 Nov 28 12:18 qmail-getpw.8
-rw-r--r-- 1 root qmail 5596 Nov 28 12:18 qmail-inject.8
-rw-r--r-- 1 root qmail 1697 Nov 28 12:18 qmail-local.8
-rw-r--r-- 1 root qmail 981 Nov 28 12:18 qmail-lspawn.8
-rw-r--r-- 1 root qmail 836 Nov 28 12:18 qmail-newmrh.8
-rw-r--r-- 1 root qmail 762 Nov 28 12:18 qmail-newu.8
-rw-r--r-- 1 root qmail 820 Nov 28 12:18 qmail-pop3d.8
-rw-r--r-- 1 root qmail 1382 Nov 28 12:18 qmail-popup.8
-rw-r--r-- 1 root qmail 3327 Nov 28 12:18 qmail-pw2u.8
-rw-r--r-- 1 root qmail 621 Nov 28 12:18 qmail-qmqpc.8
-rw-r--r-- 1 root qmail 558 Nov 28 12:18 qmail-qmqpd.8
-rw-r--r-- 1 root qmail 599 Nov 28 12:18 qmail-qmtpd.8
-rw-r--r-- 1 root qmail 539 Nov 28 12:18 qmail-qread.8
-rw-r--r-- 1 root qmail 347 Nov 28 12:18 qmail-qstat.8
-rw-r--r-- 1 root qmail 3064 Nov 28 12:18 qmail-queue.8
-rw-r--r-- 1 root qmail 3866 Nov 28 12:18 qmail-remote.8
-rw-r--r-- 1 root qmail 449 Nov 28 12:18 qmail-rspawn.8
-rw-r--r-- 1 root qmail 4871 Nov 28 12:18 qmail-send.8
-rw-r--r-- 1 root qmail 224 Nov 28 12:18 qmail-showctl.8
-rw-r--r-- 1 root qmail 3546 Nov 28 12:18 qmail-smtpd.8
-rw-r--r-- 1 root qmail 1533 Nov 28 12:18 qmail-start.8
-rw-r--r-- 1 root qmail 403 Nov 28 12:18 qmail-tcpok.8
-rw-r--r-- 1 root qmail 621 Nov 28 12:18 qmail-tcpto.8
-rw-r--r-- 1 root qmail 964 Nov 28 12:18 splogger.8
/var/qmail/queue:
total 36
drwx------ 2 qmails qmail 4096 Nov 28 12:18 bounce
drwx------ 25 qmails qmail 4096 Nov 28 12:18 info
drwx------ 2 qmailq qmail 4096 Nov 28 12:18 intd
drwx------ 25 qmails qmail 4096 Nov 28 12:18 local
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 lock
drwxr-x--- 25 qmailq qmail 4096 Nov 28 12:18 mess
drwx------ 2 qmailq qmail 4096 Nov 28 12:18 pid
drwx------ 25 qmails qmail 4096 Nov 28 12:18 remote
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 todo
/var/qmail/queue/bounce:
total 0
/var/qmail/queue/info:
total 92
drwx------ 2 qmails qmail 4096 Nov 28 12:18 0
drwx------ 2 qmails qmail 4096 Nov 28 12:18 1
drwx------ 2 qmails qmail 4096 Nov 28 12:18 10
drwx------ 2 qmails qmail 4096 Nov 28 12:18 11
drwx------ 2 qmails qmail 4096 Nov 28 12:18 12
drwx------ 2 qmails qmail 4096 Nov 28 12:18 13
drwx------ 2 qmails qmail 4096 Nov 28 12:18 14
drwx------ 2 qmails qmail 4096 Nov 28 12:18 15
drwx------ 2 qmails qmail 4096 Nov 28 12:18 16
drwx------ 2 qmails qmail 4096 Nov 28 12:18 17
drwx------ 2 qmails qmail 4096 Nov 28 12:18 18
drwx------ 2 qmails qmail 4096 Nov 28 12:18 19
drwx------ 2 qmails qmail 4096 Nov 28 12:18 2
drwx------ 2 qmails qmail 4096 Nov 28 12:18 20
drwx------ 2 qmails qmail 4096 Nov 28 12:18 21
drwx------ 2 qmails qmail 4096 Nov 28 12:18 22
drwx------ 2 qmails qmail 4096 Nov 28 12:18 3
drwx------ 2 qmails qmail 4096 Nov 28 12:18 4
drwx------ 2 qmails qmail 4096 Nov 28 12:18 5
drwx------ 2 qmails qmail 4096 Nov 28 12:18 6
drwx------ 2 qmails qmail 4096 Nov 28 12:18 7
drwx------ 2 qmails qmail 4096 Nov 28 12:18 8
drwx------ 2 qmails qmail 4096 Nov 28 12:18 9
/var/qmail/queue/info/0:
total 0
/var/qmail/queue/info/1:
total 0
/var/qmail/queue/info/10:
total 0
/var/qmail/queue/info/11:
total 0
/var/qmail/queue/info/12:
total 0
/var/qmail/queue/info/13:
total 0
/var/qmail/queue/info/14:
total 0
/var/qmail/queue/info/15:
total 0
/var/qmail/queue/info/16:
total 0
/var/qmail/queue/info/17:
total 0
/var/qmail/queue/info/18:
total 0
/var/qmail/queue/info/19:
total 0
/var/qmail/queue/info/2:
total 0
/var/qmail/queue/info/20:
total 0
/var/qmail/queue/info/21:
total 0
/var/qmail/queue/info/22:
total 0
/var/qmail/queue/info/3:
total 0
/var/qmail/queue/info/4:
total 0
/var/qmail/queue/info/5:
total 0
/var/qmail/queue/info/6:
total 0
/var/qmail/queue/info/7:
total 0
/var/qmail/queue/info/8:
total 0
/var/qmail/queue/info/9:
total 0
/var/qmail/queue/intd:
total 0
/var/qmail/queue/local:
total 92
drwx------ 2 qmails qmail 4096 Nov 28 12:18 0
drwx------ 2 qmails qmail 4096 Nov 28 12:18 1
drwx------ 2 qmails qmail 4096 Nov 28 12:18 10
drwx------ 2 qmails qmail 4096 Nov 28 12:18 11
drwx------ 2 qmails qmail 4096 Nov 28 12:18 12
drwx------ 2 qmails qmail 4096 Nov 28 12:18 13
drwx------ 2 qmails qmail 4096 Nov 28 12:18 14
drwx------ 2 qmails qmail 4096 Nov 28 12:18 15
drwx------ 2 qmails qmail 4096 Nov 28 12:18 16
drwx------ 2 qmails qmail 4096 Nov 28 12:18 17
drwx------ 2 qmails qmail 4096 Nov 28 12:18 18
drwx------ 2 qmails qmail 4096 Nov 28 12:18 19
drwx------ 2 qmails qmail 4096 Nov 28 12:18 2
drwx------ 2 qmails qmail 4096 Nov 28 12:18 20
drwx------ 2 qmails qmail 4096 Nov 28 12:18 21
drwx------ 2 qmails qmail 4096 Nov 28 12:18 22
drwx------ 2 qmails qmail 4096 Nov 28 12:18 3
drwx------ 2 qmails qmail 4096 Nov 28 12:18 4
drwx------ 2 qmails qmail 4096 Nov 28 12:18 5
drwx------ 2 qmails qmail 4096 Nov 28 12:18 6
drwx------ 2 qmails qmail 4096 Nov 28 12:18 7
drwx------ 2 qmails qmail 4096 Nov 28 12:18 8
drwx------ 2 qmails qmail 4096 Nov 28 12:18 9
/var/qmail/queue/local/0:
total 0
/var/qmail/queue/local/1:
total 0
/var/qmail/queue/local/10:
total 0
/var/qmail/queue/local/11:
total 0
/var/qmail/queue/local/12:
total 0
/var/qmail/queue/local/13:
total 0
/var/qmail/queue/local/14:
total 0
/var/qmail/queue/local/15:
total 0
/var/qmail/queue/local/16:
total 0
/var/qmail/queue/local/17:
total 0
/var/qmail/queue/local/18:
total 0
/var/qmail/queue/local/19:
total 0
/var/qmail/queue/local/2:
total 0
/var/qmail/queue/local/20:
total 0
/var/qmail/queue/local/21:
total 0
/var/qmail/queue/local/22:
total 0
/var/qmail/queue/local/3:
total 0
/var/qmail/queue/local/4:
total 0
/var/qmail/queue/local/5:
total 0
/var/qmail/queue/local/6:
total 0
/var/qmail/queue/local/7:
total 0
/var/qmail/queue/local/8:
total 0
/var/qmail/queue/local/9:
total 0
/var/qmail/queue/lock:
total 4
-rw------- 1 qmails qmail 0 Nov 28 12:18 sendmutex
-rw-r--r-- 1 qmailr qmail 1024 Nov 28 14:17 tcpto
prw--w--w- 1 qmails qmail 0 Nov 28 12:18 trigger
/var/qmail/queue/mess:
total 92
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 0
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 1
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 10
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 11
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 12
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 13
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 14
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 15
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 16
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 17
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 18
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 19
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 2
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 20
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 21
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 22
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 3
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 4
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 5
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 6
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 7
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 8
drwxr-x--- 2 qmailq qmail 4096 Nov 28 12:18 9
/var/qmail/queue/mess/0:
total 0
/var/qmail/queue/mess/1:
total 0
/var/qmail/queue/mess/10:
total 0
/var/qmail/queue/mess/11:
total 0
/var/qmail/queue/mess/12:
total 0
/var/qmail/queue/mess/13:
total 0
/var/qmail/queue/mess/14:
total 0
/var/qmail/queue/mess/15:
total 0
/var/qmail/queue/mess/16:
total 0
/var/qmail/queue/mess/17:
total 0
/var/qmail/queue/mess/18:
total 0
/var/qmail/queue/mess/19:
total 0
/var/qmail/queue/mess/2:
total 0
/var/qmail/queue/mess/20:
total 0
/var/qmail/queue/mess/21:
total 0
/var/qmail/queue/mess/22:
total 0
/var/qmail/queue/mess/3:
total 0
/var/qmail/queue/mess/4:
total 0
/var/qmail/queue/mess/5:
total 0
/var/qmail/queue/mess/6:
total 0
/var/qmail/queue/mess/7:
total 0
/var/qmail/queue/mess/8:
total 0
/var/qmail/queue/mess/9:
total 0
/var/qmail/queue/pid:
total 0
/var/qmail/queue/remote:
total 92
drwx------ 2 qmails qmail 4096 Nov 28 12:18 0
drwx------ 2 qmails qmail 4096 Nov 28 12:18 1
drwx------ 2 qmails qmail 4096 Nov 28 12:18 10
drwx------ 2 qmails qmail 4096 Nov 28 12:18 11
drwx------ 2 qmails qmail 4096 Nov 28 12:18 12
drwx------ 2 qmails qmail 4096 Nov 28 12:18 13
drwx------ 2 qmails qmail 4096 Nov 28 12:18 14
drwx------ 2 qmails qmail 4096 Nov 28 12:18 15
drwx------ 2 qmails qmail 4096 Nov 28 12:18 16
drwx------ 2 qmails qmail 4096 Nov 28 12:18 17
drwx------ 2 qmails qmail 4096 Nov 28 12:18 18
drwx------ 2 qmails qmail 4096 Nov 28 12:18 19
drwx------ 2 qmails qmail 4096 Nov 28 12:18 2
drwx------ 2 qmails qmail 4096 Nov 28 12:18 20
drwx------ 2 qmails qmail 4096 Nov 28 12:18 21
drwx------ 2 qmails qmail 4096 Nov 28 12:18 22
drwx------ 2 qmails qmail 4096 Nov 28 12:18 3
drwx------ 2 qmails qmail 4096 Nov 28 12:18 4
drwx------ 2 qmails qmail 4096 Nov 28 12:18 5
drwx------ 2 qmails qmail 4096 Nov 28 12:18 6
drwx------ 2 qmails qmail 4096 Nov 28 12:18 7
drwx------ 2 qmails qmail 4096 Nov 28 12:18 8
drwx------ 2 qmails qmail 4096 Nov 28 12:18 9
/var/qmail/queue/remote/0:
total 0
/var/qmail/queue/remote/1:
total 0
/var/qmail/queue/remote/10:
total 0
/var/qmail/queue/remote/11:
total 0
/var/qmail/queue/remote/12:
total 0
/var/qmail/queue/remote/13:
total 0
/var/qmail/queue/remote/14:
total 0
/var/qmail/queue/remote/15:
total 0
/var/qmail/queue/remote/16:
total 0
/var/qmail/queue/remote/17:
total 0
/var/qmail/queue/remote/18:
total 0
/var/qmail/queue/remote/19:
total 0
/var/qmail/queue/remote/2:
total 0
/var/qmail/queue/remote/20:
total 0
/var/qmail/queue/remote/21:
total 0
/var/qmail/queue/remote/22:
total 0
/var/qmail/queue/remote/3:
total 0
/var/qmail/queue/remote/4:
total 0
/var/qmail/queue/remote/5:
total 0
/var/qmail/queue/remote/6:
total 0
/var/qmail/queue/remote/7:
total 0
/var/qmail/queue/remote/8:
total 0
/var/qmail/queue/remote/9:
total 0
/var/qmail/queue/todo:
total 0
/var/qmail/supervise:
total 8
drwxr-xr-t 3 root root 4096 Nov 28 14:04 qmail-send
drwxr-xr-t 3 root root 4096 Nov 28 14:05 qmail-smtpd
/var/qmail/supervise/qmail-send:
total 8
drwxr-xr-x 2 root root 4096 Nov 28 13:09 log
-rwxr-xr-x 1 root root 28 Nov 28 13:07 run
/var/qmail/supervise/qmail-send/log:
total 4
-rwxr-xr-x 1 root root 108 Nov 28 13:09 run
/var/qmail/supervise/qmail-smtpd:
total 8
drwxr-xr-x 2 root root 4096 Nov 28 13:10 log
-rwxr-xr-x 1 root root 263 Nov 28 13:12 run
/var/qmail/supervise/qmail-smtpd/log:
total 4
-rwxr-xr-x 1 root root 108 Nov 28 13:10 run
/var/qmail/users:
total 0
It looks like you haven't started the supervise process.
The svc command is looking for files in the
/var/qmail/supervise/qmail-send/suervise directory and they only get
created when the supervise process is running.
Check your startup scripts to ensure that supervise is started prior
to issuing the svc commands.
Regards.
On Tue, Nov 28, 2000 at 03:52:12PM -0500, Silberman, Malcolm (BHR) wrote:
>
> I have attched the output of ls -lR /var/qmail
>
> hope it helps, thanks for your help!
>
> Regards
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 28, 2000 3:06 PM
> To: QMail Mailing List
> Subject: Re: unable to control /var/qmail/supervise/qmail-send
>
>
> On Tue, Nov 28, 2000 at 02:34:37PM -0500, Silberman, Malcolm (BHR) wrote:
> > I have installed Qmail a few times on Mandrake OS, and it worked fine. I
> go
> > exactly according to Qmail how to by Adam McKenna. Now I tried to install
> on
> > RedHat7 (and posted ome questions last week). I cameup with a dead end, so
> > droped down to 6.2, but still I getthe following;
> > svc: warning: unable to control /var/qmail/supervise/qmail-send: file does
> > not exist
> >
> > svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file
> does
> > not exist
> > qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
> > file does not exist
> > svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
> > does not exist
> > logging.
>
> Post the output of: ls -lR /var/qmail
>
>
> Regards.
>
>
>
>
> This e-mail and any files transmitted with it are intended for, and should only be
>read by, the intended addressee. Its contents are confidential and if you are not
>the intended addressee, please notify the sender immediately and delete all records
>of the message from your computer. Any reproduction, dissemination, copying,
>disclosure, modification, distribution and/or publication of this message without the
>prior written consent of the sender are strictly prohibited. The contents of this
>communication represent the sender's personal views and opinions, which do not
>necessarily reflect those of Bass Hotels & Resorts, Inc.
> Starting mail-transport-agent:svc: warning: unable to control
>/var/qmail/supervise/qmail-send: file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file does not exist
> qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log: file does
>not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file does not
>exist
> logging.
* "Silberman, Malcolm \(BHR\)" <[EMAIL PROTECTED]>
> I have installed Qmail a few times on Mandrake OS, and it worked
> fine. I go exactly according to Qmail how to by Adam McKenna. Now I
> tried to install on RedHat7 (and posted ome questions last week). I
> cameup with a dead end, so droped down to 6.2, but still I get the
> following; svc: warning: unable to control
> /var/qmail/supervise/qmail-send: file does not exist
Well, this is pretty obvious, isn't it? Trace back your steps through
Adam's document and you'll find the error. Oh. And get qmail-conf. Just
do it. Don't bitch, don't argue: grab it at
<http://pobox.com/~tu/qmail-conf.html>.
> This e-mail and any files transmitted with it are intended for, and
> should only be read by, the intended addressee.
Oh. Sorry for that.
> Its contents are confidential and if you are not the intended addressee,
> please notify the sender immediately and delete all records of the message
> from your computer.
Hmmmm... Damn! *clicketyclick* Ok.
> Any reproduction, dissemination, copying, disclosure, modification,
> distribution and/or publication of this message without the prior
> written consent of the sender are strictly prohibited.
Are you going to sue me for answering on the list?
> The contents of this communication represent the sender's personal
> views and opinions, which do not necessarily reflect those of Bass
> Hotels & Resorts, Inc.
Don't take it personally, Silberman, Malcom \(BHR\), but this kinda
pisses me off. But maybe my irony detector is broken.
--
Robin S. Socha <http://socha.net/>
PGP signature
I feel like an idiot, went back and checked my scripts and had the qmail
script in the svscan script. Thanks Mark for pointing the direction.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 28, 2000 4:01 PM
To: QMail Mailing List
Subject: Re: unable to control /var/qmail/supervise/qmail-send
It looks like you haven't started the supervise process.
The svc command is looking for files in the
/var/qmail/supervise/qmail-send/suervise directory and they only get
created when the supervise process is running.
Check your startup scripts to ensure that supervise is started prior
to issuing the svc commands.
Regards.
On Tue, Nov 28, 2000 at 03:52:12PM -0500, Silberman, Malcolm (BHR) wrote:
>
> I have attched the output of ls -lR /var/qmail
>
> hope it helps, thanks for your help!
>
> Regards
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 28, 2000 3:06 PM
> To: QMail Mailing List
> Subject: Re: unable to control /var/qmail/supervise/qmail-send
>
>
> On Tue, Nov 28, 2000 at 02:34:37PM -0500, Silberman, Malcolm (BHR) wrote:
> > I have installed Qmail a few times on Mandrake OS, and it worked fine. I
> go
> > exactly according to Qmail how to by Adam McKenna. Now I tried to
install
> on
> > RedHat7 (and posted ome questions last week). I cameup with a dead end,
so
> > droped down to 6.2, but still I getthe following;
> > svc: warning: unable to control /var/qmail/supervise/qmail-send: file
does
> > not exist
> >
> > svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file
> does
> > not exist
> > qmailsvc: warning: unable to control
/var/qmail/supervise/qmail-send/log:
> > file does not exist
> > svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log:
file
> > does not exist
> > logging.
>
> Post the output of: ls -lR /var/qmail
>
>
> Regards.
>
>
>
>
> This e-mail and any files transmitted with it are intended for, and should
only be read by, the intended addressee. Its contents are confidential and
if you are not the intended addressee, please notify the sender immediately
and delete all records of the message from your computer. Any reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this message without the prior written consent of the sender
are strictly prohibited. The contents of this communication represent the
sender's personal views and opinions, which do not necessarily reflect those
of Bass Hotels & Resorts, Inc.
> Starting mail-transport-agent:svc: warning: unable to control
/var/qmail/supervise/qmail-send: file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd: file
does not exist
> qmailsvc: warning: unable to control /var/qmail/supervise/qmail-send/log:
file does not exist
> svc: warning: unable to control /var/qmail/supervise/qmail-smtpd/log: file
does not exist
> logging.
This e-mail and any files transmitted with it are intended for, and should only be
read by, the intended addressee. Its contents are confidential and if you are not the
intended addressee, please notify the sender immediately and delete all records of the
message from your computer. Any reproduction, dissemination, copying, disclosure,
modification, distribution and/or publication of this message without the prior
written consent of the sender are strictly prohibited. The contents of this
communication represent the sender's personal views and opinions, which do not
necessarily reflect those of Bass Hotels & Resorts, Inc.
I have qmail running on a Debian Linux box, and hopefully someone can
clarify for me how qmail is supposed to handle it's logging processes.
I find log directories in /var/log/qmail and I would assume this is
where qmail is supposed to do it's logging. However, after some
searching, I find /var/log/mail/mail.info, and this mail.info file
appears to accumulate and log all the activities of the server including
startup time, SMTP connections from remote hosts, POP connections, etc.
I don't think this is the way the logging is supposed to work, after
studying the qmail documentation.
Is it possible I have a 'bastard' installation of qmail? By that I mean
that Corel (Debian) Linux Server Version was loaded into this box and
qmail was installed with the Linux installation. The more I work with
this system the more I suspect that there's been some custom settings
made to qmail by whoever wrote the Corel distribution of Linux. So I'm
asking if someone can tell me if this /var/log/mail/mail.info file is a
normal file for qmail to generate during it's logging processes?
Thanks much,
------------------------------------------------
Chris Olson
My Personal Webpage http://www.astcomm.net/chris
I've been told unix is user-friendly. It's just
very choosey about who it's friends are.
------------------------------------------------
Hi!
I'm getting stuff like this in my logs:
Nov 28 22:16:09 sol qmail: 975446169.345287 warning: trouble marking
remote/9/96701; message will be delivered twice!
Nov 28 22:16:09 sol qmail: 975446169.347416 delivery 8796: deferral:
qmail-spawn_unable_to_create_pipe._(#4.3.0)/
This seems to mean trouble. What else does it mean?
-Johan
--
Johan Almqvist
On Tue, Nov 28, 2000 at 10:22:02PM +0100, Johan Almqvist wrote:
> Hi!
>
> I'm getting stuff like this in my logs:
>
> Nov 28 22:16:09 sol qmail: 975446169.345287 warning: trouble marking
> remote/9/96701; message will be delivered twice!
> Nov 28 22:16:09 sol qmail: 975446169.347416 delivery 8796: deferral:
> qmail-spawn_unable_to_create_pipe._(#4.3.0)/
>
> This seems to mean trouble. What else does it mean?
Apart from trouble? Nothing.
Seriously, you have some serious resource and permission problems. Tell
us more about the installation. Is it new? How did you do it? Which instructions
did you follow? Has this mail system ever been running? What has changed recently?
Any change of permissions, moving of directories, backup/restores? How do you start
qmail?
I suspect that the permission settings in /var/qmail differ from the ones set
by a standard qmail install. I also suspect that the limits inherited by
qmail-start need to be increased.
Regards.
On Tue, Nov 28, 2000 at 12:50:58PM -0800, [EMAIL PROTECTED] wrote:
> > It may have to do with too little memory (I use qmail-scanner, and a lot
> > of other stuff runs on this machine with 32 megs of RAM). It may be the
> > case that this only happens when I put extra load on the machine, I'll
> > look into that.
> I'd be surprised. Just because a server is overloaded doesn't mean
> that permissions start acting differently. But certainly the "cannot
> create pipe" *may* be that too many processes are consuming all system
> limited resources. That can be changed, but it is OS dependent.
>
> > > I suspect that the permission settings in /var/qmail differ from the ones set
> > > by a standard qmail install. I also suspect that the limits inherited by
> > > qmail-start need to be increased.
> > Okay, I will check the perms (done. they were okay, it seems...) and
> How did you check?
i "ls -l'd" around a bit.
I also ran queue-fix (with patch for big-todo because of RPMs) from the
qmail homepage.
-Johan
--
Johan Almqvist
Hello,
Suppose I have two domaines (mymachine1.example1.com and
mymachine2.example2.com) each having it's intenet-IP and
mail server.
example1.com use qmail server, how I can tell qmail to get
all mails of example2.com mail server and sending them for
destinated users on my LAN?
Thanks
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
|
Hi
I have a system where domains/mail is added to
files, no mysql databases.
Would it be difficult, or problematic to allow a
customer to use 1 000 pop3 email accounts ?
Any advice is appriciated!
Are Haugsdal
|
On Tue, 28 Nov 2000, Are Haugsdal wrote:
> Hi
>
> I have a system where domains/mail is added to files, no mysql databases.
>
> Would it be difficult, or problematic to allow a customer to use 1 000
> pop3 email accounts ?
>
> Any advice is appriciated!
If you use the vpopmail-package from inter7, you can have all the
authentication information in cdbs, which should make it more scalable
than flat files.
(If not, then, well, why not? ;) )
Thorkild
Ben Beuchler writes:
> I know the book topic has been beat to death (something like 575
> messages in the archives) but Amazon claims that it will be
> available next month. Nothing at all appears on the O'Reilly site
> except for the old "Ask Tim" columns from 1998.
>
>
>http://www.amazon.com/exec/obidos/ASIN/1565926285/qid=975305593/sr=1-4/102-8514671-6796143
> Russ? John?
Only if they've given up on us and contracted with someone else
without telling us.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | The best way to help the poor
521 Pleasant Valley Rd. | +1 315 268 1925 voice | is to help the rich build
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | up their capital.
Piotr Kasztelowicz writes:
> Qmail is one MTA only, which suports and propagates ORBS "moral"
Who does this? Not me. If anybody asks about ORBS, I tell them not
to use it.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | The best way to help the poor
521 Pleasant Valley Rd. | +1 315 268 1925 voice | is to help the rich build
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | up their capital.
Hello
> Who does this? Not me. If anybody asks about ORBS, I tell them not
> to use it.
OK :-), Sorry if you have take my remarks personal. I had many problems
with ORBS and will say that negative results of its activity should
be streng said. If you are this same opinion as I - OK, thank you
Best Wishes from Torun
Piotr
---
Piotr Kasztelowicz <[EMAIL PROTECTED]>
[http://www.am.torun.pl/~pekasz]
Hello everyone!
Im sorry if this question has been asked 100000 times and im #
100001..
I admin quite a large mail server that is currently running
sendmail/qpopper, it has about 60000 accounts on it currently. I know
that UNIX has a limit on the UID's of 65534, any file that has a UID
higher than that number defaults back to UID0..
I hoped to solve this problem by upgrading to Qmail+its popper program
and use MySQL to authenicate both. I would move (via long scripts and
perl :) /var/spool/mail/<uname> to hashed home directories
/var/spool/mail/a/a<uname>, /var/spool/mail/b/b<uname>, etc, etc.. to
get rid of that nasty problem when a unix file system as too many
files/directories in one main directory.
I have read the MySQL patch, and from what I understand, the user
accounts still need a UID in the MySQL database, as well as their home
directories need to be owned by the UID assigned to them in MySQL...
Now if the OS has a limit of 65534 UID's how can I fit more than that
on one machine (actually its two machines, a smtp and pop3 with the
mail spools mounted to pop3 over NFS)?
My question now, How can I use MySQL to overcome this 65534 ceiling
with Qmail? Will assigning them all the same UID solve this problem?
I know that some *VERY* large e-mail servers run this program and I
would like to know how they manage to house so many people when you
can only have 65k users due to the OS constraints. Show me oh wise
ones of Qmail <bowing>.. Just so you all know, being a Sendmail geek
migrating to Qmail, I find qmail to have a greater learning curve to
setup (which isnt that much) but is 10000000x better in the long run..
:)
Frank
-=-=-=-=-=-8<-=-=-=-=-=-
'I sense much NT in you. NT leads to blue screen, blue screen leads to
downtime, downtime leads to much suffering.' --- unknown linux jedi
http://www.vadept.com/pgp-public.txt
On Tue, Nov 28, 2000 at 07:48:47PM -0800, [EMAIL PROTECTED] wrote:
>that UNIX has a limit on the UID's of 65534, any file that has a UID
>higher than that number defaults back to UID0..
Actually, it's more like they get UID%65534, but it's a similar result ;-)
>I have read the MySQL patch, and from what I understand, the user
>accounts still need a UID in the MySQL database, as well as their home
>directories need to be owned by the UID assigned to them in MySQL...
Yes, it needs *A* UID, doesn't say it needs a *UNIQUE* ID. I set up
a similar system using my own checkpoppasswd (I can provide it if you
like, it's written in Python) which uses the hashed directories and
stores all the data under one user-id. Works great, especially over
NFS, because the passwords are in the user home directory, so they
get distributed via NFS as well. No need to sync /etc/passwd between
machines.
The other alternative is to use something like vpopmail or vmailmgr.
Sean
--
When the law supports you, pound the law. When the facts support you, pound
the facts. If neither, pound the table. Bush supporters are rioting...
Sean Reifschneider, Inimitably Superfluous <[EMAIL PROTECTED]>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
Am Mittwoch, 29. November 2000 04:48 schrieb [EMAIL PROTECTED]:
...
> I admin quite a large mail server that is currently running
> sendmail/qpopper, it has about 60000 accounts on it currently. I know
> that UNIX has a limit on the UID's of 65534, any file that has a UID
> higher than that number defaults back to UID0..
> I hoped to solve this problem by upgrading to Qmail+its popper program
> and use MySQL to authenicate both. I would move (via long scripts and
> perl :) /var/spool/mail/<uname> to hashed home directories
> /var/spool/mail/a/a<uname>, /var/spool/mail/b/b<uname>, etc, etc.. to
> get rid of that nasty problem when a unix file system as too many
> files/directories in one main directory.
You should have a look to qmail-ldap, it's designed for such environments.
You should also consider upgrading to maildirs instead of mailboxes, it's
really worth the work.
qmail-ldap runs great, really fast and rock-solid. Builtin cluster support
might be interesting too... oh, quota support is also builtin ;-))
url is http://diehard.n-r-g.com . Documentation is a bit poor at the moment,
but this may be solved soon ;-)).
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
Greg White writes:
> Paul Jarc wrote:
> > Dan's software isn't open source.
>
> Oh, really? By whose definition?
By the Open Source Initiative's, the vice-president of which is yours
truly. It's okay if you don't believe us when we say it's not Open
Source, but you'll find yourself in a small minority (dare I call them
fanatics?)
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | The best way to help the poor
521 Pleasant Valley Rd. | +1 315 268 1925 voice | is to help the rich build
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | up their capital.
Hi
I have installed qmail-ldap patch,whenever i start the qmail ,i get this
info
I have made a file in the control folder and i tried by entering the ip
address as well as by the dns name
i am not able start the debug process even after i set the env variable ,Is
there any particular syntax i should be calling qmail-start for this?
bash-2.03# Nov 29 11:11:21 qmailjol qmail: [ID 748625 mail.alert]
975467481.7424
69 alert: cannot start qmail-lspawn or it had an error! Check if
~control/ldapse
rver exists
Suresh
Mithi.com Pvt. Ltd.
------------------------------------------
Send and receive mail in Indian languages
Register free at http://www.mailjol.com
Suresh
Mithi.com Pvt. Ltd.
------------------------------------------
Send and receive mail in Indian languages
Register free at http://www.mailjol.com
Am Mittwoch, 29. November 2000 13:24 schrieb suresh:
> Hi
> I have installed qmail-ldap patch
You posted this on qmail-ldap's list, there it is right. Here it is false. No
one can and will answer your question here.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
PLEASE DO NOT READ NEWBIE QUESTION IF WANT TO USE THOSE DEROGATORY
STATEMENTS .YU DONT EVEN HELP EITHER .I AM SURE THERE ARE OTHER PEOPLE WHO
WOULD LIKE TO HELP!
-----Original Message-----
From: Henning Brauer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 6:55 AM
To: suresh; Qmail-Ldap@Argus. Pipeline. Ch
Subject: Re: Newbie question
Am Mittwoch, 29. November 2000 13:24 schrieb suresh:
You are giving us much to less infos to help you. Check if the file
mentioned
in the error message exists and is world readable. If not, RTFM before
asking
here.
> Hi
> I have installed qmail-ldap patch,whenever i start the qmail ,i get this
> info
> I have made a file in the control folder and i tried by entering the ip
> address as well as by the dns name
> i am not able start the debug process even after i set the env variable
,Is
> there any particular syntax i should be calling qmail-start for this?
>
>
> bash-2.03# Nov 29 11:11:21 qmailjol qmail: [ID 748625 mail.alert]
> 975467481.7424
> 69 alert: cannot start qmail-lspawn or it had an error! Check if
> ~control/ldapse
> rver exists
>
> Suresh
> Mithi.com Pvt. Ltd.
> ------------------------------------------
> Send and receive mail in Indian languages
> Register free at http://www.mailjol.com
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
Am Mittwoch, 29. November 2000 15:11 schrieb suresh:
Suresh, for first writing such nonsens to the list and asking me for help off
list does not fit together. before asking other busy people for help (it is
no paid support staff here, we all have our work to do!), you should
-have read the docs at least twice
-checked if you fulfilled the requirements for qmail-ldap, both on you
installation and youself (yes, the wonderfull sentence "you should have
fairly good knowledge of qmail and ldap..." and so on in bold letters aside
to the dowload link on the wepages
-if you ask a question, provide all necessary information, in general as much
as possible. At least OS, versions (including patch version), _complete_
logs, configuration
-checked all logs yourself, including ldap logs, set loglevel to highest
possible value - helps a lot
> PLEASE DO NOT READ NEWBIE QUESTION IF WANT TO USE THOSE DEROGATORY
> STATEMENTS .YU DONT EVEN HELP EITHER .I AM SURE THERE ARE OTHER PEOPLE WHO
> WOULD LIKE TO HELP!
> -----Original Message-----
> From: Henning Brauer [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 29, 2000 6:55 AM
> To: suresh; Qmail-Ldap@Argus. Pipeline. Ch
> Subject: Re: Newbie question
>
>
> Am Mittwoch, 29. November 2000 13:24 schrieb suresh:
>
> You are giving us much to less infos to help you. Check if the file
> mentioned
> in the error message exists and is world readable. If not, RTFM before
> asking
> here.
>
> > Hi
> > I have installed qmail-ldap patch,whenever i start the qmail ,i get this
> > info
> > I have made a file in the control folder and i tried by entering the ip
> > address as well as by the dns name
> > i am not able start the debug process even after i set the env variable
>
> ,Is
>
> > there any particular syntax i should be calling qmail-start for this?
> >
> >
> > bash-2.03# Nov 29 11:11:21 qmailjol qmail: [ID 748625 mail.alert]
> > 975467481.7424
> > 69 alert: cannot start qmail-lspawn or it had an error! Check if
> > ~control/ldapse
> > rver exists
> >
> > Suresh
> > Mithi.com Pvt. Ltd.
> > ------------------------------------------
> > Send and receive mail in Indian languages
> > Register free at http://www.mailjol.com
>
> --
>
> Henning Brauer | BS Web Services
> Hostmaster BSWS | Roedingsmarkt 14
> [EMAIL PROTECTED] | 20459 Hamburg
> www.bsws.de | Germany
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
Before you dump this mail message to /dev/null, I have a relaying
question..
I setup the anti-relaying rules all fine and dandy according to the FAQ
with tcpserver.. Everything works fine, *but* i need the ability to filter
by DNS hostmask and IP address.. I tried the following test:
This setup works:
209.142.1.150:allow,RELAYCLIENT=""
:allow
This setup does NOT work:
vadept.com:allow,RELAYCLIENT=""
:allow
I need the ability to just wildcard IP's based upon their DNS lookup, I
know I can enable paranoid mode to cut down on the spoofing, but will the
current anti-relaying rules support a *.vadept.com rather than about
150-200 class C's?
Saves me a lot of keystrokes, plus if we forget to reverse map an IP pool,
the phones dont light up (with paranoid mode off)... :(
Thanks!
Frank
-=-=-=-=-=-8<-=-=-=-=-=-
'I sense much NT in you. NT leads to blue screen, blue screen leads to
downtime, downtime leads to much suffering.' --- unknown linux jedi
http://www.vadept.com/pgp-public.txt
On Tue, Nov 28, 2000 at 11:12:45PM -0800, [EMAIL PROTECTED] wrote:
> I setup the anti-relaying rules all fine and dandy according to the FAQ
> with tcpserver.. Everything works fine, *but* i need the ability to filter
> by DNS hostmask and IP address.. I tried the following test:
>
> This setup works:
>
> 209.142.1.150:allow,RELAYCLIENT=""
> :allow
>
> This setup does NOT work:
> vadept.com:allow,RELAYCLIENT=""
> :allow
>
> I need the ability to just wildcard IP's based upon their DNS lookup, I
> know I can enable paranoid mode to cut down on the spoofing, but will the
> current anti-relaying rules support a *.vadept.com rather than about
> 150-200 class C's?
Presume your tcpserver invocation is simple:
tcpserver 0 smtp qmail-smtpd
Insert a call to a script like so:
tcpserver 0 smtp shouldirelay qmail-smtpd.
Create a script "shouldirelay" that does two things:
1. Uses ucspi-tcp environment variables to decide if RELAYCLIENT
should be set. man tcp-environ for details.
2. execs the arguments in $@.
PGP signature
hii
i write an qmail log analyzer in PERL
here is description:
IsoQlog is a qmail log analysis program written in Perl. It is
designed to scan qmail logfiles and produce usage statistics in HTML
format for viewing through a Web
browser. It produces top domains output according to incoming,
outgoing, and total mails. It maintains your main domain mail statistics
per day and per month, like webalizer.
it is under GPL licences
if you interest you can get it from
http://www.students.itu.edu.tr/~yenigul
thanx
bye
