Dear Majordomo Majordomos:
I administer a majordomo list that is beginning to act in an undesireable
way. We are getting a rising number of messages coming through without the
fronter. To be more precise, the fronter is not visible to MIME-aware mail
clients.
Our ISP is running a:
"slightly customized version of majordomo 1.94.4 running on Solaris 2.5.1."
As far as I can tell so far, the messages that come through without visible
fronters are sent by Microsoft Outlook Express, maybe Internet Explorer,
and Netscape's browser, with HTML formatting. Since a rising number of
folks are using these clients, this is becoming noticeable. (My own mail
client is Eudora Pro 4.0 for Macintosh.)
My ISP Tech Support guy says:
"The list software is putting the fronter in on all messages. However the
problem is users who post MIME encoded mail (Content-Type:
multipart/alternative) cause MIME-aware mail readers to not see the added
fronter. So for example, John Smith's mail this evening appeared to have
the fronter missing. But when you look close it is actually there.
"However, MIME-aware mail readers cannot see it. Unfortunately there is no
solution for this as there is no way for majordomo to determine where it is
appropriate to place the fronter without possibly corrupting the
MIME-encoded message."
Any ideas you have on how to get our fronters to appear consistently will
be most appreciated. If you think a more recent version of Majordomo (if
there is one) would solve this, I'd love to hear about it.
TIA,
Roy Komack (NAPFA E-mail Admin)
CONFIG File excerpt
-----------------------------------------------------------------------
message_footer << END
END
# message_fronter [string_array] (undef) <resend,digest>
# Text to be prepended to the beginning of all messages posted to
# the list. The text is expanded before being used. The following
# expansion tokens are defined: $LIST - the name of the current
# list, $SENDER - the sender as taken from the from line, $VERSION,
# the version of majordomo. If used in a digest, only the expansion
# token _SUBJECTS_ is available, and it expands to the list of
# message subjects in the digest
message_fronter << END
-
********************************************************************
This message is being sent to all Members of the NAPFA e-mail list.
To reply to the sender, $SENDER,
just use the "Reply" function (or button) of your e-mail software.
If you think your reply will be of interest to all NAPFA Members,
THINK AGAIN!! We urge you to be considerate of your colleagues' time.
********************************************************************
END
# message_headers [string_array] (undef) <resend,digest>
# These headers will be appended to the headers of the posted
# message. The text is expanded before being used. The following
# expansion tokens are defined: $LIST - the name of the current
# list, $SENDER - the sender as taken from the from line, $VERSION,
# the version of majordomo.
message_headers << END
END
-----------------------------------------------------------------------
Sample Offending Message with INVISIBLE fronter:
-----------------------------------------------------------------------
Return-Path: napfa-owner@shore.net
Received: from aquarium.shore.net (aquarium.shore.net [207.244.124.7]) by
acestes-fe0.ultra.net (8.8.8/ult/n20340/mtc.v2) with ESMTP id NAA06678 for
<royk@komack.com>; Wed, 17 Mar 1999 13:22:20 -0500 (EST)
Received: (from major@localhost)
by aquarium.shore.net (8.8.7/8.8.7) id NAA08749
for napfa-outgoing; Wed, 17 Mar 1999 13:07:34 -0500 (EST)
Received: from siren.shore.net (siren.shore.net [207.244.124.5])
by aquarium.shore.net (8.8.7/8.8.7) with ESMTP id NAA08742
for <napfa@mlist.shore.net>; Wed, 17 Mar 1999 13:07:30 -0500 (EST)
Received: from (enyo.ez2.net) [209.203.127.19]
by siren.shore.net with smtp (Exim)
for napfa@shore.net
id 10NKnW-0007DU-00; Wed, 17 Mar 1999 13:12:06 -0500
Received: from [209.203.127.132] by enyo.ez2.net (NTMail 3.03.0018/1d.aaby)
with ESMTP id ba573171 for <napfa@shore.net>; Wed, 17 Mar 1999 10:22:01
-0800
Message-ID: <000901be70a2$17eeee60$847fcbd1@oemcomputer>
From: "Karin McKerahan" <mckerahan@ez2.net>
To: "NAPFA members" <napfa@shore.net>
Subject: Seeking RMD calculator
Date: Wed, 17 Mar 1999 10:15:09 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0006_01BE705F.09349E80"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-napfa@shore.net
Precedence: bulk
Reply-To: "Karin McKerahan" <mckerahan@ez2.net>
X-UIDL: 9ddc3db09bab61ae446b48954aabbb50
<x-html><!x-stuff-for-pete base="" src="" id="0"><!DOCTYPE HTML PUBLIC
"-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.72.3110.7"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#000000 size=2>I am looking for an inexpensive RMD
calculator. I seem to recall that Brentmark made theirs available last
year to NAPFA members at no cost. Does anyone know if that offer still
stands and how I can obtain it?</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV>
<DIV><FONT color=#000000 size=2>Thanks for your help.</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV>
<DIV><FONT color=#000000 size=2>Karin McKerahan</FONT></DIV>
<DIV><FONT color=#000000 size=2>Temecula, CA</FONT></DIV>
<DIV><FONT color=#000000 size=2><A
href="mailto:mckerahan@ez2.net";>mckerahan@ez2.net</A></FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV></BODY></HTML>
</x-html>
-----------------------------------------------------------------------
Roy L. Komack, NAPFA CyberCop <royk@komack.com>
Komack Management Services, Inc. Phone & FAX: (508) 655-0210
WWW: http://www.napfa.org News news://blackrat.cqlcorp.com/napfa.forum
___________________________________________________
Follow-Ups:
|
|
