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

On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> Hi,
>
> This has happened to me a few times. I give an email a very quick look,
> determine it is spam, move on, then a few seconds later realize that it
> was a job offer.
>
> I tried to make up for it by bouncing the message to pgsql-jobs, but
> that didn't work; I assume Exim or something determined that the message
> was spam since it wasn't coming from whom was the real sender address.
> I don't think this is really workable anyway.
>
> 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
>
> I think a good fix here would be to have the archives code display a
> message-in-message.

If you forwarded it as text it would've worked :-P

I'm betting the problem this time (not on a computer to confirm atm) is
that your message was sent as one plaintext piece with nothing, or possibly
your signature, in it. And then one rfc822 arraignment. We then extract the
plaintext piece and show that.

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)?

> (Another fix would be that I no longer moderate pgsql-jobs, but then
> somebody else would have to do it. Should I ping pgsql-core to nominate
> a moderator?)

In that regard you are probably better off just asking for a volunteer
first. Its not like someone can actually be appointed to it, they'd have to
volunteer first..

/Magnus