PGP on Usenet (was Re: Can't Keep Kernel Log Messages From Console)

2003-08-14 Thread Mark L. Kahnt
On Tue, 2003-07-29 at 03:05, Alan Connor wrote:
  From [EMAIL PROTECTED] Mon Jul 28 23:47:50 2003
  
  
  Alan Connor wrote:
  From [EMAIL PROTECTED] Mon Jul 28 20:12:58 2003
   
  
  The stupid idiot must have have jumped to the insane conclusion that you 
  were reading this with mutt from the irrelevant facts that you were 
  complaining that you couldn't read it and that you said you were using mutt.
  
  Imagine!  believing what you told him instead of looking for the enough 
  clues in my posts to deduce you were talking crap!
  
  I think I'll killfile him too, in case he starts believing what I say.
  
  
  
 
 I didn't say anything about killfiling Colin. Are you troll?
 
 
 
 I DO use mutt to post with, and slrn to read the posts off usenet.
 
 Obviously, neither can do anything with what ended up on usenet
 
 
 I believe that I am being blamed for someone else's ignorance or selfishness.
 
 THEY were unaware or disdainful of the fact that a LOT of people read ldu from
 the usenet. There was a thread on the subject earlier, the latter part of which
 made it onto the mailing list. I participated in that thread. In fact, it was
 initiated by a fellow kind enough to point out that my posts to the newsfeed
 were not making it onto the mailing list, which I did not realize.
 
 
 PGP, attachments, and HTML have no place on the usenet, and people whose posts
 ultimately end up there, or those responsible for the delivery, need to observe
 proper netiquette. At least that's my take on the subject, and that of many
 others.
 
 I DO wonder what the mailing list posting rules are, and will look into it.
 
 
 Meanwhile, welcome to my killfile, ya jerk.
 
 
 Alan
 
  
 
 -- 
For Linux/Bash users: Eliminate spam from your life
with the Mailbox-Sentry-Program. See the thread
MSP on comp.mail.misc for the latest version.
  

I know, I'm late on this one (for all those who wish this thread would
end,) but PGP is considered very appropriate on Usenet - wander into any
of the news.* hierarchy (one of the Big-Eight hierarchies) and you will
find all manner of posts, particularly on posted reports, PGP or GPG
signed to indicate that they are authoritatively from who they claim to
be. This is particularly the case in the news.admin groups, where
spoofing of emails has been a problem in the past.

PGP/GPG is something I value on posts here as it reflects that I am not
getting someone from Microsoft or SCO pretending to be someone regular
and trusted on this list, offering *unhelpful* advice in their stead.
-- 
Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP
ML Kahnt New Markets Consulting
Tel: (613) 531-8684 / (613) 539-0935
Email: [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part


Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Ron Johnson
On Tue, 2003-07-29 at 00:41, Andrew McGuinness wrote:
 Alan Connor wrote:
 From [EMAIL PROTECTED] Mon Jul 28 20:12:58 2003
 
 
 On Mon, Jul 28, 2003 at 03:13:08PM -0700, Alan Connor wrote:
 
 From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003
 
 
 This is a multi-part message in MIME format.
 --8222A093BEB3CE9D0AF16851
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 --8222A093BEB3CE9D0AF16851
 Content-Type: text/plain; charset=us-ascii;
  name=syslog.conf
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename=syslog.conf
 
 
 
 --8222A093BEB3CE9D0AF16851--
 
 Would someone PLEASE tell me what all that CRAP is, and how to get rid
 of it?
 
 How have you managed to break mutt to the point where it doesn't
 understand attachments? I'm awed; mutt is an excellent MIME client.
 Maybe chapter 5 of the mutt manual would be helpful?
 
 -- 
 Colin Watson  [EMAIL PROTECTED]
 
 
  
  
  
  And pray tell just what are attachments  doing on Usenet?
  
  The answer is that they aren't, are they? 
  
  
  So the question should be: Since when does *slrn*  deal with attachments?
  Which doesn't make a lot of sense.
  
  Kindly direct your sarcasm where it belongs.
  
 
 The stupid idiot must have have jumped to the insane conclusion that you 
 were reading this with mutt from the irrelevant facts that you were 
 complaining that you couldn't read it and that you said you were using mutt.
 
 Imagine!  believing what you told him instead of looking for the enough 
 clues in my posts to deduce you were talking crap!

Besides, from his original message:
User-Agent: Mutt/1.3.24i

-- 
+-+
| Ron Johnson, Jr.Home: [EMAIL PROTECTED] |
| Jefferson, LA  USA  |
| |
| I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!|
|unknown  |
+-+



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Joey Hess
Alan Connor wrote:
 And pray tell just what are attachments  doing on Usenet?

If you shoose to read this list via usenet or other gateways, the burden
is on you to do any conceptual shifts necessary. This includes not
flaming people for complying with standard email etiquette even when it
conflicts with usenet etiquette. It also includes getting your
References header right, which I notice your post did not do.

 So the question should be: Since when does *slrn*  deal with attachments?

slrn has supported MIME since well before 1995. While it doesn't bother
with attachments, it can use metamail to view MIME messages.

 Not-to-mention that sending attachments is verboten on every mailing list that
 I have ever subscribed to, as are HTML mails.

Small attachments for gpg signatures and bits of log files or patches or
transcripts are completly acceptable on this mailing list.

 Henceforth I will simply killfile anyone on the list who does either.
 
 Fortunately, the vast majority have better manners/sense than that.

You should expect to be killfiling a lot of Debian developers then.

-- 
see shy jo, slrn maintainer for Debian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Michael Waters
On Mon, Jul 28, 2003, Brian White wrote:
 I've been trying to stop kernel log messages (generally from iptables)
 from going to the console, and thus making the console unusable for login.
 I've tried different things, but they just keep popping up.
 
 I have iptables lines like:
 
   iptables -A WATCH -m limit -j LOG --log-level warn --log-prefix ACCEPT-
 
 and those message always appear on the console -- nothing else; just these
 messages.  I've attached the syslog.conf file for more information.  Any
 help is appreciated!  Thanks!

One way is to add `kernel.printk = 1 4 1 7` to /etc/sysctl.conf.

Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Alan Connor
 From [EMAIL PROTECTED] Mon Jul 28 23:47:50 2003
 
 
 Alan Connor wrote:
 From [EMAIL PROTECTED] Mon Jul 28 20:12:58 2003
  
 
 The stupid idiot must have have jumped to the insane conclusion that you 
 were reading this with mutt from the irrelevant facts that you were 
 complaining that you couldn't read it and that you said you were using mutt.
 
 Imagine!  believing what you told him instead of looking for the enough 
 clues in my posts to deduce you were talking crap!
 
 I think I'll killfile him too, in case he starts believing what I say.
 
 
 

I didn't say anything about killfiling Colin. Are you troll?



I DO use mutt to post with, and slrn to read the posts off usenet.

Obviously, neither can do anything with what ended up on usenet


I believe that I am being blamed for someone else's ignorance or selfishness.

THEY were unaware or disdainful of the fact that a LOT of people read ldu from
the usenet. There was a thread on the subject earlier, the latter part of which
made it onto the mailing list. I participated in that thread. In fact, it was
initiated by a fellow kind enough to point out that my posts to the newsfeed
were not making it onto the mailing list, which I did not realize.


PGP, attachments, and HTML have no place on the usenet, and people whose posts
ultimately end up there, or those responsible for the delivery, need to observe
proper netiquette. At least that's my take on the subject, and that of many
others.

I DO wonder what the mailing list posting rules are, and will look into it.


Meanwhile, welcome to my killfile, ya jerk.


Alan

 

-- 
   For Linux/Bash users: Eliminate spam from your life
   with the Mailbox-Sentry-Program. See the thread
   MSP on comp.mail.misc for the latest version.
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Colin Watson
On Mon, Jul 28, 2003 at 08:31:39PM -0700, Alan Connor wrote:
 Colin Watson wrote:
  How have you managed to break mutt to the point where it doesn't
  understand attachments? I'm awed; mutt is an excellent MIME client.
  Maybe chapter 5 of the mutt manual would be helpful?
 
 And pray tell just what are attachments  doing on Usenet?

Since when was this Usenet? (Hint: Usenet == big-8 newsgroup
hierarchies, netnews == newsgroups in general. Usenet most certainly
isn't whatever random gateway you're reading this through.)

 So the question should be: Since when does *slrn*  deal with attachments?
 Which doesn't make a lot of sense.

If you're doing something weird then you should expect to have to cope
with weirdness yourself; please start by not breaking every thread you
respond to.

 It seems to me that others should do the same.
 
 
 Not-to-mention that sending attachments is verboten on every mailing list that
 I have ever subscribed to, as are HTML mails.
 
 
 Henceforth I will simply killfile anyone on the list who does either.

Bye-bye. Attachments are not remotely in the same league as HTML mails.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Colin Watson
On Tue, Jul 29, 2003 at 12:05:40AM -0700, Alan Connor wrote:
 PGP, attachments, and HTML have no place on the usenet, and people
 whose posts ultimately end up there, or those responsible for the
 delivery, need to observe proper netiquette. At least that's my take
 on the subject, and that of many others.

Nope. There's absolutely no reason why users of lists.debian.org need
care about the existence of news gateways; it's not their fault that
they exist. Users of news gateways should take the responsibility of
knowing that they're looking through a window into a different world
with different rules.

(PGP-signed to see if Alan will killfile me.)

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


pgp0.pgp
Description: PGP signature


Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Colin Watson
On Mon, Jul 28, 2003 at 08:31:39PM -0700, Alan Connor wrote:
 Colin Watson wrote:
  How have you managed to break mutt to the point where it doesn't
  understand attachments? I'm awed; mutt is an excellent MIME client.
  Maybe chapter 5 of the mutt manual would be helpful?
 
 And pray tell just what are attachments  doing on Usenet?
 
 The answer is that they aren't, are they? 
 
 
 So the question should be: Since when does *slrn*  deal with attachments?
 Which doesn't make a lot of sense.
 
 Kindly direct your sarcasm where it belongs.
 
 
 There are enough clues in my posts indicating that I read the newsfeed rather 
 than subscribe to the list directly.

Oh yeah, I genuinely thought that you were using mutt to read posts
(particularly since, oh let me see, *you said you were using mutt*), and
had somehow managed to configure it such that it didn't decode MIME, and
I genuinely tried to help by pointing you at the relevant section of the
manual (even though I couldn't find any option there which would disable
MIME when I looked, but hey, someone else might be able to). There was
no sarcasm in my post, only amazement and curiosity since I'd never
heard of such a mutt configuration before.

I can't be expected to remember the personal mail reading arrangements
of every last person on this mailing list, particularly when it's so
hard to follow threads you're involved in without going back and fixing
up their threading by hand, which I don't always bother with.

If your response to a genuine effort to help is a flame, then I strongly
suggest that you inspect your own manners before impugning those of
others.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Paul Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jul 28, 2003 at 08:31:39PM -0700, Alan Connor wrote:
 And pray tell just what are attachments  doing on Usenet?
 
 The answer is that they aren't, are they? 

This is a mailing list:  [EMAIL PROTECTED]  If you're able
to read and post to this mailing list from some USENET source, good
for you, you're special, deal with it.  8:o)

Most newsreaders can also deal with MIME, just because slrn is behind
the times doesn't mean progress gets to stop and wait up at this
point.  Heck, MIME encoded PGP is the preferred method for signing
anymore...

- -- 
 .''`. Paul Johnson [EMAIL PROTECTED]
: :'  :proud Debian admin and user
`. `'`
  `-  Debian - when you have better things to do than fix a system
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/JmJkJ5vLSqVpK2kRAuE3AJ4j1PQ4Zq7sgOAXPBdU1qzEHMr8lwCaAwul
D2NOjHWrfptSZzOqSoHf+28=
=/iII
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Brian White
  I've been trying to stop kernel log messages (generally from iptables)
  from going to the console, and thus making the console unusable for login.
  I've tried different things, but they just keep popping up.
 
  I have iptables lines like:
 
iptables -A WATCH -m limit -j LOG --log-level warn --log-prefix ACCEPT-
 
  and those message always appear on the console -- nothing else; just these
  messages.  I've attached the syslog.conf file for more information.  Any
  help is appreciated!  Thanks!
 
 One way is to add `kernel.printk = 1 4 1 7` to /etc/sysctl.conf.

This sounds like the best way, but I can't find any documentation on what
the four numbers mean.  Do you have a reference?

Other things suggested (but not posted to the list were):

 - add -c 4 to KLOGD in /etc/init.d/klogd
 - echo 4 /proc/sys/kernel/printk

  Brian
 ( [EMAIL PROTECTED] )

---
  Relationships go through seasons.  Winter often comes before Spring.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-29 Thread Michael Waters
On Tue, Jul 29, 2003, Brian White wrote:
   I've been trying to stop kernel log messages (generally from iptables)
   from going to the console, and thus making the console unusable for login.
   I've tried different things, but they just keep popping up.
  
   I have iptables lines like:
  
 iptables -A WATCH -m limit -j LOG --log-level warn --log-prefix ACCEPT-
  
   and those message always appear on the console -- nothing else; just these
   messages.  I've attached the syslog.conf file for more information.  Any
   help is appreciated!  Thanks!
  
  One way is to add `kernel.printk = 1 4 1 7` to /etc/sysctl.conf.
 
 This sounds like the best way, but I can't find any documentation on what
 the four numbers mean.  Do you have a reference?

It's in the kernel source in
/usr/src/linux/Documentation/sysctl/kernel.txt  or 
/usr/src/linux/Documentation/proc.txt in older kernels.

 
 Other things suggested (but not posted to the list were):
 
  - add -c 4 to KLOGD in /etc/init.d/klogd
  - echo 4 /proc/sys/kernel/printk


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Brian White
I've been trying to stop kernel log messages (generally from iptables)
from going to the console, and thus making the console unusable for login.
I've tried different things, but they just keep popping up.

I have iptables lines like:

  iptables -A WATCH -m limit -j LOG --log-level warn --log-prefix ACCEPT-

and those message always appear on the console -- nothing else; just these
messages.  I've attached the syslog.conf file for more information.  Any
help is appreciated!  Thanks!

  Brian
 ( [EMAIL PROTECTED] )

P.S.  Please CC me when replying; I'm not on the debian-users list right now.

---
  Relationships go through seasons.  Winter often comes before Spring.#  /etc/syslog.conf Configuration file for syslogd.
#
#   For more information see syslog.conf(5)
#   manpage.

#
# First some standard logfiles.  Log by facility.
#

*.*;auth,authpriv,kern.none -/var/log/syslog
auth,authpriv.* /var/log/auth.log
cron,daemon.*   -/var/log/daemon.log
kern.*  /var/log/kern.log
lpr.*   -/var/log/lpr.log
user.*  -/var/log/user.log
uucp.*  -/var/log/uucp.log

#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
mail.*  -/var/log/mail.log
#mail.info  -/var/log/mail.info
#mail.warn  -/var/log/mail.warn
#mail.err   /var/log/mail.err

#
# Logging for INN news system
#
news.*  -/var/log/news.log
#news.crit  /var/log/news/news.crit
#news.err   /var/log/news/news.err
#news.notice-/var/log/news/news.notice

#
# Logging for extra (local) services
#
local2.*-/var/log/ppp.log

#
# Some `catch-all' logfiles.
#
*.=debug;\
auth,authpriv.none;\
news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv,kern.none;\
cron,daemon.none;\
local2.none;\
local5.none;\
local7.none;\
mail,news.none  -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg *

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#

daemon;mail.*;\
news.=crit;news.=err;news.=notice;\
*.=debug;*.=info;\
*.=notice;*.=warn   /dev/tty12


# The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
# you must invoke `xconsole' with the `-file' option:
# 
#$ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
#  busy site..
#



Re: Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Andreas Janssen
Hello

Brian White wrote:

 I've been trying to stop kernel log messages (generally from iptables)
 from going to the console, and thus making the console unusable for
 login. I've tried different things, but they just keep popping up.

I think you can disable kernel logs on consoles completely by passing
the quiet parameter to the kernel on startup or adding it to the
append-line of your bootloader.

best regards
Andreas Janssen

-- 
Andreas Janssen
[EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674
Registered Linux User #267976


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Alan Connor
 From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003
 
 
 This is a multi-part message in MIME format.
 --8222A093BEB3CE9D0AF16851
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 --8222A093BEB3CE9D0AF16851
 Content-Type: text/plain; charset=us-ascii;
  name=syslog.conf
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline;
  filename=syslog.conf
 
 
 
 --8222A093BEB3CE9D0AF16851--
 
 
 



Would someone PLEASE tell me what all that CRAP is, and how to get rid
of it?

I can't even figure out what the guy is trying to say


Using mutt.


Thanks,


Alan


-- 
   For Linux/Bash users: Eliminate spam from your life
   with the Mailbox-Sentry-Program. See the thread
   MSP on comp.mail.misc for the latest version.
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Ron Johnson
On Mon, 2003-07-28 at 17:13, Alan Connor wrote:
  From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003
  
  
  This is a multi-part message in MIME format.


This is the hint...

  --8222A093BEB3CE9D0AF16851
  Content-Type: text/plain; charset=us-ascii
  Content-Transfer-Encoding: 7bit
  --8222A093BEB3CE9D0AF16851
  Content-Type: text/plain; charset=us-ascii;
   name=syslog.conf
  Content-Transfer-Encoding: 7bit
  Content-Disposition: inline;
   filename=syslog.conf
  
  
  
  --8222A093BEB3CE9D0AF16851--
  
  
  
 
 
 
 Would someone PLEASE tell me what all that CRAP is, and how to get rid
 of it?
 
 I can't even figure out what the guy is trying to say

You don't want to get rid of it.  It's integral to his email.

He sent a text email and attached his syslog.conf

It's offensive when html mails or binary file attachments are sent.

-- 
+-+
| Ron Johnson, Jr.Home: [EMAIL PROTECTED] |
| Jefferson, LA  USA  |
| |
| I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!|
|unknown  |
+-+



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Colin Watson
On Mon, Jul 28, 2003 at 03:13:08PM -0700, Alan Connor wrote:
  From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003
  
  
  This is a multi-part message in MIME format.
  --8222A093BEB3CE9D0AF16851
  Content-Type: text/plain; charset=us-ascii
  Content-Transfer-Encoding: 7bit
  --8222A093BEB3CE9D0AF16851
  Content-Type: text/plain; charset=us-ascii;
   name=syslog.conf
  Content-Transfer-Encoding: 7bit
  Content-Disposition: inline;
   filename=syslog.conf
  
  
  
  --8222A093BEB3CE9D0AF16851--
 
 Would someone PLEASE tell me what all that CRAP is, and how to get rid
 of it?

How have you managed to break mutt to the point where it doesn't
understand attachments? I'm awed; mutt is an excellent MIME client.
Maybe chapter 5 of the mutt manual would be helpful?

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Alan Connor
 From [EMAIL PROTECTED] Mon Jul 28 20:12:58 2003
 
 
 On Mon, Jul 28, 2003 at 03:13:08PM -0700, Alan Connor wrote:
   From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003
   
   
   This is a multi-part message in MIME format.
   --8222A093BEB3CE9D0AF16851
   Content-Type: text/plain; charset=us-ascii
   Content-Transfer-Encoding: 7bit
   --8222A093BEB3CE9D0AF16851
   Content-Type: text/plain; charset=us-ascii;
name=syslog.conf
   Content-Transfer-Encoding: 7bit
   Content-Disposition: inline;
filename=syslog.conf
   
   
   
   --8222A093BEB3CE9D0AF16851--
  
  Would someone PLEASE tell me what all that CRAP is, and how to get rid
  of it?
 
 How have you managed to break mutt to the point where it doesn't
 understand attachments? I'm awed; mutt is an excellent MIME client.
 Maybe chapter 5 of the mutt manual would be helpful?
 
 -- 
 Colin Watson  [EMAIL PROTECTED]
 
 


And pray tell just what are attachments  doing on Usenet?

The answer is that they aren't, are they? 


So the question should be: Since when does *slrn*  deal with attachments?
Which doesn't make a lot of sense.

Kindly direct your sarcasm where it belongs.


There are enough clues in my posts indicating that I read the newsfeed rather 
than subscribe to the list directly.

*I* am cognizant of the fact that my posts are going to a mailing list as
well as Usenet, and take this into account.


It seems to me that others should do the same.


Not-to-mention that sending attachments is verboten on every mailing list that
I have ever subscribed to, as are HTML mails.


Henceforth I will simply killfile anyone on the list who does either.

Fortunately, the vast majority have better manners/sense than that.




Alan

 

-- 
   For Linux/Bash users: Eliminate spam from your life
   with the Mailbox-Sentry-Program. See the thread
   MSP on comp.mail.misc for the latest version.
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Can't Keep Kernel Log Messages From Console

2003-07-28 Thread Andrew McGuinness
Alan Connor wrote:
From [EMAIL PROTECTED] Mon Jul 28 20:12:58 2003

On Mon, Jul 28, 2003 at 03:13:08PM -0700, Alan Connor wrote:

From [EMAIL PROTECTED] Mon Jul 28 15:09:43 2003

This is a multi-part message in MIME format.
--8222A093BEB3CE9D0AF16851
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
--8222A093BEB3CE9D0AF16851
Content-Type: text/plain; charset=us-ascii;
name=syslog.conf
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=syslog.conf


--8222A093BEB3CE9D0AF16851--
Would someone PLEASE tell me what all that CRAP is, and how to get rid
of it?
How have you managed to break mutt to the point where it doesn't
understand attachments? I'm awed; mutt is an excellent MIME client.
Maybe chapter 5 of the mutt manual would be helpful?
--
Colin Watson  [EMAIL PROTECTED]



And pray tell just what are attachments  doing on Usenet?

The answer is that they aren't, are they? 

So the question should be: Since when does *slrn*  deal with attachments?
Which doesn't make a lot of sense.
Kindly direct your sarcasm where it belongs.

The stupid idiot must have have jumped to the insane conclusion that you 
were reading this with mutt from the irrelevant facts that you were 
complaining that you couldn't read it and that you said you were using mutt.

Imagine!  believing what you told him instead of looking for the enough 
clues in my posts to deduce you were talking crap!

I think I'll killfile him too, in case he starts believing what I say.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]