[petsc-dev] Fwd: [petsc-maint #124771] bug report

Jed Brown jedbrown at mcs.anl.gov
Thu Jul 19 17:46:32 CDT 2012


On Thu, Jul 19, 2012 at 5:38 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

> > This is what I do for myself [with pine]
>
>    Doesn't solve the problem because the user still has in their header
> the developers email address.
>

This is something that a developer using certain hosts can do to make the
issue moot, not something that involves the user.


> >> Alternative would be for petsc-maint to remove the user's email from
> >> reply-to when it delivers to us, then match message headers so that our
> >> replies which go only to petsc-maint would be forwarded to the original
> >> reporter. Seems very fragile.
>
>     That is what it should do. Nothing fragile about it. Not hard shit.
>

What happens when the user Cc's other people in a follow-up. We don't even
see the Cc's, but petsc-maint keeps emailing them. Even if the user
shortens the Cc list, does the server know to remove it? Suppose the
initial report Cc's some people that might be interested, but later they
remove those addresses and send something sensitive that the original Cc
list should not be able to see. It would have to be written carefully to
preserve email semantics while emulating all of us being a single address.
I don't have a reason why it can't be done, but I think it's something that
could easily be messed up.


> > And then there will be no more private
> > messages [between us] on petsc-maint :)
>
>     Why? petsc-maint server will always bounce everything sent to it back
> to the developers.


How often does some not-to-be-named developer remove the user from the Cc
list and make a snide remark?

If you answered Never, you earn two points.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120719/463156f6/attachment.html>


More information about the petsc-dev mailing list