qmail Digest 28 Apr 2001 10:00:01 -0000 Issue 1348
Topics (messages 61558 through 61616):
Freebsd 4.3's packages changed (and along with it qmail)!
61558 by: Foo Ji-Haw
61564 by: Karsten W. Rohrbach
61602 by: Oleg Polyakov
61603 by: Oleg Polyakov
61611 by: Peter van Dijk
Re: TCPserver; ucspi-tcp; inetd
61559 by: Ted Mead
Re: Cyrus IMAP newbie
61560 by: Joerg Lenneis
61567 by: question question
Re: Queue Building
61561 by: Mehul Choksi
61574 by: Charles Cazabon
Re: "A news.newusers.questions's Guide to Qmail"
61562 by: Brett Randall
61565 by: question question
61600 by: Felix von Leitner
61604 by: Brett Randall
61606 by: question question
Re: php replacement for ezmlm-cgi
61563 by: Karsten W. Rohrbach
61566 by: Peter van Dijk
Is there something like a BADMAILTO directive???HELP...
61568 by: Julio Guillen
61581 by: Markus Stumpf
Re: Help abot qmail and vpomail
61569 by: Javier Frias
61570 by: Javier Frias
61594 by: Keary Suska
61597 by: Henning Brauer
Re: qmail delivery speed comparison graphs available
61571 by: Dave Sill
Re: qmail-pop3d not working?
61572 by: Steven Katz
61573 by: Mark Delany
61576 by: Steven Katz
61578 by: Steven Katz
61579 by: Steven Katz
Re: Qmail, double-bounces, and RFC2821
61575 by: Dave Sill
Where to download Dr.Erwin Hoffmann SPAMPATCH patch???
61577 by: Julio Guillen
61580 by: Frank Tegtmeyer
61586 by: David Talkington
qmail-newu
61582 by: Peter Farmer
61583 by: Peter Farmer
61584 by: Frank Tegtmeyer
Re: Remote server connects then QUIT's, why?
61585 by: Alex Pennace
61589 by: Henning Brauer
lower concurrency on _certain_ domains?
61587 by: Alan Clegg
61588 by: Dave Sill
Return Receipt
61590 by: Thomas Booms
61592 by: Willy De la Court
61598 by: Henning Brauer
Re: Maildirmake...
61591 by: Wagner Teixeira
Re: Please help! I'm so close to getting qmail up...
61593 by: Keary Suska
Receiving mail for multiple domains
61595 by: Mark
61596 by: Bob Greene
61599 by: Henning Brauer
61601 by: Keary Suska
61605 by: James Stevens
61607 by: question question
Updated contact information
61608 by: Argenis Fernandez
bb
61609 by: Ramoni
cv
61610 by: Ramoni
Re: svscan on linux
61612 by: Rick Updegrove
cannot post question to list
61613 by: lemoninsz
Strange POP Problem
61614 by: |nix ZixinG
61616 by: Robin S. Socha
Continued
61615 by: |nix ZixinG
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]
----------------------------------------------------------------------
Thanks for replying Oleq,
Looks like the freebsd cd that comes with the qmail book is coming in handy
after all (probably the first time I ever use the cd that comes with a
book!).
I find it quite odd that freebsd 4.3's packages seem to be rearranged a
little. for example, Lynx is included in the package (and links is thrown
out). Of course, my qmail package has also disappeared, and they finally put
in uwimap! argh!
Do you know if freebsd 4.1 is a stable release? the one at www.linuxiso.org
is still calling it an 'alpha'...
----- Original Message -----
From: "Oleg Polyakov" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, 27 April, 2001 5:01 PM
Subject: Re: Please help! I'm so close to getting qmail up...
> I've got some explanation, but no solution..
>
> qmail for local delivery into /var/mail/$user
> uses part of sendmail - mail.local (for BSD systems).
> As from FreeBSD version 4.2 mail.local is no more
> setuid and could not be used directly by user for
> local mail delivery. You have to call sendmail for it
> which in turn passes message to mail.local.
>
> I believe you use script binm1 or binm1+df for running
> qmail. And maybe this part should be rewritten to do
> local mail deliveries as root.
>
> Oleg
>
> --- Foo Ji-Haw <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > Some background:
> > -I'm trying to run qmail on my Freebsd 4.2.
> > -I'm using qmail from the freebsd cd package.
> > -I read the FAQs, bought the Qmail book from SAMS, and
> > prepared the qmail daemons. They are up and running exactly as
> > depicted in the book.
> > -I tried a simple test to send a local mail to myself with the
> > following command:
> >
> > cat test | /var/qmail/bin/qmail-inject
> >
> > The mail did not get processed. I found this in the maillog:
> >
> > Apr 27 13:42:48 markus qmail: 988350168.284945 delivery 32:
> > deferral: mail.local
> > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > Apr 27 13:42:48 markus qmail: 988350168.285228 status: local
> > 1/10 remote 0/20
> > Apr 27 13:43:10 markus mail.local: lockmailbox /var/mail/jhfoo
> > failed; error cod
> > e 75
> > Apr 27 13:43:10 markus qmail: 988350190.305262 delivery 33:
> > deferral: mail.local
> > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > Apr 27 13:43:10 markus qmail: 988350190.305477 status: local
> > 0/10 remote 0/20
> >
> > I trid setting /var/mail to drwxrwxrwx, then I get this error:
> >
> > Apr 27 14:16:00 markus qmail: 988352160.082426 delivery 54:
> > deferral: mail.local
> > :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > Apr 27 14:16:00 markus qmail: 988352160.082655 status: local
> > 0/10 remote 0/20
> > Apr 27 14:17:38 markus qmail: 988352258.085002 starting
> > delivery 55: msg 454 to
> > local [EMAIL PROTECTED]
> > Apr 27 14:17:38 markus qmail: 988352258.085580 status: local
> > 1/10 remote 0/20
> > Apr 27 14:17:38 markus mail.local: setreuid(0, 1000):
> > Operation not permitted (r
> > =1000, e=1000)
> > Apr 27 14:17:38 markus qmail: 988352258.149416 delivery 55:
> > deferral: mail.local
> > :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > Apr 27 14:17:38 markus qmail: 988352258.149625 status: local
> > 0/10 remote 0/20
> >
> > Can someone please tell me what to do? I'm so darn close to
> > getting qmail up!!!
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
>
freebsd-4.3 supports building qmail from the ports collection in
/usr/ports/mail/qmail or other flavors in /usr/ports/mail/qmail-*
qmail does not use any part of sendmail if you do not want it to,
mailsystem processes are invoked via mailwrapper(8) which might not be
top of the line in performance but allows you to reconfigure your
mailsystem on the fly. the apparent sendmail binaries in the path are
actually mailwrapper invocation scripts. check mailer.conf(5).
freebsd packages are only distributed if the creator of the software
allows binary packaging. dan is very restrictive (and that's a good
thing imho) about binary packaging of qmail since the release engineers
might break something they do not want to and therefor the qmail
security warranty would not mean much anymore.
freebsd releases are tagged as -release -stable -whatever behind the
versioning unlike linux which uses even/odd versioning of the kernel to
differentiate stable and devel versions.
if you got 4.1-release you are running a production release.
if you ran 4.3-beta you would have a beta running (but with a lot of
fixes against 4.1 anyway which would be a better thing).
4.3-release is out since 20th of april. you can get it in source onto
your box by editing /etc/make.conf and
/usr/share/examples/cvsup/stable-supfile to get the release tagged
RELENG_4_3. the handbook tells you how to do this.
when you got the source update in your /usr/src tree just do
# cd /usr/src
# make buildworld
# make buildkernel
# shutdown -r
in the bootloader:
> set boot_single
> boot
to boot to singleuser
then
# fsck -p
# mount -a
# cd /usr/src
# make installworld
# make installkernel
# mergemaster
# shutdown -r now
and then you should be running freebsd 4.3-stable
do not forget to read the upgrading section in the handbook
(www.freebsd.org) and /usr/src/UPDATING and, of course, mergemaster(8)
if you want information on the different ports in the ports collection
# cd /usr/ports
# make readme
have fun
/k
Foo Ji-Haw([EMAIL PROTECTED])@2001.04.27 18:46:45 +0000:
> Thanks for replying Oleq,
>
> Looks like the freebsd cd that comes with the qmail book is coming in handy
> after all (probably the first time I ever use the cd that comes with a
> book!).
>
> I find it quite odd that freebsd 4.3's packages seem to be rearranged a
> little. for example, Lynx is included in the package (and links is thrown
> out). Of course, my qmail package has also disappeared, and they finally put
> in uwimap! argh!
>
> Do you know if freebsd 4.1 is a stable release? the one at www.linuxiso.org
> is still calling it an 'alpha'...
>
> ----- Original Message -----
> From: "Oleg Polyakov" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, 27 April, 2001 5:01 PM
> Subject: Re: Please help! I'm so close to getting qmail up...
>
>
> > I've got some explanation, but no solution..
> >
> > qmail for local delivery into /var/mail/$user
> > uses part of sendmail - mail.local (for BSD systems).
> > As from FreeBSD version 4.2 mail.local is no more
> > setuid and could not be used directly by user for
> > local mail delivery. You have to call sendmail for it
> > which in turn passes message to mail.local.
> >
> > I believe you use script binm1 or binm1+df for running
> > qmail. And maybe this part should be rewritten to do
> > local mail deliveries as root.
> >
> > Oleg
> >
> > --- Foo Ji-Haw <[EMAIL PROTECTED]> wrote:
> > > Hi all,
> > >
> > > Some background:
> > > -I'm trying to run qmail on my Freebsd 4.2.
> > > -I'm using qmail from the freebsd cd package.
> > > -I read the FAQs, bought the Qmail book from SAMS, and
> > > prepared the qmail daemons. They are up and running exactly as
> > > depicted in the book.
> > > -I tried a simple test to send a local mail to myself with the
> > > following command:
> > >
> > > cat test | /var/qmail/bin/qmail-inject
> > >
> > > The mail did not get processed. I found this in the maillog:
> > >
> > > Apr 27 13:42:48 markus qmail: 988350168.284945 delivery 32:
> > > deferral: mail.local
> > > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > > Apr 27 13:42:48 markus qmail: 988350168.285228 status: local
> > > 1/10 remote 0/20
> > > Apr 27 13:43:10 markus mail.local: lockmailbox /var/mail/jhfoo
> > > failed; error cod
> > > e 75
> > > Apr 27 13:43:10 markus qmail: 988350190.305262 delivery 33:
> > > deferral: mail.local
> > > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > > Apr 27 13:43:10 markus qmail: 988350190.305477 status: local
> > > 0/10 remote 0/20
> > >
> > > I trid setting /var/mail to drwxrwxrwx, then I get this error:
> > >
> > > Apr 27 14:16:00 markus qmail: 988352160.082426 delivery 54:
> > > deferral: mail.local
> > > :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > > Apr 27 14:16:00 markus qmail: 988352160.082655 status: local
> > > 0/10 remote 0/20
> > > Apr 27 14:17:38 markus qmail: 988352258.085002 starting
> > > delivery 55: msg 454 to
> > > local [EMAIL PROTECTED]
> > > Apr 27 14:17:38 markus qmail: 988352258.085580 status: local
> > > 1/10 remote 0/20
> > > Apr 27 14:17:38 markus mail.local: setreuid(0, 1000):
> > > Operation not permitted (r
> > > =1000, e=1000)
> > > Apr 27 14:17:38 markus qmail: 988352258.149416 delivery 55:
> > > deferral: mail.local
> > > :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > > Apr 27 14:17:38 markus qmail: 988352258.149625 status: local
> > > 0/10 remote 0/20
> > >
> > > Can someone please tell me what to do? I'm so darn close to
> > > getting qmail up!!!
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great prices
> > http://auctions.yahoo.com/
> >
--
> Captain Hook died of jock itch.
KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de
[Key] [KeyID---] [Created-] [Fingerprint-------------------------------------]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
I think you can just fetch /usr/libexec/mail.local
from FreeBSD 4.1 or just compile it.
It should be installed setuid. Setuid bit was removed
for security reasons..
Oleg
--- Foo Ji-Haw <[EMAIL PROTECTED]> wrote:
> Thanks for replying Oleq,
>
> Looks like the freebsd cd that comes with the qmail book is
> coming in handy
> after all (probably the first time I ever use the cd that
> comes with a
> book!).
>
> I find it quite odd that freebsd 4.3's packages seem to be
> rearranged a
> little. for example, Lynx is included in the package (and
> links is thrown
> out). Of course, my qmail package has also disappeared, and
> they finally put
> in uwimap! argh!
>
> Do you know if freebsd 4.1 is a stable release? the one at
> www.linuxiso.org
> is still calling it an 'alpha'...
>
> ----- Original Message -----
> From: "Oleg Polyakov" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, 27 April, 2001 5:01 PM
> Subject: Re: Please help! I'm so close to getting qmail up...
>
>
> > I've got some explanation, but no solution..
> >
> > qmail for local delivery into /var/mail/$user
> > uses part of sendmail - mail.local (for BSD systems).
> > As from FreeBSD version 4.2 mail.local is no more
> > setuid and could not be used directly by user for
> > local mail delivery. You have to call sendmail for it
> > which in turn passes message to mail.local.
> >
> > I believe you use script binm1 or binm1+df for running
> > qmail. And maybe this part should be rewritten to do
> > local mail deliveries as root.
> >
> > Oleg
> >
> > --- Foo Ji-Haw <[EMAIL PROTECTED]> wrote:
> > > Hi all,
> > >
> > > Some background:
> > > -I'm trying to run qmail on my Freebsd 4.2.
> > > -I'm using qmail from the freebsd cd package.
> > > -I read the FAQs, bought the Qmail book from SAMS, and
> > > prepared the qmail daemons. They are up and running
> exactly as
> > > depicted in the book.
> > > -I tried a simple test to send a local mail to myself with
> the
> > > following command:
> > >
> > > cat test | /var/qmail/bin/qmail-inject
> > >
> > > The mail did not get processed. I found this in the
> maillog:
> > >
> > > Apr 27 13:42:48 markus qmail: 988350168.284945 delivery
> 32:
> > > deferral: mail.local
> > > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > > Apr 27 13:42:48 markus qmail: 988350168.285228 status:
> local
> > > 1/10 remote 0/20
> > > Apr 27 13:43:10 markus mail.local: lockmailbox
> /var/mail/jhfoo
> > > failed; error cod
> > > e 75
> > > Apr 27 13:43:10 markus qmail: 988350190.305262 delivery
> 33:
> > > deferral: mail.local
> > > :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> > > Apr 27 13:43:10 markus qmail: 988350190.305477 status:
> local
> > > 0/10 remote 0/20
> > >
> > > I trid setting /var/mail to drwxrwxrwx, then I get this
> error:
> > >
> > > Apr 27 14:16:00 markus qmail: 988352160.082426 delivery
> 54:
> > > deferral: mail.local
> > >
> :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > > Apr 27 14:16:00 markus qmail: 988352160.082655 status:
> local
> > > 0/10 remote 0/20
> > > Apr 27 14:17:38 markus qmail: 988352258.085002 starting
> > > delivery 55: msg 454 to
> > > local [EMAIL PROTECTED]
> > > Apr 27 14:17:38 markus qmail: 988352258.085580 status:
> local
> > > 1/10 remote 0/20
> > > Apr 27 14:17:38 markus mail.local: setreuid(0, 1000):
> > > Operation not permitted (r
> > > =1000, e=1000)
> > > Apr 27 14:17:38 markus qmail: 988352258.149416 delivery
> 55:
> > > deferral: mail.local
> > >
> :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> > > Apr 27 14:17:38 markus qmail: 988352258.149625 status:
> local
> > > 0/10 remote 0/20
> > >
> > > Can someone please tell me what to do? I'm so darn close
> to
> > > getting qmail up!!!
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great prices
> > http://auctions.yahoo.com/
> >
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
--- "Karsten W. Rohrbach" <[EMAIL PROTECTED]> wrote:
> qmail does not use any part of sendmail if you do not want it
> to,
Well, if you use binm1 script, which comes with qmail,
you can find there explicit call to mail.local :
exec \
qmail-start \
'|preline -f /usr/libexec/mail.local
-r"${SENDER:-MAILER-DAEMON}" -d "$USER"' \
splogger qmail
---
Oleg
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
On Fri, Apr 27, 2001 at 04:08:25PM -0700, Oleg Polyakov wrote:
> I think you can just fetch /usr/libexec/mail.local
> from FreeBSD 4.1 or just compile it.
>
> It should be installed setuid. Setuid bit was removed
> for security reasons..
qmail most definitely has no need for a setuid maildropper.
Greetz, Peter.
Joe,
I had the same problem.
I was (and still am) totally confused with daemontools, inetd, ucspi,
xinitd, blah, blah, blah:)! I was reading a bunch of FAQ and install notes
and added an SMTP to my /etc/xinetd.d directory. Here is what I added:
"{
flags = REUSE NAMEINARGS
socket_type = stream
protocol = tcp
wait = no
user = qmaild
server = /usr/sbin/tcpd
server_args = /var/qmail/bin/tcp-env -R
/var/qmail/bin/qmail-smtpd
disable =no
}"
I did this because one of the FAQs said that I needed to use this with
xinetd. Of course, you don't need this if you are under control (in terms
of managing services) of ucspi. I changed "disable =no" to "disable =yes"
and it took care of this error messages. This caused the conflict with the
address in use.
I still don't have everything working yet, but I am still trying!
Thanks,
Ted
-----Original Message-----
From: jx001 [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 9:21 PM
To: [EMAIL PROTECTED]
Subject: TCPserver; ucspi-tcp; inetd
When I did install the ucspi-tcp package I receive the following
error-message (var/log/qmail/qmail-smtpd):
"tcpserver: fatal: unable to bind: adress already use"
I did install ucspi-tcp as described (http://cr.yp.to/ucspi-tcp.html)
There must be some problems with inetd...
How can I solve this problem?
THX
Joe
question question:
> I'm going through all of the qmail/djbdns/etc. archives, but it is slow
> going.
> I've used sendmail/DNS/BIND on various unix boxes for years and am
> absolutely sick of them.
> I would like to use qmail and Cyrus IMAP and djbdns, etc. on a single Redhat
> 7.0 server that has 8 IP addresses for 8 virtual websites.
> I've printed off reams of the documentation from D. J. Bernstein's website
> about qmail, tcpserver, djbdns, ucspi-tcp, daemontools, etc.
> My initial understanding was that qmail was a straight MTA replacement for
> sendmail so that I would be able to use Cyrus Imap. The Cyrus Imap is not
> supposed to require Unix accounts/homedirectories, so it scales for a larger
> number of webmail clients.
> In my reading of the Cyrus IMAP website, it only refers to postfix. I saw
> the sendmail/postfix April fool's joke, and it was quite funny.
> However, why do I not see any info about using qmail with either UW or Cyrus
> IMAP? Or am I missing something obvious?
Qmail is indeed a drop-in replacement for Sendmail and can therefore
be used with Cyrus. The key is the interface to get the mail into the
Cyrus mailboxes. You have to invoke /usr/cyrus/bin/deliver on the
message in a suitable .qmail file. Here is a very simple possible
setup, just to get you started. In /var/qmail/user/assign there is a
list of email adresses of your users plus delivery instructions. Note
that these users do not actually have to exist as Unix accounts, even
though you need to have some form of authentication, so that they can
get into their mailboxes:
=firstname1.lastname1:user1:96:12:/var/qmail/alias/delivery:-:userfolder:
=firstname2.lastname2:user2:96:12:/var/qmail/alias/delivery:-:userfolder:
=firstname3.lastname3:user3:96:12:/var/qmail/alias/delivery:-:userfolder:
.
firstname1.lastname1 is the email adress of the first user and user1
is the name of the Cyrus mailbox of that user. They cannot be the
same, since Cyrus mailboxes must not contain dots. 96 is the userid of
the Cyrus user an 12 the id of the group mail. You need to compile
that file into hashtable format with qmail-newu. Check out qmail
virtual domain support on how you could adapt this scheme for virtual
domains.
The directory /var/qmail/alias/delivery directory contains just one file,
.qmail-userfolder, with the single line
|/usr/cyrus/bin/deliver $USER || exit 111
That will either successfully deliver into the Mailbox of $USER (which
would be set to "user1" by qmail for the first example user) or
temporarily fail (with whatever reason /usr/cyrus/bin/deliver
gives). Qmail would retry delivery later on, for up to a week. In a
production enviroment you would probably want to refine this for
various exit conditions of deliver, some should probably cause the
mail to be rejected on first try. Try man qmail-command for the
various things that can be done in a .qmail file. Feel free to mail me
for further questions.
PS: Does your Webmail interface have a Imap backend? That is what you
would need to get into the Cyrus mailboxes to actually access the mail
after delivery.
--
Joerg Lenneis
email: [EMAIL PROTECTED]
Kieran, Henning, and Joerg,
I want to express my appreciation for your replies to my three posts last
night. It was late and I apologize for not organizing my thoughts into one
single post. I was so tangled up that I needed to just get my questions out
any which way.
I'm still trying to come up with a game plan before I start installing.
My goal is to use IMAP so that I can store email on the server for webmail
clients. At this point I have not settled on a IMAP solution or my webmail
interface. I think I will use PHP/IMAP for the webmail interface. I'm going
to keep looking at Courier IMAP today. I don't think I've found a direct
comparison of Courier vs Cyrus, although I have several articles comparing
Cyrus to UW.
Regardless, thanks again for helping me to understand the virtual domain and
virtual user situation.
I'll post again when I've sorted myself out!
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Hi Again,
We put the QMAIL server in the production to see its behavior; quickly the
queue grew to 24000 (with big-TODO, conf-split is set to 44), we had to
switch back to sendmail, which did the job well.
Well, how do we optimize the QMAIL server to handle 300,000 unique outbound
mails in a day?
Many thanks in advance.
Regards,
Mehul.
-----Original Message-----
From: Charles Cazabon [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 23, 2001 3:56 PM
To: Qmail (E-mail)
Subject: Re: Queue Building
Mehul Choksi <[EMAIL PROTECTED]> wrote:
> 2. The test setup was run exactly same as the production; the only
> difference was the email- ids were non-existent.
This makes a big difference; the system trying to deliver to non-existent
local or remote accounts will spend a lot of additional time and queue disk
I/O injecting and delivering bounce messages.
> 3. Well, I think I misunderstood "sending unique mails Vs sending same
mail
> to different addresses". Well, the application sends unique mails to
> different addresses with the same contents (the header changes each time
> since the "rcpt to:" changes in each mail, the body remains same)
Yes, you're sending unique messages to each recipient. This puts a large
load
on the queue disk. Sending a single message to multiple recipients only
requires queuing it once, while your method queues it separately for each
recipient.
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.
-----------------------------------------------------------------------
Mehul Choksi <[EMAIL PROTECTED]> wrote:
>
> We put the QMAIL server in the production to see its behavior; quickly the
> queue grew to 24000 (with big-TODO, conf-split is set to 44), we had to
> switch back to sendmail, which did the job well.
You haven't done enough homework about qmail; if you had, you'd know that
conf-split should be a prime number.
> Well, how do we optimize the QMAIL server to handle 300,000 unique outbound
> mails in a day?
300k messages a day is an easy load; you should be able to handle that with
average PC hardware with no problem. Obviously, you've got some major
configuration problems.
However, you've told us nothing about your configuration. Read some of the
mailing list archives, and "Life with qmail". Then send us a _good_ problem
report. Maybe we can help you then.
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.
-----------------------------------------------------------------------
>>>>> "Peter" == Peter van Dijk <[EMAIL PROTECTED]> writes:
> He does mention the list, but says [EMAIL PROTECTED], which
> probably doesn't work.
<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. (#5.1.1)
Quite right.
--
"In a world without walls and fences, who needs Windows and Gates?"
- Dino Esposito
FYI, I did successfully subscribe to this mailing list yesterday by sending
an empty message to [EMAIL PROTECTED] per the instructions on
the following webpage:
http://cr.yp.to/lists.html#qmail
"qmail: For discussion of the qmail package, the qmailanalog package, the
dot-forward package, and the fastforward package. To subscribe, send an
empty message to [EMAIL PROTECTED] This list is unmoderated and
high-volume. There is a hypertext archive of the mailing list at ORNL."
>From: Brett Randall <[EMAIL PROTECTED]>
>To: Peter van Dijk <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: "A news.newusers.questions's Guide to Qmail"
>Date: 28 Apr 2001 00:42:03 +1000
>
> >>>>> "Peter" == Peter van Dijk <[EMAIL PROTECTED]> writes:
>
> > He does mention the list, but says [EMAIL PROTECTED], which
> > probably doesn't work.
>
><[EMAIL PROTECTED]>:
>Sorry, no mailbox here by that name. (#5.1.1)
>
>Quite right.
>--
>"In a world without walls and fences, who needs Windows and Gates?"
>
>- Dino Esposito
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Thus spake Robin S . Socha ([EMAIL PROTECTED]):
> |Please direct any questions regarding Qmail, dot-forward, fastforward,
> |and/or EZMLM to Dan Bernstein .
> Bet they'll never publish my comments...
I particularly dislike the comment about Solaris and you having to move
cc to cc.sol. What kind of uber-luser has written this incredible heap
of bull-crap? I hope the name they put there is a pseudonym.
Man, that guy has _really_ lost it.
Felix
>>>>> "question" == question question <[EMAIL PROTECTED]> writes:
Compare your statement with mine.
You:
> FYI, I did successfully subscribe to this mailing list yesterday by
> sending an empty message to [EMAIL PROTECTED] per the
> instructions on the following webpage:
Me:
>> <[EMAIL PROTECTED]>:
>> Sorry, no mailbox here by that name. (#5.1.1)
@list.cr.yp.to != @cr.yp.to
--
"BUG, n.: An undesirable, poorly-understood undocumented feature."
- The Devil's Dictionary to Computer Studies
Hi Brett,
I had no intention of correcting or offending you or anyone. If you'll note,
I said a simple "FYI". I did notice the difference in the article in which
the "list." was left off. I was just describing the the method that worked
for me yesterday so that no one would feel that they needed to make the
effort to test signing up again to see exactly what worked.
Regards!
>From: Brett Randall <[EMAIL PROTECTED]>
>To: "question question" <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED]
>Subject: Re: "A news.newusers.questions's Guide to Qmail"
>Date: 28 Apr 2001 09:38:03 +1000
>
> >>>>> "question" == question question <[EMAIL PROTECTED]> writes:
>
>Compare your statement with mine.
>
>You:
>
> > FYI, I did successfully subscribe to this mailing list yesterday by
> > sending an empty message to [EMAIL PROTECTED] per the
> > instructions on the following webpage:
>
>Me:
>
> >> <[EMAIL PROTECTED]>:
> >> Sorry, no mailbox here by that name. (#5.1.1)
>
>@list.cr.yp.to != @cr.yp.to
>--
>"BUG, n.: An undesirable, poorly-understood undocumented feature."
>
>- The Devil's Dictionary to Computer Studies
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
hi there, this is way offtopic but i wondered if there are any
replacements for the ezmlm-cgi in exmlm-idx-0.40, since i do not fork
off cgi scripts on my servers. a replacement for the -cgi in php would
be a pretty good idea.
any ideas?
/k
--
> "In Christianity neither morality nor religion come into contact with
> reality at any point." -- Friedrich Nietzsche
KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de
[Key] [KeyID---] [Created-] [Fingerprint-------------------------------------]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
On Fri, Apr 27, 2001 at 05:28:40PM +0200, Karsten W. Rohrbach wrote:
> hi there, this is way offtopic but i wondered if there are any
> replacements for the ezmlm-cgi in exmlm-idx-0.40, since i do not fork
> off cgi scripts on my servers. a replacement for the -cgi in php would
> be a pretty good idea.
> any ideas?
ezmlm.cgi needs to run as the user. mod_php can't do that. Using an
external php cgi handler has no performance benefits (is in fact much
slower) than ezmlm.cgi.
Greetz, Peter.
Hi there, I hope someone help me with this issue. My
scenario is as follows:
Internet<->Mail Gateway<->Main Mail Server<->End Users
Both mail servers run Sendmail, but I am migrating to
Qmail (diferent reasons).All the internal accounts are
managed by the main mail server and all outgoing and
incoming mail from/for the internet are forwarded to
the Mail Gateway and let's say the main mail server
has 100 mail account, but my boss wants that, out of
the 100 mail accounts only 10 mail accounts (specific
users) can receive and send mail to and from the
internet.
So the question is: how do I block the mail that comes
from any address from the internet to some internal
mail account that is not supposed to recieve mail from
the internet??? Yet this account must be able to send
and receive mail internally...
I have read the qmail docs (life with qmail, FAQ,
etc...) but I have only found how to stop mail from
certain mail accounts or ip addresses....
Help me PLEASE.... :-)
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
On Fri, Apr 27, 2001 at 09:48:52AM -0700, Julio Guillen wrote:
> Hi there, I hope someone help me with this issue. My
> scenario is as follows:
>
> Internet<->Mail Gateway<->Main Mail Server<->End Users
Set up a virtual domain on the "Mail Gateway" that is your real domain
(called example.com further on):
file: control/virtualdomains:
example.com:filter
create a qmail user account like:
file users/assign:
+filter-:<user>:<uid>:<uid>:/home/filter:-::
.
(please notice that a "." has to be alone on the last line, see man
qmail-users for more information on the structure of the file)
Run "qmail-newu".
Now
# mkdir /home/filter
# chmod 711 /home/filter
# chown <uid>:<gid> /home/filter
In that directory add files
.qmail-<user>
for each <user>@example.com containing the line
&[EMAIL PROTECTED]
where "internal.example.com" is the name of "Main Mail Server".
add one file .qmail-default
containing the line
|/var/qmail/bin/bouncesaying "the rejection message sent back to senders"
this will bounce back eMails to all addresses <user>@example.com that
do not have a .qmail-<user> file in that directory.
The text is the error message that will be sent back along with the
message to the sender sending to a "blocked" user.
If tou simply want the error message to be "no such user" you don't
need the .qmail-default file.
On "Main Mail Server" set up a qmail server that does the deliveries
as you like. Via tcpserver (see -x option) block all connections but
from IP addresses of your internal net and "Mail Gateway".
This setup should work as a "mail from the Internet" block, as you
wanted it to be.
For the outgoing block it is a bit harder and depends on local
infrastructure:
On your firewall, block port 25 for outgoing connections
originiating from all local IPs but your "Mail Gateway".
On the Mail Gateway block all SMTP connections from local IP addresses
but from "Main Mail Server" and make the IP of "Main Mail Server" a
RELAYCLIENT (again, using tcpserver).
On "Main Mail Server" create a file
control/smtproutes and add one line:
:mailgate.example.com
which will forward all messages that are non local to the "Mail Gateway".
For the last step (allow certain users to send to the Internet) you need
two constraints:
- none of the other users has a login on "Main Mail Server"
- you can identify those "certain users" by IP address.
Allow relaying from the IP addresses of those certain users by making
them RELAYCLIENTs (again, via tcpserver).
----------
IMHO this setup should work, but maybe someone has a better/easier solution.
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
Stress is when you wake up screaming and you realize you haven't fallen
asleep yet.
If what you want is to send unmatched emails to a remote server,
I have a patch to vpopmail to do this.
http://jfns.net/qmail-stuff/drip.patch.fixed.README
http://jfns.net/qmail-stuff/drip.patch.fixed.tar.gz
Hope that helps...
-Jav
[EMAIL PROTECTED]
If what you want is to send unmatched emails to a remote server,
I have a patch to vpopmail to do this.
http://jfns.net/qmail-stuff/drip.patch.fixed.README
http://jfns.net/qmail-stuff/drip.patch.fixed.tar.gz
Hope that helps...
-Jav
[EMAIL PROTECTED]
I don't follow you. If you want qmail to act as a mail gateway to the NT
machine, simply put the NT domain in the SMTProutes control file, and do
_not_ accept delivery (i.e. don't have the domain in your rcpthosts file).
vpopmail should only be configured for mail you expect to receive and store
on that host, not mail destined for a remote host, unless you are trying to
do address forwarding, which you really can only do effectively using .qmail
files.
-K
> From: "Desarrollo y Sistemas" <[EMAIL PROTECTED]>
> Date: Thu, 26 Apr 2001 18:15:52 -0300
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Subject: Help abot qmail and vpomail
>
> Hi:
>
> I have a Linux platform Red Hut 7.0 working on qmail, vopmail, qmailadmin
> and sqlwebmail. My virtual domains work great. I have the following inquiry
> as follow:
>
> - I have an NT with an application with domain xxx.com name of with the
> following IP address.xxx.xxx.xxx.38
>
>
> - I created a vopmail in my virtual domain with the same name as the NT
> domain name xxx.com on my Linux platform Red Hut 7.0. The Linux server has
> the following IP address xxx.xxx.xxx.47
>
>
> I need to :
>
> Modify the MX in order to point from my virtual domain to the Linux IP
> adress xxx.xxx.xxx.47 . Right now point to xxx.xxx.xxx.38
>
>
> If an email cuenta.xxx.com arrives to the vopmail and the email or account
> cuenta.xxx.com does not exist then it should qmail should solve the problem
> and the qmail should send the information to the NT server. And this last
> one NT, work with this count.
>
>
> If an cuenta.xxx.com arrives to vopmail and exists then qmail should take
> care of the email or account and workds
>
> Is possible to do it?
>
> Thanks a lot for your help
>
> Best Regards,
>
> Alexandra Murillo
>
>
>
>
>
On Fri, Apr 27, 2001 at 03:26:06PM -0600, Keary Suska wrote:
> If you want qmail to act as a mail gateway to the NT
> machine, simply put the NT domain in the SMTProutes control file, and do
> _not_ accept delivery (i.e. don't have the domain in your rcpthosts file).
Huh? You are thinking of locals or virtualdomains here. The domain must be
in locals if qmail should accept and queue mail fro that domain.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
Markus Stumpf <[EMAIL PROTECTED]> wrote:
>The "main" work at concurrencyremote=500 was finished after about 1250
>seconds, at concurrencyremote=150 it was finished after about 1450
>seconds; concurrencyremote=250 is in between at about 1350 seconds.
I think that's because you're not just measuring the local system's
ability to pump out messages, but also the ability of an unknown set
up remote hosts to receive them.
>The number of finished successful deliveries/second is nearly the same
>for all three data sets (about 75-80 deliveries/second).
I think what you've determined is that the remote hosts on your list
can only accept 75-80 deliveries/second, not that qmail can't deliver
faster than that. In these tests, your system was able to keep 500
qmail-remotes busy, but it's possible that if the remote systems were
more receptive--able to receive 200, 300, 400 messages/second--it
might not have been able to keep them all busy.
>However the number of failures/deferrals per second was lower in the
>150 data set than in the 250 and much lower than in the 500.
Evidence that you're overwhelming some of the remotes. Do you see
deferrals for different reasons with higher concurrencies?
>*MY* conclusion from that comparisons is that the power of the
>qmail-bigconcurrency patch is probably commonly overestimated
>and the patch is kinda useless.
>
>PLEASE NOTE: the data sets are collected from delivery cycles of three
> successive weeks (the newsletter is a weekly one). Although it's
> delivered the same weekday (Friday) and around the same time (early
> afternoon GMT+2) the load on the remote (i.e. receiving) mail servers
> has a large impact on the data. This is even more true as 90% of
> the messages are sent to only 300 unique IP addresses (some of which
> are surely hidden behind load balancers).
> Thus minor tendencies are to be handled with care and the data sets
> may not be really representative.
I'm not sure you can safely draw that general conclusion. Clearly, in
this case it's nearly useless. But I don't think your situation is
typical--90% of the messages to 1/3% of the hosts. And 90000 is a
pretty large list. The chances are good that a large percentage of
those 300 hosts couldn't handle a sudden surge of up to 500 additional
SMTP sessions--or least they couldn't handle it well.
I think smaller mailings and/or a more diverse distribution of
recipients would reveal more impact of a higher concurrencyremote.
>I'd be very interested in your opinions/comments.
Thanks for taking the time to publish this information. It's further
demonstration of the need for profiling versus speculation. And it
points out how difficult it can be to accurately measure the impact of
a local change when the measurement depends on the response of remote
systems that have the potential to adapt (positively or negatively,
intentionally or accidentally) to the local change.
-Dave
Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
pop was working) and got:
qmail-pop3d: up (pid 598) 1420 seconds
qmail-send: up (pid 594) 1420 seconds
qmail-smtpd: up (pid 595) 1420 seconds
qmail-pop3d/log: up (pid 28975) 0 seconds
qmail-send/log: up (pid 596) 1420 seconds
qmail-smtpd/log: up (pid 599) 1420 seconds
Then I did it again (when pop stopped working) and got:
qmail-pop3d: up (pid 598) 1678 seconds
qmail-send: up (pid 594) 1678 seconds
qmail-smtpd: up (pid 595) 1678 seconds
qmail-pop3d/log: up (pid 26225) 0 seconds
qmail-send/log: up (pid 596) 1678 seconds
qmail-smtpd/log: up (pid 599) 1678 seconds
Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
increasing, even after it stops working.
However, doing 'ps auxw | grep pop3' while pop is working (up to 15
minutes after rebooting) gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
But doing it again when pop stops working gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
There does seem to be a connection to the second instance of tcpserver.
How can I find why and where the second tcpserver instance is being
initiated?
Thanks again, everyone.
Steven
-----Original Message-----
From: Rick Updegrove <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 10:22 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-pop3d not working?
Charles Cazabon said,
> You have two tcpserver instances, both trying to bind to the same
> interface(s) and port. At least one of those _has_ to be failing,
> and it should be showing up in your logs.
Steve said,
>>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
>> gives me:
I use this to check for status on supervised processes.
bash-2.04# cd /var/qmail/supervise; svstat * */log
qmail-pop3d: up (pid 658) 178697 seconds
qmail-send: up (pid 9480) 178696 seconds
qmail-smtpd: up (pid 3846) 178697 seconds
qmail-pop3d/log: up (pid 11946) 178697 seconds
qmail-send/log: up (pid 7901) 178697 seconds
qmail-smtpd/log: up (pid 13335) 178697 seconds
When you supervise, and one of the "seconds" columns stays at 0
seconds, you definitely have a problem. After you reboot, or better
yet, when your pop stops working, try that and see what happens.
Also, do not start pop3d from the command line if you are starting it
in your boot scripts, even if pop3 is not working properly.
Hope that helped
Rick Up
The zero seconds for qmail-pop3d/log is your problem. The logging
output of qmail-pop3d is ultimately filling up the pipe buffer and
then wedging since the pipe is never drained by qmail-pop3d/log.
The zero seconds is telling you that qmail-pop3d/log is repeatedly
being started and is exiting immediately. You need to work out why
that is.
1. Is qmail-pop3d/log/run executable?
2. What does it have in it exactly? Is the script correct?
3. What happens if you run it manually - what output do you get?
Regards.
On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote:
> Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
> pop was working) and got:
>
> qmail-pop3d: up (pid 598) 1420 seconds
> qmail-send: up (pid 594) 1420 seconds
> qmail-smtpd: up (pid 595) 1420 seconds
> qmail-pop3d/log: up (pid 28975) 0 seconds
> qmail-send/log: up (pid 596) 1420 seconds
> qmail-smtpd/log: up (pid 599) 1420 seconds
>
> Then I did it again (when pop stopped working) and got:
>
> qmail-pop3d: up (pid 598) 1678 seconds
> qmail-send: up (pid 594) 1678 seconds
> qmail-smtpd: up (pid 595) 1678 seconds
> qmail-pop3d/log: up (pid 26225) 0 seconds
> qmail-send/log: up (pid 596) 1678 seconds
> qmail-smtpd/log: up (pid 599) 1678 seconds
>
> Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
> increasing, even after it stops working.
>
> However, doing 'ps auxw | grep pop3' while pop is working (up to 15
> minutes after rebooting) gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> But doing it again when pop stops working gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
> root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> There does seem to be a connection to the second instance of tcpserver.
> How can I find why and where the second tcpserver instance is being
> initiated?
>
> Thanks again, everyone.
>
> Steven
>
>
> -----Original Message-----
> From: Rick Updegrove <[EMAIL PROTECTED]>
> Sent: Wednesday, April 25, 2001 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: qmail-pop3d not working?
>
>
> Charles Cazabon said,
> > You have two tcpserver instances, both trying to bind to the same
> > interface(s) and port. At least one of those _has_ to be failing,
> > and it should be showing up in your logs.
>
> Steve said,
> >>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
> >> gives me:
>
> I use this to check for status on supervised processes.
>
> bash-2.04# cd /var/qmail/supervise; svstat * */log
>
> qmail-pop3d: up (pid 658) 178697 seconds
> qmail-send: up (pid 9480) 178696 seconds
> qmail-smtpd: up (pid 3846) 178697 seconds
> qmail-pop3d/log: up (pid 11946) 178697 seconds
> qmail-send/log: up (pid 7901) 178697 seconds
> qmail-smtpd/log: up (pid 13335) 178697 seconds
>
> When you supervise, and one of the "seconds" columns stays at 0
> seconds, you definitely have a problem. After you reboot, or better
> yet, when your pop stops working, try that and see what happens.
>
> Also, do not start pop3d from the command line if you are starting it
> in your boot scripts, even if pop3 is not working properly.
>
> Hope that helped
>
> Rick Up
>
>
Sorry, I do have /var/qmail/supervise/qmail-pop3d/log/run (with
permissions: -rw-rw-r--). I'll fix that and see what happens.
It looks like:
#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \
/var/log/qmail/pop3d
Steven
-----Original Message-----
From: Steven Katz <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 10:24 AM
To: [EMAIL PROTECTED]
Subject: RE: qmail-pop3d not working?
Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
pop was working) and got:
qmail-pop3d: up (pid 598) 1420 seconds
qmail-send: up (pid 594) 1420 seconds
qmail-smtpd: up (pid 595) 1420 seconds
qmail-pop3d/log: up (pid 28975) 0 seconds
qmail-send/log: up (pid 596) 1420 seconds
qmail-smtpd/log: up (pid 599) 1420 seconds
Then I did it again (when pop stopped working) and got:
qmail-pop3d: up (pid 598) 1678 seconds
qmail-send: up (pid 594) 1678 seconds
qmail-smtpd: up (pid 595) 1678 seconds
qmail-pop3d/log: up (pid 26225) 0 seconds
qmail-send/log: up (pid 596) 1678 seconds
qmail-smtpd/log: up (pid 599) 1678 seconds
Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
increasing, even after it stops working.
However, doing 'ps auxw | grep pop3' while pop is working (up to 15
minutes after rebooting) gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
But doing it again when pop stops working gives me:
root 591 0.0 0.4 1272 344 ? S 09:06 0:00
supervise qmail-pop3d
root 596 0.0 0.6 1344 512 ? S 09:06 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
There does seem to be a connection to the second instance of tcpserver.
How can I find why and where the second tcpserver instance is being
initiated?
Thanks again, everyone.
Steven
-----Original Message-----
From: Rick Updegrove <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 10:22 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-pop3d not working?
Charles Cazabon said,
> You have two tcpserver instances, both trying to bind to the same
> interface(s) and port. At least one of those _has_ to be failing,
> and it should be showing up in your logs.
Steve said,
>>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
>> gives me:
I use this to check for status on supervised processes.
bash-2.04# cd /var/qmail/supervise; svstat * */log
qmail-pop3d: up (pid 658) 178697 seconds
qmail-send: up (pid 9480) 178696 seconds
qmail-smtpd: up (pid 3846) 178697 seconds
qmail-pop3d/log: up (pid 11946) 178697 seconds
qmail-send/log: up (pid 7901) 178697 seconds
qmail-smtpd/log: up (pid 13335) 178697 seconds
When you supervise, and one of the "seconds" columns stays at 0
seconds, you definitely have a problem. After you reboot, or better
yet, when your pop stops working, try that and see what happens.
Also, do not start pop3d from the command line if you are starting it
in your boot scripts, even if pop3 is not working properly.
Hope that helped
Rick Up
POP instantly started working once I fixed the perms! Thanks!
Steven
-----Original Message-----
From: Steven Katz <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 11:08 AM
To: [EMAIL PROTECTED]
Subject: RE: qmail-pop3d not working?
Sorry, I do have /var/qmail/supervise/qmail-pop3d/log/run (with
permissions: -rw-rw-r--). I'll fix that and see what happens.
It looks like:
#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \
/var/log/qmail/pop3d
Steven
-----Original Message-----
From: Mark Delany <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-pop3d not working?
The zero seconds for qmail-pop3d/log is your problem. The logging
output of qmail-pop3d is ultimately filling up the pipe buffer and
then wedging since the pipe is never drained by qmail-pop3d/log.
The zero seconds is telling you that qmail-pop3d/log is repeatedly
being started and is exiting immediately. You need to work out why
that is.
1. Is qmail-pop3d/log/run executable?
2. What does it have in it exactly? Is the script correct?
3. What happens if you run it manually - what output do you get?
Regards.
On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote:
> Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
> pop was working) and got:
>
> qmail-pop3d: up (pid 598) 1420 seconds
> qmail-send: up (pid 594) 1420 seconds
> qmail-smtpd: up (pid 595) 1420 seconds
> qmail-pop3d/log: up (pid 28975) 0 seconds
> qmail-send/log: up (pid 596) 1420 seconds
> qmail-smtpd/log: up (pid 599) 1420 seconds
>
> Then I did it again (when pop stopped working) and got:
>
> qmail-pop3d: up (pid 598) 1678 seconds
> qmail-send: up (pid 594) 1678 seconds
> qmail-smtpd: up (pid 595) 1678 seconds
> qmail-pop3d/log: up (pid 26225) 0 seconds
> qmail-send/log: up (pid 596) 1678 seconds
> qmail-smtpd/log: up (pid 599) 1678 seconds
>
> Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
> increasing, even after it stops working.
>
> However, doing 'ps auxw | grep pop3' while pop is working (up to 15
> minutes after rebooting) gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> But doing it again when pop stops working gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
> root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> There does seem to be a connection to the second instance of tcpserver.
> How can I find why and where the second tcpserver instance is being
> initiated?
>
> Thanks again, everyone.
>
> Steven
>
>
> -----Original Message-----
> From: Rick Updegrove <[EMAIL PROTECTED]>
> Sent: Wednesday, April 25, 2001 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: qmail-pop3d not working?
>
>
> Charles Cazabon said,
> > You have two tcpserver instances, both trying to bind to the same
> > interface(s) and port. At least one of those _has_ to be failing,
> > and it should be showing up in your logs.
>
> Steve said,
> >>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
> >> gives me:
>
> I use this to check for status on supervised processes.
>
> bash-2.04# cd /var/qmail/supervise; svstat * */log
>
> qmail-pop3d: up (pid 658) 178697 seconds
> qmail-send: up (pid 9480) 178696 seconds
> qmail-smtpd: up (pid 3846) 178697 seconds
> qmail-pop3d/log: up (pid 11946) 178697 seconds
> qmail-send/log: up (pid 7901) 178697 seconds
> qmail-smtpd/log: up (pid 13335) 178697 seconds
>
> When you supervise, and one of the "seconds" columns stays at 0
> seconds, you definitely have a problem. After you reboot, or better
> yet, when your pop stops working, try that and see what happens.
>
> Also, do not start pop3d from the command line if you are starting it
> in your boot scripts, even if pop3 is not working properly.
>
> Hope that helped
>
> Rick Up
>
>
I don't have qmail-pop3d/log/run, but I do have
/var/qmail/supervise/qmail-pop3d/run (with permissions: -rwxr-xr-x).
It looks like:
#!/bin/sh
exec /usr/local/bin/softlimit -m 2000000 \
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup \
idma.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1
I also have /var/log/qmail/pop3d, which is empty, as you might've guessed.
The output of running 'qmail-pop3d/run' manually is:
tcpserver: fatal: unable to bind: address already used
-----Original Message-----
From: Mark Delany <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-pop3d not working?
The zero seconds for qmail-pop3d/log is your problem. The logging
output of qmail-pop3d is ultimately filling up the pipe buffer and
then wedging since the pipe is never drained by qmail-pop3d/log.
The zero seconds is telling you that qmail-pop3d/log is repeatedly
being started and is exiting immediately. You need to work out why
that is.
1. Is qmail-pop3d/log/run executable?
2. What does it have in it exactly? Is the script correct?
3. What happens if you run it manually - what output do you get?
Regards.
On Fri, Apr 27, 2001 at 10:23:56AM -0700, Steven Katz wrote:
> Thanks, Rick. I did 'cd /var/qmail/supervise; svstat * */log' (while
> pop was working) and got:
>
> qmail-pop3d: up (pid 598) 1420 seconds
> qmail-send: up (pid 594) 1420 seconds
> qmail-smtpd: up (pid 595) 1420 seconds
> qmail-pop3d/log: up (pid 28975) 0 seconds
> qmail-send/log: up (pid 596) 1420 seconds
> qmail-smtpd/log: up (pid 599) 1420 seconds
>
> Then I did it again (when pop stopped working) and got:
>
> qmail-pop3d: up (pid 598) 1678 seconds
> qmail-send: up (pid 594) 1678 seconds
> qmail-smtpd: up (pid 595) 1678 seconds
> qmail-pop3d/log: up (pid 26225) 0 seconds
> qmail-send/log: up (pid 596) 1678 seconds
> qmail-smtpd/log: up (pid 599) 1678 seconds
>
> Although qmail-pop3d/log stayed at 0 seconds, qmail-pop3d keeps
> increasing, even after it stops working.
>
> However, doing 'ps auxw | grep pop3' while pop is working (up to 15
> minutes after rebooting) gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> But doing it again when pop stops working gives me:
>
> root 591 0.0 0.4 1272 344 ? S 09:06 0:00
> supervise qmail-pop3d
> root 596 0.0 0.6 1344 512 ? S 09:06 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
> root 4454 0.0 0.6 1344 516 ? S 09:17 0:00
> /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup idma
>
> There does seem to be a connection to the second instance of tcpserver.
> How can I find why and where the second tcpserver instance is being
> initiated?
>
> Thanks again, everyone.
>
> Steven
>
>
> -----Original Message-----
> From: Rick Updegrove <[EMAIL PROTECTED]>
> Sent: Wednesday, April 25, 2001 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: qmail-pop3d not working?
>
>
> Charles Cazabon said,
> > You have two tcpserver instances, both trying to bind to the same
> > interface(s) and port. At least one of those _has_ to be failing,
> > and it should be showing up in your logs.
>
> Steve said,
> >>At which point, doing 'sh -x /var/qmail/supervise/qmail-pop3d/run'
> >> gives me:
>
> I use this to check for status on supervised processes.
>
> bash-2.04# cd /var/qmail/supervise; svstat * */log
>
> qmail-pop3d: up (pid 658) 178697 seconds
> qmail-send: up (pid 9480) 178696 seconds
> qmail-smtpd: up (pid 3846) 178697 seconds
> qmail-pop3d/log: up (pid 11946) 178697 seconds
> qmail-send/log: up (pid 7901) 178697 seconds
> qmail-smtpd/log: up (pid 13335) 178697 seconds
>
> When you supervise, and one of the "seconds" columns stays at 0
> seconds, you definitely have a problem. After you reboot, or better
> yet, when your pop stops working, try that and see what happens.
>
> Also, do not start pop3d from the command line if you are starting it
> in your boot scripts, even if pop3 is not working properly.
>
> Hope that helped
>
> Rick Up
>
>
[EMAIL PROTECTED] (Patrick J. LoPresti) wrote:
>This is the new RFC which supersedes RFC821 as the SMTP specification:
>
> http://www.faqs.org/rfcs/rfc2821.html
>
>The grammar in sections 4.1.2 and 4.1.3 appears not to permit [] as
>the domain portion of a mailbox in an address. In particular, the
>address "#@[]", which Qmail uses as the envelope sender for
>double-bounces, is not syntactically valid according to this grammar.
I believe #@[] was invalid under RFC821, as well--and is one of the
reasons that particular string was selected, so this is nothing
new. Double bounces should be delivered locally, so RFC821/2821
doesn't apply.
-Dave
Does anyone knows where to download Dr.Erwin Hoffmann
SPAMPATCH patch for QMAIL????
Thank you....
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
Try
http://www.fehcom.de/
select QMAIL in the left frame.
Regards, Frank
-----BEGIN PGP SIGNED MESSAGE-----
Julio Guillen wrote:
>Does anyone knows where to download Dr.Erwin Hoffmann
>SPAMPATCH patch for QMAIL????
http://www.fehcom.de/qmail/qmail_en.html
- --
David Talkington
http://www.spotnet.org
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOunFwb1ZYOtSwT+tAQHvRwgAwP3YTj8G6EiOBXS/mKHciFNDobcIBYZO
cf/CG6O+WdLDVlatGZqa7Us9zKpJkYRPaaZxaD0JU8RmBiPuYV3cAU85s7BRybIt
7efV6HJYjnpdUVtA5ymEgCJ2ZhQ0LjawTJXuqzhSmQsRzzjOkkIma438fojFfRhb
ejjujIddQO6CMGqPRdh77HZ3wXO6U124UAFYpDC7rmDW1M9qnIn4RAUEcDQcAYO4
LnzvB9vI2yqyyRPYLqDgH92iuYuRH4qjNYYI+EGcbfA5Gv3gguGGw+K7IIx1pwd0
qkDObvvhjMKy1WNFcvLwPyOUkpn7eyB7d3waJrH3L60bhHT5jOIm1w==
=UjbT
-----END PGP SIGNATURE-----
Hi all,
I'm trying to get /var/qmail/users/assign to compile with qmail-newu but get the
following error:
[shells] qmail # qmail-newu
qmail-newu: fatal: bad format in users/assign
As per the qmail-users man page:
The file /var/qmail/users/assign assigns addresses to users. For example,
=joe.shmoe:joe:503:78:/home/joe:::
so my users/assign looks like this
=peter.farmer:pfarmer:1001:100:/usr/local/pfarmer:::
Am I doing something wrong?
TIA
--
Peter Farmer <[EMAIL PROTECTED]>
Senior Systems Engineer
blueyonder - http://www.blueyonder.co.uk/
On 19:37:13 - 27/04/01, Peter Farmer wrote:
Ignore me, just had my question answered by
Markus Stumpf in the thread "Is there something like a BADMAILTO directive???HELP..."
Soz
Peter
> Hi all,
>
> I'm trying to get /var/qmail/users/assign to compile with qmail-newu but get the
>following error:
>
> [shells] qmail # qmail-newu
> qmail-newu: fatal: bad format in users/assign
>
>
> As per the qmail-users man page:
>
> The file /var/qmail/users/assign assigns addresses to users. For example,
>
> =joe.shmoe:joe:503:78:/home/joe:::
>
> so my users/assign looks like this
>
> =peter.farmer:pfarmer:1001:100:/usr/local/pfarmer:::
>
> Am I doing something wrong?
>
>
> TIA
>
> --
> Peter Farmer <[EMAIL PROTECTED]>
>
> Senior Systems Engineer
> blueyonder - http://www.blueyonder.co.uk/
Peter Farmer <[EMAIL PROTECTED]> writes:
> Am I doing something wrong?
Did you possibly delete the final line (the one containing only a
dot)?
Frank
On Fri, Apr 27, 2001 at 01:08:41AM -0400, Jay Swackhamer wrote:
> > 988341350.667080 tcpserver: pid 10036 from 138.220.29.7
> > 988341350.668046 tcpserver: ok 10036 matrixit.net:216.58.86.3:25
> > :138.220.29.7::2037
> > 988341350.672839 10036 > 220 matrixit.net ESMTP ready^M
> > 988341350.739657 10036 < EHLO worldbank.org^M
> > 988341350.739847 10036 > 250-matrixit.net^M
> > 988341350.739958 10036 > 250-SIZE 10485760^M
> > 988341350.740083 10036 > 250-PIPELINING^M
> > 988341350.740182 10036 > 250 8BITMIME^M
> > 988341350.808618 10036 < QUIT^M
> > 988341350.808958 tcpserver: end 10036 status 0
Perhaps it has a message larger than 10485760 bytes for you. Note that
stock qmail-smtpd doesn't use EHLO SIZE, so either try a stock
qmail-smtpd or find some other way to cause qmail-smtpd to not spit
out EHLO SIZE.
> The remote mail server at 138.220.29.7 just connects, then QUIT's
> immediately, NOT delivering the mail it has for me (and yes, it does have
> some). So it's not like qmail is refusing the mail, the remote just decides
> to QUIT before sending it. It has been doing this every 5 minutes over the
> past few days. Everything else is honky-dory. I'm totally at a loss for why
> this is happening. Any possible explanations?
>
> From the occasional messages I have received, it appears to be running Lotus
> Domino Release 5.0.5 and Mailsweeper SMTPRS 4.2.1
I speculate that Lotus Domino is probably head-of-line blocking on
this one oversize message, preventing smaller messages from getting
through.
On Fri, Apr 27, 2001 at 03:08:50PM -0400, Alex Pennace wrote:
> I speculate that Lotus Domino is probably head-of-line blocking on
> this one oversize message, preventing smaller messages from getting
> through.
Domino0 doesn't behave this way. The SMTP implementation isn't good, though.
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
I run mailinglists.org and have come to find out that they way that AOL is
determining that I am a "spammer" (I'm not), is the number of concurrent
connections into AOL.
Is there any way to lower the concurrency rate on a single domain (AOL.com)
while leaving everyone else intact?
AlanC
--
Alan Clegg I do UNIX and Networks
[EMAIL PROTECTED] I don't have any certification
I have experience
Alan Clegg <[EMAIL PROTECTED]> wrote:
>I run mailinglists.org and have come to find out that they way that AOL is
>determining that I am a "spammer" (I'm not), is the number of concurrent
>connections into AOL.
>
>Is there any way to lower the concurrency rate on a single domain (AOL.com)
>while leaving everyone else intact?
Sure.
# echo aol.com:alias-aol >>/var/qmail/control/virtualdomains
# echo ./AOLspool/ >/var/qmail/alias/.qmail-aol-default
# qmail restart
Then install serialmail and add a cron entry to run maildirsmtp on the
AOLspool periodically.
-Dave
Hi all,
does qmail generally support the "Return Rceipt" feature? If so, how?
And if not so, are there any workarounds or so?
I want to be able to use this feature.
Thanks for your help.
Thomas
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thomas,
man qreceipt
qreceipt only reacts to "Notice Request upon delivery to"
but there is a problem with some clients like outlook that use
"Return Receipt To"
I made a patch for qreceipt to enable this you can find it at
http://www.quint.be/projects/
On Friday, April 27, 2001 22:52, Thomas Booms
[SMTP:[EMAIL PROTECTED]] wrote:
>
> Hi all,
>
> does qmail generally support the "Return Rceipt" feature? If so,
> how? And if not so, are there any workarounds or so?
>
> I want to be able to use this feature.
>
> Thanks for your help.
>
Thomas
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOunTT/4IaGw3x6aJEQLuVwCgtvfGm4ePDanQ4tP3YyrZ81gpAYcAni7J
oeOuILFvRqrx9ivepxBhx0fP
=+L69
-----END PGP SIGNATURE-----
On Fri, Apr 27, 2001 at 10:51:59PM +0200, Thomas Booms wrote:
> Hi all,
>
> does qmail generally support the "Return Rceipt" feature? If so, how?
> And if not so, are there any workarounds or so?
>
> I want to be able to use this feature.
man -m /var/qmail/man qreceipt
> Thanks for your help.
>
> Thomas
>
>
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
>
> By my last qmail-installation I've given the maildirs the right 703.
> I think that is also a good setting for that.
>
??? I see no meaning for that. Are you *sure* *everyone* can create and
remove files on every Maildir in your system? I wouldn't like to be one of
your users, I'm sorry.
Wagner.
Have you read the INSTALL.mbox file that came with the qmail source? It may
have some clues. If I am not mistaken, only root can change its identity,
and this error is indicating that the real uid of the process is 1000, which
is not root, so it can't change to real uid 0, so the setuid call is
failing. I am assuming that 1000 is the uid of qmaill, or whichever qmail
user is responsible for local deliveries.
It may be necessary that qmail-start should be invoked under root, which
seems to be the case on my machine. If it is not, that could be a cause.
-K
> From: "Foo Ji-Haw" <[EMAIL PROTECTED]>
> Date: Fri, 27 Apr 2001 14:21:08 +0800
> To: <[EMAIL PROTECTED]>
> Subject: Please help! I'm so close to getting qmail up...
>
> Hi all,
>
> Some background:
> -I'm trying to run qmail on my Freebsd 4.2.
> -I'm using qmail from the freebsd cd package.
> -I read the FAQs, bought the Qmail book from SAMS, and prepared the qmail
> daemons. They are up and running exactly as depicted in the book.
> -I tried a simple test to send a local mail to myself with the following
> command:
>
> cat test | /var/qmail/bin/qmail-inject
>
> The mail did not get processed. I found this in the maillog:
>
> Apr 27 13:42:48 markus qmail: 988350168.284945 delivery 32: deferral:
> mail.local
> :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> Apr 27 13:42:48 markus qmail: 988350168.285228 status: local 1/10 remote 0/20
> Apr 27 13:43:10 markus mail.local: lockmailbox /var/mail/jhfoo failed; error
> cod
> e 75
> Apr 27 13:43:10 markus qmail: 988350190.305262 delivery 33: deferral:
> mail.local
> :_lockmailbox_/var/mail/jhfoo_failed;_error_code_75_/
> Apr 27 13:43:10 markus qmail: 988350190.305477 status: local 0/10 remote 0/20
>
> I trid setting /var/mail to drwxrwxrwx, then I get this error:
>
> Apr 27 14:16:00 markus qmail: 988352160.082426 delivery 54: deferral:
> mail.local
> :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> Apr 27 14:16:00 markus qmail: 988352160.082655 status: local 0/10 remote 0/20
> Apr 27 14:17:38 markus qmail: 988352258.085002 starting delivery 55: msg 454
> to
> local [EMAIL PROTECTED]
> Apr 27 14:17:38 markus qmail: 988352258.085580 status: local 1/10 remote 0/20
> Apr 27 14:17:38 markus mail.local: setreuid(0, 1000): Operation not permitted
> (r
> =1000, e=1000)
> Apr 27 14:17:38 markus qmail: 988352258.149416 delivery 55: deferral:
> mail.local
> :_setreuid(0,_1000):_Operation_not_permitted_(r=1000,_e=1000)/
> Apr 27 14:17:38 markus qmail: 988352258.149625 status: local 0/10 remote 0/20
>
> Can someone please tell me what to do? I'm so darn close to getting qmail
> up!!!
>
How can I configure qmail to accept mail for mail.domaina.com and
mail.domainb.com?
Nothing in the FAQ could be found.
Thanks,
Mark
Mark wrote:
>
> How can I configure qmail to accept mail for mail.domaina.com and
> mail.domainb.com?
>
> Nothing in the FAQ could be found.
>
> Thanks,
>
> Mark
Add them both to /var/qmail/control/rcpthosts
--
Bob Greene
[EMAIL PROTECTED]
Pull my finger for my public key
On Fri, Apr 27, 2001 at 02:56:08PM -0600, Mark wrote:
>
> How can I configure qmail to accept mail for mail.domaina.com and
> mail.domainb.com?
> Nothing in the FAQ could be found.
Nonsense. Read it again. Hint: rcpthosts, locals, virtualdomains
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
http://www.bsws.de | Germany
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
man qmail-control
Check out rcpthosts.
-K
> From: Mark <[EMAIL PROTECTED]>
> Date: 27 Apr 2001 14:56:08 -0600
> To: [EMAIL PROTECTED]
> Subject: Receiving mail for multiple domains
>
>
> How can I configure qmail to accept mail for mail.domaina.com and
> mail.domainb.com?
>
> Nothing in the FAQ could be found.
>
> Thanks,
>
> Mark
>
>
> Unix is very simple, but it takes a genius to understand the simplicity.
> (Dennis Ritchie)
Good GOD!!! I'm an idiot then........
--JT :)
I agree that it is difficult to figure out the domain configurations. My
favorite documentation on that at the moment is at:
http://x42.com/qmail/cookbook/domains/
Mark wrote:
>
>How can I configure qmail to accept mail for mail.domaina.com and
>mail.domainb.com?
>
>Nothing in the FAQ could be found.
>
>Thanks,
>
>Mark
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Title: Scout
|
|
| |
|
Argenis Fernandez has sent you
the updated contact information below using Scout. You can cut and paste the
information below into your address book, or let Scout update your entire address
book automatically. To learn more about Scout, click here.
|
| |
|
|
Argenis Fernandez
Engineer
Juntos Interactive Media Networks
2665 South Bayshore Drive, Suite 1100
Miami, FL 33133
Phone: 305 8600116
Fax: 305 8609401
[EMAIL PROTECTED]
|
|
If you've already registered for the Scout service and this an
additional email address of yours,
click here
to add this address to your account.
|
|
If you do not wish to receive further mail from your contacts through the Scout system,
click here
|
|
--
------------------------------------------
Andre Luiz - #UIN:1109616 -> http://www.ramoni.hpg.com.br
Databras Informatica -> http://www.databras.com.br
LinuxInfo -> http://www.linuxinfo.com.br
BrasNET: #linuxall -> http://www.linuxall.org
--
------------------------------------------
Andre Luiz - #UIN:1109616 -> http://www.ramoni.hpg.com.br
Databras Informatica -> http://www.databras.com.br
LinuxInfo -> http://www.linuxinfo.com.br
BrasNET: #linuxall -> http://www.linuxall.org
From: "Subba Rao" <[EMAIL PROTECTED]>
> I have followed the instructions on DJB's site to install and start svscan.
>
> On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn
> :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service </dev/null
> >/dev/console 2>/dev/console to the end of /etc/inittab, and type kill -HUP 1.
the command "init q" (without the quotes) will reload inittab.
I never did get the "new and improved instructions" to work, so I went back to
the original instructions that always worked the first try.
echo Starting svscan in /service
env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin csh -cf 'svscan /service &'
Add the above two lines to rc.local and reboot.
Hope that helped.
Rick Up
hi,qmail list admin:
i can not post question to the [EMAIL PROTECTED]
i can receive list mail.
|
Hi guys, I've got a strange problem with my POP3
Daemon.
It was working fine all along when suddenly, my
client's can't authenticate. They keep having timeout error. I felt strange, so
I waited, and found that after waiting for 2 minutes, it will actually
authenticate and get my mail.
I checked my network config, and found
nothing wrong with it. I even temporilly disabled my POP3D to my old sendmail's
POP3d, and its working fine. There is absolutely no lag. I even tried to
send a mail with attachment to check out the network speed, and its rather fast.
I'm getting 20kps consistent for my 5MB file. No problem.
The lag is just at the connection. Outlook express
will just show connected for 2 minutes before it actually check
I'm using VPOPMail, QMail, TCPServer
Any help will be deeply appreciated
Thanks
David
|
* |nix ZixinG <[EMAIL PROTECTED]> [010428 04:59]:
> I've got a strange problem with my POP3 Daemon.
Not. You have a problem with your MUA (sending HTML to lists is
*extremely* rude) and your not reading the docs.
> It was working fine all along when suddenly, my client's can't
> authenticate. They keep having timeout error. I felt strange, so I
> waited, and found that after waiting for 2 minutes, it will actually
> authenticate and get my mail.
What did you change?
> The lag is just at the connection. Outlook express will just show
> connected for 2 minutes before it actually check
Outlook Express is FUBAR. Test with a working MUA. Gnus, mutt, PMail.
> I'm using VPOPMail, QMail, TCPServer
Thanks for not submitting any useful information (like your pop3d run
script).
--
Robin S. Socha
http://my.gnus.org/ - To boldly frobnicate what no newbie has grokked before.
|
BTW guys, I'm running Redhat 7.0, kernel
2.2.16
Is it by any chance my Kernel?
David
|
