chat filter, my own site is blocked?

Discussion in 'Windows MSN Messenger' started by Wes., Aug 2, 2007.

  1. Wes.

    Wes. Guest

    i was chatting with a mate of mine, and he didn't received the url of my
    website ?

    Could someone of you microsoft wizards tell my why i can't talk about my own
    website ? ( http://www.misbruik.info/ )

    If you guys use something of content filtering i would like to know when my
    message is blocked.

    This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    windows messenger 4.7 and windows messenger 7.something.

    Can someone in the name of god tell me what's going on ?
     
    Wes., Aug 2, 2007
    #1
    1. Advertisements

  2. Wes.

    mae Guest

    An instant message that has ".info" is blocked.
    Just "info" in a message is not.
    --
    mae

    "Wes." <> wrote in message
    news:...
    |i was chatting with a mate of mine, and he didn't received the url of my
    | website ?
    |
    | Could someone of you microsoft wizards tell my why i can't talk about my own
    | website ? ( http://www.misbruik.info/ )
    |
    | If you guys use something of content filtering i would like to know when my
    | message is blocked.
    |
    | This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    | windows messenger 4.7 and windows messenger 7.something.
    |
    | Can someone in the name of god tell me what's going on ?
    |
     
    mae, Aug 3, 2007
    #2
    1. Advertisements

  3. Greetings,

    It's not a bug -- it's done on the server. .Info domains have obviously (this is not
    official, but it's the reasoning for this filtering when done in the past) been identified as
    a major source of Messenger worm activity.

    I realize your site is not, but it's not that selective I'm afraid.

    As a workaround, you can do http://www.misbruik.info

    --
    Jonathan Kay
    Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    Associate Expert
    http://www.microsoft.com/windowsxp/expertzone/
    Messenger Resources - http://messenger.jonathankay.com
    All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    You *must* contact me for redistribution rights.
    --



    "Wes." <> wrote in message
    news:...
    >i was chatting with a mate of mine, and he didn't received the url of my
    > website ?
    >
    > Could someone of you microsoft wizards tell my why i can't talk about my own
    > website ? ( http://www.misbruik.info/ )
    >
    > If you guys use something of content filtering i would like to know when my
    > message is blocked.
    >
    > This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    > windows messenger 4.7 and windows messenger 7.something.
    >
    > Can someone in the name of god tell me what's going on ?
    >
     
    Jonathan Kay [MVP], Aug 4, 2007
    #3
  4. Wes.

    Wes. Guest

    Jonathan, thanks for your reply..

    Since today i'm getting a notification if the message is blocked:
    " The following message could not be delivered to all recipients:
    http://www.misbruik.info "

    I'm pleased with that solution, so i know when the message is "blocked".
    But as you can see in the message above the workaround doesn't work anymore!

    Wesley.


    "Jonathan Kay [MVP]" wrote:

    > Greetings,
    >
    > It's not a bug -- it's done on the server. .Info domains have obviously (this is not
    > official, but it's the reasoning for this filtering when done in the past) been identified as
    > a major source of Messenger worm activity.
    >
    > I realize your site is not, but it's not that selective I'm afraid.
    >
    > As a workaround, you can do http://www.misbruik.info
    >
    > --
    > Jonathan Kay
    > Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    > Associate Expert
    > http://www.microsoft.com/windowsxp/expertzone/
    > Messenger Resources - http://messenger.jonathankay.com
    > All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    > You *must* contact me for redistribution rights.
    > --
    >
    >
    >
    > "Wes." <> wrote in message
    > news:...
    > >i was chatting with a mate of mine, and he didn't received the url of my
    > > website ?
    > >
    > > Could someone of you microsoft wizards tell my why i can't talk about my own
    > > website ? ( http://www.misbruik.info/ )
    > >
    > > If you guys use something of content filtering i would like to know when my
    > > message is blocked.
    > >
    > > This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    > > windows messenger 4.7 and windows messenger 7.something.
    > >
    > > Can someone in the name of god tell me what's going on ?
    > >

    >
     
    Wes., Aug 14, 2007
    #4
  5. Hi,

    Yes I noticed this too. The problem has gotten recent press after years of being ignored, so
    it's unclear exactly what's being tweaked about it now.

    I'm sure some sort of details will be available in the near future.

    --
    Jonathan Kay
    Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    Associate Expert
    http://www.microsoft.com/windowsxp/expertzone/
    Messenger Resources - http://messenger.jonathankay.com
    All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    You *must* contact me for redistribution rights.
    --


    "Wes." <> wrote in message
    news:...
    > Jonathan, thanks for your reply..
    >
    > Since today i'm getting a notification if the message is blocked:
    > " The following message could not be delivered to all recipients:
    > http://www.misbruik.info "
    >
    > I'm pleased with that solution, so i know when the message is "blocked".
    > But as you can see in the message above the workaround doesn't work anymore!
    >
    > Wesley.
    >
    >
    > "Jonathan Kay [MVP]" wrote:
    >
    >> Greetings,
    >>
    >> It's not a bug -- it's done on the server. .Info domains have obviously (this is not
    >> official, but it's the reasoning for this filtering when done in the past) been identified
    >> as
    >> a major source of Messenger worm activity.
    >>
    >> I realize your site is not, but it's not that selective I'm afraid.
    >>
    >> As a workaround, you can do http://www.misbruik.info
    >>
    >> --
    >> Jonathan Kay
    >> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    >> Associate Expert
    >> http://www.microsoft.com/windowsxp/expertzone/
    >> Messenger Resources - http://messenger.jonathankay.com
    >> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    >> You *must* contact me for redistribution rights.
    >> --
    >>
    >>
    >>
    >> "Wes." <> wrote in message
    >> news:...
    >> >i was chatting with a mate of mine, and he didn't received the url of my
    >> > website ?
    >> >
    >> > Could someone of you microsoft wizards tell my why i can't talk about my own
    >> > website ? ( http://www.misbruik.info/ )
    >> >
    >> > If you guys use something of content filtering i would like to know when my
    >> > message is blocked.
    >> >
    >> > This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    >> > windows messenger 4.7 and windows messenger 7.something.
    >> >
    >> > Can someone in the name of god tell me what's going on ?
    >> >

    >>
     
    Jonathan Kay [MVP], Aug 14, 2007
    #5
  6. Hi,

    And they're on mess.be. Since mess.be doesn't allow direct links to their content, I am
    repasting it for convenience

    Upon request we have received official communication from Microsoft on the *.info filtering
    that has been going on in the background for a few weeks:

    "In order to prevent the spread of a malicious advertising effort that included Windows Live
    Messenger accounts as targets, Microsoft took steps to block instant messages that include
    the words ".info" and a few additional key words to protect our customers. The targeted
    accounts were sent either info or another URL, which led to a website asking them to provide
    their Windows Live user id and password. If the customer provided that information, the user's
    complete contact list also received a message with the domain site link. This was not a
    Microsoft sponsored effort, and in order to prevent the spread of it through our service,
    instant messages that include the words ".info" and a few additional key words have been
    blocked. This action may block some safe, reputable sites and we apologize for any
    inconvenience this may cause our customers, however, given the circumstances this action was
    necessary. In an effort to remedy this moving forward, Microsoft continues to investigate
    other ways to protect our consumers from this threat.

    Microsoft recommends that Windows Live Messenger users do not provide their account
    information to third-party sites. To learn more about how to recognize a social engineering
    threat, more information is available at
    http://www.microsoft.com/athome/security/email/socialengineering.mspx. In addition, Microsoft
    continues to encourage people to follow the "Protect Your Computer" guidance of enabling a
    firewall, applying all software updates and installing anti-virus and anti-spyware software.
    Additional information can be found at www.microsoft.com/protect."
    Nothing new here, but our upset reaction to what could be considered as censorship appears to
    have come across. While writing this, I noticed that they have weakened the filter to some
    extent:

    1) You can now send .info if it's not part of an URL.

    2) You can send www.* hyperlinks to domains that start with info (with possibly a few
    exceptions), eg. www.infosyncworld.com and www.informationweek.com.

    3) If you send a blacklisted string, you'll get an error message informing you that "The
    following message could not be delivered to all recipients". Unfortunately, this notification
    appears rather randomly and not on every single filtering occasion.


    --
    Jonathan Kay
    Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    Associate Expert
    http://www.microsoft.com/windowsxp/expertzone/
    Messenger Resources - http://messenger.jonathankay.com
    All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    You *must* contact me for redistribution rights.
    --


    "Jonathan Kay [MVP]" <> wrote in message
    news:...
    > Hi,
    >
    > Yes I noticed this too. The problem has gotten recent press after years of being ignored,
    > so it's unclear exactly what's being tweaked about it now.
    >
    > I'm sure some sort of details will be available in the near future.
    >
    > --
    > Jonathan Kay
    > Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    > Associate Expert
    > http://www.microsoft.com/windowsxp/expertzone/
    > Messenger Resources - http://messenger.jonathankay.com
    > All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    > You *must* contact me for redistribution rights.
    > --
    >
    >
    > "Wes." <> wrote in message
    > news:...
    >> Jonathan, thanks for your reply..
    >>
    >> Since today i'm getting a notification if the message is blocked:
    >> " The following message could not be delivered to all recipients:
    >> http://www.misbruik.info "
    >>
    >> I'm pleased with that solution, so i know when the message is "blocked".
    >> But as you can see in the message above the workaround doesn't work anymore!
    >>
    >> Wesley.
    >>
    >>
    >> "Jonathan Kay [MVP]" wrote:
    >>
    >>> Greetings,
    >>>
    >>> It's not a bug -- it's done on the server. .Info domains have obviously (this is not
    >>> official, but it's the reasoning for this filtering when done in the past) been
    >>> identified as
    >>> a major source of Messenger worm activity.
    >>>
    >>> I realize your site is not, but it's not that selective I'm afraid.
    >>>
    >>> As a workaround, you can do http://www.misbruik.info
    >>>
    >>> --
    >>> Jonathan Kay
    >>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    >>> Associate Expert
    >>> http://www.microsoft.com/windowsxp/expertzone/
    >>> Messenger Resources - http://messenger.jonathankay.com
    >>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    >>> You *must* contact me for redistribution rights.
    >>> --
    >>>
    >>>
    >>>
    >>> "Wes." <> wrote in message
    >>> news:...
    >>> >i was chatting with a mate of mine, and he didn't received the url of my
    >>> > website ?
    >>> >
    >>> > Could someone of you microsoft wizards tell my why i can't talk about my own
    >>> > website ? ( http://www.misbruik.info/ )
    >>> >
    >>> > If you guys use something of content filtering i would like to know when my
    >>> > message is blocked.
    >>> >
    >>> > This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    >>> > windows messenger 4.7 and windows messenger 7.something.
    >>> >
    >>> > Can someone in the name of god tell me what's going on ?
    >>> >
    >>>

    >
     
    Jonathan Kay [MVP], Aug 14, 2007
    #6
  7. im just bored!

    > On Thursday, August 02, 2007 6:32 PM We wrote:


    > i was chatting with a mate of mine, and he didn't received the url of my
    > website ?
    >
    > Could someone of you microsoft wizards tell my why i can't talk about my own
    > website ? ( http://www.misbruik.info/ )
    >
    > If you guys use something of content filtering i would like to know when my
    > message is blocked.
    >
    > This "bug" was tested with more then 15 systems, using Live messenger 8.5,
    > windows messenger 4.7 and windows messenger 7.something.
    >
    > Can someone in the name of god tell me what's going on ?



    >> On Thursday, August 02, 2007 7:51 PM mae wrote:


    >> An instant message that has ".info" is blocked.
    >> Just "info" in a message is not.
    >> --
    >> mae



    >>> On Friday, August 03, 2007 12:30 AM TheCroW wrote:


    >>> It's the paranoia filtering that Micro$oft is doing. Guess your best shot is
    >>> contacting MSN Messenger folks trough the MSN site ... and wish you luck
    >>> with that cause other then an automated response you will get no answer from
    >>> those monopolists.
    >>>
    >>> Menno
    >>> who obviously is not a big MS fan ;-)



    >>>> On Friday, August 03, 2007 9:17 PM Jonathan Kay [MVP] wrote:


    >>>> Greetings,
    >>>>
    >>>> It's not a bug -- it's done on the server. .Info domains have obviously (this is not
    >>>> official, but it's the reasoning for this filtering when done in the past) been identified as
    >>>> a major source of Messenger worm activity.
    >>>>
    >>>> I realize your site is not, but it's not that selective I'm afraid.
    >>>>
    >>>> As a workaround, you can do http://www.misbruik.info
    >>>>
    >>>> --
    >>>> Jonathan Kay
    >>>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    >>>> Associate Expert
    >>>> http://www.microsoft.com/windowsxp/expertzone/
    >>>> Messenger Resources - http://messenger.jonathankay.com
    >>>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    >>>> You *must* contact me for redistribution rights.
    >>>> --
    >>>>
    >>>>
    >>>>
    >>>> "Wes." <> wrote in message
    >>>> news:...



    >>>>> On Tuesday, August 14, 2007 8:20 AM We wrote:


    >>>>> Jonathan, thanks for your reply..
    >>>>>
    >>>>> Since today i'm getting a notification if the message is blocked:
    >>>>> " The following message could not be delivered to all recipients:
    >>>>> http://www.misbruik.info "
    >>>>>
    >>>>> I'm pleased with that solution, so i know when the message is "blocked".
    >>>>> But as you can see in the message above the workaround doesn't work anymore!
    >>>>>
    >>>>> Wesley.
    >>>>>
    >>>>>
    >>>>> "Jonathan Kay [MVP]" wrote:



    >>>>>> On Tuesday, August 14, 2007 10:34 AM Jonathan Kay [MVP] wrote:


    >>>>>> Hi,
    >>>>>>
    >>>>>> Yes I noticed this too. The problem has gotten recent press after years of being ignored, so
    >>>>>> it's unclear exactly what's being tweaked about it now.
    >>>>>>
    >>>>>> I'm sure some sort of details will be available in the near future.
    >>>>>>
    >>>>>> --
    >>>>>> Jonathan Kay
    >>>>>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    >>>>>> Associate Expert
    >>>>>> http://www.microsoft.com/windowsxp/expertzone/
    >>>>>> Messenger Resources - http://messenger.jonathankay.com
    >>>>>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    >>>>>> You *must* contact me for redistribution rights.
    >>>>>> --
    >>>>>>
    >>>>>>
    >>>>>> "Wes." <> wrote in message
    >>>>>> news:...



    >>>>>>> On Tuesday, August 14, 2007 12:21 PM Jonathan Kay [MVP] wrote:


    >>>>>>> Hi,
    >>>>>>>
    >>>>>>> And they're on mess.be. Since mess.be doesn't allow direct links to their content, I am
    >>>>>>> repasting it for convenience
    >>>>>>>
    >>>>>>> Upon request we have received official communication from Microsoft on the *.info filtering
    >>>>>>> that has been going on in the background for a few weeks:
    >>>>>>>
    >>>>>>> "In order to prevent the spread of a malicious advertising effort that included Windows Live
    >>>>>>> Messenger accounts as targets, Microsoft took steps to block instant messages that include
    >>>>>>> the words ".info" and a few additional key words to protect our customers. The targeted
    >>>>>>> accounts were sent either info or another URL, which led to a website asking them to provide
    >>>>>>> their Windows Live user id and password. If the customer provided that information, the user's
    >>>>>>> complete contact list also received a message with the domain site link. This was not a
    >>>>>>> Microsoft sponsored effort, and in order to prevent the spread of it through our service,
    >>>>>>> instant messages that include the words ".info" and a few additional key words have been
    >>>>>>> blocked. This action may block some safe, reputable sites and we apologize for any
    >>>>>>> inconvenience this may cause our customers, however, given the circumstances this action was
    >>>>>>> necessary. In an effort to remedy this moving forward, Microsoft continues to investigate
    >>>>>>> other ways to protect our consumers from this threat.
    >>>>>>>
    >>>>>>> Microsoft recommends that Windows Live Messenger users do not provide their account
    >>>>>>> information to third-party sites. To learn more about how to recognize a social engineering
    >>>>>>> threat, more information is available at
    >>>>>>> http://www.microsoft.com/athome/security/email/socialengineering.mspx. In addition, Microsoft
    >>>>>>> continues to encourage people to follow the "Protect Your Computer" guidance of enabling a
    >>>>>>> firewall, applying all software updates and installing anti-virus and anti-spyware software.
    >>>>>>> Additional information can be found at www.microsoft.com/protect."
    >>>>>>> Nothing new here, but our upset reaction to what could be considered as censorship appears to
    >>>>>>> have come across. While writing this, I noticed that they have weakened the filter to some
    >>>>>>> extent:
    >>>>>>>
    >>>>>>> 1) You can now send .info if it's not part of an URL.
    >>>>>>>
    >>>>>>> 2) You can send www.* hyperlinks to domains that start with info (with possibly a few
    >>>>>>> exceptions), eg. www.infosyncworld.com and www.informationweek.com.
    >>>>>>>
    >>>>>>> 3) If you send a blacklisted string, you'll get an error message informing you that "The
    >>>>>>> following message could not be delivered to all recipients". Unfortunately, this notification
    >>>>>>> appears rather randomly and not on every single filtering occasion.
    >>>>>>>
    >>>>>>>
    >>>>>>> --
    >>>>>>> Jonathan Kay
    >>>>>>> Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
    >>>>>>> Associate Expert
    >>>>>>> http://www.microsoft.com/windowsxp/expertzone/
    >>>>>>> Messenger Resources - http://messenger.jonathankay.com
    >>>>>>> All posts unless otherwise specified are (c) 2007 Jonathan Kay.
    >>>>>>> You *must* contact me for redistribution rights.
    >>>>>>> --
    >>>>>>>
    >>>>>>>
    >>>>>>> "Jonathan Kay [MVP]" <> wrote in message
    >>>>>>> news:...
     
    patricia aguilar, Apr 9, 2011
    #7
    1. Advertisements

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads
  1. DavePie

    HP Live Chat works but Symantec Live Chat crashes IE

    DavePie, Feb 12, 2007, in forum: Windows Vista File Management
    Replies:
    1
    Views:
    572
    Ronnie Vernon MVP
    Feb 12, 2007
  2. jim

    OT: RIAA: It's 'Illegal' to Rip Your Own CDs to Your Own Computer

    jim, Jan 3, 2008, in forum: Windows Vista General Discussion
    Replies:
    124
    Views:
    2,692
    The Ghost In The Machine
    Jan 16, 2008
  3. Rich T

    PLEASE how can I "own" my own computer?

    Rich T, Mar 1, 2008, in forum: Windows Vista General Discussion
    Replies:
    63
    Views:
    1,201
    NoStop
    Mar 2, 2008
  4. Frank

    I don't "own" this ng, but I sure as hell "own' these losers!...LOL!

    Frank, Jul 19, 2008, in forum: Windows Vista General Discussion
    Replies:
    10
    Views:
    603
    Adam Albright's Psychiatrist
    Jul 21, 2008
  5. Laurens Van Dyck

    save voice chat/webcam chat

    Laurens Van Dyck, Oct 29, 2003, in forum: Windows MSN Messenger
    Replies:
    1
    Views:
    1,048
    Jonathan Kay [MVP]
    Oct 29, 2003
  6. swhite1

    Copies of my own DVDs to my own Media Center

    swhite1, Jun 4, 2007, in forum: Windows Media Center
    Replies:
    12
    Views:
    603
    Jaime
    Jul 6, 2007
  7. Mike
    Replies:
    5
    Views:
    1,282
    Jonathan Kay [MVP]
    Mar 12, 2010
  8. rnhell

    "blocked::blocked:http://www.site.com/" error

    rnhell, Sep 1, 2010, in forum: Windows Live Mail
    Replies:
    0
    Views:
    1,075
    rnhell
    Sep 1, 2010
Loading...