🚀 go-pugleaf

For some time, now, my mail feed has been munging incoming From: lines.
Where the original reads 'user@some.site.name', I get it and it looks
like 'umn-cs!user%some.site.name'.  On really rare occasions, I'll see
something like 'othersite!yasn!user@some.site.name' get turned into
'umn-cs!othersite^yasn^user%some.site.name' or 'user%place@some.site'
turn into 'umn-cs!user%place%some.site'.

When the carats appear, replies choke after I pass them to the feed, but
I compensate for those manually.  But what if the mail's not for me?

With the increased traffic on my fileserver this past weekend, I'm
noticing that they are rewriting the Reply-To: line too!  I had thought
that was sacrosanct, but noooooooo....

I'm asking yet again to have this fixed.  Meanwhile, what's the
consensus about rewriting headers?  Are they going too far in nailing
the Reply-To?  I think so, but I can't find anything (yet) in the RFCs
that speaks specifically to rewriting headers.

I can compensate in the fileserver's logic, but I'd really rather have
things work right the first time, y'know?
--
Roy M. Silvernail --  roy%cybrspc@cs.umn.edu - OR-  cybrspc!roy@cs.umn.edu
  perl -e '$x = 1/20; print "Just my \$$x! (adjusted for inflation)\n"'
          "Does that not fit in with your plans?"
                      -- Mr Wiggen, of Ironside and Malone (Monty Python)