Re: [admin] NO HTML posts please!
On Thu, 30 Mar 2000, Stas Bekman wrote: Please don't tell me to get more _sophisticated_ email client, my pine does everything for me. HTML should NOT be used for posting emails. Not only that, the list of mail sizes on mod_perl went: 1k 3k 2k 4k 20k - HTML Yikes. (although pine 4 and above does display HTML ok, it's not a good idea. Turn it off...) -- Matt/ Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org http://xml.sergeant.org
Re: [admin] NO HTML posts please!
Stas Bekman wrote: Folks, please refrain from posting in HTML. Some of us use email clients that post and read email in the old good text mode. When I don't have enough time on my hands I delete such emails since I cannot read them right away. Probably others too. Please don't tell me to get more _sophisticated_ email client, my pine does everything for me. HTML should NOT be used for posting emails. And then there are those of us that do have sophisticated email clients that simply don't care for HTML posting. I agree 100%, keep it simple, keep it TEXT! Sam
Re: [admin] NO HTML posts please!
Stas Bekman [EMAIL PROTECTED] writes: I agree 100%. HTML belongs in web browsers. If you happen to have a web browser in your mail reader, fine, but don't force others to have one as well :) Chip Folks, please refrain from posting in HTML. Some of us use email clients that post and read email in the old good text mode. When I don't have enough time on my hands I delete such emails since I cannot read them right away. Probably others too. Please don't tell me to get more _sophisticated_ email client, my pine does everything for me. HTML should NOT be used for posting emails. -- Chip Turner [EMAIL PROTECTED] ZFx, Inc. www.zfx.com PGP key available at wwwkeys.us.pgp.net
Re: [admin] NO HTML posts please!
On Thu, 30 Mar 2000, Sam Carleton wrote: Stas Bekman wrote: Folks, please refrain from posting in HTML. Some of us use email clients that post and read email in the old good text mode. When I don't have enough time on my hands I delete such emails since I cannot read them right away. Probably others too. Please don't tell me to get more _sophisticated_ email client, my pine does everything for me. HTML should NOT be used for posting emails. And then there are those of us that do have sophisticated email clients that simply don't care for HTML posting. I agree 100%, keep it simple, keep it TEXT! Sam And then there are those of us who use pine who think HTML in email is overkill. If your words don't convey your message, what makes you think that blinking text or bold text conveys it better? J. J. Horner Linux, Apache, Perl, Unix, Stronghold [EMAIL PROTECTED] http://www.knoxlug.org System has been up: 8 days.
Re: [admin] NO HTML posts please!
how about avoiding the me toos... At 02:04 PM 3/30/00 -0500, J. Horner wrote: On Thu, 30 Mar 2000, Sam Carleton wrote: Stas Bekman wrote: Folks, please refrain from posting in HTML. Some of us use email clients that post and read email in the old good text mode. When I don't have enough time on my hands I delete such emails since I cannot read them right away. Probably others too. Please don't tell me to get more _sophisticated_ email client, my pine does everything for me. HTML should NOT be used for posting emails. And then there are those of us that do have sophisticated email clients that simply don't care for HTML posting. I agree 100%, keep it simple, keep it TEXT! Sam And then there are those of us who use pine who think HTML in email is overkill. If your words don't convey your message, what makes you think that blinking text or bold text conveys it better? J. J. Horner Linux, Apache, Perl, Unix, Stronghold [EMAIL PROTECTED] http://www.knoxlug.org System has been up: 8 days. Angel R. Rivera, [EMAIL PROTECTED] -- Website: http://www.wolf.com Lists: http://www.wolf.com/lists/ -- "The Quality of a person's life is in direct proportion to their commitment to excellence, regardless of their chosen field of endeavor." Vincent T. Lombardi
Re: [admin] NO HTML posts please!
"Angel" == Angel R Rivera [EMAIL PROTECTED] writes: Angel how about avoiding the me toos... Yeah, and the people that post "upside down", with the answer *before* the question! Definitely. Let's avoid those. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Re: [admin] NO HTML posts please!
how about avoiding the me toos...
[44 lines of crud we've already seen before]
Hm... something wrong's with that message...
% msgchk `mhpath cur`
Quote follows response, Jeopardy style #2
Overquoted: 30 lines quoted out of 41: 73%
Non-canonical signature separator:
`--'
Signature too long: 7 lines
More than just *some*thing: that's four different violations.
print "BAD!\n" for 1..4;
--tom
#!/usr/bin/perl -w
# msgchk - check mail and news messages for netiquette violations
# [EMAIL PROTECTED]
use strict;
my $Msg = get_message();
missing_headers();
bogus_address();
allcap_subject();
annoying_subject();
mimes();
lines_too_long();
control_characters();
miswrapped();
jeopardy_quoted();
overquoted();
good_signature();
exit(0);
###
sub AUTOLOAD {
use vars '$AUTOLOAD';
my $field;
($field = uc($AUTOLOAD)) =~ s/.*:://;
if (!defined wantarray) {
require Carp;
Carp::confess("Undefined function call: $AUTOLOAD");
}
$Msg-$field();
}
sub bogus_address {
my $address = from();
if ($address !~ /\@\w.*\.\w/) {
print "From address must contain an at sign, etc.\n";
return;
}
if ($address =~ /(remove|spam)/i) {
print "Munged return address suspected, found `$1' in from.\n";
}
ck822($address);# inscrutable
my($host) = $address =~ /\@([a-zA-Z0-9_.-]+)/;
dns_check($host); # very slow!
}
sub control_characters {
my $lineno = 0;
my $MAX_CONTROL = 5;
for (lines()) {
$lineno++;
if (/(?=[^\s\b])([\000-\037])/) {
printf "Control character (char %#o) appears at line %d of body.\n",
ord $1, $lineno;
}
if (/([\202-\237])/) {
printf "Evil and rude MS-ASCII character (char %#o) appears at line %d of
body.\n",
ord $1, $lineno;
}
last if --$MAX_CONTROL 0;
}
}
sub lines_too_long {
my $MAX_LINE_LEN = 80;
my $line_count = scalar @{ [ lines() ] };
my ($long_lines, $longest_line_data, $longest_line_number) = (0,'',0);
my $lineno = 0;
for (lines()) {
$lineno++;
next if /^[+-]/; # skip quotes and patch diffs
if (length() $MAX_LINE_LEN) {
$long_lines++;
if (length() length($longest_line_data)) {
$longest_line_data = $_;
$longest_line_number = $lineno;
}
}
}
if ($long_lines) {
printf "%d of %d lines exceed maxlen %d, ",
$long_lines, $line_count, $MAX_LINE_LEN;
printf "longest is #%d at %d bytes\n",
$longest_line_number, length($longest_line_data);
}
}
sub missing_headers {
if (subject() !~ /\S/) {
print "Missing required subject header.\n";
}
if (newsgroups() subject() =~ /^\s*Re:/i !references()) {
print "Followup posting missing required references header.\n";
}
}
sub allcap_subject {
my $subject = subject();
$subject =~ s/^(\s*Re:\s*)+//i;
if ($subject !~ /[a-z]/) {
print "No lower-case letters in subject header.\n";
}
}
sub miswrapped {
my($bq1, $bq2);
for (paragraphs()) {
next unless /\A(^\S.*){2,}\Z/ms; # no indented code
if (!$bq1 /^\S.*\n\s*[a-zA-Z]/) {
print "Incorrectly wrapped quoted text.\n";
$bq1++;
}
next if $bq2;
my $count = 0;
while (/^[^].{60,}\n[^].{1,20}\n(?=[^].{60,}\n)/gm) {
$count++;
}
if ($count 1) {
print "Incorrectly wrapped regular text.\n";
$bq2++;
### print "OOPS count = $count:\n$_\n\n";
}
}
}
sub jeopardy_quoted {
local $_ = body();
$_ = unquote_wrap($_);
$_ = strip_signature($_);
$_ = strip_attribution($_);
# check quotation at bottom but nowhere else
# XXX: these can go superlong superlong! i've added
# some more anchors and constraints to try to avoid this,
# but I still mistrust it
if (/ ((^\s*.*){2,}) \s* \Z/mx
!/ (\n.*?)+ (\n[^].*?)+ (\n.*?)+ /x )
{
print "Quote follows response, Jeopardy style #1\n";
}
# completely at bottom
elsif (/^.* wr(?:ote|ites):\n(.*\n)+\s*\Z/m) {
print "Quote follows response, Jeopardy style #2\n";
}
# another way of saying the same
elsif (/^(?:+\s*)?-[_+]\s*Original Message\s*-[_+]\s.*\Z/ms) {
print "Quote follows response, Jeopardy style #3\n";
}
# another way of saying the same
elsif (/^(?:+\s*)?[_-]+\s*Reply Separator\s*[_-]+\s.*\Z/ms) {
print "Quote follows response, Jeopardy style #4\n";
}
}
sub overquoted {
# cfoq: check fascistly overquoted by [EMAIL PROTECTED]
# (wants perl 5.0 or better; developed under 5.002)
my (
$total,
Re: [admin] NO HTML posts please!
ROTFLOL On 30 Mar 2000, Randal L. Schwartz wrote: "Angel" == Angel R Rivera [EMAIL PROTECTED] writes: Angel how about avoiding the me toos... Yeah, and the people that post "upside down", with the answer *before* the question! Definitely. Let's avoid those. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Re: [admin] NO HTML posts please!
esrever ni snoitseuq gnirewsna diova esaelp dna On 30 Mar 2000, Randal L. Schwartz wrote: "Angel" == Angel R Rivera [EMAIL PROTECTED] writes: Angel how about avoiding the me toos... Yeah, and the people that post "upside down", with the answer *before* the question! Definitely. Let's avoid those.
