[techtalk] sendmail/Mailman Lag
First, thanks to all who offered suggestions to get Mailman up and running...and it is working just very, very slowly. First, a little info about the machine ("gundam") it is installed on: Redhat 6.2 Sendamail 8.9.3 I believe Procmail handles local delivery in Redhat I have some accounts on gundam subscribed to the list "listfoo" I also have an account on another machine on the network subscribed as well. If I just send a plain old email from one account to the other on gundam it arrives in seconds. If I post to listfoo it takes anywhere from 2-15min to arrive in the boxes of the other subscribers. This huge delivery lag is also the case for the account on another machine so I'm ruling out a local delivery problem. Everything in the maillog looks kosher, here's a snip from a message outgoing to listfoo: sendmail[3220]: JAA03220: from=<[EMAIL PROTECTED]>, size=262, class=0, pri=30262, nrcpts=1, msgid=<[EMAIL PROTECTED]>, proto=ESMTP, relay=IDENT:[EMAIL PROTECTED] [127.0.0.1] Aug 10 09:39:50 gundam sendmail[3221]: JAA03220: to="|/home/mailman/mail/wrapper post listfoo", delay=00:00:00, xdelay=00:00:00, mailer=prog, stat=Sent Here's some headers from a listfoo post (this arrived the same time as one send 20 min before it!?!): Return-Path: <[EMAIL PROTECTED]> Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] [127.0.0.1]) by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03242; Thu, 10 Aug 2000 09:42:01 -0400 Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] [127.0.0.1]) by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03220 for <[EMAIL PROTECTED]>; Thu, 10 Aug 2000 09:39:50 -0400 Date: Thu, 10 Aug 2000 09:39:50 -0400 (EDT) From: jlg <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Listfoo] 9:44 Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0beta5 Precedence: bulk List-Id: listfoo a cool list for testing - Any suggstions? Any more info required to troubleshoot? Jen x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x [EMAIL PROTECTED] x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] Port forwarding the port 21
On Wed, Aug 09, 2000 at 09:03:00PM -0400 or so it is rumoured hereabouts, Beverly Guillermo thought... > I have 2.2.x kernel and I'm using ipchains and ipmasqadm -- > I want to forward the ftp port from one computer to another computer but > it doesn't want to do it. I know about the active and passive modes but I > still cannot get certain commands to act correctly for ftp. (Things like > ls will not work.) > > Here's what I've done (from what I understood): > > $ ipchains -I forward -p udp -s 192.168.1.21/32 21 -j MASQ > $ ipchains -I forward -p tcp -s 192.168.1.21/32 21 -j MASQ > $ ipmasqadm portfw -a -P udp -L 192.168.1.1 21 -R 192.168.1.21 21 > $ ipmasqadm portfw -a -P tcp -L 192.168.1.1 21 -R 192.168.1.21 21 > > This doesn't work and I think it has to do with the passive > mode anyone let me know what I'm doing wrong please. > Guess... Is it anything to do with forwarding port 20 (the ftp data port) also? -- Conor Daly <[EMAIL PROTECTED]> Domestic Sysadmin :-) ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] mailman help
On Wed, Aug 09, 2000 at 11:21:59PM +0200, Olivier Tharan wrote: > Sendmail does not like group-writable directories very much. This is > because everyone the same group as you could potentially change your > .forward file and thus receive your email. > > do an 'ls -ld /usr/share/mailman' and look that the directory is indeed > group-writable; beware also of /usr and /usr/share as sendmail won't > like either them being group-writable (but they shouldn't be). Then do a > 'chmod g-w /usr/share/mailman' > > If the latter is not an option for you (eg Mailman has to write things > in this directory with group access and so on), you can use as a last > resort sendmail's option 'O GroupWritableForwardFileSafe'. Oops. I just realized that I sent my last reply off-list yesterday. The problem that was breaking mailman was that the aliases needed to be set to the link in /etc/smrsh/ rather than /home/mailman/mail. -- Aaron Malone ([EMAIL PROTECTED]) System Administrator I can bend minds with my spoon. Poplar Bluff Internet, Inc. http://www.semo.net ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] sendmail/Mailman Lag
On Thu, 10 Aug 2000, JLG wrote: I think I've figuered out thatMailman is using cron to send out its messages. How can I make the job run more frequently? in /home/mailman/cron there are the following files: checkdbs crontab.in gate_news mailpasswds nightly_gzip paths.py paths.pyc qrunner senddigests would crontab.in be the file I need to change? Mailman's docs are kind of sparse but i can include a copy of this file if it'll help Jen > First, thanks to all who offered suggestions to get > Mailman up and running...and it is working just very, very slowly. > > First, a little info about the machine ("gundam") it is installed on: > Redhat 6.2 > Sendamail 8.9.3 > I believe Procmail handles local delivery in Redhat > > I have some accounts on gundam subscribed to the list "listfoo" > I also have an account on another machine on the network subscribed as > well. > > If I just send a plain old email from one account to the other on gundam > it arrives in seconds. If I post to listfoo it takes anywhere from > 2-15min to arrive in the boxes of the other subscribers. This > huge delivery lag is also the case for the account on another machine so > I'm ruling out a local delivery problem. > > Everything in the maillog looks kosher, here's a snip from a message > outgoing to listfoo: > > > sendmail[3220]: JAA03220: from=<[EMAIL PROTECTED]>, size=262, > class=0, pri=30262, nrcpts=1, > msgid=<[EMAIL PROTECTED]>, > proto=ESMTP, relay=IDENT:[EMAIL PROTECTED] [127.0.0.1] > Aug 10 09:39:50 gundam > sendmail[3221]: JAA03220: to="|/home/mailman/mail/wrapper post listfoo", > delay=00:00:00, xdelay=00:00:00, mailer=prog, stat=Sent > > > > Here's some headers from a listfoo post (this arrived the same time as > one send 20 min before it!?!): > > Return-Path: <[EMAIL PROTECTED]> > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > [127.0.0.1]) > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03242; > Thu, 10 Aug 2000 09:42:01 -0400 > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > [127.0.0.1]) > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03220 > for <[EMAIL PROTECTED]>; Thu, 10 Aug 2000 09:39:50 -0400 > Date: Thu, 10 Aug 2000 09:39:50 -0400 (EDT) > From: jlg <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > MIME-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > Subject: [Listfoo] 9:44 > Sender: [EMAIL PROTECTED] > Errors-To: [EMAIL PROTECTED] > X-BeenThere: [EMAIL PROTECTED] > X-Mailman-Version: 2.0beta5 > Precedence: bulk > List-Id: listfoo a cool list for testing > > > - > > Any suggstions? Any more info required to troubleshoot? > > Jen > > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > [EMAIL PROTECTED] > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > > > > ___ > techtalk mailing list > [EMAIL PROTECTED] > http://www.linux.org.uk/mailman/listinfo/techtalk > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x [EMAIL PROTECTED] x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] RESOLVED!!sendmail/Mailman Lag
On Thu, 10 Aug 2000, JLG wrote: Hey Folks, I think I just solved my own problem...sorry that last message was so incoherant but i was trying to dash it off quickly so the other sysadmin wouldn't catch me :) ! (new job!) Jen > On Thu, 10 Aug 2000, JLG wrote: > > I think I've figuered out thatMailman is using cron to send out its > messages. How can I make the job run more frequently? > > in /home/mailman/cron there are the following files: > > checkdbs crontab.in gate_news mailpasswds nightly_gzip paths.py > paths.pyc qrunner senddigests > > would crontab.in be the file I need to change? > Mailman's docs are kind of sparse but i can include a copy of this file if > it'll help > > Jen > > > First, thanks to all who offered suggestions to get > > Mailman up and running...and it is working just very, very slowly. > > > > First, a little info about the machine ("gundam") it is installed on: > > Redhat 6.2 > > Sendamail 8.9.3 > > I believe Procmail handles local delivery in Redhat > > > > I have some accounts on gundam subscribed to the list "listfoo" > > I also have an account on another machine on the network subscribed as > > well. > > > > If I just send a plain old email from one account to the other on gundam > > it arrives in seconds. If I post to listfoo it takes anywhere from > > 2-15min to arrive in the boxes of the other subscribers. This > > huge delivery lag is also the case for the account on another machine so > > I'm ruling out a local delivery problem. > > > > Everything in the maillog looks kosher, here's a snip from a message > > outgoing to listfoo: > > > > > > sendmail[3220]: JAA03220: from=<[EMAIL PROTECTED]>, size=262, > > class=0, pri=30262, nrcpts=1, > > msgid=<[EMAIL PROTECTED]>, > > proto=ESMTP, relay=IDENT:[EMAIL PROTECTED] [127.0.0.1] > > Aug 10 09:39:50 gundam > > sendmail[3221]: JAA03220: to="|/home/mailman/mail/wrapper post listfoo", > > delay=00:00:00, xdelay=00:00:00, mailer=prog, stat=Sent > > > > > > > > Here's some headers from a listfoo post (this arrived the same time as > > one send 20 min before it!?!): > > > > Return-Path: <[EMAIL PROTECTED]> > > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > > [127.0.0.1]) > > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03242; > > Thu, 10 Aug 2000 09:42:01 -0400 > > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > > [127.0.0.1]) > > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03220 > > for <[EMAIL PROTECTED]>; Thu, 10 Aug 2000 09:39:50 -0400 > > Date: Thu, 10 Aug 2000 09:39:50 -0400 (EDT) > > From: jlg <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Message-ID: <[EMAIL PROTECTED]> > > MIME-Version: 1.0 > > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Subject: [Listfoo] 9:44 > > Sender: [EMAIL PROTECTED] > > Errors-To: [EMAIL PROTECTED] > > X-BeenThere: [EMAIL PROTECTED] > > X-Mailman-Version: 2.0beta5 > > Precedence: bulk > > List-Id: listfoo a cool list for testing > > > > > > - > > > > Any suggstions? Any more info required to troubleshoot? > > > > Jen > > > > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > > [EMAIL PROTECTED] > > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > > > > > > > > ___ > > techtalk mailing list > > [EMAIL PROTECTED] > > http://www.linux.org.uk/mailman/listinfo/techtalk > > > > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > [EMAIL PROTECTED] > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x > > > > ___ > techtalk mailing list > [EMAIL PROTECTED] > http://www.linux.org.uk/mailman/listinfo/techtalk > x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x [EMAIL PROTECTED] x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] Problem setting up dual-homed IBM NetFinity 1000
On Wed, 09 Aug 2000, C. M. Martin wrote: > I have an IBM NetFinity 1000 running Caldera OpenLinux 2.4. The system needs > to be dual-homed, and the system seems to recognize both ethernet cards. One > is on eth0, IRQ11, and is working properly. Network connectivity is just fine. > The other is eth1, IRQ10, different I/O memory range from the first card. The > box can ping itself at that address, but can't see any other box on that > network, and nothing on that net can see this box. > > I went into the network settings with COAS and found that the default gateway > wasn't set on eth1. I tried setting it, but the system would not save the new > settings. Sometimes it gives me a python error saying it cannot communicate > with the network, sometimes not. It reads: > > Error when executing command ip-config change eth1 > the command produced the following output: > SIOCADDRT: Network is unreachable > eth1: initialization failed It's probably a routing problem. Here's how to fix/troubleshoot it interactively, though I don't know how to fix it with COAS. Run "/sbin/route" and see what it gives you ("man route" if you need help understanding what it says). Ifconfig just sets up the IP on the card; it doesn't tell the kernel which interface to send packets through in order to get to a certain net. The kernel needs to know: - that it can send packets to eth1 to get to itself - that it can send packets to eth1 to get to the rest of the world. IIRC, that means you need to do something like: # /sbin/route add -host $IP_FOR_ETH1 eth1 # /sbin/route add -net default gw $YOUR_GATEWAY netmask $YOUR_NETMASK eth1 Let me know if this works; I haven't tested it, but I was playing with this yesterday, so it's fairly fresh in my head. srl -- --- Shane R. Landrum + [EMAIL PROTECTED] + Software/Systems Engineer -- www.ainnovations.com - Anansi Innovations -- ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] sendmail/Mailman Lag
Jen, I run Mailman 2.0b2 on one production server and 2.0b5 on the other production server for my own lists. crontab.in on my systems contains entries for logging, archiving, mail to news gateways, etc. but doesn't appear to have any direct impact on when a message is delivered, except in the case of retrying previously bounced messages. Mailman has a setting for each list which determines how many simultaneous outbound connections can be open. By default, this is set to "5" - probably good for the load on your server, but not great when you have hundreds of list members (as I do). If your server's hardware/RAM/network connection are sufficient to handle it, you can improve delivery time somewhat by increasing the number of simultaneous deliveries. Some of it is just "how mailman works" - From /home/mailman/scripts/mailcmd: # Create the message object msg = Message.Message(sys.stdin) # Immediately queue the message for disposition by qrunner, most likely in # about a minute from now. The advantage to this approach is that # messages should never get lost -- some MTAs have a hard limit to the # time a filter prog can run. Postfix is a good example; if the limit is # hit, the proc is SIGKILL'd giving us no chance to save the message. It # could take a long time to acquire the lock. This way we're fairly safe # against catastrophe at the expense of more disk I/O. This makes it look like the delay is intentional, as mailman creates a database object out of the mail object. So some of the delay may be unavoidable. Kind of rambly here... hope some of this helps. :) It was a good excuse for me to dig around a little and get a better handle on what Mailman is doing... -Saska On Thu, 10 Aug 2000, JLG wrote: > On Thu, 10 Aug 2000, JLG wrote: > > I think I've figuered out thatMailman is using cron to send out its > messages. How can I make the job run more frequently? > > in /home/mailman/cron there are the following files: > > checkdbs crontab.in gate_news mailpasswds nightly_gzip paths.py > paths.pyc qrunner senddigests > > would crontab.in be the file I need to change? > Mailman's docs are kind of sparse but i can include a copy of this file if > it'll help > > Jen > > > First, thanks to all who offered suggestions to get > > Mailman up and running...and it is working just very, very slowly. > > > > First, a little info about the machine ("gundam") it is installed on: > > Redhat 6.2 > > Sendamail 8.9.3 > > I believe Procmail handles local delivery in Redhat > > > > I have some accounts on gundam subscribed to the list "listfoo" > > I also have an account on another machine on the network subscribed as > > well. > > > > If I just send a plain old email from one account to the other on gundam > > it arrives in seconds. If I post to listfoo it takes anywhere from > > 2-15min to arrive in the boxes of the other subscribers. This > > huge delivery lag is also the case for the account on another machine so > > I'm ruling out a local delivery problem. > > > > Everything in the maillog looks kosher, here's a snip from a message > > outgoing to listfoo: > > > > > > sendmail[3220]: JAA03220: from=<[EMAIL PROTECTED]>, size=262, > > class=0, pri=30262, nrcpts=1, > > msgid=<[EMAIL PROTECTED]>, > > proto=ESMTP, relay=IDENT:[EMAIL PROTECTED] [127.0.0.1] > > Aug 10 09:39:50 gundam > > sendmail[3221]: JAA03220: to="|/home/mailman/mail/wrapper post listfoo", > > delay=00:00:00, xdelay=00:00:00, mailer=prog, stat=Sent > > > > > > > > Here's some headers from a listfoo post (this arrived the same time as > > one send 20 min before it!?!): > > > > Return-Path: <[EMAIL PROTECTED]> > > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > > [127.0.0.1]) > > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03242; > > Thu, 10 Aug 2000 09:42:01 -0400 > > Received: from gundam.x.com (IDENT:[EMAIL PROTECTED] > > [127.0.0.1]) > > by gundam.x.com (8.9.3/8.9.3) with ESMTP id JAA03220 > > for <[EMAIL PROTECTED]>; Thu, 10 Aug 2000 09:39:50 -0400 > > Date: Thu, 10 Aug 2000 09:39:50 -0400 (EDT) > > From: jlg <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Message-ID: <[EMAIL PROTECTED]> > > MIME-Version: 1.0 > > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Subject: [Listfoo] 9:44 > > Sender: [EMAIL PROTECTED] > > Errors-To: [EMAIL PROTECTED] > > X-BeenThere: [EMAIL PROTECTED] > > X-Mailman-Version: 2.0beta5 > > Precedence: bulk > > List-Id: listfoo a cool list for testing > > > > > > - > > > > Any suggstions? Any more info required to troubleshoot? > > > > Jen -- Saska - [EMAIL PROTECTED] - http://www.noogie.com/~saska "He's an affable enough screen presence, but you'd be affable too if you could generate a lucrative movie career by copulating with baked goods." -Paul Tatara on Jason Biggs ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org
[techtalk] ISDN and Linux
Hi I've tried to do this before unsuccessfully but I thought I'd have another go at it. At the moment my network at home consists of two pooters. A doze box called George and a Linux box called Dot. ATM i am connecting to the net throughGeorge because I have a USB TA (I know there is slowly getting to be USB support for Linux but i dont have USB on Dot). I bought an ASUSCOM ISDNlink card for Dot as it is supposed to be supported by Redhat, and its in the list in isdn-config (redhat 6.2) I would really like to be able to connect to the net from Linux and set it up as a firewall, but so far all attempts to get the card even recognised as being there seem to have failed. Any ideas? Rachel ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
Re: [techtalk] LILO >1024 cylinders?
Thanks, I'll give that a try. Any pointers as to how to get this? I'm still kind of new to Linux/Debian ... the way I know to get files is to use apt-get. When we tried this for LILO, it didn't get the latest. Thanks! Jen - Original Message - From: "Malcolm Tredinnick" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 09, 2000 8:54 PM Subject: Re: [techtalk] LILO >1024 cylinders? The latest LILO versions (version 21.3 and later) can do this, using the lba32 option in lilo.conf (or -L on the command line). Your BIOS needs to be fairly recent to allow this to work, but apprently most BIOS chips that are 1998 or later will suffice. Apparently, the Potato version of Debian (frozen version) contains LILO 21.4, so you can even get a debian package for it. :-) Cheers, Malcolm ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk
[techtalk] Anyone tried Orb drives?
The Orb drive sounds pretty cool ... really inexpensive compared to Jaz. Has anyone had any luck with getting these to work on Linux? I've searched the Web, and it seems like people have had trouble w/ the SCSI version, which was the one I was looking at getting. Any advice is appreciated! Thanks! Jen ___ techtalk mailing list [EMAIL PROTECTED] http://www.linux.org.uk/mailman/listinfo/techtalk