[SuSE Linux] Mailinglist troubles
Hi all, first of all I want to apologize for the trouble the last days. Following Murphy's law, several things came together and made the mailinglist trouble the worst we ever had: - the list maintainer (Bodo) is on vacation - trouble started when the new maintainer was out at a customer for a whole day - Lenz (who also reads the list) is on vacation - I myself was at home because both my children became sick So we realized the problems way too late. I unsubscribed the problematic addresses from the list. Also, I removed this "reply-to" header from the configuration because many mail systems handle this as the return-path. Also, I changed the list post policy to allow postings only from subscribed users in order to avoid spam. I think the backlog of queued messages is almost empty so the problem now really should be solved. This kind of problems can not be avoided by 100%, but in this case it has been very annoying because nobody at SuSE was browsing the list for more than one whole day. Please note that this is not the usual situation and take my serious apologies. -o) Hubert Mantel Goodbye, dots... /\\ _\_v - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Thanks for fixing the list, Hubert. I will just point out in passing that we list users often compound the problem by using the list to ask/complain about the loop; every message gets sent to the problem address(es), which in turn send noise back to the list and so on. Perhaps as much as 250f the noise was the result of users acknowledging and/or inquiring/bitching about the loop. While I'm glad that the reply-to header is changed (I think this will go a long way to solving the whole problem), I can't get too irritated with the list maintainers; it's not easy being on-call 24/7, and my house certainly has enough glass in it to make stone-throwing risky. We users need to figure it out and not contribute to the problem. Opinions expressed are mine only, phil (donning his asbestos union suit) -- Don't have awk? Use this simple sh emulation: #!/bin/sh echo 'Awk bailing out!' exit 2 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
<DL> <DT><STRONG>Warning</STRONG></DT> <DD>Could not process message with given Content-Type: <CODE>multipart/signed; boundary=Nq2Wo0NMKNjxTN9z; micalg=pgp-md5;protocol="application/pgp-signature"</CODE> </DD> </DL>
On 12 Jan, phillip mannie wrote:
Thanks for fixing the list, Hubert. I will just point out in passing that we list users often compound the problem by using the list to ask/complain about the loop; every message gets sent to the problem address(es), which in turn send noise back to the list and so on. Perhaps as much as 250f the noise was the result of users acknowledging and/or inquiring/bitching about the loop.
While I'm glad that the reply-to header is changed (I think this will go a long way to solving the whole problem), I can't get too irritated with the list maintainers; it's not easy being on-call 24/7, and my house certainly has enough glass in it to make stone-throwing risky. We users need to figure it out and not contribute to the problem.
Opinions expressed are mine only, phil (donning his asbestos union suit)
I dont have a flame or problem with this explanation but list maintainers really are not on call 24x7 to fix list problems. Many list maintainers have other things like lives that they have to do too. When I managed lists, I noted that things went to sh*t as soon as I thought that they were doing well. Then things like bad email addresses would cause email to bounce here and there or whatever. It would often be an extremely quite period when I decided to go off and do some sordid private thing (like get completely toasted!!) and then find out that the list members were angrily awaiting my return. I think though that a list has to have an active maintainer that has as his or her interest peeking in on a daily basis, looking at the ebb and flow of email from a simple management perspective, seeing whether there are bounceroos out there, and then moving on to other pressing duties. No flame intended. I think SuSE management staff has to address some approach to having the list covered on a daily basis but not 24x7. Fixing the replyto and outside posting is quite important. But... Everyone has the right to go get drunk, eat some good food, or do other random acts of beauty. -- Michael E. Perry mperry@basin.com ------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (4)
-
jblosser＠firinn.org -
mantel＠suse.de -
mperry＠basin.com -
phil＠servcom.com