I know this might sound a bit odd, but I have a number of subscribers
who are complaining about not seeing the proper formatting (line breaks)
on their messages to my lists.
They all use Eudora (various recent versions) on Windows and I have
confirmed that their messages are being sent with the format=flowed
Content-type. The messages display correctly in all other systems that I
have access to but I have confirmed that when I use Eudora on an MSPC
the paragraph breaks (i.e. the inserted returns) are removed.
The fly in the ointment is that if messages are sent directly to these
subscribers the formatting comes through correctly. So if I send a
message to the list using format=flowed and CC the subscriber they will
see the CC message correctly but he one they get via Smartlist is
displayed with empty lines stripped (although all other subscribers see
things as intended).
My rc.? files do not touch the Content-type header so I'm not munging it
in any way on the listserver (and I have confirmed that header comes
back as it was sent).
This seems to be very confusing and telling people to drop Eudora or
even turn off format=flowed isn't the best option (especially when they
get their ordinary mail) just fine.
Rich
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it.
==============================================================================
I plucked this recipe from the FAQ's for rc.local.s20. It
isn't working at all - no footers are getting inserted.
Any clues what may be wrong?
Can you also explain how much of the footer.txt files this
'pulls in' to compare against the message?
Jo
#
# Add text below each message - this one prevents duplication
#
TEXT=`sed -n '2 p' <footer.txt`
:0 fbBw
* $ ! $\TEXT
| cat - footer.txt
Folks;
Has anyone written any add-ons for SmartList to limit the number of
archive server requests any given address may submit within a given
timeframe? Before I look at playing around with it, I figured I'd better ask
to avoid re-inventing the wheel...
Charlie
On 2003.01.06 15:38 Jim Osborn wrote:
> I'm totally confused by the statement "I have indeed replaced A with
> B".
No wonder, since I stupidly reversed the symbols. Twice. Sorry.
The story with real names this time: subscribers David and Leo dislike
each other. Leo has blocked mail from David. David posted to the
list, so David's list traffic bounced from Leo's address. SmartList
removed David, the innocent party.
(I double-checked, and that time I told the tale right-side-out.)
Anyway, David is reinstated and Leo is banned for the present.
Hopefully Charlie Summers' testing will lead to something more
palatable to Leo.
--
Don Doumakes
I'm using the latest version of SmartList. Recently I had an episode
in which subscriber A started selectively bouncing all mail from
subscriber B. SmartList automatically unsubscribed subscriber B,
rather than the address creating the bounced mail (A).
Leaving aside the question of why A and B can't just get along, is
there a solution to the erroneous behavior? Is this a bug of which the
developers are aware?
--
Don Doumakes
On 2003.01.06 11:23 Charlie Summers wrote:
> It's unlikely he's "bouncing" mail through his SMTP server; I
> could, for
> example, add your address to sendmail's access file as a REJECT, but
> your
> list messages would still get through, since when the list distributes
> a
> message _it_ is the envelope sender, not you. Looks more like A is
> doing
> something with procmail, or worse some moronic Windoze application
> that
> trusts the From: header field.
That makes sense. Clearly, though, A is somehow returning an error
return to the MTA. Mr. A is an AOL subscriber. The bounce message
from the AOL mailer daemon to the list-request address (addresses
munged) says:
> From MAILER-DAEMON(a)mymachine.mydomain.net Fri Jan 3 07:58:09 2003
Return-Path: <MAILER-DAEMON(a)mymachine.mydomain.net>
Received: from omr-d03.mx.aol.com (omr-d03.mx.aol.com [205.188.159.1])
by mymachine.mydomain.net (8.11.6/8.11.2) with ESMTP id
h03Dw4602881
for <mylist-request(a)mydomain.net>; Fri, 3 Jan 2003 07:58:04
-0600
Received: from air-xi03.mail.aol.com (air-xi03.mail.aol.com
[172.20.116.3]) by omr-d03.mx.aol.com (v86_r1.15) with ESMTP id
RELAYIN10-0103085745; Fri, 03 Jan 2003 08:57:45 -0500
from: Mail Delivery Subsystem <MAILER-DAEMON(a)aol.com>
Date: Fri, 3 Jan 2003 08:55:58 EST
To: <mylist-request(a)mydomain.net>
Subject: Mail Delivery Problem
Mailer: AIRmail [v90.10]
Message-ID: <200301030857.10IdEFUa06586(a)omr-d03.mx.aol.com>
Your mail to the following recipients could not be delivered
because they are not accepting mail from A(a)aol.com:
B
I don't have an informed opinion on whether this is a malformed
bounce. (Do you?) In any case, B was eventually told:
Your mail address B has been removed
from the mylist(a)mydomain.net mailinglist.
It generated an excessive amount of bounced mails.
> Your specific problem doesn't seem to call for a technical
> solution, but
> rather a social one. My solution would be, as listmaster, to reinstate
> B and
> immediately unsubscribe A until A bought a clue on how to tell the
> difference
> between Return-Path: and From:.
The suggestion at a social solution is well taken, and I have indeed
replaced A with B.
Still, I'm guessing that as an AOL subscriber, A lacks the kind of
tools that would make it possible to bounce more politely. Sooner or
later this problem will be back, with a different cast of characters,
and it would be nice to solve it technically.
--
Don Doumakes
Are the principal text files available somewhere in spanish?
thanks,
....................................................................
Libros en Español, Diccionarios Electrónicos,
Música de América y de España...
http://www.LeerEsPoder.com/LibrosEnEspanol.php
A bug has been introduced into the confirm versions 1.2.7 - 1.3.0
resulting in the failure to put someone on the subscriber list after
succesful confirmation. In versions 1.2.7 - 1.3.0 I did some bugfixes
and improvements for the unsubscribe feature of confirm and missed to
test also the subscribe functionality which lets the newly introduced
bug leak through. If you use the versions mentioned above you should
upgrade to version 1.3.1 (ftp://ftp.pure.ch/smartlist) or apply the
attached patch to rc.request. confirm versions below 1.2.7 are not
affected.
Werner
I have not located a way to put a [ListName] in each message and to include
text or links in the bottom of a message.
Thanks in advance.
Russell Griechen
I have an unmoderated SmartList mailing list with foreign_submit off. On
a few occasions, subscribers have sent messages to the list, and have
copied people who are not on the list. When those people respond, their
messages bounce to the list maintainer (i.e. me).
What's the right way to approve those messages, so that they do go to the
list?
I tried setting an Approved header, as you would if the list were
moderated and the person was subscribed. This would work in Majordomo,
regardless of whether the person were subscribed or the list were
moderated. However, the message bounces back to me, presumably because
the person is not subscribed.
I've managed to do it by adding the person's e-mail address to accept2,
and reforwarding the message to the list. I'm not crazy about this as a
solution. Is there a correct way to accomplish this?
Thanks!
-Eugene
--
+=== Eugene Eric Kim ===== eekim(a)eekim.com ===== http://www.eekim.com/ ===+
| "Writer's block is a fancy term made up by whiners so they |
+===== can have an excuse to drink alcohol." --Steve Martin ===========+
