Oct. 26, 2000
4:50 a.m.
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.