On Wed, 10 Apr 1996, Douglas J. Archell wrote:
> Marc, I've run into a snag with the list config. I've searched high
> and low and cannot find an answer to this problem.
> As it stands right now, when a message is sent out to the list:
> a - If you are using something like Pegasus mail, when you receive
> the message, you do NOT get a listing of all the users that are on
> the list. (That's good!) BUT:
> b - If a subscriber is on one of the major services, for example,
> CompuServe, a listing of other CIS subscribers is provided. For
Looking at who is currently on the list, everyone is @compuserve.com
*except* for your @netcent.com account. Did you send this to the list
from the netcent.com account? If so, I'm wondering if the only
reason that that address wasn't listed as well was because it strips
off that one.
If so...I don't think that the error is with Majordomo, or our system,
but with the way that compuserve handles email. It doesn't get sent
out as individual messages, but as one large message, I believe, using
Bcc. It is quite possible that compuserve doesn't honor the Bcc header,
which is why you are getting the "Apparently-To:" header in it.
Its like with FidoNet, where all email/newsgroups are the same thing, except
that some are considered public and some private...CompuServe is a BBS, not
an Internet server, and uses a gateway to get its mail across :(
I've CC'd this into both the users and workers mailing list for Majordomo
for a more complete assessment of the problem, and hopefully, either a
confirmation of the above, or a fix.
> Following is the header portion of a message, as it was received on
> Subject: Message from Internet
> From: INTERNET:firstname.lastname@example.org
> To: Doug Archell [NetWire] 74777,2670
> Date: 10-Apr-96 04:58
> Sender: email@example.com
> Received: from ki.net (ki.net [126.96.36.199]) by
> dub-img-6.compuserve.com (8.6.10/5.950515)
> id EAA06188; Wed, 10 Apr 1996 04:57:32 -0400
> From: <firstname.lastname@example.org>
> Received: (from majordom@localhost) by ki.net (8.7.4/8.7.4) id
> EAA15977 for netnotify-outgoing; Wed, 10 Apr 1996 04:57:35 -0400 (EDT)
> Date: Wed, 10 Apr 1996 04:57:35 -0400 (EDT) Message-Id:
> <199604100857.EAA15977@ki.net> X-Authentication-Warning: ki.net:
> majordom set sender to owner-netnotify using -f Apparently-To:
> <email@example.com> Apparently-To: <firstname.lastname@example.org>
> Apparently-To: <email@example.com> Apparently-To:
> <firstname.lastname@example.org> Apparently-To: <email@example.com>
> Apparently-To: <firstname.lastname@example.org> Apparently-To:
> <email@example.com> Apparently-To: <firstname.lastname@example.org>
> Apparently-To: <email@example.com>
> To the initial NetNotify subscribers....
> Sender: owner-netnotify
> Precedence: bulk
> As you can see from the above, for some reason, all other CIS id's
> that had subscribed to the list have their ID's listed here. This
> can result in a MAJOR problem and PITA for the users. I am expecting
> upwards of 2000 subscribers coming from CompuServe. I really don't
> think subscribers will like receiving a message whereby the header
> alone is 2000 lines long. Actually, 2000 subscribers from CIS is
> probably modest. Of the 15,000 users expected in the first 3 months,
> I could easily see 5000 of those potentially coming from CIS.
> If you're like me, you probably would get a bit ticked if you had to
> spend 5 mins downloading a single email message because their were
> 5000 lines of email addresses.
> Suggestions? This is a serious problem and definitely a rush. Come
> Friday, there will be a shitload of users that will know about the
> list server and will start subscribing to it.....HELP.....
Marc G. Fournier firstname.lastname@example.org
Systems Administrator @ ki.net email@example.com