[Mailman-Developers] Re: [Mailman-Users] minor archive problem after upgrade..

[Mentor Cana]

I think it is true that the "reply_goes_to_list" decides(indirectly) if the
sender's e-mail is displayed in the archives or the list e-mail addresses [as
described below]. Actually, my experiment showed that if the Reply-To:
field is present in the messages it is used to set the addresses in the
archives. Given that "reply_goes_to_list" will set Reply-To: to list's
address, that is the address to show up in the archives.

Question: Is this as per design? My understanding is that the
"reply_goes_to_list" should not be the deciding maker on whether sender's
e-mail address shows in the archives or not. There are other setting to
decide about this.

Any comments?!

thanks,
Mentor

On Tue, 23 Jan 2001, at 08:42, D.J. Atkinson wrote:
> I'd guess it's related to the setting of "reply_goes_to_list"  [General
> Options page of the list admin interface, described as "Where are replies
> to list messages directed?"] If this is set so that replies default to the
> sender, the archive shows the sender's email address.  If the default
> reply goes to the list, the archive shows the list address.  It seemed
> pretty consistent across the lists I checked.
>
> On Tue, 23 Jan 2001, Phydeaux wrote:
>
> >On Tue, 16 Jan 2001, at 04:42, Michael Dunston wrote:
> > > I recently upgraded both Mailman (2.0b5 -> 2.0) and Python (1.42 -> 2.0)
> > > and just noticed that the HTML archives are being created differently.
> > >
> > > In the old system, the individual HTML archived messages listed the
> > > poster's name and email address at the top of the page.  For all messages
> > > after the upgrade, this is now being created as the poster's name with
> > > the list address (instead of the user's email).
> > >
> > >     it was: Tom Smith tsmith@domain.com
> > >     now is: Tom Smith list@listaddress.com
> > >
> > > Is this normal?  Can anyone offer any insight into this?   Thanks in
> > > advance for any enlightenment.
> >
> >IMHO this is NOT just an upgrade problem...
> >
> >I have the same problem on one of my lists, and I am using Python 2.0
> >and initially installed Mailman 2.0 and then upgraded to 2.01. Only one
> >of my numerous lists suffers from this problem.  I tried wiping out the
> >archives and each time they get recreated with the same problem.
> >
> >I just tried creating a new, test, list and it seems to function fine (I
> >used the default options). Does anyone have any idea what is wrong here?
> >
> >reb
> >
> >
> >------------------------------------------------------
> >Mailman-Users maillist  -  Mailman-Users@python.org
> >http://mail.python.org/mailman/listinfo/mailman-users
> >
>
> --
>        o o o o o o o . . .                                  _______
>       o         _____ _____        ____________________ ____] D D [_||___
>    ._][__n__n___|DD[ [     \_____  |  D.J. Atkinson   | | dj@pcisys.net |
>   >(____________|__|_[___________]_|__________________|_|_______________|
>   _/oo OOOO OOOO oo` 'ooooo ooooo` 'o!o            o!o` 'o!o         o!o`
> -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-
> Visit my web page at http://www.pcisys.net/~dj
>
>
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
>