Обсуждение: messed up message/rfc822 in archives.pg.org
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. (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?) -- Álvaro Herrera Developer, http://www.PostgreSQL.org/ Jason Tesser: You might not have understood me or I am not understanding you. Paul Thomas: It feels like we're 2 people divided by a common language...
On Wed, Jun 10, 2015 at 3:16 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > 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. Are you sure this isn't just spam? I received recruitment spam about a Postgres DBA job in Berlin today. Some recruiter sent this to my personal e-mail address, and I marked it as spam. I classify it as spam because had the recruiter taken 2 seconds to consider what he was doing, he would not have sent it. Clearly getting me to move from San Francisco to Berlin to go from hacking on Postgres to being an ordinary DBA is an impossibly hard sell. And so, I'm sure that everyone with an e-mail address on the contributors pages received a similar e-mail. -- Peter Geoghegan
Peter Geoghegan wrote: > On Wed, Jun 10, 2015 at 3:16 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > 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. > > Are you sure this isn't just spam? I received recruitment spam about a > Postgres DBA job in Berlin today. Some recruiter sent this to my > personal e-mail address, and I marked it as spam. I am not, but I view these job offers as possibly very valuable for some people, and therefore I strive not to lose any. > I classify it as spam because had the recruiter taken 2 seconds to > consider what he was doing, he would not have sent it. Clearly getting > me to move from San Francisco to Berlin to go from hacking on Postgres > to being an ordinary DBA is an impossibly hard sell. Well, I'm not eager to work as a DBA either, but then I'm not everybody. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
<p dir="ltr"><br /> On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <<a href="mailto:alvherre@alvh.no-ip.org">alvherre@alvh.no-ip.org</a>>wrote:<br /> ><br /> > Hi,<br /> ><br /> >This has happened to me a few times. I give an email a very quick look,<br /> > determine it is spam, move on, thena few seconds later realize that it<br /> > was a job offer.<br /> ><br /> > I tried to make up for it by bouncingthe message to pgsql-jobs, but<br /> > that didn't work; I assume Exim or something determined that the message<br/> > was spam since it wasn't coming from whom was the real sender address.<br /> > I don't think this isreally workable anyway.<br /> ><br /> > I next tried forwarding it. It worked fine, but the archives don't<br />> display it well. See for yourselves:<br /> ><br /> > <a href="http://www.postgresql.org/message-id/20150610214737.GB133019@postgresql.org">http://www.postgresql.org/message-id/20150610214737.GB133019@postgresql.org</a><br />><br /> > I think a good fix here would be to have the archives code display a<br /> > message-in-message.<p dir="ltr">Ifyou forwarded it as text it would've worked :-P<p dir="ltr">I'm betting the problem this time (not on a computerto confirm atm) is that your message was sent as one plaintext piece with nothing, or possibly your signature, init. And then one rfc822 arraignment. We then extract the plaintext piece and show that. <p dir="ltr">Actually doing a fullyrecursive 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)?<br /><br /><p dir="ltr">> (Another fix would be that I no longer moderate pgsql-jobs, but then<br /> > somebodyelse would have to do it. Should I ping pgsql-core to nominate<br /> > a moderator?)<br /><p dir="ltr">In thatregard you are probably better off just asking for a volunteer first. Its not like someone can actually be appointedto it, they'd have to volunteer first.. <p dir="ltr">/Magnus
Magnus Hagander wrote: > On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <alvherre@alvh.no-ip.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.) > 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. Yeah, exactly. > 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 ... > > (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.. I have appointed Vik Fearing, who volunteered on IM. Other moderators are Devrim (I'm sure you know the guy) and Josh Berkus. Btw I received no less than FOUR notices on IM that my email on pgsql-jobs surprised people. I am happy not to moderate that list anymore. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Thu, Jun 11, 2015 at 5:25 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Actually, bounce would be the best thing to make work. I wonder what ate it thoguh - can you find that in the logs?
Magnus Hagander wrote:
> On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <alvherre@alvh.no-ip.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...
> 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.
Yeah, exactly.
> 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?
> > (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..
I have appointed Vik Fearing, who volunteered on IM. Other moderators
are Devrim (I'm sure you know the guy) and Josh Berkus.
Btw I received no less than FOUR notices on IM that my email on
pgsql-jobs surprised people. I am happy not to moderate that list
anymore.
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.
Magnus Hagander wrote: > On Thu, Jun 11, 2015 at 5:25 PM, Alvaro Herrera <alvherre@2ndquadrant.com> > wrote: > > > Magnus Hagander wrote: > > > On Jun 11, 2015 12:16 AM, "Alvaro Herrera" <alvherre@alvh.no-ip.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