2.0rc1 / no explicit Reply-To: header
I've got one list that I run explicit Reply-To: headers on. I just upgraded from a lightly patched b6 to 2.0rc1, and the Reply-To: header is still not being sent to the list. Since this version is a release candidate it seemed reporting.
-- Michael
argh... bad taste to reply to my own post, but it just occurred to
me that I saw one other bug. With the explicit header defined, I
tried to remove it by blanking the explicit Reply-To header field.
However, when I submitted the changes, the redisplayed page still
had the old value. It seems that once it gets in, it is stuck.
-- Michael
On Wed, 25 Oct 2000, Michael Brennen wrote:
I've got one list that I run explicit Reply-To: headers on. I just upgraded from a lightly patched b6 to 2.0rc1, and the Reply-To: header is still not being sent to the list. Since this version is a release candidate it seemed reporting.
"MB" == Michael Brennen <mbrennen@fni.com> writes:
MB> With the explicit header defined, I tried to remove it by
MB> blanking the explicit Reply-To header field. However, when I
MB> submitted the changes, the redisplayed page still had the old
MB> value. It seems that once it gets in, it is stuck.Correct. Although it doesn't make any sense to have explit reply-to set and have an empty reply-to field, Mailman's admin interface could be smarter about this. It won't get fixed for 2.0, but I've submitted a bug report so it won't get lost.
-Barry
participants (2)
-
barry＠wooz.org -
Michael Brennen