The Gateway

A information about a key piece of software for the early days of the Ruby community.

1

DEC
2006

What is the Ruby Talk Gateway?

[Update: The Ruby Gateway was retired in June of 2011. Our community simply grew past the point were we needed to combine the various groups, in my opinion.]

The Ruby community makes use of both email and Usenet communication, in addition to other resources. The primary mailing list is Ruby Talk and the primary Usenet group is comp.lang.ruby. These two services are joined by the Ruby Gateway.

In 2001 The Pragmatic Programmers wrote the initial version of the Ruby Gateway to ferry messages back and forth between these two resources. Emails sent to Ruby Talk are posted as Usenet messages and Usenet posts are forwarded to Ruby Talk by the Gateway. The Gateway has had a few guardians and code changes since then, but the functionality remains the same.

I'm am the current caretaker of the Ruby Gateway. Highgroove Studios generously provides hosting for it and I monitor the system for problems. I also wrote the current version of the Gateway.

You are free to report Gateway problems for me to look into. Before you do though, please read the following notes:

  • I rewrote the entire Gateway after I assumed control of it. My code was deployed on December 4th, 2006, so anything before that is history. If you raise issues, please make sure they involve posts after that date.
  • I now have very detailed logs on everything the Gateway does, so please be specific. For example, please send me links to exact messages that appeared on one side of the Gateway, but not the other.
  • Our Usenet host does not allow us to post HTML emails (multipart/alternative). This is not changing. These messages are not supported. (Yes, that means you should not be sending HTML email to Ruby Talk.)
  • Our Gateway is an NNTP ↔ email Gateway. There has been at least one instance of a Usenet post using ancient header formatting predating NNTP. These messages are not supported.
Comments (4)
  1. Daniel Berger
    Daniel Berger December 3rd, 2006 Reply Link

    Are you rejecting HTML messages out of hand or simply stripping the HTML?

    I'm pretty sure I've sent emails in HTML format by mistake, since that's what Thunderbird defaults to.

    1. Reply (using GitHub Flavored Markdown)

      Comments on this blog are moderated. Spam is removed, formatting is fixed, and there's a zero tolerance policy on intolerance.

      Ajax loader
    2. James Edward Gray II
      James Edward Gray II December 3rd, 2006 Reply Link

      I am not doing anything about HTML. I forward all emails Ruby Talk receives to the NNTP host the Gateway uses.

      That host rejects posts that are not appropriate for Usenet. (It's important to remember that Usenet is a different world than mailing lists and has its own rules.) Many Usenet servers block HTML posts (sent as multipart/alternative) and the host the Gateway uses is the one of them. Even if we had our host lift this ban, the message would have poor circulation on the Usenet hosts and it's hard to see that as an improvement.

      It is feasible that we could convert HTML emails before forwarding them to Usenet and try to get them down to a reasonable format. Some emails would be pretty non-trivial to handle correctly though, in my opinion.

      Sending HTML email is a frowned upon by more than just our NNTP host though. Spam Assassin assigns spam points just for an email being formatted as such and since that's pretty much a standard now, you best avoid the format if you want your message to actually get where you sent it. It's probably an even bigger sin in tech communities like Ruby Talk, where we are constantly working with code.

      Given that, I'm not too concerned about burning effort to do the HTML conversions myself. I'll offer a compromise though, I'm going to release the code the Gateway uses on this blog soon. Others who are interested are welcome to offer up changes to the code to handle these and other issues. We will debate their value and I may choose to include some modifications.

      My opinion is that this is an important enough issue to spend a few moments learning how to configure your email client properly though.

      1. Reply (using GitHub Flavored Markdown)

        Comments on this blog are moderated. Spam is removed, formatting is fixed, and there's a zero tolerance policy on intolerance.

        Ajax loader
      2. Daniel Berger
        Daniel Berger December 3rd, 2006 Reply Link

        I think making some effort to strip HTML would be reasonable, perhaps with a warning attached somewhere in the message that it was reformatted. That, or a reply to the sender that HTML formatted email is unwelcome. Or both. Something tells me that hpricot will be involved one way or another. :)

        As for configuring email clients, it's not as easy as you might think. In Thunderbird, there are actually two different places to specify settings for message composition.

        In MS Outlook, I still don't think I've gotten it set right, as it insists on replying in HTML format if that's the format I received the original post in, even though I've selected options that are supposed to make all of my replies plain text.

        Mind you, that's mostly a moot point now with the annoying disclaimer my company has decided to tack onto all outgoing emails (perhaps an issue in and of itself that we may want to tackle some day). Now I use Gmail via the web browser which, btw, I will now have to remember to set to plain text before hitting the send button. :)

        Hopefully this reply didn't sound like whining. It's not meant to, anyway. Just a heads up as to what some of the issues are that the end users will be facing.

        1. Reply (using GitHub Flavored Markdown)

          Comments on this blog are moderated. Spam is removed, formatting is fixed, and there's a zero tolerance policy on intolerance.

          Ajax loader
        2. James Edward Gray II
          James Edward Gray II December 3rd, 2006 Reply Link

          Thanks for volunteering for the HTML assistance. ;)

          I'll get the code up for you soon.

          1. Reply (using GitHub Flavored Markdown)

            Comments on this blog are moderated. Spam is removed, formatting is fixed, and there's a zero tolerance policy on intolerance.

            Ajax loader
Leave a Comment (using GitHub Flavored Markdown)

Comments on this blog are moderated. Spam is removed, formatting is fixed, and there's a zero tolerance policy on intolerance.

Ajax loader