Someone did reply... don't remember what he/she/it said, but it had to do
something with the way Imail writes/rewrites headers.
For myself, I've never seen this problem until Outlook 2k. It's a client
issue... if you got a problem with it, either don't use O2k or talk to
Microsoft to see if they'll fix it.
My mailbox looks fine from pine and mutt... dunno about the other GUI MUAs,
O2k is the only one I use. Taking this argument further, it's worth noting
that I'm subscribed to several lists, being run on a wide variety of MTA and
list management software. Outlook 2K has the same problem on *ALL* of my
subscribed mailing lists.
-Troy
** -----Original Message-----
** From: [EMAIL PROTECTED]
** [mailto:[EMAIL PROTECTED]]On Behalf Of Sanford
** Whiteman
** Sent: Sunday, April 09, 2000 11:46 PM
** To: [EMAIL PROTECTED]
** Subject: [IMail Forum] Imail Mailing Lists, Sender: field, and Outlook
** 2000
**
**
** (I posted this last week and no one responded. C'mon, guys, can
** I get some
** real help here instead of watching y'all waste time making fun
** of some guy
** who mistyped "600" as "6000"? There are still people --
** including Ziad as
** well -- who are using this list for supplementary technical support.
** Thanks!)
**
** Hey, everyone...have you noticed this? In Outlook 2000, the
** Sender: value
** appears in the From: address in the following form:
**
** From: <sender:> on behalf of <from:>
**
** This is only visible in Message Preview and Message View modes,
** not in the
** Inbox itself.
**
** The problem is not present in Netscape 3.x and 4.x, nor in
** Outlook Express
** 4.x and 5.x. I don't know about Eudora or other clients, but,
** in any case,
** this is a MAJOR problem for our organization, since we just
** moved to Outlook
** 2000. See, we reuse a series of generic mailing lists ("List1," "List2,"
** etc.) to get around having to dynamically create new mailing lists for
** one-off mailings, and use recipient impersonation via a friendly name:
**
** To: "Friendly Name" <genericlistname>
**
** It's a cool scheme, and one that I would have otherwise suggested to you
** all, except that under OL2K it breaks. Users are now asking, "Who's this
** 'List79-owner' who keeps sending me messages?" Previously, the true list
** names would only be viewable in View Source mode, and we didn't consider
** that a problem, since internal users have no business
** questioning raw SMTP.
** But now, they *see* the field in general use, and our masquerade
** is undone.
**
** An additional note for the Ipswitch people: the SMTP RFCs
** specify that the
** Sender: field is appropriate if the server has a more reliable or "true"
** sender that it knows about. Many servers "x-" out the Sender:
** field because
** they know that it can cause problems. In this case, I understand that
** Imailsrv.exe is really doing the sending, and that it thinks that the
** Mailing List owner is a more reliable sender than the From:
** address of the
** original post, so it will "x-" out any other Sender: fields and
** put in its
** own. But there's a logical issue here. Imailsrv puts a name like
** "List79-owner" in as the Sender: field without first checking to
** see if that
** is a legit address. In fact, I can delete all of the
** "<listname>-owner" and
** "owner-<listname>" aliases, and the server *still* thinks that
** "List79-owner" is a more reliable source than the From: address
** -- which in
** our organization is always a legitimate local user of the Imail
** server who
** has to (a) supply a password and (b) be on the POSTERS.LST to
** even use the
** list! Isn't that user a LOT more reliable as a Sender: field?
** I'd say yes!
**
** Is there a workaround for this issue? Can anyone help?
**
** Thanks,
**
** Sandy
**
**
** Please visit http://www.ipswitch.com/support/mailing-lists.html
** to be removed from this list.
**
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
