qmail Digest 4 Nov 2000 11:00:00 -0000 Issue 1174
Topics (messages 51598 through 51637):
Re: RCPTHOSTS Dilemma
51598 by: Justin Bell
Re: TCPSERVER: Unable to Bind to Port
51599 by: Anthony Abby
51600 by: Anthony Abby
Re: (Fwd) ezmlm response
51601 by: Albert Hopkins
51602 by: Greg Owen
Error 451
51603 by: Tom Laudeman
51606 by: Charles Cazabon
51608 by: Michael Stevens
51611 by: Hubbard, David
51612 by: Jerry Lynde
Re: QMail and Win NT user auth
51604 by: Kris Kelley
51618 by: Henry Baragar
Re: More trouble
51605 by: Howard Miller
51607 by: Adam McKenna
51610 by: David Dyer-Bennet
51613 by: Howard Miller
51615 by: Aaron L. Meehan
51616 by: Adam McKenna
51617 by: Jerry Lynde
51623 by: Howard Miller
qmail and pine - I don't get it
51609 by: Robin S. Socha
51614 by: Robin S. Socha
Force Queue run
51619 by: Warren Small
51620 by: Greg Owen
51621 by: James Browning
Re: ANNOUNCE: qrblcheck -- rbl checking for .qmail
51622 by: Robert J Adams
51625 by: Jon Rust
51628 by: Jon Rust
51631 by: Jon Rust
Connection closed by foreign host
51624 by: Javier Morquecho Morquecho
51626 by: Greg Owen
51627 by: Gerry Boudreaux
configuring backmailservers
51629 by: Jens Georg
51633 by: Peter van Dijk
Qmail Configuration
51630 by: Manu K.U.
Quota on outgoing mail
51632 by: Eduardo Augusto Alvarenga
51634 by: Peter van Dijk
smtp, pop3, RH7 and qmail
51635 by: Bauhaus
Re: high performance configs [was: Blocked pipe to qmail-queue]
51636 by: Greg Cope
51637 by: Greg Cope
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]
----------------------------------------------------------------------
On Thu, Nov 02, 2000 at 04:37:43PM -0500, Anthony Abby wrote:
# I'm having a problem with RCPTHOSTS and relaying. Without RCPTHOSTS (or
# MORERCPTHOSTS) my mail server is an open relay, and yet I'm having
# difficulty setting it up so that my Listserv (Listar), which runs on the
# same box as QMail, can send out email to list subscribers?
#
# I have the following in rcpthosts:
#
# listserv.genexchange.com
# listserv.genexchange.org
# listserv.genexchange.net
#
# and I have the following in defaulthost
#
# listserv.genexchange.com
#
# I've read through the relaying tutorials linked to from the QMail website,
# but didn't find anything addresses this point. I need to relay selectively
# for mailing lists traffic, for not for anyone else...
#
# Any ideas?
it sounds like you need to add localhost (127.0.0.1) to your relay hosts
settings
--
Justin Bell
Played with TCPSERVER a little more this morning and I'm still unable to
connect to port 25 (telnet listserv.genexchange.com 25) but if I run 'ps ax'
I don't see anything running that would be using port 25 either. I have
already removed SMTP from xinetd.d so I know xinetd isn't trying to bind
port 25, but if it was I should be able to connect to it right? So perhaps
I thought I didn't set up tcpserver correctly and decided to go back through
the steps again.
I downloaded the tar to /usr/local/src/ and then untarred it to
/usr/local/src/ucspi-tcp-0.88 and ran 'make' and then 'make setup check' in
that directory. Then as Dan's installation instructions
(ftp://koobera.math.uic.edu/www/ucspi-tcp/install.html) indicates I
"installed" tcpserver to /usr/local/ but I don't see any changes, or
anything different than from last night. I ran 'install -d /usr/local/' but
nothings changed, nor do I see any new directories or files in /usr/local/.
That has to be the problem I would think because nothing else is using port
25 on this system.
running install --help indicates installation can be done in one of three
methods. I chose the third option orignally but just now tried a simpler
option (the second) as such "install /usr/local/ucspi-tcp-0.88/ /usr/local/"
and got the following error
install: basename.c:67: base_name: Assertion 'all_slashes || *(p-1) |= '/''
failed.
aborted (core dumped)
Anthony
Dropping smtp back into /etc/xinetd.d/ allows me to connect to port 25 again
so I know I think that pretty conclusively indicates I did not "install"
tcpservers correctly.
Anthony
On Thu, Nov 02, 2000 at 08:14:10PM -0500, Alex Pennace wrote:
[...]
> alex@buick:~$ telnet mail01.sherwin.com smtp
> Trying 148.141.15.156...
> Connected to mail01.sherwin.com.
> Escape character is '^]'.
> 220
>********************************************************0******************2*****2000
>******02**0*00
> EHLO buick.978.org
> 500 Syntax error, command "XXXX buick.978.org" unrecognized
> QUIT
> 221 ehub1.sherwin.com SMTP Service closing transmission channel
>
> This proves my theory that there is a very broken firewall product out
> there that corrupts the banner and ESMTP stuff on SMTP connections. We
> at UML are fortunate enough to be "protected" by this product as well
> (check out SMTP @ buick.978.org, and no those asterisks are NOT what
> gets sent). Of course, it breaks ESMTP, but who cares? We have to
> protect broken mailers.
This looks like what the Cisco PIX firewall does.
--
Albert Hopkins
Sr. Systems Specialist
Dynacare Laboratories
[EMAIL PROTECTED]
You know you work in corporate America in the 90's being sick is defined as
can't walk or you're in the hospital.
> > 220
> ********************************************************0*****
> *************2*****2000 ******02**0*00
> > EHLO buick.978.org
> > 500 Syntax error, command "XXXX buick.978.org" unrecognized
> > QUIT
> > 221 ehub1.sherwin.com SMTP Service closing transmission channel
> >
> This looks like what the Cisco PIX firewall does.
Yes, that is a Cisco PIX firewall.
To turn off this "feature" just add the command "no fixup protocol
smtp 25" to the configuration on the PIX.
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
Is there a way to prevent qmail smtp from sending error 451? Rumor has
it that there was a qmail bug where extra newlines in the email message
generated a 451 response.
We think we are running the latest stable version under Linux.
Thanks!
Tom.
--
804.951.3844
[EMAIL PROTECTED]
http://calendar.yahoo.com/public/twl8n
Tom Laudeman <[EMAIL PROTECTED]> wrote:
> Is there a way to prevent qmail smtp from sending error 451?
Why would you want to? qmail only sends this when it detects an error.
> Rumor has it that there was a qmail bug where extra newlines in the email
> message generated a 451 response.
Rumor is wrong; there is no such bug. The bug is in some other MTAs which
send bare linefeeds.
See http://cr.yp.to/docs/smtplf.html for details.
> We think we are running the latest stable version under Linux.
That would be 1.03, yes?
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 Fri, Nov 03, 2000 at 11:18:36AM -0500, Tom Laudeman wrote:
> Is there a way to prevent qmail smtp from sending error 451? Rumor has
> it that there was a qmail bug where extra newlines in the email message
> generated a 451 response.
You run your systems based on rumours you hear? Doesn't sound like a very
sensible policy to me...
> We think we are running the latest stable version under Linux.
Are you or aren't you? what version are you running?
Michael.
Why would you not want to send a 451? Here's
two reasons:
1) Why send a 451 back to a broken MTA who's sending you
emails with bare newlines? It's very unlikely that someone
is going to fix their MTA while the email destined to you
is still in the queue so it would get fixed before the
final retry. So switch it to a 553 just to keep the
other MTA from bothering you again.
2) Some broken MTAs like Microsoft's SMTP Service will
ignore that 451 when it is a newline failure and hit your
server as often as the data connection between the two
will allow. On a big pipe, this can really kill your
connection. I have edited my qmail-smtpd.c to replace
the 451 with a 553 for the smtplf issue.
Dave
-----Original Message-----
From: Charles Cazabon
To: [EMAIL PROTECTED]
Sent: 11/3/00 11:20 AM
Subject: Re: Error 451
Tom Laudeman <[EMAIL PROTECTED]> wrote:
> Is there a way to prevent qmail smtp from sending error 451?
Why would you want to? qmail only sends this when it detects an error.
You don't mean the Fahrenheit error, do you? That one means that your
qmail-send has processed one too many flames. ;o)
At 09:20 AM 11/3/2000, Charles Cazabon wrote:
>Tom Laudeman <[EMAIL PROTECTED]> wrote:
> > Is there a way to prevent qmail smtp from sending error 451?
>
>Why would you want to? qmail only sends this when it detects an error.
>
> > Rumor has it that there was a qmail bug where extra newlines in the email
> > message generated a 451 response.
>
>Rumor is wrong; there is no such bug. The bug is in some other MTAs which
>send bare linefeeds.
>
>See http://cr.yp.to/docs/smtplf.html for details.
>
> > We think we are running the latest stable version under Linux.
>
>That would be 1.03, yes?
>
>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.
>-----------------------------------------------------------------------
> Is there any way that I can use the same NT Domain Logon based system (the
file)
> to auth my further QMail users when checking their mail.
The trick is to use NIS. This enables a centralized server to control all
your user authentication information, instead of having each computer have
/etc/passwd and /etc/shadow files, or the NT equivalent.
There are NIS clients and servers for NT, all bundled with other stuff in a
package called Services for UNIX. My company subscribes to MSDN, and we
installed Services for Unix from somewhere within that monster load of CDs.
I'm afraid I'm not aware of how to get this package elsewhere, nor do I have
any experience in how to set it up for NIS; we're using the package to
provide NFS shares from an NT box. Scrounge around on M****s***'s web pages
and see where you can get this package (assuming you don't have an MSDN
subscription). A word of warning: the documentation for Services for UNIX
is spaghetti.
---Kris Kelley
You might find something in SAMBA (www.samba.org).
Henry
> Hello to everyone, My company has the mail server running on Exchange
> 5.0 (needles to say it works like hell) and I would like to move all
> the accounts on Linux QMail:PROBLEM: Is it possible to authentificate
> the QMail users against the an NT station? -->(at this time when the
> user logs on to check his mail on Exchnage he uses the same user/pass
> that he uses to log on to the local domain) <--I mean ... Is there any
> way that I can use the same NT Domain Logon based system (the file) to
> auth my further QMail users when checking their mail. If so PLEASE
> tell me how or give me some links... Thank youRegards,Victor
begin:vcard
n:Baragar;Henry
tel;cell:416-453-5626
tel;work:416-453-5626
x-mozilla-html:TRUE
url:www.instantiated.on.ca
org:Instantiated Software Inc.
adr:;;130 Banff Road;Toronto;Ontario;M4P 2P5;Canada
version:2.1
email;internet:[EMAIL PROTECTED]
title:Principal
fn:Henry Baragar
end:vcard
Well, we all had to start somewhere didn't we? Did you know everything
about MTAs the first time you installed one? I am almost completely new to
Unix systems but have had many years experience on various other platforms.
I am the first to admit that I am used to commercial, expensively
documented and supported software and am finding the Open Source ideas
quite a culture shock. I did in fact read everything I could find about
qmail and its peripheral programs, but it isn't so easy when everything I
read told me to install it in a different way. What else was I suppose to do?
I have got qmail working now. I have a few little bugs to sort out but I'm
sure that I will. This would not have been possible without the kind help
of a number of people on the mailing list who solved my problems. They
didn't have to help me at all of course! If you are sure your script works
then great, it most certainly is something I have done wrong but nobody
came up with a better explanation than chopping out all the delivery rules
except the ./Maildir/ bit (which I do understand BTW)
Anyway, just you wait until I'm a Unix expert!!!! You might need to give me
a few years though at this rate.
Howard Miller
(Long suffering NT - yes NT - sysadmin/developer)
At 10:47 03/11/00 -0500, you wrote:
>On Fri, Nov 03, 2000 at 09:16:24AM -0800, Howard Miller wrote:
> > Not a clue, but it still didn't work for me, my system was trying to send
> > to " __./Maildir/" (the underscores are for real). It was help from
> guys on
> > the qmail mailing list that suggested that the rc script didn't look
> > correct. Getting rid of all the do-forward stuff got it working. To be
> > honest (and excuse my ignorance, I am an MTA newbie) I don't see what
> > dot-forward does anyway, my system seems to do what I need without it.
> I am
> > not upgrading from sendmail however.
>
>I've seen your posts on the qmail mailing list, and it's obvious that you
>don't know what you're doing. If you don't know what a program does, then
>you certainly shouldn't be installing it on your system, regardless of what
>some HOWTO says.
>
> > Howard
> >
> > PS I have got lots and lots of real work to do. If I send you an email
> > amout your HOWTO its because I am trying to help. I followed your
> otherwise
> > excellent howto to the letter - it is quite clear and easy to follow, but
> > it didn't work. I am sure other people will have similar problems.
>
>Funny, you're the only person who's had this particular problem. I've set up
>almost all of my customers with that exact same /var/qmail/rc and I've never
>had a problem.
>
>--Adam
On Fri, Nov 03, 2000 at 04:16:55PM -0800, Howard Miller wrote:
> Well, we all had to start somewhere didn't we? Did you know everything
> about MTAs the first time you installed one? I am almost completely new to
> Unix systems but have had many years experience on various other platforms.
> I am the first to admit that I am used to commercial, expensively
> documented and supported software and am finding the Open Source ideas
> quite a culture shock. I did in fact read everything I could find about
> qmail and its peripheral programs, but it isn't so easy when everything I
> read told me to install it in a different way. What else was I suppose to do?
>
> I have got qmail working now. I have a few little bugs to sort out but I'm
> sure that I will. This would not have been possible without the kind help
> of a number of people on the mailing list who solved my problems. They
> didn't have to help me at all of course! If you are sure your script works
> then great, it most certainly is something I have done wrong but nobody
> came up with a better explanation than chopping out all the delivery rules
> except the ./Maildir/ bit (which I do understand BTW)
>
> Anyway, just you wait until I'm a Unix expert!!!! You might need to give me
> a few years though at this rate.
Maybe by then you'll realize how rude it is to take a private e-mail and post
it to a mailing list.
Fucking asshole.
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> | "No matter how much it changes,
http://flounder.net/publickey.html | technology's just a bunch of wires
GPG: 17A4 11F7 5E7E C2E7 08AA | connected to a bunch of other wires."
38B0 05D0 8BF7 2C6D 110A | Joe Rogan, _NewsRadio_
11:28am up 146 days, 9:44, 9 users, load average: 0.04, 0.03, 0.00
Howard Miller <[EMAIL PROTECTED]> writes on 3 November 2000 at 16:16:55
-0800
> Well, we all had to start somewhere didn't we? Did you know everything
> about MTAs the first time you installed one? I am almost completely new to
> Unix systems but have had many years experience on various other platforms.
> I am the first to admit that I am used to commercial, expensively
> documented and supported software and am finding the Open Source ideas
> quite a culture shock. I did in fact read everything I could find about
> qmail and its peripheral programs, but it isn't so easy when everything I
> read told me to install it in a different way. What else was I suppose to do?
No insult intended here; but there is in fact something I consider an
obvious step when things aren't working and your sources recommend
different installation approaches.
You could try to debug the problem.
You know, return to the man pages for the actual pieces of qmail, or
even the sources if the man pages don't say what you need (I didn't
need to look at sources for installation myself); figure out what the
different installation procedures you have are trying to do; and see
if what you actually did is something that might work.
An MTA is a highly configurable entity, and installing and configuring
that level of software is in my experience always a process of
development and debugging.
> I have got qmail working now. I have a few little bugs to sort out but I'm
> sure that I will. This would not have been possible without the kind help
> of a number of people on the mailing list who solved my problems. They
> didn't have to help me at all of course! If you are sure your script works
> then great, it most certainly is something I have done wrong but nobody
> came up with a better explanation than chopping out all the delivery rules
> except the ./Maildir/ bit (which I do understand BTW)
>
> Anyway, just you wait until I'm a Unix expert!!!! You might need to give me
> a few years though at this rate.
Well, it's an amazing amount simpler than NT, so maybe not as long as
you think!
--
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/
Photos: http://dd-b.lighthunters.net/
>Date: Fri, 03 Nov 2000 16:59:04 -0800
>To: Adam McKenna <[EMAIL PROTECTED]>
>From: Howard Miller <[EMAIL PROTECTED]>
>Subject: Re: More trouble
>Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
>
>Yes, well it's remarkably easy to talk big when you on the other side of
>the Atlantic isn't it? I haven't at any stage been rude to anybody.
>
>I may be no expert, but that does not in any way shape or form give you
>the right to talk to me in that manner. You might like to think about the
>impression you are giving to somebody new to the Unix world - a great start!
>
>Grow up, and get a grip on yourself. You are obviously a professional
>person. I am disgusted!
>
>Oh.... and I posted this to the mailing list as well. I am sure everybody
>will be interested! in your behaviour!!
>
>At 11:30 03/11/00 -0500, you wrote:
>>On Fri, Nov 03, 2000 at 04:16:55PM -0800, Howard Miller wrote:
>> > Well, we all had to start somewhere didn't we? Did you know everything
>> > about MTAs the first time you installed one? I am almost completely
>> new to
>> > Unix systems but have had many years experience on various other
>> platforms.
>> > I am the first to admit that I am used to commercial, expensively
>> > documented and supported software and am finding the Open Source ideas
>> > quite a culture shock. I did in fact read everything I could find about
>> > qmail and its peripheral programs, but it isn't so easy when everything I
>> > read told me to install it in a different way. What else was I suppose
>> to do?
>> >
>> > I have got qmail working now. I have a few little bugs to sort out but
>> I'm
>> > sure that I will. This would not have been possible without the kind help
>> > of a number of people on the mailing list who solved my problems. They
>> > didn't have to help me at all of course! If you are sure your script
>> works
>> > then great, it most certainly is something I have done wrong but nobody
>> > came up with a better explanation than chopping out all the delivery
>> rules
>> > except the ./Maildir/ bit (which I do understand BTW)
>> >
>> > Anyway, just you wait until I'm a Unix expert!!!! You might need to
>> give me
>> > a few years though at this rate.
>>
>>Maybe by then you'll realize how rude it is to take a private e-mail and post
>>it to a mailing list.
>>
>>Fucking asshole.
>>
>>--Adam
>>
>>--
>>Adam McKenna <[EMAIL PROTECTED]> | "No matter how much it changes,
>>http://flounder.net/publickey.html | technology's just a bunch of wires
>>GPG: 17A4 11F7 5E7E C2E7 08AA | connected to a bunch of other wires."
>> 38B0 05D0 8BF7 2C6D 110A | Joe Rogan, _NewsRadio_
>> 11:28am up 146 days, 9:44, 9 users, load average: 0.04, 0.03, 0.00
Quoting Howard Miller ([EMAIL PROTECTED]):
> >Oh.... and I posted this to the mailing list as well. I am sure everybody
> >will be interested! in your behaviour!!
Excuse me, Howie, but STOP posting private messages to the list
just to spite people. We have some real work to do here. Goodness.
Aaron
On Fri, Nov 03, 2000 at 05:05:11PM -0800, Howard Miller wrote:
> >Yes, well it's remarkably easy to talk big when you on the other side of
> >the Atlantic isn't it? I haven't at any stage been rude to anybody.
You've been rude to everyone on the list. The fact that you didn't think you
were being rude doesn't excuse you.
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> | "No matter how much it changes,
http://flounder.net/publickey.html | technology's just a bunch of wires
GPG: 17A4 11F7 5E7E C2E7 08AA | connected to a bunch of other wires."
38B0 05D0 8BF7 2C6D 110A | Joe Rogan, _NewsRadio_
1:26pm up 146 days, 11:42, 10 users, load average: 0.01, 0.01, 0.00
At 11:10 AM 11/3/2000, Aaron L. Meehan wrote:
>Quoting Howard Miller ([EMAIL PROTECTED]):
> > >Oh.... and I posted this to the mailing list as well. I am sure everybody
> > >will be interested! in your behaviour!!
>
>Excuse me, Howie, but STOP posting private messages to the list
>just to spite people. We have some real work to do here. Goodness.
>
>Aaron
Is it time for shock therapy yet? :o)
or are we still in the "firm-talking-to" stage?
"Describe in single words only the good things that come to mind about.....
your mother."
"My mother? I'll tell you about my mother."
Jer
Aaron, I am very sorry it won't happen again.
I was really quite upset by Mr. McKenna's attitude. I questioned as aspect of
his HOWTO and he became very personal and insulting. I have had a great deal of
help from this list and wouldn't have got my system running without it. His
attitude was quite shocking to me, I hope though that it is not typical.
Cheers.... "Howie"
"Aaron L. Meehan" wrote:
> Quoting Howard Miller ([EMAIL PROTECTED]):
> > >Oh.... and I posted this to the mailing list as well. I am sure everybody
> > >will be interested! in your behaviour!!
>
> Excuse me, Howie, but STOP posting private messages to the list
> just to spite people. We have some real work to do here. Goodness.
>
> Aaron
I maybe entirely dense, but I don't get how the Maildir patches for pine
are supposed to work. I've successfully patched and built pine-4.30 on
FreeBSD-3.4-RELEASE, but I'm stymied: how do I get the equivalent of
mutt -f ~Maildir? Thanks a lot in advance,
Robin
--
Robin S. Socha (RSS110-RIPE) http://socha.net/
"If you are too low a lifeform to be able to learn how to use the
manual page subsystem, why should we help you?" (Theo de Raadt)
* Robin S. Socha <[EMAIL PROTECTED]> [001103 12:08]:
> I may be entirely dense
s/may be/am/g Damn, I suck... Sorry for the interruption. Now on with
the show.
I was wondering if there was a way to force a queue run with qmail. For
sendmail we would do:
sendmail -q0 -v
The -v is optional, of course. Since qmail handles the queue and retries
differently I suspect that trying to do this is irrelevant. I am
experimenting with qmail for the first time and the question came to me as
I was looking at the queue and solving some local delivery problems.
Warren
> I was wondering if there was a way to force a queue run with
> qmail.
Find the qmail-send process and send it a kill -ALRM. See the FAQ
entry at:
http://cr.yp.to/qmail/faq/admin.html#queuerun
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
Send qmail-send an ALRM signal. Better yet, if you configure qmail to use
daemontools you can use the system V style script Dave Sill provides in his
"Life with Qmail" page. IMHO you should read his page from start to finish
before you even begin to install qmail. It's a must read.
regards,
--jtb
> From: Warren Small <[EMAIL PROTECTED]>
> Organization: Mainstream EIS
> Date: Fri, 03 Nov 2000 13:54:20 -0500
> To: [EMAIL PROTECTED]
> Subject: Force Queue run
>
> I was wondering if there was a way to force a queue run with qmail. For
> sendmail we would do:
>
> sendmail -q0 -v
>
> The -v is optional, of course. Since qmail handles the queue and retries
> differently I suspect that trying to do this is irrelevant. I am
> experimenting with qmail for the first time and the question came to me as
> I was looking at the queue and solving some local delivery problems.
>
> Warren
>
Jon,
Does this work for you? I was trying to get it up and running, didn't work,
so I added a few debugging printf's and noticed that it looks up
Domain: 0.0.2.151.relays.orbs.org
For each message no matter what's in the "Received" line..
I also wanted to say thanks for starting the development on this.. I was
looking for something like this!
-j
----- Original Message -----
From: "Jon Rust" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 02, 2000 1:08 PM
Subject: ANNOUNCE: qrblcheck -- rbl checking for .qmail
> I took rblcheck and added some extra code to read a message from stdin,
> find the IP of the last relay. It then compares a rating, based on
> running lookups against various RBL-style lists, against the value
> supplied on the command line. These mods make it suitable to be used in
> a .qmail file.
>
> In other words, it looks for the first instance of this type of line:
>
> Received: from mail.domain.com (HELO domain.com) (12.34.56.78)
>
> It will grab the IP in ()'s and feed it into the rblcheck routine
> written by Edward Marshall. The rblcheck routine(s) has been modified to
> return a value based on which list(s) matched. Namely:
>
> rbl.maps.vix.com = 16
> dul.maps.vix.com = 8
> relays.mail-abuse.org = 4
> outputs.orbs.org = 2
> relays.orbs.org = 1
>
> Add all values of lists that matched together, and compare it to the
> value supplied on the command line. If the returned value is less than
> or equal to the command line value, qrblcheck returns code 0, which
> tells qmail to continue delivery. If the value is greater than that
> supplied on the command line, qrblcheck returns 100 which tells qmail to
> stop all deliveries and return the message.
>
> If, for whatever reason, no IP was found, qrblcheck returns 0 (mail is
> accepted).
>
> EXAMPLE:
>
> Putting "|qrblcheck 15" on the first line of your .qmail file will block
> any mail that matches rbl.maps.vix.com. Instead, using "|qrblcheck 1"
> will reject mail that matches all the lists except for relays.orbs.org.
>
> Download the source at
>
> http://jon.rusts.net/qrblcheck.c
>
> I'm not an experienced C programmer, so feedback is welcome and
> encouraged. The biggest problem I see right now is that it will match
> bogus IP's... like 999.999.999.999, but I don't see how that would work
> it's way into headers written by qmail. Regardless, I do plan on
> implementing some sort of trap for this.
>
> It successfully compiles on FreeBSD 4.x, but can't be sure it will on
> any other system.
>
> Hopefully this will be useful to someone.
>
> jon
>
>
>
On Fri, Nov 03, 2000 at 02:48:22PM -0500, Robert J Adams wrote:
> Jon,
>
> Does this work for you? I was trying to get it up and running, didn't work,
> so I added a few debugging printf's and noticed that it looks up
>
> Domain: 0.0.2.151.relays.orbs.org
>
> For each message no matter what's in the "Received" line..
Hmmm... very odd. No, it's working fine here. I can pipe your entire
message through it and get a result of 0. Then I can change the IP in
the first Received: from header to 127.0.0.3 and it gets a rating of 10.
Send me a copy of what the headers look like on your system. Can't
really think of anything else. :-/
> I also wanted to say thanks for starting the development on this.. I was
> looking for something like this!
Well thanks. Be better if it actually worked for ya.
jon
Robert,
I have reproduced your problem... err my problem. I'm looking into it
now.
jon
All fixed. Please try it out now and tell me what you think.
Jon
Hi...
I just installed QMail, I follow all indications of "Life with qmail", but
I have a trouble when
% telnet 127.0.0.1 110
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Connection closed by foreign host.
Searching on http://www.ornl.gov/its/archives/mailing-lists/qmail/ I found
this
"Try running
strace -vs 512 -o out -f \
/var/qmail/bin/qmail-popup qmail-popup juara.com /usr/sbin/logpopauth-pre \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir
there may be a hint around the end of the file "out".
"
And works !!!, So I guess the problem is at the port's (25 and 110)
configuration....
Any idea....I have looking for 3 days ago....
Ing. J@vier Morquecho Morquecho
Cedetel
Desarrollo de proyectos comerciales
Tel : 177-10-87
Cel : 177-00-87
e-mail : [EMAIL PROTECTED]
e-movil : [EMAIL PROTECTED]
Home Cedetel : http://www.cedetel.com.mx
"#define QUESTION ((bb) || !(bb)) // Shakespeare"
> % telnet 127.0.0.1 110
> Trying 127.0.0.1...
> Connected to 127.0.0.1.
> Escape character is '^]'.
> Connection closed by foreign host.
...
> Any idea....I have looking for 3 days ago....
Use 'lsof' to verify that the program you think is listening to
those ports, is the program listening to those ports.
If you modified your inetd.conf so that inetd was listening to those
ports but didn't have a valid program to run, that would cause this problem.
Inetd would probably be listening to the ports rather than tcpserver because
it runs earlier.
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
Did you read the excellent FAQ that Dan bundles with
the qmail distribution?
Section 5. Setting up servers covers this pretty well.
Hope this helps.
Gerry
At 04:52 PM 11/3/2000 -0600, Javier Morquecho Morquecho wrote:
>Hi...
>
> I just installed QMail, I follow all indications of "Life with
> qmail", but
>I have a trouble when
>% telnet 127.0.0.1 110
>Trying 127.0.0.1...
>Connected to 127.0.0.1.
>Escape character is '^]'.
>Connection closed by foreign host.
>
> Searching on
> http://www.ornl.gov/its/archives/mailing-lists/qmail/ I found
>this
>
>"Try running
>strace -vs 512 -o out -f \
> /var/qmail/bin/qmail-popup qmail-popup juara.com /usr/sbin/logpopauth-pre \
> /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir
>there may be a hint around the end of the file "out".
>"
>
> And works !!!, So I guess the problem is at the port's (25 and 110)
>configuration....
>
>Any idea....I have looking for 3 days ago....
>
>Ing. J@vier Morquecho Morquecho
>Cedetel
>Desarrollo de proyectos comerciales
>Tel : 177-10-87
>Cel : 177-00-87
>e-mail : [EMAIL PROTECTED]
>e-movil : [EMAIL PROTECTED]
>Home Cedetel : http://www.cedetel.com.mx
>
>"#define QUESTION ((bb) || !(bb)) // Shakespeare"
hi,
i am running a webserver with fine working qmail on it. a friend of mine
has an own server, too. now, we would like to configure the follwing.
his qmail-server should act as backup-mailserver for my system and my
qmail-server should be his back-mailserver.
the question now is, if it is enought to put our mailsystems with priority
of 20 in each dns-zone files ?? how to configure each mailsystem to accept
and store mails of the other system ???
--
jens
---------------------------------------------------------------------------
instant networks - netzwerkmanagment & internetfullservices
http://www.instant-networks.de
On Sat, Nov 04, 2000 at 03:16:59AM +0100, Jens Georg wrote:
[snip]
> his qmail-server should act as backup-mailserver for my system and my
> qmail-server should be his back-mailserver.
>
> the question now is, if it is enought to put our mailsystems with priority
> of 20 in each dns-zone files ?? how to configure each mailsystem to accept
> and store mails of the other system ???
On a qmail-server, to run fallback for a domain, put that domain in
rcpthosts or morercpthosts and *not* in locals and/or virtualdomains.
man qmail-control and man qmail-smtpd for more info.
Greetz, Peter
--
dataloss networks
'/ignore-ance is bliss' - me
'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me
|
Dear Sir,
Can you send
me the qmail configuration details, with integrating qmail with virtual
domains.
regards,
Manu
|
Hi,
Is there any way to limit the size (quota) of outgoing SMTP data in
qmail ? I'd like to limit a qmail-send outgoing size to 10MB. My users
are making constant overloads on my bandwidth...
Tks.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Eduardo Augusto Alvarenga - Analista de Suporte - #179653
Blumenau - Santa Catarina. Tel. (47) 9102-3303
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/"\
\ / Campanha da Fita ASCII - Contra Mail HTML
X ASCII Ribbon Campaign - Against HTML Mail
/ \
On Sat, Nov 04, 2000 at 05:06:57AM -0200, Eduardo Augusto Alvarenga wrote:
> Hi,
>
> Is there any way to limit the size (quota) of outgoing SMTP data in
> qmail ? I'd like to limit a qmail-send outgoing size to 10MB. My users
> are making constant overloads on my bandwidth...
echo 10485760 > /var/qmail/control/databytes
Greetz, Peter
--
dataloss networks
'/ignore-ance is bliss' - me
'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me
Hi,
I was runing RH 6.2. Qmaill was OK. SMTP and POP3 worked.
Now I've switched to RH7 and I can connect neither to SMTP nor POP3.
Qmail starts. SMTP and POP3 is started with tcpserver and supervised. I can
send mail to locals and to remotes. But I can not receive mails from remote
(connection refused) and I can not connect to POP3 at all.
Trying: telnet 212.244.57.120 25
I get:
Trying 212.244.57.120
Connected to 212.244.57.120
Escape character is "^]"
and that's all.
What to to? The inetd is replaced with xinetd.
There are proper (I hope) entries in /etc/services:
smtp 25/tcp mail
.
.
pop3 110/tcp pop-3
pop3 110/udp pop-3
I hope it's a kind of silly mistake, but I have no idea what kind.
Waiting for any answer.
Przemek
Sean Reifschneider wrote:
>
> On Wed, Nov 01, 2000 at 12:53:27PM +0000, Greg Cope wrote:
> >Out of interest does the Netfilter have a large / battery backed cache
> >to decrease the I/O / disk bottle neck ?
>
> Yes. They have a chunk of NVRAM which ACKs the write request as soon as it's
> committed there. This gives it the ability to ack write messages very quickly
> while still ensuring that the data is resiliant to crashes.
So you are avoiding one big bottle neck - the disks.
Also sending one message will reduce the I/O required compared to n
messages.
> >Also does your system only send one message - the ones I deal with are
> >all individual (both in content and message headers).
>
> That's the problem. It's relatively slow throwing a bunch of messages
> into QMail. It doesn't take a very powerful machine to completely swamp
> a fairly hefty QMail server, I've found. And since the smtp daemons
> are fat, dumb, and happy individual processes, they don't really have the
> smarts to do any sort of throttling on incoming connections.
>
> We ended up having to implement that sort of thing externally so that the
> originating program wouldn't swamp the box.
What about using tcpserver to limit the inbound connections - or even
move this to another box (if you can split the list like that).
I've used mutiple outbound boxes and a single inbound box to deal with
bounces etc ...
<snippage>
Greg
>
> Sean
> --
> Laws are the source code to our government. Submit a patch November 7.
> VOTE! November 7, 2000
> Sean Reifschneider, Inimitably Superfluous <[EMAIL PROTECTED]>
> tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
Markus Stumpf wrote:
>
> On Thu, Nov 02, 2000 at 02:54:10PM -0700, Sean Reifschneider wrote:
> > That's the problem. It's relatively slow throwing a bunch of messages
> > into QMail. It doesn't take a very powerful machine to completely swamp
> > a fairly hefty QMail server, I've found.
>
> I think the main problem is within qmail-send.
> qmail doesn't use concurrencies to their max as long as there are still
> unprocessed messages in the queue or the deliveries generate a lot of
> bounces.
This sounds like a bumber for what I want it to do ...
> We have a customers that injects about 15000 single messages in bunches
> of 100 messages to a dedicated qmail server. Sadly the "list" isn't too
> well administrated and even after the queue has reached a status where
> you have no unprocessed messages at one point the bounces slow down
> qmail quite a lot.
> I have generated a graph from the
> qmail: 973205710.228381 status: local 0/120 remote 1/120
> lines which show this "waving" behaviour. I'd posted that info to the
> list some time ago, but anyway, here's the URL for that graph (10 KB) again:
>
> http://www.lamer.de/maex/creative/software/qmail/deliver-stats.gif
>
> The lot of local deliveries are due to the QUEUE_EXTRA delivery we have
> for accounting reasons.
>
> I have made a second graph. This is also a dedicated qmail server
> running a mailinglist (newsletter) with approx 91000 subscribers.
> The graph is one "shot". As the mailing-list is run by ezmlm there are
> very few bounces and only some occasional (un-)subscribe messages.
> This time qmail keeps the concurrency at max. The second and third
> shorter peaks are due to deferred messages tried again after backoff.
> The image (40 KB) is at
>
> http://www.lamer.de/maex/creative/software/qmail/deliver-stats2.gif
>
> I know it would be better to also have some figures about messages
> in queue, unprocessed messages in queue, successful/deferred deliveries
> included, but those are hard to extract from the logfile :/
>
> I think a big gain in performance would be to split up the scheduler
> in qmail-send into at least one for remote, one for locals and one
> for sorting in new messages into the remote or local queue.
These graphs were quite interesting - and seem to backup evidence that
I've seen (in that concurrency remote is not hit untill injection
stops).
Assuming an outbound machine is being used (and another machine for
inbound / bounces)
Hence to improve performance inject should be split up i.e inject 2000,
wait, inject another 2000. In the wait times concurrency remote would
be reached.
Any ideas on what a good number to try would be for inject / wait cycle
?
Also is changing the scheduler easy ?
Interesting stuff - thanks.
Greg
>
> \Maex
>
> --
> SpaceNet GmbH | http://www.Space.Net/ | Stress is when you wake
> Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
> Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
> D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
