From mantel@suse.de Tue May 5 23:17:25 1998 From: mantel@suse.de To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Mail Loop Date: Wed, 06 May 1998 01:17:25 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6119935559494701713==" --===============6119935559494701713== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, the following has happened: Mail to Jean-Michel_Dossogne@f7111.surf.be could not be delivered due to an error on their site. Their mailsystem is misconfigured and ignores the Return-Path which is to be used for error notifications. So the bounced mail did not go to the list maintainer, but to the list itself. And therefore it got sent to Jean-Michel_Dossogne@f7111.surf.be again and so on. A classic mail loop which happens on many mailing lists from time to time. There's nothing the list maintainers can do other than unsubscribing the person as soon as they become aware of the problem. After unsubscribing, there are still mails in the queue, so it will take some time until the trouble stops. Blame the sysadmin at surf.be, not the one at suse.com. It's almost impossible to detect this kind of loop (our loop detection did prevent lots of loops in the past). Hubert -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============6119935559494701713==-- From braden@shadow.net Wed May 6 02:19:02 1998 From: braden@shadow.net To: users@lists.opensuse.org Subject: RE: [S.u.S.E. Linux] Mail Loop Date: Tue, 05 May 1998 22:19:02 -0400 Message-ID: <000001bd7895$5606fa40$01018080@bonezero> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6480961392968416498==" --===============6480961392968416498== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: owner-suse-linux-e@suse.com [mailto:owner-suse-linux-e@suse.com]On > Behalf Of Hubert Mantel > Sent: Tuesday, May 05, 1998 7:17 PM > To: suse-linux-e@suse.com > Subject: [S.u.S.E. Linux] Mail Loop > Hi, > > the following has happened: > > Mail to Jean-Michel_Dossogne@f7111.surf.be could not be delivered due to > an error on their site. Their mailsystem is misconfigured and ignores the > Return-Path which is to be used for error notifications. So the bounced > mail did not go to the list maintainer, but to the list itself. And > therefore it got sent to Jean-Michel_Dossogne@f7111.surf.be again and so > on. A classic mail loop which happens on many mailing lists from time to > time. > > There's nothing the list maintainers can do other than unsubscribing the > person as soon as they become aware of the problem. After unsubscribing, > there are still mails in the queue, so it will take some time until the > trouble stops. Would refusing non-subscriber submissions curb this at all? Yeah, I know this isn't you guys' fault--but nonetheless, it's gotten rather ridiculous. I seem still to be receiving the backed-up notifications even now. Prismatic Booger Braden N. McDaniel, braden@shadow.net <http://www.shadow.net/0.000000E+00braden/<= /A>> -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============6480961392968416498==-- From mantel@suse.de Wed May 6 09:26:49 1998 From: mantel@suse.de To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Re: Mail Loop Date: Wed, 06 May 1998 11:26:49 +0200 Message-ID: In-Reply-To: <000001bd7895$5606fa40$01018080@bonezero> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4581794116073713942==" --===============4581794116073713942== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, On Tue, 5 May 1998, Braden N. McDaniel wrote: > Would refusing non-subscriber submissions curb this at all? Yes, but this would cause other problems: Several people are posting from another account than they subscribed, so this would become impossible. > Yeah, I know this isn't you guys' fault--but nonetheless, it's gotten rather > ridiculous. I seem still to be receiving the backed-up notifications even > now. Yes, it's bad. But there are not only mails in our queue but also at surf.be ;-( > Prismatic Booger > Braden N. McDaniel, braden@shadow.net > <http://www.shadow.net/0.000000E+00braden= />> Hubert PS: Some month ago somebody did set up a procmail file that responded to _every_ mail of the german list. In one night this guy did produce more than 100.000 mails. It took more than a day to get rid of them (apparently he was connecting via UUCP, so mails were coming in quite some time after unsubscribing him).=20 -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============4581794116073713942==-- From Ted.Harding@nessie.mcc.ac.uk Wed May 6 11:40:45 1998 From: Ted.Harding@nessie.mcc.ac.uk To: users@lists.opensuse.org Subject: RE: [S.u.S.E. Linux] Re: Mail Loop Date: Wed, 06 May 1998 12:40:45 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0353440632712465907==" --===============0353440632712465907== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 06-May-98 Hubert Mantel wrote: > On Tue, 5 May 1998, Braden N. McDaniel wrote: >> Would refusing non-subscriber submissions curb this at all? >=20 > Yes, but this would cause other problems: Several people are posting from > another account than they subscribed, so this would become impossible. Agreed! I co-run a list where for "political" reasons we have to impose this constraint. We regularly have to rescue people who find themselves unable to post (usually because their local sysadmins have altered their email alias or the like -- why DO these guys keep moving the furniture around?). Not a reasonable option for an "ordinary" list (unless you get heavy spam). >> Yeah, I know this isn't you guys' fault--but nonetheless, it's gotten rath= er >> ridiculous. I seem still to be receiving the backed-up notifications even >> now. >=20 > Yes, it's bad. But there are not only mails in our queue but also at > surf.be I've known much worse -- remembering one night when the Linux-Development-Apps (IIRC) digest got into a loop with a screwed site in Australia which sent the whole digest (about 200K in the first instance) back to the digestifier which then ... (in ever-larger copies)! My local Univ mailhost then normally had ab= out 20MB free space on /var/spool/mail which soon filled up with this stuff. After unsubscribing from the digest I then sat up until about 4am deleting further copies until the backlog was cleared. The digest manager later wrote to me th= at his own mail spool filled with over 100MB until his server folded under the weight. On a practical note: suse-linux is served by majordomo, and I don't know if MD has the facility: but the above "political" list runs on LISTSERV which can be set to detect the presence of the list address occurring later in the message, resulting in the message then being returned to the originating site as a "possible mailloop", and it doesn't get sent to the list. This has its own problems (if a user's mailer incorrectly quotes headers in the included message-copy in a reply, then the same happens -- which is not what the repli= er intended, but since they shouldn't do that in the first place it's only right that it should bounce back to them so that they can get it put right at their end). This resource is very effective at detecting attempts to send a message back to the list. It also means that such cases can be forwarded to the postmaster at the offending site, which is where they should end up: let the manager of the bad site get a full mailbox, instead of everybody else. However, I noticed that someone's attempt to cc: to postmaster@surf.be also got bounced on the grounds that it couldn't be delivered to that address either, even though the bounce was apparently sent back by "postmaster@surf.b= e". That is some mean site ... On another practical note: All you guys who mailed to the list while this was in full swing only made the problem worse since all your messages joined the mail-loop stream! Mail-loops are rare, but when they occur it is a VERY unstable situation. Correct action is inaction: good-humouredly, do nothing; and wait for the managers to clear it up. If (as in the case I described abov= e) you feel you HAVE to unsubscribe, then take care to send your command to the admin service of the list (in this case majordomo@suse.com, as appended to all the suse-linux mails ... ). Even then, it may be some time before the backlog runs dry. Remember that even list managers sometimes sleep: disasters can build up unnoticed overnight (in some other timezone than your own ... ). Detection and correction may take a little time. A mail-loop is almost always arises through someone else's fault, so don't blast off blame to the wrong address. Best wishes to all, and thanks to Bodo Bauer and colleagues for breaking the loop. Ted. -------------------------------------------------------------------- E-Mail: (Ted Harding) Date: 06-May-98 Time: 12:40:45 -------------------------------------------------------------------- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0353440632712465907==-- From brauki@cww.de Wed May 6 12:39:19 1998 From: brauki@cww.de To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Re: Mail Loop Date: Wed, 06 May 1998 14:39:19 +0200 Message-ID: <355059F7.5EE39636@cww.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1034024650133220436==" --===============1034024650133220436== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hubert Mantel wrote: >=20 > Hi, >=20 > On Tue, 5 May 1998, Braden N. McDaniel wrote: >=20 > > Would refusing non-subscriber submissions curb this at all? >=20 > Yes, but this would cause other problems: Several people are posting from > another account than they subscribed, so this would become impossible. I appreciate that possibility. For the risks: Well, I've tried procmail and I think I've to file all those RE: messages quoting the whole rubbish to the /dev/zero folder ;-) >=20 > > Yeah, I know this isn't you guys' fault--but nonetheless, it's gotten rat= her > > ridiculous. I seem still to be receiving the backed-up notifications even > > now. >=20 > Yes, it's bad. But there are not only mails in our queue but also at > surf.be ;-( >=20 > > Prismatic Booger > > Braden N. McDaniel, braden@shadow.net > > <http://www.shadow.net/0.000000E+00brad= en/>> >=20 > Hubert >=20 > PS: Some month ago somebody did set up a procmail file that responded to > _every_ mail of the german list. In one night this guy did produce more > than 100.000 mails. It took more than a day to get rid of them (apparently > he was connecting via UUCP, so mails were coming in quite some time after > unsubscribing him). Oh, I remember him. Think he had to buy a free beer for everyone on the list. ;-) Wanted to be wise, tell everybody that unsubscribed into the list to unsubscribe at majordomo (hello Patrick are you still with the list ;-)) with his procmail. unfortunetely the dreadful words appear in every mail... J=C3=BCrgen --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D __ _ J=C3=BCrgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ = Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /____/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============1034024650133220436==-- From phil@servcom.com Thu May 7 02:05:25 1998 From: phil@servcom.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Re: Mail Loop Date: Wed, 06 May 1998 18:05:25 -0800 Message-ID: <355116E5.422C7626@servcom.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0550685345225351507==" --===============0550685345225351507== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Good advice! (Ted Harding) wrote: >=20 <(snip!)> >Correct action is inaction: good-humouredly, do nothing; > and wait for the managers to clear it up. If (as in the case I described ab= ove) > you feel you HAVE to unsubscribe, then take care to send your command to the > admin service of the list (in this case majordomo@suse.com, as appended to = all > the suse-linux mails ... ). Even then, it may be some time before the backl= og > runs dry. >=20 > Remember that even list managers sometimes sleep: disasters can build up > unnoticed overnight (in some other timezone than your own ... ). Detection = and > correction may take a little time. A mail-loop is almost always arises thro= ugh > someone else's fault, so don't blast off blame to the wrong address. >=20 > Best wishes to all, and thanks to Bodo Bauer and colleagues for breaking the > loop. >=20 > Ted. >=20 > -------------------------------------------------------------------- > E-Mail: (Ted Harding) > Date: 06-May-98 Time: 12:40:45 > -------------------------------------------------------------------- > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e -- phil@servcom.com {*} Hell, by the time a man scratches his ass, clears his throat and tells me how smart he is, we've already wasted fifteen minutes! --Lyndon B. Johnson -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0550685345225351507==-- From vhearn@wenet.net Thu May 7 03:09:31 1998 From: vhearn@wenet.net To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Re:Glokkenspeil Date: Wed, 06 May 1998 20:09:31 -0700 Message-ID: <355125EB.68D84332@wenet.net> In-Reply-To: <355059F7.5EE39636@cww.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2414932049487176568==" --===============2414932049487176568== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable just spam the serversending...wouldin't that wake them up????i dunno it's their fault(i dunno all the technical params)sorry it just seems that the server should be alerted of a bounce yours truly, #FrAcTeL23# Juergen Braukmann wrote: > Hubert Mantel wrote: > > > > Hi, > > > > On Tue, 5 May 1998, Braden N. McDaniel wrote: > > > > > Would refusing non-subscriber submissions curb this at all? > > > > Yes, but this would cause other problems: Several people are posting from > > another account than they subscribed, so this would become impossible. > > I appreciate that possibility. For the risks: Well, I've tried procmail > and I think I've to file all those RE: messages quoting the whole > rubbish to the /dev/zero folder ;-) > > > > > Yeah, I know this isn't you guys' fault--but nonetheless, it's gotten r= ather > > > ridiculous. I seem still to be receiving the backed-up notifications ev= en > > > now. > > > > Yes, it's bad. But there are not only mails in our queue but also at > > surf.be ;-( > > > > > Prismatic Booger > > > Braden N. McDaniel, braden@shadow.net > > > <http://www.shadow.net/0.000000E+00br= aden/>> > > > > Hubert > > > > PS: Some month ago somebody did set up a procmail file that responded to > > _every_ mail of the german list. In one night this guy did produce more > > than 100.000 mails. It took more than a day to get rid of them (apparently > > he was connecting via UUCP, so mails were coming in quite some time after > > unsubscribing him). > > Oh, I remember him. Think he had to buy a free beer for everyone on the > list. ;-) > Wanted to be wise, tell everybody that unsubscribed into the list to > unsubscribe at majordomo (hello Patrick are you still with the list ;-)) > with his procmail. unfortunetely the dreadful words appear in every > mail... > > J=C3=BCrgen > > -- > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D __ _ > J=C3=BCrgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ > Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /____/_/_//_/\_,_/ /_/\_\ > -- > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============2414932049487176568==-- From leonmcclatchey@homemail.com Thu May 7 04:19:29 1998 From: leonmcclatchey@homemail.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Mail Loop Date: Wed, 06 May 1998 23:19:29 -0500 Message-ID: <35513650.C9447305@homemail.com> In-Reply-To: <000001bd7895$5606fa40$01018080@bonezero> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7280754739844911928==" --===============7280754739844911928== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Braden N. McDaniel wrote: > the following has happened: > > > > Mail to Jean-Michel_Dossogne@f7111.surf.be could not be delivered due to > > an error on their site. Their mailsystem is misconfigured and ignores the > > Return-Path which is to be used for error notifications. So the bounced > > mail did not go to the list maintainer, but to the list itself. And > > therefore it got sent to Jean-Michel_Dossogne@f7111.surf.be again and so > > on. A classic mail loop which happens on many mailing lists from time to > > time. Yeppers! The only solution that I found to "skip" all those bounced messages is to go into netscapes Edit Mail Filters setup and create a filter to delete any message that contains "Bounced" in the subject line. Not a real good solution as it still takes up some bandwidth to download all that junk mail, but at least I don't have to manually delete them ;-0 -- cya l8r Leon McClatchey mailto:leonmcclatchey@homemail= .com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============7280754739844911928==-- From alfiesty@chaffee.net Thu May 7 10:14:28 1998 From: alfiesty@chaffee.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Mail Loop Date: Thu, 07 May 1998 04:14:28 -0600 Message-ID: <3.0.1.32.19980507041428.007ea690@chaffee.net> In-Reply-To: <35513650.C9447305@homemail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1802840536302642029==" --===============1802840536302642029== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit At 11:19 PM 5/6/98 -0500, you wrote: >Yeppers! The only solution that I found to "skip" all those bounced messages >is to go into netscapes Edit Mail Filters setup and create a filter to delete >any message that contains "Bounced" in the subject line. Not a real good >solution as it still takes up some bandwidth to download all that junk mail, >but at least I don't have to manually delete them ;-0 Easy solution which avoids long downkoad times is to telnet to your ISP, use elm on thier site to delete the bounces, then dl the rest. Jim -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============1802840536302642029==-- From mantel@suse.de Thu May 7 10:45:31 1998 From: mantel@suse.de To: users@lists.opensuse.org Subject: [S.u.S.E. Linux] Re:Glokkenspeil Date: Thu, 07 May 1998 12:45:31 +0200 Message-ID: In-Reply-To: <355125EB.68D84332@wenet.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7823162690682043797==" --===============7823162690682043797== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, On Wed, 6 May 1998, vic wrote: > just spam the serversending...wouldin't that wake them up????i dunno > it's their fault(i dunno all the technical params)sorry > it just seems that the server should be alerted of a bounce The complaints to postmaster@surf.be did bounce, too. > yours truly, > > #FrAcTeL23# Hubert -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============7823162690682043797==-- From brauki@cww.de Thu May 7 13:35:11 1998 From: brauki@cww.de To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Mail Loop Date: Thu, 07 May 1998 15:35:11 +0200 Message-ID: <3551B88F.7A9218C@cww.de> In-Reply-To: <3.0.1.32.19980507041428.007ea690@chaffee.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0066309550057500927==" --===============0066309550057500927== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Jim Hodgers wrote: >=20 > At 11:19 PM 5/6/98 -0500, you wrote: > >Yeppers! The only solution that I found to "skip" all those bounced messa= ges > >is to go into netscapes Edit Mail Filters setup and create a filter to del= ete > >any message that contains "Bounced" in the subject line. Not a real good > >solution as it still takes up some bandwidth to download all that junk mai= l, > >but at least I don't have to manually delete them ;-0 >=20 > Easy solution which avoids long downkoad times is to telnet to your ISP, use > elm on thier site to delete the bounces, then dl the rest. As long as telnet is possible, or worst of all, the mail server is not "limping" with NT.... >=20 > Jim >=20 Juergen --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D __ _ J=C3=BCrgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ = Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /____/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0066309550057500927==-- From martin_moeller@ibm.net Thu May 7 21:52:13 1998 From: martin_moeller@ibm.net To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Re: Mail Loop Date: Thu, 07 May 1998 23:52:13 +0200 Message-ID: <35522D0D.EEE534C8@ibm.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0020104369371213047==" --===============0020104369371213047== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hubert Mantel skrev: > > Would refusing non-subscriber submissions curb this at all? > > Yes, but this would cause other problems: Several people are posting from > another account than they subscribed, so this would become impossible. > A suggestion: Couldn't you redirect mails from postmaster@whatever and maybe similar addresses like webmaster@whatever, since I am sure it is very rare that mail from these addresses have relevance to this list? Certainly postmaster@surf.be could be put on a side-track, right? I am not really into procmail but I've heard a lot about it's incredible flexibility so I doubt it would pose a problem there, except if there is a legitimate concern about derailing messages from such addresses? How about throwing them in an 'Error' folder and skim them (titlewise anyway) before deleting or forwaring them? Ok, now you can all tell me what a stupid idea this is and why ;) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============0020104369371213047==-- From leonmcclatchey@homemail.com Fri May 8 02:08:08 1998 From: leonmcclatchey@homemail.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Mail Loop Date: Thu, 07 May 1998 21:08:08 -0500 Message-ID: <35526908.D49027E3@homemail.com> In-Reply-To: <3.0.1.32.19980507041428.007ea690@chaffee.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6187510253564083318==" --===============6187510253564083318== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Jim Hodgers wrote: > Easy solution which avoids long downkoad times is to telnet to your ISP, use > elm on thier site to delete the bounces, then dl the rest. > Thanx! I'll have to try that, it out to work if they have a telenet link? I= do know that for some reason I can only pick up 30 messages at a time, and judgi= ng from that last mail loop, that can be detected within the first batch:-) -- cya l8r Leon McClatchey mailto:leonmcclatchey@homemail= .com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e --===============6187510253564083318==--