Re: [sysadmins] messed up message/rfc822 in archives.pg.org

Magnus Hagander wrote:
> On Thu, Jun 11, 2015 at 5:25 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> wrote:
>
> > Magnus Hagander wrote:
> > > On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>
> > wrote:
> >
> > > > I next tried forwarding it. It worked fine, but the archives don't
> > > > display it well. See for yourselves:
> > > >
> > >
> > http://www.postgresql.org/message-id/20150610214737.GB133019@postgresql.org
> > >
> > > If you forwarded it as text it would've worked :-P
> >
> > Why would I do that! (I'm sure there's a keystroke or setting for that
> > in Mutt, but I never use it.)
> >
>
> There is. I set it to prompt (set mime_forward=ask-yes).
>
> You wouldn't believe the number of MUAs that can't deal with the other
> one...

Bummer. I like the rfc822 format much better.

> > > Actually doing a fully recursive parse of the mime structure can
> > > basically become arbitrarily complex. We could special case this
> > > one of course, but does it really happen often enough to be worth
> > > it? And when it had such a simple workaround (use plain text)?
> >
> > Well, I think I have forwarded messages in counted other cases. It's
> > not like I do it every week, but it does happen. Then again, I'm not
> > writing any of that code ...
>
> :)
>
> Actually, bounce would be the best thing to make work. I wonder what ate it
> thoguh - can you find that in the logs?

Will look later.

> Haha :) Well, if we have other moderators on it, then we're probably OK.
>
> But that doesn't mean we shouldn't figure out the right way to deal with
> the tech.

Ok.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services