qmail Digest 23 Feb 2001 11:00:01 -0000 Issue 1284
Topics (messages 57766 through 57824):
about qmailadmin
57766 by: Someone
about quota for qmail
57767 by: Someone
Re: LWQ & OpenBSD
57768 by: Henning Brauer
57773 by: Dave Sill
57774 by: Henning Brauer
57780 by: Robin S. Socha
57781 by: Dave Sill
57784 by: Dave Sill
57788 by: Robin S. Socha
57789 by: Henning Brauer
57803 by: Dave Sill
57806 by: Dave Sill
Patching error with qmail-smtpd
57769 by: John P
57778 by: Charles Cazabon
SMTP-AUTH problems
57770 by: John P
57790 by: Kris Kelley
57792 by: John P
57794 by: Kris Kelley
57808 by: listy-dyskusyjne Krzysztof Dabrowski
Re: qmail-scanner wrapper
57771 by: Brett Randall
57772 by: John P
57796 by: Jason Haar
Re: Slow connection on send & Server connection closed
57775 by: Dave Sill
Re: warning: trouble opening remote/4/r
57776 by: Charles Cazabon
57819 by: flint
57820 by: flint
Re: mail queue problem.
57777 by: Charles Cazabon
57816 by: Manvendra Bhangui
long delay in receiving from HOTMAIL, routing problem?
57779 by: Chrisanthy Chrisanthy
57782 by: Jonathan D. Poole
qmail-qfilter ~ Help...
57783 by: jsunday.parview.com
Where to ask ezmlm-idx questions?
57785 by: nolan.celery.tssi.com
57787 by: Jonathan D. Poole
Re: qmail test scripts
57786 by: Dave Sill
autorespond
57791 by: Mark Lane
yay
57793 by: Carl
qmail-pop3d: tcpserver: unable to bind: address in use problem
57795 by: schoon.amgt.com
57798 by: Charles Cazabon
57799 by: schoon.amgt.com
57801 by: Greg White
Qmail-Scanner for each user
57797 by: Alan R.
thinko
57800 by: Charles Cazabon
newbie question on forwarding email
57802 by: Virginia Chism
57804 by: Charles Cazabon
forward and keep mail....
57805 by: Javier Morquecho Morquecho
57807 by: Charles Cazabon
Newbies tcpserver question [slightly offtopic]
57809 by: John Peterson
57810 by: Kris Kelley
unsubsribe
57811 by: wheatly
LWQ & qmail-smtp-auth
57812 by: dennis
how can i change from inetd to xinetd in Redhat 7.0??
57813 by: jerry
57814 by: Peter Cavender
pam-checkpassword .diff ?
57815 by: dennis
qmailadmin compile question
57817 by: sberg.white.pangaealink.com
CNAME problem with qmail and djbdns
57818 by: Marcus Korte
Mysterious error message
57821 by: Tim Hassan
Virtual Domain Quota
57822 by: Eko Yulianto
57823 by: Frank Tegtmeyer
About qmail & sendmail.
57824 by: Someone
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]
----------------------------------------------------------------------
|
Hi all
If i use qmailadmin but not use vpopmail.
Can i do it ?
How?
Thank you
someone
|
|
Hi, all
If i not use vpopmail.
Can i set quota for user in /etc/passwd ?
How ?
Thank you
someone
|
On Wed, Feb 21, 2001 at 11:46:26AM -0800, Rick Updegrove wrote:
> Since I do not have a init.d directory in OpenBSD and it seems everything is
> started from rc.conf and rc.local in OpenBSD how am I to follow LWQ?
The lack of the complicated sysv-style init and its dependencies is a big
advantage for OpenBSD ;-))
Just enter
PATH=$PATH:/usr/local/bin
svscan /service &
in your /etc/rc.local
Greetings
Henning
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Henning Brauer <[EMAIL PROTECTED]> wrote:
>Just enter
>
>PATH=$PATH:/usr/local/bin
>svscan /service &
>
>in your /etc/rc.local
Since we're talking about LWQ, that would have to be "svscan
/var/qmail/supervise &". But putting:
/usr/local/sbin/qmail start
in rc.local is the correct approach.
-Dave
On Thu, Feb 22, 2001 at 09:24:04AM -0500, Dave Sill wrote:
> Henning Brauer <[EMAIL PROTECTED]> wrote:
>
> >Just enter
> >
> >PATH=$PATH:/usr/local/bin
> >svscan /service &
> >
> >in your /etc/rc.local
>
> Since we're talking about LWQ, that would have to be "svscan
> /var/qmail/supervise &". But putting:
>
> /usr/local/sbin/qmail start
>
> in rc.local is the correct approach.
Sorry Dave, but having such a beast like the sysv-init-script for qmail on
OpenBSD is definetly not the correct approach. Thats against any BSD
concept, especially the OpenBSD concept. Just (soft-)link you stuff from
/var/qmail/supervise to /service and use the lines as I typed them.
For my taste lwq is a bit too linux-specific. Don't tell people to use
sysv-sytle init scripts on non-sysv-init-systems. Thats confusing.
> -Dave
>
Greetings
Henning
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
* Henning Brauer <[EMAIL PROTECTED]> [010222 09:36]:
> On Thu, Feb 22, 2001 at 09:24:04AM -0500, Dave Sill wrote:
> > Since we're talking about LWQ, that would have to be "svscan
> > /var/qmail/supervise &". But putting:
> >
> > /usr/local/sbin/qmail start
> >
> > in rc.local is the correct approach.
>
> Sorry Dave, but having such a beast like the sysv-init-script for qmail on
> OpenBSD is definetly not the correct approach. Thats against any BSD
> concept, especially the OpenBSD concept. Just (soft-)link you stuff from
> /var/qmail/supervise to /service and use the lines as I typed them.
Also, putting init scripts in /usr/local does not make any sense at all
(unless you happen to own an Lintendo) - cf. DJB's explation of why he
chose /var.
> For my taste lwq is a bit too linux-specific. Don't tell people to use
> sysv-sytle init scripts on non-sysv-init-systems. Thats confusing.
I find it quite interesting that although DJB himself uses OpenBSD, none
of the 3rd party docs deal with it (adding users and groups is certainly
different from even FreeBSD). Mind you, this is not a critique of LWQ:
great piece of documentation. Rather, it's a suggestion for a possible
enhancement. Add to that a section about SysV under SuSE Linux as
described by Erwin Hoffmann.
Henning Brauer <[EMAIL PROTECTED]> wrote:
>Sorry Dave, but having such a beast like the sysv-init-script for qmail on
>OpenBSD is definetly not the correct approach. Thats against any BSD
>concept, especially the OpenBSD concept.
Nonsense. The "qmail" script from LWQ is compatible with the System V
init script mechanism, but it's also perfectly compatible with BSD and
generally useful on all UNIX flavors as a qmail control
interface. Maybe I should rename it qmailctl a la apachectl or
ctlqmail a la ctlinnd...
>For my taste lwq is a bit too linux-specific. Don't tell people to use
>sysv-sytle init scripts on non-sysv-init-systems. Thats confusing.
Granted, I should add a note about adding:
if [ -x /usr/local/sbin/qmail ]; then
/usr/local/sbin/qmail start
fi
to rc.local for BSD variants, but I have no Linux bias. I've been
managing both BSD and Sys V machines for more than 12 years.
-Dave
"Robin S. Socha" <[EMAIL PROTECTED]> wrote:
>Also, putting init scripts in /usr/local does not make any sense at all
I've been putting stuff in /usr/local for at least a decade. I'm not
going to stop just because some upstart free OS's want to impose their
idea of the One True Filesystem Hierarchy on me.
>(unless you happen to own an Lintendo)
Cute, but I'd rather support fellow UNIX-like OS users than degrade
them. Save the namecalling for Wintendo lusers. :-)
>- cf. DJB's explation of why he chose /var.
Which is where?
-Dave
* Dave Sill <[EMAIL PROTECTED]> [010222 10:41]:
> "Robin S. Socha" <[EMAIL PROTECTED]> wrote:
>
> >Also, putting init scripts in /usr/local does not make any sense at all
> I've been putting stuff in /usr/local for at least a decade. I'm not
> going to stop just because some upstart free OS's want to impose their
> idea of the One True Filesystem Hierarchy on me.
man hier should be a lot older than OpenBSD or whatever. I mean, really.
And system components (I consider an MTA a system component, don't you?)
don't belong under /something/local but /something - cf. NFS.
> >(unless you happen to own an Lintendo)
> Cute, but I'd rather support fellow UNIX-like OS users than degrade
> them. Save the namecalling for Wintendo lusers. :-)
I was in fact referring to desktop boxes (usually running Linux, not
some flavour of BSD).
> >-cf. DJB's explation of why he chose /var.
>
> Which is where?
http://cr.yp.to/compatibility.html
http://cr.yp.to/qmail/faq/install.html#whyvar
I'm shocked ;-)
On Thu, Feb 22, 2001 at 10:00:46AM -0500, Dave Sill wrote:
> Henning Brauer <[EMAIL PROTECTED]> wrote:
> >Sorry Dave, but having such a beast like the sysv-init-script for qmail on
> >OpenBSD is definetly not the correct approach. Thats against any BSD
> >concept, especially the OpenBSD concept.
> Nonsense. The "qmail" script from LWQ is compatible with the System V
> init script mechanism, but it's also perfectly compatible with BSD and
> generally useful on all UNIX flavors as a qmail control
> interface. Maybe I should rename it qmailctl a la apachectl or
> ctlqmail a la ctlinnd...
No. I'd go with Robin to say that init scripts shouldn't live in
/usr/local/whatever, and your qmail script, perfect for linux and other
sysv-init systems, is not adequate for *BSD. It's totally against the "keep
it simple"-approach.
> >For my taste lwq is a bit too linux-specific. Don't tell people to use
> >sysv-sytle init scripts on non-sysv-init-systems. Thats confusing.
> Granted, I should add a note about adding:
> if [ -x /usr/local/sbin/qmail ]; then
> /usr/local/sbin/qmail start
> fi
> to rc.local for BSD variants,
No, see above.
> but I have no Linux bias.
Thats not what I wanted to tell you. I believe that you don't have a linux
bias, and in fact i'd guess most qmail-installations _are_ on linux. I'd
just separate basic instructions from os specifica as we have done it in
http://www.lifewithdjbdns.org/ and http://www.lifewithqmail.org/ldap/.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
"Robin S. Socha" <[EMAIL PROTECTED]> wrote:
>* Dave Sill <[EMAIL PROTECTED]> [010222 10:41]:
>> "Robin S. Socha" <[EMAIL PROTECTED]> wrote:
>>
>> >Also, putting init scripts in /usr/local does not make any sense at all
>> I've been putting stuff in /usr/local for at least a decade. I'm not
>> going to stop just because some upstart free OS's want to impose their
>> idea of the One True Filesystem Hierarchy on me.
>
>man hier should be a lot older than OpenBSD or whatever.
Hmm... My OpenBSD 2.8 "man hier" says:
[/usr/] local/ Local executables, libraries, etc.
>And system components (I consider an MTA a system component, don't you?)
>don't belong under /something/local but /something - cf. NFS.
Yes, an MTA is a "system component".
Back in the olden days, we didn't install replacements for vendor-
supplied components in directories under the control of vendor. This
isolation was done for two reasons: (1) it prevented vendor upgrades
from blowing away our replacement components, and (2) it made it easy
to identify the replacement components.
Sure, when Sun was shipping their variant of Sendmail 5.65 and I was
installing 8.6.10, I *could* have just plopped it into
/usr/lib/sendmail and /etc/sendmail.cf...but it wouldn't have terribly
bright.
I still think it's good to isolate components added by the admin--even
though it's not always as necessary as it used to be.
>> Which is where?
>
>http://cr.yp.to/compatibility.html
>http://cr.yp.to/qmail/faq/install.html#whyvar
>
>I'm shocked ;-)
Don't be. I've read all that before, I just couldn't remember where it
lived.
-Dave
Henning Brauer <[EMAIL PROTECTED]> wrote:
>On Thu, Feb 22, 2001 at 10:00:46AM -0500, Dave Sill wrote:
>>
>> Nonsense. The "qmail" script from LWQ is compatible with the System V
>> init script mechanism, but it's also perfectly compatible with BSD and
>> generally useful on all UNIX flavors as a qmail control
>> interface. Maybe I should rename it qmailctl a la apachectl or
>> ctlqmail a la ctlinnd...
>
>No. I'd go with Robin to say that init scripts shouldn't live in
>/usr/local/whatever,
Where should they live? Where does apachectl live?
>and your qmail script, perfect for linux and other
>sysv-init systems, is not adequate for *BSD.
Does "qmail start" not work on *BSD? Of course it does. It may be more
than you want, but that doesn't make it inadequate.
>It's totally against the "keep it simple"-approach.
How is having a simple control interface like:
qmail start
qmail stop
qmail queue
qmail doqueue
qmail pause
qmail cont
qmail stat
qmail reload
qmail restart
qmail cdb
against "keep it simple"?
What are the *BSD-approved equivalents for the above commands?
>> Granted, I should add a note about adding:
>> if [ -x /usr/local/sbin/qmail ]; then
>> /usr/local/sbin/qmail start
>> fi
>> to rc.local for BSD variants,
>
>No, see above.
I just don't get it.
>... I believe that you don't have a linux
>bias, and in fact i'd guess most qmail-installations _are_ on linux. I'd
>just separate basic instructions from os specifica as we have done it in
>http://www.lifewithdjbdns.org/ and http://www.lifewithqmail.org/ldap/.
My goal with LWQ--and it was obviously less than 100% successful--was
to keep the installation instructions as portable as possible. I
wanted to avoid having constant interruptions for OS-specific
details.
-Dave
I have already patched Qmail to run Qmail-Scanner; I tried to apply
Krzysztof Dabrowski's SMTP-AUTH patch, but when I ran make setup I got the
following warning:
qmail-smtpd.c:787: warning: return type of `main' is not `int'
./load qmail-smtpd rcpthosts.o commands.o timeoutread.o \
timeoutwrite.o ip.o ipme.o ipalloc.o control.o constmap.o \
received.o date822fmt.o now.o qmail.o cdb.a fd.a wait.a \
datetime.a getln.a open.a sig.a case.a env.a stralloc.a \
alloc.a substdio.a error.a str.a fs.a auto_qmail.o `cat \
socket.lib`
It seems to be running OK otherwise.
Will this cause me any problems?
Cheers
John
John P <[EMAIL PROTECTED]> wrote:
> I have already patched Qmail to run Qmail-Scanner; I tried to apply
> Krzysztof Dabrowski's SMTP-AUTH patch, but when I ran make setup I got the
> following warning:
>
> qmail-smtpd.c:787: warning: return type of `main' is not `int'
>
> It seems to be running OK otherwise. Will this cause me any problems?
No. It's a bogus warning from the compiler, because it isn't smart enough
to determine that the offending code (an implicit void return) will never
be executed.
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.
-----------------------------------------------------------------------
Hi All,
I have patched qmail-smtpd with Krzysztof Dabrowski's SMTP-AUTH patch and
have changed the line in /var/qmail/supervise/qmail-smtpd/run to end "..
/var/qmail/bin/qmail-smtpd /bin/checkpassword /bin/true &2>&1" and have been
trying to send e-mail from an IP address that is not permitted in the
tcp.cdb for relaying purposes.
I am using Outlook Express 5 to send the e-mail with the "My outgoing mail
server requires authentication" and "Use same settings as incoming e-mail"
(eg. /etc/shadow passwords) but still the password is not being accepted.
(Outlook just keeps asking for the password). Sent SMTP mail from allowed IP
address ranges sends fine.
Here's an extract from /var/log/qmail/smtpd/current: (typed as PuTTY won't
let me copy it!)
tcpserver: status 1/40
tcpserver: pid 17876 from 212.1.156.167
tcpserver: ok 17876 pluto.office.internal:10.0.0.12:25
ppp-1-167.cvx6.telinco.net:212.1.156.167::1186
tcpserver: end 17876 status 256
tcpserver: status 0/40
I did have a problem with patching qmail-smtpd (I got a warning about a
return type, see earlier e-mail on list) but I'm not sure if that's the
problem.
/etc/shadow is owned by user/group root.
What else could be causing this problem?
Thanks in advance
John
John P. wrote:
> I have patched qmail-smtpd with Krzysztof Dabrowski's SMTP-AUTH patch and
> have changed the line in /var/qmail/supervise/qmail-smtpd/run to end "..
> /var/qmail/bin/qmail-smtpd /bin/checkpassword /bin/true &2>&1" and have
been
> trying to send e-mail from an IP address that is not permitted in the
> tcp.cdb for relaying purposes.
Dabrowski's version of the authenticated SMTP patch supports two
authentication schemes, simple passwords and CRAM-MD5 challenges and
responses. Therefore, qmail-smtpd modified with the patch will require two
"checkpassword" type arguments, one to handle simple passwords, the other to
handle CRAM-MD5.
Dabrowski also wrote his own replacement for checkpassword, cmd5checkpw,
specifically to handle the CRAM-MD5 scheme. However, the latest version of
cmd5checkpw also handles simple passwords, so it can be used for both
purposes. My qmail-smtpd start-up script looks like this:
... /var/qmail/bin/qmail-smtpd \
/bin/cmd5checkpw /bin/true /bin/cmd5checkpw /bin/true ...
Note that if you do use cmd5checkpw, you will have to create a new password
file that stores passwords unencrypted; the default is /etc/poppasswd. The
source package for cmd5checkpw provides an example to help you set up this
new password file. Details and downloads at:
http://members.elysium.pl/brush/cmd5checkpw/
---Kris Kelley
> Therefore, qmail-smtpd modified with the patch will require two
> "checkpassword" type arguments, one to handle simple passwords, the other
to
> handle CRAM-MD5.
>
> Dabrowski also wrote his own replacement for checkpassword, cmd5checkpw,
> specifically to handle the CRAM-MD5 scheme. However, the latest version
of
> cmd5checkpw also handles simple passwords, so it can be used for both
> purposes. My qmail-smtpd start-up script looks like this:
>
> ... /var/qmail/bin/qmail-smtpd \
> /bin/cmd5checkpw /bin/true /bin/cmd5checkpw /bin/true ...
>
> Note that if you do use cmd5checkpw, you will have to create a new
password
> file that stores passwords unencrypted; the default is /etc/poppasswd.
The
> source package for cmd5checkpw provides an example to help you set up this
> new password file. Details and downloads at:
Kris,
I wanted to avoid using the cmd5checkpw program as I didn't want to have two
sets of password files to update. Also I'm using Outlook Express so that
means plaintext passwords only (?) - so I only put one argument on the
qmail-smtpd line. I was going to install the predecessor, that only has
plaintext auth - but that was a qmail-smtpd.c program only, and I wanted to
keep my patch for Qmail-Scanner - or can I install the new qmail-smtpd.c
program and then install the qmail-scanner patch ?
Or is there another way to force the program to check the POP3 passwords?
Cheers
John
John P. wrote:
> I wanted to avoid using the cmd5checkpw program as I didn't want to have
two
> sets of password files to update. Also I'm using Outlook Express so that
> means plaintext passwords only (?) - so I only put one argument on the
> qmail-smtpd line.
Regardless of your set-up, the patched version of qmail-smtpd will need two
checkpassword arguments. Since you won't be using CRAM-MD5 at all, you can
probably forego installing cmd5checkpw and simply give a dummy argument for
the second checkpassword requirement. So your script might look like this:
... /var/qmail/bin/qmail-smtpd \
/bin/checkpassword /bin/true dummy /bin/true ...
I would recommend that "dummy" be replaced with a program that always
returns failure, in case some smart-alec in your domain tries to use a
CRAM-MD5 enabled client.
> I was going to install the predecessor, that only has
> plaintext auth - but that was a qmail-smtpd.c program only, and I wanted
to
> keep my patch for Qmail-Scanner - or can I install the new qmail-smtpd.c
> program and then install the qmail-scanner patch ?
I am not using qmail-scanner, so I'm afraid I have no experience with it.
At any rate, using the original version of "Mrs. Brisby"'s qmail-smtpd is
not recommended, due to a bug that would allow anybody to relay if the
checkpassword program crashed. The latest version of Dabrowski's patch
fixes that bug.
---Kris Kelley
>I did have a problem with patching qmail-smtpd (I got a warning about a
>return type, see earlier e-mail on list) but I'm not sure if that's the
>problem.
>/etc/shadow is owned by user/group root.
the roots of your (and 90% of other people's problems) are 2
a) either your qmail-smtpd is not able to call checkpassowrd (check perms)
b) your checkpassword is unable to authenticate you because of access rights.
QUICK TEST:
chmod a+rxs /bin/checkpassword
If it works now, then it's one of the 2 problems, think about it and find a
good solution for your OS.
Kris
On Thu, 22 Feb 2001, [EMAIL PROTECTED] wrote:
> ns1:/usr/src/qmail-scanner-0.95# ./qmail-scanner-queue.pl -g
> Script is not setuid/setgid in suidperl
> ns1:/usr/src/qmail-scanner-0.95#
>
> Trying the test script gives:
>
> ns1:/usr/src/qmail-scanner-0.95/contrib# ./test_installation.sh -doit
> setting QMAILQUEUE to /var/qmail/bin/qmail-scanner-queue.pl for this
> test...
>
> Sending eicar test virus - should be caught by perlscanner module...
> Script is not setuid/setgid in suidperl
> qmail-inject: fatal: qq temporary problem (#4.3.0)
> done!
What is this qq error? I can't use qmail-scanner and I REALLY need
to, but every message that I receive gets lost to this error. Any
body know why/how to fix?
--
"Your mouse has moved. Windows NT must be restarted for the change to
take effect. Reboot now ? [OK]"
----- Original Message -----
From: Brett Randall <[EMAIL PROTECTED]>
To: Chris Hellberg <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, February 22, 2001 1:20 PM
Subject: Re: qmail-scanner wrapper
> > Sending eicar test virus - should be caught by perlscanner module...
> > Script is not setuid/setgid in suidperl
> > qmail-inject: fatal: qq temporary problem (#4.3.0)
> > done!
>
> What is this qq error? I can't use qmail-scanner and I REALLY need
> to, but every message that I receive gets lost to this error. Any
> body know why/how to fix?
I'm hopeful I did the right thing, but I chmod'ed both /usr/bin/suidperl and
qmail-scanner-queue.pl to 4755, and made them both owned by root. That fixed
the problem.
Cheers
John
On Thu, Feb 22, 2001 at 02:16:50PM -0000, John P wrote:
> I'm hopeful I did the right thing, but I chmod'ed both /usr/bin/suidperl and
> qmail-scanner-queue.pl to 4755, and made them both owned by root. That fixed
> the problem.
Arrrrgh! Absolutely not!!!
Do NOT run qmail-scanner-queue.pl as setuid root!! BAD BAD BAD
No known security holes that I know of - but there is ABSOLUTELY NOT REASON
to run is setuid root. It's supposed to be setuid qmailq - make it so and
I'll sleep better at night ;-)
Also, this is all off-topic. You should all be subscribed to the
Qmail-Scanner mailing-list and be having this discussion there :-)
http://lists.sourceforge.net/mailman/listinfo/qmail-scanner-general
--
Cheers
Jason Haar
Unix/Special Projects, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417
"JK" <[EMAIL PROTECTED]> wrote:
>I have a Linux 6.2 box with qmail, bind8 and apache on it. It was installed
>by a Linux consultant
Ugh. BIND might not be your problem at the moment, but it will be
sooner or later. How could your consultant have been clueful enough to
install qmail but not djbdns?
-Dave
flint <[EMAIL PROTECTED]> wrote:
> >
> >You can either use queue-fix to replace/fix the (non-existent?) queue, or
> >restore from your backups and THEN use queue-fix to fix the queue.
> I have fix the queue using queue-fix. It unlinked some file under
> /var/qmail/queue/remote, but now I still can see the Warning messages in
> the maillog? Is there something wrong?
Did you run queue-fix while qmail was running? That would be bad. Stop
qmail, run queuefix, then re-start qmail.
> I have noticed for days,now it becomes more and more unbearable. That is,it
> is very slowly when we receive mails through POP3. The strange thing is that
> when you have received the mails then receive mails again immediately, it is
> very quickly.
This was not a good reason to remove the queue. qmail-pop3d doesn't look for
mail in the queue anyways; it looks in the user's mailstore (~/Maildir/
typically).
Your problem could be ident and DNS lookup timeouts from tcpserver.
Investigate the possibility of turning off ident lookups, and either
disabling DNS lookups or fixing your DNS resolver/content server.
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.
-----------------------------------------------------------------------
Dear Charles Cazabon
>Your problem could be ident and DNS lookup timeouts from tcpserver.
>Investigate the possibility of turning off ident lookups, and either
>disabling DNS lookups or fixing your DNS resolver/content server.
>
>Charles
Yes! It's really our DNS problem. Several days ago,we have changed DNS
server. Today i check the DNS server carefully, I found it can resolve the
names in our domain,but it doen't use it's own data,it always say:"Non-authoritative
answer: ......". I have configure the Named again. It's ok now.
But I have not fix the queue yet, because I don't know how to Shut
down the qmail-send. I know it is really a very stupid question. I have
seen many documents,some use "svc" command, there isn't "svc" command
in our server, also I cann't find qmail-send.pid file in /var/run like
some articles said. How could I do?
I'm appreaciate for your warmheartedness and patience.
flint
Dear Charles Cazabon
>Your problem could be ident and DNS lookup timeouts from tcpserver.
>Investigate the possibility of turning off ident lookups, and either
>disabling DNS lookups or fixing your DNS resolver/content server.
>
>Charles
Yes! It's really our DNS problem. Several days ago,we have changed DNS
server. Today i check the DNS server carefully, I found it can resolve the
names in our domain,but it doen't use it's own data,it always say:"Non-authoritative
answer: ......". I have configure the Named again. It's ok now.
But I have not fix the queue yet, because I don't know how to Shut
down the qmail-send. I know it is really a very stupid question. I have
seen many documents,some use "svc" command, there isn't "svc" command
in our server, also I cann't find qmail-send.pid file in /var/run like
some articles said. How could I do?
I'm appreaciate for your warmheartedness and patience.
flint
Haig Earl <[EMAIL PROTECTED]> wrote:
>
> my qmail-qstat shows me over 4000 mails and its
> increasing. why arent the mails being delivered ??
You're either injecting a lot of new mail at the same time, or there are
remote hosts not responding. The second reason is quite normal. Your
qmail logs will tell you _exactly_ why those messages are not being
delivered.
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.
-----------------------------------------------------------------------
I had the same problem and was grappling with it for few days.
I have done th following to ease the situation.
1. Apply the big concurrency patch
2. I applied concurrenty value of 500 in th files conncurrencylocal
and concurrencyremote
3. Applied the BIG Todo patch (this patch has more or less solved my
problem
4. change the file split-conf to 151 from default 23
5. Dowloaded qmHandle package to show me the remote and local files
in the queue
6. Stoped the tcpserver listening on port 25
7. Allowed the queue to drop to zero
8. did make setup check in the qmail package to recompile the package
9. Started qmail
(Also if you are using queue-fix package don't forget to apply queue-fix
todo patch also)
Whenever the number deliver of remote mails become high, I see the deliver
of local mails
also suffering. So once in a while I make the concurrency value in
concurrencyremote to
zero and restart qmail to deliver only the local mails
I do not know what your setup is. Mine is on Solaris 2.6 on E3500 with very
High I/O
bottleneck. But on the same box critical path's mplex was doing local
delivery much
better than qmail. I am still working on how to improve the local deliver
speeds. Will share the results when I am successful
Hope some of these may help.
----- Original Message -----
From: Haig Earl <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 22, 2001 3:23 PM
Subject: mail queue problem.
> hi,
>
> my qmail-qstat shows me over 4000 mails and its
> increasing. why arent the mails being delivered ??
>
> urgent !
>
> TIA,
> - sg.
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - Buy the things you want at great prices!
http://auctions.yahoo.com/
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Greetings everybody!
I've installed qmail-1.03 and vpopmail which was just up last week.
I tried to send and receive email from several servers, such as
Yahoo!, Excite, and some other servers. Some works fine, the messages
could be received just in a short period.
BUT, it takes a few hours, even a few days, when I tried to receive
email from my Hotmail acct. Also from some mail servers. I have no idea why this
happened, could this because of the routing problem or something is
wrong with my mail server?
can anyone help?
Thanks!
--
Best regards,
Chrisanthy
I've expierenced the same with hotmail in the last few days. Perhaps an
overlooked MX config at slothmail has been introduced to both of us.
At 09:57 PM 2/22/2001 +0700, Chrisanthy Chrisanthy wrote:
>Greetings everybody!
>
>I've installed qmail-1.03 and vpopmail which was just up last week.
>I tried to send and receive email from several servers, such as
>Yahoo!, Excite, and some other servers. Some works fine, the messages
>could be received just in a short period.
>
>BUT, it takes a few hours, even a few days, when I tried to receive
>email from my Hotmail acct. Also from some mail servers. I have no idea
>why this
>happened, could this because of the routing problem or something is
>wrong with my mail server?
>
>can anyone help?
>Thanks!
>
>--
>Best regards,
> Chrisanthy
Okay, I've tried to install qmail-filter and thought
I did everything correctly... but it's not filtering out
anything...
Here's what I did...
edited Makefile (added -DQMAIL_QUEUE=\"/var/qmail/bin/qmail-queue-old\" )
so that I didn't have to install QMAILQUEUE patch
make (looked like it worked ok)
mv qmail-queue qmail-queue-old
created qmail-queue with the following:
#!/bin/sh
exec /path/to/qmai:-qfilter /var/qmail/bin/qmail-inject -n
chmod +x qmail-queue
restarted qmail and qmail-smtpd
Sent test message to myself with .VBS attachment (went through ok)
Ran (in the 'samples' directory) ./deny-filetypes
Sent another message... Still went through...
What I am doing wrong??? Please help, thanks!!!
Jesse
Is this the place to ask ezmlm-idx questions or is there another discussion
list for it? (I don't see one mentioned on ezmlm.org.)
--
Mike Nolan
See http://www.ezmlm.org/
All kinds of information there.
At 09:55 AM 2/22/2001 -0600, [EMAIL PROTECTED] wrote:
>Is this the place to ask ezmlm-idx questions or is there another discussion
>list for it? (I don't see one mentioned on ezmlm.org.)
>--
>Mike Nolan
"Sumith" <[EMAIL PROTECTED]> wrote:
>perl qmail-qsanity-0_52
>
>did not display anything does that mean..that my Qmail Queue system
>is set right. or what does it really mean.
What does the qmail-qsanity documentation say?
>perl qmail-lint-0_55
>Warning: users/assign checking not implemented.
>
>What does that warning mean...
It means that qmail-lint doesn't check users/assign files.
>Is it really bad?
No.
>what can i do to make this error disppear.
Just ignore it, it's not an error.
-Dave
I have question about autoreponder. It is responding to an email by replying
with the message as it should but with the email that it received as well
with full headers. Is there a way to turn this off?
--
Mark Lane, T.T.
CTO
myKapital Inc.
(403)547-9939
(403)537-9934
I completed a full changeover from sendmail to qmail today! :)
Thanks djb for all your stuff and to anyone that contributed to qmail.
--Carl--
http://slackerbsd.org
PGP signature
Thanks for reading!
Subject tells all. I installed qmail-pop3d using LWQ, and it's working
just fine. I've searched the archives hi and lo and have checked
inetd.conf, commented out pop3 and HUPed it. Nmap reports nothing on
port 110. Tcpserver is reporting the above error message and I can't
figure out why. Here's my run file:
#!/bin/shexec /usr/local/bin/softlimit -m 2000000
\/usr/local/bin/tcpserver -v -R xxx.xxx.xxx.xxx pop3
/var/qmail/bin/qmail-popup \mail.computer.domain /bin/checkpassword
/var/qmail/bin/qmail-pop3d Maildir 2>&1 \| /var/qmail/bin/splogger pop3d
2>&1
Hopefully I've just made some silly mistake. If you need additional
information, please let me know. For now I just commented out the
splogger command so I don't fill the logfile.
TIA
.mark
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/E/IT/O d- s+ a C++++$ L++++$> P+++$> L++ E--- W-- N+ o K- w-- !O
M- !V PS+ PE+ Y+ PGP t+ !5 X R- tv b+++ DI+ D- G e++ h--- r+++ z++++
------END GEEK CODE BLOCK------
1.79x10^12 furlongs per fortnight -- it's not just a good idea, it's the
law!!
use Disclaimer;
my $opinion_only;
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Subject tells all.
Don't rely on it -- please repeat the problem in the body of the message in
future.
> I installed qmail-pop3d using LWQ, and it's working just fine. I've searched
> the archives hi and lo and have checked inetd.conf, commented out pop3 and
> HUPed it. Nmap reports nothing on port 110.
Possibly its another instance of tcpserver reporting the error, like the
one starting qmail itself?
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.
-----------------------------------------------------------------------
Charles,
Thanks for the reply. Well, tcpserver is called in the run file for
qmail-smtpd and qmail-pop3d. When I make changes to the qmail-pop3d run
file, the errors do change in syslog - like commenting out the line for
splogger.
OK - I just figured it out!! Seems my rc.qmail script doesn't
stop/restart qmail-pop3d properly. There were two copies of qmail-pop3d
running. As soon as I killed the old, incorrect pop3d, the errors went
away.
>|> Subject tells all.
>
>|Don't rely on it -- please repeat the problem in the body of the message in
>|future.
Sorry, I've been only doing this on the net for about 15 years! I'll
reinclude this information in the bodies of future emails.
Thanks again for the tip!
.mark
>----------
>From: Charles Cazabon[SMTP:[EMAIL PROTECTED]]
>Sent: Thursday, February 22, 2001 12:00 PM
>To: [EMAIL PROTECTED]
>Subject: Re: qmail-pop3d: tcpserver: unable to bind: address in use problem
>
>[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> Subject tells all.
>
>Don't rely on it -- please repeat the problem in the body of the message in
>future.
>
>> I installed qmail-pop3d using LWQ, and it's working just fine. I've
>>searched
>> the archives hi and lo and have checked inetd.conf, commented out pop3 and
>> HUPed it. Nmap reports nothing on port 110.
>
>Possibly its another instance of tcpserver reporting the error, like the
>one starting qmail itself?
>
>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.
>-----------------------------------------------------------------------
>
On Thu, Feb 22, 2001 at 12:28:24PM -0800, [EMAIL PROTECTED] wrote:
> Charles,
>
> Thanks for the reply. Well, tcpserver is called in the run file for
> qmail-smtpd and qmail-pop3d. When I make changes to the qmail-pop3d run
> file, the errors do change in syslog - like commenting out the line for
> splogger.
>
> OK - I just figured it out!! Seems my rc.qmail script doesn't
> stop/restart qmail-pop3d properly. There were two copies of qmail-pop3d
> running. As soon as I killed the old, incorrect pop3d, the errors went
> away.
>
Make sure that you're 'exec'ing tcpserver in the run file. Dave Sill,
this might want updating in 'Life with qmail' -- this seems to burn a
lot of people....
Bad:
tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup FQDN \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 \
/var/qmail/bin/splogger pop3d
Good:
exec tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup FQDN \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 \
/var/qmail/bin/splogger pop3d
and then maybe instructions for supervising it properly? If it sounds
like I'm volunteering to write the new docs, I am more than willing...
--
Greg White
Those who make peaceful revolution impossible will make violent
revolution inevitable.
-- John F. Kennedy
Hi, people...
Someone knows if there is a way to enable qmail-scanner to act for just some
users ? I use .qmail file for redirection and i want that qmail-scanner
takes out all attachment of some users...
Thanks,
Alan R.
Of course, I meant "qmail-smtpd", not "qmail itself". Thinko on my part.
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.
-----------------------------------------------------------------------
My server is a UNIX box with BSDI 4.0, Apache, Qmail, and Frontpage. My
BSDI and QMail were set up by someone else (no longer with us) and I am
pretty much a newbie in this arena
A Frontpage client wants to publish a form to be received on my server
addressed to [EMAIL PROTECTED] and relayed (forwarded/redirected) to her
personal email address which is not on my server. The first hurdle was to
add SMTPHost mymailserver.address.com in the frontpage.cnf AND her
domainname.cnf file .
Now I have been told that I need to add herdomain.org to the QMail list of
allowable 'local' domains.
Reading on, in LWQ 3.5 it seems I may need to set her up in /var/qmail/alias
as well? If so, I would set her up as 'info'? And how do I set it up to
redirect to her personal [EMAIL PROTECTED]?
Do I also need to do adduser 'info' in the BSDI side of the server?
Can anyone point me in the right direction? And, is there anything else I
need to configure so this will work?
Thanks in advance for your help.
Virginia Chism <[EMAIL PROTECTED]> wrote:
>
> A Frontpage client wants to publish a form to be received on my server
> addressed to [EMAIL PROTECTED] and relayed (forwarded/redirected) to her
> personal email address which is not on my server.
[...]
> Now I have been told that I need to add herdomain.org to the QMail list of
> allowable 'local' domains. Reading on, in LWQ 3.5 it seems I may need to set
> her up in /var/qmail/alias as well? If so, I would set her up as 'info'?
> And how do I set it up to redirect to her personal [EMAIL PROTECTED]?
Easier: make herdomain.org virtual, and forward mail out of an appropriate
.qmail file directly:
echo "herdomain.org:alias-herdomain" >>/var/qmail/control/virtualdomains
echo "&forwardaddress" >~alias/.qmail-herdomain-info
Remember to remove the old entry from "locals", and to restart qmail or
HUP qmail-send. No system user accounts are necessary in this setup.
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.
-----------------------------------------------------------------------
I created a forward to each account. Unfortunately with this configuration
Qmail to forward the mail without to keep a copy of those mails. I have
found that an alias (equal name to pop account) can be created pointing to
the pop accounts and then they still get their mail. Is there a simpler way
to fix this?.
Tnanks....
Javier Morquecho Morquecho <[EMAIL PROTECTED]> wrote:
>
> I created a forward to each account. Unfortunately with this configuration
> Qmail to forward the mail without to keep a copy of those mails.
`man dot-qmail` -- remember you're allowed more than one delivery instruction
in a .qmail file.
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.
-----------------------------------------------------------------------
Hi,
Im trying to get tcpserver to work with my simple
program written in C. However, Im getting unexpected
results. My programm on execution is supposed to print
a welcome message to stdout, then read text from stdin
, then writes into stdout again. The source code looks
something like this.
...
printf("Welcome! Enter your name\n");
scanf("%s",name);
printf("Hello %s",name);
...
I use tcpserver to execute that program when there is
a connection to localhost on port 123 , like so
tcpserver 127.0.0.1 123 programname
however when i try telneting to 127.0.0.1 123
I dont get any "Welcome message" from my program.
upon telneting the programm is waiting for me to input
something... When I enter somthing , only then do I
get
the "Welcome..." then "Hello ".
------------------------------------------
bash-2.04$ telnet 127.0.0.1 555
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Bob
Welcome! Enter your name:
Hello Bob
------------------------------------------
It does the input first, and then all the output in
one shot!
Any ideas why that is happening or how to get it to
work???
Newbie.
_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca
John Peterson
> Im trying to get tcpserver to work with my simple
> program written in C. However, Im getting unexpected
> results...
> ...
> printf("Welcome! Enter your name\n");
> scanf("%s",name);
> printf("Hello %s",name);
> ...
> ------------------------------------------
> bash-2.04$ telnet 127.0.0.1 555
> Trying 127.0.0.1...
> Connected to 127.0.0.1.
> Escape character is '^]'.
> Bob
> Welcome! Enter your name:
> Hello Bob
> ------------------------------------------
> It does the input first, and then all the output in
> one shot!
Try flushing the output after the welcome message. Worked for me.
---Kris
Hi all...
Does anyone use qmail-smtp-auth ?
http://members.elysium.pl/brush/qmail-smtpd-auth/
Just wondering if it's safe to start the smtpd as requested by INSTALL in
qmail-smtp-auth.
LWQ starts smtpd differently, I don't want to upset the LWQ installation.
Can anyone offer any suggestions ?
Dennis
I install with Redhat 7.0, but qmail FAQ only has something in
inetd.conf, and Redhat 7.0 change the file to xinetd.conf, I don't know how to
install with it.
jerry
below is the content of xinetd.conf
#
# Simple configuration file for xinetd
#
#
Some defaults, and include /etc/xinetd.d/
defaults
{
instances
= 60
log_type
= SYSLOG authpriv
log_on_success = HOST
PID
log_on_failure =
HOST RECORD
}
includedir /etc/xinetd.d
|
You should read life with qmail, and use tcpserver rather than inetd or
xinetd.
--Pete
On Fri, 23 Feb 2001, jerry wrote:
> I install with Redhat 7.0, but qmail FAQ only has something in inetd.conf, and
>Redhat 7.0 change the file to xinetd.conf, I don't know how to install with it.
>
> jerry
>
> below is the content of xinetd.conf
> #
> # Simple configuration file for xinetd
> #
> # Some defaults, and include /etc/xinetd.d/
>
> defaults
> {
> instances = 60
> log_type = SYSLOG authpriv
> log_on_success = HOST PID
> log_on_failure = HOST RECORD
> }
>
> includedir /etc/xinetd.d
>
>
>
Hi...
I'm trying to achieve a authentication system by which all pop3 and IMAP
accounts are authenticated via our PDC(NT4). The IMAP authentication works
well using pam_smb but given that qmail-pop3d needs to use checkpass I need
to patch it to support PAM.
Which brings me to my question... does anyone use pam-checkpassword ?
http://www.glasswings.com.au/qmail/pam-checkpassword-0.81-diffs
As I'm a relative newbie when it comes to matters regarding patching and
.diff's, I need to know what I have to do with the .diff file.
I have tried to contact "Kelley L" at "[EMAIL PROTECTED]" with no success
(bounced email)
Can anyone offer any advice?
Cheers
Dennis
Having trouble setting up qmailadmin on a redhat 7 machine.
So far I've got qmail, vpopmail, autoresponder, ezmlm all installed and
working.
When I go to compile I get lots of "undefined reference" warnings and the
compile craps out with a couple of errors. I've attached a copy of the
compile output hoping that someone will be able to get me going in the
right direction to get this thing running.
I'm working on this with a friend so if you have a good idea for us could
you CC: [EMAIL PROTECTED]
[root@server9 qmailadmin-0.42]# make
make all-recursive
make[1]: Entering directory `/usr/src/qmailadmin-0.42'
make[2]: Entering directory `/usr/src/qmailadmin-0.42'
gcc -I. -g -O2 -c qmailadmin.c
gcc -I. -g -O2 -c alias.c
gcc -I. -g -O2 -c autorespond.c
gcc -I. -g -O2 -c forward.c
gcc -I. -g -O2 -c mailinglist.c
gcc -I. -g -O2 -c sysadmin.c
gcc -I. -g -O2 -c user.c
In file included from user.c:32:
vpopmail_config.h:138:17: warning: "PACKAGE" redefined
config.h:97:1: warning: this is the location of the previous definition
vpopmail_config.h:141:17: warning: "VERSION" redefined
config.h:100:1: warning: this is the location of the previous definition
gcc -I. -g -O2 -c util.c
gcc -I. -g -O2 -c auth.c
gcc -I. -g -O2 -c template.c
gcc -I. -g -O2 -c command.c
gcc -I. -g -O2 -c show.c
gcc -I. -g -O2 -c cgi.c
gcc -I. -g -O2 -c limits.c
gcc -I. -g -O2 -c dotqmail.c
gcc -g -O2 -o qmailadmin qmailadmin.o alias.o autorespond.o forward.o mailinglist.o
sysadmin.o user.o util.o auth.o template.o command.o show.o cgi.o limits.o dotqmail.o
-lnsl -lm -lcrypt
autorespond.o: In function `main':
/usr/src/qmailadmin-0.42/autorespond.c:250: multiple definition of `main'
qmailadmin.o:/usr/src/qmailadmin-0.42/qmailadmin.c:84: first defined here
/usr/bin/ld: Warning: size of symbol `main' changed from 1820 to 1474 in autorespond.o
qmailadmin.o: In function `main':
/usr/src/qmailadmin-0.42/qmailadmin.c:122: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/qmailadmin.c:125: undefined reference to `vget_assign'
/usr/src/qmailadmin-0.42/qmailadmin.c:164: undefined reference to `vget_assign'
/usr/src/qmailadmin-0.42/qmailadmin.c:194: undefined reference to `vget_assign'
/usr/src/qmailadmin-0.42/qmailadmin.c:210: undefined reference to `vauth_user'
/usr/src/qmailadmin-0.42/qmailadmin.c:229: undefined reference to `vget_assign'
alias.o: In function `show_redirect_lines':
/usr/src/qmailadmin-0.42/alias.c:295: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/alias.c:301: undefined reference to `slen'
/usr/src/qmailadmin-0.42/alias.c:303: undefined reference to `scopy'
/usr/src/qmailadmin-0.42/alias.c:304: undefined reference to `scat'
alias.o: In function `doredirect':
/usr/src/qmailadmin-0.42/alias.c:326: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/alias.c:333: undefined reference to `slen'
/usr/src/qmailadmin-0.42/alias.c:335: undefined reference to `scopy'
/usr/src/qmailadmin-0.42/alias.c:336: undefined reference to `scat'
alias.o: In function `moddotqmailnow':
/usr/src/qmailadmin-0.42/alias.c:404: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/alias.c:409: undefined reference to `vauth_getpw'
alias.o: In function `adddotqmailnow':
/usr/src/qmailadmin-0.42/alias.c:476: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/alias.c:501: undefined reference to `vauth_getpw'
alias.o: In function `delredirectnow':
/usr/src/qmailadmin-0.42/alias.c:582: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/alias.c:587: undefined reference to `slen'
/usr/src/qmailadmin-0.42/alias.c:589: undefined reference to `scopy'
/usr/src/qmailadmin-0.42/alias.c:590: undefined reference to `scat'
mailinglist.o: In function `delmailinglistnow':
/usr/src/qmailadmin-0.42/mailinglist.c:277: undefined reference to `slen'
/usr/src/qmailadmin-0.42/mailinglist.c:287: undefined reference to `vdelfiles'
mailinglist.o: In function `showlistusers':
/usr/src/qmailadmin-0.42/mailinglist.c:439: undefined reference to `lowerit'
mailinglist.o: In function `showlistmod':
/usr/src/qmailadmin-0.42/mailinglist.c:484: undefined reference to `lowerit'
mailinglist.o: In function `addlistusernow':
/usr/src/qmailadmin-0.42/mailinglist.c:539: undefined reference to `lowerit'
mailinglist.o: In function `addlistmodnow':
/usr/src/qmailadmin-0.42/mailinglist.c:573: undefined reference to `lowerit'
mailinglist.o: In function `dellistusernow':
/usr/src/qmailadmin-0.42/mailinglist.c:676: undefined reference to `lowerit'
mailinglist.o:/usr/src/qmailadmin-0.42/mailinglist.c:706: more undefined references to
`lowerit' follow
user.o: In function `show_user_lines':
/usr/src/qmailadmin-0.42/user.c:87: undefined reference to `vauth_getall'
/usr/src/qmailadmin-0.42/user.c:94: undefined reference to `vauth_getall'
/usr/src/qmailadmin-0.42/user.c:125: undefined reference to `vauth_getall'
/usr/src/qmailadmin-0.42/user.c:130: undefined reference to `vauth_getall'
/usr/src/qmailadmin-0.42/user.c:175: undefined reference to `vauth_getall'
user.o: In function `addusernow':
/usr/src/qmailadmin-0.42/user.c:332: undefined reference to `vadduser'
user.o: In function `modusergo':
/usr/src/qmailadmin-0.42/user.c:378: undefined reference to `vpasswd'
/usr/src/qmailadmin-0.42/user.c:381: undefined reference to `vauth_getpw'
/usr/src/qmailadmin-0.42/user.c:383: undefined reference to `vauth_setpw'
user.o: In function `delusergo':
/usr/src/qmailadmin-0.42/user.c:493: undefined reference to `vdeluser'
user.o: In function `count_users':
/usr/src/qmailadmin-0.42/user.c:545: undefined reference to `vauth_getall'
util.o: In function `show_counts':
/usr/src/qmailadmin-0.42/util.c:67: undefined reference to `count_autoresponders'
util.o: In function `check_email_addr':
/usr/src/qmailadmin-0.42/util.c:90: undefined reference to `lowerit'
util.o: In function `fixup_local_name':
/usr/src/qmailadmin-0.42/util.c:123: undefined reference to `lowerit'
template.o: In function `send_template':
/usr/src/qmailadmin-0.42/template.c:201: undefined reference to
`show_autorespond_line'
/usr/src/qmailadmin-0.42/template.c:247: undefined reference to `show_autoresponders'
/usr/src/qmailadmin-0.42/template.c:338: undefined reference to `vauth_getall'
/usr/src/qmailadmin-0.42/template.c:342: undefined reference to `vauth_getall'
command.o: In function `process_commands':
/usr/src/qmailadmin-0.42/command.c:54: undefined reference to `show_autoresponders'
/usr/src/qmailadmin-0.42/command.c:155: undefined reference to `modautorespond'
/usr/src/qmailadmin-0.42/command.c:157: undefined reference to `addautorespond'
/usr/src/qmailadmin-0.42/command.c:163: undefined reference to `addautorespondnow'
/usr/src/qmailadmin-0.42/command.c:169: undefined reference to `modautorespondnow'
/usr/src/qmailadmin-0.42/command.c:178: undefined reference to `delautorespond'
/usr/src/qmailadmin-0.42/command.c:181: undefined reference to `delautorespondnow'
command.o: In function `setdefaultaccount':
/usr/src/qmailadmin-0.42/command.c:209: undefined reference to `vauth_getpw'
collect2: ld returned 1 exit status
make[2]: *** [qmailadmin] Error 1
make[2]: Leaving directory `/usr/src/qmailadmin-0.42'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/qmailadmin-0.42'
make: *** [all-recursive-am] Error 2
Hi,
I have setup a qmail server with the patched dns.c file (PACKETSZ increased
to 65536).
Also a local dnscache based on djbdns-1.05 is setup according to the FAQs.
Normal lookups are working fine, but qmail together with dnscache running
connecting to the localhost as server (127.0.0.1 in resolv.conf) I got the
following messages in the qmail/current log for any mail message.
2001-02-22 17:19:07.687368500 status: local 0/10 remote 2/20
2001-02-22 17:19:07.690907500 delivery 3: deferral:
CNAME_lookup_failed_temporarily._(#4.4.3)/
2001-02-22 17:19:07.690914500 status: local 0/10 remote 1/20
2001-02-22 17:19:07.690996500 delivery 4: deferral:
CNAME_lookup_failed_temporarily._(#4.4.3)/
2001-02-22 17:19:07.691000500 status: local 0/10 remote 0/20
With the resolv.conf containing our nameservers there are no problems.
Has anybody experienced a similar problem?
Is my dnscache setup wrong?
Any ideas?
Regards,
Marcus
--
Sent through GMX FreeMail - http://www.gmx.net
Hello,
This might be a little off topic but it is pretty much about qmail.
I have a very mysterious problem. I had setup a qmail server (and a local
dnscache running on 127.0.0.1 for faster nslookups) for a customer of mine,
and it has been working absolutely fine. He also had some weird crappy ms
asp code, vbscript, and something to do with MS SQL and odbc connections.
This code basically stores e-mail addresses on the MS SQL server, divided in
tables by categories, and at a later time, you could use the asp web
interface to send emails to email addresses listed under certain categories.
He had it working against his sendmail or Imail box or something. His code
just uses the basic RFC compliant commands like HELO, MAIL FROM, RCPT TO,
data, etc. He liked the performance and reliability and thus wanted to do
more migration.
Now he changed his "asp code" or "stuff" (I am not exactly sure what
exactly) to relay the mail through this qmail server and not through the
sendmail/Imail box as it used to. All the emails to be sent are sent to
remote addresses and not local of course. I also made sure I allow relaying
for that entire Class C Subnet like 1.2.3.:allow,RELAYCLIENT="" in
/etc/tcp.smtp and compiled it with tcprules to tcp.smtp which the mentioned
in the tcpserver -x command to start qmail. Now he tests his code, and he
keeps getting the following error (on his nt box that is sending the emails
to the qmail server to actually deliver them):
550 5.7.1 <[EMAIL PROTECTED]>... Relaying denied. IP name lookup failed
[some.ip.add.ress]
At a first glance, I could swear on anything that this looks nothing to me
like a qmail error.
1. I am not running tcpserver with -p and -P
2. The error message is not in a recognized message format like for example
the unimplemented qmail error message:
502 unimplemented (#5.5.1)
First, the error code is mentioned *always* last!
Second, the error code is *always* prefixed with a hash mark "#"
Third, the error code is enclosed in paranthesis
Now, I telnet to the qmail box (from the server that runs his code that
connects to the qmail box to send emails) on port 25 and helo my.host.com,
mail from:<[EMAIL PROTECTED]> rcpt to:<[EMAIL PROTECTED]> data, body, and
"." and qmail queues the message with no errors, I get the email at the
other end. Hrmmmmmm
Does this error message look familiar? I also connected to that qmail box
from an ip that doesn't resolve and relayed mail through it fine (after
putting the ip address in tcp.smtp and compiling it's .cdb)
So I really believe that is not a qmail error! What is it then?
I'd really appreciate any ideas
(Please cc me a copy of your reply)
Best Regards,
Tamer Hassan
Hello,
I 've installed Qmail 1.03 on FreeBSD 4.2. I install Vpopmail for virtual
domain.
But, How to make user quota in virtual domain, because I try to use
vsetuserquota in Vpopmail and cannot blok the user space.
Can any one explain to me
Thanks
Regards,
eko
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
> But, How to make user quota in virtual domain, because I try to use
> vsetuserquota in Vpopmail and cannot blok the user space.
Please ask such questions at the vpopmail mailinglist.
Regards, Frank
|
Hi all,
I want infomations about qmail compares with
sendmail.
Can you help me?
Where www talk about them?
Such as efficiency, speedy, security, why?,
...etc.
Thank you
someone...
|
