qmail Digest 10 Dec 2000 11:00:01 -0000 Issue 1209
Topics (messages 53802 through 53809):
Re: ezmlm response
53802 by: Charles Cazabon
big-concurrency.patch
53803 by: Federico Edelman Anaya
53804 by: Charles Cazabon
53805 by: Sean Reifschneider
all mail forwarding and catching all bounces
53806 by: Alex Kramarov
IPCHAINS and Qmail
53807 by: Steve Manes
53808 by: Sean Reifschneider
53809 by: Timothy Legant
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Liberty <[EMAIL PROTECTED]> wrote:
> My site's host uses Qmail for the mail list, but
> does not provide assistance for the advanced features.
> How can I set up masquerading so when I send mail
> to my email list no one can obtain the address of the
> list?
> Recently my list was spammed because of it's
> visibility in the "To" address box when I send
> messages out to it.
Is your mailing list an ezmlm list, or just a .qmail file with a bunch of
forward directives in it?
If it's ezmlm (which means this question should be asked on the ezmlm list
instead of the qmail list), you can fix this by making the list moderated,
so you can approve all messages, or make it a read-only list, so only you
can send messages at all. You could also configure it to only accept
submissions from list members.
If it's just a .qmail file, have the first line be a pipe to a script, which
checks either the originating IP address or the envelope sender (less secure).
The script should exit 0 if the message is to be delivered to the rest of the
list, or 99 to drop it on the floor. `man qmail-command` for more details.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
A few days ago .. I post on the list many question about
big-concurrency.patch ...
I was reading other list about Qmail and I get this solution about the
problem with the FD ..
This is the log whit error:
Report of Qmailanalog:
- Errors of FD?:
24 6.36 /bin/sh: /usr/bin/ezmlm-return: Too many open files in
system/
16 28.13 /bin/sh: /usr/bin/ezmlm-weed: Too many open files in
system/
92 27.81 /bin/sh: error in loading shared libraries: libc.so.6:
cannot open shared object file: Error 23/
59 41.43 /bin/sh: error in loading shared libraries: libdl.so.2:
cannot open shared object file: Error 23/
48 63.30 /bin/sh: error in loading shared libraries:
libncurses.so.5: cannot open shared object file: Error 23/
58 18.57 /usr/bin/ezmlm-return: error in loading shared libraries:
libc.so.6: cannot open shared object file: Error 23/
106 37.99 /usr/bin/ezmlm-return: error in loading shared libraries:
libcrypt.so.1: cannot open shared object file: Error 23/
4 1.46 /usr/bin/ezmlm-return: error in loading shared libraries:
libm.so.6: cannot open shared object file: Error 23/
- Other error:
851 3182.23 Connected to 200.41.50.10 but connection died. (#4.4.2)/
1 60.03 Connected to 200.41.50.7 but connection died. (#4.4.2)/
316 12453.57 Connected to 200.41.50.9 but connection died. (#4.4.2)/
1 0.20 Sorry, I couldn't find any host by that name. (#4.1.2)/
3 0.74 bin/qmail-local: error in loading shared libraries:
libc.so.6: cannot open shared object file: Error 23/
The solution was:
echo "65536" > /proc/sys/fs/inode-max
echo "16384" > /proc/sys/fs/file-max
So.. you need to do this every system reboot, I don't know how to make
this persistent.. anybody have idea or know how to make this persistent?
Thanks :)
Federico Edelman Anaya <[EMAIL PROTECTED]> wrote:
>
> The solution was:
>
> echo "65536" > /proc/sys/fs/inode-max
> echo "16384" > /proc/sys/fs/file-max
>
> So.. you need to do this every system reboot, I don't know how to make
> this persistent.. anybody have idea or know how to make this persistent?
This is really more of a Unix/Linux question than anything else. However,
try adding those two lines to the end of /etc/rc.d/rc.local or your
system's equivalent.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
On Sat, Dec 09, 2000 at 12:31:16PM -0600, Charles Cazabon wrote:
>> echo "65536" > /proc/sys/fs/inode-max
>> echo "16384" > /proc/sys/fs/file-max
>
>This is really more of a Unix/Linux question than anything else. However,
>try adding those two lines to the end of /etc/rc.d/rc.local or your
>system's equivalent.
Also, realize that by default user's are limited to 1024 open files unless
you use ulimit -n to increase it.
Sean
--
It's bad precident for a president to win through illegal influence of
the ballots and election process.
Sean Reifschneider, Inimitably Superfluous <[EMAIL PROTECTED]>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
|
I am new to this list, but i am a diligent reader, and after reading
all documentation on q-mail i couldn't find two things i need a lot ,
after I successfully installed a qmail server and put it instead of my old
exchange, which was giving me a lot of trouble before ...
1. Is it possible to copy every bounce message generated to any user
to another user (in this case - me : i want to know when my users do
not succeede sending, or someone from the outside is sending mail to
a wrong address in my domain)
2. Is it possible to forward all mail (except the local mail, as
listed in control/local) to another host - and I am not talking of
smtproutes, which takes place after the original e-mail has been parsed
and copies of it has been generated to every domain it's destined to
go. I want to forward all non-local mail to the server of my
provider, so that if someone sends a 2MB mail to 50 recipients, which
unfortunately my users do sometimes, that will not take my 128 bit line
till the rest of the day sending 50 copies of the mail (and instead, of
course, forward 1 mail to my provider's server, so he would have to send
these 50 copies).
I thank you in advance and patiently waiting for your answer
...
Alex
Incredimail Admin |
__________________________________________
Created and best viewed
with IncrediMail!
Get your free copy at: www.incredimail.com |
I installed 'ipchains' on my Redhat 7.0 mail server today. Not being a
firewall guru, I had the www.linux-firewall-tools.com/linux/firewall/ site
build me a script. I had pretty good luck with it on a web server but I've
run into a problem with Qmail. As soon as I activate the firewall, mail
gets backed up.
/var/log/messages says:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x0000 T=64 (#37)
Dec 10 01:02:55 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
124:4396 204.242.84.1:25 L=60 S=0x00 I=46421 F=0x0000 T=64 SYN (#37)
Any idea what's causing this?
The problematic firewall script is rather large (25k) so I've posted it on
my web server at http://www.magpie.com/work/rc.firewall.html
-----------------------[ http://www.magpie.com ]-------=o&>o-------
Steve Manes
Brooklyn, N'Yawk
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
>Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
>124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x0000 T=64 (#37)
>Dec 10 01:02:55 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
>124:4396 204.242.84.1:25 L=60 S=0x00 I=46421 F=0x0000 T=64 SYN (#37)
>
>Any idea what's causing this?
ipchains is blocking incoming connections to port 25/tcp. You know, the
e-mail port.
>The problematic firewall script is rather large (25k) so I've posted it on
>my web server at http://www.magpie.com/work/rc.firewall.html
Yikes! 25KB?!? I have a hard time imagining it being a tenth the size
of that. Allow incoming 25 and 113 TCP, maybe 110 and 143, allow outgoing
connections, and allow DNS. Probably also want SSH... A dozen rules?
Sean
--
I never thought I'd live in a country where physical violence would be used
to disenfranchise voters. Have you heard about Bush supporters rioting?
Sean Reifschneider, Inimitably Superfluous <[EMAIL PROTECTED]>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
On Sun, Dec 10, 2000 at 01:31:54AM -0700, Sean Reifschneider wrote:
> On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
> >Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
> >124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x0000 T=64 (#37)
> >Dec 10 01:02:55 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
> >124:4396 204.242.84.1:25 L=60 S=0x00 I=46421 F=0x0000 T=64 SYN (#37)
> >
> >Any idea what's causing this?
>
> ipchains is blocking incoming connections to port 25/tcp. You know, the
> e-mail port.
Er, it looks like exactly the opposite. ipchains is blocking _outgoing_
connections _to_ port 25 on other machines. Steve's IP is
166.84.147.124.
I don't use ipchains and don't know how to fix this. Hopefully someone
can tell you how to open up the ports qmail needs for output.
-thl
