qmail Digest 30 Oct 1999 10:00:01 -0000 Issue 805
Topics (messages 32276 through 32293):
Is it possible to route mail to /dev/null from .qmail files
32276 by: Yusuf Goolamabbas
32277 by: Magnus Bodin
Re: Maildir & Pine 4.20
32278 by: Benjamin de los Angeles Jr .
Re: Basics
32279 by: Markus Stumpf
Novell Border Manager patch
32280 by: Delanet Administration
pop lock problem
32281 by: Luis Bezerra
32282 by: Anand Buddhdev
Re: High Volume server??
32283 by: Peeter Pirn
Number of accounts > 65,536 in a single server ?
32284 by: Heman Lu
32285 by: Petr Novotny
Re: Various newbie questions
32286 by: Dave Sill
Re: snoop and bare line feeds
32287 by: Racer X
32288 by: Michael Boyiazis
HELP - qmail server and apache server on separated boxes
32289 by: stanw.alphainter.net
32290 by: John R. Levine
Still trying to figure out delay on smtp/pop3
32291 by: Bill Parker
32293 by: Lukman Wiryahadi Kusuma
Re: host masquerade doesn't work.
32292 by: Carrott
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]
----------------------------------------------------------------------
Platform RH 6.0 with kernel 2.2.13
Hi, I just tried the following experiement in a .qmail-ext file
which contains the following line
/dev/null
Sending email to user-ext@machine results in the following message in
the log file
deferral: Unable_to_write_/dev/null:_invalid_argument._(#4.3.0)/
However, the above scheme works on a FreeBsd box
Anything I might have missed
Regards, Yusuf
--
Yusuf Goolamabbas
[EMAIL PROTECTED]
On Fri, Oct 29, 1999 at 10:07:50AM -0000, Yusuf Goolamabbas wrote:
>
> Hi, I just tried the following experiement in a .qmail-ext file
> which contains the following line
> /dev/null
>
> Anything I might have missed
Just put a comment in the .qmail-file!
#this comment means that the mail goes in the bit-bucket.
It's even faster because qmail takes the descision before even trying to
spool.
--
magnus
-- MOST useless 1998 * http://x42.com/
I'm using a patched for Maildir Pine 4.10 and no problems at all,
just put the Pine-created folders to ~/mail. This explains that
the patched Pine can read both mbox and Maildir format.
On Fri, Oct 29, 1999 at 10:04:43AM +0200, Jozef Hitzinger wrote:
>
> I'm working on a linux/qmail with ~/Maildir/ delivery for cca 1500 users.
> The problem is that we'd like to use pine as the client. I've found
> patches for 4.10, but ..
>
> What's current situations in maildir support for pine - anything new with
> 4.20? If you are using such a setup, what problems should I prepare for?
> Pine folder collection (sent-mail, saved-msg etc) will be in Maildir or
> mbox format? Thanx for any comments on this.
>
>
On Thu, Oct 28, 1999 at 01:28:52PM -0700, James wrote:
> creates a user mailbox when a new user is created. Currently I just
> create the Mailbox file for the newly created user. How do I automate
> this process?
If you use Mailbox (vs. Maildir) delivery to the $HOME you don't need to
create the Mailbox file. qmail will do that for you with the first
message the users receives.
> I feel I must be doing something wrong because with a newly
> created user, the .qmail forward doesn't seem to be working. Thanks for
> any hints.
What do you mean by .qmail forward?
What do the logfiles say?
A .qmail file must be owned by the user and may not be writable except
for that user. Same for the $HOME of the user.
\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 |
Not sure if anyone has reported this or not, but the recent versions of
the Novell Border Manager had the problem of inserting bare lf's into
outgoing mail. In my case, a client of a customer of mine was trying to
send mail from MS Outlook Express to their own Exchange server and then
out through Novell BM and on to my client which was picked up by my
qmail server and promptly rejected. Novell finally released a patch
(below) which fixes this problem.
The patch is bm3pc11.exe at
http://support.novell.com/products/nbmee3/patches.htm
Regards,
--
Stephen Comoletti
Systems Administrator
Delanet, Inc. http://www.delanet.com
ph: (302) 326-5800 fax: (302) 326-5802
Anyone has one good solution for the pop&lock problem.
regards,
--
-----------------------------
Lu�s Bezerra de A. Junior
[EMAIL PROTECTED]
SecrelNet Inform�tica LTDA
Fortaleza - Cear� - Brasil
Fone: 021852882090
-----------------------------
On Fri, Oct 29, 1999 at 10:06:53AM -0200, Luis Bezerra wrote:
> Anyone has one good solution for the pop&lock problem.
What problem? We're not mind readers. If you mean allowing each IP
address only one POP session at a time, see the recent archives. I had
posted a suggestion.
--
See complete headers for more info
I'm normally a digest subscriber and I saw this come through the digest.
We have approx 15,000 accounts on our server.
I solved the "unable to fork" problem using sh's limit (not the bash(?),
csh(?) ulimit) and by increasing the value of the -c option in tcpserver.
I have the following lines in my init script:
# Start qmail for local deliveries.
csh -cf '/var/qmail/rc &'
# Start qmail SMTP.
csh -cf '/root/bin/qmailsmtprc &'
# Start qmail POP3.
csh -cf '/root/bin/qmailpop3drc &'
and, for example, here's my qmailsptprc script using limit:
#!/bin/sh
limit maxproc 240
/usr/contrib/bin/tcpserver -c 100 -x /etc/tcp.smtp.cdb \
-u 13985 -g 105 0 smtp \
sh -c '
/usr/contrib/bin/fixcr | /var/qmail/bin/qmail-smtpd
cd /var/qmail/autoturn
exec /usr/contrib/bin/setlock -nx $TCPREMOTEIP/seriallock \
/usr/contrib/bin/maildirsmtp $TCPREMOTEIP \
autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN
' 2>&1 | /var/qmail/bin/splogger smtpd 3
P. Pirn - Sys Admin - see complete headers for more info
Hi,
I'm planning to migrate our mail server from sendmail
to qmail. There are 55,000+ mail accounts. When simulating
to grow beyond 65,536 accounts, I encounter some problems.
Here is my test environment:
Hardware: Acer Altos 12000
-- Pentium III 450 x 2
-- 1 GB DRAM
-- IBM Ultra2 SCSI Disk 9GB x 7 (as RAID 5)
Software: RedHat Linux 6.1
-- With shadow passwd
-- qmail 1.0.3
The major problem is for all the accounts with UID larger
than 65,535 are invalid when chown, su or checkpassword for
qmail-pop3d. But I still can do getpwnam and getpwent perfectly
by Perl or C. There is no such a problem in Solaris 2.6.
I know it's a crazy idea to put tens of thousands accounts in
a single box. But it should work. Performance is acceptable
if seperating mail queues to another machine in my experience.
So I'm curious whether there are any tricks to fix the problem?
Any advice for better scalability is also welcome and highly
appreciated.
Cheers,
Heman Lu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30 Oct 99, at 0:59, Heman Lu wrote:
> Hi,
>
> I'm planning to migrate our mail server from sendmail
> to qmail. There are 55,000+ mail accounts. When simulating
> to grow beyond 65,536 accounts, I encounter some problems.
>
> Here is my test environment:
>
> Hardware: Acer Altos 12000
> -- Pentium III 450 x 2
> -- 1 GB DRAM
> -- IBM Ultra2 SCSI Disk 9GB x 7 (as RAID 5)
>
> Software: RedHat Linux 6.1
> -- With shadow passwd
> -- qmail 1.0.3
>
> The major problem is for all the accounts with UID larger
> than 65,535 are invalid when chown, su or checkpassword for
> qmail-pop3d. But I still can do getpwnam and getpwent perfectly
> by Perl or C. There is no such a problem in Solaris 2.6.
AFAIK, the number of accounts in linux in general is limited by
16bits. I don't know if you can only recompile - the problem _may_
be in glibc, and in ext2 filesystem. (NIS/NIS+ might help - I have
never tried that.)
If you do NOT need them as separate login accounts, but mail-only
accounts, you can use a single-UID setup; I think www.qmail.org
has a page on how. Basically, you have one account for all the
mailboxes and you use qmail-users mechanism to deliver in
specific maildirs, and patched checkpassword to select the right
maildir on pop3 login. (I don't know if you can do with mailboxes...)
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOBnjS1MwP8g7qbw/EQLUeACfV/M6f/8OuRROcoWA6ldyT5aZWtsAnRoZ
mLzoKvc+LZXyvKJG6Ng0Y8sU
=ALTk
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
Peter Abplanalp <[EMAIL PROTECTED]> wrote:
>Hello all. I have been trying to get qmail to work with little success. I
>have probably made some mistakes. Let me start off with the, IMO, worst: I
>removed /var/log/maillog thinking that it was writen by qmail and that
>qmail would recreate it.
If you installed according to LWQ, qmail-send is logging to
/var/log/qmail.
>The original problem I had was something like 'can not
>opendir todo' in the maillog as well as '940965762.308214 delivery 345:
>deferral: Unable_to_chdir_to_maildir._(#4.2.1)/' any time I try to mail a
>local message using 'echo to: me | /var/qmail/bin/qmail-inject'.
Try Russ Nelson's qmail-lint, available from www.qmail.org.
-Dave
This is a known bug in the Microsoft SMTP server (the thing that comes with
the NT Option Pack). It correctly interprets temporary errors as temporary
and retries the message, but unfortunately it tries again IMMEDIATELY, which
causes a lot of useless traffic.
I can't advise as to what the problem is with that particular message; I've
seen the problem pop up with various temporary errors, but it's always MS
SMTP on the other end.
The solution is to tell the remote to get a real mail server - this is
pretty broken behavior. You can also, if you have the tarpitting patches
installed, tarpit the remote server, which will at least slow it down until
the remote administrator fixes it.
shag
=====
Judd Bourgeois | CNM Network +1 (805) 520-7170
Software Architect | 1900 Los Angeles Avenue, 2nd Floor
[EMAIL PROTECTED] | Simi Valley, CA 93065
Quidquid latine dictum sit, altum viditur.
----- Original Message -----
From: Michael Boyiazis <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thu 28 Oct 1999 21.07
Subject: snoop and bare line feeds
> Greetings,
> I occasionally have smtp servers begin to "chatter" with my
> servers and 99% of the time, a telnet to port 25 of the offending server
> yields the dreaded: Microsoft SMTP MAIL
>
> So I block the IP to prevent the chatter as they just keep coming over
> and over again trying to deliver mail which my servers must be saying
> no way to. I ass/u/me that this is a bare-line-feed issue. Since
> everything
> I've read says do the fixcr with "clients" sending buggy mail, my option
> seems to be to block those IP's from sending (tcpserver) and try to get
> mail to them telling them they've been blocked.
>
> I've tried running snoop to see if I could see anything odd with the smtp
> packets, but I really don't know what to look for that is out of the
> ordinary
> so I can tell these folks what to fix. Any suggestions as to what might
> look odd? and what to tell them to fix their mail server?
>
> Thanks,
> mike.
>
> __________________________________________
> NetZero - Defenders of the Free World
> Get your FREE Internet Access and Email at
> http://www.netzero.net/download/index.html
>
Thanks to Judd and Markus for your replies.
I just may add the snippet in there. A daily report
of who is bogging down our servers would let me
get them out of there instead of waiting a few days
for the things to time out or go away for whatever
reason they do.
I was talking with an admin who was wondering if we
were blocking his servers. I mentioned the problem
w/ the bare line feeds and he said he had installed a
patch to get rid of it. So at least I have something to
tell these people. "Patch your broken server...and
have you looked into qmail?" 8^)
Michael Boyiazis -----
[EMAIL PROTECTED]
NetZero
Mail/Sys/Network Admin
> -----Original Message-----
> From: Racer X [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 29, 1999 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: snoop and bare line feeds
>
>
> This is a known bug in the Microsoft SMTP server (the thing
> that comes with
> the NT Option Pack). It correctly interprets temporary
> errors as temporary
> and retries the message, but unfortunately it tries again
> IMMEDIATELY, which
> causes a lot of useless traffic.
>
> I can't advise as to what the problem is with that particular
> message; I've
> seen the problem pop up with various temporary errors, but
> it's always MS
> SMTP on the other end.
>
> The solution is to tell the remote to get a real mail server - this is
> pretty broken behavior. You can also, if you have the
> tarpitting patches
> installed, tarpit the remote server, which will at least slow
> it down until
> the remote administrator fixes it.
and:
> What I did was to patch qmail-smtpd.c to report stray newlines:
> There is a function called straynewline().
> To that function I've added:
> logerr("protoerror: "); logerrpid(); logerrf("error: stray
newlines\n");
> (before the _exit(1); :-)
> To make it work you also need the following code snippet:
> char strnum[FMT_ULONG];
> char sserrbuf[512];
> substdio sserr = SUBSTDIO_FDBUF(write,2,sserrbuf,sizeof(sserrbuf));
> void logerr(s) char *s; { if(substdio_puts(&sserr,s) == -1) _exit(1); }
> void logerrf(s) char *s; { if(substdio_puts(&sserr,s) == -1) _exit(1);
> if(substdio_flush(&sserr) == -1) _exit(1); }
> void logerrpid() { strnum[fmt_ulong(strnum,getpid())] = 0; logerr("pid ");
loger
> r(strnum); logerr(": ");}
> (this is only tested with qmail-1.01 but should also work finde with 1.03)
__________________________________________
NetZero - Defenders of the Free World
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html
Hello world !
How to configure qmail to handle following scenario:
Apache server is running on separate box with numbers
of virtual hosts.
How to convince qmail server to service virtual hosts
mail ?
So far when both www and qmail were on the same box
mail worked perfectly.
Could you help me ?
regards
s.w.
>How to configure qmail to handle following scenario:
>Apache server is running on separate box with numbers of virtual hosts.
>How to convince qmail server to service virtual hosts mail ?
>So far when both www and qmail were on the same box mail worked perfectly.
>Could you help me ?
You need to add an MX record for each domain pointing to the box that's
handling the mail.
--
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
Hello All,
I am still trying to figure out why smtp/pop3 requests take so long
to respond or process when users try to send/retrieve mail off of the
server...
Machine Specs:
Pent-133, 32MB, 1.6GB HD, CD-ROM, 2 Intel EEPro NIC's
eth0 has static class C IP address connected to D-Link Switch
for internet access (Cisco 4700 router with T-1 connected)
eth1 has private ip address of 192.168.3.1 which several machines
go thru to get internet access via IP chains (No problems observed)
Distro is OpenLinux 2.2 (Caldera) with latest security RPM updates
tcp.smtp.cdb allows 127.0.0.1, 192.168.3. and 192.168.2., and any
machine assigned to our class C...The lan segment also has IPX/SPX
traffic on it as we use Novell 3.12 for a file server...
Machine runs caching DNS on port 53 (no problems observed)
Machine runs ssh 1.2.2x on port 22 (no problems from work or home)
Ipchains in rc.local looks like this:
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -j MASQ -s 192.168.3.0/24 -d 0.0.0.0/0
other commands in rc.local (before above lines) are:
/sbin/ifconfig eth1 192.168.3.1 netmask 255.255.255.0 up
# enable ip forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
Here are the start lines for qmail script in init.d
start)
echo -n "Starting: "
env - PATH="/var/qmail/bin:/usr/local/bin" \
qmail-start ./Maildir/ /usr/local/bin/accustamp \
| /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
echo -n "qmail "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -H -R -c100 0 pop-3 /var/qmail/bin/qmail-popup \
nermal.xxxxx.com \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
echo -n "pop3 "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -H -R -x /etc/tcp.smtp.cdb -c100 -u7791 -g2108 0 smtp \
/var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
echo "smtp"
;;
stop)
echo -n "stopping qmail"
killall qmail-send
killall tcpserver
echo
;;
Does anyone have any idea or clues why smtp/pop3d would take so
long to process...This used to work fine under a 2.0.36 >= kernel when
I ran OpenLinux 1.2 Base (what I mean by this is issuing send/receive
on OutLook Express or the same in Eudora Light ran in less than 5 seconds,
but now runs in anywhere from 3 seconds to a full minute in some cases)...
I'm going to cross-post this to the caldera list to see if anyone
there has any ideas (it's driving me and my users crazy, a little at a
time, so I have a woeful look on my face)...
-Bill
I am also facing the same problem. And it is only happened if my client used
private IP (DHCP), and it is not only for POP. Telnet, and PCAnywhere also has the
same problem.
Anybody knows ?
Lukman
Bill Parker wrote:
> Hello All,
>
> I am still trying to figure out why smtp/pop3 requests take so long
> to respond or process when users try to send/retrieve mail off of the
> server...
>
> Machine Specs:
>
> Pent-133, 32MB, 1.6GB HD, CD-ROM, 2 Intel EEPro NIC's
>
> eth0 has static class C IP address connected to D-Link Switch
> for internet access (Cisco 4700 router with T-1 connected)
>
> eth1 has private ip address of 192.168.3.1 which several machines
> go thru to get internet access via IP chains (No problems observed)
>
> Distro is OpenLinux 2.2 (Caldera) with latest security RPM updates
>
> tcp.smtp.cdb allows 127.0.0.1, 192.168.3. and 192.168.2., and any
> machine assigned to our class C...The lan segment also has IPX/SPX
> traffic on it as we use Novell 3.12 for a file server...
>
> Machine runs caching DNS on port 53 (no problems observed)
>
> Machine runs ssh 1.2.2x on port 22 (no problems from work or home)
>
> Ipchains in rc.local looks like this:
>
> /sbin/ipchains -P forward DENY
> /sbin/ipchains -A forward -j MASQ -s 192.168.3.0/24 -d 0.0.0.0/0
>
> other commands in rc.local (before above lines) are:
>
> /sbin/ifconfig eth1 192.168.3.1 netmask 255.255.255.0 up
>
> # enable ip forwarding
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> echo 1 > /proc/sys/net/ipv4/tcp_syncookies
>
> Here are the start lines for qmail script in init.d
>
> start)
> echo -n "Starting: "
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> qmail-start ./Maildir/ /usr/local/bin/accustamp \
> | /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
> echo -n "qmail "
>
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver -H -R -c100 0 pop-3 /var/qmail/bin/qmail-popup \
> nermal.xxxxx.com \
> /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
> echo -n "pop3 "
>
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver -H -R -x /etc/tcp.smtp.cdb -c100 -u7791 -g2108 0 smtp \
> /var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
> echo "smtp"
> ;;
> stop)
> echo -n "stopping qmail"
> killall qmail-send
> killall tcpserver
> echo
> ;;
>
> Does anyone have any idea or clues why smtp/pop3d would take so
> long to process...This used to work fine under a 2.0.36 >= kernel when
> I ran OpenLinux 1.2 Base (what I mean by this is issuing send/receive
> on OutLook Express or the same in Eudora Light ran in less than 5 seconds,
> but now runs in anywhere from 3 seconds to a full minute in some cases)...
>
> I'm going to cross-post this to the caldera list to see if anyone
> there has any ideas (it's driving me and my users crazy, a little at a
> time, so I have a woeful look on my face)...
>
> -Bill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> Archive: http://www.mail-archive.com/[email protected]
I have posted the same question. The defaulthost only applies to mail which
does not have an existing host part.
I was hoping to do the same as you but it was not to be.
At 20:04 16/10/99 , randyboy wrote:
>I wrote earlier about majordomo lists not accepting my masqueraded e-mail
>address. I did some more tests and it seems that host masquerading just
>isn't working.
>
>
>Here is a message from me to a machine running sendmail.
>
> >From [EMAIL PROTECTED] Sat Oct 16 11:37:39 1999
>Date: 16 Oct 1999 11:38:08 -0700
>From: "randyboy" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: hi3
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Priority: 3 (Normal)
>X-MSMail-Priority: Normal
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
>X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
>Importance: Normal
>
>hi3
>
>
>This is what I used to do. The MUA lives on a different node from qmail.
>
>tcpserver -> qmail-smtpd -> qmail-queue -> qmail-send -> qmail-rspawn ->
>qmail-remote
>
>When I first set things up I though setting defaulthost would take care of
>the masquerading, not realizing that only applies to qmail-inject.
>
>I have since switch over to this
>
>tcpserver -> ofmipd -> qmail-queue -> qmail-send -> qmail-rspawn ->
>qmail-remote
>
>but it still doesn't work.
>
>tcpserver is inovked by this:
> /usr/local/bin/tcpserver -x /usr/local/etc/tcp.smtp.cdb -v -u 82
> -g 81 0
>smtp /usr/local/bin/ofmipd /usr/local/etc/ofmip.name.cdb \
> 2>&1 | /var/qmail/bin/splogger smtpd 3 &
>
>and the db for ofmipd contains
> -blackmist.org:
>
>What I was trying to accomplish was to strip out all domain info and replace
>with blackmist.org.
>
>I also tried putting -blackmist.org: in control/rewrite.
>
>But it still doesn't work.
>
>Can somebody please tell me what I'm doing wrong.
>
>r.
