qmail Digest 7 Sep 1999 10:00:01 -0000 Issue 752
Topics (messages 29874 through 29937):
Check the RCPT TO: against
29874 by: "Einar Bordewich" <[EMAIL PROTECTED]>
29885 by: Balazs Nagy <[EMAIL PROTECTED]>
29891 by: Sam <[EMAIL PROTECTED]>
29914 by: "Einar Bordewich" <[EMAIL PROTECTED]>
patch wanted: add maildir to elm
29875 by: Anand Buddhdev <[EMAIL PROTECTED]>
Setting qmail to be a local server and a gateway
29876 by: Anand Buddhdev <[EMAIL PROTECTED]>
Error message in mail.log
29877 by: Anand Buddhdev <[EMAIL PROTECTED]>
Header Rewriting in Qmail
29878 by: Farooq Ashraf <[EMAIL PROTECTED]>
Starting qmail for maildir
29879 by: "Jean-Pierre H. Dumas" <[EMAIL PROTECTED]>
qmail and > 4,000 users ?
29880 by: Chris McCarthy <[EMAIL PROTECTED]>
29881 by: [EMAIL PROTECTED]
29882 by: Anand Buddhdev <[EMAIL PROTECTED]>
29883 by: Balazs Nagy <[EMAIL PROTECTED]>
29884 by: "Markus Storm" <[EMAIL PROTECTED]>
29886 by: Russell Nelson <[EMAIL PROTECTED]>
29887 by: Krzysztof Dabrowski <[EMAIL PROTECTED]>
29888 by: Sam <[EMAIL PROTECTED]>
29893 by: "Robin Bowes" <[EMAIL PROTECTED]>
29896 by: [EMAIL PROTECTED]
29906 by: "Robin Bowes" <[EMAIL PROTECTED]>
maildir subfolders?
29889 by: Jukka Zitting <[EMAIL PROTECTED]>
29890 by: "David Harris" <[EMAIL PROTECTED]>
29892 by: Sam <[EMAIL PROTECTED]>
29894 by: Robert Varga <[EMAIL PROTECTED]>
29907 by: Daemeon Reiydelle <[EMAIL PROTECTED]>
29908 by: Sam <[EMAIL PROTECTED]>
29912 by: Daemeon Reiydelle <[EMAIL PROTECTED]>
spawn connection
29895 by: Robert <[EMAIL PROTECTED]>
29909 by: Daemeon Reiydelle <[EMAIL PROTECTED]>
testing for an open relay
29897 by: "Ben Beuchler" <[EMAIL PROTECTED]>
29911 by: "Ben Beuchler" <[EMAIL PROTECTED]>
29913 by: Russell Nelson <[EMAIL PROTECTED]>
29930 by: [EMAIL PROTECTED] (John R. Levine)
Problems getting started
29898 by: "Michael" <[EMAIL PROTECTED]>
29899 by: "Adam D . McKenna" <[EMAIL PROTECTED]>
29920 by: [EMAIL PROTECTED]
RAID 5 and queue restore
29900 by:
29903 by: Sam <[EMAIL PROTECTED]>
29910 by: Daemeon Reiydelle <[EMAIL PROTECTED]>
Problems with qmail and dns
29901 by: [EMAIL PROTECTED]
29904 by: Brad Shelton <[EMAIL PROTECTED]>
29905 by: Magnus Bodin <[EMAIL PROTECTED]>
fastforward: wildcards
29902 by: Kush <[EMAIL PROTECTED]>
Started!
29915 by: James <[EMAIL PROTECTED]>
29921 by: Dustin Marquess <[EMAIL PROTECTED]>
29929 by: Chris Johnson <[EMAIL PROTECTED]>
checking email
29916 by: James <[EMAIL PROTECTED]>
29917 by: Magnus Bodin <[EMAIL PROTECTED]>
29918 by: James <[EMAIL PROTECTED]>
29919 by: Magnus Bodin <[EMAIL PROTECTED]>
IMAP/Maildir
29922 by: Sam <[EMAIL PROTECTED]>
29923 by: "David Harris" <[EMAIL PROTECTED]>
29924 by: Tim Tsai <[EMAIL PROTECTED]>
29925 by: Sam <[EMAIL PROTECTED]>
Stuck at bootup
29926 by: James <[EMAIL PROTECTED]>
29927 by: James <[EMAIL PROTECTED]>
29932 by: James <[EMAIL PROTECTED]>
Maildir and Pine-4.10
29928 by: Josh Pennell <[EMAIL PROTECTED]>
qmailanalog scripts
29931 by: "Ron 'The InSaNe One' Rosson" <[EMAIL PROTECTED]>
Stuck at bootup solved
29933 by: James <[EMAIL PROTECTED]>
limiting the file size of bounces ?
29934 by: torben fjerdingstad <[EMAIL PROTECTED]>
29935 by: Van Liedekerke Franky <[EMAIL PROTECTED]>
.qmail - deliveries and bounces
29936 by: Markus Stumpf <[EMAIL PROTECTED]>
Security Issue on qmail
29937 by: [EMAIL PROTECTED]
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
I must confess that I'm a little unsure what I really want...... My problem is that
95% of bounced mail, is typical doublebounce, where a user that don't exist anymore
(at my servers) has received mail and that bounce at my side. A spamer don't use a
correct address, so I then get the doublebounce back. Another problem I then get, is
the overview of "correct" bounces where there is a misspellings of some sort, that I
then could correct. Today I don't do this a 100%, since most of the "correct" bounce
mail drowns with the rest.
I can't see that I'm helping anybody with ignoring mail to non-existing (known) users.
I think I would be more help to my customers by getting the bounces down. Then again,
I can concentrate more on the issue about open relays, by have my users (that exist)
to report back to us about SPAM mail they have received. Here I can use some more
energy to block SPAM.
I'm not to found of having non-existing addresses in the lists out there, wasting my
(costly) bandwidth.
After we started to check against maps.vix.com and relays.orbs.org, the doublebounce
has gone down a little bit, but it's still to high. Anyway, I think we are on the
right track blocking traffic from known relays, even if I hate when persons tries to
make me do things, and I'm now in the situation trying to make other people to take
care and responsibility of their own mailservers ;)
regards
-------------------------------------------------------------------
IDG New Media Einar Bordewich
System Manager Phone: +47 2205 3034
E-Mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
----- Original Message -----
From: Russell Nelson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 05, 1999 5:39 AM
Subject: Check the RCPT TO: against
> Einar Bordewich writes:
> > What I really would like, is someone telling me how to make qmail
> > check the RCPT TO: against the actual users on my machine.
>
> Remember when some spammer got the bright idea of checking RCPT TO:
> against the users he would like to spam? Are you really sure that you
> want to give away that much information about your users?
>
> --
> -russ nelson <[EMAIL PROTECTED]> http://russnelson.com
> Crynwr sells support for free software | PGPok | Government schools are so
> 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
> Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
>
On Mon, 6 Sep 1999, Einar Bordewich wrote:
> I must confess that I'm a little unsure what I really want...... My
> problem is that 95% of bounced mail, is typical doublebounce, where a user
> that don't exist anymore (at my servers) has received mail and that bounce
> at my side. A spamer don't use a correct address, so I then get the
> doublebounce back. Another problem I then get, is the overview of
> "correct" bounces where there is a misspellings of some sort, that I then
> could correct. Today I don't do this a 100%, since most of the "correct"
> bounce mail drowns with the rest.
I have a patch for qmail which denies posting to nonexisting host names. It
does with an extra DNS query. A lot of people say that this kind of check
is obsolete but I found it very useful for this kind of bounce.
> I can't see that I'm helping anybody with ignoring mail to non-existing
> (known) users. I think I would be more help to my customers by getting the
> bounces down. Then again, I can concentrate more on the issue about open
> relays, by have my users (that exist) to report back to us about SPAM mail
> they have received. Here I can use some more energy to block SPAM.
Well, denying posting to nonexisting users is a security hole. Denying
nonexisting hosts isn't - you can get this info yourself.
--
Regards: Kevin (Balazs)
On Sat, 4 Sep 1999, Russell Nelson wrote:
> Einar Bordewich writes:
> > What I really would like, is someone telling me how to make qmail
> > check the RCPT TO: against the actual users on my machine.
>
> Remember when some spammer got the bright idea of checking RCPT TO:
> against the users he would like to spam? Are you really sure that you
> want to give away that much information about your users?
The other alternative is to swallow about a few thousand messages
addressed to a non-existent recipient, then spend another couple of hours
bouncing the whole thing back.
> I have a patch for qmail which denies posting to nonexisting host names. It
> does with an extra DNS query. A lot of people say that this kind of check
> is obsolete but I found it very useful for this kind of bounce.
Does this mean a:
Deferred: 451 <[EMAIL PROTECTED]>... Sender domain must resolve
Is the patch available for retrieval, or are you kind to attach it to me?
Or do I misunderstand you here, and this actually check to see if the host exist
before bouncing the message? If this is so, I think this probably takes away a small
amount of the doublebounces, but the common situation is that I get:
550 <[EMAIL PROTECTED]>... User unknown
when my qmail has sent away a bounce for an nonexistent recipient.
-------------------------------------------------------------------
IDG New Media Einar Bordewich
System Manager Phone: +47 2205 3034
E-Mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
----- Original Message -----
From: Balazs Nagy <[EMAIL PROTECTED]>
To: Einar Bordewich <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, September 06, 1999 3:50 PM
Subject: Re: Check the RCPT TO: against
> On Mon, 6 Sep 1999, Einar Bordewich wrote:
>
> > I must confess that I'm a little unsure what I really want...... My
> > problem is that 95% of bounced mail, is typical doublebounce, where a user
> > that don't exist anymore (at my servers) has received mail and that bounce
> > at my side. A spamer don't use a correct address, so I then get the
> > doublebounce back. Another problem I then get, is the overview of
> > "correct" bounces where there is a misspellings of some sort, that I then
> > could correct. Today I don't do this a 100%, since most of the "correct"
> > bounce mail drowns with the rest.
>
> I have a patch for qmail which denies posting to nonexisting host names. It
> does with an extra DNS query. A lot of people say that this kind of check
> is obsolete but I found it very useful for this kind of bounce.
>
> > I can't see that I'm helping anybody with ignoring mail to non-existing
> > (known) users. I think I would be more help to my customers by getting the
> > bounces down. Then again, I can concentrate more on the issue about open
> > relays, by have my users (that exist) to report back to us about SPAM mail
> > they have received. Here I can use some more energy to block SPAM.
>
> Well, denying posting to nonexisting users is a security hole. Denying
> nonexisting hosts isn't - you can get this info yourself.
> --
> Regards: Kevin (Balazs)
>
>
On Sat, Sep 04, 1999 at 10:48:26PM -0500, [EMAIL PROTECTED] wrote:
> I'm replacing/upgrading servers, and I'd like to switch to qmail.
> The change makes for an easy opportunity to do the change. But
> I have one crucial need before I can do that. I need a patch to
> elm to make it pick up mail from a maildir as stored by qmail.
>
> Has anyone put together such a patch yet?
Try elq in the qmail distribution. It's a small script that converts a
Maildor to an mbox, and then runs elm.
> Alternatives:
>
> A patch to elm to make it read via POP3 would suffice since POP3
> can be done on maildirs and it would thus be transparent to elm.
And then elm would store the mail locally in mbox format. So then why go
to the trouble of POPping the mail, when elq will suffice?
> Someone who is an internals guru with mutt who knows how to disable
> the color pallette change it does when it starts. I cannot use
> mutt until that problem is corrected. Several people have tried,
> as have I, and all have failed, so this might take a guru.
>From my experience with mutt, you'll need to make sure that mutt is
launched with a TERM environment setting that will make it not use
colours. Try TERM=vt100.
> A guide to how to configure qmail to use a different delivery
> mechanism per user, or how to configure it so it delivers in
> the usual mailbox format for local users and in maildir format
> for POP3 users.
man dot-qmail: per-user delivery controls.
--
See complete headers for more info
On Mon, Sep 06, 1999 at 03:19:04PM +0800, Mark Parker wrote:
> Hi,
>
> Is it possible to configure a qmail server to receive and store email for
> POP3 retrieval for some virtual domains, and also have it act as a gateway
> which simply forwards e-mails for other virtual domains to servers within a
> connected internal network.(all domains have MX record pointing to the qmail
> server)??
Yes. For storing mail locally for some virtual domains, use the
control/virtualdomains feature. For forwarding mail for other virtual
domains to internal hosts, use the control/smtproutes feature. Read the
man pages, especially for qmail-send and qmail-remote, and you'll be
fine.
--
See complete headers for more info
On Mon, Sep 06, 1999 at 05:40:25PM +0800, Mark Parker wrote:
Could be due to various reasons. Change directory to your qmail source,
and run "make setup check" to attempt to fix the problem. Most likely
you have altered permissions on the qmail controls directory, and so it
is unable to read the control files.
> Hi again.
>
> Have been attempting to configure the qmail server to perform sections of
> the functionality I mentioned in my previous email. However I am receiving
> an error when the qmail server attempts to forward the mail to another
> server.
>
> The error contains the phrase "Unable_to_Read_Control_Files"
>
> Does anyone now if I have made a fundamental error in my configuration which
> would result in this and a possible solution.
>
> Thanks again.
>
> Mark Parker
--
See complete headers for more info
On Sun, 5 Sep 1999, PointyBird wrote:
> Hi,
>
> If you get any useful replies, I'd greatly appreciate a copy, as I currently
> run a similar setup.
I was myself able to figure out what to do. Had to poke a little bit
into the source code. Here it is:
1. Edit the file qmail-queue.c in the source code of qmail, and comment
the last line {receivedfmt(received);} of the function
received_setup().
2. Edit the file received.c and comment the entire inside of the function
received(qqt,protocol,local,remoteip,remotehost,remoteinfo,helo).
Recompile (make setup). That does the job, no headers!!!!
Any better suggestions???
-----------------------------------------------------------
| Farooq Ashraf | Tel : (966) 3-860-5634 |
| System Admin. & Lecturer | Fax : (966) 3-860-5634 |
| College of Computer Science | |
| and Engineering (CCSE) | |
| King Fahd University of | E-Mail: |
| Petroleum & Minerals (KFUPM)| [EMAIL PROTECTED] |
| KFUPM Box 1218 | [EMAIL PROTECTED] |
| Dhahran 31261, Saudi Arabia | |
-----------------------------------------------------------
>
> I run Qmail on a second system behind the firewall. The firewall itself is a
> masquerade system which runs from a CDROM. I use 'junkbuster' as a web proxy
> to obfuscate http headers, but I don't have anything to serve a similar
> function for outgoing mail.
>
> I hope, by the way, that you'll excuse my presumption in suggesting this,
> but it's generally considered a bad idea to run anything on a firewall that
> may potentially be used to gain access to it.
>
> Best regards,
>
> Pointy
>
>
>
I am trying to run qmail with the Maildir/.
I use FreeBSD 3.2, the qmail package (binary)
If I start qmail with the provided :
qmail-start ./Mailbox splogger qmail &
everything is going OK (I am just following the
instructions in INSTALL)
But, if I change ./Mailbox for ./Maildir/ qmail does not
start, I find no messages whatsoever in thge logs.
I have 3 users with the Maildir/ installed, when I test
qmail (./Mailbox) the mail arrive in the Maildir/new
directory correctly, and all the test described in
test.DELIVER wotks OK.
I need the Maildir format to set up the POP toaster
only service.
What I am missing ?
(sendmail is still running, but it should not be problem
at this point.)
Jean-Pierre Dumas
[EMAIL PROTECTED]
(Sorry, I do not subscribe to any list, so please
cc: or to: me!)
___________________________________________________________
Do You Yahoo!?
Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr
My company wants to provide users on the internet with a free email
service ([EMAIL PROTECTED]). We'll be starting off with about
3,000 users, potentially growing up to 10,000 in the next 12 months.
How feasible is it to create a passwd/shadow entry for each user,
providing them with POP/IMAP access ? (or maybe just pop if imap puts
too much load on the server).
With the passwd and shadow files containing so many entries, will the
password lookups take forever ?
Our current server spec is a PIII 400, 256M, but we'll replace it with a
high spec server if/when needed.
Does this sound OK, or should we look at buying (or developing) hotmail
style software instead ?
Any ideas/comments appreciated,
..Chris.
begin:vcard
n:McCarthy;Chris
tel;cell:+353 86 8209078
tel;fax:+353 86 9209078
x-mozilla-html:TRUE
org:Contractor
adr:;;;Cork;;;IRELAND
version:2.1
email;internet:[EMAIL PROTECTED]
title:Software Engineer
fn:Chris McCarthy
end:vcard
At 02:10 PM 9/6/99 +0100, Chris McCarthy wrote:
>My company wants to provide users on the internet with a free email
>service ([EMAIL PROTECTED]). We'll be starting off with about
>3,000 users, potentially growing up to 10,000 in the next 12 months.
10,000 is not very many.
>
>How feasible is it to create a passwd/shadow entry for each user,
>providing them with POP/IMAP access ? (or maybe just pop if imap puts
>too much load on the server).
Entirely feasible. What problems do you anticipate in creating users?
>With the passwd and shadow files containing so many entries, will the
>password lookups take forever ?
You don't say which OS you're using, but a number of them have an optimized
/etc/passwd lookup. Failing that you can use the qmail/users database which
can be cron-ologically derived from /etc/passwd.
>
>Our current server spec is a PIII 400, 256M, but we'll replace it with a
>high spec server if/when needed.
>
>Does this sound OK, or should we look at buying (or developing) hotmail
>style software instead ?
An amount of hotmail-like s/w actually uses POP to connect to the mail
system (which seems entirely sensible to me) so unless you purchase one that
directly reads your mail store, the advantages of a web-based mail interface
would be functional ones, not performance/load ones.
>Any ideas/comments appreciated,
Of course the number of users only provides a vague hint as to the likely
load. 10,000 corporate users typically hit a mail system a lot hard then
10,000 freemail systems.
Regards.
On Mon, Sep 06, 1999 at 02:10:49PM +0100, Chris McCarthy wrote:
> My company wants to provide users on the internet with a free email
> service ([EMAIL PROTECTED]). We'll be starting off with about
> 3,000 users, potentially growing up to 10,000 in the next 12 months.
10,000 isn't that big a number. qmail should be able to handle that
easily.
> How feasible is it to create a passwd/shadow entry for each user,
> providing them with POP/IMAP access ? (or maybe just pop if imap puts
> too much load on the server).
putting all those users into passwd/shadow may very well work, but it
would depend highly on the OS. Some OS's like solaris have a text
passwd/shadow file, which needs to be scanned linearly every time a
lookup is required, and it starts to get slow as the numbers of entries
increase, especially if it is not cached in memory. the BSDs build their
passwd file into a DB for fast lookups. You might want to investigate
that. A better idea would be to put your users into a CDB, which can be
looked up very quickly. Look around on the qmail homepage for
checkpasswords that use CDB, and ideas on building a POP toaster using a
single unix uid.
> With the passwd and shadow files containing so many entries, will the
> password lookups take forever ?
>
> Our current server spec is a PIII 400, 256M, but we'll replace it with a
> high spec server if/when needed.
Should be OK to start with. You may want to add more memory to it later,
but if it's only doing email, it should be just fine. More importantly,
you should be using fast SCSI disks with it.
--
See complete headers for more info
On Mon, 6 Sep 1999, Chris McCarthy wrote:
> My company wants to provide users on the internet with a free email
> service ([EMAIL PROTECTED]). We'll be starting off with about
> 3,000 users, potentially growing up to 10,000 in the next 12 months.
It's quite common nowadays. Just keep in mind that Linux (and SCO
OpenServer) supports only 32767 userids (~32200 users by default) due of
uid_t's definition (signed short). Other systems (as Sun Solaris, HP/HPUX,
IBM/AIX) supports much more (2147483648) because of defining uid_t as int.
Thus, if your planned system would use more than 30000 users, you could
decide if you want to use a tougher system, or use virtual hosting.
> How feasible is it to create a passwd/shadow entry for each user,
> providing them with POP/IMAP access ? (or maybe just pop if imap puts
> too much load on the server).
In modern systems this data is cached or accessed by a database manager.
For example if you turn off pam in RedHat 6.0, you can use the database
feature of /var/db (it hashes /etc/group, /etc/passwd, /etc/shadow and rpc,
protocols, services list). You can turn'em on and off by
/etc/nsswitch.conf. If you want to use these gdbm hashes, I recommend you
to use a non-pam distribution of Linux.
Or you can use LDAP or SQL authentication system for virtual serving. This
sounds OK, but beware of spreading out authorization and authentication
data. This way you can easily set up a POP3 daemon on an ethernet alias
port with your special checkpassword (with PAM and the pam_ldap module).
Maybe this is the most cost-effective way if you want to give complete
solution to your users (POP3, maybe IMAP, central address book).
> Does this sound OK, or should we look at buying (or developing) hotmail
> style software instead ?
The web interface is the bottleneck. If you have enough resources to build
one, or you can hire someone to who has, that's good. There are a lot of
this kind of interface on the net, whcih can be good for you. BTW I don't
encourage you to use web interface, unless it's a requirement. I like an
IMAP-like service much better.
--
Regards: Kevin (Balazs)
Chris McCarthy wrote:
>
> My company wants to provide users on the internet with a free email
> service ([EMAIL PROTECTED]). We'll be starting off with about
> 3,000 users, potentially growing up to 10,000 in the next 12 months.
>
> How feasible is it to create a passwd/shadow entry for each user,
> providing them with POP/IMAP access ? (or maybe just pop if imap puts
> too much load on the server).
A POP demon is included w/ qmail, but IMAP is an entirely
different story.
Though 10K users can be handled using /etc/passwd without
problems, you
should consider qmail-ldap. It will give you flexibility,
scalability and
ease administration once you're familiar with it.
>
> With the passwd and shadow files containing so many entries, will the
> password lookups take forever ?
>
> Our current server spec is a PIII 400, 256M, but we'll replace it with a
> high spec server if/when needed.
>
> Does this sound OK, or should we look at buying (or developing) hotmail
> style software instead ?
>
> Any ideas/comments appreciated,
> ..Chris.
Markus
begin:vcard
n:Storm;Markus
tel;fax:++49 +5241 80-67867
tel;work:++49 +5241 80-7867
x-mozilla-html:FALSE
org:mediaWays GmbH;NTM-T
adr:;;Postfach 185;Guetersloh;;33311;Germany
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:ils.mediaways.net;-20832
fn:Markus Storm
end:vcard
[EMAIL PROTECTED] writes:
> >Our current server spec is a PIII 400, 256M, but we'll replace it with a
> >high spec server if/when needed.
>
> Of course the number of users only provides a vague hint as to the likely
> load. 10,000 corporate users typically hit a mail system a lot hard then
> 10,000 freemail systems.
Yes, but a PIII 400, 256M (how much disk space??) should be plenty of
machine for 10K users. I've got a customer with about that much
machine serving about that many users.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
> > >Our current server spec is a PIII 400, 256M, but we'll replace it with a
> > >high spec server if/when needed.
> >
> > Of course the number of users only provides a vague hint as to the likely
> > load. 10,000 corporate users typically hit a mail system a lot hard then
> > 10,000 freemail systems.
>
>Yes, but a PIII 400, 256M (how much disk space??) should be plenty of
>machine for 10K users. I've got a customer with about that much
>machine serving about that many users.
P2 - 256, 128k RAM, 8 gig scsi raid storage, serves 4000 users and few
mailing litst here.
And it works in REALTIME :)
That's about speed.
Kris
On Mon, 6 Sep 1999, Chris McCarthy wrote:
> With the passwd and shadow files containing so many entries, will the
> password lookups take forever ?
Maybe not forever, but with lotsa mail going through, it's definitely
going to be a bottleneck.
> Does this sound OK, or should we look at buying (or developing) hotmail
> style software instead ?
You don't need to buy anything. Just use some user account database.
This isn't an answer to the original question - just some thoughts...
How would vchkpw perform in this situation? (http://www.inter7.com/vchkpw/)
Presumably, the vpasswd file would be the bottleneck? Is it possible to use
vchkpw with a DB of some sort, eg CDB? Presumably, this would involve
hacking vchkpw appropriately?
R.
Chris McCarthy <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> My company wants to provide users on the internet with a free email
> service ([EMAIL PROTECTED]). We'll be starting off with about
> 3,000 users, potentially growing up to 10,000 in the next 12 months.
>
> How feasible is it to create a passwd/shadow entry for each user,
> providing them with POP/IMAP access ? (or maybe just pop if imap puts
> too much load on the server).
>
> With the passwd and shadow files containing so many entries, will the
> password lookups take forever ?
>
> Our current server spec is a PIII 400, 256M, but we'll replace it with a
> high spec server if/when needed.
>
> Does this sound OK, or should we look at buying (or developing) hotmail
> style software instead ?
>
>
> Any ideas/comments appreciated,
> .Chris.
>
>
Vchkpw handles 10k users just fine in it's current version. I'm running 200
virtual domains totaling about 10k pop accounts on a p2/300 with 256mb ram,
a couple scsi-2 drives, Apache 1.3.4, SQWebmail 0.20 on FreeBSD 3.1 and it
runs like a top. No complaints in the slightest from here as far as
performance goes. I was thinking of looking at hacking vchkpw to handle a
cdb style password file instead of flat text however. While I'm doing fine
now, the business is growing and I want to be sure I can continue when I
hit 15k+.
Steve
Robin Bowes writes:
> This isn't an answer to the original question - just some thoughts...
>
> How would vchkpw perform in this situation? (http://www.inter7.com/vchkpw/)
> Presumably, the vpasswd file would be the bottleneck? Is it possible to use
> vchkpw with a DB of some sort, eg CDB? Presumably, this would involve
> hacking vchkpw appropriately?
>
> R.
>
> Chris McCarthy <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > My company wants to provide users on the internet with a free email
> > service ([EMAIL PROTECTED]). We'll be starting off with about
> > 3,000 users, potentially growing up to 10,000 in the next 12 months.
> >
> > How feasible is it to create a passwd/shadow entry for each user,
> > providing them with POP/IMAP access ? (or maybe just pop if imap puts
> > too much load on the server).
> >
> > With the passwd and shadow files containing so many entries, will the
> > password lookups take forever ?
> >
> > Our current server spec is a PIII 400, 256M, but we'll replace it with a
> > high spec server if/when needed.
> >
> > Does this sound OK, or should we look at buying (or developing) hotmail
> > style software instead ?
> >
> >
> > Any ideas/comments appreciated,
> > .Chris.
> >
> >
>
>
> Vchkpw handles 10k users just fine in it's current version. I'm running
200
> virtual domains totaling about 10k pop accounts on a p2/300 with 256mb
ram,
I'm speculating here (I know, I know... :o) but if you have 200 virtual
domains with 10k users total, that's an average of 50 users per vpasswd
file. If there is only 1 virtual domain (as in the example) then there
would be 10k users in vpasswd.
> a couple scsi-2 drives, Apache 1.3.4, SQWebmail 0.20 on FreeBSD 3.1 and it
> runs like a top. No complaints in the slightest from here as far as
> performance goes. I was thinking of looking at hacking vchkpw to handle a
> cdb style password file instead of flat text however. While I'm doing fine
> now, the business is growing and I want to be sure I can continue when I
> hit 15k+.
Sounds like this may be a useful patch to have.
R.
> Steve
>
> Robin Bowes writes:
> > This isn't an answer to the original question - just some thoughts...
> >
> > How would vchkpw perform in this situation?
(http://www.inter7.com/vchkpw/)
> > Presumably, the vpasswd file would be the bottleneck? Is it possible to
use
> > vchkpw with a DB of some sort, eg CDB? Presumably, this would involve
> > hacking vchkpw appropriately?
> >
> > R.
> >
> > Chris McCarthy <[EMAIL PROTECTED]> wrote in message
> > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > My company wants to provide users on the internet with a free email
> > > service ([EMAIL PROTECTED]). We'll be starting off with about
> > > 3,000 users, potentially growing up to 10,000 in the next 12 months.
> > >
> > > How feasible is it to create a passwd/shadow entry for each user,
> > > providing them with POP/IMAP access ? (or maybe just pop if imap puts
> > > too much load on the server).
> > >
> > > With the passwd and shadow files containing so many entries, will the
> > > password lookups take forever ?
> > >
> > > Our current server spec is a PIII 400, 256M, but we'll replace it with
a
> > > high spec server if/when needed.
> > >
> > > Does this sound OK, or should we look at buying (or developing)
hotmail
> > > style software instead ?
> > >
> > >
> > > Any ideas/comments appreciated,
> > > .Chris.
> > >
> > >
> >
> >
>
Hi all,
I'm implementing maildir support for the GNOME's messaging library
Camel. Camel uses a provider abstraction for mail stores. A store
provider object allows a MUA to access mail folders and messages through
a simple storage-independent API. The folder abstraction has support for
both messages and subfolders although a provider is not required to
implement both.
It was quite easy and straightforward to implement the basic message
handling operations for isolated maildir folders. I'm now wondering
whether I should also add support for subfolders. It doesn't seem too
difficult and I already have a few ideas for doing it. I'd like to know
if anyone has already implemented subfolders in maildirs and how it has
been done.
I searched through the mailing list archives for more information about
maildir subfolders and found a number of messages discussing the matter.
There however doesn't seem to be any standard way to implement
subfolders. I'm asking anyone who's developed or used maildir subfolders
to share his/her experiences so I can make the Camel library support any
extensions to the maildir format.
Here's a bunch of specific questions for which I'd like to have answers.
1) Should the maildir format be extended to support subfolders?
The official documentation only mentions the three subdirectories and a
couple of meta files in a maildir folder. Perhaps it's not a good idea
to add subfolders in the maildir format?
2) If subfolders shouldn't be used, then how should I handle multiple
maildirs?
A user might want to store mail in multiple different maildir folders.
Is there a standard place where such folders should be located? I've
seem people use ~/Mail, ~/IMAP, ~/Maildirs and other places to store
multiple maildir folders in addition to the default $MAILDIR.
3) If subfolders are used, then how they should be formatted?
It seems to me that subfolders should be fullblown maildir folders in
themselves and not just extra "cur" directories with different names. If
the subfolders are true maildirs then mail can be directly delivered to
them.
4) If subfolders are used, then how they should be named/located?
The subfolders could be additional maildir subdirectories of the maildir
folder. That way it would be easy to access the folders, the subfolder
"bar" in the subfolder "foo" of the default maildir would be in
$MAILDIR/foo/bar. What should be done with folders named "new" or "tmp"?
A solution could be to use some kind of name mapping or a specific
directory for holding the subfolders. Examples: $MAILDIR/.foo/.bar,
$MAILDIR/folder-foo/folder-bar, $MAILDIR/sub/foo/sub/bar.
I also started wondering about caching of message summary information.
It could be quite slow to open and parse each message file in a folder
just to list the folder contents. Camel will probably have an internal
summary cache, but knowledge of other caching mechanisms wouldn't hurt.
Question:
5) How should message contents be changed in a maildir?
When a MUA want's to add a header or otherwise modify the message,
should it assign a new name to the message file? It's generally a bad
idea to rewrite received messages and Camel probably wont do that, but
I'd like to know about other implementations. If the filename of the
message is changed whenever the message is modified, then caching will
be much easier as a single stat on the "cur" directory will be enough to
determine whether folder contents have changed.
Thanks for your attention!
Jukka Zitting
[EMAIL PROTECTED]
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
> I'm implementing maildir support for the GNOME's messaging library
> Camel. Camel uses a provider abstraction for mail stores. A store
> provider object allows a MUA to access mail folders and messages through
> a simple storage-independent API. The folder abstraction has support for
> both messages and subfolders although a provider is not required to
> implement both.
>
> It was quite easy and straightforward to implement the basic message
> handling operations for isolated maildir folders. I'm now wondering
> whether I should also add support for subfolders. It doesn't seem too
> difficult and I already have a few ideas for doing it. I'd like to know
> if anyone has already implemented subfolders in maildirs and how it has
> been done.
I can tell you how the UW IMAP Maildir driver does it...
If one folder is ~/cool_folder/{cur,tmp,new} then a sub folder can be created
as ~/cool_folder/sub_folder/{cur,tmp,new}. This means that you can't have a
sub-folder named "cur", "tmp", or "new" but that's not that bad of a loss. It
seems that the Maildir client and the delivery agent in qmail-local ignore the
new directories created inside the maildir just fine. There should be code to
prevent you from creating a sub-folder with one of those reserved names.
I think this method is the most straight forward and it seems to work just
fine.
- David Harris
Principal Engineer, DRH Internet Services
On Mon, 6 Sep 1999, Jukka Zitting wrote:
> Hi all,
>
> I'm implementing maildir support for the GNOME's messaging library
> Camel. Camel uses a provider abstraction for mail stores. A store
> provider object allows a MUA to access mail folders and messages through
> a simple storage-independent API. The folder abstraction has support for
> both messages and subfolders although a provider is not required to
> implement both.
>
> It was quite easy and straightforward to implement the basic message
> handling operations for isolated maildir folders. I'm now wondering
> whether I should also add support for subfolders. It doesn't seem too
> difficult and I already have a few ideas for doing it. I'd like to know
> if anyone has already implemented subfolders in maildirs and how it has
> been done.
Yes, I have implemented maildir subfolders in two separate applications:
webmail CGI client, and a maildir-aware mail filter. I'm also working on
a third application that uses the same layout.
> I searched through the mailing list archives for more information about
> maildir subfolders and found a number of messages discussing the matter.
> There however doesn't seem to be any standard way to implement
> subfolders. I'm asking anyone who's developed or used maildir subfolders
> to share his/her experiences so I can make the Camel library support any
> extensions to the maildir format.
DJB does not have anything to say on this, so it's pretty much everyone on
their own. When I looked at it ages ago, someone else on a mailing list
mentioned how he was working on implementing maildir folders in his imap
client. I don't believe that he actually finished it, but I just took his
rough idea, and ran with it. Afterwards, I've also implemented a
voluntary quota mechanism for maildirs and subfolders on top of the same
layout.
Before you go any further, you might want to take a look at how I did it.
Look at: http://www.inter7.com/sqwebmail/ and
http://www.flounder.net/~mrsam/maildrop/.
In either package you want to take a look at the maildir subdirectory -
it's the same in both packages. The subdirectory includes some
documentation of what I did, plus some source code.
Currently, the mechanism allows for one level of subfolders only. I'm
currently thinking of ways to implement a subfolder hierarchy. For various
reasons, I'm leaning against implementing a subfolder hierarchy using
nested subdirectories. Instead, I'm leaning towards using a hierarchy
separator character in the name of each subfolder, a'la IMAP.
On Mon, 6 Sep 1999, Jukka Zitting wrote:
> Hi all,
>
> Here's a bunch of specific questions for which I'd like to have answers.
>
> 1) Should the maildir format be extended to support subfolders?
> The official documentation only mentions the three subdirectories and a
> couple of meta files in a maildir folder. Perhaps it's not a good idea
> to add subfolders in the maildir format?
I think the should not, because it won't be compatible with pine's maildir
functions. (patched version)
>
> 2) If subfolders shouldn't be used, then how should I handle multiple
> maildirs?
> A user might want to store mail in multiple different maildir folders.
> Is there a standard place where such folders should be located? I've
> seem people use ~/Mail, ~/IMAP, ~/Maildirs and other places to store
> multiple maildir folders in addition to the default $MAILDIR.
>
pine with maildir patch handles maildirs the same as other mail folders,
so they are under ~/mail
> 3) If subfolders are used, then how they should be formatted?
> It seems to me that subfolders should be fullblown maildir folders in
> themselves and not just extra "cur" directories with different names. If
> the subfolders are true maildirs then mail can be directly delivered to
> them.
>
fullblown maildirs with delivery capability.
> 5) How should message contents be changed in a maildir?
> When a MUA want's to add a header or otherwise modify the message,
> should it assign a new name to the message file? It's generally a bad
> idea to rewrite received messages and Camel probably wont do that, but
> I'd like to know about other implementations. If the filename of the
> message is changed whenever the message is modified, then caching will
> be much easier as a single stat on the "cur" directory will be enough to
> determine whether folder contents have changed.
>
look at the maildir doc at Dan's homepage about info part of the name in
cur directory.
Robert Varga
Just a performance comment. Qmail is IO bound. Adding additional
subdirectories force additional stat'ing of inode/vnode structures. ...
Typically these are NOT in your cache as you get closer to the
user-directory. With access time (atime) enabled, adding a single
additional directory immediately before your final email user directory
could easily reduce throughput by 15-30%. If atime is disabled (NFS on
Solaris 7, FreeBSD, I don't recall Linux), delay is on the order of
5-15%.
Sam wrote:
>
> On Mon, 6 Sep 1999, Jukka Zitting wrote:
>
> > Hi all,
> >
> > I'm implementing maildir support for the GNOME's messaging library
> > Camel. Camel uses a provider abstraction for mail stores. A store
> > provider object allows a MUA to access mail folders and messages through
> > a simple storage-independent API. The folder abstraction has support for
> > both messages and subfolders although a provider is not required to
> > implement both.
> >
> > It was quite easy and straightforward to implement the basic message
> > handling operations for isolated maildir folders. I'm now wondering
> > whether I should also add support for subfolders. It doesn't seem too
> > difficult and I already have a few ideas for doing it. I'd like to know
> > if anyone has already implemented subfolders in maildirs and how it has
> > been done.
>
> Yes, I have implemented maildir subfolders in two separate applications:
> webmail CGI client, and a maildir-aware mail filter. I'm also working on
> a third application that uses the same layout.
>
> > I searched through the mailing list archives for more information about
> > maildir subfolders and found a number of messages discussing the matter.
> > There however doesn't seem to be any standard way to implement
> > subfolders. I'm asking anyone who's developed or used maildir subfolders
> > to share his/her experiences so I can make the Camel library support any
> > extensions to the maildir format.
>
> DJB does not have anything to say on this, so it's pretty much everyone on
> their own. When I looked at it ages ago, someone else on a mailing list
> mentioned how he was working on implementing maildir folders in his imap
> client. I don't believe that he actually finished it, but I just took his
> rough idea, and ran with it. Afterwards, I've also implemented a
> voluntary quota mechanism for maildirs and subfolders on top of the same
> layout.
>
> Before you go any further, you might want to take a look at how I did it.
> Look at: http://www.inter7.com/sqwebmail/ and
> http://www.flounder.net/~mrsam/maildrop/.
>
> In either package you want to take a look at the maildir subdirectory -
> it's the same in both packages. The subdirectory includes some
> documentation of what I did, plus some source code.
>
> Currently, the mechanism allows for one level of subfolders only. I'm
> currently thinking of ways to implement a subfolder hierarchy. For various
> reasons, I'm leaning against implementing a subfolder hierarchy using
> nested subdirectories. Instead, I'm leaning towards using a hierarchy
> separator character in the name of each subfolder, a'la IMAP.
--
Daemeon Reiydelle
Systems Engineer, Anthropomorphics Inc.
[EMAIL PROTECTED]
On Mon, 6 Sep 1999, Daemeon Reiydelle wrote:
> Just a performance comment. Qmail is IO bound. Adding additional
> subdirectories force additional stat'ing of inode/vnode structures. ...
Only if you're actually delivering to the subdirectory, and if the
filesystem does not cache pathnames versus inodes (I don't know which do
or don't).
Sam wrote:
>
> On Mon, 6 Sep 1999, Daemeon Reiydelle wrote:
>
> > Just a performance comment. Qmail is IO bound. Adding additional
> > subdirectories force additional stat'ing of inode/vnode structures. ...
>
> Only if you're actually delivering to the subdirectory, and if the
> filesystem does not cache pathnames versus inodes (I don't know which do
> or don't).
First, the following applies only to the OS's I know about currently
(Solaris 2.6/7, Linux, FreeBSD).
Re. caching of vnodes: (UNIX) systems cache Vnode structures or
equivalent whether data, directory, link, or whatever. Directory lookups
are done by breaking down the path into it's components and walking the
filesystem (with associated cache hits when the data is in-cache). If
the OS (e.g. 2.6) has limited space for the name of the vnode (e.g. 35
chars or so in Solaris 2.6) and the file name is larger than that limit,
then the inode will not be cached. I am unaware of a global "directory"
cache in any OS's: all directory path's are cached in terms of their
component vnodes.
(Question) does Stat'ing the directory sets the atime? My recollection
of the kernel code is fuzzy, but I seem to recall that a stat does cause
the vnode to be updated. If so, that stat causes a write to the physical
media to be queued (I have not seen any code that does a vflush) even if
there isn't actually a "delivery".
Re. the IO bound and reduced throughput: I have benchmarked the 15-30%.
My logic to explain the empirical observation was as follows:
= The file system cache is limited.
= Seldom-hit cached values on a busy system are most likely to be
flushed out before they are revisited.
= A node associated with a user directory has about the same probability
of access as the user directory
= Adding a directory that corresponds directly to the user directory
increases the IO by one or two to access the directory (one to stat into
the cache, and a second to update the atime if atime cannot be
disabled).
= Email is seldom delivered to a given user
= A typical (ignoring NFS overhead) directory might be
/home/daemeonr/Mail/<file>
= A modified directory might be
/qmail/<hash>/anthros.com/<hash>/daemeonr/Inbox/<hash in email>/<file>
(I ignore this case in the discussion) but it is a typical mod to
enhance operational maintenance of qmail) by reducing file system time
to recover/migrate/etc.)
... The cache of a user directory on a busy system has a negligible
probability of being in the cache when email is actually delivered to
the user.
... Adding an additional subdir increases io by doubling the io's
necessary to stat the user's home directory node itself.
... There are 3 stat's required at least (daemeonr + mail + file).
Adding one more results in about a 20% increase in stat's (daemeonr +
mail + hash + file). If atime is ignored it results in about a 10%
increase.
--
Daemeon Reiydelle
Systems Engineer, Anthropomorphics Inc.
[EMAIL PROTECTED]
Hello,
I'm the sysadmin for a small ISP with a little less than 3,000 users.
We are currently using an NT based email system called vopmail. I'm
working on switching to qmail running on BSDI 4.0.1 Everything appears
to be working alright except for getting the following error in my
/var/log/messages file:
Sep 6 10:48:01 qmail: 936592618.270006: alert: oh no! lost spawn
connection! dying...
When I intially installed qmail, I installed daemontools-0.53. Should I
be running a newer version than this?? If so, could that be why I'm
having this problem??
The server in question is a dual pentium III 500 with 512MB of ram
running on a DPT smartraid IV controller. The kernel has been fully
patched, and I am running qmail with the unlimit command.
Thanks in advance for any assistance you can give.
Althouhg you didn't say, I assume this is happening all the time?
I see this error when a qmail-lspawn'ed qmail-local fails
catastrophically (e.g. protection exception, core dump). Are there any
core files under /var/qmail (or whatever your auto_qmail is set to)?
You may want to set up ddd and walk through qmail-local's execution (put
a sleep loop near the beginning of the main() function so you can attach
- it is much easier than trying to walk through the spawn/vfork logic in
qmail-lspawn.c+spawn.c).
Obviously check that your cdb file, /etc/passwd, and end-user directory
are correct. I also assume that all patches have been applied.
Robert wrote:
>
> Hello,
> I'm the sysadmin for a small ISP with a little less than 3,000 users.
> We are currently using an NT based email system called vopmail. I'm
> working on switching to qmail running on BSDI 4.0.1 Everything appears
> to be working alright except for getting the following error in my
> /var/log/messages file:
>
> Sep 6 10:48:01 qmail: 936592618.270006: alert: oh no! lost spawn
> connection! dying...
>
> When I intially installed qmail, I installed daemontools-0.53. Should I
> be running a newer version than this?? If so, could that be why I'm
> having this problem??
>
> The server in question is a dual pentium III 500 with 512MB of ram
> running on a DPT smartraid IV controller. The kernel has been fully
> patched, and I am running qmail with the unlimit command.
>
> Thanks in advance for any assistance you can give.
--
Daemeon Reiydelle
Systems Engineer, Anthropomorphics Inc.
[EMAIL PROTECTED]
I believe I've correctly configured qmail to serve as a selective relay for
local users only. Is there an easy way to test this?
Ben
----------
The phrasing, style, and content of this message are the sole property of
Ben Beuchler, Inc. and may not be reproduced in any way, shape or form
without the written consent Ben Beuchler Enterprises. All rights reserved.
Void where prohibited by law. Do not remove under penalty of law. Do not
spindle or fold. Not valid in Alaska, Hawaii, or Puerto Rico.
OK.... Tried that (http://maps.vix.com/tsi/ar-test.html) and I failed the
very last test. However, they state several times on their page that they
can have false positives. Here's the output:
Relay test 6
>>> RSET
<<< 250 flushed
>>> MAIL FROM:<spamtest@[205.218.58.195]>
<<< 250 ok
>>> RCPT TO:<relaytest%mail-abuse.org@[205.218.58.195]>
<<< 250 ok
and the relevant (I think) chunks from my logs:
/var/log/qmail/
936646638.403377 new msg 61209
936646638.403409 info msg 61209: bytes 1242 from <[EMAIL PROTECTED]> qp
6223 uid 500
936646638.501516 starting delivery 41: msg 61209 to remote
[EMAIL PROTECTED]
936646638.501578 status: local 1/10 remote 1/20
936646638.501615 delivery 40: success: did_0+1+0/qp_6223/
936646638.501661 status: local 0/10 remote 1/20
936646638.501698 end msg 61208
936646639.963452 delivery 41: success:
208.132.52.4_accepted_message./Remote_host_said:_250_OK/
936646639.963526 status: local 0/10 remote 0/20
936646639.963563 end msg 61209
/var/log/qmail/smtpd/
936646638.513102 tcpserver: status: 0/40
936646781.759362 tcpserver: status: 1/40
936646781.760102 tcpserver: pid 6237 from 204.152.184.35
936646782.181669 tcpserver: ok 6237 :205.218.58.195:25
maps1.pa.vix.com:204.152.184.35::1901
936646785.082179 tcpserver: end 6237 status 256
936646785.082396 tcpserver: status: 0/40
>From what I can tell, it looks like qmail failed this one test and actually
accepted the message. Is this interpretation correct? And if so, what can
I do about it?
Ben
----------
The phrasing, style, and content of this message are the sole property of
Ben Beuchler, Inc. and may not be reproduced in any way, shape or form
without the written consent Ben Beuchler Enterprises. All rights reserved.
Void where prohibited by law. Do not remove under penalty of law. Do not
spindle or fold. Not valid in Alaska, Hawaii, or Puerto Rico.
> -----Original Message-----
> From: Gerd Suppan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 06, 1999 2:36 PM
> To: Ben Beuchler
> Subject: Re: testing for an open relay
>
>
> Hi Ben!
>
> > I believe I've correctly configured qmail to serve as a
> selective relay for
> > local users only. Is there an easy way to test this?
>
> Just look at:
>
> http://maps.vix.com/tsi/ar-test.html
>
> That should do it.
>
>
> HTH
> Gerd
>
> -----------------------------------------------------------------------
> This is Linux Country. On a quiet night, you can hear Windows NT reboot!
>
Ben Beuchler writes:
> I believe I've correctly configured qmail to serve as a selective relay for
> local users only. Is there an easy way to test this?
I'm working on an automatic method, but you can test by hand fairly
easily:
On a host which is not allowed to relay:
telnet hostname 25
mail <>
rcpt <foo@bar>
If it whinges about the rcpt, you're successfully not relaying.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
>OK.... Tried that (http://maps.vix.com/tsi/ar-test.html) and I failed the
>very last test.
Nope, qmail gives a misleading response. It accepts the message and then
bounces it, since it checks only the domain at SMTP time.
>> http://maps.vix.com/tsi/ar-test.html
It's based on one I wrote. For the original, which can actually send a
little test mail, try http://www.abuse.net/relay.html.
I've been meaning to make it smarter and look at the SMTP banner, see if
it recognizes the MTA, and if so skip tests that won't give useful results.
--
John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869
[EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl,
Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Would someone please post a version of the startup script that works with
Daemontools 0.61?
I have meticulously read the "Life with qmail" as well as the "qmail How-to"
before starting my qmail installation. I thought I understood everything.
Everything compiled and tested as planned. Then, I tried starting qmail. I
got a few errors related to setuser, accustamp, and syslog. Okay, after a
little more searching, I find that they have all been replaced in the new
Daemontools by setuidgid, tai64n, and multilog. I switched them, and
though I had fixed 'em. The startup script still doesn't work. I realize that
the supervise parameters have changed. Drastically. Then I realize
(through the mailing-list archives) that the "Life with qmail" and "qmail How-
to" docs, the ones I based my entire installation on, are not quite up to date
in regards to the new Daemontools. Now, I'm lost.
Would someone post a version of the startup script with works with
Daemontools 0.61 that is equivalent to the script listed on the "Life with
qmail" doc? Or would the better solution be to just grab Daemontools 0.53,
recompile and reinstall, and use the old script?
I have been reading the thread started by James, as it seem he is having
the same problem. However, he has not come to any solution. At least I
don't feel like I am the only one having these problems. I take it everyone
"out there" is still using the old Daemontools. Should I be too?
Any insight would be appreciated.
Thanks,
Michael Lundberg
[EMAIL PROTECTED]
I've changed the link in my howto to point to daemontools-0.53, and I
suggest that people use that. There is absolutely nothing wrong with
daemontools 0.53.
--Adam
On Mon, Sep 06, 1999 at 01:02:55PM -0500, Michael wrote:
> Would someone please post a version of the startup script that works with
> Daemontools 0.61?
>
> I have meticulously read the "Life with qmail" as well as the "qmail How-to"
> before starting my qmail installation. I thought I understood everything.
> Everything compiled and tested as planned. Then, I tried starting qmail. I
> got a few errors related to setuser, accustamp, and syslog. Okay, after a
> little more searching, I find that they have all been replaced in the new
> Daemontools by setuidgid, tai64n, and multilog. I switched them, and
> though I had fixed 'em. The startup script still doesn't work. I realize that
> the supervise parameters have changed. Drastically. Then I realize
> (through the mailing-list archives) that the "Life with qmail" and "qmail How-
> to" docs, the ones I based my entire installation on, are not quite up to date
> in regards to the new Daemontools. Now, I'm lost.
>
> Would someone post a version of the startup script with works with
> Daemontools 0.61 that is equivalent to the script listed on the "Life with
> qmail" doc? Or would the better solution be to just grab Daemontools 0.53,
> recompile and reinstall, and use the old script?
>
> I have been reading the thread started by James, as it seem he is having
> the same problem. However, he has not come to any solution. At least I
> don't feel like I am the only one having these problems. I take it everyone
> "out there" is still using the old Daemontools. Should I be too?
>
> Any insight would be appreciated.
>
> Thanks,
> Michael Lundberg
> [EMAIL PROTECTED]
>
Recently, Michael had the following to say about Problems getting started:
> Would someone please post a version of the startup script that works with
> Daemontools 0.61?
>
[Sorry for the length--the scripts and my explanations were
not as short as I had hoped. Also, anyone with improvements, don't be shy,
feel free to e-mail me so I can make the setup better.]
Well, these are not based on lwq, but are based on Bruce Guenther's
startup scripts included with his qmail+patches srpms for redhat. I had to
play with them for awhile, but this is what has worked for me (although I am
sure there are guru's out there who will point out how to improve these
dramatically.) Note, the first step was to grab Bruce's Source RPMS for
daemontools-0.61 and his supervise-scripts SRPMS (version 2.0). They are
located on http://em.ca/~bruceg although you may have to look around to find
them, that's the parent directory). AFAIK, The following *will not work*
without having these in place first.
First use RPM to build daemontools-0.61 and install it. Same for the
supervise scripts.
NOTE: I use several RBL services which you may want to eliminate
from your setup. I also use Bruce's vmailmgr program to handle virtual
users. Thus the following is specific to those programs.
Oh, and thanks Bruce! You've made this much easier for me.
Then, here are the scripts I use to start up qmail, pop3 services
and smtpd services in that order. These reside in /etc/rc.d/init.d on my
RedHat 6.0 installation:
qmail:
---------------------------------------
#!/bin/sh
#
# chkconfig: 345 70 30
# description: qmail mail transport agent
#
service=qmail
# Source function library.
. /etc/rc.d/init.d/qmail-functions
# See how we were called.
case "$1" in
start)
# Start daemons.
readdefault aliasempty aliasempty ./Mailbox
make-owners /etc/qmail
cd /var/log
svc-start qmail qmail-start "$aliasempty"
exit $?
;;
*)
echo "Usage: qmail {start|stop|status|restart}"
exit 1
esac
-----------------------------------------------------------
pop3d:
--------------------------------
#!/bin/sh
#
# chkconfig: 345 70 30
# description: the POP-3 server from qmail
#
service=pop3d
# Source function library.
. /etc/rc.d/init.d/qmail-functions
# See how we were called.
case "$1" in
start)
# Start daemons.
uid="0"
gid="`id -g qmaild`"
hostname="`hostname`"
readdefault concurrency concurrencypop3d 20
readdefault checkpass checkpassword checkpassword
do_ulimits
cd /var/log
svc-start pop3d \
tcpserver -u "$uid" -g "$gid" -c "$concurrency" -v -R \
-x /etc/tcpcontrol/pop-3.cdb 0 pop-3 \
qmail-popup "$hostname" \
$checkpass \
qmail-pop3d-log Maildir/
exit $?
;;
*)
echo "Usage: pop3d {start|stop|status|restart}"
exit 1
esac
-------------------------------------------------------------------------
smtpd:
------------------
#!/bin/sh
#
# chkconfig: 345 70 30
# description: The SMTP daemon for qmail with optional RBL blocking.
#
service=smtpd
# Source function library.
. /etc/rc.d/init.d/qmail-functions
# If antirbl is installed, process antirbldomains
if [ -x /usr/bin/antirbl ]; then
readdefault domains antirbldomains ""
for domain in $domains; do
rbl="$rbl /usr/bin/antirbl $domain"
done
fi
# If rblsmtpd is installed, process rbltimeout and rbldomains
if [ -x /usr/bin/rblsmtpd ]; then
readdefault timeout rbltimeout 60
readdefault domains rbldomains rbl.maps.vix.com
for domain in $domains; do
rbl="$rbl /usr/bin/rblsmtpd -t $timeout -r $domain"
done
fi
# See how we were called.
case "$1" in
start)
# Start daemons.
uid="`id -u qmaild`"
gid="`id -g qmaild`"
readdefault concurrency concurrencysmtpd 20
do_ulimits
cd /var/log
svc-start smtpd \
tcpserver -u "$uid" -g "$gid" -c "$concurrency" -v \
-x /etc/tcpcontrol/smtp.cdb 0 smtp $rbl \
qmail-pipe fixcr -- qmail-smtpd
exit $?
;;
*)
echo "Usage: smtpd {start|stop|status|restart}"
exit 1
esac
------------------------------------------------------------------------
[If you don't know what or where 'do_ulimits' and 'readddefault' and
'aliasempty' come from, pick up Bruce's qmail+patches-8 SRPMS compilation.
They are in the included 'qmail-functions' file.]
Next come the files to run the services. The supervise scripts pretty much
set these up for you themselves, which is why I highly recommend them. They
do NOT, however, set up the run files for logging purposes, so I've included
mine here. These set up cylog-style logs in the /var/log/{service}
(i.e.,qmail, pop3d and smtp) directories. Note I also keep my log files
between 1 and 2.5 megs since the standard 100K is too small for my purposes.
To help visualize all of the following, I have attached a script showing
the directory structure in /var/lock/svc/, so you can see the ownerships
and permissions.
First the "run" file for qmail, which is located in /var/lock/svc/qmail and
which is owned by root.root, perms 755:
---------------------------
#!/bin/sh
exec qmail-start ./Maildir/
-------------------------
Then in my /var/lock/svc/qmail directory, I have created a directory called
"log" and have my run file in it which sets up the logging in /var/log/qmail:
-----------------------------------------------------------
#! /bin/sh
exec setuidgid qmaill multilog t s2500000 /var/log/qmail
----------------------------------------------------------
Note, you must have the /var/log/qmail directory owned by qmaill (qmail
logger) perms 755
Now the run file for smtpd (this is all on ONE line in my file, formatted and
'\' added for readability purposes):
---------------------------------------------
#!/bin/sh
exec tcpserver -u 101 -g 234 -c 20 -v -x /etc/tcpcontrol/smtp.cdb 0 smtp \
/usr/bin/rblsmtpd -t 60 -r rbl.maps.vix.com /usr/bin/rblsmtpd -t 60 -r \
dul.maps.vix.com /usr/bin/rblsmtpd -t 60 -r relays.radparker.com qmail-pipe\
fixcr -- qmail-smtpd
--------------------------------
Now for the run file for logging (located in /var/lock/svc/smtpd/log)
---------------------------------
#! /bin/sh
exec setuidgid qmaill multilog t s2500000 /var/log/smtpd
-------------------------------------------------------
Make sure your /var/log/smtpd directory is owned by qmaill
Finally, the run files for pop3 services. First the run file for the service
located in /var/lock/svc/pop3d (This too is on one line in my file,
formatted to make review of the contents easy):
--------------------------------------
#!/bin/sh
exec tcpserver -u 0 -g 234 -c 20 -v -R -x /etc/tcpcontrol/pop-3.cdb 0 pop-3\
qmail-popup joshua /usr/bin/checkvpw qmail-pop3d-log Maildir/
----------------------------------------------------------------
And now the run file for pop3 logging, residing in /var/lock/svc/pop3d/log
--------------------------------------------
#! /bin/sh
exec setuidgid qmaill multilog t s1000000 /var/log/pop3d
--------------------------------------------------------
Here again, you must have /var/log/pop3d owned by qmaill.
Also, all run file are perms 755 owned by root.root.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
After all the init scripts and run files are in place, you can start
up svscan with it's init script to start svscan and forget about it (it can
just run forever AFAIK). The start up the services with their init
scripts. This will start up a supervised process for pop3d, qmail and smtpd as
well as a supervised process for the logging for each service. This
creates the familiar 'supervise' subdirectory in /var/lock/svc/{service} as
well as a 'supervise' subdirectory in /var/lock/svc/{service}/log.
Hope that helps someone get through the switch. Now that I have this
set up, I find starting and stopping the services to be a breeze and have
started converting over services over to daemontools too.
Please remember that your setup may differ dramatically and the
above is specific to Redhat Linux 6.0 with Bruce's daemontools, supervise
scripts, vmailmgr and qmail+patches. You may need to change the paths and
many other items to get it to work. But it does run just fine on my system.
Sorry if there are some typos in the above. I dashed it off in a
rush in response to the request from Michael.
Fred
--
Fred B. Ringel -- Rivertown.Net Internet Access
Systems Administrator -- http://www.rivertown.net
and General Fixer Upper -- Voice/Fax/Support: +1.914.478.2885
E-mail: [EMAIL PROTECTED] for current my public key
Cloning is the sincerest form of flattery.
Script started on Mon Sep 6 14:51:18 1999
joshua: /var/lock/svc :1001 :# ls -la
total 7
drwxr-xr-x 5 root root 1024 Sep 6 14:51 .
drwxrwxr-x 6 root uucp 1024 Aug 9 20:17 ..
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:55 pop3d
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:21 qmail
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:19 smtpd
joshua: /var/lock/svc/pop3d :1003 :# ls -la
total 5
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:55 .
drwxr-xr-x 5 root root 1024 Sep 6 14:51 ..
drwxr-xr-x 3 root root 1024 Sep 5 21:15 log
-rwxr-xr-x 1 root root 148 Sep 5 21:55 run
drwx------ 2 root root 1024 Sep 5 21:55 supervise
joshua: /var/lock/svc/pop3d :1004 :# cd supervise/
joshua: /var/lock/svc/pop3d/supervise :1005 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:55 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:55 ..
prw------- 1 root root 0 Sep 5 21:55 control
-rw------- 1 root root 0 Sep 5 21:52 lock
prw------- 1 root root 0 Sep 5 21:52 ok
-rw-r--r-- 1 root root 18 Sep 5 21:55 status
joshua: /var/lock/svc/pop3d :1007 :# cd log/
joshua: /var/lock/svc/pop3d/log :1008 :# ls -la
total 4
drwxr-xr-x 3 root root 1024 Sep 5 21:15 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:55 ..
-rwxr-xr-x 1 root root 68 Sep 5 21:15 run
drwx------ 2 root root 1024 Sep 5 21:55 supervise
joshua: /var/lock/svc/pop3d/log :1009 :# cd supervise/
joshua: /var/lock/svc/pop3d/log/supervise :1010 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:55 .
drwxr-xr-x 3 root root 1024 Sep 5 21:15 ..
prw------- 1 root root 0 Sep 5 21:55 control
-rw------- 1 root root 0 Sep 5 21:52 lock
prw------- 1 root root 0 Sep 5 21:52 ok
-rw-r--r-- 1 root root 18 Sep 5 21:55 status
joshua: /var/lock/svc :1012 :# cd qmail/
joshua: /var/lock/svc/qmail :1013 :# ls -la
total 6
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:21 .
drwxr-xr-x 5 root root 1024 Sep 6 14:51 ..
drwxr-xr-x 3 qmaill root 1024 Sep 5 21:11 log
-rwxr-xr-x 1 root root 38 Sep 5 21:21 run
drwx------ 2 root root 1024 Sep 5 21:21 supervise
joshua: /var/lock/svc/qmail :1014 :# cd log/
joshua: /var/lock/svc/qmail/log :1015 :# ls -la
total 4
drwxr-xr-x 3 qmaill root 1024 Sep 5 21:11 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:21 ..
-rwxr-xr-x 1 qmaill root 68 Sep 5 21:11 run
drwx------ 2 root root 1024 Sep 5 21:21 supervise
joshua: /var/lock/svc/qmail/log :1016 :# cd supervise/
joshua: /var/lock/svc/qmail/log/supervise :1017 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:21 .
drwxr-xr-x 3 qmaill root 1024 Sep 5 21:11 ..
prw------- 1 root root 0 Sep 5 21:19 control
-rw------- 1 root root 0 Sep 5 15:14 lock
prw------- 1 root root 0 Sep 5 15:14 ok
-rw-r--r-- 1 root root 18 Sep 5 21:21 status
joshua: /var/lock/svc/qmail :1019 :# cd supervise/
joshua: /var/lock/svc/qmail/supervise :1020 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:21 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:21 ..
prw------- 1 root root 0 Sep 5 21:19 control
-rw------- 1 root root 0 Sep 5 15:13 lock
prw------- 1 root root 0 Sep 5 15:13 ok
-rw-r--r-- 1 root root 18 Sep 5 21:21 status
joshua: /var/lock/svc :1022 :# cd smtpd/
joshua: /var/lock/svc/smtpd :1023 :# ls -la
total 5
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:19 .
drwxr-xr-x 5 root root 1024 Sep 6 14:51 ..
drwxr-xr-x 3 root root 1024 Sep 5 21:15 log
-rwxr-xr-x 1 root root 251 Sep 5 21:19 run
drwx------ 2 root root 1024 Sep 5 21:20 supervise
joshua: /var/lock/svc/smtpd/supervise :1025 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:20 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:19 ..
prw------- 1 root root 0 Sep 5 21:19 control
-rw------- 1 root root 0 Sep 5 15:14 lock
prw------- 1 root root 0 Sep 5 15:14 ok
-rw-r--r-- 1 root root 18 Sep 5 21:20 status
joshua: /var/lock/svc/smtpd :1027 :# cd log/
joshua: /var/lock/svc/smtpd/log :1028 :# ls -la
total 4
drwxr-xr-x 3 root root 1024 Sep 5 21:15 .
drwxr-xr-t 4 qmaill root 1024 Sep 5 21:19 ..
-rwxr-xr-x 1 root root 68 Sep 5 21:15 run
drwx------ 2 root root 1024 Sep 5 21:20 supervise
joshua: /var/lock/svc/smtpd/log/supervise :1030 :# ls -la
total 3
drwx------ 2 root root 1024 Sep 5 21:20 .
drwxr-xr-x 3 root root 1024 Sep 5 21:15 ..
prw------- 1 root root 0 Sep 5 21:19 control
-rw------- 1 root root 0 Sep 5 15:14 lock
prw------- 1 root root 0 Sep 5 15:14 ok
-rw-r--r-- 1 root root 18 Sep 5 21:20 status
Script done on Mon Sep 6 14:52:46 1999
Suppose I was running a DPT RAID 5 controller and the mail queue was
stored on this RAID array. What will happen to the inode structure of
the queue if one of the disks fails, I replace it and the controller
rebuilds it?
- - - - - - - - - - - - - - - - - - - - - - -
Peeter Pirn, Sys Admin, FWI Internet, 219-426-7701 x17
On Mon, 6 Sep 1999 [EMAIL PROTECTED] wrote:
> Suppose I was running a DPT RAID 5 controller and the mail queue was
> stored on this RAID array. What will happen to the inode structure of
> the queue if one of the disks fails, I replace it and the controller
> rebuilds it?
RAID controllers, as a rule, are filesystem independent. They present a
logical block device to the RAID client, which then uses it to format and
use a filesystem.
Presumably, if a disk fails, the RAID controller will rebuild its contents
in a transparent fashion so that the filesystem client can't tell the
difference.
The recovery will ALWAYS be transparent at the inode level (well below
it actually). Inode values will be unchanged. You will observe a
SIGNIFICANT reduction in througput while the recovery is occurring,
however. FYI, if your RAID software supports it, you might want to
consider keeping a hot spare spinning at all times. Cost is negligible
and the only risk is that you will lose a drive, re-RAID, and you will
miss the warning that you lost a drive.
Sam wrote:
>
> On Mon, 6 Sep 1999 [EMAIL PROTECTED] wrote:
>
> > Suppose I was running a DPT RAID 5 controller and the mail queue was
> > stored on this RAID array. What will happen to the inode structure of
> > the queue if one of the disks fails, I replace it and the controller
> > rebuilds it?
>
> RAID controllers, as a rule, are filesystem independent. They present a
> logical block device to the RAID client, which then uses it to format and
> use a filesystem.
>
> Presumably, if a disk fails, the RAID controller will rebuild its contents
> in a transparent fashion so that the filesystem client can't tell the
> difference.
--
Daemeon Reiydelle
Systems Engineer, Anthropomorphics Inc.
[EMAIL PROTECTED]
Hi,
With some mail servers,when sending mail, I'm getting this problem, but
everything seems well configured for my domain which is: sintesoft.net
(check it out with nslookup)
Any idea?.
o_206.250.5.2_but_sender_was_rejected./Remote_host_said:_451_<[EMAIL PROTECTED]>..._Sender_domain_must_resolve/
On Mon, Sep 06, 1999 at 06:18:10PM +0000, [EMAIL PROTECTED] wrote:
> Hi,
> With some mail servers,when sending mail, I'm getting this problem, but
> everything seems well configured for my domain which is: sintesoft.net
> (check it out with nslookup)
>
> Any idea?.
>
>
>o_206.250.5.2_but_sender_was_rejected./Remote_host_said:_451_<[EMAIL PROTECTED]>..._Sender_domain_must_resolve/
How about letting us see the other relevant log entries to that failure so we
have a chance to see what might be wrong that you're overlooking?
--
Brad Shelton On Line Exchange http://online-isp.com
On Mon, Sep 06, 1999 at 06:18:10PM +0000, [EMAIL PROTECTED] wrote:
> Hi,
> With some mail servers,when sending mail, I'm getting this problem, but
> everything seems well configured for my domain which is: sintesoft.net
> (check it out with nslookup)
>
> Any idea?.
>
>
>o_206.250.5.2_but_sender_was_rejected./Remote_host_said:_451_<[EMAIL PROTECTED]>..._Sender_domain_must_resolve/
Some MTA:s demand that the remote mail server resolves well while doing a
reverse dns lookup.
The algorithm some MTA:s using is the following:
1. ok. she's connecting from IP a.b.c.d.
2. let's do a reverse lookup, checking who's a.b.c.d => ok it's name.domain
3. let's resolve name.domain and check if we get a.b.c.d
It's sometimes called "double DNS lookup".
--
magnus
-- MOST useless 1998 * http://x42.com/
Hi,
I have a mail gateway and it forwards email to specific mail hosts in my
network. I have a few mailing lists on these mail hosts, but the mail
gateway (with fastforward) is unable to forward any email destined to
the ezmlm list email addresses.
I.e:
I have `noc:@shell.blah.com` in my aliases file
On shell.blah.com is where the ezmlm lists are running. When someone
send
email to [EMAIL PROTECTED] normally I wnat the gateway to forward
the
email to shell.balh.com server for processing.
This doesn't happen because noc-subscribe@ isnt in the alias file. Is
there
anyway I can specify a wildcard in the alias files? perhaps:
noc::@shell.blah.com? (I heard ":" could be a wildcard in qmail?)
Thanks.
ok.. after reading the suggestion to install the old daemontools, I seem to
have Qmail working when I go to the init.d directory and type ./qmail start
I can't start qmail with just "qmail start".. what do I need to do to fix
that? Though, it really isn't that important because qmail starts when I
reboot.. but i'd like to know why I need the ./ before the executable.
Thanks again for all the help! Now on to figuring out the virtual email part.
james
At 09:32 AM 9/6/99 , James wrote:
>ok.. after reading the suggestion to install the old daemontools, I seem to
>have Qmail working when I go to the init.d directory and type ./qmail start
>
>I can't start qmail with just "qmail start".. what do I need to do to fix
>that? Though, it really isn't that important because qmail starts when I
>reboot.. but i'd like to know why I need the ./ before the executable.
>
>Thanks again for all the help! Now on to figuring out the virtual email part.
>
>james
This is because the current working directory (".") is not in your PATH.
This is usually considered a security hazard. If you do decide to add it
however, make sure it add it at the end of your PATH instead of at the start.
-Dustin
On Mon, Sep 06, 1999 at 03:32:05PM +0100, James wrote:
> ok.. after reading the suggestion to install the old daemontools, I seem to
> have Qmail working when I go to the init.d directory and type ./qmail start
>
> I can't start qmail with just "qmail start".. what do I need to do to fix
> that? Though, it really isn't that important because qmail starts when I
> reboot.. but i'd like to know why I need the ./ before the executable.
This has nothing to do with qmail. If you want to run an executable in Unix,
you must supply the full path to it if it's not in your path (echo $PATH to see
what is in your path). For security reasons, which are covered in any basic
Unix book, the current directory is not in your path, so you have to supply the
path with ./ .
Chris
One thing.. I am receiving mail in my Mailbox file.. but pine doesn't look
there. If I've overlooked the area of the qmail documentation that tells
me how to read mail, forgive me. But I don't see where to redirect my pine
to look at the right file to check mail.. how do I do this?
james
On Mon, Sep 06, 1999 at 03:43:51PM +0100, James wrote:
> One thing.. I am receiving mail in my Mailbox file.. but pine doesn't look
> there. If I've overlooked the area of the qmail documentation that tells
> me how to read mail, forgive me. But I don't see where to redirect my pine
> to look at the right file to check mail.. how do I do this?
reconfigure your Pine:
SETUP->CONFIG->
inbox-path = ./Mailbox
--
magnus
Ok.. thanks. Is there a way to make ./Mailbox the default for every user
we add? Or is this covered somewhere else in the documentation?
james
At 12:47 AM 9/7/99 +0200, you wrote:
>On Mon, Sep 06, 1999 at 03:43:51PM +0100, James wrote:
>> One thing.. I am receiving mail in my Mailbox file.. but pine doesn't
look
>> there. If I've overlooked the area of the qmail documentation that
tells
>> me how to read mail, forgive me. But I don't see where to redirect my
pine
>> to look at the right file to check mail.. how do I do this?
>
>reconfigure your Pine:
>
>SETUP->CONFIG->
>
>inbox-path = ./Mailbox
>
>--
>magnus
>
On Mon, Sep 06, 1999 at 05:16:02PM -0700, James wrote:
> Ok.. thanks. Is there a way to make ./Mailbox the default for every user
> we add? Or is this covered somewhere else in the documentation?
This is of course covered in the _Pine_ documentation.
Include the line
inbox-path=$HOME/Mailbox
in the file /usr/lib/pine.conf
--
magnus
-- MOST useless 1998 * http://x42.com/
Denis Voitenko writes:
> Are there any known IMAP servers that would work with Maildir?
There are patching of UW-IMAP. I'm seriously considering writing one from
scratch.
--
Sam
Sam [mailto:[EMAIL PROTECTED]] wrote:
> Denis Voitenko writes:
>
> > Are there any known IMAP servers that would work with Maildir?
>
> There are patching of UW-IMAP. I'm seriously considering writing one from
> scratch.
Why not just dig in the detail of the current UW-IMAP driver and clean it up?
Or if you really want to write something from scratch, write a maildir driver
from scratch. You could save quite a bit of work, I think.
- David Harris
Principal Engineer, DRH Internet Services
I am hoping Sam means that he's going to write an IMAP server from
scratch that works with Maildir. :-)
Tim
On Mon, Sep 06, 1999 at 09:11:45PM -0400, David Harris wrote:
>
> Sam [mailto:[EMAIL PROTECTED]] wrote:
> > Denis Voitenko writes:
> >
> > > Are there any known IMAP servers that would work with Maildir?
> >
> > There are patching of UW-IMAP. I'm seriously considering writing one from
> > scratch.
>
> Why not just dig in the detail of the current UW-IMAP driver and clean it up?
> Or if you really want to write something from scratch, write a maildir driver
> from scratch. You could save quite a bit of work, I think.
>
> - David Harris
> Principal Engineer, DRH Internet Services
Tim Tsai writes:
> I am hoping Sam means that he's going to write an IMAP server from
> scratch that works with Maildir. :-)
Correct.
I don't feel like pushing a square block into a round peg, which is what
stuffing maildir support into UW-IMAP would be like.
I'd rather put together some clean code from scratch. Because, in addition
to maildir support itself, I want to see a few things in the IMAP server
itself.
--
Sam
hmm.. I thought I had qmail working ok, but I am at a remote location. I
just found out that when the system is booted, it gets stuck at "starting
qmail".. but from a remote location, I can telnet in. Is it in some kind
of loop that I can get it out of? I am now unable to get the apache
server to serve pages.
I'm using Red Hat Mandrake 6.0
james
I was able to stop qmail, and when I restart it I get a continual loop:
Starting mail-transfer agent: qmail[1] 561
/var/qmail/rc: default: command not found
936674099.795938 status: local 0/10 remote 0/20
tcpserver: usage: tcpserver [ -1pPhHrRoOdDqQv ] [ -c limit ] [ -x
rules.cdb ] [
-B banner ] [ -g gid ] [ -u uid ] [ -b backlog ] [ -l localname ] [ -t
timeout ]
host port program
and that just keeps looping. I have no idea what is wrong =(
james
I was able to narrow down part of my last problem, and it seems like I am
only one step away from having qmail run properly. When I start qmail, I
get this:
Starting mail-transfer agent: qmail[1] 775
936686709.312775 status: local 0/10 remote 0/20
tcpserver: usage: tcpserver [ -1pPhHrRoOdDqQv ] [ -c limit ] [ -x rules.cdb
] [
-B banner ] [ -g gid ] [ -u uid ] [ -b backlog ] [ -l localname ] [ -t
timeout ]
host port program
It seems if I can figure out where this tcpserver command is being issued,
I might be able to narrow down this looping problem. Does anyone know
where this tcpserver command is coming from? Thanks for any help.
james
Greetings,
I read every thread on getting pine-4.10 to work with qmail-1.03 and I
still can't get pine to read the Maildir format.
I downloaded the patched pine src from
http://3.am/pine4.10.maildir.tar.gz and built it on an Intel Solaris 2.6
box.
What I have tried to get pine to read Maildir:
// edits to the ~/.pinerc file
inbox-path=~/Maildir (didn't work)
inbox-path=$HOME/Maildir (didn't work)
inbox-path=~/Maildir/ (didn't work)
inbox-path="inbox" (didn't work)
// shell enviro mods
MAIL=~/Maildir
export MAIL (didn't work)
It just always reads 0 messages in inbox :(
// I do have mail waiting:
[joshp@162-131-134 joshp]$ telnet mail.ioactive.com 110
Trying 209.162.131.139...
Connected to mail.ioactive.com.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
USER userTest
+OK
PASS *****
+OK
STAT
+OK 1780 594446
Any ideas? I'm at my wits end here.
Thanks for your time/help.
Josh
Running qmail 1.03 with daemontools and ucspi-tcp. So far so good everything
is working like clock work. The only place I am lacking is the statistics of
how my mail is being processed. I have qmailanalog installed and have looked
at the output of some of the combinations I tried. The only thing is I am
wondering if anyone has made qmailanalog insto a set of scripts that basically
replaces Sendmail's mailstats program. ANy scripts taking advantage of
qmailanalog would be greatly appreciated.
TIA
--
-------------------------------------------------------------------
Ron Rosson ... and a UNIX user said ...
The InSaNe One rm -rf *
[EMAIL PROTECTED] and all was null and void
-------------------------------------------------------------------
Allow me to introduce myselves
Ah.. I may have figured out my problem.. when I cut and paste the scripts
from either qmail howto web site, some of the commands are returned to the
next line, which screws everything up. I've removed my loop problem, and I
think it's fixed now.
james
At 11:41 PM 9/6/99 +0100, you wrote:
>I was able to narrow down part of my last problem, and it seems like I am
>only one step away from having qmail run properly. When I start qmail, I
>get this:
>
>Starting mail-transfer agent: qmail[1] 775
>936686709.312775 status: local 0/10 remote 0/20
>tcpserver: usage: tcpserver [ -1pPhHrRoOdDqQv ] [ -c limit ] [ -x rules.cdb
>] [
>-B banner ] [ -g gid ] [ -u uid ] [ -b backlog ] [ -l localname ] [ -t
>timeout ]
> host port program
>
>It seems if I can figure out where this tcpserver command is being issued,
>I might be able to narrow down this looping problem. Does anyone know
>where this tcpserver command is coming from? Thanks for any help.
>
>james
>
How do I limit the filesize in bounces?
Too often, a customer sent a huge mail mail through our mail
relay which could not be delivered to the destination because
of the size. It could not be returned to the sender either,
because it is too large. And the whole message ends up in
my postmaster mailbox as a double bounce :-(
Then, I lowered databytes to 1Mb, because it had to be
lower than on our customers mail servers to solve the
problem above.
A customer suggests that I instead just bounce the mail
headers and the error messages back to the sender.
(and discard the content of the original letter).
How is that done?
--
Med venlig hilsen / Regards
Netdriftgruppen / Network Management Group
UNI-C
Tlf./Phone +45 35 87 89 41 Mail: UNI-C
Fax. +45 35 87 89 90 Bygning 304
E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
their is a patch available for limitting bounce sizes. Maybe it is still on
the qmail pages, otherwise search in the mailarchives (someone recently
posted it again).
Franky
> ----------
> From: torben fjerdingstad[SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, September 07, 1999 9:34 AM
> To: [EMAIL PROTECTED]
> Subject: limiting the file size of bounces ?
>
> How do I limit the filesize in bounces?
>
> Too often, a customer sent a huge mail mail through our mail
> relay which could not be delivered to the destination because
> of the size. It could not be returned to the sender either,
> because it is too large. And the whole message ends up in
> my postmaster mailbox as a double bounce :-(
>
> Then, I lowered databytes to 1Mb, because it had to be
> lower than on our customers mail servers to solve the
> problem above.
>
> A customer suggests that I instead just bounce the mail
> headers and the error messages back to the sender.
> (and discard the content of the original letter).
>
> How is that done?
>
> --
> Med venlig hilsen / Regards
> Netdriftgruppen / Network Management Group
> UNI-C
>
> Tlf./Phone +45 35 87 89 41 Mail: UNI-C
>
> Fax. +45 35 87 89 90 Bygning 304
> E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
>
I'm still using qmail-1.01 on that machine.
Today I noticed something did (no longer) work, what I thought already did
(and I have a few of the emails in my folder dated later than the last
modification date of the .qmail file)
I want to create a bounce message for accounts of ppl that no longer
work here, but I also want to drop the mail into a valid users mailbox.
~alias/.qmail-joe:
&[EMAIL PROTECTED]
| (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
(which I thought already worked, doesn't any longer) only a bounce
message is delivered.
However if I use
~alias/.qmail-joe:
|forward [EMAIL PROTECTED]
| (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
it works as expected.
WHY? :-)) and are the few messages I had in my box "an accident" ?
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
Hello,
I am a rookie on using qmail, but I can feel the power of it, really
amazing.
I have several questions about the implementation of qmail. If possible,
please give me some advice. Thanks.
(1) Anti-relay Issue
Any security risk about Mail Relaying? If I really want to get rid of
relay, which module or file is required to be modified? According to Mr.
Peter Samuel's qmail tutorial at the recent SAGE-AU '99 conference, he
states that qmail can be configured to prevent mail relaying by specifying
valid incoming domains in /var/qmail/control/rcpthosts. Is it the case?
(2) EXPN and VRFY Issue
Any security risk about EXPN and VRFY? I can't find any information about
them on qmail released notes. Is that mean I can ignore these issues? Is it
enabled as default on qmail?
Discussion is welcomed. Thank you.
Jackie Chow
Email : [EMAIL PROTECTED]
