Re: [suse-security] list moderation, message mangling (was: TIS FWTK)
Hey guys, stop this silly discussion. :0 fhw * ^From suse-security-return- * ^X-Mailinglist: suse-security$ | sed -e '/^[Ss][Uu][Bb][Jj][Ee][Cc][Tt]:/ !bend' \ -e 's/\[suse-security\]//' \ -e :end Problem fixed. (untested) Volker PS No doubt someone could improve on the sed bit.
also sprach Volker Kuhlmann (on Mon, 11 Dec 2000 05:11:15PM +1300):
| sed -e '/^[Ss][Uu][Bb][Jj][Ee][Cc][Tt]:/ !bend' \ PS No doubt someone could improve on the sed bit.
well, try sed -e '/^subject/ !bend/i' here. but in either case, please explain why you are replacing subject with !bend? or is this some form of syntax that i am not parsing correctly? martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- "i wish there was a knob on the tv to turn up the intelligence. there's a knob called 'brightness', but it doesn't seem to work." -- gallagher
On Mon, Dec 11, 2000 at 17:11 +1300, Volker Kuhlmann wrote:
Hey guys, stop this silly discussion.
[ ... ] | sed -e '/^[Ss][Uu][Bb][Jj][Ee][Cc][Tt]:/ !bend' \ [ ... ]
Problem fixed. (untested)
Not fixed, circumvented only. This is very much like saying "Let's produce HTML by default and have everyone else use 'lynx -dump' to read it in text form. Counter productive. Why should one damage things to repair them afterwards for no good reason? I already have problems with "fixing" all the broken signature and quotes indentation stuff. Since people are sooo creative when it comes to "being different, since functional is boring" there sometimes are false positives. That's when "fixing" things makes them worse. Just because someone knows better "for pure coolness". It would have been better to not produce any need for fixing! virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
i am personally a big fan of subject prefixes, especially when i tell procmail to route several mailing lists into one folder. so whenever there is a list that does not have one, i add it with sed: :0 fh * ^Sender.*owner-accu-general@accu\.org * ! ^Subject.*\[accu-general\] | sed -e "s/accu-general:/[accu-general]/gi" now, this is like converting all arriving mail to html when reading and it solves the problem quite nicely for me. so suse-security couldd remove the prefix and ask each who likes it to put it in themselves. this would definitely be more preferable than removing it. it also saves 15 bytes of bandwidth :) martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- ever wondered whether schroedinger is dead? have you seen him?
also sprach MaD dUCK (on Mon, 11 Dec 2000 10:26:39PM -0500):
:0 fh * ^Sender.*owner-accu-general@accu\.org * ! ^Subject.*\[accu-general\] | sed -e "s/accu-general:/[accu-general]/gi"
and of all such filters in my .procmailrc, i chose the one that doesn't do what i was talking about. this one replaces one style of prefix with the one i prefer. what i was saying could be accomplished by replacing the last line with:
| sed -e "s/\(^Subject:\)/\1 [accu-general]/i"
also, the trailing gi is a gnu extension as volker kindly pointed out. the g really isn't needed for we theoretically only replace "Subject:" once per line per file. the i makes the match case-insensitive. martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- may the bluebird of happiness twiddle your bits.
Hello, I have just installed SuSE 7 about a month ago and have not had any messages recorded to /var/log/messages since Nov 21. Is this a sign of a healthy system or could there be a problem? Thanks in advance, Mike
EEEKKKKKK You should at LEAST have something like this: Dec 12 10:34:55 dante -- MARK -- Dec 12 10:39:11 dante sshd[5547]: Accepted password for petern from 10.1.0.178 port 1036 Dec 12 10:40:03 dante su: (to root) nix on /dev/pts/0 Dec 12 10:40:03 dante PAM-unix2[5559]: session started for user root, service su Dec 12 10:44:55 dante -- MARK -- try looking at your processes.... should look like this # ps afx |grep syslogd 80 ? S 0:00 /usr/sbin/syslogd -r -m 5 6117 pts/0 S 0:00 \_ grep syslogd dante:~ # Either syslogd is not running, or you have been backdoored... Nix At 01:04 AM 12/12/2000 -0500, you wrote:
Hello,
I have just installed SuSE 7 about a month ago and have not had any messages recorded to /var/log/messages since Nov 21. Is this a sign of a healthy system or could there be a problem?
Thanks in advance, Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
On Mon, Dec 11, 2000 at 22:26 -0500, MaD dUCK wrote:
i am personally a big fan of subject prefixes, especially when i tell procmail to route several mailing lists into one folder. so whenever there is a list that does not have one, i add it with sed:
[ ... ]
That's exactly what I said. :) You're perfectly free to do whatever you want to with the messages you receive and record somewhere. It's *your* data when you're the terminal station. It's just that I don't allow a list admin (read: a transporter) to fiddle with the user supplied data (subject fields, reply-to fields, from fields, etc). And I get especially upset about this mangling when it causes some kind of information loss or causes me and other recipients extra work although there's no (real or sane) reason to cause this trouble. Regarding the "marking the list articles with a prefix in the subject" -- there are already nine(!) other pointers in the message header (plus the two in the footer) to recognize that the message belongs to the list. If that's not redundancy, what else is? virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
On Tue, 12 Dec 2000 18:09:58 +0100 Gerhard Sittig
On Mon, Dec 11, 2000 at 22:26 -0500, MaD dUCK wrote:
i am personally a big fan of subject prefixes, especially when i tell procmail to route several mailing lists into one folder. so whenever there is a list that does not have one, i add it with sed:
[ ... ]
That's exactly what I said. :) You're perfectly free to do whatever you want to with the messages you receive and record somewhere. It's *your* data when you're the terminal station.
It's just that I don't allow a list admin (read: a transporter) to fiddle with the user supplied data (subject fields, reply-to fields, from fields, etc). And I get especially upset about this mangling when it causes some kind of information loss or causes me and other recipients extra work although there's no (real or sane) reason to cause this trouble.
Regarding the "marking the list articles with a prefix in the subject" -- there are already nine(!) other pointers in the
None of which the brain-dead email client that I have to use at the office will filter on. I'm lucky to get it to work on "Subject:" I can use Subject, from, to, cc, reply-to, in-reply-to, recipient, and all. It doen't allow for "and" or "or". Just one of the above exclusively. But then again if everyone would put the list in the "To" field instead of cc'ing the list it might make life a little easier. End of diatribe!! Maybe they'll let me use linux at work one of these days.
message header (plus the two in the footer) to recognize that the message belongs to the list. If that's not redundancy, what else is?
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
----------------------------------------- Mearl Danner Data Communications/Network Specialist Email: jmdanner@samford.edu Samford University
On Tue, Dec 12, 2000 at 14:32 -0600, Mearl Danner wrote:
On Tue, 12 Dec 2000 18:09:58 +0100 Gerhard Sittig
wrote: Regarding the "marking the list articles with a prefix in the subject" -- there are already nine(!) other pointers in the message header (plus the two in the footer) to recognize that the message belongs to the list. If that's not redundancy, what else is?
None of which the brain-dead email client that I have to use at the office will filter on. I'm lucky to get it to work on "Subject:"
I can use Subject, from, to, cc, reply-to, in-reply-to, recipient, and all. It doen't allow for "and" or "or". Just one of the above exclusively. But then again if everyone would put the list in the "To" field instead of cc'ing the list it might make life a little easier.
How about '"all" contains "X-Mailinglist: suse-security"' then? This is exactly the "trick" in how to filter with Netscape mail frontends discussed a few dozen times in several suse lists in the past few years. And of course you're free to use any of the other ten occurencies of "suse-security". But the "X-Mailinglist:" is the one which got in for this very reason. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
I'll try that, but IIRC all includes the body, which didn't work on some
messages very well. It'll probably work all right on suse-security though.
On Wed, 13 Dec 2000 18:39:34 +0100 Gerhard Sittig
On Tue, Dec 12, 2000 at 14:32 -0600, Mearl Danner wrote:
On Tue, 12 Dec 2000 18:09:58 +0100 Gerhard Sittig
wrote: Regarding the "marking the list articles with a prefix in the subject" -- there are already nine(!) other pointers in the message header (plus the two in the footer) to recognize that the message belongs to the list. If that's not redundancy, what else is?
None of which the brain-dead email client that I have to use at the office will filter on. I'm lucky to get it to work on "Subject:"
I can use Subject, from, to, cc, reply-to, in-reply-to, recipient, and all. It doen't allow for "and" or "or". Just one of the above exclusively. But then again if everyone would put the list in the "To" field instead of cc'ing the list it might make life a little easier.
How about '"all" contains "X-Mailinglist: suse-security"' then? This is exactly the "trick" in how to filter with Netscape mail frontends discussed a few dozen times in several suse lists in the past few years.
And of course you're free to use any of the other ten occurencies of "suse-security". But the "X-Mailinglist:" is the one which got in for this very reason.
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
----------------------------------------- Mearl Danner Data Communications/Network Specialist Email: jmdanner@samford.edu Samford University
[ ... reformatted for TOFU avoidance and readability, sigh ... ] On Wed, Dec 13, 2000 at 14:38 -0600, Mearl Danner wrote:
On Wed, 13 Dec 2000 18:39:34 +0100 Gerhard Sittig
wrote: How about '"all" contains "X-Mailinglist: suse-security"' then? This is exactly the "trick" in how to filter with Netscape mail frontends discussed a few dozen times in several suse lists in the past few years.
I'll try that, but IIRC all includes the body, which didn't work on some messages very well. It'll probably work all right on suse-security though.
Usually "all" includes the body as well as(!) the header. It's mainly found in those frontends which feel the user doesn't know any more about email than "from", "to", "subject", and "the message text". But it can be (ab)used to differ between "from", "to", "subject" and "other header lines the author was afraid of shocking the user when naming them since this would be too much info at once". There usually is no problem with searching for special header lines by means of "all", as long as you can avoid false positives. Just make the matching patterns as lengthy and as concrete as you can. The above example should do very well. The ability to specify "start of line" and "end of line" would be handy, too, and would suddenly eradicate _all_ false positives. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
None of which the brain-dead email client that I have to use at the office will filter on. I'm lucky to get it to work on "Subject:"
I can use Subject, from, to, cc, reply-to, in-reply-to, recipient, and all. It doen't allow for "and" or "or". Just one of the above exclusively. But then again if everyone would put the list in the "To" field instead of cc'ing the list it might make life a little easier.
End of diatribe!! Maybe they'll let me use linux at work one of these days.
I have no idea what "X-Mailer: Execmail for Win32 5.1 Build (9) " is. But as long as you are using standards compliant mail servers. (Even MS Exchange) You may want to have a look at Eudora Pro. It's what I use, and I have not yet found an equivalently powerful (yet nice) mail client under linux. It and MS Word are the two things that keep me in windows most of my working day... If anyone know about an equavelent to Eudora for Linux I would LOVE to hear about it. Kmail and the like just don't cut it... Yet. -Nix
On Thu, 14 Dec 2000, Nix wrote:
None of which the brain-dead email client that I have to use at the office will filter on. I'm lucky to get it to work on "Subject:"
I can use Subject, from, to, cc, reply-to, in-reply-to, recipient, and all. It doen't allow for "and" or "or". Just one of the above exclusively. But then again if everyone would put the list in the "To" field instead of cc'ing the list it might make life a little easier.
End of diatribe!! Maybe they'll let me use linux at work one of these days.
I have no idea what "X-Mailer: Execmail for Win32 5.1 Build (9) " is. But as long as you are using standards compliant mail servers. (Even MS Exchange) You may want to have a look at Eudora Pro. It's what I use, and I have not yet found an equivalently powerful (yet nice) mail client under linux. It and MS Word are the two things that keep me in windows most of my working day...
If anyone know about an equavelent to Eudora for Linux I would LOVE to hear about it.
Kmail and the like just don't cut it... Yet.
-Nix
If you are looking for sheer functionality and don't mind using the console, then the pine/procmail combo is the best that I have come across. Granted it is archaic, but it really is pretty powerful once you get past the lack of GUI. If you are looking for GUI, then I would say that Netscape Mail (when it doesn't catch on fire) or Kmail is about the best there is right now. Cliff
also sprach Cliff Friedel (on Wed, 13 Dec 2000 07:45:41PM -0500):
If you are looking for sheer functionality and don't mind using the console, then the pine/procmail combo is the best that I have come across. Granted it is archaic, but it really is pretty powerful once you get past the lack of GUI.
except pine's folder handling is pretty bad i find. and pine is (a) a security problem, and (b) very cpu/memory intensive. i am using procmail to deliver to Maildir folders which I use with mutt, and mutt's macros and configuration allow me to do whatever i want. and it's soooo much better than a GUI just because it's fast over SSH. i have yet to see a GUI mail client (even on windoze) which provides all the functionality mutt provides... martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- never underestimate the power of human stupidity.
also sprach Gerhard Sittig (on Tue, 12 Dec 2000 06:09:58PM +0100):
Regarding the "marking the list articles with a prefix in the subject" -- there are already nine(!) other pointers in the message header (plus the two in the footer) to recognize that the message belongs to the list. If that's not redundancy, what else is?
i use mutt, and none of these but the subject prefix shows up in the message index. of course, once i am reading a message the origin is obvious from trailer, headers, recipient address and the like, but in the mutt index, this isn't obvious and that's when subject prefixes are handy. martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- "and no one sings me lullabies, and no one makes me close my eyes, and so i throw the windows wide, and call to you across the sky" -- pink floyd, 1971
Hi, On Tue, Dec 12 2000 at 15:53 -0500, MaD dUCK wrote:
i use mutt, and none of these but the subject prefix shows up in the message index. of course, once i am reading a message the origin is obvious from trailer, headers, recipient address and the like, but in the mutt index, this isn't obvious and that's when subject prefixes are handy.
If you've set the subscribe and index_format options properly, e.g. subscribe suse-security set index_format="%4C %Z %{%b %d} %-15.15L (%4l) %s" mutt will display the list name instead of the from address in the message index. Ciao, Stefan
also sprach Stefan Troeger (on Tue, 12 Dec 2000 10:05:57PM +0100):
mutt will display the list name instead of the from address in the message index.
well, but i would rather see the author of the message. plus the subject prefix. i am mainly arguing that the subject prefix is a lot more useful than headers and trailers (at least in my case). i am not arguing for or against it being added by the MLM. martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- "the eternal feminine draws us upward." -- goethe
As much fun as this subject is (well, actually it's not) can we please kill this thread off? To have subject line prefixes we either need to teach users to do it (not gonna happen) or get the list moderated (ick) or automatically happening (double ick). It's not gonna happen folks. Kurt
On Tue, 12 Dec 2000, Kurt Seifried wrote:
It's not gonna happen folks.
It might be necessary to mention that this is Kurt's opinion.
Kurt
The subject index thread:
People who are subscribed to just a few mailing lists might very well get
used to this feature. Those who sort their incoming mail into seperate
designated folders are also capable of rewriting the message header upon
mail delivery.
The moderation thread:
There has been a discussion about moderation some weeks ago. I've been
asking people to give me some feedback, and I've received quite much of
it. There were many valid arguments against as well as for moderation, but
the decision was to not moderate the list for the time being. The decision
was mainly based on two arguments: latency and latency. We can't moderate
the list as long as this problem isn't solved yet. I'd like SuSE security
concentrate on solving the issues rather than throttling the information
flow on the public security mailing list.
FAQ:
Johannes Geiger (thanks) came up with the idea of having an FAQ
(frequently asked questions) about the suse-security mailing list. I'm
much in favour for this idea. Would someone vulunteer to write something
so that we can merge the ideas, credits included, of course? I could send
a clean, tidied-up draft to the list every once in a while, probably
clearing up some questions that seem to reoccur every few weeks.
So long,
Roman.
--
- -
| Roman Drahtmüller
*grin* I believe I mentioned that I was thinking of starting a faq a few weeks back also.. I would be happy to have a stab at it. -Nix
FAQ: Johannes Geiger (thanks) came up with the idea of having an FAQ (frequently asked questions) about the suse-security mailing list. I'm much in favour for this idea. Would someone vulunteer to write something so that we can merge the ideas, credits included, of course? I could send a clean, tidied-up draft to the list every once in a while, probably clearing up some questions that seem to reoccur every few weeks.
So long, Roman.
participants (10)
-
Cliff Friedel
-
Gerhard Sittig
-
Kurt Seifried
-
MaD dUCK
-
Mearl Danner
-
Michael Long
-
Nix
-
Roman Drahtmueller
-
Stefan Troeger
-
Volker Kuhlmann